[sap-basis] We are receiving many memory related dumps like SYSTEM_NO_ROLL and UNCAUGHT_EXCEPTION in our BW 7 system
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by mona10 (Software Engineer) on Mar 17 at 2:05 PM |
Hi All,
We are receiving many memory related dumps like SYSTEM_NO_ROLL and UNCAUGHT_EXCEPTION in our BW 7 system (db oracle:10.2.0.4)
The error description:
The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
anywhere along the call hierarchy.
Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program 'CL_SDB_ORA_UPDATE_STATS=======CP' has to be terminated.
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
caught andtherefore caused a runtime error.
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 62904 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
...
Client.............. 530
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4B9F2787270F0078E1008000828BD457"
Program............. "CL_SDB_ORA_UPDATE_STATS=======CP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
2:34 PM Termination occurred in the ABAP program "CL_SDB_ORA_UPDATE_STATS=======CP" -
in "UPDATE_STATS".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 40
of the (Include) program "CL_SDB_ORA_UPDATE_STATS=======CM00I".
The program "CL_SDB_ORA_UPDATE_STATS=======CP" was started as a background job.
Job Name....... "BIROLL_4H62WYUDMN3KDG6XPMY2OYVKN"
Job Initiator.. "ALEREMOTE"
I have searched many sap notes which suggests to increase the size of parameter SHARED_POOL_SIZE. However current value of the parameter in the system is 44G.
I need to confirm whether it is really required to increase the memory parameters if yes then which all parameters are required to be increased or is there some other reason for it.
Please help.
Thanks & Regards,
Mona
__.____._ We are receiving many memory related dumps like SYSTEM_NO_ROLL and UNCAUGHT_EXCEPTION in our BW 7 system (db oracle:10.2.0.4)
The error description:
The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
anywhere along the call hierarchy.
Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program 'CL_SDB_ORA_UPDATE_STATS=======CP' has to be terminated.
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
caught andtherefore caused a runtime error.
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 62904 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
...
Client.............. 530
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4B9F2787270F0078E1008000828BD457"
Program............. "CL_SDB_ORA_UPDATE_STATS=======CP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
2:34 PM Termination occurred in the ABAP program "CL_SDB_ORA_UPDATE_STATS=======CP" -
in "UPDATE_STATS".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 40
of the (Include) program "CL_SDB_ORA_UPDATE_STATS=======CM00I".
The program "CL_SDB_ORA_UPDATE_STATS=======CP" was started as a background job.
Job Name....... "BIROLL_4H62WYUDMN3KDG6XPMY2OYVKN"
Job Initiator.. "ALEREMOTE"
I have searched many sap notes which suggests to increase the size of parameter SHARED_POOL_SIZE. However current value of the parameter in the system is 44G.
I need to confirm whether it is really required to increase the memory parameters if yes then which all parameters are required to be increased or is there some other reason for it.
Please help.
Thanks & Regards,
Mona
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
In the Spotlight
55% of IT Pros Use Social Media to Advance Their Careers. See the Survey Results
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
_.____.__ 
