Initialization operations completed with errors after RSA Identity Governance & Lifecycle 7.1P03 upgrade
Originally Published: 2018-12-06
Article Number
Applies To
| RSA Product Set: RSA Identity Governance & Lifecycle 7.1 |
Issue
Initialization Status Initialization operations completed with errors. Please resolve the problem(s) before the application server can accept requests. ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "DATA_50M" ORA-06512: at line 6
Issue is that upgrade SQL script ACM-83939.sql failed to execute with below error log from AveksaServer logs
java.sql.SQLException: ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "DATA_50M" ORA-06512: at line 6
Cause
It is possible that ‘SEGMENT SPACE MANAGEMENT’ is not set to AUTO.
Run below as avuser to verify:
Select * from user_tablespaces;
If ‘SEGMENT SPACE MANAGEMENT’ is set to MANUAL for tablespace DATA_50M, that could be the reason why you noticed the error message and it should be set to AUTO.
Resolution
‘SEGMENT SPACE MANAGEMENT’ needs to be set to AUTO so ASSM is enabled and securefile lob can be set.
Related Articles
Private key decryption error: Unsupported keysize or algorithm 24Number of Views How to configure a global default Circuit Breaker threshold value in RSA Identity Governance & Lifecycle 83Number of Views The impact on RSA Authentication Manager 8.x of vulnerabilities reported in: OpenSSL Security Advisory - Dec 2015 - False … 66Number of Views RSA Identity Governance & Lifecycle - Unable to create change requests when running a form that has more than one Provisio… 61Number of Views Error "Unable to generate TSF URL" on RSA Authentication Manager 8.x 44Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?