DS Connection Issues
Posted: Mon Sep 06, 2004 1:02 am
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
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