Datastage Common Errors and Solutions
1.
Failed to authenticate the current user against the selected Domain:
Could not connect to server.
RC:
Client has invalid entry in host file
Server listening port might be blocked by a
firewall
Server is down
SOL:
Update the host file on client system so that the server hostname can be
resolved from client.
Make sure the WebSphere TCP/IP ports are
opened by the firewall.
Make sure the WebSphere application server is
running. (OR)
Restart Websphere services.
2.
The connection was refused or the RPC daemon is not running (81016)
RC:
The dsprcd process must be running in order to be able to login to
DataStage.
If you restart DataStage, but the socket used
by the dsrpcd (default is 31538) was busy, the dsrpcd will fail to start. The
socket may be held by dsapi_slave processes that were still running or recently
killed when DataStage was restarted.
SOL:
Run "ps -ef | grep dsrpcd" to confirm the dsrpcd process is
not running.
Run "ps -ef | grep dsapi_slave" to
check if any dsapi_slave processes exist. If so, kill them.
Run "netstat -a | grep dsprc" to
see if any processes have sockets that are ESTABLISHED, FIN_WAIT, or
CLOSE_WAIT. These will prevent the dsprcd from starting. The sockets with
status FIN_WAIT or CLOSE_WAIT will eventually time out and disappear, allowing
you to restart DataStage.
Then Restart DSEngine. (if above doesn’t work) Needs to reboot
the system.
3.
To save Datastage logs in notepad or readable format
SOL:
a) /opt/ibm/InformationServer/server/DSEngine (go to this directory)
./bin/dsjob -logdetail project_name job_name
>/home/dsadm/log.txt
b) In director client, Project tab Print select print to file option
and save it in local directory.
4.
"Run time error '457'. This Key is already associated with an
element of this collection."
SOL:
Needs to rebuild repository objects.
a)
Login to the Administrator client
b)
Select the project
c)
Click on Command
d)
Issue the command ds.tools
e)
Select option ‘2’
f)
Keep clicking next until it finishes.
g)
All objects will be updated.
5.
To stop the datastage jobs in linux level
SOL:
ps –ef | grep dsadm
To Check process id and phantom jobs
Kill -9 process_id
6.
To run datastage jobs from command line
SOL:
cd
/opt/ibm/InformationServer/server/DSEngine
./dsjob -server $server_nm -user
$user_nm -password $pwd
-run $project_nm $job_nm
7.
Failed to connect to JobMonApp on port 13401.
SOL:
needs to restart jobmoninit script (in
/opt/ibm/InformationServer/Server/PXEngine/Java)
Type sh jobmoninit
start $APT_ORCHHOME
Add 127.0.0.1 local host in /etc/hosts file
(Without local entry, Job monitor will be unable to use the ports
correctly)
8. While running ./NodeAgents.sh start command... getting the following error: “LoggingAgent.sh process stopped unexpectedly”
8. While running ./NodeAgents.sh start command... getting the following error: “LoggingAgent.sh process stopped unexpectedly”
SOL: needs to kill
LoggingAgentSocketImpl
Ps –ef
| grep
LoggingAgentSocketImpl (OR)
PS –ef
| grep Agent (to check the process id of the above)
9. Warning: A
sequential operator cannot preserve the partitioning of input data set on input
port 0
SOL: Clear the
preserve partition flag before Sequential file stages.
10. Warning: A user
defined sort operator does not satisfy the requirements.
SOL: Check the order of sorting columns and make
sure use the same order when use join stage after sort to joing two inputs.
11. Conversion
error calling conversion routine timestamp_from_string data may have been lost.
xfmJournals,1: Conversion error calling conversion routine decimal_from_string
data may have been lost
SOL: check for the
correct date format or decimal format and also null values in the date or
decimal fields before passing to datastage StringToDate,
DateToString,DecimalToString or StringToDecimal functions.
12. To display all
the jobs in command line
SOL: cd /opt/ibm/InformationServer/Server/DSEngine/bin
./dsjob -ljobs <project_name>
13. “Error trying
to query dsadm[]. There might be an issue in database server”
SOL: Check XMETA
connectivity.
db2 connect to xmeta (A connection to or activation of
database “xmeta” cannot be made because of
BACKUP pending)
14. “DSR_ADMIN:
Unable to find the new project location”
SOL: Template.ini
file might be missing in /opt/ibm/InformationServer/Server.
Copy the
file from another severs.
15. “Designer
LOCKS UP while trying to open any stage”
SOL: Double click on
the stage that locks up datastage
Press
ALT+SPACE
Windows
menu will popup and select Restore
It will
show your properties window now
Click on “X” to close this window.
Now, double
click again and try whether properties window appears.
16. “Error Setting
up internal communications (fifo RT_SCTEMP/job_name.fifo)
SOL: Remove the
locks and try to run (OR)
Restart
DSEngine and try to run (OR)
Go to /opt/ibm/InformationServer/server/Projects/proj_name/
ls RT_SCT* then
rm –f RT_SCTEMP
then try to
restart it.
17. While
attempting to compile job, “failed to
invoke GenRunTime using Phantom process helper”
RC: /tmp space
might be full
Job status
is incorrect
Format
problems with projects uvodbc.config file
SOL: a) clean up /tmp directory
b) DS Director à JOB à clear status file
c)
confirm uvodbc.config has the following entry/format:
[ODBC SOURCES]
<local uv>
DBMSTYPE = UNIVERSE
Network = TCP/IP
Service = uvserver
Host = 127.0.0.1
