DS Connection Issues

[ar_shriks]

We have installed Datastage (Version 6.0) on a Windows 2003 server. We are in the process of migrating all our datastage jobs to this server from the existing Windows 2000 server. We have the following issues:

Problem 1
=========
1) While loggin on to datastge, if we 'Omit' the user name and password we get the error messages:

First Message:
DSR.ADMIN: Failed to add user to UV_USERS file.

Second Message:
Access Denied: Internal SQL Error.
Failed to register this user for SQL.

We fail to understand why we get this message. What could we have missed during the installation process? Please note that we are able to connect to DS if username and password are provided.

Problem 2
=========
2) The following error message is displayed in the log file when the target is ORAOCIBL irrespective of whatever is the source.

DataStage Job 1 Phantom 2756
Program "DSP.Open": Line 122, Exception raised in GCI subroutine:
Access violation.
Attempting to Cleanup after ABORT raised in stage TestORAOCIBL..ORAOCIBL_2
DataStage Phantom Aborting with @ABORT.CODE = 3

What could be the reason for the "Access violation"? Is it related to Oracle or Windows 2003?

ARE THE ABOVE TWO MESSAGES RELATED IN ANY WAY?

Any sort of suggestions or solutions are most welcome.

Thanks & Regards,
Shrikanth

[denzilsyb]

hi shrikanth

problem 1:

do you log into DS with the same user that is logged in on the windows server? when you select 'omit' the user currently logged on to the windows server is authenticated against DS.

It might be that you are using a lower level security user to access key files that DS uses to verify connectivity. I am mentioning this because we have a strict security protocol here and i have experienced problems mainly because the user i have does not have access to write to C:\Program Files\etc\etc\.

So, test the user and let us know.

problem 2:

Im not sure if they are related; test problem 1 and then we can move onto problem 2..

[chulett]

For Problem #2 - have you verified that you have an Oracle client installed on and have Oracle connectivity from the new server from outside of DataStage? If you can 'tnsping' or get to your target databases from something like SQL*Plus from it, that would narrow down the problem to an issue with DataStage.

[ray.wurlod]

UV_USERS is one of the SQL system tables for DataStage; it records users to whom database privileges (CONNECT, RESOURCE or DBA) have been granted. You require DBA privilege to grant database privileges. To find out who has DBA privilege, execute the query

Code: Select all

SELECT NAME FROM UV_USERS WHERE DBAUTH = 'YES';

(Note that identifiers are case sensitive.)

The other problem, generated from the DSP.Open routine, is unrelated. Firstly it doesn't occur when logging in. Secondly, it's not being generated from any of the "UV" components. It has to do with trying to establish a connection from a plug-in stage; from your description this seems to be an OCI stage, and may relate to accessing table/column definitions during that process. If you reset (not re-compile, reset) the job, you may get an event logged "from previous run" that contains additional diagnostic information.

Access violation is a generic description of any attempt to access a memory address that is not owned by the process making the attempt. It's often associated with processing character strings that are too long for the buffer allocated to them, or sometimes to processing NULL.

[Eric]

Windows 2003 Server uses different security policies to other Windows platforms. In order to allow access to a DataStage server on this platform, additional setup steps are required.

This is taken from a newer version than 6.0, Perhaps these will be the same ... Could you could ask you Ascential contact?

[Oancea]

Sometime, setting the value of the NLS on the Stage to the same the Database has, can eliminate "Access violation" error message.