ORA-00600 [2662]和ORA-00600 [4194]恢复

数据库启动报ORA-600 2662
20201226220431


Sat Dec 26 19:34:05 2020
alter database open
Beginning crash recovery of 1 threads
 parallel recovery started with 7 processes
Started redo scan
Completed redo scan
 read 0 KB redo, 0 data blocks need recovery
Started redo application at
 Thread 1: logseq 24, block 2, scn 2621149392
Recovery of Online Redo Log: Thread 1 Group 3 Seq 24 Reading mem 0
  Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG
Completed redo application of 0.00MB
Completed crash recovery at
 Thread 1: logseq 24, block 3, scn 2621169394
 0 data blocks read, 0 data blocks written, 0 redo k-bytes read
Sat Dec 26 19:34:06 2020
Thread 1 advanced to log sequence 25 (thread open)
Thread 1 opened at log sequence 25
  Current log# 1 seq# 25 mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO01.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sat Dec 26 19:34:06 2020
SMON: enabling cache recovery
Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc  (incident=110636):
ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], []
Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc:
ORA-00704: 引导程序进程失败
ORA-00704: 引导程序进程失败
ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], []
Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_ora_5812.trc:
ORA-00704: 引导程序进程失败
ORA-00704: 引导程序进程失败
ORA-00600: 内部错误代码, 参数: [2662], [0], [2621169401], [0], [2621591939], [4194545], [], [], [], [], [], []
Error 704 happened during db open, shutting down database
USER (ospid: 5812): terminating the instance due to error 704
Instance terminated by USER, pid = 5812
ORA-1092 signalled during: alter database open...
opiodr aborting process unknown ospid (5812) as a result of ORA-1092
Sat Dec 26 19:34:10 2020
ORA-1092 : opitsk aborting process

对应的trace文件内容,主要在查询undo$表触发ORA-600 2662错误
20201226220104


通过修改scn,解决ORA-600 2662错误之后,数据库启动报ORA-600 4194

Sat Dec 26 20:13:28 2020
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
Trace dumping is performing id=[cdmp_20201226201328]
No Resource Manager plan active
Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_smon_8104.trc  (incident=114188):
ORA-00600: internal error code, arguments: [4194], [], [
Incident details in: e:\oracle\app\administrator\diag\rdbms\xff\xff\incident\incdir_114188\xff_smon_8104_i114188.trc
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x470E9BAC] [PC:0x6F21343, ___dyn_tls_init_callback()+111576860]
Sat Dec 26 20:13:29 2020
Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\cdump\xffcore.log
ORA-07445: caught exception [ACCESS_VIOLATION] at [___dyn_tls_init_callback()+111576860] [0x06F21343]
Doing block recovery for file 3 block 3121
Resuming block recovery (PMON) for file 3 block 3121
Block recovery from logseq 12, block 73 to scn 3221225727
Recovery of Online Redo Log: Thread 1 Group 3 Seq 12 Reading mem 0
  Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG
Block recovery stopped at EOT rba 12.75.16
Block recovery completed at rba 12.75.16, scn 0.3221225724
Doing block recovery for file 3 block 176
Resuming block recovery (PMON) for file 3 block 176
Block recovery from logseq 12, block 73 to scn 3221225721
Recovery of Online Redo Log: Thread 1 Group 3 Seq 12 Reading mem 0
  Mem# 0: E:\ORACLE\APP\ADMINISTRATOR\ORADATA\xff\REDO03.LOG
Block recovery completed at rba 12.73.16, scn 0.3221225722
Errors in file e:\oracle\app\administrator\diag\rdbms\xff\xff\trace\xff_smon_8104.trc:
ORA-01595: error freeing extent (3) of rollback segment (4))
ORA-00600: internal error code, arguments: [4194], [], [                                      
Trace dumping is performing id=[cdmp_20201226201331]
Sat Dec 26 20:13:31 2020
PMON (ospid: 5200): terminating the instance due to error 397
Instance terminated by PMON, pid = 5200

解决异常undo,数据库启动正常,导出数据

发表在 Oracle备份恢复 | 标签为 , | 评论关闭

记录oracle安装的两个小问题(INS-30060和弹出子窗口异常)

很久没有做安装的活,今天帮朋友处理安装的活遇到两个小问题,顺手记录下
1. 在linux 7.2中安装11.2.0.4在安装oui界面中弹出子窗口异常问题,如下图
20201225141012


问题原因是由于java兼容性的问题导致,不使用数据库软件自带程序,人工指定系统自带java即可
20201225140812

2. 报INS-30060错误
20201225141205

SEVERE: [FATAL] [INS-30060] Check for group existence failed.
CAUSE: Unexpected error occurred while trying to check for group existence.
ACTION: Refer to the logs or contact Oracle Support Services. 
Note for advanced users: Launch the installer by passing the following flag ''-ignoreInternalDriverError''..

出现这个问题的原因是由于开始创建了不合适的oracle用户,我删除了重建,导致uid不一致,从而使得CVU_11.2.0.3.0_oracle(及其内容)的权限不合适,从而出现该问题,删除掉/tmp下面相关目录解决

发表在 Oracle安装升级 | 一条评论

dblink会话引起library cache lock

有客户反馈,系统最近几天晚上都有卡顿
alert日志里面报如下错误
20201213180505


查看对应的trace文件
20201213180555

确定在收集统计信息的时候报ORA-04021错误.
查看这段时间ash报告
20201213180855

大量的library cache lock等待,而且引起等待的是类似语句,主要都是集中在一张表上,和收集统计信息报错的trace表匹配.
正好当天有对该表进行增加分区维护hang住
20201213181100

查询等待事件和阻塞情况

SQL> select distinct sid,a.BLOCKING_SESSION_STATUS,a.BLOCKING_INSTANCE,a.BLOCKING_SESSION
  2  ,event from gv$session a where sid=7399;

       SID BLOCKING_SE BLOCKING_INSTANCE BLOCKING_SESSION
---------- ----------- ----------------- ----------------
EVENT
----------------------------------------------------------------
      7399 VALID                       3             3593
library cache lock

SQL>  select a.INST_ID,a.sid,a.paddr,a.sql_id,a.event,a.MACHINE,a.PROGRAM 
   2 ,status from gv$session a where a.sid=3593;

   INST_ID        SID PADDR            SQL_ID
---------- ---------- ---------------- -------------
EVENT
----------------------------------------------------------------
MACHINE
----------------------------------------------------------------
PROGRAM                                          STATUS
------------------------------------------------ --------
         3       3593 0000001F91E80670 grxhz2vpmsrc6
SQL*Net message from dblink
WORKGROUP\XG
PlatformSyn.exe                                  ACTIVE

由于对应的sql_id 无法找到sql语句,不过根据等待事件基本上确认是调用一个dblink导致该问题,通过查询该回话,发现该回话一致处于active状态,但是一致无任何变化,实在可能处于僵死状态,对其进行kill之后,增加分区正常,收集统计信息正常.

发表在 Oracle | 标签为 | 评论关闭