标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2131 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 Oracle 恢复 ORACLE恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (103)
- 数据库 (1,701)
- DB2 (22)
- MySQL (74)
- Oracle (1,562)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (68)
- Oracle Bug (8)
- Oracle RAC (53)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (571)
- Oracle安装升级 (94)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (81)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- fio测试io,导致磁盘文件系统损坏故障恢复
- ORA-742 写丢失常见bug记录
- Oracle 19c 202501补丁(RUs+OJVM)
- 避免 19c 数据库性能问题需要考虑的事项 (Doc ID 3050476.1)
- Bug 21915719 Database hang or may fail to OPEN in 12c IBM AIX or HPUX Itanium – ORA-742, DEADLOCK or ORA-600 [kcrfrgv_nextlwn_scn] ORA-600 [krr_process_read_error_2]
- ORA-600 ktuPopDictI_1恢复
- impdp导入数据丢失sys授权问题分析
- impdp 创建index提示ORA-00942: table or view does not exist
- 数据泵导出 (expdp) 和导入 (impdp)工具性能降低分析参考
- 19c非归档数据库断电导致ORA-00742故障恢复
- Oracle 19c – 手动升级到 Non-CDB Oracle Database 19c 的完整核对清单
- sqlite数据库简单操作
- Oracle 暂定和恢复功能
- .pzpq扩展名勒索恢复
- Oracle read only用户—23ai新特性:只读用户
- 迁移awr快照数据到自定义表空间
- .hmallox加密mariadb/mysql数据库恢复
- 2025年首个故障恢复—ORA-600 kcbzib_kcrsds_1
- 第一例Oracle 21c恢复咨询
- ORA-15411: Failure groups in disk group DATA have different number of disks.
标签归档:ORA-600[6749]
ORA-600[6749] 发生在 SYSMAN.MGMT_METRICS_RAW表
数据库alert日志长时间出现ORA-00600[6749]错误
日志报错如下
Fri Jun 1 12:01:30 2012 Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_396.trc: ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], [] Fri Jun 1 12:01:34 2012 Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_396.trc: Fri Jun 1 13:01:06 2012 Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_13226.trc: ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], [] Fri Jun 1 13:01:10 2012 Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_13226.trc: Fri Jun 1 14:01:46 2012 Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_26691.trc: ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], [] Fri Jun 1 14:01:51 2012 Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_26691.trc: Fri Jun 1 15:01:21 2012 Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_7119.trc: ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], []
查看trace日志
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production With the Partitioning, OLAP and Data Mining options ORACLE_HOME = /opt/oracle/product/10/oraapp System name: Linux Node name: oracle2 Release: 2.6.18-92.el5 Version: #1 SMP Tue Apr 29 13:16:15 EDT 2008 Machine: x86_64 Instance name: oraapp Redo thread mounted by this instance: 1 Oracle process number: 44 Unix process pid: 26691, image: oracle@oracle2 (J000) *** ACTION NAME:(target 5) 2012-06-01 14:01:00.298 *** MODULE NAME:(Oracle Enterprise Manager.rollup) 2012-06-01 14:01:00.298 *** SERVICE NAME:(SYS$USERS) 2012-06-01 14:01:00.298 *** SESSION ID:(406.24103) 2012-06-01 14:01:00.298 Dumping current redo log in thread 1 DUMP OF REDO FROM FILE '/opt/oracle/oradata/oraapp/systable/redo03.log' Opcodes 11.* DBAs (file#, block#): (3, 13970) RBAs: 0x000000.00000000.0000 thru 0xffffffff.ffffffff.ffff SCNs: scn: 0x0000.00000000 thru scn: 0xffff.ffffffff Times: creation thru eternity FILE HEADER: Compatibility Vsn = 169869568=0xa200100 Db ID=1462349529=0x5729aed9, Db Name='ORAAPP' Activation ID=1462334681=0x572974d9 Control Seq=2614156=0x27e38c, File size=245760=0x3c000 File Number=3, Blksiz=512, File Type=2 LOG descrip:"Thread 0001, Seq# 0000003963, SCN 0x0000129fc9df-0xffffffffffff"
猜测ORA-600[6749]部分参数
SQL> select DBMS_UTILITY.data_block_address_file (12596882) "file#", 2 DBMS_UTILITY.data_block_address_block (12596882) "block#" 3 from dual; file# block# ---------- ---------- 3 13970
ORA-600[6749][a][b]{c}
这里证明c表示rdba
根据dba查询对象
SQL> select * from dba_extents where 13970 between block_id and block_id + blocks and file_id=3; OWNER SEGMENT_NAME SEGMENT_TYPE ---------- ------------------------------- ------------------- SYSMAN SYS_IOT_OVER_10448 TABLE SQL> select owner,iot_name from dba_tables where table_name = 'SYS_IOT_OVER_10448'; OWNER IOT_NAME ------------------------------ ------------------------------ SYSMAN MGMT_METRICS_RAW SQL> ANALYZE TABLE SYSMAN.MGMT_METRICS_RAW VALIDATE STRUCTURE CASCADE; Table analyzed.
按照常理ORA-00600[6749]错误是因为坏块或者表和索引数据不一致导致,通过ANALYZE可以检查出来.这里显示正常,那可能是其他原因导致,查询MOS果然发现是ORA-600 [6749] Occurring on SYSMAN.MGMT_METRICS_RAW [ID 467439.1]
解决方法
The following workaround may resolve the problem temporarily: 1. Ensure you have a good backup before proceeding. 2. Create a copy of the SYSMAN.MGMT_METRICS_RAW table: SQL> create table SYSMAN.MGMT_METRICS_RAW_COPY as select * from SYSMAN.MGMT_METRICS_RAW; 3. Truncate the table: SQL> truncate table SYSMAN.MGMT_METRICS_RAW; May need to disable trigger: "sysman.raw_metrics_after_insert" before proceeding. Re-enable after the insert. 4. Re-insert the rows: SQL> insert into SYSMAN.MGMT_METRICS_RAW select * from SYSMAN.MGMT_METRICS_RAW_COPY; SQL> commit; 5. Drop the copy table: SQL> drop table SYSMAN.MGMT_METRICS_RAW_COPY;