DataStage job fails with code=-14 [Timed out while waiting for an event]
DataStage job fails with code=-14 [Timed out while waiting for an event] – this generally happens when jobs are called from sequencers.
Resolving the problem :
Follow steps 1-3 in resolving this error.
1) DSWaitStartup – environment variable -
When multiple instances of a job are run from a sequence, and one or more of the job instances are set to reset, the sequence might report a status=99 or -14. This can occur because the controlling sequence did not give the job instances enough time to reset before polling its status. The start up time for a job reset must be increased. The environment variable DSWaitResetStartup can be used for this purpose.
When multiple instances of a job are run from a sequence, and one or more of the job instances are set to reset, the sequence might report a status=99 or -14. This can occur because the controlling sequence did not give the job instances enough time to reset before polling its status. The start up time for a job reset must be increased. The environment variable DSWaitResetStartup can be used for this purpose.
(The maximum value that can be set for DSWaitResetStartup is the value of DSWaitStartup (default is 60). For example, if a value of 120 is required for DSWaitResetStartup, then ensure that DSWaitStartup is also set to a minimum of 120.)
2) uvconfig changes:
Unix.Linux:
A# Please log on as dsadm or root.
B# Next, make sure there are no connections to DataStage
(Unix/Linux) specific instructions – Windows will need to use Task Manager
ps -ef | grep dsapi –>This will test for open client connections
ps -ef | grep dscs –> This will test for running jobs.if you find any client connections
and you know everyone is out, they are probably dormant.
Please kill them using kill -9.
C# If all is clear, from the DSEngine directory, source the dsenv and
shut down the server. ./dsenv./bin/uv -admin -stop
D# edit the uvconfig file and make the necessary changes
MFILES to 150
T30FILES to 300
RLTABSZ 200
MAXRLOCK to 199.
E# To save the changes to uvconfig and generate a new .uvconfig binary
file you will need to run regen:./bin/uv -admin -regen
F# Now restart server:./bin/uv -admin -start
Unix.Linux:
A# Please log on as dsadm or root.
B# Next, make sure there are no connections to DataStage
(Unix/Linux) specific instructions – Windows will need to use Task Manager
ps -ef | grep dsapi –>This will test for open client connections
ps -ef | grep dscs –> This will test for running jobs.if you find any client connections
and you know everyone is out, they are probably dormant.
Please kill them using kill -9
C# If all is clear, from the DSEngine directory, source the dsenv and
shut down the server. ./dsenv./bin/uv -admin -stop
MFILES to 150
T30FILES to 300
RLTABSZ 200
MAXRLOCK to 199.
file you will need to run regen:./bin/uv -admin -regen
Windows:
a. Make sure you are the Administrator on this machine
b. Next, make sure there are no connections to DataStage
c. If there are no connections, stop the dsrpc services.
d. edit the uvconfig file in the DSEngine directory and make the necessary changes
MFILES to 150
T30FILES to 300
RLTABSZ 200
MAXRLOCK to 199.
Syncaloc to 0
e. To save the changes to uvconfig and generate a new .uvconfig binary file you will need to run regen from the DSEngine directory: bin\uvregen
f. Now restart dsrpc services
a. Make sure you are the Administrator on this machine
b. Next, make sure there are no connections to DataStage
c. If there are no connections, stop the dsrpc services.
d. edit the uvconfig file in the DSEngine directory and make the necessary changes
MFILES to 150
T30FILES to 300
RLTABSZ 200
MAXRLOCK to 199.
Syncaloc to 0
e. To save the changes to uvconfig and generate a new .uvconfig binary file you will need to run regen from the DSEngine directory: bin\uvregen
f. Now restart dsrpc services
3) If the above 2 steps do not resolve the -14 error and you are using DataStage/Information Server 8.1 – verify that either patch JR30015### is installed in the Version.xml or that you have FixPack1 installed for 8.1.
NOTE: You may need to schedule your job runs so there are not so many processes running at the same time.
NOTE: You may need to schedule your job runs so there are not so many processes running at the same time.
No comments:
Post a Comment