win强制修改盘符导致oracle异常恢复----惜分飞

有客户反馈,他们在系统没有关闭数据库的情况下,强制修改了win系统盘符,然后导致数据库异常,启动报错

Sat Feb 25 12:50:40 2023

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

Mem# 0 errs 0: G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG

Sat Feb 25 12:50:40 2023

Completed redo application

Sat Feb 25 12:50:40 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p001_5604.trc:

ORA-00600: 内部错误代码, 参数: [2037], [25801018], [2973409798], [6], [255], [25], [1198764346], [100796692]

Sat Feb 25 12:50:40 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_7648.trc:

ORA-07445: 出现异常错误: 核心转储 [ACCESS_VIOLATION][_kslwlmod+166][PC:0x469742][ADDR:0x54F8][UNABLE_TO_WRITE][]

ORA-04096: 触发器 ''的 WHEN 子句过大, 限量为 2K

Sat Feb 25 12:50:40 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_7252.trc:

ORA-00600: internal error code, arguments: [ksuapc2], [258], [0], [2], [1], [2], [], []

Sat Feb 25 12:50:43 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_p001_5604.trc:

ORA-00081: 地址范围 [0x77240440, 0x77240444) 不可读

ORA-07445: 出现异常错误: 核心转储 [ACCESS_VIOLATION][_ksl_cleanup+723][PC:0x46E373][ADDR:0x1C][UNABLE_TO_READ][]

ORA-00081: 地址范围 [0x77240440, 0x77240444) 不可读

ORA-00600: 内部错误代码, 参数: [2037], [25801018], [2973409798], [6], [255], [25], [1198764346], [100796692]

Sat Feb 25 12:50:45 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_dbw0_6332.trc:

ORA-07445: ??????: ???? [ACCESS_VIOLATION][_kews_idle_wait+378][PC:0x604AE6][ADDR:0xED30C470][UNABLE_TO_WRITE][]

Sat Feb 25 12:50:48 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_7648.trc:

ORA-00600: 内部错误代码, 参数: [kslwlflux:1], [0xAB805400], [0x549C], [2], [], [], [], []

ORA-00081: 地址范围 [0x74480443, 0x74480447) 不可读

ORA-00600: 内部错误代码, 参数: [kslwlflux:1], [0xAB805400], [0x549C], [2], [], [], [], []

ORA-00081: 地址范围 [0x74480443, 0x74480447) 不可读

ORA-00600: 内部错误代码, 参数: [kslwlflux:1], [0xAB805400], [0x549C], [2], [], [], [], []

ORA-00081: 地址范围 [0x74480443, 0x74480447) 不可读

ORA-00600: 内部错误代码, 参数: [kslwlflux:1], [0xAB805400], [0x549C], [2], [], [], [], []

ORA-00081: 地址范围 [0x74480443, 0x74480447) 不可读

ORA-00600: 内部错误代码, 参数: [kslwlflux:1], [0xAB805400], [0x549C], [2], [], [], [], []

ORA-00081: 地址范围 [0x74480443, 0x74480447) 不可读

ORA-00600: 内部错误代码, 参数: [kslwlflux:1], [0xAB805400], [0x549C], [2], [], [], [], []

ORA-00081: 地址范围 [0x74480443, 0x74480447) 不可读

ORA-00600: 内部错误代码, 参数: [kslwlflux:1], [0xAB805400], [0x549C], [2], [], [], [], []

ORA-00081: 地址范围 [0x74480443, 0x74480447) 不可读

ORA-00600: 内部错误代码, 参

Sat Feb 25 12:51:34 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_d000_8116.trc:

ORA-07445: ??????: ???? [ACCESS_VIOLATION][_kmcgms+121][PC:0x5D6C71][ADDR:0x50][UNABLE_TO_WRITE][]

Sat Feb 25 12:52:04 2023

USER: terminating instance due to error 472

Sat Feb 25 12:52:48 2023

