Page 1 of 1

Re: Client not able to connect to DataStage server

Posted: Wed Sep 20, 2006 6:40 am
by psv
Try to login with admin user i.e dsadm and create a test project.Then try to login with other user id.

Also check whether impersonation mode is enabled on Datastage server.

Posted: Wed Sep 20, 2006 7:06 am
by rijeshpp
There are already 5 projects existing on the server.. and users were able to connect to the server till yesterday. Suddenly this problem started today. The server is running fine...

Impersonation mode is enabled on the server.

What could be the other reasons?

Posted: Wed Sep 20, 2006 7:09 am
by Krazykoolrohit
Is Datastage server running ? try restarting it.

Posted: Wed Sep 20, 2006 7:48 am
by rijeshpp
yes, did so many times. DataStage server is running fine and it has started under dsadm user using av -admin -start. Please see the uv -admin -info

bash-2.03$ ps -ef |grep DataStage
root 514 1 0 17:41:49 ? 0:00 /isvol1/GM/apps/IBM/Ascential/DataStage/home/dsadm/Ascential/DataStage/PXEngine
root 489 1 0 17:41:40 ? 0:00 /isvol1/GM/apps/IBM/Ascential/DataStage/home/dsadm/Ascential/DataStage/DSEngine
dsadm 769 767 0 17:42:29 pts/2 0:00 grep DataStage
bash-2.03$

================
bash-2.03$ uv -admin -info

Details for DataStage Engine release 7.5.1.2 instance "ade"
===============================================================================
Install history : Installed by root (admin:dsadm) on: Apr 06 2006 13:06:16
: Upgraded by root (admin:dsadm) on: Apr 06 2006 13:55:00
: Upgraded by root (admin:dsadm) on: Apr 17 2006 12:00:38
Instance tag : ade
Engine status : Running w/active nls
Engine location : /isvol1/GM/apps/IBM/Ascential/DataStage/home/dsadm/Ascential/DataStage/DSEngine
Binary location : /isvol1/GM/apps/IBM/Ascential/DataStage/home/dsadm/Ascential/DataStage/DSEngine/bin
Impersonation : Enabled
Administrator : dsadm
Autostart mode : enabled
Autostart link(s) : /etc/rc2.d/S99ds.rc
Startup script : /isvol1/GM/apps/IBM/Ascential/DataStage/home/dsadm/Ascential/DataStage/DSEngine/sample/ds.rc
Cache Segments : 0 active
User Segments : 1 active

1 phantom printer segments!
DSnum Uid Pid Ppid C Stime Tty Time Command
64739carduser 797 796 0 17:44:53 ? 0:00 dsapi_slave 8 7 0
bash-2.03$
===============

Even we restarted the server and tried.. no luck..

Is there any way i can enable server logging and see whats wrong?

Posted: Wed Sep 20, 2006 9:00 am
by srinagesh
Can you quickly check if the Project Directories exist and the permissions on those directories are set up correctly.

Also check if the dstage group has been modified in the recent past.

Posted: Wed Sep 20, 2006 6:48 pm
by kumar_s
Is it only from single machnie or from all the clinet pc?
Is it only to single project or to all the 5 projects?
If it is only to single project, you may need to check the integrity of you project files or you may even need to FIX some files.
If its only with one PC, reinstall the client software.

Posted: Thu Sep 21, 2006 12:59 am
by rijeshpp
Another update, it looks like some problem happned in the project entries. When we ran the command ./dsadmin -listprojects , its not able to read the project entries.....

bash-2.03$ ./dsadmin -listprojects

ERROR: 81016

Status code = 81016
bash-2.03$

Where as the projects folders and files are there on the server..

bash-2.03$ pwd
/isvol1/GM/apps/IBM/Ascential/DataStage/home/dsadm/Ascential/DataStage/DSEngine/projects
bash-2.03$ ls -la
total 536
drwxrwxr-x 9 dsadm dstage 512 Sep 21 11:41 .
drwxrwxr-x 57 dsadm dstage 4608 Sep 21 11:10 ..
drwxrwxr-x 389 dsadm dstage 9216 Sep 21 09:03 Card20
drwxrwxr-x 1133 dsadm dstage 24576 Sep 21 09:03 GMVPS
drwxrwxr-x 71 dsadm dstage 2560 Sep 21 09:03 MQIS
drwxrwxr-x 4678 dsadm dstage 101888 Sep 21 09:03 QIS2
drwxrwxr-x 4370 dsadm dstage 94720 Sep 21 09:03 card30
drwxrwxr-x 814 dsadm dstage 17920 Sep 21 09:03 card30_Test
drwxrwxr-x 67 dsadm dstage 2560 Sep 20 19:59 gm
bash-2.03$

Where is teh configuration file in DaatSatge? It seems to be some entries are corruped. Any ideas?

Posted: Thu Sep 21, 2006 2:13 am
by ray.wurlod
That's because the command you needed was dsjob, not dsadmin. There is no such command as dsadmin.