标签云
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)
- 操作系统 (91)
- 数据库 (1,419)
- DB2 (22)
- MySQL (58)
- Oracle (1,305)
- Data Guard (41)
- EXADATA (7)
- GoldenGate (20)
- ORA-xxxxx (150)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (12)
- ORACLE 21C (3)
- Oracle ASM (58)
- Oracle Bug (7)
- Oracle RAC (42)
- Oracle 安全 (6)
- Oracle 开发 (26)
- Oracle 监听 (26)
- Oracle备份恢复 (438)
- Oracle安装升级 (71)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (63)
- PostgreSQL (10)
- SQL Server (26)
- SQL Server恢复 (7)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (24)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (7)
-
最近发表
- O/S-Error: (OS 23) 数据错误(循环冗余检查) 数据库恢复
- 数据库open报ORA-00959: tablespace ‘UNDOTBS1′ does not exist分析
- ASM删除表空间恢复
- ORA-12518 ORA-27302: 错误发生在: ssthrddcr
- plsql 插入blob
- 分享运气超级好的一次drop tablespace 数据恢复
- segment header异常对象删除处理
- Oracle 数据库(RDBMS)的版本支持状态摘要 (Doc ID 1674382.1)
- [back2023@proxy.tg].eking勒索数据库恢复
- ORA-600 ktbsdp2 处理
- win文件系统损坏oracle恢复
- asm disk 磁盘部分被清空恢复
- File #xxx found in data dictionary but not in controlfile. Creating OFFLINE file ‘MISSING00XXX’ in the controlfile
- commit_wait和commit_logging设置不当导致数据库无法正常启动
- ORA-00742 ORA-00312故障恢复
- 110T oracle故障恢复
- ora-600 kcratr_scan_lastbwr
- .asistchinadecryption扩展名勒索数据库恢复
- .[decrypt20@firemail.cc].eking 数据库勒索恢复
- ocr磁盘组掉盘故障处理
友情链接
标签归档:kokasgi1
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,数据库正常启动,业务测试正常.

重命名sys用户引起数据库启动报ORA-01092 ORA-00600 kokasgi1错误
有客户和我反馈,他们为了防止有人使用sys用户进行登录,对sys用户进行了重命名,具体操作语句为:
update user$ set name='THISISSYS' where user#=0;
然后重启数据库发现数据库无法正常启动,报ORA-01092 ORA-00600 kokasgi1错误
[oracle@ecs-d75e-0618923 ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.1.0 Production on Fri Aug 7 14:40:28 2020 Copyright (c) 1982, 2009, Oracle. All rights reserved. Connected to an idle instance. SQL> startup mount; ORACLE instance started. Total System Global Area 6881345536 bytes Fixed Size 2214056 bytes Variable Size 4227860312 bytes Database Buffers 2617245696 bytes Redo Buffers 34025472 bytes Database mounted. SQL> alter database open; alter database open * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [kokasgi1], [], [], [], [], [], [],[], [], [], [], [] Process ID: 6269 Session ID: 530 Serial number: 3
以前写过处理过类似问题,参见:ORA-600 kokasgi1故障恢复,通过特殊处理,数据库open之后,对其user#=0的用户修改为SYS.
[oracle@ecs-d75e-0618923 ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.1.0 Production on Fri Aug 7 14:52:09 2020 Copyright (c) 1982, 2009, Oracle. All rights reserved. Connected to an idle instance. SQL> startup mount; ORACLE instance started. Total System Global Area 6881345536 bytes Fixed Size 2214056 bytes Variable Size 4227860312 bytes Database Buffers 2617245696 bytes Redo Buffers 34025472 bytes Database mounted. SQL> alter database open; Database altered. SQL> select name from user$ where user#=0; NAME ------------------------------ THISISSYS SQL> update user$ set name='SYS' where user#=0; 1 row updated. SQL> commit; Commit complete. SQL> shutdown abort; ORACLE instance shut down. SQL> startup; ORACLE instance started. Total System Global Area 6881345536 bytes Fixed Size 2214056 bytes Variable Size 4227860312 bytes Database Buffers 2617245696 bytes Redo Buffers 34025472 bytes Database mounted. Database altered.
至此恢复完成,再次sys是oracle内部默认的超级用户,系统很多调用在程序中写死的sys.,对其用户不能进行重命名操作.