Unable to create schema. (class java.sql.SQLSyntaxErrorException: ORA-00959: tablespace 'INDX_256K' does not exist) initialization error for weblogic application server in RSA Identity Governance & Lifecycle
2 years ago
Originally Published: 2018-06-08
Article Number
000041866
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.2, 7.1.0
 
Issue
The following initialization error displays when installing RSA Identity Governance & Lifecycle on a WebLogic application server:
 
Initialization operations completed with errors.  Please restart the application server.
Unable to create schema. (class java.sql.SQLSyntaxErrorException: ORA-00959: tablespace 'INDX_256K' does not exist)
ORA_06512: at line 34
 
User-added image

The following error is seen in the AveksaServer.log 
04/27/2018 14:37:36.313 FATAL ([STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)') [com.aveksa.server.runtime.AveksaSystem] 

****************************************

Initialization has failed!

Unable to create schema. (class java.sql.SQLSyntaxErrorException: ORA-00959: tablespace 'INDX_256K' does not exist
ORA-06512: at line 34)

****************************************

You can see a similar error in the create.log:   
java.sql.SQLSyntaxErrorException: ORA-00959: tablespace 'INDX_256K' does not exist
ORA-06512: at line 34

	at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:494)
	at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:446)
	at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1054)
	at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:623)
	at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
	at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
	at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:213)
	at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:37)
	at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:890)
	at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1119)
	at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1661)
	at oracle.jdbc.driver.OracleStatement.executeLargeUpdate(OracleStatement.java:1626)
	at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1613)
	at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:282)
	at weblogic.jdbc.wrapper.Statement.executeUpdate(Statement.java:523)
Cause
This is due to a defect in the code.
Resolution
Upgrading to V7.0.2 P09 or V7.1.0 P01 or V7.1.1 will fix this issue.
Workaround
Modify the file ACM-75951.sql present in /opt/oracle/domains/SECURITY_ACT_DOMAIN/servers/aveksa-bar/tmp/_WL_user/aveksa/r8uygp/aveksa.war/WEB-INF/database/updates/7.1/ACM-75951.sql, as below.

Replace the following line: 
"--execute immediate 'CREATE INDEX IDX_REVCOMP_CRI_STATUS ON T_AV_REVIEW_COMPONENTS (CR_ITEM_ID, CHANGE_REQUEST_STATUS) tablespace %INDX1_TABLESPACE% COMPUTE STATISTICS';
        execute immediate 'CREATE INDEX IDX_REVCOMP_CRI_STATUS ON T_AV_REVIEW_COMPONENTS (CR_ITEM_ID, CHANGE_REQUEST_STATUS) tablespace INDX_256K COMPUTE STATISTICS';

Use the text below in ACM-75951.sql with the text below:  
"execute immediate 'CREATE INDEX IDX_REVCOMP_CRI_STATUS ON T_AV_REVIEW_COMPONENTS (CR_ITEM_ID, CHANGE_REQUEST_STATUS) tablespace %INDX1_TABLESPACE% COMPUTE STATISTICS';"

The syntax will work on any configuration.

After making the changes above, follow the steps below to resolve the error.
  1. Shutdown the AppServer.
  2. Drop schema AVEKSA_AVUSER from the instance
  3. Start the AppServer and monitor the aveksaServer.log to start installing the schema.

Related Articles

Trending Articles

Don't see what you're looking for?