on 09-20-2007 11:37 AM
Hi,
Background job BI_ODSA_ASD is getting cancelled,
i have increased the tablespace, still no luck,
last time i faced the same problem at that time , i gave some permission at oracle level which worked fine, i dont not remember now,
it was something like GRANT PRIVILEGE SAPSYS SAPCON...... (not sure)
if anyone knows please let me know.
Regards,
SM
try to run catalog.sql
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
please post exact error message you are getting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SDB_ORA_PROGRAM_ERROR
Date and Time 20.09.2007 15:46:44
-
-
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: |
ـbernehmen |
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-20000: Insufficient privileges ORA-06512: at "SYS.DBMS_STATS", line |
2150 ORA-06512: at "SYS.DBMS_STATS", line 14112 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. |
-
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.