Sunteți pe pagina 1din 7

I have this strange thing happening to our DataStage environment: I have this DataStage Server job extracting data

from a table and updating same table based on some rules. Job finished with warning. When I am opening Director log for that job to see th e warnings and fix the job- it says "retireving" and hangs. Then I close the Dir ector client using Windows Task Manager. But after that no one is able to login to DataStage. Error: Failed to connect to host: moppgmddwd01, project: INSIGHT_DEV (Internal Error (39202)) Support team is bringing the server back up by rebootoing server etc. its long p rocess. This issue is reproducable -Everytime I goes to see the job log, this is happeni ng. Issue is with log of this job only. I can see all other logs just fine. Has anyone had similar experience? Please through some insights and probable causes if you can . Thanks a lot! _________________ Attitude is everything.... View user's profile Send private message ArndW Participant Group memberships: Premium Members, Inner Circle, Australia Usergroup Joined: 16 Nov 2004 Posts: 14456 Location: Germany Points: 81426 Posted: Tue Oct 19, 2010 10:31 am Reply with quote

Back to top

--------------------------------------------------------------------------------

Perhaps the log is very large or corrupt or both. This can be fixed if you "Job -> Clear Log -> Immediate Clear all entries" from the director. _________________

View user's profile Send private message Send e-mail Visit poster's website R ate this response: 0 1 2 3 4 5 Not yet rated

just4geeks

Group memberships: Premium Members Joined: 26 Aug 2006 Posts: 517 Location: Mclean, VA Points: 4861 Posted: Tue Oct 19, 2010 10:59 am Reply with quote

Back to top

--------------------------------------------------------------------------------

Quote: "Job -> Clear Log -> Immediate Clear all entries" from the director Thanks ArndW! Currently we can't get to Director. I will try that once we do. If we can delete the log file for that job from project directory, will it work? How to locate the job log created by that job in the project directory? Take care! --Added: Basically How can we fix this issue withour rebooting the server? _________________ Attitude is everything.... View user's profile Send private message 4 5 Not yet rated sajarman Participant Rate this response: 0 1 2 3

Joined: 28 Nov 2005 Posts: 41 Points: 321 Posted: Tue Oct 19, 2010 11:36 am Reply with quote Back to top

--------------------------------------------------------------------------------

I guess the job is throwing many info or warning messages that is causing the lo gs to be huge which leads to hung log retrieval process.

Generally the warnings will be logged for each row encountering the issue. Run t he job with the option 'Abort after 50 warnings' and see how it works. Fix the c ause of warning messages. Otherwise you can also log all the messages to a UNIX file and read it from ther e and fix the issues. View user's profile Send private message 4 5 Not yet rated dsusersaj Participant Rate this response: 0 1 2 3

Joined: 17 Dec 2007 Posts: 95 Points: 584 Posted: Tue Oct 19, 2010 12:23 pm Reply with quote Back to top

--------------------------------------------------------------------------------

just4geeks wrote: Quote: "Job -> Clear Log -> Immediate Clear all entries" from the director Thanks ArndW! Currently we can't get to Director. I will try that once we do. If we can delete the log file for that job from project directory, will it work? How to locate the job log created by that job in the project directory? Take care! --Added: Basically How can we fix this issue withour rebooting the server? IF you know the job name , login to administrator and go to your correspoding pr oject. Then click command. Execute the below command whic will give your job number(No.) select * from DS_JOBS where NAME='JOB_NAME' Then in the command line execute CLEAR.FILE RT_LOGnnnn Where nnn is job number. This should empty the log file if you have write privil eges. View user's profile Send private message Rate this response: 0 1 2 3

Not yet rated

just4geeks

Group memberships: Premium Members Joined: 26 Aug 2006 Posts: 517 Location: Mclean, VA Points: 4861 Posted: Tue Oct 19, 2010 12:42 pm Reply with quote

Back to top

--------------------------------------------------------------------------------

Thanks a lot! Quote: IF you know the job name , login to administrator and go to your correspoding pr oject. Then click command. We can't get to administrator because of this issue. We are unable to login to a ny DataStage client. Quote: Then in the command line execute CLEAR.FILE RT_LOGnnnn How to find which job created which log file. In other words how to find 'nnn' n umber belongs to which job? Thanks, Tara _________________ Attitude is everything.... View user's profile Send private message 4 5 Not yet rated dsusersaj Participant Rate this response: 0 1 2 3

Joined: 17 Dec 2007 Posts: 95 Points: 584

Posted: Tue Oct 19, 2010 12:55 pm Reply with quote

Back to top

--------------------------------------------------------------------------------

nnn is nothing but the job number that you find out by running the command select * from DS_JOBS where NAME='JOB_NAME' You get category, job description and job number by runnign this command View user's profile Send private message 4 5 Not yet rated dsusersaj Participant Rate this response: 0 1 2 3

Joined: 17 Dec 2007 Posts: 95 Points: 584 Posted: Tue Oct 19, 2010 1:00 pm Reply with quote Back to top

--------------------------------------------------------------------------------

just4geeks wrote: Thanks a lot! Quote: IF you know the job name , login to administrator and go to your correspoding pr oject. Then click command. We can't get to administrator because of this issue. We are unable to login to a ny DataStage client. Quote: Then in the command line execute CLEAR.FILE RT_LOGnnnn How to find which job created which log file. In other words how to find 'nnn' n umber belongs to which job? Thanks, Tara To be more clear the two commands which I mentioned needs to be run from adminis trator. So if you cannot login to administrator this might not work for you.

View user's profile Send private message 4 5 Not yet rated rameshrr3

Rate this response: 0

Group memberships: Premium Members Joined: 10 May 2004 Posts: 294 Location: South Central Pennsylvania Points: 3070 Posted: Tue Oct 19, 2010 1:00 pm Reply with quote

Back to top

--------------------------------------------------------------------------------

Quote: We can't get to administrator because of this issue. We are unable to login to a ny DataStage client. Try logging on to the server command line prompt using telnet/ssh, go to DSEngin e directory and run Code: uvsh or Code: dssh after uv command prompt appears , use Code: LOGTO <projectname> to log on to you project and start issuing the UV commands _________________ What If God was the Devil in disguise.. What If..? View user's profile Send private message 4 5 Not yet rated -Rate this response: 0 1 2 3

Thanks Guys! This really helped. We followed all these steps and our environment is up and running again!! Take care

_________________ Attitude is everything.... View user's profile Send private message 4 5 Not yet rated Rate this response: 0 1 2 3