标签云
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,885)
- DB2 (22)
- MySQL (82)
- Oracle (1,710)
- 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 (73)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (663)
- 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)
-
最近发表
- 恢复案例分享:win丢失数据文件恢复
- 记录19c ASM磁盘掉线触发ORA-59048故障处理
- aix平台Oracle数据库由于断电无法启动故障处理
- 断电引起ORA-600 3005故障处理
- 记录一次云存储资源到期之后引起的数据库恢复
- Firebird 损坏数据库数据抢救工具—firebirdext
- 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系统数据库恢复过程
分类目录归档:ORA-xxxxx
rman备份出现ORA-19625/ORA-27054解决
RAC环境NFS挂载归档日志使用rman备份出现ORA-19625/ORA-27054错误分析
系统运行环境
OS:AIX 6100-06 DB:11.1.0.6.0 RAC 归档:挂载NFS
rman执行archive log时候报错
sql statement: alter system archive log current Starting backup at 25-OCT-11 current log archived released channel: c1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 02/17/2012 13:03:51 RMAN-06059: expected archived log not found, lost of archived log compromises recoverability ORA-19625: error identifying file /rarchlogA/1_13775_764866137.dbf ORA-27054: NFS file system where the file is created or resides is not mounted with correct options Additional information: 6
这里由于RAC存放归档使用了NFS文件系统,在使用rman备份归档日志执行alter system archive log current的时候发生如下错误.
相关目录挂载情况
$ df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
…………
/dev/lv_arch 50.00 43.24 14% 166 1% /arch1
oradb2:/arch2 50.00 35.31 30% 463 1% /arch2
/dev/baklv 90.00 83.82 7% 10 1% /backup
$ mount:
…………
/dev/lv_oracle /oracle jfs2 Oct 14 11:27 rw,log=/dev8
/dev/lv_arch /arch1 jfs2 Oct 14 11:27 rw,log=/dev8
oradb2 /arch2 /arch2 nfs3 Oct 14 11:47
通过这里可以知道,这里使用默认的参数挂载NFS,从而使得NFS在rman工作时候不能正常工作。
错误原因
From Oracle 10G R2 , Oracle checks the options with which a NFS mount is mounted on the filesystem. and this is done to ensure that no corruption of the database can happen as incorrectly mounted NFS volumes can result in data corruption. There are no single set of NFS mount options that work across all Oracle platforms Please ensure that you have the proper mount options specified by the NAS vendor /Vendor user guide The exact checks used for an NFS mounted disk vary between platforms but in general the basic checks will include the following checks a) The mount table (eg; /etc/mnttab) can be read to check the mount options b) The NFS mount is mounted with the "hard" option c) The mount options include rsize>=32768 and wsize>=32768 d) For RAC environments, where NFS disks are supported, the "noac" mount option is used.
解决方案
1.临时解决方案
As suggested in the bug the workaround recommended is to use the Event 10298.
alter system set events ’10298 trace name context forever, level 32′;
2.永久解决方案
具体见://www.xifenfei.com/3269.html
发表在 ORA-xxxxx
评论关闭
ORACLE 11.2.0.3 生成awr html文件报SYS.DBMS_WORKLOAD_REPOSITORY异常
在想分析数据库性能的关键时刻,突然发现awr不能正常的工作,那就和你上了战场突然发现枪没有子弹一样的郁闷,今天就遇到了11.2.0.3在win的环境中awr生成html不能正常工作.通过查询mos发现该问题出现在各种平台中(win,linux,aix等),提醒大家注意该问题.
数据库版本
SQL> SELECT * FROM V$VERSION; BANNER ------------------------------------------------------------------------- Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production PL/SQL Release 11.2.0.3.0 - Production CORE 11.2.0.3.0 Production TNS for 32-bit Windows: Version 11.2.0.3.0 - Production NLSRTL Version 11.2.0.3.0 - Production
awr报错(html)
SQL> @?/rdbms/admin/awrrpt.sql ORA-06502: PL/SQL: 数字或值错误 : 字符串缓冲区太小 ORA-06512: 在 "SYS.DBMS_WORKLOAD_REPOSITORY", line 919 ORA-06512: 在 line 1
设置errorstack
SQL> alter session set events '6502 trace name errorstack level 12'; 会话已更改。
分析错误
----- Error Stack Dump -----
ORA-06502: PL/SQL: 数字或值错误 : 字符串缓冲区太小
----- Current SQL Statement for this session (sql_id=572fbaj0fdw2b) -----
select output from table(dbms_workload_repository.awr_report_html( :dbid,
:inst_num,
:bid, :eid,
:rpt_options ))
----- PL/SQL Call Stack -----
object line object
handle number name
94348684 919 package body SYS.DBMS_WORKLOAD_REPOSITORY
983BAD54 1 anonymous block
----- Call Stack Trace -----
_skdstdst()+121 CALLrel _kgdsdst() 19D99520 2
_ksedst1()+93 CALLrel _skdstdst() 19D99520 0 1 485816 4863B2
485816
_ksedst()+49 CALLrel _ksedst1() 0 1
_dbkedDefDump()+368 CALLrel _ksedst() 0
6
_ksedmp()+44 CALLrel _dbkedDefDump() C 0
_dbkdaKsdActDriver( CALLreg 00000000 C
)+4209
…………
通过查询mos发现Bug 13575143一致,可以确定是该bug,但是通过进一步测试证明不光是awrrpt会出现该错误,awr的相关报告中,只要是展示html结果的都有可能出现类此错误(比如awrrpti.sql/awrddrpt.sql/awrddrpi.sql等等).同时这里通过进一步分析发现其实该bug的起源是Bug 6458801(REPLACE on a CLOB can corrupt multibyte data ID 6458801.8),不过该bug说明已经在11.2.0.1中修复,其实通过这里的分析发现并没有真正的在11.2.0.3中修复该bug,针对该问题没有官方没有提供较好解决方法,只能是用过WORKAROUND来临时解决
They are able to generate the AWR report in the .txt format
large pool太小导致shared server异常
数据库出现如下错误
Fri Oct 5 09:33:54 2012 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20 Process S001 started up but failed with error = 20 failed to start shared server 'S001', oer=20
重启后错误提示变为
Successfully onlined Undo Tablespace 1.
Fri Oct 5 09:34:41 2012
SMON: enabling tx recovery
Fri Oct 5 09:34:41 2012
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: ALTER DATABASE OPEN
Fri Oct 5 13:53:50 2012
Errors in file /oracle/admin/ora/bdump/ora_s000_25948.trc:
ORA-04031: unable to allocate 72 bytes of shared memory
("large pool","unknown object","session heap","trigger condition node")
Fri Oct 5 13:53:50 2012
Errors in file /oracle/admin/ora/bdump/ora_s000_25948.trc:
ORA-00600: internal error code, arguments: [ksudel1], [], [], [], [], [], [], []
ORA-04031: unable to allocate 72 bytes of shared memory
("large pool","unknown object","session heap","trigger condition node")
Fri Oct 5 13:54:52 2012
found dead shared server 'S000', pid = (11, 1)
Fri Oct 5 17:25:59 2012
Errors in file /oracle/admin/ora/bdump/ora_s000_31081.trc:
ORA-04031: unable to allocate 72 bytes of shared memory
("large pool","unknown object","session heap","trigger condition node")
Fri Oct 5 17:25:59 2012
Errors in file /oracle/admin/ora/bdump/ora_s000_31081.trc:
ORA-00600: internal error code, arguments: [ksudel1], [], [], [], [], [], [], []
ORA-04031: unable to allocate 72 bytes of shared memory
("large pool","unknown object","session heap","trigger condition node")
通过这里的错误,我们可以看到是large pool不能分配72 bytes的连续内存空间而使得S000进程报错.那这两者有什么联系:我们知道S000是shared server的进程,那shared server为什么导致large pool不足呢?查询官方文档得出,如下三种情况会使用large pool
Session memory for the shared server and the Oracle XA interface (used where transactions interact with more than one database) I/O server processes Oracle backup and restore operations
主要也就是shared server/parallel query buffers/backup restore这几个操作会使用到large pool.在该案例中很明显的可以看到是因为shared server进程需要分配large pool中一部分空间,而没有连续空间从而出现该错误.数据库相关参数配置
SQL> show parameter mts; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ mts_circuits integer 555 mts_dispatchers string (PROTOCOL=TCP) (SERVICE=oraXDB) mts_listener_address string mts_max_dispatchers integer 5 mts_max_servers integer 20 mts_multiple_listeners boolean FALSE mts_servers integer 1 mts_service string ora mts_sessions integer 550 SQL> show parameter large; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ large_pool_size big integer 16777216
这里可以看出来,数据库明显配置了MTS,因为数据库在启动时候,最少会建立一个shared server进程,而这个时候因为large pool太小(16M),导致该进程无法正常建立,从而出现上述alert中相关错误,临时处理方法增加large pool.后续需要关注业务特点,考虑是否可以采用Oracle Dedicated server模式来处理.
发表在 ORA-xxxxx
评论关闭

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

