Troubleshooting
Problem
Wave in cancelled status but shippers still associated to it SQLCD 1002 Fetch out of sequence by 02010
Symptom
Prior to 6.2 or Oracle Upgrade to 8.1.7.3 or higher, wave release on failure
would remove a shipper from the wave and continue to
PART: Outbound 6.2
SP2 DCS
PRODUCT: <None>
COMPONENT: <None>
OS: <None> -
<None>
DATABASE: Oracle - 8.1.7
WEB SERVER: <None> - <None>
WEB
BROWSER: Internet Explorer - 5.5 sp2
Cause
Resolving The Problem
Oracle Defect.
Based on metalink.oracle.com Doc 202261.1 there that
basically says the following:
Patch Set Addendum - Unexpected ORA-1002 after
ROLLBACK TO SAVEPOINT
This note documents the issue in <Bug:2401670
</metalink/plsql/showdoc?db=Bug&id=2401670>> which may affect customers after
applying one of the Patch Sets listed below.
Versions Affected
This
problem affects Oracle versions:
8.1.7.3 and 8.1.7.4
9.0.1.3
9.2.0.1 (Base Release)
The problem does NOT affect:
Versions
prior to and including 8.1.7.2
9.0.1.0 to 9.0.1.2 inclusive
9.0.1.4
9.2.0.2 onwards (not available at time of writing)
Platforms
Affected
GENERIC , all platforms are affected
Description
Sessions
which perform ROLLBACK TO SAVEPOINT operations may encounter an unexpected
ORA-1002 error for cursors opened before the SAVEPOINT.
Likelihood of
Occurrence
Only specific types of application are affected by this
issue.
You will encounter this problem if a session performs the following
sequence of operations:
opens a cursor (referred to below as C1);
performs a COMMIT;
issues a SAVEPOINT;
performs a ROLLBACK TO
SAVEPOINT;
tries to FETCH from cursor C1.
During the FETCH above an
unexpected ORA-1002 error occurs.
The problem is known to affect some
Oracle Applications products running against the database versions listed
above.
Based on the database activity flow leading to this error which
matches exactly with how wh132 releases a wave we identify this to be the cause
of this problem.
Workaround provided by Oracle -
Applying the
patch is the preferred method of resolution for this issue.
The workaround
is to recode the application to re-open (and reposition) any cursors after a
rollback to savepoint. This is often not practical.
Patches
Patches for
this bug can be found on MetaLink by following these steps:
a. Login to
MetaLink - <http://metalink.oracle.com>
b. Choose Patches from the Menu.
c. Input 2401670 into the Patch Number field.
d. Click the Submit
button.
References
Bug to fix the ORA-1002
<Bug:2401670>
Temporary workaround - For shippers already affected by
this problem you should do the data fix in the pick_ticket table to remove
these shippers from the wave. Contact Yantra Technical Support for the sample
query. To avoid this problem until the upgrade you could set the whse parameter
PCK/RLSCOMMT in 09289 to a large number say 500
Historical Number
PRI49043
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21548943