又一例ORA-600 kcbzpbuf_1恢复

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：又一例ORA-600 kcbzpbuf_1恢复

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

数据库突然报ORA-600 kdddgb1和ORA-600 kcl_snd_cur_2错误,并且导致实例crash

Tue May 09 22:29:40 2023
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_338012.trc  (incident=962050):
ORA-00600: internal error code, arguments: [kdddgb1], [0], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_962050/orcl1_ora_338012_i962050.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue May 09 22:29:43 2023
Hex dump of (file 75, block 1154926) in trace file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms3_217928.trc
Corrupt block relative dba: 0x12d19f6e (file 75, block 1154926)
Bad header found during preparing block for transfer
Data in bad block:
 type: 0 format: 2 rdba: 0x1affe051
 last change scn: 0x0009.a2266e65 seq: 0x2 flg: 0x10
 spare1: 0x83 spare2: 0x36 spare3: 0x3700
 consistency value in tail: 0x6e650002
 check value in block header: 0x0
 block checksum disabled
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms3_217928.trc  (incident=960186):
ORA-00600: internal error code, arguments: [kcl_snd_cur_2], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_960186/orcl1_lms3_217928_i960186.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue May 09 22:29:43 2023
Sweep [inc][962050]: completed
Sweep [inc][960186]: completed
Sweep [inc2][962050]: completed
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lms3_217928.trc:
ORA-00600: internal error code, arguments: [kcl_snd_cur_2], [], [], [], [], [], [], [], [], [], [], []
LMS3 (ospid: 217928): terminating the instance due to error 484
System state dump requested by (instance=1, osid=217928 (LMS3)), summary=[abnormal instance termination].
System State dumped to trace file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_diag_217897_20230509222949.trc
Tue May 09 22:29:52 2023
ORA-1092 : opitsk aborting process
Tue May 09 22:29:53 2023
ORA-1092 : opitsk aborting process
Tue May 09 22:29:54 2023
Instance terminated by LMS3, pid = 217928

另外一个正在运行的实例做instance recovery,然后节点报ORA-600 kcbzpbuf_1,节点也crash,再次启动一直该错误无法正常启动.

Wed May 10 08:17:07 2023
Hex dump of (file 75, block 1154926) in trace file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dbw9_134621.trc
Corrupt block relative dba: 0x12d19f6e (file 75, block 1154926)
Bad header found during preparing block for write
Data in bad block:
 type: 0 format: 2 rdba: 0x1affe051
 last change scn: 0x0009.a2266e65 seq: 0x2 flg: 0x34
 spare1: 0x83 spare2: 0x36 spare3: 0x3700
 consistency value in tail: 0x6e650002
 check value in block header: 0xf894
 computed block checksum: 0x0
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dbw9_134621.trc  (incident=2240402):
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_2240402/orcl1_dbw9_134621_i2240402.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_dbw9_134621.trc:
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
DBW9 (ospid: 134621): terminating the instance due to error 471
Wed May 10 08:17:08 2023
System state dump requested by (instance=1, osid=134621 (DBW9)), summary=[abnormal instance termination].
System State dumped to trace file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_diag_134555_20230510081708.trc
Instance terminated by DBW9, pid = 134621

尝试直接recover datafile 75失败,报ORA-03113

SQL> recover datafile 75;
ORA-03113: end-of-file on communication channel
Process ID: 281304
Session ID: 14161 Serial number: 1503

dbv检查file 75,发现15个block逻辑坏块

[oracle@oradb21 ~]$ dbv userid=xxx/xxx file=+datadg/orcl/datafile/xifenfei01.377.1130539753

DBVERIFY: Release 11.2.0.4.0 - Production on Wed May 10 08:29:44 2023

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

DBVERIFY - Verification starting : FILE = +datadg/orcl/datafile/xifenfei01.377.1130539753
Block Checking: DBA = 314866909, Block Type = KTB-managed data block
data header at 0x7f852b573064
kdbchk: row locked by non-existent transaction
        table=0   slot=13
        lockid=101   ktbbhitc=2
Page 294109 failed with check code 6101
Block Checking: DBA = 314866928, Block Type = KTB-managed data block
data header at 0x7f852b599064
kdbchk: row locked by non-existent transaction
        table=0   slot=18
        lockid=101   ktbbhitc=2
Page 294128 failed with check code 6101
Block Checking: DBA = 315415269, Block Type = KTB-managed data block
data header at 0x7f852b583064
kdbchk: the amount of space used is not equal to block size
        used=7470 fsc=0 avsp=625 dtl=8088
Page 842469 failed with check code 6110
Block Checking: DBA = 315415302, Block Type = KTB-managed data block
data header at 0x7f852b3c3064
kdbchk: row locked by non-existent transaction
        table=0   slot=13
        lockid=101   ktbbhitc=2
Page 842502 failed with check code 6101
Block Checking: DBA = 315415350, Block Type = KTB-managed data block
data header at 0x7f852b423064
kdbchk: row locked by non-existent transaction
        table=0   slot=14
        lockid=101   ktbbhitc=2
Page 842550 failed with check code 6101
Block Checking: DBA = 315415351, Block Type = KTB-managed data block
data header at 0x7f852b425064
kdbchk: row locked by non-existent transaction
        table=0   slot=10
        lockid=101   ktbbhitc=2
Page 842551 failed with check code 6101
Block Checking: DBA = 315415397, Block Type = KTB-managed data block
data header at 0x7f852b481064
kdbchk: row locked by non-existent transaction
        table=0   slot=14
        lockid=101   ktbbhitc=2
Page 842597 failed with check code 6101
Block Checking: DBA = 315415414, Block Type = KTB-managed data block
data header at 0x7f852b4a3064
kdbchk: row locked by non-existent transaction
        table=0   slot=14
        lockid=101   ktbbhitc=2
Page 842614 failed with check code 6101
Block Checking: DBA = 315665300, Block Type = KTB-managed data block
data header at 0x7f852b2dd0ac
kdbchk: the amount of space used is not equal to block size
        used=7191 fsc=0 avsp=832 dtl=8016
Page 1092500 failed with check code 6110
Block Checking: DBA = 315665302, Block Type = KTB-managed data block
data header at 0x7f852b2e10ac
kdbchk: row locked by non-existent transaction
        table=0   slot=14
        lockid=101   ktbbhitc=5
Page 1092502 failed with check code 6101
Block Checking: DBA = 315665316, Block Type = KTB-managed data block
data header at 0x7f852b2fd0ac
kdbchk: the amount of space used is not equal to block size
        used=7140 fsc=0 avsp=883 dtl=8016
Page 1092516 failed with check code 6110
Block Checking: DBA = 315665491, Block Type = KTB-managed data block
data header at 0x7f852f4170c4
kdbchk: row locked by non-existent transaction
        table=0   slot=3
        lockid=101   ktbbhitc=6
Page 1092691 failed with check code 6101
Block Checking: DBA = 315727518, Block Type = KTB-managed data block
data header at 0x7f852b4f50c4
kdbchk: row locked by non-existent transaction
        table=0   slot=8
        lockid=101   ktbbhitc=6
Page 1154718 failed with check code 6101
Block Checking: DBA = 315727614, Block Type = KTB-managed data block
data header at 0x7f852b5b50ac
kdbchk: row locked by non-existent transaction
        table=0   slot=15
        lockid=101   ktbbhitc=5
Page 1154814 failed with check code 6101
Block Checking: DBA = 315727646, Block Type = KTB-managed data block
data header at 0x7f852b3f30ac
kdbchk: row locked by non-existent transaction
        table=0   slot=3
        lockid=101   ktbbhitc=5
Page 1154846 failed with check code 6101


DBVERIFY - Verification complete

Total Pages Examined         : 1835008
Total Pages Processed (Data) : 250749
Total Pages Failing   (Data) : 15
Total Pages Processed (Index): 74532
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 1244181
Total Pages Processed (Seg)  : 0
Total Pages Failing   (Seg)  : 0
Total Pages Empty            : 265546
Total Pages Marked Corrupt   : 0
Total Pages Influx           : 0
Total Pages Encrypted        : 0
Highest block SCN            : 2720428335 (9.2720428335)

通过对坏块一些处理,数据库open成功,以前有过类似恢复ORA-600 kcbzpbuf_1故障恢复

SQL> alter database open;

Database altered.

alert日志报事务异常

