Data Stage connection Error.....

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
MaheshKumar Sugunaraj
Participant
Posts: 84
Joined: Thu Dec 04, 2003 9:55 pm

Data Stage connection Error.....

Post by MaheshKumar Sugunaraj »

Hi All,

The regarding a new issue which i seen for the first time. The problem is somebody has installed DS Server on the HP-UX box and I installed DS Client and tried to connect to the Server for the first time, it gives me the following error:

Failed to connect to host: <server_name>, project: UV
(Internal Error (39202))

Any help would be appreciated.

Thanks & Regards
Mahesh
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

Verify the permissions of the project directory, the dsenv file, the umask setting in the ds.rc script, etc. Your userid is probably running into group/permissions issues.

99% of first time access problems relate to permissions.
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
ketfos
Participant
Posts: 562
Joined: Mon May 03, 2004 8:58 pm
Location: san francisco
Contact:

Post by ketfos »

Hi,
Try rebotting the server
This error code 39202 relates to a failure to connect. InterCall Developer's Guide from IBM describes that
"slave failed to give server the Go Ahead message"

Ketfos
trokosz
Premium Member
Premium Member
Posts: 188
Joined: Thu Sep 16, 2004 6:38 pm
Contact:

Post by trokosz »

Hmm...it's more than likely account permission error where you must belong to the dsadm group (such as dstage) that your root admin established during install....you can have secondary groups but you must always be assigned the primary dsadm group.
MaheshKumar Sugunaraj
Participant
Posts: 84
Joined: Thu Dec 04, 2003 9:55 pm

Post by MaheshKumar Sugunaraj »

Hi All,

Thank you for your valuable sugeestions, I have done the necessary checks and they have installed the DS Server as root and there were a few permission issues which I checked and corrected.

the dsenv file is in the "dsadm" owner and group.

Now after checking and correcting as stated, when I restart the DS i get the following errors:

# bin/uv -admin -start
Unable to get disk shared memory segment: Invalid argument

An error has occurred during DataStage initialization
Please contact the system administrator
Error code: 2 2
An error has occurred during DataStage initialization
Please contact the system administrator
Error code: 2 2
An error has occurred during DataStage initialization
Please contact the system administrator
Error code: 2 2
DataStage Engine 7.0.1.1 instance "ade" has been brought up.

Any help would heighly be apprecaited.

Thanks & Regards
Mahesh
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

You need to start/stop DataStage as dsadm rather than root.

Did you load dsenv before starting the DataStage Engine?
MaheshKumar Sugunaraj
Participant
Posts: 84
Joined: Thu Dec 04, 2003 9:55 pm

Post by MaheshKumar Sugunaraj »

Hi Sainath,

**************

You need to start/stop DataStage as dsadm rather than root.

Did you load dsenv before starting the DataStage Engine?

************

As stated, I have loaded the dsenv variables before starting the DS server. If I goto dsadm and do a DS Start then asks for a passoword so I logged in as root and started the services

We still get the above messages.

I have also checked the segments which have been allaocated.

Thanks & Regards
Mahesh
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Can you check who owns the directory mentioned in your /.dshome file. Also check the permissions of its sub-directories.

I believe there is some kind of permission issue(s) in your setup that is preventing datastage from starting.

What happens when you issue the command 'netstat -na | grep 31538' ?
MaheshKumar Sugunaraj
Participant
Posts: 84
Joined: Thu Dec 04, 2003 9:55 pm

Post by MaheshKumar Sugunaraj »

Sainath.Srinivasan wrote:Can you check who owns the directory mentioned in your /.dshome file. Also check the permissions of its sub-directories.

I believe there is some kind of permission issue(s) in your setup that is preventing datastage from starting.

What happens when you issue the command 'netstat -na | grep 31538' ?
I have rechecked the permissions and its the same as stated.

when I do a netstat -na | grep 31538

I get one line LISTEN

I also ran the script to clear the connections and inspite of it we get the error message as mentioned.

Any help would be appreciated.

Thanks & Regards
Mahesh
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

The line listen says that something is running and occupying the port 31538 already. Maybe your datastage is up and running already.

You may need to stop the server before starting it.

Try `cat /.dshome`/bin/uv -admin -stop
command after loading your dsenv.

Then try the netstat command. You must not have any return line.

Only then you can start datastage.
trokosz
Premium Member
Premium Member
Posts: 188
Joined: Thu Sep 16, 2004 6:38 pm
Contact:

Post by trokosz »

It's ok if dsadm owns dsenv.....root installed with dsadm option and impersonation is on and so on so this is good....if I see "shared memory" error I think of the uvconfig file in $DSHOME. Either the permission on this file is not right or possibly the DMEMOFF and PMEMOFF settings in this file are too low.

Just some thoughts
MaheshKumar Sugunaraj
Participant
Posts: 84
Joined: Thu Dec 04, 2003 9:55 pm

Post by MaheshKumar Sugunaraj »

Hi All,

Thanks for all your valuable suggestions, we have resolved this issue.

Just to share what we did,

We had asked the UNIX Admin person to change the Kernal parameters as per Ascential support request and they have done the necessay changes and then we stopped and restarted the DS Services and we are able to connect to server now.

Thank you all again.

With Regards
Mahesh
Post Reply