java.lang.IllegalStateException: Context pushed was [(pId = 0, pName = DOMAIN, appId = EJB-xxx, appName = EJB-xxx, appVersion = null

We are seeing these errors in our logs and our weblogic server health is going to WARNING state because of this error.

Error –> 

java.lang.IllegalStateException: Context pushed was [(pId = 0, pName = DOMAIN, appId = EJB-xxx, appName = EJB-xxx, appVersion = null, mId = /EJB-xxx-EJB-xxx
o-webapp, compName = /EJB-xxxx-EJB-xxx-webapp)], but context being popped is [(pId = 0, pName = DOMAIN, appId = EJB-xxx, appName = EJB-xxx, appVersion = null
, mId = EAR-xxx-jar, compName = SessionEJB)].
java.lang.IllegalStateException: Context pushed was [(pId = 0, pName = DOMAIN, appId = EJB-xxxx, appName = EJB-anno, appVersion = null, mId = /EJB-xxx-EJB-xxx
-webapp, compName = /EJB-xxx-EJB-Anno-webapp)], but context being popped is [(pId = 0, pName = DOMAIN, appId = EJB-xxx, appName = EJB-xxx, appVersion = null,
mId = EAR-xxx-jar, compName = SessionEJB)]
at weblogic.application.ComponentInvocationContextManagerImpl$4.validate(ComponentInvocationContextManagerImpl.java:256)
at weblogic.application.ComponentInvocationContextManagerImpl$4.close(ComponentInvocationContextManagerImpl.java:231)

Cause –> 

Exception java.lang.IllegalStateException occurs when accessing EJB bean which is exposed as a web service.
This is reported in Bug 22648025 – .ILLEGALSTATEEXCEPTION WHEN INVOKING A WEBSERVICE/EJB IN WLS 12.2.1.

Solution –> 

Please apply Patch 22648025 available on My Oracle Support.

Advertisements

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

I am facing a problem in starting my weblogic server 12.2.1.0.0 ,  It forcefully shuts down every time with below error.

Error –> 

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)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate.java:464)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:637)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:793)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:614)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:98)
… 94 more

Solution –>  Verify that the database is in the OPEN state before starting the WebLogic server.

Enter user-name: connect /as sysdba
Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> shutdown abort;
ORACLE instance shut down..

SQL> startup mount;
ORACLE instance started.

Total System Global Area 313159680 bytes
Fixed Size 2280816 bytes
Variable Size 180355728 bytes
Database Buffers 125829120 bytes
Redo Buffers 4694016 bytes
Database mounted.

SQL> alter database open;

ORA-00600: internal error code, arguments: [kcratr_scan_lastbwr], [], [], [], [], [], [], [], [], [], [], []

We will face this error while starting Database.

SQL> startup
ORACLE instance started.

Total System Global Area 313159680 bytes
Fixed Size 2280816 bytes
Variable Size 180355728 bytes
Database Buffers 125829120 bytes
Redo Buffers 4694016 bytes
Database mounted.
ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1],
[754], [67402], [67403], [], [], [], [], [], [], []

Cause : This is due to server crash or due to hardware or power failure.

Solution: Recover the database with below steps:

 

Shutdown and startup normally

 

SQL> Shutdown abort ;

Take a OS Level backup of the controlfile (This is to ensure we have a backup of current state of controlfile)

SQL> Startup mount ;
SQL> recover database using backup controlfile until cancel ;

Enter location of redo log shown as current in Query 1 when prompted for recovery

Hit Enter

SQL> Alter database open resetlogs ;