19c库启动报ORA-600 kcbzib_kcrsds_1---惜分飞

2024-08-26 15:04

本文主要是介绍19c库启动报ORA-600 kcbzib_kcrsds_1---惜分飞,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

一套19c的库由于某种情况,发现异常,当时的技术使用隐含参数强制拉库,导致数据库启动报ORA-00704 ORA-600 kcbzib_kcrsds_1错误

2024-08-24T06:11:25.494304+08:00

ALTER DATABASE OPEN

2024-08-24T06:11:25.494370+08:00

TMI: adbdrv open database BEGIN 2024-08-24 06:11:25.494324

Smart fusion block transfer is disabled:

  instance mounted in exclusive mode.

2024-08-24T06:11:25.515306+08:00

Beginning crash recovery of 1 threads

 parallel recovery started with 7 processes

 Thread 1: Recovery starting at checkpoint rba (logseq 2 block 3), scn 286550073

2024-08-24T06:11:25.567011+08:00

Started redo scan

2024-08-24T06:11:25.587170+08:00

Completed redo scan

 read 0 KB redo, 0 data blocks need recovery

2024-08-24T06:11:25.595192+08:00

Started redo application at

 Thread 1: logseq 2, block 3, offset 0, scn 0x0000000011146839

2024-08-24T06:11:25.595552+08:00

Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0

  Mem# 0: /dbf/RLZY/redo02.log

2024-08-24T06:11:25.595712+08:00

Completed redo application of 0.00MB

2024-08-24T06:11:25.596058+08:00

Completed crash recovery at

 Thread 1: RBA 2.3.0, nab 3, scn 0x000000001114683a

 0 data blocks read, 0 data blocks written, 0 redo k-bytes read

Endian type of dictionary set to little

2024-08-24T06:11:25.648152+08:00

LGWR (PID:1614826): STARTING ARCH PROCESSES

2024-08-24T06:11:25.661738+08:00

TT00 (PID:1614908): Gap Manager starting

Starting background process ARC0

2024-08-24T06:11:25.677246+08:00

ARC0 started with pid=54, OS id=1614910

2024-08-24T06:11:25.687525+08:00

LGWR (PID:1614826): ARC0: Archival started

LGWR (PID:1614826): STARTING ARCH PROCESSES COMPLETE

2024-08-24T06:11:25.687733+08:00

ARC0 (PID:1614910): Becoming a 'no FAL' ARCH

ARC0 (PID:1614910): Becoming the 'no SRL' ARCH

2024-08-24T06:11:25.696437+08:00

TMON (PID:1614886): STARTING ARCH PROCESSES

Starting background process ARC1

2024-08-24T06:11:25.711645+08:00

Thread 1 advanced to log sequence 3 (thread open)

Redo log for group 3, sequence 3 is not located on DAX storage

2024-08-24T06:11:25.715270+08:00

ARC1 started with pid=56, OS id=1614914

Starting background process ARC2

Thread 1 opened at log sequence 3

  Current log# 3 seq# 3 mem# 0: /dbf/RLZY/redo03.log

Successful open of redo thread 1

2024-08-24T06:11:25.728586+08:00

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Stopping change tracking

2024-08-24T06:11:25.734124+08:00

ARC2 started with pid=57, OS id=1614916

Starting background process ARC3

2024-08-24T06:11:25.752891+08:00

ARC3 started with pid=58, OS id=1614918

2024-08-24T06:11:25.752979+08:00

TMON (PID:1614886): ARC1: Archival started

TMON (PID:1614886): ARC2: Archival started

TMON (PID:1614886): ARC3: Archival started

TMON (PID:1614886): STARTING ARCH PROCESSES COMPLETE

2024-08-24T06:11:25.802551+08:00

ARC0 (PID:1614910): Archived Log entry 2828 added for T-1.S-2 ID 0x74f18f91 LAD:1

2024-08-24T06:11:25.806845+08:00

TT03 (PID:1614922): Sleep 5 seconds and then try to clear SRLs in 2 time(s)

Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc  (incident=124865):

ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []

Incident details in: /oracle/diag/rdbms/xff/xff/incident/incdir_124865/xff_ora_1614892_i124865.trc

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

2024-08-24T06:11:25.871925+08:00

2024-08-24T06:11:26.772652+08:00

*****************************************************************

An internal routine has requested a dump of selected redo.

This usually happens following a specific internal error, when

analysis of the redo logs will help Oracle Support with the

diagnosis.

It is recommended that you retain all the redo logs generated (by

all the instances) during the past 12 hours, in case additional

redo dumps are required to help with the diagnosis.

*****************************************************************

2024-08-24T06:11:26.872265+08:00

Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc:

ORA-00704: bootstrap process failure

ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []

2024-08-24T06:11:26.872351+08:00

Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc:

ORA-00704: bootstrap process failure

ORA-00704: bootstrap process failure

ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []

2024-08-24T06:11:26.872412+08:00

Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc:

ORA-00704: bootstrap process failure

ORA-00704: bootstrap process failure

ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []

2024-08-24T06:11:26.872455+08:00

Error 704 happened during db open, shutting down database

Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc  (incident=124866):

ORA-00603: ORACLE server session terminated by fatal error

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-00704: bootstrap process failure

ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []

Incident details in: /oracle/diag/rdbms/xff/xff/incident/incdir_124866/xff_ora_1614892_i124866.trc

opiodr aborting process unknown ospid (1614892) as a result of ORA-603

2024-08-24T06:11:27.498146+08:00

Errors in file /oracle/diag/rdbms/xff/xff/trace/xff_ora_1614892.trc:

