once I amended the routine not to write any log to the Sequencer. i got the error like 'Failed to connect RT_LOG43'ArndW wrote:Then you have reached an impasse. Either reduce the number and size of messages or, better yet, don't log them in the job log but elsewhere. This heavy I/O to the log file is most certainly slowing your job down as well.
Unable to view the Log file.
Moderators: chulett, rschirm, roy
-
prasanna_anbu
- Participant
- Posts: 42
- Joined: Thu Dec 28, 2006 1:39 am
</a>-
Sainath.Srinivasan
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
prasanna_anbu
- Participant
- Posts: 42
- Joined: Thu Dec 28, 2006 1:39 am
Sainath.Srinivasan wrote:Why not run with a small volume ? Something like 10 records.
That way you can diagnose the problem easier.
Are you having errors in the load ? Is there any metadata mismatch ? Or is it your routine that is logging so many rows ?
Other than 'Failed to connect to RT_LOG43'. I am not able to see any error messages. I planned to try with minimum records but now the sequencer itself not shown in the director, if i tried to import newly it shows the same error.
-
prasanna_anbu
- Participant
- Posts: 42
- Joined: Thu Dec 28, 2006 1:39 am
I re-imported the jobs with keep the copy, now I am able to see the logs.prasanna_anbu wrote:Sainath.Srinivasan wrote:Why not run with a small volume ? Something like 10 records.
That way you can diagnose the problem easier.
Are you having errors in the load ? Is there any metadata mismatch ? Or is it your routine that is logging so many rows ?
Other than 'Failed to connect to RT_LOG43'. I am not able to see any error messages. I planned to try with minimum records but now the sequencer itself not shown in the director, if i tried to import newly it shows the same error.
I dont get the clear picture of the previous error. Thanks for everyone.
