Attempting to Cleanup after Abort
Moderators: chulett, rschirm, roy
Attempting to Cleanup after Abort
Hi All,
I did not find proper reason why the job aborts randomly with the error below and also with "Abnormal Termination of stage detected" .
opened ticket with IBM but no definite response ,waiting for them to get back to us.
DataStage Job 348 Phantom 6404
Program "DSP.Close": Line 94, Exception raised in GCI subroutine:
Access violation.
Attempting to Cleanup after ABORT raised in stage HF_DIM_PRODUCT..ora_DIM_PRODUCT
DataStage Phantom Aborting with @ABORT.CODE = 3
No idea why jobs abort randomly with these errors
Any thoughts or suggestions appreciated
Thanks
Paddu
I did not find proper reason why the job aborts randomly with the error below and also with "Abnormal Termination of stage detected" .
opened ticket with IBM but no definite response ,waiting for them to get back to us.
DataStage Job 348 Phantom 6404
Program "DSP.Close": Line 94, Exception raised in GCI subroutine:
Access violation.
Attempting to Cleanup after ABORT raised in stage HF_DIM_PRODUCT..ora_DIM_PRODUCT
DataStage Phantom Aborting with @ABORT.CODE = 3
No idea why jobs abort randomly with these errors
Any thoughts or suggestions appreciated
Thanks
Paddu
My jobs reads data from a flat file and does tranformations using Hash file (lookups) and writes to Oracle .i use sequential file stage , transformer, hash file & Oci stage .
I am just using KeyMgtGetNextValue routine in the transformer .
when i double clicked the "From Previous run", i got this message
From previous run
DataStage Job 482 Phantom 4328
DataStage Phantom Finished.
Unhandled exception raised at address 0x7C82F583 : Access violation
Attempted to read from address 0x00000000
I am just using KeyMgtGetNextValue routine in the transformer .
when i double clicked the "From Previous run", i got this message
From previous run
DataStage Job 482 Phantom 4328
DataStage Phantom Finished.
Unhandled exception raised at address 0x7C82F583 : Access violation
Attempted to read from address 0x00000000
Guys!! i am slso getting same error
ERROR
""Attempting to Cleanup after ABORT raised in stage JOBNAME..AfterJob""
I am using 'four Oracle database stages', 'Change capture', 'one transformer'. I have two Keys, one is NUM, another one is DATE.
My UPDATE coding in Target Oracle DBSTAGE.
UPDATE
#$SCHEMA#.TableName
SET
Field 1= ORCHESTRATE.Field1,Field 2= ORCHESTRATE.Field2,Field 3= ORCHESTRATE.Field3,Field 4= ORCHESTRATE.Field4,Field 5= ORCHESTRATE.Field5
WHERE 1=2
Above code " 1 and 2 are Keys, which are Field1 and Field4"
Option : Upsert Mode = User-defined Update & Insert
Some times after running Script from Unix to run the job, The Error is " Check UPDATE (..) Statement".
Really confusing............. Please advice me this.....Thanks
""Attempting to Cleanup after ABORT raised in stage JOBNAME..AfterJob""
I am using 'four Oracle database stages', 'Change capture', 'one transformer'. I have two Keys, one is NUM, another one is DATE.
My UPDATE coding in Target Oracle DBSTAGE.
UPDATE
#$SCHEMA#.TableName
SET
Field 1= ORCHESTRATE.Field1,Field 2= ORCHESTRATE.Field2,Field 3= ORCHESTRATE.Field3,Field 4= ORCHESTRATE.Field4,Field 5= ORCHESTRATE.Field5
WHERE 1=2
Above code " 1 and 2 are Keys, which are Field1 and Field4"
Option : Upsert Mode = User-defined Update & Insert
Some times after running Script from Unix to run the job, The Error is " Check UPDATE (..) Statement".
Really confusing............. Please advice me this.....Thanks
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Your Search for "access violation" would have revealed a number of possible characteristics of your data or design that might result in such a signal being raised. These include inappropriate handling of null values and oversized string data.
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.
just an update .
Looks like version 7.5.2 has fixed abnormal termination problem .
In our project we did not see this problem after switching from datastage 7.5x2 to 7.5.2 march 2006 release. IBM told us they had a patch for this problem and fixed in 7.5.2.
I wish they come up with a patch for abnormal termination in 7.5.x2 also
Thanks
paddu
Looks like version 7.5.2 has fixed abnormal termination problem .
In our project we did not see this problem after switching from datastage 7.5x2 to 7.5.2 march 2006 release. IBM told us they had a patch for this problem and fixed in 7.5.2.
I wish they come up with a patch for abnormal termination in 7.5.x2 also
Thanks
paddu