This content has been marked as final. Show 2 replies
It seems the RCA has been found.
We have a trigger in one of the OWM tables, which has invoked a package who has a global collection not initialized. Having that piece of code fixed, this exception is not happening any more.
When debugging the code, I traced to the exception in WMSYS codes that invoked this trigger.
As to why sometimes it happens and the other time does not, that's because in that package containing the global collection, one of its procedure initialized this collection. Therefore, we may happened to invoked that API and got collection initialized. This is totally a code issue in our side.
Edited by: user5736610 on 2011-4-14 下午7:03