存储故障,强制拉库报ORA-600 kcbzib_kcrsds_1处理---惜分飞

文章描述了一次Oracle数据库实例在客户误操作强制重置redologs后遇到ORA-600kcbzib_kcrsds_1错误的情况,涉及了数据库一致性检查、可能的数据库损坏、redo日志清理和重建过程,以及后续的诊断和恢复措施,包括数据泵迁移数据到新库的步骤。

硬件故障,客户自行强制resetlogs库,报ORA-600 kcbzib_kcrsds_1错误

2024-01-17T17:30:33.094367+08:00

alter database open resetlogs

2024-01-17T17:30:33.105461+08:00

RESETLOGS is being done without consistancy checks. This may result

in a corrupted database. The database should be recreated.

RESETLOGS after incomplete recovery UNTIL CHANGE 16456823130015 time

.... (PID:1584): Clearing online redo logfile 1 /u01/app/oracle/oradata/XFF/redo01.log

.... (PID:1584): Clearing online redo logfile 2 /u01/app/oracle/oradata/XFF/redo02.log

.... (PID:1584): Clearing online redo logfile 3 /u01/app/oracle/oradata/XFF/redo03.log

Clearing online log 1 of thread 1 sequence number 1345

Clearing online log 2 of thread 1 sequence number 1346

Clearing online log 3 of thread 1 sequence number 1347

2024-01-17T17:30:43.054150+08:00

.... (PID:1584): Clearing online redo logfile 1 complete

.... (PID:1584): Clearing online redo logfile 2 complete

.... (PID:1584): Clearing online redo logfile 3 complete

Resetting resetlogs activation ID 259120030 (0xf71db9e)

Online log /u01/app/oracle/oradata/XFF/redo01.log: Thread 1 Group 1 was previously cleared

Online log /u01/app/oracle/oradata/XFF/redo02.log: Thread 1 Group 2 was previously cleared

Online log /u01/app/oracle/oradata/XFF/redo03.log: Thread 1 Group 3 was previously cleared

2024-01-17T17:30:43.201042+08:00

Setting recovery target incarnation to 3

2024-01-17T17:30:43.267669+08:00

Smart fusion block transfer is disabled:

  instance mounted in exclusive mode.

2024-01-17T17:30:43.282033+08:00

Crash Recovery excluding pdb 2 which was cleanly closed.

Endian type of dictionary set to little

2024-01-17T17:30:43.396061+08:00

Assigning activation ID 280673168 (0x10babb90)

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

2024-01-17T17:30:43.433441+08:00

TT00 (PID:1652): Gap Manager starting

2024-01-17T17:30:43.526972+08:00

Thread 1 opened at log sequence 1

  Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/XFF/redo01.log

Successful open of redo thread 1

2024-01-17T17:30:43.528058+08:00

MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set

Stopping change tracking

2024-01-17T17:30:44.097557+08:00

Errors in file /u01/app/oracle/diag/rdbms/XFF/XFF/trace/XFF_ora_1584.trc(incident=263984)(PDBNAME=CDB$ROOT):

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

Incident details <

若在下载https://github.com/dbeaver/dbeaver/releases/download/25.2.5/dbeaver-ce-25.2.5-win32.win32.x86_64.zip文件时遇到问题,可能是网络因素或代理设置等原因。 像下载https://github.com/electron-userland/electron-builder-binaries/releases/download/appimage-12.0.1/appimage-12.0.1.7z文件时,会因网络因素导致无法下载 [^1]。还有设置代理后失败,出现 “fatal: unable to access 'https://github.com/lucidrains/bottleneck-transformer-pytorch.git/': Failed to connect to 127.0.0.1 port 7890: Connection refused” 这类错 [^2]。在使用Git进行代码管理,执行git clone或git pull等操作时,也会因网络连接问题或代理设置不正确,出现 “fatal: unable to access ‘https://github.com/…/.git’: Recv failure Connection was reset” 的错 [^3]。 若遇到下载问题,可尝试以下操作: 1. 检查网络连接,确保网络稳定且能正常访问GitHub。 2. 检查代理设置,若设置了代理,可尝试关闭代理或者重新配置正确的代理信息。 3. 尝试更换下载工具或浏览器进行下载。 ```python # 若使用Python的requests下载文件示例 import requests url = 'https://github.com/dbeaver/dbeaver/releases/download/25.2.5/dbeaver-ce-25.2.5-win32.win32.x86_64.zip' response = requests.get(url) if response.status_code == 200: with open('dbeaver-ce-25.2.5-win32.win32.x86_64.zip', 'wb') as file: file.write(response.content) print('文件下载成功!') else: print(f'下载失败,状态码:{response.status_code}') ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值