USER: terminating instance due to error 472

Sat Feb 25 12:52:48 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6252.trc:

ORA-07445: exception encountered: core dump [ACCESS_VIOLATION][_ksuitm+631][PC:0x410C07][ADDR:0x1][UNABLE_TO_READ][]

Sat Feb 25 12:55:35 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_7656.trc:

ORA-07445: ??????: ???? [ACCESS_VIOLATION][_kews_idle_wait+378][PC:0x604AE6][ADDR:0xE530C470][UNABLE_TO_WRITE][]

通过恢复一些恢复之后,数据库open之后又挂掉

Sat Feb 25 15:05:49 2023

SMON: enabling tx recovery

Sat Feb 25 15:05:49 2023

Database Characterset is ZHS16GBK

Sat Feb 25 15:05:50 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_5308.trc:

ORA-00600: 内部错误代码, 参数: [4194], [34], [31], [], [], [], [], []

Sat Feb 25 15:05:50 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_7568.trc:

ORA-00600: 内部错误代码, 参数: [kcbgtcr_13], [], [], [], [], [], [], []

Sat Feb 25 15:05:51 2023

Non-fatal internal error happenned whileSMON was doing logging scn->timemapping.

SMON encountered 1 out of maximum 100 non-fatal internal errors.

Sat Feb 25 15:05:51 2023

Doing block recovery forfile2 block 2951

Block recovery from logseq 10441, block 78 to scn 109906860017

Sat Feb 25 15:05:51 2023

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

Mem# 0 errs 0: G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG

Block recovery stopped at EOT rba 10441.81.16

Block recovery completed at rba 10441.81.16, scn 25.2532677517

Doing block recovery forfile2 block 113

Block recovery from logseq 10441, block 78 to scn 109906859718

Sat Feb 25 15:05:52 2023

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

Mem# 0 errs 0: G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG

Block recovery completed at rba 10441.80.16, scn 25.2532677516

replication_dependency_tracking turned off (no async multimaster replication found)

Starting background process QMNC

QMNC started with pid=30, OS id=6904

Sat Feb 25 15:05:53 2023

db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a

user-specified limit on the amount of space that will be used by this

database forrecovery-related files, and does not reflect the amount of

space available inthe underlying filesystem or ASM diskgroup.

Sat Feb 25 15:05:53 2023

Completed: alter database open

Sat Feb 25 15:05:53 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j000_5400.trc:

ORA-00600: 内部错误代码, 参数: [4194], [6], [4], [], [], [], [], []

Sat Feb 25 15:05:54 2023

DEBUG: Replaying xcb 0xac458698, pmd 0x8d7e9b9c forfailed op8

Doing block recovery forfile2 block 1515

No block recovery was needed

Sat Feb 25 15:05:55 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j000_5400.trc:

ORA-00600: 内部错误代码, 参数: [4194], [6], [4], [], [], [], [], []

ORA-00600: 内部错误代码, 参数: [4194], [6], [4], [], [], [], [], []

Sat Feb 25 15:05:56 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j000_5400.trc:

ORA-00603: ORACLE server session terminated by fatal error

ORA-00600: internal error code, arguments: [4194], [6], [4], [], [], [], [], []

ORA-00600: internal error code, arguments: [4194], [6], [4], [], [], [], [], []

Sat Feb 25 15:05:57 2023

Doing block recovery forfile2 block 2951

Block recovery from logseq 10441, block 78 to scn 109906860017

Sat Feb 25 15:05:57 2023

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

Mem# 0 errs 0: G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG

Block recovery completed at rba 10441.81.16, scn 25.2532677620

Doing block recovery forfile2 block 113

Block recovery from logseq 10441, block 78 to scn 109906860083

Sat Feb 25 15:05:57 2023

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

Mem# 0 errs 0: G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG

Block recovery completed at rba 10441.138.16, scn 25.2532677684

