My Oracle Support Banner

After applying jan 2019 bundle patch database instance crashing with ORA-27550: Target ID protocol check failed (Doc ID 2535576.1)

Last updated on JANUARY 30, 2020

Applies to:

Oracle Exadata Storage Server Software - Version 12.2.1.1.1 to 18.1.9.0.0 [Release 12.2]
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Linux x86-64

Symptoms

After applying 12.1.0.2 Jan 2019 bundle patch then database getting crashed with the below error

starting up 1 shared server(s) ...
Wed Apr 24 04:52:50 2019
NOTE: ASMB connected to ASM instance +ASM1 osid: 229304 (Flex mode; client id 0xffffffffffffffff)
NOTE: initiating MARK startup
Starting background process MARK
Wed Apr 24 04:52:50 2019
MARK started with pid=47, OS id=229325
Wed Apr 24 04:52:50 2019
Errors in file /u01/app/oracle/diag/rdbms/DBTest/DBTest1/trace/DBTest1_lmon_229084.trc:
ORA-27550: Target ID protocol check failed. tid vers=1, type=4, remote instance number=2, local instance number=1
Wed Apr 24 04:52:51 2019
LCK1 (ospid: 229164): terminating the instance due to error 27550
Wed Apr 24 04:52:51 2019
System state dump requested by (instance=1, osid=229164 (LCK1)), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/DBTest/DBTest1/trace/DBTest1_diag_229044_20190424045251.trc
Wed Apr 24 04:52:51 2019
Dumping diagnostic data in directory=[cdmp_20190424045251], requested by (instance=1, osid=229164 (LCK1)), summary=[abnormal instance termination]

Changes

 12.1.0.2 Database home patched with Jan 2019 Exadata bundle patch

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!


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