topic Oracle error ORA-12801 ? in Data Management Questions

Oracle error ORA-12801 ?

ChrisJacob — Thu, 13 May 2010 12:52:30 GMT

Hi all.

[ArcSDE 9.3.1 on Oracle 10.2.0.3 on AIX 5.3]

Yesterday we started encountering an unusual Oracle error when trying to reconcile a version in SDE.

"The version could not be reconciled.
Underlying DBMS error[ORA-12801: error signalled in parallel query server P007
ORA-00600: internal error code, arguments: [kxspoac : EXL 1], [23], [23], [], [], [], [], []
]"

We discovered that we got a very similar error when previewing some datasets in ArcCatalog. The errors came from four annotation featureclasses. There were many anno FCs that weren't a problem, and a couple of hundred or so other FCs that were fine too.

We've since restarted SDE and Oracle, and everything appears to be running normally. The data that had been a problem is now queryable with no apparent issues.

The question is... what might have caused the error, and is it something that we can avoid in future? Any thoughts?

Thanks!

Chris J.

Chris Jacob
City of Waterloo
Waterloo, ON, Canada
e: Chris.Jacob @ waterloo.ca

Re: Oracle error ORA-12801 ?

VinceAngelo — Thu, 13 May 2010 13:26:19 GMT

That might be a memory leak in the database server. Are you up-to-date with your
Oracle Critical Patch Update (CPU) release?

- V

Re: Oracle error ORA-12801 ?

ChrisJacob — Fri, 14 May 2010 15:12:11 GMT

Hi there.

Thanks for the quick reply!

I believe that we're up-to-date with Oracle critical patch updates. Our DBA hasn't let me know otherwise yet at least! 🙂

A parallel enquiry with tech support resulted in a reference to the following article:
http://resources.arcgis.com/content/kbase?fa=articleShow&d=35418

We've applied the suggested fix there for now (altering tables and indices so that their degree of parallelism is 1), and everything appears to be back to working normally.

Within a short time frame, we're also looking to migrate from our existing Oracle DB machine at 10.2.0.3 to a new machine with 10.2.0.4, at which release the underlying Oracle bug is apparently fixed (according to their metalink article).

Thanks!

Chris Jacob