Not able to update OAM policies when CPU count on the database changed
Last updated on JUNE 08, 2015
Applies to:Oracle Access Manager - Version 188.8.131.52.1 and later
Information in this document applies to any platform.
We had OAM 11gR2PS1 (184.108.40.206.0) and then upgraded to OAM11gR2PS2 BP01 (220.127.116.11.1). While performing the PS2 schema upgrade, we experienced the below error and we had resolved it by reducing the CPU count on the database from 80 to 2. After completing the PS2 upgrade, we reverted the CPU count back to 80.
Now, while creating Application Domains on oamconsole, we are experiencing the following error - ' The policy store is not available; please see the log file for more details.' As per this, we checked the logs and found the same error (mentioned below) that we observed while performing the PS2 schema upgrade. After changing the CPU count value on the database from 80 to 2, we could successfully create application domains without seeing this error. Anyhow, CUstomer need to keep CPU count to 80.
Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-12801: error signaled in parallel query server P319, instance phcgqz62.safeway.com:iaimq2 (2)
ORA-12853: insufficient memory for PX buffers: current 425056K, max needed 123033600K
ORA-04031: unable to allocate 65560 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms