My Oracle Support Banner

OPSS - WebLogic Startup Fails After OMS Repository Change in EM Environment with Error: java.sql.SQLRecoverableException: ORA-01033 (Doc ID 2144665.1)

Last updated on AUGUST 11, 2021

Applies to:

Oracle Platform Security for Java - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

Unable to start WebLogic Server after changing the OMS repository from primary to standby database
Server startup fails with ORA-01033 error

 

<starting weblogic with Java version:
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
Starting WLS with line:
/<MW_HOME>/oracle_common/jdk/bin/java -server -Xms256M -Xmx1740M -XX:PermSize=128M -XX:MaxPermSize=1024M -XX:CompileThreshold=8000 -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing -XX:ReservedCodeCacheSize=100M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled -Dweblogic.Name=EMGC_ADMINSERVER -

<Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
<Info> <WorkManager> <BEA-002942> <CMM memory level becomes 0. Setting standby thread pool size to 256.>
AM oracle.security.jps.JpsStartup start
INFO: Jps initializing.
org.hibernate.validator.util.Version <clinit>
INFO: Hibernate Validator 12.1.3.0.0
 org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
[EL Severe]: ejb: 2016-05-24 10:32:22.349--ServerSession(907008403)--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

Error Code: 1033
 oracle.security.jps.internal.common.config.AbstractSecurityStore getSecurityStoreVersion
WARNING: Unable to get the Version from Store returning the default
oracle.security.jps.service.policystore.PolicyStoreException: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

Error Code: 1033
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.processJPAException(JpsDBDataManager.java:2180)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.init(JpsDBDataManager.java:1028)
at oracle.security.jps.internal.policystore.rdbms.JpsDBDataManager.jpsObjectBaseQuery(JpsDBDataManager.java:3089)

Error Code: 1033
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:331)
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:326)
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:138)

Caused By: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:391)
at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:503)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:546)
Truncated. see log file for complete stacktrace
>
<Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
 <INFO> <NodeManager> <The server '<SERVER-NAME>' with process id 21664 is no longer alive; waiting for the process to die.>
<FINEST> <NodeManager> <Process died.>
 <INFO> <NodeManager> <Server failed during startup so will not be restarted>


 

 

Changes

The Data Base switch over was done by changing the OMS repository connection string using the following command line

emctl config oms -store_repos_details -repos_user_sysman -repos_conndesc "<db_connect_string>"

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.