Cannot Purge WSH_EXCEPTIONS TABLE Due to Too Many Closed Exceptions
(Doc ID 1079743.1)
Last updated on DECEMBER 17, 2018
Applies to:Oracle Shipping Execution - Version 126.96.36.199 and later
Information in this document applies to any platform.
Form:WSHFXCDF.FMB - Define Shipping Exceptions Form
Checked for currency 3-June-2017
You are attempting to purge old and un-wanted shipping exceptions from the WSH_EXCEPTIONS table using the purge tool from within the shipping Exceptions form, but this is taking many hours to complete and/or ends with a 'rollback segment too small' error message. So you then attempted to use the API WSH_EXCEPTIONS_PUB.Exception_Action to purge old shipping exceptions from the WSH_EXCEPTIONS table. However, when you attempt to execute the API, the program runs for a long time, encounters an error, and rolls back all updates.
Expect to be able to purge all un-wanted exceptions from the WSH_EXCEPTIONS table.
The issue can be reproduced at will with the following steps:
1. Create wrapper code which defines input variables, then calls the API WSH_EXCEPTIONS_PUB.Exception_Action.
2. Execute the wrapper code.
3. Wrapper code runs for a very long time.
4. When the program appears to complete, query the WSH_EXCEPTIONS table and see that nothing was purged
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document