标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 obet ORA-00312 ORA-00704 ORA-00742 ORA-01110 ORA-01200 ORA-01555 ORA-01578 ORA-01595 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-600 kcratr_nab_less_than_odr ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle碎片 OSD-04016 YOUR FILES ARE ENCRYPTED 比特币加密文章分类
- MongoDB (1)
- MongoDB恢复 (1)
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (112)
- 数据库 (1,879)
- DB2 (22)
- MySQL (82)
- Oracle (1,705)
- Data Guard (53)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (168)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (72)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (659)
- Oracle安装升级 (108)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (91)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (5)
- 达梦恢复 (3)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (51)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (34)
- MongoDB (1)
-
最近发表
- Oracle 19c 202610补丁(RUs+OJVM)-19.33
- 由于con$.con#值达到极限,触发数据库增加约束报ORA-600 12807错误
- MongoDB 离线提取工具—mongoext
- .bres勒索病毒加密数据库dmp文件可恢复
- ORA-600 krsm_mrp_rebuild_lf_list.lno_mismatch
- 记录一次0丢失的ORA-00354: 损坏重做日志块标头故障恢复
- 不当数据库恢复操作导致一个月数据丢失
- obet快速修复oracle 位图损坏块
- 不太常见的10.2.0.1的oracle redo损坏恢复
- obet forcecopy功能抢救硬件故障中的数据文件
- kcratr_nab_less_than_odr和system坏块故障处理
- 通过obet 恢复system坏块,打开数据库
- obet dbv功能完整说明
- 分享一例运行在aix上的sap系统数据库恢复过程
- OBET-Oracle Block Editor Tool使用说明
- 几乎动用了所有手段的Oracle故障恢复
- Oracle Block Edit Tool (obet) 功能增强–2026.07
- Oracle 19c 202607补丁(RUs+OJVM)-19.32
- Patch_SCN快速修复ORA-01555数据库open故障
- 快速处理 ORA-01210: data file header is media corrupt 故障
分类目录归档:ORA-xxxxx
ORA-07217: sltln: environment variable cannot be evaluated.
dg备库mount报ORA-07217
在一次搭建dg过程中,备库无法mount,报ORA-07217: sltln: environment variable cannot be evaluated.错误
[oracle@localhost orcl]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Wed Feb 13 22:27:31 2019 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> alter database mount; alter database mount * ERROR at line 1: ORA-07217: sltln: environment variable cannot be evaluated.
alert日志报错
Set as converted control file due to db_unique_name mismatch Changing di2dbun from ORCL to ORCLDG ORA-7217 signalled during: alter database mount... Wed Feb 13 20:33:41 2019 alter database mount ORA-7217 signalled during: alter database mount... Wed Feb 13 20:36:11 2019 alter database mount ORA-7217 signalled during: alter database mount...
根据mos排查
根据mos ORA-07217: sltln: environment variable cannot be evaluated (Doc ID 2487898.1)描述排查,确认不是该问题
SQL> show parameter diag; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ diagnostic_dest string /u01/app/oracle [oracle@dg:/opt/app/oracle/arch]$env|grep ORA ORACLE_SID=orcl ORACLE_BASE=/opt/app/oracle ORACLE_TERM=xterm ORACLE_HOME=/opt/app/oracle/product/11.2.0/db_1
检查发现数据文件异常
SQL> select name from v$datafile where name like '%$%'; NAME ------------------------------------------------------ +DATA/orcl/datafile/ts_his$emr01 +DATA/orcl/datafile/ts_his$emr02
通过分析,注释掉db_file_name_convert=’+DATA/orcl/datafile/’,’/u01/app/oradata/orcl/’即可正常mount成功,数据文件命令一定要规范(不要有特殊符号),不然给后人和自己留下巨坑
下调虚拟化资源导致ORA-00494
在虚拟化环境中的Oracle数据库近期报大量ORA-00494: 入队 [CF] 被持有的时间过长 (more than 900 seconds) 错误,每次客户重启一段时间之后又不行
Mon Nov 26 14:04:39 中国标准时间 2018 Thread 1 advanced to log sequence 97327 (LGWR switch) Current log# 1 seq# 97327 mem# 0: D:\ORADATA\xifenfei\REDO01.LOG Mon Nov 26 14:20:02 中国标准时间 2018 Errors in file c:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_arc1_1860.trc: ORA-00494: 入队 [CF] 被持有的时间过长 (more than 900 seconds) (由 'inst 1, osid 3264') Mon Nov 26 14:20:03 中国标准时间 2018 Errors in file c:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_arc4_1872.trc: ORA-00494: 入队 [CF] 被持有的时间过长 (more than 900 seconds) (由 'inst 1, osid 3264') Mon Nov 26 14:20:03 中国标准时间 2018 Errors in file c:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_arc3_1868.trc: ORA-00494: 入队 [CF] 被持有的时间过长 (more than 900 seconds) (由 'inst 1, osid 3264') Mon Nov 26 14:20:03 中国标准时间 2018 Errors in file c:\oracle\product\10.2.0\admin\xifenfei\bdump\xifenfei_arc0_1856.trc: ORA-00494: 入队 [CF] 被持有的时间过长 (more than 900 seconds) (由 'inst 1, osid 3264')
因为这个系统有一段历史,以前是客户的核心生产库,虚拟化资源给的比较多128G,后来核心生产迁移到其他系统,该系统跑一些边缘小业务,所以怀疑客户有可能下调了虚拟化的资源(cpu和内存),检查机器硬件资源
C:\Users\Administrator>systeminfo
主机名: HIS-VM
OS 名称: Microsoft Windows Server 2008 R2 Enterprise
OS 版本: 6.1.7601 Service Pack 1 Build 7601
OS 制造商: Microsoft Corporation
OS 配置: 独立服务器
OS 构件类型: Multiprocessor Free
注册的所有人: Windows 用户
注册的组织:
产品 ID: 00486-OEM-8400691-20006
初始安装日期: 2013/4/19, 12:22:44
系统启动时间: 2018/11/27, 8:06:00
系统制造商: VMware, Inc.
系统型号: VMware Virtual Platform
系统类型: x64-based PC
处理器: 安装了 2 个处理器。
[01]: Intel64 Family 6 Model 45 Stepping 2 GenuineIntel
Mhz
[02]: Intel64 Family 6 Model 45 Stepping 2 GenuineIntel
Mhz
BIOS 版本: Phoenix Technologies LTD 6.00, 2014/4/14
Windows 目录: C:\Windows
系统目录: C:\Windows\system32
启动设备: \Device\HarddiskVolume1
系统区域设置: zh-cn;中文(中国)
输入法区域设置: zh-cn;中文(中国)
时区: (UTC+08:00) 北京,重庆,香港特别行政区,乌鲁木齐
物理内存总量: 32,767 MB
可用的物理内存: 22,740 MB
虚拟内存: 最大值: 95,047 MB
虚拟内存: 可用: 10,426 MB
虚拟内存: 使用中: 84,621 MB
页面文件位置: C:\pagefile.sys
域: WORKGROUP
果然系统内存从128G下调到了32G,但是数据库sga估计没有对应降低
SQL> show parameter sga; NAME TYPE VALUE ------------------------------------ ----------- ------ lock_sga boolean FALSE pre_page_sga boolean FALSE sga_max_size big integer 80G sga_target big integer 80G
基本上就是由于虚拟机内存下调,但是数据库sga配置过大导致该问题.
ORA-600 2131故障说明
oracle 12c数据库启动报ORA-600 2131错误
Mon Nov 26 09:43:57 2018 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared server(s) ... ORACLE_BASE from environment = D:\app\Administrator alter database mount exclusive Mon Nov 26 09:44:00 2018 Using default pga_aggregate_limit of 2048 MB Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\trace\orcl12c_ora_3040.trc (incident=375524): ORA-00600: ??????, ??: [2131], [9], [8], [], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\orcl12c\orcl12c\incident\incdir_375524\orcl12c_ora_3040_i375524.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. ORA-600 signalled during: alter database mount exclusive...
这个日志比较明显,数据库无法mount,在mount操作的时候报ORA-600 2131错误.
trace文件报错
Error: kccpb_sanity_check_2
Control file sequence number mismatch!
fhcsq: 497844 bhcsq: 497849 cfn 0 rpbn 16
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst1()+92 CALL??? skdstdst() 000000001 000004000 000030000
016301338
kccpb_sanity_check( CALL??? ksedst1() 1492761E0 0000798B4 0000798B9
)+834 000000000
kccbmp_get()+275 CALL??? kccpb_sanity_check( 000000000 000000000 000000000
) 000004000
kccsed_rbl()+174 CALL??? kccbmp_get() 000017E28 015A67E14 015592200
000000001
kccocx()+1399 CALL??? kccsed_rbl() 100000010 100000001 0000354D8
000035508
kccocf()+167 CALL??? kccocx()+528 016303990 000000000
7FF00000001 000000000
kcfcmb()+1254 CALL??? kccocf() 000000000 000000000 000000000
000000000
kcfmdb()+69 CALL??? kcfcmb() 000000000 7FF59FFF856
000000007 7FE00000000
adbdrv_options()+43 CALL??? kcfmdb() 0163083E0 14903FF2C 000000005
724 000000000
adbdrv()+149 CALL??? adbdrv_options() 000000000 000000000 0163084A0
851F2CC90B75
opiexe()+22668 CALL??? adbdrv() 7FF00000023 000000003
000000000 016309380
opiosq0()+6009 CALL??? opiexe() 000000000 000000000 016309990
000000000
kpooprx()+410 CALL??? opiosq0() 000000003 000000000 000000000
0000000A4
kpoal8()+994 CALL??? kpooprx() 0146A57FC 000000001 0146A5820
000000001
opiodr()+1601 CALL??? kpoal8() 000000000 015523288 015523270
0159FCDD0
ttcpip()+1223 CALL??? opiodr() 7FE0000005E 00000001F
01630DA20 7FE00000000
opitsk()+2160 CALL??? ttcpip() 0146C0690 000000000 000000000
000000000
opiino()+1079 CALL??? opitsk() 000000007 000000000 01630F200
01630E970
opiodr()+1601 CALL??? opiino() 00000003C 000000000 01630F470
000000000
opidrv()+842 CALL??? opiodr() 00000003C 000000004 01630F470
000000000
sou2o()+94 CALL??? opidrv()+156 10000003C 7FE00000004
01630F470 0154E6A30
opimai_real()+276 CALL??? sou2o() 1D4851F4C467583 00A9D55E0
8001A000B07E2 1004B0039001E
opimai()+170 CALL??? opimai_real() 000000000 851F2CB1B179
00A9D55E0 01630F628
OracleThreadStart() CALL??? opimai() 000000000 149031F90 000000050
+713 0000005C8
00000000775259CD CALL??? OracleThreadStart() 000000000 000000000 000000000
000000000
000000007765A561 CALL??? 00000000775259C0 000000000 000000000 000000000
000000000
--------------------- Binary Stack Dump ---------------------
这个错误和以往版本中的kccpb_sanity_check_2比较类似,由于数据库异常关闭导致ctl写丢失导致
ORA-600 2131/kccpb_sanity_check_2解释
DESCRIPTION: This internal error is raised when the sequence number (seq#) of the current block of the controlfile is greater than the seq# in the controlfile header. The header value should always be equal to, or greater than the value held in the control file block(s). This extra check was introduced in Oracle 10gR2 to detect lost writes or stale reads to the header. ARGUMENTS: Arg [a] seq# in control block header. Arg [b] seq# in the control file header. Arg 1 FUNCTIONALITY: Kernel Cache layer Control file component.

加我微信(17813235971)
加我QQ(107644445)

