Oracle Database Immediate Kill Session error Solution

1. error message

Immediate Kill Session #: 1024, Serial #: 9855

Immediate Kill Session: sess: 7000001cc9bb9e8 OS pid: 799228

2. cause:

This is caused by unpublished Bug 6955040 all the sessions lost connection after killing crsd. BIN.

The problem is when CRSD is killed or crashed and restarted,

CRSD will run resource check action but CRS resource status will not be available at that time.

Then in instance check action,

It fails to get the preferred node VIP resource status and considered the preferred

Node VIP resource is not running.

Therefore, instance check action will remove the default database service name

And disconnect sessions connected using default database service name.

Simply put, the session is lost. Resource status information is not available for resource confirmation.

Therefore, the resource is not running.

Then, the session with the default database service name is disconnected.

Then there will be no more...

3. Solution

Solution 1: Upgrade the database to version 10.2.0.5 or later.

The fix is already ded in 10.2.0.5 patchset and 11.1.0.7 patchset.

Apply the patchset once they are available.

Solution 2: Change the service name, which is not consistent with db_name.

Configure a service name other than the default one (same as db_name ),

And get user to use the non-default service name for connection.

The procedure is as follows:

1. Obtain the Instance name:

Select instance_name from v $ instance;

 

2. Obtain the current service_names:

SQL> show parameter name

 

NAME TYPE VALUE

------------------------------------------------------------

Db_file_name_convert string

Db_name string orcl

Db_unique_name string orcl

Global_names boolean FALSE

Instance_name string orcl

Lock_name_space string

Log_file_name_convert string

Service_names string orcl

3. Change service_names:

Alter system set service_names = 'orcl1' scope = MEMORY sid = 'orcl ';