Reply from Dave Thornburgh on Dec 22 at 1:10 AM Praveen -
Have you checked the OSS? If you have and need help understanding what you've found (or not found), you should ask your question in the Basis forum. This isn't an MM question.
Dave
| | | ---------------Original Message---------------
From: praveengbasis
Sent: Wednesday, December 21, 2011 8:50 AM
Subject: UNCAUGHT_EXCEPTION Runtime Error
Hi Friends,
The error I am getting last week. How can I resolve the issue can please help me.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SDB_ORA_PROGRAM_ERROR
Date and Time 20.12.2011 12:37:26
----
----
|Short text |
| An exception occurred that was not caught. |
----
----
|What happened? |
| 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. |
----
----
|What can you do? |
| Note down which actions and inputs caused the error. |
| |
| |
| To process the problem further, contact you SAP system |
| administrator. |
| |
| Using Transaction ST22 for ABAP Dump Analysis, you can look |
| at and manage termination messages, and you can also |
| keep them for a long time. |
----
----
|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-20001: invalid column name or duplicate columns/column groups/expressions |
| in method_opt
ORA-06512: at "SYS.DBMS_STATS", line 23393
ORA-06512: at |
| "SYS.DBMS_STATS", line 23444
ORA-06512: at line 1 |
| ... |
| |
----
----
|How to correct the error |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR" |
| "CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I" |
| "UPDATE_STATS" |
| |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
----
----
|System environment |
| SAP-Release 700 |
| |
| Application server... "p19442db01" |
| Network address...... "172.19.122.101" |
| Operating system..... "Linux" |
| Release.............. "2.6.18-238.12.1.el5" |
| Hardware type........ "x86_64" |
| Character length.... 8 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 5 |
| Shortdump setting.... "full" |
| |
| Database server... "p19442db01" |
| Database type..... "ORACLE" |
| Database name..... "P15" |
| Database user ID.. "SAPSR3" |
| |
| Terminal................. " " |
| |
| Char.set.... "en_US.ISO-8859-1" |
| |
| SAP kernel....... 700 |
| created (date)... "Jul 10 2011 20:19:32" |
| create on........ "Linux GNU SLES-9 x86_64 cc3.3.3" |
| Database version. "OCI_102 (10.2.0.4.0) " |
| |
| Patch level. 310 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 700 |
| Operating system..... "Linux 2.6" |
| |
| Memory consumption |
| Roll.... 5285008 |
| EM...... 0 |
| Heap.... 0 |
| Page.... 24576 |
| MM Used. 4550224 |
| MM Free. 705888 |
----
----
|User and Transaction |
| |
| Client.............. 100 |
| User................ "ALEREMOTE" |
| Language key........ "E" |
| Transaction......... " " |
| Transactions ID..... "4EF0D0F373291004E1000000AC137A65" |
| |
| Program............. "CL_SDB_ORA_UPDATE_STATS=======CP" |
| Screen.............. "SAPMSSY0 1000" |
| Screen line......... 6 |
----
----
|Information on where terminated |
| 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_83DB42DR9XVNOMTHO0OFN19PH" |
| Job Initiator.. "ALEREMOTE" |
| Job Number..... 12372300
Thanks
Praveen |
| Reply to this email to post your response. __.____._ |   _.____.__ |
0 Response to "RE: [sap-log-mm] UNCAUGHT_EXCEPTION Runtime Error"
Post a Comment