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

相关文章

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

Linux服务器Java启动脚本

Linux服务器Java启动脚本 1、初版2、优化版本3、常用脚本仓库 本文章介绍了如何在Linux服务器上执行Java并启动jar包, 通常我们会使用nohup直接启动,但是还是需要手动停止然后再次启动, 那如何更优雅的在服务器上启动jar包呢,让我们一起探讨一下吧。 1、初版 第一个版本是常用的做法,直接使用nohup后台启动jar包, 并将日志输出到当前文件夹n

衡石分析平台使用手册-单机安装及启动

单机安装及启动​ 本文讲述如何在单机环境下进行 HENGSHI SENSE 安装的操作过程。 在安装前请确认网络环境,如果是隔离环境,无法连接互联网时,请先按照 离线环境安装依赖的指导进行依赖包的安装,然后按照本文的指导继续操作。如果网络环境可以连接互联网,请直接按照本文的指导进行安装。 准备工作​ 请参考安装环境文档准备安装环境。 配置用户与安装目录。 在操作前请检查您是否有 sud

SpringBoot项目是如何启动

启动步骤 概念 运行main方法,初始化SpringApplication 从spring.factories读取listener ApplicationContentInitializer运行run方法读取环境变量,配置信息创建SpringApplication上下文预初始化上下文,将启动类作为配置类进行读取调用 refresh 加载 IOC容器,加载所有的自动配置类,创建容器在这个过程

嵌入式Openharmony系统构建与启动详解

大家好,今天主要给大家分享一下,如何构建Openharmony子系统以及系统的启动过程分解。 第一:OpenHarmony系统构建      首先熟悉一下,构建系统是一种自动化处理工具的集合,通过将源代码文件进行一系列处理,最终生成和用户可以使用的目标文件。这里的目标文件包括静态链接库文件、动态链接库文件、可执行文件、脚本文件、配置文件等。      我们在编写hellowor

三相直流无刷电机(BLDC)控制算法实现:BLDC有感启动算法思路分析

一枚从事路径规划算法、运动控制算法、BLDC/FOC电机控制算法、工控、物联网工程师,爱吃土豆。如有需要技术交流或者需要方案帮助、需求:以下为联系方式—V 方案1:通过霍尔传感器IO中断触发换相 1.1 整体执行思路 霍尔传感器U、V、W三相通过IO+EXIT中断的方式进行霍尔传感器数据的读取。将IO口配置为上升沿+下降沿中断触发的方式。当霍尔传感器信号发生发生信号的变化就会触发中断在中断

kubelet组件的启动流程源码分析

概述 摘要: 本文将总结kubelet的作用以及原理,在有一定基础认识的前提下,通过阅读kubelet源码,对kubelet组件的启动流程进行分析。 正文 kubelet的作用 这里对kubelet的作用做一个简单总结。 节点管理 节点的注册 节点状态更新 容器管理(pod生命周期管理) 监听apiserver的容器事件 容器的创建、删除(CRI) 容器的网络的创建与删除