标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-01595 ORA-08103 ORA-600 2131 ORA-600 2662 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-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 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (103)
- 数据库 (1,768)
- DB2 (22)
- MySQL (77)
- Oracle (1,609)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (166)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (69)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (591)
- Oracle安装升级 (97)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (86)
- PostgreSQL (30)
- pdu工具 (6)
- PostgreSQL恢复 (9)
- SQL Server (32)
- SQL Server恢复 (13)
- TimesTen (7)
- 达梦数据库 (3)
- 达梦恢复 (1)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (39)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (22)
-
最近发表
- ORA-600 kokiasg1故障分析(obj$中核心字典序列全部被恶意删除)
- ORA-00756 ORA-10567故障数据0丢失恢复
- 数据库文件变成32k故障恢复
- tcp连接过多导致监听TNS-12532 TNS-12560 TNS-00502错误
- 文件系统格式化MySQL数据库恢复
- .sstop勒索加密数据库恢复
- 解决一次硬件恢复之后数据文件0kb的故障恢复case
- Error in invoking target ‘libasmclntsh19.ohso libasmperl19.ohso client_sharedlib’问题处理
- ORA-01171: datafile N going offline due to error advancing checkpoint
- linux环境oracle数据库被文件系统勒索加密为.babyk扩展名溯源
- ORA-600 ksvworkmsgalloc: bad reaper
- ORA-600 krccfl_chunk故障处理
- Oracle Recovery Tools恢复案例总结—202505
- ORA-600 kddummy_blkchk 数据库循环重启
- 记录一次asm disk加入到vg通过恢复直接open库的案例
- CHECKDB 发现了 N 个分配错误和 M 个一致性错误
- 达梦数据库dm.ctl文件异常恢复
- Oracle Recovery Tools修复ORA-00742、ORA-600 ktbair2: illegal inheritance故障
- 可能是 tempdb 空间用尽或某个系统表不一致故障处理
- 11.2.0.4库中遇到ORA-600 kcratr_nab_less_than_odr报错
月归档:四月 2012
ORA-00600[729]分析和处理方法
alert中ORA-00600[729]
Fri Apr 6 04:30:04 2012 Errors in file /oracle9/app/admin/crm/udump/crm2_ora_2548236.trc: ORA-00600: internal error code, arguments: [729], [1067976], [space leak], [], [], [], [], []
a. the first bracketed number [729] is the common argument for space leak problems.
b. the second number [1067976] is the number of bytes leaked by the error.
c. the third argument is always [space leak].
分析trace文件
*** 2012-04-06 04:30:04.656 *** SESSION ID:(1361.35607) 2012-04-06 04:30:04.648 ******** ERROR: UGA memory leak detected 1067976 ******** ****************************************************** HEAP DUMP heap name="session heap" desc=1103a05f0
a. the memory was leaked from the UGA area
b. the amount leaked is reported again in the text (1067976 bytes).
c. the above few lines describe this dump as SESSION HEAP with the descriptor 0x1103a05f0.
计算泄露内存大小
****************************************************** HEAP DUMP heap name="session heap" desc=1103a05f0 extent sz=0xff80 alt=32767 het=32767 rec=0 flg=3 opc=3 parent=110009628 owner=700000c3b6f5620 nex=0 xsz=0xff80 EXTENT 0 addr=1107dbf50 Chunk 1107dbf60 sz= 65392 free " " EXTENT 1 addr=1107cbf50 Chunk 1107cbf60 sz= 65392 free " " EXTENT 2 addr=110541da0 Chunk 110541db0 sz= 61312 free " " EXTENT 3 addr=11062ae88 Chunk 11062ae98 sz= 266264 freeable "kllcqgf:kllsltb" EXTENT 4 addr=1105dae88 Chunk 1105dae98 sz= 266264 freeable "kllcqgf:kllsltb" EXTENT 5 addr=110550d48 Chunk 110550d58 sz= 266264 freeable "kllcqgf:kllsltb" EXTENT 6 addr=110500d48 Chunk 110500d58 sz= 266264 freeable "kllcqgf:kllsltb" EXTENT 7 addr=1104e1df0 Chunk 1104e1e00 sz= 200 perm "perm " alo=200 Chunk 1104e1ec8 sz= 65192 free " " EXTENT 8 addr=1104c1df0 Chunk 1104c1e00 sz= 40720 perm "perm " alo=40720 Chunk 1104cbd10 sz= 56 free " " Chunk 1104cbd48 sz= 408 freeable "kcbl_structure_" Chunk 1104cbee0 sz= 6952 free " " Chunk 1104cda08 sz= 2424 freeable "kllcqc:kllcqslt" Chunk 1104ce380 sz= 14832 free " " EXTENT 9 addr=1104d1df0 Chunk 1104d1e00 sz= 65392 free " " EXTENT 10 addr=1104b1df0 Chunk 1104b1e00 sz= 544 free " " Chunk 1104b2020 sz= 88 freeable "kllcqc:kllcq " Chunk 1104b2078 sz= 64760 free " " EXTENT 11 addr=110427390 Chunk 1104273a0 sz= 65392 free " " EXTENT 12 addr=110417390 Chunk 1104173a0 sz= 65392 free " " EXTENT 13 addr=110407390 Chunk 1104073a0 sz= 65392 free " " EXTENT 14 addr=1103f7390 Chunk 1103f73a0 sz= 65392 free " " EXTENT 15 addr=1103e7390 Chunk 1103e73a0 sz= 65392 free " " EXTENT 16 addr=1103d7390 Chunk 1103d73a0 sz= 65392 free " " EXTENT 17 addr=1103c7390 Chunk 1103c73a0 sz= 408 free " " Chunk 1103c7538 sz= 2232 perm "perm " alo=2232 Chunk 1103c7df0 sz= 62752 free " " EXTENT 18 addr=1103b7390 Chunk 1103b73a0 sz= 65392 free " " EXTENT 19 addr=110370080 Chunk 110370090 sz= 2008 perm "perm " alo=2008 Chunk 110370868 sz= 63384 free " " EXTENT 20 addr=110360098 Chunk 1103600a8 sz= 20424 perm "perm " alo=20424 Chunk 110365070 sz= 44944 free " " Total heap size = 2172616 FREE LISTS: Bucket 0 size=56 Chunk 1104cbd10 sz= 56 free " " Bucket 1 size=88 Bucket 2 size=152 Bucket 3 size=168 Bucket 4 size=280 Chunk 1103c73a0 sz= 408 free " " Bucket 5 size=432 Bucket 6 size=536 Chunk 1104b1e00 sz= 544 free " " Bucket 7 size=1048 Bucket 8 size=2072 Bucket 9 size=4120 Chunk 1104cbee0 sz= 6952 free " " Bucket 10 size=8216 Chunk 1104ce380 sz= 14832 free " " Bucket 11 size=16408 Bucket 12 size=32792 Chunk 110365070 sz= 44944 free " " Chunk 110370868 sz= 63384 free " " Chunk 1104d1e00 sz= 65392 free " " Chunk 1103b73a0 sz= 65392 free " " Chunk 1103c7df0 sz= 62752 free " " Chunk 1103d73a0 sz= 65392 free " " Chunk 1103f73a0 sz= 65392 free " " Chunk 1104073a0 sz= 65392 free " " Chunk 1104b2078 sz= 64760 free " " Chunk 1103e73a0 sz= 65392 free " " Chunk 1104e1ec8 sz= 65192 free " " Chunk 1104273a0 sz= 65392 free " " Chunk 1104173a0 sz= 65392 free " " Chunk 1107cbf60 sz= 65392 free " " Chunk 110541db0 sz= 61312 free " " Chunk 1107dbf60 sz= 65392 free " " Bucket 13 size=65560 Bucket 14 size=131096 Bucket 15 size=262168 Bucket 16 size=524312 Bucket 17 size=2097176 Total free space = 1039056 UNPINNED RECREATABLE CHUNKS (lru first): PERMANENT CHUNKS: Chunk 1104e1e00 sz= 200 perm "perm " alo=200 Chunk 1104c1e00 sz= 40720 perm "perm " alo=40720 Chunk 1103c7538 sz= 2232 perm "perm " alo=2232 Chunk 110370090 sz= 2008 perm "perm " alo=2008 Chunk 1103600a8 sz= 20424 perm "perm " alo=20424 Permanent space = 65584 ******************************************************
FREEABLE and RECREATABLE chunks总和等于1067976 byte(leaked memory)
会话状态分析
*** 2012-04-06 04:30:04.658 ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [729], [1067976], [space leak], [], [], [], [], [] ----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------------- ---------------------------- ksedmp+0148 bl ksedst 1029746FC ? ksfdmp+0018 bl 01FD4014 kgeriv+0118 bl _ptrgl kgesiv+0080 bl kgeriv 000000001 ? 000000002 ? 1100610D0 ? 000000000 ? 00000000A ? ksesic2+005c bl kgesiv FFFFFFFFFFF9320 ? 1101FAF78 ? 110006308 ? 1103A0818 ? 000000009 ? ksmuhe+026c bl ksesic2 2D9000002D9 ? 000000000 ? 000104BC8 ? 000000001 ? 00000000A ? 103164968 ? 12E0BE826D694B2F ? 000000000 ? ksmugf+0214 bl ksmuhe 110002A20 ? 110061238 ? 000000009 ? 102975DE8 ? ksuxds+170c bl ksmugf 000000000 ? 020000000 ? 1029754D0 ? ksudel+006c bl ksuxds 700000C3B6F5620 ? 100000001 ? opilof+03dc bl 01FD427C <--表示logoff opiodr+08cc bl _ptrgl ttcpip+0cc4 bl _ptrgl opitsk+0d60 bl ttcpip 11000CF90 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? 000000000 ? opiino+0758 bl opitsk 000000000 ? 000000000 ? opiodr+08cc bl _ptrgl opidrv+032c bl opiodr 3C00000018 ? 4101FAF78 ? FFFFFFFFFFFF7B0 ? 0A000F350 ? sou2o+0028 bl opidrv 3C0C000000 ? 4A00E8B50 ? FFFFFFFFFFFF7B0 ? main+0138 bl 01FD3A28 __start+0098 bl main 000000000 ? 000000000 ? --------------------- Binary Stack Dump --------------------- ……………… ---------------------------------------- SO: 700000c3b6f5620, type: 4, owner: 700000c3c987a18, flag: INIT/-/-/0x00 --flag: (41) USR/- BSY/-/-/DEL/-/- shows that the session has been deleted (session) trans: 0, creator: 700000c3c987a18, flag: (41) USR/- BSY/-/-/DEL/-/- DID: 0002-0927-01D67CAD, short-term DID: 0000-0000-00000000 txn branch: 0 oct: 0, prv: 0, sql: 700000caf2c0e30, psql: 700000caf2c0e30, user: 52/MONITOR O/S info: user: oracrm, term: , ospid: 1490968, machine: zwq_crm2 program: exp@zwq_crm2 (TNS V1-V3) last wait for 'SQL*Net message from client' blocking sess=0x0 seq=59222 wait_time=1537 driver id=54435000, #bytes=1, =0 temporary object counter: 0 ----------------------------------------
a.在logoff的时候发生UGA中的session heap发生内存泄露
b.该进程是一个exp导出数据库程序,并且该程序已经被释放
出现ORA-00600[729]原因
Memory leak problems generally occur when Oracle is trying to free memory allocated to a process. The memory leak dump is generally discovered during session logoff, when Oracle frees the heaps that are allocated for the user process. When a user connects to Oracle, a user process is created and at that time the heap is allocated. Every process will have its own memory heap. The memory is organized in to heaps and every heap consists of one or more extents. Each extent contains a series of contiguous memory chunks, and these chunks can be either FREE or ALLOCATED. The Generic Heap Manager takes care of allocating and deallocating the memory chunks, with the help of FREE LISTS and LRU LISTS. Chunk types are as follows: 1. FREE 2. FREEABLE 3. RECREATABLE 4. PERMANENT 5. FREEABLE WITH MARK It is not mandatory that each extent contain only one type of chunk. Extents can contain various types of chunks. When processes require memory chunks, they are allocated as needed. Oracle keeps track of the amount of memory allocated for the process internally. When the process terminates, all of the memory that has been allocated for the process is automatically released. When the memory is released the allocated heaps are freed. Generally, when the heap is freed the only chunks that the process should identify as allocated are the PERMANENT chunks and FREE chunks on the freelist. If the process finds there are still FREEABLE or RECREATABLE chunks remaining, then the process has not properly deallocated the memory. This situation is considered a space leak.
ORA-00600[729]处理方案
1. If there are no other errors reported at the same time, this may be a case where the error was a rare occurrence and can be safely ignored. As a rule of thumb, leaks less than 90,000 bytes in size are considered to be of low significance. The solution in this case is to set event 10262 (see below). a. Set the following event in init.ora parameter file. This example disables reporting for space leaks less than 90000 bytes: event = "10262 trace name context forever, level 90000" b. Stop and restart the database. If the level is set to 1, space leak checking is disabled. This is not advised because large memory leaks will be missed. If the event is set to a value greater than 1, any space leak up to the number specified in the event is ignored. 2. Is the leak in the SGA? The alert.log should be reviewed for additional errors such as ORA-4030 and ORA-4031 to ensure there are no additional problems with the shared pool or operating system memory. 3. Does the error reproduce with a given task? If so, this is a case that should be investigated further because the leak could be a known bug. See Note 31056.1 ORA-600 [729] UGA Space Leak for a list of known bugs and fixes.
参考:Understanding and Diagnosing ORA-600 [729] Space Leak Errors [ID 403584.1]
ORA-00001: unique constraint (PERFSTAT.STATS$SQL_SUMMARY_PK) violated
出现如下错误(ORA-00001: unique constraint (PERFSTAT.STATS$SQL_SUMMARY_PK) violated)
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production With the Partitioning option JServer Release 9.2.0.6.0 - Production ORACLE_HOME = /oracle9/app/product/9.2.0 System name: AIX Node name: zwq_bill_1 Release: 1 Version: 6 Machine: 00F64FF34C00 Instance name: bill1 Redo thread mounted by this instance: 1 Oracle process number: 30 Unix process pid: 46531060, image: oracle@zwq_bill_1 (J000) *** SESSION ID:(218.47085) 2012-04-02 19:30:45.561 *** 2012-04-02 19:30:45.561 ORA-12012: error on auto execute of job 1 ORA-00001: unique constraint (PERFSTAT.STATS$SQL_SUMMARY_PK) violated ORA-06512: at "PERFSTAT.STATSPACK", line 1361 ORA-06512: at "PERFSTAT.STATSPACK", line 2471 ORA-06512: at "PERFSTAT.STATSPACK", line 91 ORA-06512: at line 1
这个是oracle的一个Bug 2784796,提供解决方法有
1.run the statspack at level 0
2.restart the instance
3.set cursor sharing to exact (probably not feasible)
4.禁用主键,创建合适非唯一index
ALTER TABLE PERFSTAT.STATS$SQL_SUMMARY MODIFY CONSTRAINT STATS$SQL_SUMMARY_PK DISABLE NOVALIDATE;
5.修改STATS$V_$SQLXS视图
分析思路如下:
1)根据主键冲突找到主键包含列(spctab.sql)
create table STATS$SQL_SUMMARY (snap_id number(6) not null ,dbid number not null ,instance_number number not null ,text_subset varchar2(31) not null ,sql_text varchar2(1000) ,sharable_mem number ,sorts number ,module varchar2(64) ,loaded_versions number ,fetches number ,executions number ,loads number ,invalidations number ,parse_calls number ,disk_reads number ,buffer_gets number ,rows_processed number ,command_type number ,address raw(8) ,hash_value number ,version_count number ,cpu_time number ,elapsed_time number ,outline_sid number ,outline_category varchar2(64) ,child_latch number --注意下面5列构成主键 ,constraint STATS$SQL_SUMMARY_PK primary key (snap_id, dbid, instance_number, hash_value, text_subset) using index tablespace &&tablespace_name storage (initial 1m next 1m pctincrease 0) ,constraint STATS$SQL_SUMMARY_FK foreign key (snap_id, dbid, instance_number) references STATS$SNAPSHOT on delete cascade )tablespace &&tablespace_name storage (initial 1m next 1m pctincrease 0) pctfree 5 pctused 40;
2)找到该表插入数据(spcpkg.sql)
insert into stats$sql_summary ( snap_id , dbid , instance_number , text_subset , sharable_mem , sorts , module , loaded_versions , fetches , executions , loads , invalidations , parse_calls , disk_reads , buffer_gets , rows_processed , command_type , address , hash_value , version_count , cpu_time , elapsed_time , outline_sid , outline_category , child_latch ) select l_snap_id , p_dbid , p_instance_number , substrb(sql_text,1,31) , sharable_mem , sorts , module , loaded_versions , fetches , executions , loads , invalidations , parse_calls , disk_reads , buffer_gets , rows_processed , command_type , address , hash_value , version_count , cpu_time , elapsed_time , outline_sid , outline_category , child_latch from stats$v$sqlxs where is_obsolete = 'N' and ( buffer_gets > l_buffer_gets_th or disk_reads > l_disk_reads_th or parse_calls > l_parse_calls_th or executions > l_executions_th or sharable_mem > l_sharable_mem_th or version_count > l_version_count_th );
3)找出stats$v$sqlxs对象(spcusr.sql)
create or replace view STATS$V_$SQLXS as select max(sql_text) sql_text , sum(sharable_mem) sharable_mem , sum(sorts) sorts , min(module) module , sum(loaded_versions) loaded_versions , sum(fetches) fetches , sum(executions) executions , sum(loads) loads , sum(invalidations) invalidations , sum(parse_calls) parse_calls , sum(disk_reads) disk_reads , sum(buffer_gets) buffer_gets , sum(rows_processed) rows_processed , max(command_type) command_type , address address , hash_value hash_value , count(1) version_count , sum(cpu_time) cpu_time , sum(elapsed_time) elapsed_time , max(outline_sid) outline_sid , max(outline_category) outline_category , max(is_obsolete) is_obsolete , max(child_latch) child_latch from v$sql group by hash_value, address; create or replace public synonym STATS$V$SQLXS for STATS$V_$SQLXS;
4)通过这里可以看出,要是的STATS$SQL_SUMMARY主键不重复,只要是的STATS$V_$SQLXS查询出来的记录唯一,所以解决方案就是在STATS$V_$SQLXS视图中增加下列条件,确保查询出来的记录唯一,从而不会发生主键冲突
where ( plan_hash_value > 0 or executions > 0 or parse_calls > 0 or disk_reads > 0 or buffer_gets > 0 )
该bug在10g中修复,对于不能及时升级的数据库,建议采用第五种方法解决问题,比较治标治本,对业务基本上无影响
DB2数据库激活
db2当前激活状态
[db2inst1@xifenfei ~]$ db2licm -l Product name: "DB2 Enterprise Server Edition" License type: "Trial" Expiry date: "06/22/2012" Product identifier: "db2ese" Version information: "9.5" Product name: "DB2 Connect Server" License type: "Trial" Expiry date: "06/22/2012" Product identifier: "db2consv" Version information: "9.5"
查看license文件
[db2inst1@xifenfei ~]$ db2licm -l db2ese_cV9.5CPU.lic Product name: "DB2 Enterprise Server Edition" License type: "CPU Option" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "9.5" Features: DB2 Database Partitioning: "Not licensed" DB2 Performance Optimization ESE: "Not licensed" DB2 Storage Optimization: "Not licensed" DB2 Advanced Access Control: "Not licensed" DB2 Geodetic Data Management: "Not licensed" DB2 pureXML ESE: "Not licensed" IBM Homogeneous Federation ESE: "Not licensed" IBM Homogeneous Replication ESE: "Not licensed" Product name: "DB2 Connect Server" License type: "Trial" Expiry date: "06/22/2012" Product identifier: "db2consv" Version information: "9.5"
导入license文件
[db2inst1@xifenfei ~]$ db2licm -a db2ese_cV9.5CPU.lic LIC1402I License added successfully. LIC1426I This product is now licensed for use as outlined in your License Agreement. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT, LOCATED IN THE FOLLOWING DIRECTORY: "/opt/db2/V9.5/license/en_US.iso88591"
再次查看db2激活状态
[db2inst1@xifenfei ~]$ db2licm -l Product name: "DB2 Enterprise Server Edition" License type: "CPU Option" Expiry date: "Permanent" Product identifier: "db2ese" Version information: "9.5" Features: DB2 Database Partitioning: "Not licensed" DB2 Performance Optimization ESE: "Not licensed" DB2 Storage Optimization: "Not licensed" DB2 Advanced Access Control: "Not licensed" DB2 Geodetic Data Management: "Not licensed" DB2 pureXML ESE: "Not licensed" IBM Homogeneous Federation ESE: "Not licensed" IBM Homogeneous Replication ESE: "Not licensed" Product name: "DB2 Connect Server" License type: "Trial" Expiry date: "06/22/2012" Product identifier: "db2consv" Version information: "9.5"
各种数据库的激活方式不同(只讨论激活,不涉及授权问题):
1.oracle/mysql不需要激活,可以直接使用
2.sql server 需要序列号激活
3.db2需要license文件激活