This content has been marked as final. Show 4 replies
Was the AW created in 126.96.36.199 or was it created in an earlier release (e.g. 188.8.131.52) before you upgraded the database version? This kind of error used to happen in 184.108.40.206 and before, and the problem can linger in AWs created in the older release.
My best advice is to open a service request on this. You can mention my name in the SR if you like and it should get forwarded to me.
Thanks - SR logged by one of my colleagues.
All AWs were created via DBMS_AW.EXECUTE('aw create aw_name') on 220.127.116.11 although data has been imported into those via eif from oes.
Thanks for the SR and the information it contains. I have written directly to the contact information given in the SR asking for more details.
Sorry, but any chance you could forward your questions to the alt-contact on the SR, I'll pick them up tonight if I can.