标签云
asm mount asm 恢复 asm恢复 bbed bootstrap$ dul eking In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2662 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 sql加密恢复 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币 oracle 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (92)
- 数据库 (1,442)
- DB2 (22)
- MySQL (61)
- Oracle (1,322)
- Data Guard (41)
- EXADATA (7)
- GoldenGate (20)
- ORA-xxxxx (150)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (12)
- ORACLE 21C (3)
- Oracle ASM (60)
- Oracle Bug (7)
- Oracle RAC (42)
- Oracle 安全 (6)
- Oracle 开发 (26)
- Oracle 监听 (26)
- Oracle备份恢复 (451)
- Oracle安装升级 (71)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (64)
- PostgreSQL (13)
- PostgreSQL恢复 (3)
- SQL Server (26)
- SQL Server恢复 (7)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (29)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (12)
-
最近发表
- Oracle Recovery Tools修复空闲坏块
- Oracle Recovery Tools 解决ORA-600 3020故障
- 又一例ORA-600 kcratr_nab_less_than_odr
- oracle文件勒索恢复工具—.makop病毒恢复
- ORA-00702一键恢复工具
- 修改MySQL的ib_logfile大小和组数
- mysql ibd文件反删除恢复之后异常处理
- InnoDB: Cannot open table db/tab from the internal data dictionary of InnoDB though the .frm file for the table exists
- 存储重启,oracle无法启动故障处理
- 误删除分区oracle数据库恢复
- ORA-00333 ORA-01595 恢复
- 云主机快照之后Oracle无法正常启动处理
- ORA-600 2032故障处理
- Oracle Recovery Tools实战批量坏块修复
- ORA-15063: ASM discovered an insufficient number of disks for diskgroup 恢复
- 修改oracle scn小工具(patch scn)
- ORA-01110 ORA-17070 OSD-04006 故障恢复
- fdisk分区导致asm disk破坏数据库恢复
- ORA-600 kcvent_internal_02故障处理
- PostgreSQL恢复系列:pg_filedump基本使用
友情链接
标签归档:ORA-600 kokasgi1
2022年恢复第一单ORA-600 kokasgi1
2022年第一个数据库恢复请求,数据库启动报ORA-00600 kokasgi1错误
这种错误已经有过大量的恢复经历,一般是由于数据库启动之时无法查询到SYS用户导致.
ORA-600 kokasgi1故障恢复
win环境报ora-600 kokasgi1处理
再次遇到ORA-600 kokasgi1故障恢复
重命名sys用户引起数据库启动报ORA-01092 ORA-00600 kokasgi1错误
通过特殊手段启动数据库,然后修改SYS


win环境报ora-600 kokasgi1处理
又一例数据库启动报ORA-600 kokasgi1错误的恢复请求
SMON: enabling tx recovery Database Characterset is AL32UTF8 Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_3024.trc (incident=44691): ORA-00600: 内部错误代码, 参数: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Incident details in: e:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_44691\orcl_ora_3024_i44691.trc Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_3024.trc: ORA-00600: 内部错误代码, 参数: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_3024.trc: ORA-00600: 内部错误代码, 参数: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Error 600 happened during db open, shutting down database USER (ospid: 3024): terminating the instance due to error 600 Instance terminated by USER, pid = 3024 ORA-1092 signalled during: ALTER DATABASE OPEN... opiodr aborting process unknown ospid (3024) as a result of ORA-1092
通过咨询是由于根据某厂商给出来的建议对对oracle的user$的系统默认用户update等操作
通过分析现在库的用户情况

通过一系列处理之后绕过kokasgi1错误,open数据库报ORA-12432错误
SMON: enabling tx recovery Database Characterset is AL32UTF8 No Resource Manager plan active Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_3268.trc: ORA-12432: LBAC 错误: zllegbs:OCIStmtExecute Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_3268.trc: ORA-12432: LBAC 错误: zllegbs:OCIStmtExecute Error 12432 happened during db open, shutting down database USER (ospid: 3268): terminating the instance due to error 12432 Instance terminated by USER, pid = 3268 ORA-1092 signalled during: alter database open... opiodr aborting process unknown ospid (3268) as a result of ORA-1092
通过分析启动过程确认数据库在启动的时候访问lbacsys.lbac$pol表异常
PARSE ERROR #2:len=38 dep=1 uid=0 oct=3 lid=0 tim=37509085805630 err=942 select max(pol#) from lbacsys.lbac$pol ORA-12432: LBAC 错误: zllegnp:OCIStmtExecute ORA-12432: LBAC 错误: zllegnp:OCIStmtExecute *** 2021-07-28 18:31:15.593 USER (ospid: 3512): terminating the instance due to error 12432
经过修改文件让数据库不在访问该表,数据库启动正常
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 AL32UTF8 No Resource Manager plan active replication_dependency_tracking turned off (no async multimaster replication found) Starting background process QMNC Wed Jul 28 19:52:59 2021 QMNC started with pid=32, OS id=2840 Completed: alter database open
顺利导出数据,恢复完成
再次遇到ORA-600 kokasgi1故障恢复
接到一个朋友数据库无法启动,报错ORA-00600: 内部错误代码, 参数: [kokasgi1]错误:
Sun Nov 29 14:23:15 2020 Thread 1 advanced to log sequence 28572 (thread open) Thread 1 opened at log sequence 28572 Current log# 3 seq# 28572 mem# 0: /u01/app/oracle/oradata/xifenfei/redo03.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sun Nov 29 14:23:15 2020 SMON: enabling cache recovery [3505] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:135724 end:135754 diff:30 (0 seconds) 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 ORA-00600: 内部错误代码, 参数: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] 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 /u01/app/oracle/diag/rdbms/xifenfei/xifenfei/trace/xifenfei_ora_3505.trc: ORA-00600: 内部错误代码, 参数: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Errors in file /u01/app/oracle/diag/rdbms/xifenfei/xifenfei/trace/xifenfei_ora_3505.trc: ORA-00600: 内部错误代码, 参数: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Error 600 happened during db open, shutting down database USER (ospid: 3505): terminating the instance due to error 600 Instance terminated by USER, pid = 3505 ORA-1092 signalled during: alter database open... opiodr aborting process unknown ospid (3505) as a result of ORA-1092
对于这个错误,以前处理过一些类似故障,参考:
ORA-600 kokasgi1故障恢复
重命名sys用户引起数据库启动报ORA-01092 ORA-00600 kokasgi1错误
通过技术手段实现数据库open,查询user$信息
确认sys和system被分别被修改为sysa和systema,由于这个调整导致数据库无法正常启动.把sysa修改为sys,systema修改为system,数据库正常启动,业务测试正常.
