• ORA-00600: internal error code, arguments


    通过rman将11g异机升级到19c时,应用归档时报错,报错如下

    RMAN>  recover database ;

    Starting recover at 2023-10-15 21:10:02
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=5776 device type=DISK

    starting media recovery
    media recovery failed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 10/15/2023 21:10:03
    ORA-00283: recovery session canceled due to errors
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover
     if needed start until cancel using backup controlfile
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [kcnibrUpdate], [0], [1], [], [], [], [], [], [], [], [], []

    RMAN>

    查找MOS文档:ORA-00600: internal error code, arguments: [kcnibrUpdate] report during Managed recovery (MRP) (Doc ID 2798541.1)
    根据文档操作如下

    orcl:/home/oracle@testdb> sqlplus / as sysdba

    SQL*Plus: Release 19.0.0.0.0 - Production on Sun Oct 15 21:11:02 2023
    Version 19.3.0.0.0

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


    Connected to:
    Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
    Version 19.3.0.0.0

    SQL> select blktype,count(*) from x$kccblkcor group by blktype;

       BLKTYPE   COUNT(*)
    ---------- ----------
             6          1

    SQL> Select * from v$controlfile_record_section where type='DATABASE BLOCK CORRUPTION' ;

    TYPE                         RECORD_SIZE RECORDS_TOTAL RECORDS_USED FIRST_INDEX
    ---------------------------- ----------- ------------- ------------ -----------
    LAST_INDEX LAST_RECID     CON_ID
    ---------- ---------- ----------
    DATABASE BLOCK CORRUPTION             80          8384            1           1
             1          1          0


    SQL> exec dbms_backup_restore.resetcfilesection(35)

    PL/SQL procedure successfully completed.

    SQL> Select * from v$controlfile_record_section where type='DATABASE BLOCK CORRUPTION' ;

    TYPE                         RECORD_SIZE RECORDS_TOTAL RECORDS_USED FIRST_INDEX
    ---------------------------- ----------- ------------- ------------ -----------
    LAST_INDEX LAST_RECID     CON_ID
    ---------- ---------- ----------
    DATABASE BLOCK CORRUPTION             80          8384            0           0
             0          0          0

    操作结束后继续rman操作recover database操作正常

    orcl:/home/oracle@testdb>rman target /

    Recovery Manager: Release 19.0.0.0.0 - Production on Sun Oct 15 21:11:44 2023
    Version 19.3.0.0.0

    Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.

    connected to target database: ORCL (DBID=768804399, not open)

                                                            

    RMAN> recover database;                     

    Starting recover at 2023-10-15 21:12:34
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=5776 device type=DISK

    starting media recovery

    archived log for thread 1 with sequence 14 is already on disk as file /u01/archivelog/1_14_1150285015.dbf
    archived log for thread 1 with sequence 15 is already on disk as file /u01/archivelog/1_15_1150285015.dbf
    archived log file name=/u01/archivelog/1_14_1150285015.dbf thread=1 sequence=14
    archived log file name=/u01/archivelog/1_15_1150285015.dbf thread=1 sequence=15
    unable to find archived log
    archived log thread=1 sequence=16
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 10/15/2023 21:12:36
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 16 and starting SCN of 87204796002

    RMAN>

  • 相关阅读:
    【uniapp】【微信小程序】wxml-to-canvas
    import type {} from ‘module‘ 具体解释
    多线程与高并发(二)—— Synchronized 加锁解锁流程
    公司内部网络架设悟空CRM客户管理系统 cpolar无需公网IP实现内网,映射端口外网访问
    利用OGG实现PostgreSQL实时同步
    Python邮件发送如何设置服务器?怎么配置?
    基于vue的移动端如何监听系统返回
    [操作系统笔记]两级页表
    PHP 函数
    arm处理器IO口驱动代码编写与测试(bcm2835)
  • 原文地址:https://blog.csdn.net/kevinyu998/article/details/133848026