Tag Archives: shared pool

ORA-600(ksxp_rm_check0)错误

Posted on 2013/07/04 by yangtingkun

客户11.2.0.3 RAC的ASM实例出现ORA-600[ksxp_rm_check0]错误。 错误信息如下： Tue Jul 02 19:22:59 2013 Errors IN file /u01/app/grid/diag/asm/+asm/+ASM2/trace/+ASM2_ora_6488960.trc (incident=165804): ORA-04031: unable TO allocate 3000 bytes OF shared memory ("shared pool","select INSTANCE_NUMBER , IN…","sga heap(1,0)","call") USE ADRCI OR Support Workbench TO package the incident. See Note 411.1 … Continue reading →

Posted in BUG | Tagged , , , , , , , , | Leave a comment

ASM实例出现ORA-4031错误导致实例崩溃

Posted on 2012/08/15 by yangtingkun

数据库的ASM实例出现了ORA-4031错误，导致了数据库实例的崩溃。 详细的错误信息为： Wed Jul 25 08:03:45 2012 Errors IN file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_asmb_34668994.trc (incident=808023): ORA-04031: unable TO allocate 3432 bytes OF shared memory ("shared pool","unknown object","sga heap(1,0)","ASM file") Incident details IN: /u01/app/oracle/diag/rdbms/orcl/ORCL1/incident/incdir_808023/ORCL1_asmb_34668994_i808023.trc Wed Jul 25 08:03:47 2012 Trace dumping IS performing id=[cdmp_20120725080347] … Continue reading →

Posted in BUG | Tagged , , , , , , , , | Leave a comment

ORA-600(kjrpar:noalloc)错误

Posted on 2012/02/29 by yangtingkun

由于ORA-4031引发的ORA-600错误。 告警日志中错误如下： Sat Jan 28 06:07:49 2012 Errors IN file /export/home/OracleHomes/admin/jykfdb/bdump/jykfdb1_j000_21874.trc: ORA-12012: error ON auto EXECUTE OF job 66 ORA-04031: unable TO allocate 6592 bytes OF shared memory ("shared pool","STANDARDSYS","PL/SQL MPCODE","PKR: PL_UEP") Sat Jan 28 06:08:15 2012 Errors IN file … Continue reading →

Posted in BUG | Tagged , , , , , | 1 Comment

ORA-600(504)错误

Posted on 2012/01/26 by yangtingkun

数据库出现ORA-600[504]错误。 错误信息如下： Tue Oct 5 10:16:18 2010 Errors IN file /opt/oracle/admin/eomsdb/udump/eomsdb_ora_29837.trc: ORA-00600: internal error code, arguments: [504], [0x38006C260], [160], [7], [shared pool], [4], [0], [0x38006C070]Tue Oct 5 10:16:18 2010 Errors in file /opt/oracle/admin/eomsdb/udump/eomsdb_ora_29837.trc: ORA-00600: internal error code, arguments: [504], [0x38006C260], … Continue reading →

Posted in BUG | Tagged , , , | Leave a comment