Article Content
Article Number | 000037577 |
Applies To | RSA Product Set: Identity Governance & Lifecycle RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1 |
Issue | When testing the Default Provisioning Form for a user (in the RSA Identity Governance & Lifecycle User Interface go to Requests > Configuration > Request Forms tab > Default Provisioning Form > Fields tab > Run Form), the following error occurs: If debug is enabled, the below error is seen in the/home/oracle/wildfly-10.1.0.Final/standalone/log/aveksaServer.log 06/01/2018 10:53:50.158 WARN (default task-45) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 600, SQLState: 60000 06/01/2018 10:53:50.159 ERROR (default task-45) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-00600: internal error code, arguments: [xtyGetBindMD:ctxbposp], [], [], [], [], [], [], [], [], [], [], [] Caused by: java.sql.SQLException: ORA-00600: internal error code, arguments: [xtyGetBindMD:ctxbposp], [], [], [], [], [], [], [], [], [], [], [] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059) 06/01/2018 10:53:50.162 ERROR (default task-45) [com.aveksa.gui.components.table.core.TableModel] Unable to get groups for table ProvisioningSuggestedAccessAllTypesTable java.lang.RuntimeException: com.aveksa.server.db.PersistenceException: com.aveksa.server.db.PersistenceException: Executing JDBC query failed [select * from (SELECT COUNT AS NUM_ROWS, APPLICATION_NAME FROM (select * from (select x.*, suggest.percentage from ( select 'ent' as ENTITLEMENT_TYPE, ent.id as ENTITLEMENT_ID, nvl( ent.ALT_NAME, RESOURCE_NAME || ' : ' || ACTION_NAME) as ENTITLEMENT_NAME, ent.SHORT_DESC as ENTITLEMENT_SHORT_DESC, ent.LONG_DESC as ENTITLEMENT_LONG_DESC, ent.URL_REF as ENTITLEMENT_URL_REF, (RESOURCE_NAME || ' : ' || ACTION_NAME) as ENTITLEMENT_RAW_NAME, With no debug enabled, the /home/oracle/wildfly-10.1.0.Final/standalone/log/aveksaServer.log has the following error:
|
Cause | This is an Oracle bug that gets triggered when the initialization parameter CURSOR_SHARING is set to FORCE. Engineering has raised this to Oracle support. |
Resolution | There is no resolution at this time. |
Workaround | Until a resolution is provided by Oracle, please use the below workaround to fix this issue. Please take a valid database backup before running the workaround.
|
Notes | The purpose of the CURSOR_SHARING=FORCE setting is required for Oracle 12c, it is needed to improve Oracle Optimizer CPU usage for statement parsing. So, setting it to the default EXACT value will affect Oracle performance and might become noticeable under load when CPU resources are depleted. |