Sat Feb 25 15:05:57 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j003_1716.trc:

ORA-12012: 自动执行作业 42568 出错

ORA-00607: 当更改数据块时出现内部错误

ORA-00607: 当更改数据块时出现内部错误

Sat Feb 25 15:05:59 2023

Flush retried forxcb 0xac4c5a80, pmd 0x8c0cec74

Doing block recovery forfile2 block 2951

Block recovery from logseq 10441, block 78 to scn 109906860017

Sat Feb 25 15:05:59 2023

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

Mem# 0 errs 0: G:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG

Sat Feb 25 15:05:59 2023

DEBUG: Replaying xcb 0xac458698, pmd 0x8d7e9b9c forfailed op8

Doing block recovery forfile2 block 1515

No block recovery was needed

Sat Feb 25 15:05:59 2023

Block recovery completed at rba 10441.81.16, scn 25.2532677620

Sat Feb 25 15:06:00 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j002_6400.trc:

ORA-00600: internal error code, arguments: [4194], [6], [4], [], [], [], [], []

Sat Feb 25 15:06:02 2023

DEBUG: Replaying xcb 0xac458698, pmd 0x8d7e9b9c forfailed op8

Doing block recovery forfile2 block 1515

No block recovery was needed

Sat Feb 25 15:06:02 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_pmon_1076.trc:

ORA-00600: 内部错误代码, 参数: [4194], [6], [4], [], [], [], [], []

Sat Feb 25 15:06:03 2023

PMON: terminating instance due to error 472

Sat Feb 25 15:06:03 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j007_7188.trc:

ORA-00472: PMON 进程因错误而终止

Sat Feb 25 15:06:03 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j006_7624.trc:

ORA-00472: PMON 进程因错误而终止

Sat Feb 25 15:06:03 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_j005_5688.trc:

ORA-00472: PMON process terminated with error

Sat Feb 25 15:06:10 2023

Errors infileg:\oracle\product\10.2.0\admin\orcl\bdump\orcl_smon_7568.trc:

ORA-00472: PMON 进程因错误而终止

Instance terminated by PMON, pid = 1076

这个ORA-600 4194错误主要是由于undo异常,从而引起pmon异常,报ORA-00472错误.对undo进行处理,数据库稳定open,逻辑导出数据,完成恢复工作,完美帮忙客户恢复数据.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
要在Win11中安装mingw-w64,您可以按照以下步骤进行操作: 1. 首先,您需要下载mingw-w64的安装包。您可以从官方网站或其他可信来源获取最新版本的mingw-w64。 2. 下载完成后,您需要将安装包解压到您选择的目录下。通常情况下,将文件解压到D盘或其他任意盘符的根目录下是一个不错的选择。 3. 解压完成后,您可以打开解压后的文件夹,查看其中的内容。 4. 在文件夹中,您会找到一个bin文件夹和一个include文件夹。这些文件夹包含必要的文件和工具,以便于使用mingw-w64。 5. 接下来,您需要将bin文件夹和include文件夹添加到系统的环境变量中的path变量中。这样,系统才能够正确地找到mingw-w64的执行文件和头文件。 6. 在Win11中添加环境变量的方法是:在Windows搜索栏中输入“环境变量”,然后选择“编辑用户环境变量”。在弹出的对话框中,选择“Path”变量,然后点击“编辑”按钮。在编辑变量窗口中,点击“新建”按钮,并添加mingw-w64的bin文件夹和include文件夹的路径。确保路径之间使用分号进行分隔,并保存更改。 7. 完成以上步骤后,您可以在命令行或其他编程环境中测试mingw-w64是否已成功安装。您可以尝试运行gcc命令来编译和运行C/C++代码,以验证mingw-w64的安装是否成功。 通过按照上述步骤进行操作,您应该能够在Win11中成功安装mingw-w64,并配置好相关环境以便于使用。<span class="em">1</span><span class="em">2</span><span class="em">3</span>

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值