ORA-00742 ora-00600 [4193] [4194] [kdsgrp1] [13011]

最新推荐文章于 2024-07-25 08:45:00 发布
最新推荐文章于 2024-07-25 08:45:00 发布
阅读量709 收藏
点赞数
分类专栏： oracle
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/jycjyc/article/details/113135019
版权

存储故障导致问题：

Additional information: 3
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_q001_122961.trc  (incident=19370):
ORA-00600: internal error code, arguments: [4193], [pp/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbff
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_19370/dbtest_q001_122961_i19370.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory=[cdmp_20210125192405], requested by (instance=1, osid=122961 (Q001)), summary=[incident=19369].
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_mmon_111831.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_mmon_111831.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_ora_111939.trc  (incident=19345):
ORA-00600: internal error code, arguments: [4194], [ody "SYS.DBMS_STANDARD"
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_19345/dbtest_ora_111939_i19345.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Block recovery from logseq 1, block 60 to scn 15898926594263
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery completed at rba 1.64.16, scn 3701.3252631768
Block recovery from logseq 1, block 60 to scn 15898926594257
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery completed at rba 1.62.16, scn 3701.3252631765
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_mmon_111831.trc  (incident=19330):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_19330/dbtest_mmon_111831_i19330.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/dbtest/dbtest/incident/incdir_19370/dbtest_q001_122961_i19370.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Linux-x86_64 Error: 2: No such file or directory
Additional information: 7
ORA-00600: internal error code, arguments: [4193], [pp/oracle/proE
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_q001_122961.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00600: internal error code, arguments: [4193], [pp/oracle/proE
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_q001_122961.trc  (incident=19371):
ORA-25319: Queue table repartitioning aborted
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_19371/dbtest_q001_122961_i19371.trc
Dumping diagnostic data in directory=[cdmp_20210125192406], requested by (instance=1, osid=122961 (Q001)), summary=[incident=19370].
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_mmon_111831.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
error 25319 happened during Queue table repartitioning
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_ora_111939.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00600: internal error code, arguments: [4194], [ody "SYS.DBMSE
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_mmon_111831.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Block recovery from logseq 1, block 64 to scn 15898926594270
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery stopped at EOT rba 1.66.16
Block recovery completed at rba 1.66.16, scn 3701.3252631771
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_ora_111939.trc:
ORA-00308: cannot open archived log '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00600: internal error code, arguments: [4194], [ody "SYS.DBMSE
Block recovery from logseq 1, block 63 to scn 15898926594271
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery stopped at EOT rba 1.66.16
Block recovery completed at rba 1.66.16, scn 3701.3252631771
Block recovery from logseq 1, block 64 to scn 15898926594266
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery completed at rba 1.66.16, scn 3701.3252631771
Block recovery from logseq 1, block 63 to scn 15898926594263
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery completed at rba 1.64.16, scn 3701.3252631770
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xD591F70] [PC:0x9833C72, kgegpa()+40] [flags: 0x0, count: 1]
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xD591F70] [PC:0x98326E6, kgebse()+776] [flags: 0x2, count: 2]
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xD591F70] [PC:0x98326E6, kgebse()+776] [flags: 0x2, count: 2]
Dumping diagnostic data in directory=[cdmp_20210125192407], requested by (instance=1, osid=111831 (MMON)), summary=[incident=19330].
Mon Jan 25 19:24:09 2021
Block recovery from logseq 1, block 59 to scn 15898926594255
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery completed at rba 1.60.16, scn 3701.3252631761
Block recovery from logseq 1, block 59 to scn 15898926594272
Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
  Mem# 0: /oradata/dbtest/redo01_01.log
Block recovery completed at rba 1.67.16, scn 3701.3252631777


------

Mon Jan 25 19:31:08 2021
PMON started with pid=2, OS id=2957 
Mon Jan 25 19:31:08 2021
PSP0 started with pid=3, OS id=2959 
Mon Jan 25 19:31:09 2021
VKTM started with pid=4, OS id=2977 at elevated priority
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Mon Jan 25 19:31:09 2021
GEN0 started with pid=5, OS id=2981 
Mon Jan 25 19:31:09 2021
DIAG started with pid=6, OS id=2984 
Mon Jan 25 19:31:09 2021
DBRM started with pid=7, OS id=2989 
Mon Jan 25 19:31:09 2021
DIA0 started with pid=8, OS id=2991 
Mon Jan 25 19:31:09 2021
MMAN started with pid=9, OS id=2993 
Mon Jan 25 19:31:09 2021
DBW0 started with pid=10, OS id=2995 
Mon Jan 25 19:31:09 2021
DBW1 started with pid=11, OS id=2997 
Mon Jan 25 19:31:09 2021
LGWR started with pid=12, OS id=2999 
Mon Jan 25 19:31:09 2021
CKPT started with pid=13, OS id=3001 
Mon Jan 25 19:31:09 2021
SMON started with pid=14, OS id=3003 
Mon Jan 25 19:31:09 2021
RECO started with pid=15, OS id=3005 
Mon Jan 25 19:31:09 2021
MMON started with pid=16, OS id=3007 
Mon Jan 25 19:31:09 2021
MMNL started with pid=17, OS id=3009 
ORACLE_BASE from environment = /oracle/app/oracle
Mon Jan 25 19:31:09 2021
ALTER DATABASE   MOUNT
Successful mount of redo thread 1, with mount id 3007630333
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Mon Jan 25 19:31:13 2021
ALTER DATABASE OPEN
Thread 1 opened at log sequence 2
  Current log# 2 seq# 2 mem# 0: /oradata/dbtest/redo01_02.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
[3093] Successfully onlined Undo Tablespace 4.
Undo initialization finished serial:0 start:32696704 end:32696774 diff:70 (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
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Jan 25 19:31:14 2021
QMNC started with pid=19, OS id=3113 
Completed: ALTER DATABASE OPEN
Starting background process CJQ0
Mon Jan 25 19:31:14 2021
CJQ0 started with pid=23, OS id=3133 
Mon Jan 25 19:31:17 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
Mon Jan 25 19:31:18 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_3173.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_3173.trc  (incident=24230):
ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_24230/dbtest_j005_3173_i24230.trc
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Mon Jan 25 19:31:18 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j001_3165.trc:
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:31:19 2021
Dumping diagnostic data in directory=[cdmp_20210125193119], requested by (instance=1, osid=3171 (J004)), summary=[abnormal process termination].
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/dbtest/dbtest/trace/dbtest_j005_3173.trc:
ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
ORA-06512: 在 "testuser.CHANGE_TR_SDH_NE", line 51
ORA-04088: 触发器 'testuser.CHANGE_TR_SDH_NE' 执行过程中出错
ORA-06512: 在 "testuser.UPDATESDHNEROOMID", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:31:19 2021
Sweep [inc][24230]: completed
Sweep [inc2][24230]: completed
Mon Jan 25 19:31:19 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_3169.trc:
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j001_3165.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j001_3165.trc:
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Dumping diagnostic data in directory=[cdmp_20210125193120], requested by (instance=1, osid=3173 (J005)), summary=[incident=24230].
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_3169.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_3169.trc:
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Dumping diagnostic data in directory=[cdmp_20210125193121], requested by (instance=1, osid=3169 (J003)), summary=[abnormal process termination].
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_3169.trc:
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_3171.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Dumping diagnostic data in directory=[cdmp_20210125193122], requested by (instance=1, osid=3171 (J004)), summary=[abnormal process termination].
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_3169.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j001_3165.trc:
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_3169.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_3169.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j001_3165.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j001_3165.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j001_3165.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Dumping diagnostic data in directory=[cdmp_20210125193124], requested by (instance=1, osid=3165 (J001)), summary=[abnormal process termination].
Mon Jan 25 19:31:52 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_3163.trc:
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_3163.trc:
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_3163.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_3163.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_3163.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:31:59 2021
Starting background process SMCO
Mon Jan 25 19:31:59 2021
SMCO started with pid=31, OS id=4121 
Mon Jan 25 19:32:09 2021
Thread 1 cannot allocate new log, sequence 3
Private strand flush not complete
  Current log# 2 seq# 2 mem# 0: /oradata/dbtest/redo01_02.log
Thread 1 advanced to log sequence 3 (LGWR switch)
  Current log# 3 seq# 3 mem# 0: /oradata/dbtest/redo01_03.log
[oracle@gddbtest trace]$ tail -f alert_dbtest.log
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j002_3167.trc:
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
ORA-06512: 在 "testuser.SZW_TJ_FTTHWEEK", line 383
ORA-06512: 在 line 1
Mon Jan 25 19:33:25 2021
Dumping diagnostic data in directory=[cdmp_20210125193325], requested by (instance=1, osid=3167 (J002)), summary=[incident=24206].
Mon Jan 25 19:34:12 2021
Sweep [inc][24206]: completed
Sweep [inc2][24206]: completed
Mon Jan 25 19:34:51 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_7793.trc:
Mon Jan 25 19:34:52 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_7789.trc:
Mon Jan 25 19:34:52 2021
Dumping diagnostic data in directory=[cdmp_20210125193452], requested by (instance=1, osid=7793 (J007)), summary=[abnormal process termination].
Mon Jan 25 19:34:53 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_7791.trc:
Dumping diagnostic data in directory=[cdmp_20210125193453], requested by (instance=1, osid=7789 (J004)), summary=[abnormal process termination].
Mon Jan 25 19:34:54 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_7783.trc:
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_7783.trc:
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:34:54 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j002_7785.trc  (incident=24207):
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_24207/dbtest_j002_7785_i24207.trc
Dumping diagnostic data in directory=[cdmp_20210125193455], requested by (instance=1, osid=7791 (J005)), summary=[abnormal process termination].
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/dbtest/dbtest/trace/dbtest_j002_7785.trc:
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
ORA-06512: 在 "testuser.SZW_TJ_FTTHWEEK", line 383
ORA-06512: 在 line 1
Dumping diagnostic data in directory=[cdmp_20210125193456], requested by (instance=1, osid=7785 (J002)), summary=[incident=24207].
Mon Jan 25 19:35:00 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j008_7795.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j008_7795.trc  (incident=24279):
ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_24279/dbtest_j008_7795_i24279.trc
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_7793.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_7793.trc:
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_7793.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/dbtest/dbtest/trace/dbtest_j008_7795.trc:
ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
ORA-06512: 在 "testuser.CHANGE_TR_SDH_NE", line 51
ORA-04088: 触发器 'testuser.CHANGE_TR_SDH_NE' 执行过程中出错
ORA-06512: 在 "testuser.UPDATESDHNEROOMID", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:35:01 2021
Sweep [inc][24279]: completed
Sweep [inc][24207]: completed
Sweep [inc2][24279]: completed
Sweep [inc2][24207]: completed
Mon Jan 25 19:35:05 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_7789.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_7789.trc:
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_7789.trc:
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:35:07 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_7791.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_7791.trc:
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_7791.trc:
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:35:07 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_7783.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_7783.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:35:10 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_7793.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_7793.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:35:15 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_7789.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_7789.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_7791.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_7791.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:36:57 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_10577.trc:
Mon Jan 25 19:36:58 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_10573.trc:
Mon Jan 25 19:36:58 2021
Dumping diagnostic data in directory=[cdmp_20210125193658], requested by (instance=1, osid=10577 (J007)), summary=[abnormal process termination].
Mon Jan 25 19:36:59 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_10571.trc:
Dumping diagnostic data in directory=[cdmp_20210125193659], requested by (instance=1, osid=10573 (J004)), summary=[abnormal process termination].
Mon Jan 25 19:36:59 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j002_10393.trc  (incident=24208):
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_24208/dbtest_j002_10393_i24208.trc
Dumping diagnostic data in directory=[cdmp_20210125193700], requested by (instance=1, osid=10571 (J003)), summary=[abnormal process termination].
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/dbtest/dbtest/trace/dbtest_j002_10393.trc:
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
ORA-06512: 在 "testuser.SZW_TJ_FTTHWEEK", line 383
ORA-06512: 在 line 1
Mon Jan 25 19:37:03 2021
Sweep [inc][24208]: completed
Sweep [inc2][24208]: completed
Mon Jan 25 19:37:12 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_10577.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_10577.trc:
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_10577.trc:
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:37:12 2021
Thread 1 cannot allocate new log, sequence 4
Private strand flush not complete
  Current log# 3 seq# 3 mem# 0: /oradata/dbtest/redo01_03.log
Mon Jan 25 19:37:13 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_10571.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_10571.trc:
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_10571.trc:
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:37:13 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_10575.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_10575.trc  (incident=24246):
ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/dbtest/dbtest/incident/incdir_24246/dbtest_j005_10575_i24246.trc
Mon Jan 25 19:37:14 2021
Dumping diagnostic data in directory=[cdmp_20210125193714], requested by (instance=1, osid=10577 (J007)), summary=[abnormal process termination].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Jan 25 19:37:14 2021
Sweep [inc][24246]: completed
Sweep [inc2][24246]: completed
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j005_10575.trc:
ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
ORA-06512: 在 "testuser.CHANGE_TR_SDH_NE", line 51
ORA-04088: 触发器 'testuser.CHANGE_TR_SDH_NE' 执行过程中出错
ORA-06512: 在 "testuser.UPDATESDHNEROOMID", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:37:14 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_10573.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_10573.trc:
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_10573.trc:
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Dumping diagnostic data in directory=[cdmp_20210125193715], requested by (instance=1, osid=10575 (J005)), summary=[incident=24246].
Thread 1 advanced to log sequence 4 (LGWR switch)
  Current log# 4 seq# 4 mem# 0: /oradata/dbtest/redo01_04.log
Mon Jan 25 19:37:19 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_10389.trc:
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:37:25 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_10577.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j007_10577.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 241 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:37:25 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_10571.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j003_10571.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 215979 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Mon Jan 25 19:37:26 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_10573.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j004_10573.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 443069 出错
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_10389.trc:
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Mon Jan 25 19:37:36 2021
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_10389.trc:
ORA-00308: 无法打开归档日志 '/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1_1001262830.dbf'
ORA-27037: 无法获得文件状态
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
Errors in file /oracle/app/oracle/diag/rdbms/dbtest/dbtest/trace/dbtest_j000_10389.trc:
ORA-00604: 递归 SQL 级别 1 出现错误
ORA-08102: 未找到索引关键字, 对象号 290, 文件 1, 块 2033 (2)
ORA-12012: 自动执行作业 390351 出错
ORA-00001: 违反唯一约束条件 (testuser.IDX_JRAGE_ID)
ORA-06512: 在 "testuser.INSERT_VILLAGE_INFO", line 6
ORA-06512: 在 line 1
dateMon Jan 25 19:38:40 2021
drop tablespace undotbs1 including contents and datafiles
Deleted file /oradata/dbtest/undotbs1.265.946553091
Completed: drop tablespace undotbs1 including contents and datafiles

对于13013错误而言，随后的6个参数含义如下：

Arg [a] Passcount

Arg [b] Data Object number

Arg [c] Tablespace Relative DBA of block containing the row to be updated

Arg [d] Row Slot number

Arg [e] Relative DBA of block being updated (should be same as [c])

 

处理过程：

[oracle@dbtest ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Mon Jan 25 19:16:44 2021

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

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 6413680640 bytes
Fixed Size                  2265224 bytes
Variable Size            1157631864 bytes
Database Buffers         5234491392 bytes
Redo Buffers               19292160 bytes
Database mounted.
ORA-00742: Log read detects lost write in thread %d sequence %d block %d
ORA-00312: online log 4 thread 1: '/oradata/dbtest/redo01_04.log'


SQL> !oerr ora 742
00742, 00000, "Log read detects lost write in thread %d sequence %d block %d"
// *Cause:  Either a write issued by Oracle was lost by the underlying 
//          operating system or storage system or an Oracle internal error 
//          occurred.
// *Action: The trace file shows the lost write location. Dump the problematic
//          log file to see whether it is a real lost write. Contact Oracle
//          Support Services.

SQL> !ll /oradata/dbtest/redo0*
/bin/bash: ll: command not found

SQL> !ls -l /oradata/dbtest/redo0*
-rw-r----- 1 oracle oinstall 524288512 120 17:03 /oradata/dbtest/redo01_01.log
-rw-r----- 1 oracle oinstall 524288512 121 04:00 /oradata/dbtest/redo01_02.log
-rw-r----- 1 oracle oinstall 524288512 121 04:00 /oradata/dbtest/redo01_03.log
-rw-r----- 1 oracle oinstall 524288512 121 17:04 /oradata/dbtest/redo01_04.log
-rw-r----- 1 oracle oinstall 524288512 120 04:00 /oradata/dbtest/redo01_05.log
-rw-r----- 1 oracle oinstall 524288512 226 2019 /oradata/dbtest/redo02_01.log
-rw-r----- 1 oracle oinstall 524288512 226 2019 /oradata/dbtest/redo02_02.log
-rw-r----- 1 oracle oinstall 524288512 226 2019 /oradata/dbtest/redo02_03.log
-rw-r----- 1 oracle oinstall 524288512 226 2019 /oradata/dbtest/redo02_04.log
-rw-r----- 1 oracle oinstall 524288512 226 2019 /oradata/dbtest/redo02_05.log

SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00742: Log read detects lost write in thread %d sequence %d block %d
ORA-00312: online log 4 thread 1: '/oradata/dbtest/redo01_04.log'


SQL> select checkpoint_change# from v$database;   

CHECKPOINT_CHANGE#
------------------
        1.5899E+13

SQL> col checkpoint_change# for 9999999999999999999999999999
SQL> select checkpoint_change# from v$database;   

           CHECKPOINT_CHANGE#
-----------------------------
               15898926555157

SQL> select checkpoint_change# from v$datafile;     

           CHECKPOINT_CHANGE#
-----------------------------
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157

           CHECKPOINT_CHANGE#
-----------------------------
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157

           CHECKPOINT_CHANGE#
-----------------------------
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157
               15898926555157

30 rows selected.

SQL> select checkpoint_change# from v$datafile_header;  

           CHECKPOINT_CHANGE#
-----------------------------
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049

           CHECKPOINT_CHANGE#
-----------------------------
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049

           CHECKPOINT_CHANGE#
-----------------------------
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049
               15898926565049

30 rows selected.

SQL> recover database using backup controlfile until cancel;
ORA-00279: change 15898926565049 generated at 01/21/2021 04:00:29 needed for
thread 1
ORA-00289: suggestion :
/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1704_1001262830.dbf
ORA-00280: change 15898926565049 for thread 1 is in sequence #1704


Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/dbtest/system.263.946553089'


ORA-01112: media recovery not started


SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/dbtest/system.263.946553089'


SQL> select * from v$Log;
SQL> set line 132
SQL> set wrap off      
SQL> r
  1* select * from v$Log
truncating (as requested) before column NEXT_CHANGE#


    GROUP#    THREAD#  SEQUENCE#      BYTES  BLOCKSIZE    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME      NEXT_TIME
---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ------------------- -----------
         1          1       1701  524288000        512          1 NO  INACTIVE            1.5899E+13 2021-01-20 04:00:09 2021-01-20
         2          1       1702  524288000        512          1 NO  INACTIVE            1.5899E+13 2021-01-20 17:03:28 2021-01-21
         5          1       1700  524288000        512          1 NO  INACTIVE            1.5899E+13 2021-01-20 02:01:19 2021-01-20
         4          1       1704  524288000        512          1 NO  CURRENT             1.5899E+13 2021-01-21 04:00:29
         3          1       1703  524288000        512          1 NO  INACTIVE            1.5899E+13 2021-01-21 04:00:08 2021-01-21

SQL> select * from v$Logfile;
rows will be truncated


    GROUP# STATUS  TYPE    MEMBER
---------- ------- ------- ---------------------------------------------------------------------------------------------------------
         1         ONLINE  /oradata/dbtest/redo01_01.log
         2         ONLINE  /oradata/dbtest/redo01_02.log
         3         ONLINE  /oradata/dbtest/redo01_03.log
         4         ONLINE  /oradata/dbtest/redo01_04.log
         5         ONLINE  /oradata/dbtest/redo01_05.log

SQL> recover database using backup controlfile until cancel;
ORA-00279: change 15898926565049 generated at 01/21/2021 04:00:29 needed for thread 1
ORA-00289: suggestion : /oracle/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_1704_1001262830.dbf
ORA-00280: change 15898926565049 for thread 1 is in sequence #1704


Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oradata/dbtest/redo01_04.log
Log applied.
Media recovery complete.
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 111939
Session ID: 62 Serial number: 3


SQL> startup nomount
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> conn /as sysdba
Connected.
SQL> startup nomount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> show parameter name;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
cell_offloadgroup_name               string
db_file_name_convert                 string
db_name                              string      dbtest
db_unique_name                       string      dbtest
global_names                         boolean     FALSE
instance_name                        string      dbtest
lock_name_space                      string
log_file_name_convert                string
processor_group_name                 string
service_names                        string      dbtest
SQL> show parameter undo;       

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
_gc_undo_affinity                    boolean     FALSE
_undo_autotune                       boolean     FALSE
undo_management                      string      AUTO
undo_retention                       integer     21600
undo_tablespace                      string      UNDOTBS1
SQL> create undo tablespace undotbs2 datafile '/oradata/dbtest/undo2_01.dbf' size 100M autoextend on;
create undo tablespace undotbs2 datafile '/oradata/dbtest/undo2_01.dbf' size 100M autoextend on
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [4193], [ody "SYS.DBMSE


SQL> alter system set undo_tablespace='SYSTEM';
alter system set undo_tablespace='SYSTEM'
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-30012: undo tablespace 'SYSTEM' does not exist or of wrong type


SQL> alter system set undo_tablespace='SYSTEM' scope=spfile;

System altered.

SQL> alter system set undo_management='MANUAL' scope=spfile;

System altered.

SQL> shutdown immediate
ORA-03135: connection lost contact
SQL> conn /as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.

Total System Global Area 6413680640 bytes
Fixed Size                  2265224 bytes
Variable Size            1157631864 bytes
Database Buffers         5234491392 bytes
Redo Buffers               19292160 bytes
Database mounted.
Database opened.
SQL> show parameter undo;     

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
_gc_undo_affinity                    boolean     FALSE
_undo_autotune                       boolean     FALSE
undo_management                      string      MANUAL
undo_retention                       integer     21600
undo_tablespace                      string      SYSTEM
SQL> create undo tablespace undotbs2 datafile '/oradata/dbtest/undo2_01.dbf' size 100M autoextend on;

Tablespace created.

SQL> alter system set undo_tablespace='UNDOTBS2' scope=spfile;

System altered.

SQL> alter system set undo_management='AUTO' scope=spfile;

System altered.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 6413680640 bytes
Fixed Size                  2265224 bytes
Variable Size            1157631864 bytes
Database Buffers         5234491392 bytes
Redo Buffers               19292160 bytes
Database mounted.
Database opened.
SQL> !oerr ora  8102     
08102, 00000, "index key not found, obj# %s, file %s, block %s (%s)"
// *Cause:  Internal error: possible inconsistency in index
// *Action:  Send trace file to your customer support representative, along
//           with information on reproducing the error

SQL> Select owner, segment_name, segment_type, partition_name,tablespace_name
  2  From dba_extents
  3  Where relative_fno = 1
  4  And 2033 between block_id and (block_id+blocks-1);


OWNER                          SEGMENT_NAME                                                                      SEGMENT_TYPE
------------------------------ --------------------------------------------------------------------------------- ------------------
SYS                            I_JOB_NEXT                                                                        INDEX

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

OBJECT_NAME                                                                                                                      OBJ
-------------------------------------------------------------------------------------------------------------------------------- ---
I_JOB_NEXT                                                                                                                       IND

SQL> col OBJECT_NAME for a20
SQL> r
  1* select object_name,object_type from dba_objects where object_id=290

OBJECT_NAME          OBJECT_TYPE
-------------------- -------------------
I_JOB_NEXT           INDEX

SQL> drop index i_job_next;
drop index i_job_next
           *
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired


SQL> /
drop index i_job_next
           *
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired


SQL> /
drop index i_job_next
           *
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired


SQL> /
drop index i_job_next
           *
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired


SQL> set time on
19:37:38 SQL> /

Index dropped.

19:37:40 SQL> create index i_job_next on job$ (next_date);

Index created.

19:37:49 SQL> select object_name,object_type from dba_objects where object_id=290;

no rows selected

19:37:54 SQL> drop tablespace undotbs1 including contents and datafiles;

Tablespace dropped.

19:38:41 SQL> 

 

Mon Jan 25 19:59:00 2021
Errors in file /oracle/app/oracle/diag/rdbms/zydbtest/zydbtest/trace/zydbtest_j000_39154.trc  (incident=26606):
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/zydbtest/zydbtest/incident/incdir_26606/zydbtest_j000_39154_i26606.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/zydbtest/zydbtest/trace/zydbtest_j000_39154.trc:
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
ORA-06512: 在 "GISTAR.SZW_TJ_FTTHWEEK", line 383
ORA-06512: 在 line 1
Mon Jan 25 19:59:02 2021
Dumping diagnostic data in directory=[cdmp_20210125195902], requested by (instance=1, osid=39154 (J000)), summary=[incident=26606].
Mon Jan 25 19:59:03 2021
Sweep [inc][26606]: completed
Sweep [inc2][26606]: completed
Mon Jan 25 20:00:50 2021
Errors in file /oracle/app/oracle/diag/rdbms/zydbtest/zydbtest/trace/zydbtest_j000_41788.trc  (incident=26607):
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/zydbtest/zydbtest/incident/incdir_26607/zydbtest_j000_41788_i26607.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/zydbtest/zydbtest/trace/zydbtest_j000_41788.trc:
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
ORA-06512: 在 "GISTAR.SZW_TJ_FTTHWEEK", line 383
ORA-06512: 在 line 1
Mon Jan 25 20:00:52 2021
Dumping diagnostic data in directory=[cdmp_20210125200052], requested by (instance=1, osid=41788 (J000)), summary=[incident=26607].
Mon Jan 25 20:00:54 2021
Sweep [inc][26607]: completed
Sweep [inc2][26607]: completed
dateMon Jan 25 20:02:36 2021
Errors in file /oracle/app/oracle/diag/rdbms/zydbtest/zydbtest/trace/zydbtest_j000_44250.trc  (incident=26608):
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
Incident details in: /oracle/app/oracle/diag/rdbms/zydbtest/zydbtest/incident/incdir_26608/zydbtest_j000_44250_i26608.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/zydbtest/zydbtest/trace/zydbtest_j000_44250.trc:
ORA-00600: 内部错误代码, 参数: [13011], [116253], [47737944], [0], [47737944], [17], [], [], [], [], [], []
ORA-06512: 在 "GISTAR.SZW_TJ_FTTHWEEK", line 383
ORA-06512: 在 line 1
Mon Jan 25 20:02:38 2021
Dumping diagnostic data in directory=[cdmp_20210125200238], requested by (instance=1, osid=44250 (J000)), summary=[incident=26608].
Mon Jan 25 20:02:39 2021
Sweep [inc][26608]: completed
Sweep [inc2][26608]: completed
Mon Jan 25 20:03:59 2021
The value (167) of MAXTRANS parameter ignored.
The value (167) of MAXTRANS parameter ignored.

处理做法：https://blog.csdn.net/weixin_34324081/article/details/86001693

19:58:59 SQL> select object_name,object_type,owner from dba_objects where object_id=116253;

OBJECT_NAME          OBJECT_TYPE         OWNER
-------------------- ------------------- ------------------------------
JR_FTTH_JOIN_WEEK    TABLE               TESTUSER

19:59:35 SQL> select index_name from dba_indexes where owner='TESTUSER' and table_name='JR_FTTH_JOIN_WEEK';

INDEX_NAME
------------------------------
PKIY_WHER_1
IDX_MAINFG_PI

20:00:20 SQL> set wrap on
20:02:47 SQL> set serveroutput on
20:02:54 SQL> set long 999999
20:02:57 SQL> select dbms_metadata.get_ddl('INDEX', 'PKIY_WHER_1', 'TESTUSER') from dual;

DBMS_METADATA.GET_DDL('INDEX','PKIY_WHER_1','TESTUSER')
--------------------------------------------------------------------------------

  CREATE UNIQUE INDEX "TESTUSER"."PKIY_WHER_1" ON "TESTUSER"."JR_FTTH_JOIN_WEEK" ("ID")
  PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
  BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
  TABLESPACE "USERS"


20:03:04 SQL> select dbms_metadata.get_ddl('INDEX', 'IDX_MAINFG_PI', 'TESTUSER') from dual;

DBMS_METADATA.GET_DDL('INDEX','IDX_MAINFG_PI','TESTUSER')
--------------------------------------------------------------------------------

  CREATE INDEX "TESTUSER"."IDX_MAINFG_PI" ON "TESTUSER"."JR_FTTH_JOIN_WEEK" ("MAINTENACE_CODE")
  PCTFREE 10 INITRANS 2 MAXTRANS 167 COMPUTE STATISTICS
  STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
  BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
  TABLESPACE "USERS"


20:03:10 SQL> drop index "TESTUSER"."PKIY_WHER_1";
drop index "TESTUSER"."PKIY_WHER_1"
                    *
ERROR at line 1:
ORA-02429: cannot drop index used for enforcement of unique/primary key


20:03:21 SQL> !oerr ora 02429
02429, 00000, "cannot drop index used for enforcement of unique/primary key"
// *Cause: user attempted to drop an index that is being used as the 
//         enforcement mechanism for unique or primary key.
// *Action: drop the constraint instead of the index.

20:03:32 SQL> drop index "TESTUSER"."IDX_MAINFG_PI";

Index dropped.

20:03:48 SQL>   CREATE INDEX "TESTUSER"."IDX_MAINFG_PI" ON "TESTUSER"."JR_FTTH_JOIN_WEEK" ("MAINTENACE_CODE")
20:03:57   2    PCTFREE 10 INITRANS 2 MAXTRANS 167 COMPUTE STATISTICS
20:03:57   3    STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
20:03:57   4    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
20:03:57   5    BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
20:03:57   6    TABLESPACE "USERS";

Index created.

20:03:59 SQL>                                                                      
20:06:27 SQL> 
20:06:27 SQL> alter table TESTUSER.JR_FTTH_JOIN_WEEK drop constraint TESTUSER.PKIY_WHER_1;
alter table TESTUSER.JR_FTTH_JOIN_WEEK drop constraint TESTUSER.PKIY_WHER_1
                                                           *
ERROR at line 1:
ORA-01735: invalid ALTER TABLE option


20:06:29 SQL> alter table TESTUSER.JR_FTTH_JOIN_WEEK drop constraint PKIY_WHER_1;

Table altered.

20:06:38 SQL> drop index "TESTUSER"."PKIY_WHER_1";

Index dropped.

用到的脚本参考：删除重复记录
Select ID from TESTUSER.JR_FTTH_JOIN_WEEK 
Group by ID
Having count(ID)>1;


DELETE FROM TESTUSER.JR_FTTH_JOIN_WEEK A WHERE (A.ID) IN (SELECT ID FROM TESTUSER.JR_FTTH_JOIN_WEEK GROUP BY ID HAVING COUNT(*) > 1) AND ROWID NOT IN (SELECT MIN(ROWID) FROM TESTUSER.JR_FTTH_JOIN_WEEK GROUP BY ID HAVING COUNT(*)>1);
commit;

ORA-00742:oracle数据库服务器断电后文件丢失恢复（非归档模式下noarchive）
qq_41141058的博客
09-11 6387
错误提示： SQL> startup ORACLE instance started. Total System Global Area 5368709120 bytes Fixed Size 8632016 bytes Variable Size 2281703728 bytes Database Buffers 3070230528 bytes Redo Buffers...
ORA-00742:oracle数据库服务器断电后重启控制文件丢失恢复
weixin_43838240的博客
09-09 922
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL ORA-00279: 更改 67037966 (在 12/31/2017 05:00:12 生成) 对于线程 1 是必需的 ORA-00289: 建议: E:\APP\ADMINISTRATOR\VIRTUAL\PRODUCT\12.2.0\D...
ORA-00742 ORA-00312 恢复---惜分飞
04-15 1118
有客户反馈,断电之后数据库启动报ORA-00742和ORA-00312,无法正常open。因为recover已经成功,但是依旧报ORA-742错误,尝试查询scn相关信息。后面比较不幸，数据库报ORA-600 4194错误导致数据库异常。基于这样的情况,我们判断数据库直接open成功。我们远程上去尝试open库结果也报同样错误。报错比较明显,对undo进行处理即可.
ORA-00742: Log read detects lost write in thread 1 sequence 32 block 15358
雅冰石的专栏
08-25 1031
原文链接：https://blog.csdn.net/qq_41141058/article/details/100732596。版权声明：本文为CSDN博主「佐云」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。这里是/u01/app/oracle/oradata/zydb/redo03.log。② 执行数据库起不来时报错提示的重做日志文件。
ORA-00742: 日志读取在线程 %d 序列 %d 块 %d 中检测到写入丢失情况----惜分飞
11-26 1138
由于主机异常断电，导致oracle数据库无法正常启动,数据库启动报错ORA-07445 kdxlin,ORA-01172,ORA-00312,ORA-00742等错误
错误诊断：索引数据错误导致ORA-00600 [kdsgrp1]处理
Enmotech的博客
09-17 857
墨墨导读：客户反应一套数据库alert日志报ORA-00600 [kdsgrp1]，需要定位问题原因。问题分析alert日志报错如下：Errors in file /home/app/o...
记一次报错ORA-00600: internal error code, arguments: [kdsgrp1]，解决索引坏块问题！
zhongxiayeyu的博客
10-28 6688
记一次报错ORA-00600: internal error code, arguments: [kdsgrp1]，解决索引坏块问题！ 【原创】作者：仲夏夜雨 数据库版本：Oracle 10.2.0.5，RAC集群。 同事找我问数据库问题，客户那边网站点击按添加钮显示error如下图。 现象一： Java程序报错ORA-00600: internal error code, arguments:...
ORA-00600 内部错误代码, 参数 [kdsgrp1]
07-11
ORA-00600是Oracle数据库中的内部错误代码，表示遇到了一个未知的或无法处理的内部错误。这种错误通常需要Oracle支持团队的介入来进行故障排查和修复。参数[kdsgrp1]是具体错误的参数，它指示了错误发生的具体细节。...
ORA-00600: 内部错误代码, 参数: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
Mikya_清风的博客
09-17 3336
问题描述： 数据库巡检发现alert日志报错： Mon Sep 16 23:18:56 2019 LNS: Standby redo logfile selected for thread 1 sequence 258557 for destination LOG_ARCHIVE_DEST_2 Mon Sep 16 23:19:13 2019 Archived Log entry 51...
在11.2.0.4环境中频繁出现ora-8103的问题、dbsnmp执行dbms_job权限不够报错
最新发布
weixin_tank88921的博客
07-25 1321
MOS中的解释为，为了安全起见，之前授权给public的execute on dbms_job权限被收回，导致dbsnmp执行dbms_job权限不够报错。解决措施注： 此job为每周日执行。附：还有一个报错信息很像的MOS中解释的原因不同，如果你的数据库是通过模板创建或者使用克隆，表DBSNMP.BSLN_BASELINES中的已存在数据会与新插入的数据冲突。可以通过重新创建DBSNMP这个用户。
ORA-00600: internal error code, arguments: [4193]问题解决
weixin_30609287的博客
09-08 792
操作环境 SuSE+Oracle11gR2 问题现象 单板宕机自动重启后，ORACLE运行不正常，主要表现如下： 1、执行shutdown immedate停止数据库时，提示ORA-00600: internal error code, arguments: [4193]，[]，[] 2、压测性能时，oracle总是无缘无故关闭 问题分析 发现问题后查看告警日志&...
ORA-00742:Log read detects lost writein thread 1 sequence 1202 block 137840
m0_38048955的博客
03-23 1865
问题背景： 客户数据库环境遭遇断电宕机，启动数据库失败，协助查看。 报错如下： 1 Total System Global Area 6442450944 bytes 2 Fixed Size 8807168 bytes 3 Variable Size 1375735040 bytes 4 Database Buffers 5049942016 bytes 5 Redo Buffers 7966720 bytes 6 Database mounted...
拨云见日：揭开ORA-00600:[4193]的神秘面纱
Enmotech的博客
08-20 825
墨墨导读：从 Oracle 9i 开始，Oracle引入了一种管理前镜像的新方式。之前的版本是通过 RollBack Segment 进行的，或称为 manual undo(手动 und...
ORA-00742 ORA-00312特殊恢复
热门推荐
数据之路-忆梦前程
09-03 1万+
ERROR： ORA-00742: 日志读取在线程 1 序列 20 块 40649 中检测到写入丢失情况 ORA-00312: 联机日志 2 线程 1: '/oracle/oradata/SEM/redo02.log' SQL> RECOVER DATABASE UNTIL CANCEL;                 //尝试recover之 ORA-01547: 警告: RECO
ORA-00742 DG备库日志文件损坏导致MRP线程中断
Sebastien23的博客
07-09 754
如果上面重启MRP进程后还是一直没有恢复正常同步，很可能是由于主库和其他备库的归档日志被清理了，导致获取不到部分归档日志，这种情况下还需要额外进行增量备份恢复。上面这种情况就是归档日志中有部分序列从其他所有库都获取不到了，需要做一次增量备份恢复。
Oracle 启动故障案例之--ORA-600 [4193]错误
天涯客*Blog
12-14 7704
Oracle 启动故障案例之--ORA-600 [4193]错误 操作系统：Oracle Linux 5 数据库：    Oracle 11gR2（11.2.0.3.0） 一、故障现象： 1、在做了redo log当前日志组被破坏恢复的测试后 2、启动数据库后出现ORA-600 【4193】的错误 3、数据库被强制关闭 查看告警日志： [oracle@ocm1 ~]$ ta
Linux虚拟机意外断电导致Oracle启动失败(ORA-00742和ORA-00312)
山间清泉
06-24 1620
ORA-00742和ORA-00312
ORA-00600_内部错误代码_参数 [4193]Error 600 in redo application callback
wolihaito的博客
02-07 1413
做冷备恢复时 报ORA-00600错误： ORA-00600: 内部错误代码, 参数: [4193][ Error 600 in redo application callback （trace 部分信息如下） *** 2020-02-07 20:02:35.755 Incident 6165 created, dump file: E:\APP\WOLIHAITO\diag\rdbms\orc...
ora-00742 ora-00312
03-16
ORA-00742和ORA-00312都是Oracle数据库的错误代码。 ORA-00742表示数据库无法打开或创建控制文件。这可能是由于控制文件已经存在但无法访问，或者控制文件不存在但无法创建。 ORA-00312表示数据库无法读取或写入...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值