on 07-14-2009 2:43 PM
Hi all,
Our Production System BI7.0 with oracle 10g running on Unix . The UNCAUGHT_EXCEPTION is the ABAP Runtime error exists in ST22.
Please find the Error analysis from ABAP Dump of UNCAUGHT_EXCEPTION.
Error analysis
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
An error occurred in the program:
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_SQL_EXCEPTION", which was raised in the program
"CL_SQL_STATEMENT==============CP",
specifically in line 31 of the (include) program
"CL_SQL_STATEMENT==============CM002".
The cause of the exception was:
ORA-04031: unable to allocate 62208 bytes of shared memory ("shared
pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")#ORA-06508: PL/SQL:
could not find program unit being called: "SYS.DBMS_STATS"#ORA-06512: at line 1
Thanx,
Peter
Hi Peter,
Your shared memory is small, please check the values for kernel.shmmax, kernel.shmall. You can find the values at /etc/sysctl.conf
Thanks,
Arjun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
check this,
Note 633914 - Error when executing DBMS_STATS
Regards,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
You shared pool might be too small
Read,
SAP Note 869006 - Composite SAP note: ORA-04031
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.