Hi,
We have the debugger in DataStage 8.7. Can it be a replacement for peek stage which we generally use.
Thanks,
Prasanna
Can debug option in 8.7 replace peek stage
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Yes, it can. But it's overkill, and jobs in the debugger run (necessarily) far more slowly than not in the debugger.
You can also set the "compile in Trace mode" option in job properties. This effectively puts a Peek stage on every link in the job. This works whether or not the job is running in the debugger.
You can also set the "compile in Trace mode" option in job properties. This effectively puts a Peek stage on every link in the job. This works whether or not the job is running in the debugger.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Thank you Ray.
I have a scenario where the job is aborting at the target oracle connector stage while inserting into a table. The error which it is giving is
ORA-00060: deadlock detected while waiting for resource.
The OCI function OCIStmtExecute returned status -1. Error code: 24381, Error message: ORA-24381: error(s) in array DML
Now, I can put a peek stage and reject the erroneous record from the target stage.
But I do not want to change the job and do that.
Is there a way we can find this out using the datastage debugger.
I tried using the debugger, but unable to get this. Can you let me know how to achieve this.
I have a scenario where the job is aborting at the target oracle connector stage while inserting into a table. The error which it is giving is
ORA-00060: deadlock detected while waiting for resource.
The OCI function OCIStmtExecute returned status -1. Error code: 24381, Error message: ORA-24381: error(s) in array DML
Now, I can put a peek stage and reject the erroneous record from the target stage.
But I do not want to change the job and do that.
Is there a way we can find this out using the datastage debugger.
I tried using the debugger, but unable to get this. Can you let me know how to achieve this.
-
priyadarshikunal
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
In the alert log from what I recall. Talk to your DBA. As noted, the "deadlock trace file" will have all of the gory details behind the issue. Are you aware of the kind of things that can cause a deadlock? Is this error repeatable or does it depend on the time of day the job is run or what other processes are running at the time? Wondering if it is a "self deadlock" or not.
And these kind of things can be hard to debug as the debugger can change how the job runs under the covers and thus resolve (as in not cause) the issue.
And these kind of things can be hard to debug as the debugger can change how the job runs under the covers and thus resolve (as in not cause) the issue.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Found the issue by putting a peek stage as output to oracle connector stage and rejecting the records to peek stage.
But I had to change the job and put peek stage. Thought if I put the breakpoint before the oracle connector stage and debug at abort would give me the record which is actually causing the issue.
Had to put a peek stage finally
. It would be great if the debugger would show such records at the breakpoint in case of aborts like this. But this is not the case it seems.
But I had to change the job and put peek stage. Thought if I put the breakpoint before the oracle connector stage and debug at abort would give me the record which is actually causing the issue.
Had to put a peek stage finally
. It would be great if the debugger would show such records at the breakpoint in case of aborts like this. But this is not the case it seems.