Attempting to Cleanup after Abort

[paddu]

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

[DSguru2B]

Try searching for the key words "Exception raised in GCI subroutine". You will be amazed as to how many people ran into this error. Do an exact search.

[chulett]

Also suggest you Reset the job and see if a 'From previous run...' entry shows up in the log.

[paddu]

yes .
There is "from previuos run" entry in the log.

can you tell me how this helps to analyze?

Thanks
Paddu

[thumsup9]

What does log say when you reset the job and look for the log from previous run ?

[chulett]

You double-click on it and it should tell you why it aborted.

[kris18]

can you tell us what stages you are using in ur job? and are you calling any routines in the transformer?

kris

[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

[tobefrank]

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

[ray.wurlod]

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.

[paddu]

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