DSXchange

Hello,

Server job is aborted with the following error : ReportWIPRMJ1..TRF_ReportWIPRm: ORA-01002: fetch out of sequence

Please suggest.

Thanks in advance.

Suggest you supply more details. There's no way for anyone to know just from mentioning the ORA error. And it's obviously not happening in the transformer, that's just an artifact of Server job error reporting - the Transformer is the active stage in the job. By the way:

ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid.
Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned.
2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error.
3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.

Action:
1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch.
2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE.
3) Reexecute the statement after rebinding, then attempt to fetch again.

Suggest you supply more details. There's no way for anyone to know just from mentioning the ORA error. And it's obviously not happening in the transformer, that's just an artifact of Server job error reporting - the Transformer is the active stage in the job. By the way, not really an error you should be able to cause yourself but without knowing exactly what you are doing there's no way to tell if it is a bug or user caused.

ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid.
Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned.
2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error.
3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.

Action:
1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch.
2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE.
3) Reexecute the statement after rebinding, then attempt to fetch again.