SAP Dumps DBIF_REPO_SQL_ERROR ERROR ORA-1653
Hi ,
we have problem in our system, when ever we are trying to do something in customization or try to run some programs its going to dump. I anylized the dump, looks like I need to increase(enhance) the table space. ( I mean by creating to new data file). I don't know how to do that and from where to do that . we are using windows NT system.
here is part of SAP dump we are getting..
-------------------------------------------------
ABAP runtime errors DBIF_REPO_SQL_ERROR
Occurred on 04/17/2003 at 12:03:06
SQL error 1653 occurred when accessing program "SAPLSTUS " part "LOAD".
What happened?
What can you do?
Please make a note of the actions and input which caused the error.
Please make a note of the actions and input which caused the error.
To resolve the problem, contact your
SAP system administrator.
Choose "Print" for a hard coopy of the termination message. You can
display and adminster short dump messages using Transaction ST22.
Error analysis
How to correct the error
Database error text........: "ORA-01653: unable to extend table SAPR3.D010L by
5120 in tablespace PSAPEL46CD?"
Triggering SQL statement...: "SAPLSTUS "
Internal call code.........: "[REPO/*/WRBL/LOAD/SAPLSTUS ]"
Please check the entries in the system log (Transaction SM21).
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"DBIF_REPO_SQL_ERROR"
"SAPLSTUS " or "SAPLSTUS "
" "
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant part..
.....
...
I appriciate if anyone of you can give some idea how to procee futher to resolve this issue,
thanks in advace,
Reddy
Easy - what you should do is to report this to your Basis / DB folks.
Tell them that tablespace PSAPEL46CD is out of space, and pass this info -- they'll know what to do.
Regards,
Dabbler
Hum, our basis guy is not avialble right now. that's why i am asking any one of you can help on how to extend table space for PSAPEL46CD..?
it's bit urgent,
thanks,
Reddy
Hi, I have the same problem. The solution was given in the How to Correct Error in the dump itself and I quote:
How to correct the error
The ABAP/4 Open SQL statement concerned must be divided into several
smaller units.
If the problem occurred because an excessively large table was used
in an IN itab construct, you can use FOR ALL ENTRIES instead.
-
When you use this addition, the statement is split into smaller units
according to the restrictions of the database system used.
-
I suspect this will work particularly if its one of your own report because you can amend it.
Hope it helps.
regards