ORACLE Instance orcl1 (pid = 34) - Error 1578 encountered while recovering transaction (697, 6) on object 170692.
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_smon_301450.trc:
ORA-01578: ORACLE data block corrupted (file # 75, block # 1154926)
ORA-01110: data file 75: '+DATADG/orcl/datafile/xifenfei01.377.1130539753'
Archived Log entry 9299 added for thread 1 sequence 4781 ID 0x5f4a1865 dest 1:
Wed May 10 08:24:03 2023
NOTE: dependency between database orcl and diskgroup resource ora.ARCHDG.dg is established
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Wed May 10 08:24:04 2023
Starting background process EMNC
Wed May 10 08:24:04 2023
EMNC started with pid=49, OS id=305303 
Archived Log entry 9300 added for thread 2 sequence 4530 ID 0x5f4a1865 dest 1:
ARC2: Archiving disabled thread 2 sequence 4531
Archived Log entry 9301 added for thread 2 sequence 4531 ID 0x5f4a1865 dest 1:
Wed May 10 08:24:13 2023
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_p000_305307.trc  (incident=2560578):
ORA-01578: ORACLE data block corrupted (file # 75, block # 1154926)
ORA-01110: data file 75: '+DATADG/orcl/datafile/xifenfei01.377.1130539753'
Incident details in: /oracle/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_2560578/orcl1_p000_305307_i2560578.trc
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_p000_305307.trc  (incident=2560579):
ORA-01578: ORACLE data block corrupted (file # , block # )
Incident details in: /oracle/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_2560579/orcl1_p000_305307_i2560579.trc
Wed May 10 08:24:15 2023
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_smon_301450.trc  (incident=2560427):
ORA-01578: ORACLE data block corrupted (file # 75, block # 1154926)
ORA-01110: data file 75: '+DATADG/orcl/datafile/xifenfei01.377.1130539753'
Incident details in: /oracle/app/oracle/diag/rdbms/orcl/orcl1/incident/incdir_2560427/orcl1_smon_301450_i2560427.trc
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_smon_301450.trc  (incident=2560432):
ORA-01578: ORACLE data block corrupted (file # 75, block # 1154926)
ORA-01110: data file 75: '+DATADG/orcl/datafile/xifenfei01.377.1130539753'
ORACLE Instance orcl1 (pid = 34) - Error 1578 encountered while recovering transaction (717, 20) on object 170692.
Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_smon_301450.trc:
ORA-01578: ORACLE data block corrupted (file # 75, block # 1154926)
ORA-01110: data file 75: '+DATADG/orcl/datafile/xifenfei01.377.1130539753'

处理异常事务,并且定位异常对象表

SQL> select owner,object_name,object_type from dba_objects where object_id=170692;

OWNER
--------------------------------------------------------------------------------
OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE
---------------------------------------------------------
XFF
T_XIFENFEI
TABLE

rman检测逻辑坏块所属对象也是这个表（15个坏块均为该表）,对该表数据进行重建抛弃损坏数据,完成本次恢复

ORA-01172 ORA-01151 故障恢复

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：ORA-01172 ORA-01151 故障恢复

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

节点2报Error: Controlfile sequence number in file header is different from the one in memory,导致实例异常

Tue May 09 23:03:24 2023
Thread 2 cannot allocate new log, sequence 16728
Checkpoint not complete
  Current log# 3 seq# 16727 mem# 0: +DATA/xff/onlinelog/group_3.265.941900045
  Current log# 3 seq# 16727 mem# 1: +FRA/xff/onlinelog/group_3.259.941900045
Thread 2 advanced to log sequence 16728 (LGWR switch)
  Current log# 4 seq# 16728 mem# 0: +DATA/xff/onlinelog/group_4.266.941900045
  Current log# 4 seq# 16728 mem# 1: +FRA/xff/onlinelog/group_4.260.941900045
Tue May 09 23:03:31 2023
LNS: Standby redo logfile selected for thread 2 sequence 16728 for destination LOG_ARCHIVE_DEST_2
Tue May 09 23:03:32 2023
Archived Log entry 431615 added for thread 2 sequence 16727 ID 0x5ffc99b5 dest 1:
Tue May 09 23:05:30 2023
Error: Controlfile sequence number in file header is different from the one in memory
       Please check that the correct mount options are used if controlfile is located on NFS
USER (ospid: 30162): terminating the instance
Tue May 09 23:05:30 2023
System state dump requested by (instance=2, osid=30162), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/xff/xff2/trace/xff2_diag_6650.trc
Instance terminated by USER, pid = 30162

在节点1 进行实例重组之后,节点1 实例异常

Tue May 09 23:04:54 2023
Thread 1 cannot allocate new log, sequence 2060
Checkpoint not complete
  Current log# 1 seq# 2059 mem# 0: +DATA/xff/onlinelog/group_1.261.941899887
  Current log# 1 seq# 2059 mem# 1: +FRA/xff/onlinelog/group_1.257.941899887
Thread 1 advanced to log sequence 2060 (LGWR switch)
  Current log# 2 seq# 2060 mem# 0: +DATA/xff/onlinelog/group_2.262.941899889
  Current log# 2 seq# 2060 mem# 1: +FRA/xff/onlinelog/group_2.258.941899889
Tue May 09 23:04:58 2023
********************* ATTENTION: ******************** 
 The controlfile header block returned by the OS
 has a sequence number that is too old. 
 The controlfile might be corrupted.
 PLEASE DO NOT ATTEMPT TO START UP THE INSTANCE 
 without following the steps below.
 RE-STARTING THE INSTANCE CAN CAUSE SERIOUS DAMAGE 
 TO THE DATABASE, if the controlfile is truly corrupted.
 In order to re-start the instance safely, 
 please do the following:
 (1) Save all copies of the controlfile for later 
     analysis and contact your OS vendor and Oracle support.
 (2) Mount the instance and issue: 
     ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
 (3) Unmount the instance. 
 (4) Use the script in the trace file to
     RE-CREATE THE CONTROLFILE and open the database. 
*****************************************************
Tue May 09 23:05:31 2023
Reconfiguration started (old inc 20, new inc 22)
List of instances:
 1 (myinst: 1) 
 Global Resource Directory frozen
 * dead instance detected - domain 0 invalid = TRUE 
 Communication channels reestablished
 Master broadcasted resource hash value bitmaps
 Non-local Process blocks cleaned out
Tue May 09 23:05:31 2023
 LMS 1: 0 GCS shadows cancelled, 0 closed, 0 Xw survived
Tue May 09 23:05:31 2023
 LMS 0: 3 GCS shadows cancelled, 0 closed, 0 Xw survived
 Set master node info 
 Submitted all remote-enqueue requests
 Dwn-cvts replayed, VALBLKs dubious
 All grantable enqueues granted
 Post SMON to start 1st pass IR
Tue May 09 23:05:32 2023
Instance recovery: looking for dead threads
 Submitted all GCS remote-cache requests
 Post SMON to start 1st pass IR
 Fix write in gcs resources
Reconfiguration complete
Tue May 09 23:06:00 2023
ARC1 (ospid: 26512): terminating the instance
Tue May 09 23:06:00 2023
System state dump requested by (instance=1, osid=26512 (ARC1)), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/xff/xff1/trace/xff1_diag_26311.trc
Tue May 09 23:06:01 2023
ORA-1092 : opitsk aborting process
Instance terminated by ARC1, pid = 26512

实例重启报错

Recovery of Online Redo Log: Thread 1 Group 1 Seq 2059 Reading mem 0
  Mem# 0: +DATA/dbm/onlinelog/group_1.261.941899887
  Mem# 1: +FRA/dbm/onlinelog/group_1.257.941899887
Recovery of Online Redo Log: Thread 2 Group 3 Seq 16727 Reading mem 0
  Mem# 0: +DATA/dbm/onlinelog/group_3.265.941900045
  Mem# 1: +FRA/dbm/onlinelog/group_3.259.941900045
Recovery of Online Redo Log: Thread 2 Group 4 Seq 16728 Reading mem 0
  Mem# 0: +DATA/dbm/onlinelog/group_4.266.941900045
  Mem# 1: +FRA/dbm/onlinelog/group_4.260.941900045
Hex dump of (file 1, block 102777) in trace file /u01/app/oracle/diag/rdbms/dbm/dbm2/trace/dbm2_ora_30749.trc
Reading datafile '+DATA/dbm/datafile/system.256.941899799' for corruption at rdba: 0x00419179 (file 1, block 102777)
Reread (file 1, block 102777) found different corrupt data (logically corrupt)
Hex dump of (file 1, block 102777) in trace file /u01/app/oracle/diag/rdbms/dbm/dbm2/trace/dbm2_ora_30749.trc
RECOVERY OF THREAD 2 STUCK AT BLOCK 102777 OF FILE 1
Abort recovery for domain 0
Aborting crash recovery due to error 1172
Errors in file /u01/app/oracle/diag/rdbms/dbm/dbm2/trace/dbm2_ora_30749.trc:
ORA-01172: recovery of thread 2 stuck at block 102777 of file 1
ORA-01151: use media recovery to recover block, restore backup if needed
Abort recovery for domain 0
Errors in file /u01/app/oracle/diag/rdbms/dbm/dbm2/trace/dbm2_ora_30749.trc:
ORA-01172: recovery of thread 2 stuck at block 102777 of file 1
ORA-01151: use media recovery to recover block, restore backup if needed
ORA-1172 signalled during: ALTER DATABASE OPEN /* db agent *//* {0:890:17} */...

人工recover操作失败报ORA-600 3020错误

SQL> recover datafile 1;
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [1], [102777], [4297081],[], []
ORA-10567: Redo is inconsistent with data block (file# 1, block# 102777, file
offset is 841949184 bytes)
ORA-10564: tablespace SYSTEM
ORA-01110: data file 1: '+DATA/dbm/datafile/system.256.941899799'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 469884

---alert日志
Tue May 09 23:28:44 2023
ALTER DATABASE RECOVER  datafile 1  
Media Recovery Start
Serial Media Recovery started
Recovery of Online Redo Log: Thread 2 Group 3 Seq 16727 Reading mem 0
  Mem# 0: +DATA/xff/onlinelog/group_3.265.941900045
  Mem# 1: +FRA/xff/onlinelog/group_3.259.941900045
ORA-279 signalled during: ALTER DATABASE RECOVER  datafile 1  ...
ALTER DATABASE RECOVER    CONTINUE DEFAULT  
Media Recovery Log +FRA/xff/archivelog/2023_05_09/thread_1_seq_2055.20899.1136415701
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
ALTER DATABASE RECOVER    CONTINUE DEFAULT  
Media Recovery Log +FRA/xff/archivelog/2023_05_09/thread_1_seq_2056.20837.1136415753
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
ALTER DATABASE RECOVER    CONTINUE DEFAULT  
Media Recovery Log +FRA/xff/archivelog/2023_05_09/thread_1_seq_2057.20911.1136415803
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
ALTER DATABASE RECOVER    CONTINUE DEFAULT  
Media Recovery Log +FRA/xff/archivelog/2023_05_09/thread_1_seq_2058.21898.1136415853
Recovery of Online Redo Log: Thread 2 Group 4 Seq 16728 Reading mem 0
  Mem# 0: +DATA/xff/onlinelog/group_4.266.941900045
  Mem# 1: +FRA/xff/onlinelog/group_4.260.941900045
Recovery of Online Redo Log: Thread 1 Group 1 Seq 2059 Reading mem 0
  Mem# 0: +DATA/xff/onlinelog/group_1.261.941899887
  Mem# 1: +FRA/xff/onlinelog/group_1.257.941899887
Hex dump of (file 1, block 102777) in trace file /u01/app/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_16246.trc
Reading datafile '+DATA/xff/datafile/system.256.941899799' for corruption at rdba: 0x00419179 (file 1, block 102777)
Reread (file 1, block 102777) found different corrupt data (logically corrupt)
Hex dump of (file 1, block 102777) in trace file /u01/app/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_16246.trc
Tue May 09 23:28:59 2023
Errors in file /u01/app/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_16246.trc  (incident=6868615):
ORA-00600: internal error code, arguments: [3020], [1], [102777], [4297081], [], [], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 1, block# 102777, file offset is 841949184 bytes)
ORA-10564: tablespace SYSTEM
ORA-01110: data file 1: '+DATA/xff/datafile/system.256.941899799'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 469884
Incident details in: /u01/app/oracle/diag/rdbms/xff/xff1/incident/incdir_6868615/xff1_ora_16246_i6868615.trc
Tue May 09 23:29:00 2023
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Media Recovery failed with error 600
ORA-283 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
ALTER DATABASE RECOVER CANCEL 
ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...

根据上述报错信息可以确认报错的是一个index,而且非系统核心对象,可以通过allow 1 corruption方式进行恢复,并且open库成功

SQL> recover  datafile 1 allow 1 corruption;
Media recovery complete.
SQL> alter database open;

Database altered.

SQL> select owner,object_name,object_type from dba_objects where object_id=469884;

OWNER
--------------------------------------------------------------------------------
OBJECT_NAME
--------------------------------------------------------------------------------
OBJECT_TYPE
---------------------------------------------------------
SYSTEM
PK_XFF_SERVERS
INDEX

SQL> alter index system.PK_XFF_SERVERS rebuild online;

Index altered.

数据库完美恢复,数据0丢失,业务可以直接正常使用

存储双活同步导致数据库异常恢复

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：存储双活同步导致数据库异常恢复

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

客户双活存储异常之后,单个存储运行,故障存储修复之后,双活同步,出现多套系统异常,上一篇:Control file mount id mismatch!故障处理,这套是win的rac无法正常启动,ocr磁盘组异常(报ORA-600 kfrValAcd30无法正常mount)

C:\Users\Administrator>crsctl start cluster -all
CRS-2672: 尝试启动 'ora.crf' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.asm' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.crf' (在 'xff1' 上)
CRS-2672: 尝试启动 'ora.asm' (在 'xff1' 上)
CRS-2676: 成功启动 'ora.crf' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.crf' (在 'xff1' 上)
CRS-5017: 资源操作 "ora.asm start" 遇到以下错误:
ORA-00600: internal error code, arguments: [kfrValAcd30], [OCR_VOTE], [1], [14], [7556], [15], [7584], [], [], [], [], []
。有关详细信息, 请参阅 "(:CLSN00107:)" (位于 "F:\app\grid\Administrator\diag\crs\xff2\crs\trace\ohasd_oraagent_system.trc" 中)。
CRS-2674: 未能启动 'ora.asm' (在 'xff2' 上)
CRS-2679: 尝试清除 'ora.asm' (在 'xff2' 上)
CRS-5017: 资源操作 "ora.asm start" 遇到以下错误:
ORA-00600: internal error code, arguments: [kfrValAcd30], [OCR_VOTE], [1], [14], [7556], [15], [7584], [], [], [], [], []
。有关详细信息, 请参阅 "(:CLSN00107:)" (位于 "F:\app\grid\Administrator\diag\crs\xff1\crs\trace\ohasd_oraagent_system.trc" 中)。
CRS-2674: 未能启动 'ora.asm' (在 'xff1' 上)
CRS-2679: 尝试清除 'ora.asm' (在 'xff1' 上)
CRS-2681: 成功清除 'ora.asm' (在 'xff2' 上)
CRS-2673: 尝试停止 'ora.crf' (在 'xff2' 上)
CRS-2677: 成功停止 'ora.crf' (在 'xff2' 上)
CRS-2681: 成功清除 'ora.asm' (在 'xff1' 上)
CRS-2673: 尝试停止 'ora.crf' (在 'xff1' 上)
CRS-2677: 成功停止 'ora.crf' (在 'xff1' 上)
CRS-4705: 无法在节点 xff1 上启动集群件。
CRS-4705: 无法在节点 xff2 上启动集群件。
CRS-4000: 命令 Start 失败, 或已完成但出现错误。

因为是ocr磁盘组操作比较简单,直接重建该磁盘组，还原ocr等即可

C:\Users\Administrator>asmtool -list
NTFS                             \Device\Harddisk0\Partition1              300M
NTFS                             \Device\Harddisk0\Partition4           599472M
NTFS                             \Device\Harddisk0\Partition5          1000000M
ORCLDISKDATA0                    \Device\Harddisk1\Partition1          1048587M
ORCLDISKDATA1                    \Device\Harddisk2\Partition1          1048587M
ORCLDISKDATA2                    \Device\Harddisk3\Partition1          1048587M
ORCLDISKDATA3                    \Device\Harddisk4\Partition1          1048587M
ORCLDISKDATA4                    \Device\Harddisk6\Partition1           460797M

C:\Users\Administrator>crsctl start crs -excl -nocrs
CRS-4123: Oracle 高可用性服务已启动。
CRS-2672: 尝试启动 'ora.evmd' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.mdnsd' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.mdnsd' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.evmd' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.gpnpd' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.gpnpd' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.cssdmonitor' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.gipcd' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.cssdmonitor' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.gipcd' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.cssd' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.cssd' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.ctssd' (在 'xff2' 上)
CRS-2676: 成功启动 'ora.ctssd' (在 'xff2' 上)
CRS-2672: 尝试启动 'ora.asm' (在 'xff2' 上)
CRS-5017: 资源操作 "ora.asm start" 遇到以下错误:
ORA-00600: internal error code, arguments: [kfrValAcd30], [OCR_VOTE], [1], [14], [7556], [15], [7584], [], [], [], [], []
。有关详细信息, 请参阅 "(:CLSN00107:)" (位于 "F:\app\grid\Administrator\diag\crs\xff2\crs\trace\ohasd_oraagent_system.trc" 中)。
CRS-2674: 未能启动 'ora.asm' (在 'xff2' 上)
CRS-2679: 尝试清除 'ora.asm' (在 'xff2' 上)
CRS-2681: 成功清除 'ora.asm' (在 'xff2' 上)
CRS-2673: 尝试停止 'ora.ctssd' (在 'xff2' 上)
CRS-2677: 成功停止 'ora.ctssd' (在 'xff2' 上)
CRS-4000: 命令 Start 失败, 或已完成但出现错误。

C:\Users\Administrator>sqlplus / as sysasm

SQL*Plus: Release 12.1.0.2.0 Production on 星期四 5月 4 13:52:07 2023

Copyright (c) 1982, 2019, Oracle.  All rights reserved.

已连接到空闲例程。

SQL> startup nomount pfile='f:/pfile_asm.txt';
ASM 实例已启动

Total System Global Area 1140850688 bytes
Fixed Size                  3054680 bytes
Variable Size            1112630184 bytes
ASM Cache                  25165824 bytes

SQL>  create diskgroup OCR_VOTE  external redundancy disk '\\.\ORCLDISKDATA4' force  attribute 'COMPATIBLE.ASM' = '12.1.0';

Diskgroup created.

F:\>ocrconfig -restore backup00.ocr

F:\>crsctl replace votedisk +OCR_VOTE
已成功添加表决磁盘 e2b8fdbd05ae4f9fbf3531630853dbbc。
已成功将表决磁盘组替换为 +OCR_VOTE。
CRS-4266: 已成功替换表决文件

F:\>crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   e2b8fdbd05ae4f9fbf3531630853dbbc (\\.\ORCLDISKDATA4) [OCR_VOTE]
找到了 1 个表决磁盘。

F:\>ocrcheck
Oracle 集群注册表的状态如下:
         版本                  :          4
         总空间 (KB)     :     409568
         已用空间 (KB)      :       1348
         可用空间 (KB):     408220
         ID                       :  820087446
         设备/文件名         :  +OCR_VOTE
                                    设备/文件完整性检查成功

                                    设备/文件尚未配置

                                    设备/文件尚未配置

                                    设备/文件尚未配置

                                    设备/文件尚未配置

         集群注册表完整性检查成功

         逻辑损坏检查成功

mount其他磁盘组成功

SQL> alter diskgroup arch mount;

Diskgroup altered.

SQL>


SQL> alter diskgroup data mount;

Diskgroup altered.

尝试恢复数据库失败

C:\Users\Administrator>sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on 星期四 5月 4 14:09:39 2023

Copyright (c) 1982, 2019, Oracle.  All rights reserved.

已连接到空闲例程。

SQL> startup mount;
ORACLE 例程已经启动。

Total System Global Area 2.0992E+11 bytes
Fixed Size                  7797816 bytes
Variable Size            1.3798E+11 bytes
Database Buffers         7.1672E+10 bytes
Redo Buffers              260636672 bytes
数据库装载完毕。

SQL> recover database;
ORA-10562: Error occurred while applying redo to data block (file# 13, block#1033775)
ORA-10564: tablespace USERS
ORA-01110: 数据文件 13: '+DATA/XFF/users07.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 40396
ORA-00600: 内部错误代码, 参数: [kdolkr-2], [2], [1], [44], [], [], [], [], [],[], [], []


SQL> recover datafile 2;
ORA-00283: 恢复会话因错误而取消
ORA-00742: 日志读取在线程 1 序列 60656 块 1150508 中检测到写入丢失情况
ORA-00312: 联机日志 3 线程 1: '+DATA/XFF/redo03.log'


SQL> recover datafile 1;
ORA-00283: 恢复会话因错误而取消
ORA-00742: 日志读取在线程 1 序列 60656 块 1150508 中检测到写入丢失情况
ORA-00312: 联机日志 3 线程 1: '+DATA/XFF/redo03.log'

SQL> recover datafile 10;
ORA-00283: ??????????
ORA-10562: Error occurred while applying redo to data block (file# 10, block#
2899468)
ORA-10564: tablespace USERS
ORA-01110: ???? 10: '+DATA/XFF/users04.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 40396
ORA-00600: ??????, ??: [ktbair2: illegal  inheritance], [], [], [], [], [], [],[], [], [], [], []

除了ORA-00742,还有其他一些日志应用错误,比如:ORA-600 ktbair2: illegal inheritance,ORA-600 kdolkr-2等,无法正常应用日志,尝试强制打开库,报ORA-600 2662错误.

SQL> alter database open resetlogs;
alter database open resetlogs
*
第 1 行出现错误:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [2662], [8], [678024613], [8],
[678508930], [12583040], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [8], [678024612], [8],
[678508930], [12583040], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [8], [678024610], [8],
[678508930], [12583040], [], [], [], [], [], []
进程 ID: 4628
会话 ID: 996 序列号: 48547

通过自研的Patch_SCN工具快速解决该问题
20230507195805

open数据库成功,实现最大限度抢救客户数据.

Control file mount id mismatch!故障处理

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：Control file mount id mismatch!故障处理

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

通过沟通确认客户由于存储双活异常,业务运行在主存储上,另外一套存储修复之后,进行存储双活同步,结果在这个过程中由于遭遇Control file mount id mismatch! 导致数据库crash了

2023-05-03T20:21:07.446873+08:00
Archived Log entry 491897 added for T-1.S-246903 ID 0x97d92f0b LAD:1
2023-05-03T20:47:53.902701+08:00
Error: 2141
Control file mount id mismatch!
fhmid: 2592441863, SGA mid: 2624617448
Requesting DIAG on each RAC instance to dump the control file header block
2023-05-03T20:47:55.906490+08:00
Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_rms0_20989.trc:
2023-05-03T20:47:56.521500+08:00
RMS0 (ospid: 20989): terminating the instance
2023-05-03T20:47:56.610656+08:00
System state dump requested by (instance=1, osid=20989 (RMS0)), summary=[abnormal instance termination].
System State dumped to trace file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_diag_20912_20230503204756.trc
2023-05-03T20:47:58.480397+08:00
License high water mark = 395
2023-05-03T20:48:02.600203+08:00
Instance terminated by RMS0, pid = 20989
2023-05-03T20:48:02.601563+08:00
Warning: 2 processes are still attach to shmid 393226:
 (size: 28672 bytes, creator pid: 19941, last attach/detach pid: 20912)
2023-05-03T20:48:03.481726+08:00
USER (ospid: 967): terminating the instance
2023-05-03T20:48:03.483351+08:00
Instance terminated by USER, pid = 967

节点自动重启报错ORA-600 kccsbck_first

2023-05-03T20:48:34.870435+08:00
NOTE: ASMB mounting group 2 (FRA)
NOTE: ASM background process initiating disk discovery for grp 2 (reqid:0)
NOTE: Assigning number (2,1) to disk (/dev/asm_data0g)
NOTE: Assigning number (2,0) to disk (/dev/asm_data0f)
SUCCESS: mounted group 2 (FRA)
NOTE: grp 2 disk 1: FRA_0001 path:/dev/asm_data0g
NOTE: grp 2 disk 0: FRA_0000 path:/dev/asm_data0f
2023-05-03T20:48:34.919965+08:00
NOTE: dependency between database xff and diskgroup resource ora.FRA.dg is established
2023-05-03T20:48:38.983416+08:00
Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_2436.trc  (incident=1333249):
ORA-00600: ??????, ??: [kccsbck_first], [1], [2624617448], [], [], [], [], [], [], [], [], []
Incident details in: /opt/rac/oracle/diag/rdbms/xff/xff1/incident/incdir_1333249/xff1_ora_2436_i1333249.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ORA-600 signalled during: ALTER DATABASE MOUNT /* db agent *//* {0:8:116} */...

再次重启数据库报错ORA-00742 ORA-00312

2023-05-04T08:18:59.635790+08:00
Aborting crash recovery due to error 742
2023-05-04T08:18:59.635897+08:00
Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_80855.trc:
ORA-00742: ??????? 2 ?? 244996 ? 8262 ??????????
ORA-00312: ???? 7 ?? 2: '+FRA/xff/ONLINELOG/group_7.446.1059323695'
ORA-00312: ???? 7 ?? 2: '+DATA/xff/ONLINELOG/group_7.272.1059323695'
Abort recovery for domain 0, flags 4
2023-05-04T08:18:59.647994+08:00
Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_80855.trc:
ORA-00742: ??????? 2 ?? 244996 ? 8262 ??????????
ORA-00312: ???? 7 ?? 2: '+FRA/xff/ONLINELOG/group_7.446.1059323695'
ORA-00312: ???? 7 ?? 2: '+DATA/xff/ONLINELOG/group_7.272.1059323695'
ORA-742 signalled during: ALTER DATABASE OPEN /* db agent *//* {2:37368:2} */...
2023-05-04T08:19:00.820708+08:00
License high water mark = 33
2023-05-04T08:19:00.820936+08:00
USER (ospid: 82788): terminating the instance
2023-05-04T08:19:01.827132+08:00
Instance terminated by USER, pid = 82788

明显数据库在启动的时候做实例恢复,发现redo写丢失,从而引起数据库无法正常open,对于此类故障,处理比较多
ORA-00742 ORA-00312 故障恢复-1
ORA-00742 ORA-00312故障恢复-2
ORA-00742: 日志读取在线程 %d 序列 %d 块 %d 中检测到写入丢失情况

Maximum of 148 enabled roles exceeded for user ZLHIS. Not loading all the roles.

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：Maximum of 148 enabled roles exceeded for user ZLHIS. Not loading all the roles.

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

中联的his系统在alert日志中经常会看到如下的日志告警

[oracle@oracle1 trace]$ tail -f alert_orcl.log 
Tue May 02 22:06:46 2023
Maximum of 148 enabled roles exceeded for user ZLHIS. Not loading all the roles.
Tue May 02 22:06:50 2023
Maximum of 148 enabled roles exceeded for user ZLHIS. Not loading all the roles.
Tue May 02 22:06:50 2023
Maximum of 148 enabled roles exceeded for user ZLHIS. Not loading all the roles.
Tue May 02 22:06:50 2023
Maximum of 148 enabled roles exceeded for user ZLHIS. Not loading all the roles.
Tue May 02 22:06:50 2023
Maximum of 148 enabled roles exceeded for user ZLHIS. Not loading all the roles.

查询ZLHIS用户当前的role情况

SQL>  select Grantee, count(*) "Role Number" from
  2   (
  3   select distinct connect_by_root grantee Grantee, granted_role
  4   from dba_role_privs 
 connect by prior granted_role=grantee
  5    6   ) where GRANTEE='ZLHIS'
 group by Grantee  7  
  8  /

GRANTEE                        Role Number
------------------------------ -----------
ZLHIS                                  149

虽然max_enabled_roles参数为150

SQL> show parameter MAX_ENABLED_ROLES;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
max_enabled_roles                    integer     150

但是用户支持的默认最大enable role为148个,对于该问题可以把一些角色的权限进行合并,然后再授权给ZLHIS,或者删除掉一些不需要的角色授权.如果一定需要这些角色,而且使其在用户登录的时候enable,可以以下两种常见方法解决

alter user <username> default roles <list of roles>;   
--可以是all或者角色列表

或者在会话中启用role

set roles all;
or
execute dbms_session.set_role('ALL');

参考:What to Check When Dealing With Ora-28031: Maximum Of 148 Enabled Roles Exceeded? (Doc ID 778785.1)

echo 0 > /proc/sys/kernel/hung_task_timeout_secs disables this message

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：echo 0 > /proc/sys/kernel/hung_task_timeout_secs disables this message

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

客户反馈数据库无法登录,系统ssh也无法登录,但是可以ping通,通过sqlplus sys/pwd@tns as sysdba方式登录成功,直接对数据库进行shutdown abort操作,然后系统可以正常ssh登录.通过分析发现一些io问题

系统messages日志报错
20230430084031

默认情况下， Linux会最多使用40%[根据系统配置决定]的可用内存作为文件系统缓存。当超过这个阈值后，文件系统会把将缓存中的内存全部写入磁盘， 导致后续的IO请求都是同步的。将缓存写入磁盘时，有一个默认120秒的超时时间。 出现上面的问题的原因是IO子系统的处理速度不够快，不能在120秒将缓存中的数据全部写入磁盘。IO系统响应缓慢，导致越来越多的请求堆积，最终系统内存全部被占用，导致系统失去响应。

检查系统io情况
20230430084643
磁盘在io请求很小的情况下busy 100%,属于不正常情况,让客户安排人检查硬盘情况
20230430084802
发现raid 5中有一块磁盘异常从而引起性能下降,客户安排人员换盘之后,系统恢复正常.

调整系统参数缓解
对于linux系统文件系统缓存可以进行调整参数vm.dirty_background_ratio和vm.dirty_ratio为适当值,比如

vm.dirty_background_ratio = 5
vm.dirty_ratio = 10

ORA-600 kzrini:!uprofile处理

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：ORA-600 kzrini:!uprofile处理

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

朋友反馈,oracle expdp导出数据hang住,然后重启数据库,启动成功,但是执行导出的时候报ORA-600 kzrini:!uprofile错误
kzrini uprofile

因为有过大量类似故障的恢复case,所以第一反应这种故障很可能就是tab$被清空的故障,参见:警告：互联网中有oracle介质被注入恶意程序导致—ORA-600 16703,对于这类故障,我们是国内第一个发现并且进行预警(在blog,qq/微信群,oracle技术大会等),但是还有很多朋友中招.今天这个发现故障之后没有重启,比较顺利，进行山删除插入即可,参考以前的处理:ORA-600 16703直接把orachk备份表插入到tab$恢复

数据库open报ORA-07445 kglsget错误处理

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：数据库open报ORA-07445 kglsget错误处理

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

有朋友反馈,数据库服务器断电之后,强制拉库无法open成功

Wed Apr 19 18:13:30 2023
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
 parallel recovery started with 32 processes
Started redo scan
Completed redo scan
 read 35 KB redo, 20 data blocks need recovery
Started redo application at
 Thread 1: logseq 4, block 3
Recovery of Online Redo Log: Thread 1 Group 1 Seq 4 Reading mem 0
  Mem# 0: E:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG
Completed redo application of 0.02MB
Completed crash recovery at
 Thread 1: logseq 4, block 73, scn 157134992
 20 data blocks read, 20 data blocks written, 35 redo k-bytes read
Thread 1 advanced to log sequence 5 (thread open)
Thread 1 opened at log sequence 5
  Current log# 2 seq# 5 mem# 0: E:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO02.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
Starting background process QMNC
Wed Apr 19 18:13:34 2023
QMNC started with pid=56, OS id=6380 
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x12] [PC:0x9068BE9, kglsget()+547]
ERROR: Unable to normalize symbol name for the following short stack (at offset 199):
dbgexProcessError()+193<-dbgeExecuteForError()+65<-dbgePostErrorKGE()+1726
<-dbkePostKGE_kgsf()+75<-kgeade()+560<-kgerev()+125<-kgerec5()+60<-sss_xcpt_EvalFilterEx()+1869
<-sss_xcpt_EvalFilter()+174<-.1.6_8+59<-00007FFB13102316<-00007FFB1311398D<-00007FFB130D93A7
<-00007FFB13112B1A<-kglsget()+547<-qcdolci()+80<-qcdoloi()+167<-qcdlgcd()+940<-kkdlgcd()+129
<-PGOSF158_kkmfbtcn()+17<-qcsIsColInFro()+474<-qcsRslvColWithinQbc()+304<-qcsStrongColRslv()+632
<-qcsRslvName()+212<-qcsridn()+104<-qcsraic()+736<-qcspqbDescendents()+485<-qcspqb()+154<-kkmdrv()+200
<-opiSem()+2560<-opiDeferredSem()+565<-opitca()+391<-PGOSF525_kksFullTypeCheck()+27<-rpiswu2()+2757
<-kksLoadChild()+9357<-kxsGetRuntimeLock()+2320<-kksfbc()+15225<-kkspsc0()+2117<-kksParseCursor()+181
<-opiosq0()+2538<-opiall0()+6705<-opikpr()+699<-opiodr()+1662<-rpidrus()+862<-rpidru()+154<-rpiswu2()+2757
<-kprball()+1610<-qmCheckIfXdbInstalled()+1059<-qm_open_db()+11<-kscnfy()+778
Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_6036.trc  (incident=113085):
ORA-07445: 出现异常错误: 核心转储 [kglsget()+547] [ACCESS_VIOLATION] [ADDR:0x12] [PC:0x9068BE9] [UNABLE_TO_READ] []
Incident details in: e:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_113085\orcl_ora_6036_i113085.trc
Wed Apr 19 18:13:36 2023
Trace dumping is performing id=[cdmp_20230419181336]
Wed Apr 19 18:13:39 2023
PMON (ospid: 6624): terminating the instance due to error 397
Instance terminated by PMON, pid = 6624

查看trace文件

*** 2023-04-21 17:29:42.077
*** SESSION ID:(898.359) 2023-04-21 17:29:42.077
*** CLIENT ID:() 2023-04-21 17:29:42.077
*** SERVICE NAME:(SYS$USERS) 2023-04-21 17:29:42.077
*** MODULE NAME:(sqlplus.exe) 2023-04-21 17:29:42.077
*** ACTION NAME:() 2023-04-21 17:29:42.077
 
Dump continued from file: e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_9648.trc
ORA-07445: 出现异常错误: 核心转储 [kglsget()+547] [ACCESS_VIOLATION] [ADDR:0x12] [PC:0x9138BE9] [UNABLE_TO_READ] []

========= Dump for incident 444285 (ORA 7445 [kglsget()+547]) ========
----- Beginning of Customized Incident Dump(s) -----
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x12] [PC:0x9138BE9, kglsget()+547]

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
Process Id: 0x00000a8c  Thread Id : 0x000025b0    Time : Fri Apr 21 17:29:42 
Excp. Code: 0xc0000005  Excp. Type: ACCESS_VIO    Flags: 0x00000000

------------------- Registers ----------------------------
ip=0000000009138BE9 sp=00000000276FA470 rp=0000000A0BF280D0
r1=000000001089AFE0 r2=0000000000000000 r3=0000000000000101 
r4=00000009BDFE40B0 r5=00000000276FA470 r6=0000000A0BF280D0 r7=00000000000005C0 
r8=00000009B9DC4F48 r9=0000000A0BF280D0 r10=0000000000000200 r11=00000000276FA590 
r12=00000009ED85F4C0 r13=000000000CB3C070 r14=0000000000000001 r15=0000000000000001 
------------------- End of Registers ---------------------


*** 2023-04-21 17:29:42.077
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=gtf6tgc2ycgxx) -----
select count(*) from XDB.XDB$SCHEMA s where s.xmldata.schema_url = 'http://xmlns.oracle.com/xdb/XDBSchema.xsd'

----- Call Stack Trace -----
calling              call     entry                argument values in hex      
location             type     point                (? means dubious value)     
-------------------- -------- -------------------- ----------------------------
kglsget()+547                 0000000000000000     009962700 00996270C 000000000
                                                   0276DCCA0
qcdolci()+80         CALL???  kglsget()+347        9C5F9E7D0 009138AE2 000000018
                                                   000000001
qcdoloi()+167        CALL???  qcdolci()            00000DC7E 008D52DEF 000000006
                                                   00CB5BEE8
qcdlgcd()+940        CALL???  qcdoloi()            000000000 000000000 000000000
                                                   000000000
kkdlgcd()+129        CALL???  qcdlgcd()            000000000 9B9DC6C78 000000000
                                                   01089AA20
__PGOSF158_kkmfbtcn  CALL???  kkdlgcd()            01089AFE0 00CB5BEE8 000000000
()+17                                              000000000
qcsIsColInFro()+474  CALL???  __PGOSF158_kkmfbtcn  000000001 9BDFE41E0 000000000
                              ()                   000000001
qcsRslvColWithinQbc  CALL???  qcsIsColInFro()      900000000 01089AFE0 0276FCFC0
()+304                                             742E204F1B71
qcsStrongColRslv()+  CALL???  qcsRslvColWithinQbc  000000010 27F00000000
632                           ()+73                000000000 000000000
qcsRslvName()+212    CALL???  qcsStrongColRslv()+  0276FA9E0 9C3F136C0 00764E4E0
                              516                  0093A505B
qcsridn()+104        CALL???  qcsRslvName()        101000000000000 000000000
                                                   000000000 0276FAE90
qcsraic()+736        CALL???  qcsridn()            0276FACB0 0276FACB0 000000000
                                                   000000001
qcspqbDescendents()  CALL???  qcsraic()            0276FAE90 01089AFE0 00CB5D030
+485                                               00CB5CEE8
qcspqb()+154         CALL???  qcspqbDescendents()  00000002A 008D53029 01089AFE0
                                                   000000000
kkmdrv()+200         CALL???  qcspqb()             000000029 00895C700 0276FAF90
                                                   00895C700
opiSem()+2560        CALL???  kkmdrv()             00CB31730 0108B7820 000000001
                                                   9C3F13730
opiDeferredSem()+56  CALL???  opiSem()             0276FCFC0 A09FA3D68 00000006E
5                                                  000000001
opitca()+391         CALL???  opiDeferredSem()     000000001 000000000 006F7AC18
                                                   000000000
__PGOSF525_kksFullT  CALL???  opitca()             037615F10 9C3F138D0 0277000A0
ypeCheck()+27                                      00895C700
rpiswu2()+2757       CALL???  __PGOSF525_kksFullT  0276FEB98 000004018 0108A04E0
                              ypeCheck()           0108A0700
kksLoadChild()+9357  CALL???  rpiswu2()            9F86A81C8 000000000 9C5F9D1E4
                                                   000000002
kxsGetRuntimeLock()  CALL???  kksLoadChild()       01089AFE0 A09FA39D8 0276FF400
+2320                                              A09FA39D8
kksfbc()+15225       CALL???  kxsGetRuntimeLock()  01089AFE0 037615F10 0276FF400
                                                   000000103
kkspsc0()+2117       CALL???  kksfbc()             037615F10 000000003 A00000108
                                                   0076D1C80
kksParseCursor()+18  CALL???  kkspsc0()            00CAD1DA8 0076D1C80 00000006F
1                                                  000000003
opiosq0()+2538       CALL???  kksParseCursor()     00CACF990 000000000 00895C700
                                                   027700940
opiall0()+6705       CALL???  opiosq0()            000000003 00000000E 0277010C0
                                                   000000020
opikpr()+699         CALL???  opiall0()            000000065 000000022 0277018C8
                                                   000000000
opiodr()+1662        CALL???  opikpr()             000000065 90000001C 027703208
                                                   01089AA20
rpidrus()+862        CALL???  opiodr()             000000065 00000001C 027703208
                                                   000000000
rpidru()+154         CALL???  rpidrus()            0277027F8 000000000 000000000
                                                   000000000
rpiswu2()+2757       CALL???  rpidru()             027703030 000000000 000000000
                                                   000000000
kprball()+1610       CALL???  rpiswu2()            9F86A81C8 000000000 027702E50
                                                   000000002
qmCheckIfXdbInstall  CALL???  kprball()            027703208 000000100 000000002
ed()+1059                                          00CAEC188
qm_open_db()+11      CALL???  qmCheckIfXdbInstall  000000000 000000000 000000000
                              ed()                 00895C700
kscnfy()+778         CALL???  qm_open_db()         657FC5CD00000019 000000000
                                                   000000000 100000000
adbdrv()+45489       CALL???  kscnfy()             000000019 000000000 000000000
                                                   000000000
opiexe()+20842       CALL???  adbdrv()             000000023 000000003 A00000102
                                                   000000000
opiosq0()+5129       CALL???  opiexe()+16981       000000004 000000000 02770A8C0
                                                   009121AB3
kpooprx()+357        CALL???  opiosq0()            000000003 00000000E 02770AB90
                                                   0000000A4
kpoal8()+940         CALL???  kpooprx()            01089AFE0 0090CC0A8 01089AFE0
                                                   000000001
opiodr()+1662        CALL???  kpoal8()             00000005E 00000001C 02770E100
                                                   00ABBF224
ttcpip()+1325        CALL???  opiodr()             00000005E 00000001C 02770E100
                                                   4100200000000000
opitsk()+2040        CALL???  ttcpip()             0108B4D00 000000000 000000000
                                                   000000000
opiino()+1258        CALL???  opitsk()             00000001E 000000000 000000000
                                                   02770F9F8
opiodr()+1662        CALL???  opiino()             00000003C 000000004 02770FAB0
                                                   000000000
opidrv()+864         CALL???  opiodr()             00000003C 000000004 02770FAB0
                                                   615C3A6500000000
sou2o()+98           CALL???  opidrv()+150         00000003C 000000004 02770FAB0
                                                   000000000
opimai_real()+158    CALL???  sou2o()              064425745 000000000 000000000
                                                   02770FBA4
opimai()+191         CALL???  opimai_real()        7FFA241388C0 7FFA24138A49
                                                   000000000 00895C700

*** 2023-04-21 17:29:42.343
OracleThreadStart()  CALL???  opimai()             000401452 000000002 0085DFE20
+724                                               0000025B0
00007FFA246713D2     CALL???  OracleThreadStart()  00FCAFF18 000000000 000000000
                                                   000000000
00007FFA26D403C4     CALL???  00007FFA246713B0     7FFA246713B0 000000000
                                                   000000000 000000000
 

--------------------- Binary Stack Dump ---------------------

确定报错是在select count(*) from XDB.XDB$SCHEMA s where s.xmldata.schema_url = ‘http://xmlns.oracle.com/xdb/XDBSchema.xsd’这个sql语句中,对其数据库启动过程进行跟踪，没有发现该语句而是只有报错

EXEC #6:c=0,e=181,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=4,plh=3755742892,tim=22655713465
FETCH #6:c=0,e=12,p=0,cr=3,cu=0,mis=0,r=1,dep=2,og=4,plh=3755742892,tim=22655713503
CLOSE #6:c=0,e=6,dep=2,type=3,tim=22655713532
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x12] [PC:0x9138BE9, kglsget()+547]
 dump file: e:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_452285\orcl_ora_9848_i452285.trc
ORA-07445: 出现异常错误: 核心转储 [kglsget()+547] [ACCESS_VIOLATION] [ADDR:0x12] [PC:0x9138BE9] [UNABLE_TO_READ] []

证明ORA-07445 kglsget错误的语句没有到sql执行阶段,而是在解析阶段就开始报错.通过对oracle启动过程进行处理(因为该语句不是数据库启动个必须的语句)，规避掉该sql执行,实现数据库正常open
20230421223825

12.1.0.2最新patch信息—202304

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：12.1.0.2最新patch信息—202304

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

Database Patch Set Update (PSU)

Release Date Version Download link Included in Windows Bundle
18-Apr-2023 12.1.0.2.230418 (Apr 2023) Database Patch Set Update (DB PSU) Patch 34998358 NA – out of error correction
17-Jan-2023 12.1.0.2.230117 (Jan 2023) Database Patch Set Update (DB PSU) Patch 34677720 NA – out of error correction
18-Oct-2022 12.1.0.2.221018 (Oct 2022) Database Patch Set Update (DB PSU) Patch 34386266 NA – out of error correction
19-Jul-2022 12.1.0.2.220719 (Jul 2022) Database Patch Set Update (DB PSU) Patch 34057742 12.1.0.2.220719 WIN DB BP Patch 33883271
19-Apr-2022 12.1.0.2.220419 (Apr 2022) Database Patch Set Update (DB PSU) Patch 33711081 12.1.0.2.220419 WIN DB BP Patch 33777450
18-Jan-2022 12.1.0.2.220118 (Jan 2022) Database Patch Set Update (DB PSU) Patch 33477199 12.1.0.2.220118 WIN DB BP Patch 33492893
19-Oct-2021 12.1.0.2.211019 (Oct 2021) Database Patch Set Update (DB PSU) Patch 33128590 12.1.0.2.211019 WIN DB BP Patch 33174365
20-Jul-2021 12.1.0.2.210720 (Jul 2021) Database Patch Set Update (DB PSU) Patch 32768233 12.1.0.2.210720 WIN DB BP Patch 32774982
20-Apr-2021 12.1.0.2.210420 (Apr 2021) Database Patch Set Update (DB PSU) Patch 32328635 12.1.0.2.210420 WIN DB BP Patch 32396181
19-Jan-2021 12.1.0.2.210119 (Jan 2021) Database Patch Set Update (DB PSU) Patch 31985579 12.1.0.2.210119 WIN DB BP Patch 32000405
20-Oct-2020 12.1.0.2.201020 (Oct 2020) Database Patch Set Update (DB PSU) Patch 31550110 12.1.0.2.201020 WIN DB BP Patch 31658987
14-Jul-2020 12.1.0.2.200714 (Jul 2020) Database Patch Set Update (DB PSU) Patch 31113348 12.1.0.2.200714 WIN DB BP Patch 31211574
14-Apr-2020 12.1.0.2.200414 (Apr 2020) Database Patch Set Update (DB PSU) Patch 30700212 12.1.0.2.200414 WIN DB BP Patch 30861721
14-Jan-2020 12.1.0.2.200114 (Jan 2020) Database Patch Set Update (DB PSU) Patch 30340202 12.1.0.2.200114 WIN DB BP Patch 30455401
15-Oct-2019 12.1.0.2.191015 (Oct 2019) Database Patch Set Update (DB PSU) Patch 29918340 12.1.0.2.191015 WIN DB BP Patch 30049606
16-Jul-2019 12.1.0.2.190716 (Jul 2019) Database Patch Set Update (DB PSU) Patch 29494060 12.1.0.2.190716 WIN DB BP Patch 29831650
16-Apr-2019 12.1.0.2.190416 (Apr 2019) Database Patch Set Update (DB PSU) Patch 29141015 12.1.0.2.190416 WIN DB BP Patch 29413116
15-Jan-2019 12.1.0.2.190115 (Jan 2019) Database Patch Set Update (DB PSU) Patch 28729169 12.1.0.2.190115 WIN DB BP Patch 28810679
16-Oct-2018 12.1.0.2.181016 (Oct 2018) Database Patch Set Update (DB PSU) Patch 28259833 12.1.0.2.181016 WIN DB BP Patch 28563501
17-Jul-2018 12.1.0.2.180717 (Jul 2018) Database Patch Set Update (DB PSU) Patch 27547329 12.1.0.2.180717 WIN DB BP Patch 27937907
17-Apr-2018 12.1.0.2.180417 (Apr 2018) Database Patch Set Update (DB PSU) Patch 27338041 12.1.0.2.180417 WIN DB BP Patch 27440294
16-Jan-2018 12.1.0.2.180116 (Jan 2018) Database Patch Set Update (DB PSU) Patch 26925311 12.1.0.2.180116 WIN DB BP Patch 27162953
17-Oct-2017 12.1.0.2.171017 (Oct 2017) Database Patch Set Update (DB PSU) Patch 26713565 12.1.0.2.171017 WIN DB BP Patch 26720785
14-Aug-2017 12.1.0.2.170814 (Jul 2017) Database Patch Set Update (DB PSU) Patch 26609783 12.1.0.2.170814 WIN DB BP Patch 26161726
18-Jul-2017 12.1.0.2.170718 (Jul 2017) Database Patch Set Update (DB PSU) Patch 25755742 12.1.0.2.170718 WIN DB BP Patch 26161724
18-Apr-2017 12.1.0.2.170418 (Apr 2017) Database Patch Set Update (DB PSU) Patch 25171037 12.1.0.2.170418 WIN DB BP Patch 25632533
17-Jan-2017 12.1.0.2.170117 (Jan 2017) Database Patch Set Update (DB PSU) Patch 24732082 12.1.0.2.170117 WIN DB BP Patch 25115951
18-Oct-2016 12.1.0.2.161018 (Oct 2016) Database Patch Set Update (DB PSU) Patch 24006101 12.1.0.2.161018 WIN DB BP Patch 24591642
19-Jul-2016 12.1.0.2.160719 (Jul 2016) Database Patch Set Update (DB PSU) Patch 23054246 12.1.0.2.160719 WIN DB BP Patch 23530387
19-Apr-2016 12.1.0.2.160419 (Apr 2016) Database Patch Set Update (DB PSU) Patch 22291127 12.1.0.2.160419 WIN DB BP Patch 22809813
19-Jan-2016 12.1.0.2.160119 (Jan 2016) Database Patch Set Update (DB PSU) Patch 21948354 12.1.0.2.160119 WIN DB BP Patch 22310559
20-Oct-2015 12.1.0.2.5 (Oct 2015) Database Patch Set Update (DB PSU) Patch 21359755 12.1.0.2 Patch 10 Patch 21821214
14-Jul-2015 12.1.0.2.4 (Jul 2015) Database Patch Set Update (DB PSU) Patch 20831110 12.1.0.2 Patch 7 Patch 21126814
14-Apr-2015 12.1.0.2.3 (Apr 2015) Database Patch Set Update (DB PSU) Patch 20299023 12.1.0.2 Patch 4 Patch 20684004
20-Jan-2015 12.1.0.2.2 (Jan 2015) Database Patch Set Update (DB PSU) Patch 19769480 12.1.0.2 Patch 1 Patch 19720843
14-Oct-2014 12.1.0.2.1 (Oct 2014) Database Patch Set Update (DB PSU) Patch 19303936 none

Grid Infrastructure Patch Set Update (PSU)

Release Date Version Download link
18-Apr-2023 12.1.0.2.230418 (Apr 2023) Grid Infrastructure Patch Set Update (GI PSU) Patch 35058268
17-Jan-2023 12.1.0.2.230117 (Jan 2023) Grid Infrastructure Patch Set Update (GI PSU) Patch 34774519
18-Oct-2022 12.1.0.2.221018 (Oct 2022) Grid Infrastructure Patch Set Update (GI PSU) Patch 34535560
19-Jul-2022 12.1.0.2.220719 (Jul 2022) Grid Infrastructure Patch Set Update (GI PSU) Patch 34204576
19-Apr-2022 12.1.0.2.220419 (Apr 2022) Grid Infrastructure Patch Set Update (GI PSU) Patch 33829718
18-Jan-2022 12.1.0.2.220118 (Jan 2022) Grid Infrastructure Patch Set Update (GI PSU) Patch 33575274
19-Oct-2021 12.1.0.2.211019 (Oct 2021) Grid Infrastructure Patch Set Update (GI PSU) Patch 33248367
20-Jul-2021 12.1.0.2.210720 (Jul 2021) Grid Infrastructure Patch Set Update (GI PSU) Patch 32917447
20-Apr-2021 12.1.0.2.210420 (Apr 2021) Grid Infrastructure Patch Set Update (GI PSU) Patch 32495126
19-Jan-2021 12.1.0.2.210119 (Jan 2021) Grid Infrastructure Patch Set Update (GI PSU) Patch 32131261
20-Oct-2020 12.1.0.2.201020 (Oct 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 31718737
14-Jul-2020 12.1.0.2.200714 (Jul 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 31305174
14-Apr-2020 12.1.0.2.200414 (Apr 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 30805421
14-Jan-2020 12.1.0.2.200114 (Jan 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 30464119
15-Oct-2019 12.1.0.2.191015 (Oct 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 30070257
16-Jul-2019 12.1.0.2.190716 (Jul 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 29698592
16-Apr-2019 12.1.0.2.190416 (Apr 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 29176115
15-Jan-2019 12.1.0.2.190115 (Jan 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 28813884
16-Oct-2018 12.1.0.2.181016 (Oct 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 28349311
17-Jul-2018 12.1.0.2.180717 (Jul 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 27967747
17-Apr-2018 12.1.0.2.180417 (Apr 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 27468957
16-Jan-2018 12.1.0.2.180116 (Jan 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 27010872
17-Oct-2017 12.1.0.2.171017 (Oct 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 26635815
14-Aug-2017 12.1.0.2.170814 (Jul 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 26610308
18-Jul-2017 12.1.0.2.170718 (Jul 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 25901062
18-Apr-2017 12.1.0.2.170418 (Apr 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 25434003
17-Jan-2017 12.1.0.2.170117 (Jan 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 24917825
18-Oct-2016 12.1.0.2.161018 (Oct 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 24412235
19-Jul-2016 12.1.0.2.160719 (Jul 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 23273629
19-Apr-2016 12.1.0.2.160419 (Apr 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 22646084
19-Jan-2016 12.1.0.2.160119 (Jan 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 22191349
20-Oct-2015 12.1.0.2.5 (Oct 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 21523234
14-Jul-2015 12.1.0.2.4 (Jul 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 20996835
14-Apr-2015 12.1.0.2.3 (Apr 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 20485724
20-Jan-2015 12.1.0.2.2 (Jan 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 19954978
14-Oct-2014 12.1.0.2.1 (Oct 2014) Grid Infrastructure Patch Set Update (GI PSU) Patch 19392646

OJVM Component Patch Set Update (PSU)

Release Date Version Unix PSU Patch Windows Bundle Patch
18-Apr-2023 12.1.0.2.230418 (Apr 2023) OJVM Component Patch Set Update Patch 35077439 NA – out of error correction
17-Jan-2023 12.1.0.2.230117 (Jan 2023) OJVM Component Patch Set Update Patch 34763317 NA – out of error correction
18-Oct-2022 12.1.0.2.221018 (Oct 2022) OJVM Component Patch Set Update Patch 34412250 NA – out of error correction
19-Jul-2022 12.1.0.2.220719 (Jul 2022) OJVM Component Patch Set Update Patch 34086863 Patch 34185253
19-Apr-2022 12.1.0.2.220419 (Apr 2022) OJVM Component Patch Set Update Patch 33808385 Patch 33881387
18-Jan-2022 12.1.0.2.220118 (Jan 2022) OJVM Component Patch Set Update Patch 33561268 Patch 33577533
19-Oct-2021 12.1.0.2.211019 (Oct 2021) OJVM Component Patch Set Update Patch 33192628 Patch 33248785
20-Jul-2021 12.1.0.2.210720 (Jul 2021) OJVM Component Patch Set Update Patch 32876425 Patch 32905878
20-Apr-2021 12.1.0.2.210420 (Apr 2021) OJVM Component Patch Set Update Patch 32473164 Patch 32427683
19-Jan-2021 12.1.0.2.210119 (Jan 2021) OJVM Component Patch Set Update Patch 32119956 Patch 32142066
20-Oct-2020 12.1.0.2.201020 (Oct 2020) OJVM Component Patch Set Update Patch 31668915 Patch 31740134
14-Jul-2020 12.1.0.2.200714 (Jul 2020) OJVM Component Patch Set Update Patch 31219939 Patch 31465095
14-Apr-2020 12.1.0.2.200414 (Apr 2020) OJVM Component Patch Set Update Patch 30805558 Patch 31037459
14-Jan-2020 12.1.0.2.200114 (Jan 2020) OJVM Component Patch Set Update Patch 30502041 Patch 30671054
15-Oct-2019 12.1.0.2.191015 (Oct 2019) OJVM Component Patch Set Update Patch 30128197 Patch 30268189
16-Jul-2019 12.1.0.2.190716 (Jul 2019) OJVM Component Patch Set Update Patch 29774383 Patch 29837393
16-Apr-2019 12.1.0.2.190416 (Apr 2019) OJVM Component Patch Set Update Patch 29251241 Patch 29447962
15-Jan-2019 12.1.0.2.190115 (Jan 2019) OJVM Component Patch Set Update Patch 28790654 Patch 28994063
16-Oct-2018 12.1.0.2.181016 (Oct 2018) OJVM Component Patch Set Update Patch 28440711 Patch 28412299
17-Jul-2018 12.1.0.2.180717 (Jul 2018) OJVM Component Patch Set Update Patch 27923320 Patch 28135126
17-Apr-2018 12.1.0.2.180417 (Apr 2018) OJVM Component Patch Set Update Patch 27475603 Patch 27440294
16-Jan-2018 12.1.0.2.180116 (Jan 2018) OJVM Component Patch Set Update Patch 27001733 Patch 27001733
17-Oct-2017 12.1.0.2.171017 (Oct 2017) OJVM Component Patch Set Update Patch 26635845 Patch 26792364
18-Jul-2017 12.1.0.2.170718 (Jul 2017) OJVM Component Patch Set Update Patch 26027162 Patch 26182439
18-Apr-2017 12.1.0.2.170418 (Apr 2017) OJVM Component Patch Set Update Patch 25437695 Patch 25590993
17-Jan-2017 12.1.0.2.170117 (Jan 2017) OJVM Component Patch Set Update Patch 24917972 Patch 25112498
18-Oct-2016 12.1.0.2.161018 (Oct 2016) OJVM Component Patch Set Update Patch 24315824 Patch 24591630
19-Jul-2016 12.1.0.2.160719 (Jul 2016) OJVM Component Patch Set Update Patch 23177536 Patch 23515290
19-Apr-2016 12.1.0.2.160419 (Apr 2016) OJVM Component Patch Set Update Patch 22674709 Patch 22839633
19-Jan-2016 12.1.0.2.160119 (Jan 2016) OJVM Component Patch Set Update Patch 22139226 Patch 22311086
20-Oct-2015 12.1.0.2.5 (Oct 2015) OJVM Component Patch Set Update Patch 21555660 Patch 21788394
14-Jul-2015 12.1.0.2.4 (Jul 2015) OJVM Component Patch Set Update Patch 21068507 Patch 21153530
14-Apr-2015 12.1.0.2.3 (Apr 2015) OJVM Component Patch Set Update Patch 20415564 Patch 20391199
20-Jan-2015 12.1.0.2.2 (Jan 2015) OJVM Component Patch Set Update Patch 19877336 Patch 20225938
14-Oct-2014 12.1.0.2.1 (Oct 2014) OJVM Component Patch Set Update Patch 19282028 -

参考：Database 12.1.0.2 Proactive Patch Information (Doc ID 2285558.1)

11.2.0.4最新patch信息—202304

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：11.2.0.4最新patch信息—202304

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

Database Patch Set Update

Release Date Version Download link Included in Windows Bundle
18-Apr-2023 11.2.0.4.230418 (Apr 2023) Database Patch Set Update (DB PSU) Patch 34998337 * Out of Error Correction
17-Jan-2023 11.2.0.4.230117 (Jan 2023) Database Patch Set Update (DB PSU) Patch 34677698 * Out of Error Correction
18-Oct-2022 11.2.0.4.221018 (Oct 2022) Database Patch Set Update (DB PSU) Patch 34386237 * Patch 34474433
19-Jul-2022 11.2.0.4.220719 (Jul 2022) Database Patch Set Update (DB PSU) Patch 34057724 * Patch 33883353
19-Apr-2022 11.2.0.4.220419 (Apr 2022) Database Patch Set Update (DB PSU) Patch 33711103 * Patch 33776715
18-Jan-2022 11.2.0.4.220118 (Jan 2022) Database Patch Set Update (DB PSU) Patch 33477185 * Patch 33488457
19-Oct-2021 11.2.0.4.211019 (Oct 2021) Database Patch Set Update (DB PSU) Patch 33128584 * Patch 33174351
20-Jul-2021 11.2.0.4.210720 (Jul 2021) Database Patch Set Update (DB PSU) Patch 32758711 * Patch 32775108
20-Apr-2021 11.2.0.4.210420 (Apr 2021) Database Patch Set Update (DB PSU) Patch 32328626 * Patch 32392141
19-Jan-2021 11.2.0.4.210119 (Jan 2021) Database Patch Set Update (DB PSU) Patch 31983472 Patch 32003403
20-Oct-2020 11.2.0.4.201020 (Oct 2020) Database Patch Set Update (DB PSU) Patch 31537677 Patch 31659823
14-Jul-2020 11.2.0.4.200714 (Jul 2020) Database Patch Set Update (DB PSU) Patch 31103343 Patch 31169916
14-Apr-2020 11.2.0.4.200414 (Apr 2020) Database Patch Set Update (DB PSU) Patch 30670774 Patch 31169916
14-Jan-2020 11.2.0.4.200114 (Jan 2020) Database Patch Set Update (DB PSU) Patch 30298532 Patch 30502376
15-Oct-2019 11.2.0.4.191015 (Oct 2019) Database Patch Set Update (DB PSU) Patch 29913194 Patch 30151661
16-Jul-2019 11.2.0.4.190716 (Jul 2019) Database Patch Set Update (DB PSU) Patch 29497421 Patch 29596609
16-Apr-2019 11.2.0.4.190416 (Apr 2019) Database Patch Set Update (DB PSU) Patch 29141056 Patch 29218820
15-Jan-2019 11.2.0.4.190115 (Jan 2019) Database Patch Set Update (DB PSU) Patch 28729262 Patch 28761877
16-Oct-2018 11.2.0.4.181016 (Oct 2018) Database Patch Set Update (DB PSU) Patch 28204707 Patch 28265827
17-Jul-2018 11.2.0.4.180717 (Jul 2018) Database Patch Set Update (DB PSU) Patch 27734982 Patch 27695940
17-Apr-2018 11.2.0.4.180417 (Apr 2018) Database Patch Set Update (DB PSU) Patch 27338049 Patch 27426753
16-Jan-2018 11.2.0.4.180116 (Jan 2018) Database Patch Set Update (DB PSU) Patch 26925576 Patch 26925576
17-Oct-2017 11.2.0.4.171017 (Oct 2017) Database Patch Set Update (DB PSU) Patch 26392168 Patch 26581376
14-Aug-2017 11.2.0.4.170814 (Jul 2017) Database Patch Set Update (DB PSU) Patch 26609445 Patch 26194138
18-Jul-2017 11.2.0.4.170718 (Jul 2017) Database Patch Set Update (DB PSU) Patch 25869727 Patch 26194136
18-Apr-2017 11.2.0.4.170418 (Apr 2017) Database Patch Set Update (DB PSU) Patch 24732075 Patch 25632525
17-Jan-2017 **
18-Oct-2016 11.2.0.4.161018 (Oct 2016) Database Patch Set Update (DB PSU) Patch 24006111 Patch 24591646
19-Jul-2016 11.2.0.4.160719 (Jul 2016) Database Patch Set Update (DB PSU) Patch 23054359 Patch 23530402
19-Apr-2016 11.2.0.4.160419 (Apr 2016) Database Patch Set Update (DB PSU) Patch 22502456 Patch 22839608
19-Jan-2016 11.2.0.4.160119 (Jan 2016) Database Patch Set Update (DB PSU) Patch 21948347 Patch 22310544
20-Oct-2015 11.2.0.4.8 (Oct 2015) Database Patch Set Update (DB PSU) Patch 21352635 Patch 21821802
14-Jul-2015 11.2.0.4.7 (Jul 2015) Database Patch Set Update (DB PSU) Patch 20760982 Patch 20833831
14-Apr-2015 11.2.0.4.6 (Apr 2015) Database Patch Set Update (DB PSU) Patch 20299013 Patch 20544696
20-Jan-2015 11.2.0.4.5 (Jan 2015) Database Patch Set Update (DB PSU) Patch 19769489 Patch 20127071
14-Oct-2014 11.2.0.4.4 (Oct 2014) Database Patch Set Update (DB PSU) Patch 19121551 Patch 19651773
14-Jul-2014 11.2.0.4.3 (Jul 2014) Database Patch Set Update (DB PSU) Patch 18522509 Patch 18842982
15-Apr-2014 11.2.0.4.2 (Apr 2014) Database Patch Set Update (PSU) Patch 18031668 Patch 18296644
15-Jan-2014 11.2.0.4.1 (Jan 2014) Database Patch Set Update (PSU) Patch 17478514 Patch 17987366

Grid Infrastructure Patch Set Update

Release Date Version Download link
18-Apr-2023 11.2.0.4.230418 (Apr 2023) Grid Infrastructure Patch Set Update (GI PSU) * Patch 35058300
17-Jan-2023 11.2.0.4.230117 (Jan 2023) Grid Infrastructure Patch Set Update (GI PSU) * Patch 34774506
18-Oct-2022 11.2.0.4.221018 (Oct 2022) Grid Infrastructure Patch Set Update (GI PSU) * Patch 34536853
19-Jul-2022 11.2.0.4.220719 (Jul 2022) Grid Infrastructure Patch Set Update (GI PSU) * Patch 34204533
19-Apr-2022 11.2.0.4.220419 (Apr 2022) Grid Infrastructure Patch Set Update (GI PSU) * Patch 33829709
18-Jan-2022 11.2.0.4.220118 (Jan 2022) Grid Infrastructure Patch Set Update (GI PSU) * Patch 33575261
19-Oct-2021 11.2.0.4.211019 (Oct 2021) Grid Infrastructure Patch Set Update (GI PSU) * Patch 33248354
20-Jul-2021 11.2.0.4.210720 (Jul 2021) Grid Infrastructure Patch Set Update (GI PSU) * Patch 32917428
20-Apr-2021 11.2.0.4.210420 (Apr 2021) Grid Infrastructure Patch Set Update (GI PSU) * Patch 32495145
19-Jan-2021 11.2.0.4.210119 (Jan 2021) Grid Infrastructure Patch Set Update (GI PSU) Patch 32131250
20-Oct-2020 11.2.0.4.201020 (Oct 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 31718723
14-Jul-2020 11.2.0.4.200714 (Jul 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 31305209
14-Apr-2020 11.2.0.4.200414 (Apr 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 30805461
14-Jan-2020 11.2.0.4.200114 (Jan 2020) Grid Infrastructure Patch Set Update (GI PSU) Patch 30501155
15-Oct-2019 11.2.0.4.191015 (Oct 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 30070097
16-Jul-2019 11.2.0.4.190716 (Jul 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 29698727
16-Apr-2019 11.2.0.4.190416 (Apr 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 29255947
15-Jan-2019 11.2.0.4.190115 (Jan 2019) Grid Infrastructure Patch Set Update (GI PSU) Patch 28813878
16-Oct-2018 11.2.0.4.181016 (Oct 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 28429134
17-Jul-2018 11.2.0.4.180717 (Jul 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 27967757
17-Apr-2018 11.2.0.4.180417 (Apr 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 27475913
16-Jan-2018 11.2.0.4.180116 (Jan 2018) Grid Infrastructure Patch Set Update (GI PSU) Patch 27107360
17-Oct-2017 11.2.0.4.171017 (Oct 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 26635745
14-Aug-2017 11.2.0.4.170814 (Jul 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 26610246
18-Jul-2017 11.2.0.4.170718 (Jul 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 26030799
18-Apr-2017 11.2.0.4.170418 (Apr 2017) Grid Infrastructure Patch Set Update (GI PSU) Patch 25476126
17-Jan-2017 **
18-Oct-2016 11.2.0.4.161018 (Oct 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 24436338
19-Jul-2016 11.2.0.4.160719 (Jul 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 23274134
19-Apr-2016 11.2.0.4.160419 (Apr 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 22646198
19-Jan-2016 11.2.0.4.160119 (Jan 2016) Grid Infrastructure Patch Set Update (GI PSU) Patch 22191577
20-Oct-2015 11.2.0.4.8 (Oct 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 21523375
14-Jul-2015 11.2.0.4.7 (Jul 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 20996923
14-Apr-2015 11.2.0.4.6 (Apr 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 20485808
20-Jan-2015 11.2.0.4.5 (Jan 2015) Grid Infrastructure Patch Set Update (GI PSU) Patch 19955028
14-Oct-2014 11.2.0.4.4 (Oct 2014) Grid Infrastructure Patch Set Update (GI PSU) Patch 19380115
15-Jul-2014 11.2.0.4.3 (Jul 2014) Grid Infrastructure Patch Set Update (GI PSU) Patch 18706472
15-Apr-2014 11.2.0.4.2 (Apr 2014) Grid Infrastructure Patch Set Update (GI PSU) Patch 18139609

11.2.0.4 OJVM Patch Set Update

Release Date Version Unix PSU Patch Windows Bundle Patch
18-Apr-2023 11.2.0.4.230418 (Apr 2023) OJVM Component Patch Set Update Patch 35039831 * Out of Error Correction
17-Jan-2023 11.2.0.4.230117 (Jan 2023) OJVM Component Patch Set Update Patch 34763334 * Out of Error Correction
18-Oct-2022 11.2.0.4.221018 (Oct 2022) OJVM Component Patch Set Update Patch 34412266 * Patch 34513867
19-Jul-2022 11.2.0.4.220719 (Jul 2022) OJVM Component Patch Set Update Patch 34085652 * Patch 34185082
19-Apr-2022 11.2.0.4.220419 (Apr 2022) OJVM Component Patch Set Update Patch 33829826 * Patch 33881335
18-Jan-2022 11.2.0.4.220118 (Jan 2022) OJVM Component Patch Set Update Patch 33561250 * Patch 33577510
19-Oct-2021 11.2.0.4.211019 (Oct 2021) OJVM Component Patch Set Update Patch 33192642 * Patch 33248711
20-Jul-2021 11.2.0.4.210720 (Jul 2021) OJVM Component Patch Set Update Patch 32876451 * Patch 32905855
20-Apr-2021 11.2.0.4.210420 (Apr 2021) OJVM Component Patch Set Update Patch 32671980 * Patch 32428494
19-Jan-2021 11.2.0.4.210119 (Jan 2021) OJVM Component Patch Set Update ** Patch 32145687
20-Oct-2020 11.2.0.4.201020 (Oct 2020) OJVM Component Patch Set Update Patch 31668908 Patch 31740195
14-Jul-2020 11.2.0.4.200714 (Jul 2020) OJVM Component Patch Set Update Patch 31219953 Patch 31169916
14-Apr-2020 11.2.0.4.200414 (Apr 2020) OJVM Component Patch Set Update Patch 30805543 Patch 31169933
14-Jan-2020 11.2.0.4.200114 (Jan 2020) OJVM Component Patch Set Update Patch 30503372 Patch 30671044
15-Oct-2019 11.2.0.4.191015 (Oct 2019) OJVM Component Patch Set Update Patch 30132974 Patch 30268157
16-Jul-2019 11.2.0.4.190716 (Jul 2019) OJVM Component Patch Set Update Patch 29610422 Patch 30012911
16-Apr-2019 11.2.0.4.190416 (Apr 2019) OJVM Component Patch Set Update Patch 29251270 Patch 29447971
15-Jan-2019 11.2.0.4.190115 (Jan 2019) OJVM Component Patch Set Update Patch 28790660 Patch 28994059
16-Oct-2018 11.2.0.4.181016 (Oct 2018) OJVM Component Patch Set Update Patch 28440700 Patch 28412269
17-Jul-2018 11.2.0.4.180717 (Jul 2018) OJVM Component Patch Set Update Patch 27923163 Patch 28135121
17-Apr-2018 11.2.0.4.180417 (Apr 2018) OJVM Component Patch Set Update Patch 27475598 Patch 27381640
16-Jan-2018 11.2.0.4.180116 (Jan 2018) OJVM Component Patch Set Update Patch 26925532 Patch 27163009
17-Oct-2017 11.2.0.4.171017 (Oct 2017) OJVM Component Patch Set Update Patch 26635834 Patch 26792358
18-Jul-2017 11.2.0.4.170718 (Jul 2017) OJVM Component Patch Set Update Patch 26027154 Patch 26182425
18-Apr-2017 11.2.0.4.170418 (Apr 2017) OJVM Component Patch Set Update Patch 25434033 Patch 25590979
17-Jan-2017 11.2.0.4.170117 (Jan 2017) OJVM Component Patch Set Update Patch 24917954 Patch 25043019
18-Oct-2016 11.2.0.4.161018 (Oct 2016) OJVM Component Patch Set Update Patch 24315821 Patch 24591637
19-Jul-2016 11.2.0.4.160719 (Jul 2016) OJVM Component Patch Set Update Patch 23177551 Patch 23515277
19-Apr-2016 11.2.0.4.160419 (Apr 2016) OJVM Component Patch Set Update Patch 22674697 Patch 22839614
19-Jan-2016 11.2.0.4.160119 (Jan 2016) OJVM Component Patch Set Update Patch 22139245 Patch 22311053
20-Oct-2015 11.2.0.4.5 (Oct 2015) OJVM Component Patch Set Update Patch 21555791 Patch 21788344
14-Jul-2015 11.2.0.4.4 (Jul 2015) OJVM Component Patch Set Update Patch 21068539 Patch 21153498
14-Apr-2015 11.2.0.4.3 (Apr 2015) OJVM Component Patch Set Update Patch 20406239 Patch 20225988
20-Jan-2015 11.2.0.4.2 (Jan 2015) OJVM Component Patch Set Update Patch 19877440 Patch 20225982
14-Oct-2014 11.2.0.4.1 (Oct 2014) OJVM Component Patch Set Update Patch 19282021 Patch 19799291

参考：Database 11.2.0.4 Proactive Patch Information (Doc ID 2285559.1)