ORA-00603: ORACLE server session terminated by fatal error

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-00704: bootstrap process failure

ORA-00600: internal error code, arguments: [kcbzib_kcrsds_1], [], [], [], [], [], [], [], [], [], [], []

2024-08-24T06:11:27.501122+08:00

ORA-603 : opitsk aborting process

License high water mark = 8

USER(prelim) (ospid: 1614892): terminating the instance due to ORA error 704

2024-08-24T06:11:28.526358+08:00

Instance terminated by USER(prelim), pid = 1614892

官方关于kcbzib_kcrsds_1从解释只有:Bug 31887074 – sr21.1bigscn_hipu3 – trc – ksfdopn2 – ORA-600 [kcbzib_kcrsds_1] (Doc ID 31887074.8)
 

ksfdopn2


虽然关于ORA-600 [kcbzib_kcrsds_1],oracle官方没有给出来解决方案,其实通过以往大量的恢复案例和经验中已经知道,这个错误解决方案就是修改oracle scn的方法可以绕过去,以前有过一些类似恢复案例:
ORA-600 kcbzib_kcrsds_1报错
12C数据库报ORA-600 kcbzib_kcrsds_1故障处理
ORA-00603 ORA-01092 ORA-600 kcbzib_kcrsds_1
redo异常强制拉库报ORA-600 kcbzib_kcrsds_1修复
Patch SCN工具一键恢复ORA-600 kcbzib_kcrsds_1
存储故障,强制拉库报ORA-600 kcbzib_kcrsds_1处理

这篇关于19c库启动报ORA-600 kcbzib_kcrsds_1---惜分飞的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/1108898

相关文章

Android里面的Service种类以及启动方式

《Android里面的Service种类以及启动方式》Android中的Service分为前台服务和后台服务,前台服务需要亮身份牌并显示通知,后台服务则有启动方式选择,包括startService和b... 目录一句话总结:一、Service 的两种类型:1. 前台服务(必须亮身份牌)2. 后台服务(偷偷干

Windows设置nginx启动端口的方法

《Windows设置nginx启动端口的方法》在服务器配置与开发过程中,nginx作为一款高效的HTTP和反向代理服务器,被广泛应用,而在Windows系统中,合理设置nginx的启动端口,是确保其正... 目录一、为什么要设置 nginx 启动端口二、设置步骤三、常见问题及解决一、为什么要设置 nginx

springboot启动流程过程

《springboot启动流程过程》SpringBoot简化了Spring框架的使用,通过创建`SpringApplication`对象,判断应用类型并设置初始化器和监听器,在`run`方法中,读取配... 目录springboot启动流程springboot程序启动入口1.创建SpringApplicat

树莓派启动python的实现方法

《树莓派启动python的实现方法》本文主要介绍了树莓派启动python的实现方法,文中通过图文介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面随着小编来一起学习学习吧... 目录一、RASPBerry系统设置二、使用sandroidsh连接上开发板Raspberry Pi三、运

SpringBoot项目启动后自动加载系统配置的多种实现方式

《SpringBoot项目启动后自动加载系统配置的多种实现方式》:本文主要介绍SpringBoot项目启动后自动加载系统配置的多种实现方式,并通过代码示例讲解的非常详细,对大家的学习或工作有一定的... 目录1. 使用 CommandLineRunner实现方式:2. 使用 ApplicationRunne

bat脚本启动git bash窗口,并执行命令方式

《bat脚本启动gitbash窗口,并执行命令方式》本文介绍了如何在Windows服务器上使用cmd启动jar包时出现乱码的问题,并提供了解决方法——使用GitBash窗口启动并设置编码,通过编写s... 目录一、简介二、使用说明2.1 start.BAT脚本2.2 参数说明2.3 效果总结一、简介某些情

MySQL数据库宕机,启动不起来,教你一招搞定!

作者介绍:老苏,10余年DBA工作运维经验,擅长Oracle、MySQL、PG、Mongodb数据库运维(如安装迁移,性能优化、故障应急处理等)公众号:老苏畅谈运维欢迎关注本人公众号,更多精彩与您分享。 MySQL数据库宕机,数据页损坏问题,启动不起来,该如何排查和解决,本文将为你说明具体的排查过程。 查看MySQL error日志 查看 MySQL error日志,排查哪个表(表空间

springboot3打包成war包,用tomcat8启动

1、在pom中,将打包类型改为war <packaging>war</packaging> 2、pom中排除SpringBoot内置的Tomcat容器并添加Tomcat依赖,用于编译和测试,         *依赖时一定设置 scope 为 provided (相当于 tomcat 依赖只在本地运行和测试的时候有效,         打包的时候会排除这个依赖)<scope>provided

内核启动时减少log的方式

内核引导选项 内核引导选项大体上可以分为两类:一类与设备无关、另一类与设备有关。与设备有关的引导选项多如牛毛,需要你自己阅读内核中的相应驱动程序源码以获取其能够接受的引导选项。比如,如果你想知道可以向 AHA1542 SCSI 驱动程序传递哪些引导选项,那么就查看 drivers/scsi/aha1542.c 文件,一般在前面 100 行注释里就可以找到所接受的引导选项说明。大多数选项是通过"_

用命令行的方式启动.netcore webapi

用命令行的方式启动.netcore web项目 进入指定的项目文件夹,比如我发布后的代码放在下面文件夹中 在此地址栏中输入“cmd”,打开命令提示符,进入到发布代码目录 命令行启动.netcore项目的命令为:  dotnet 项目启动文件.dll --urls="http://*:对外端口" --ip="本机ip" --port=项目内部端口 例: dotnet Imagine.M