I am getting lot of DBIF_REPO_SQL_ERROR (ABAP Dump) in CRM system.
How can I getrid of these errors.
I am attaching ST22 log.
Your help on this urgently would be highly appriciated.
Runtime Errors DBIF_REPO_SQL_ERROR
Date and Time 09.03.2009 14:51:37
SQL error 600 occurred when accessing program "CL_IUICOBJD_CONFIG_CN=========CP
An exceptional situation has occurred in the ORACLE software,
possibly due to an error.
This is not an error in an application program.
What can you do?
You cannot eliminate this error yourself.
Please inform your database administrator.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
How to correct the error
Database error text........: "ORA-00600: internal error code, arguments:
[kdtdelrow-2], , , , , , , 
ORA-01654: unable to extend
index SAPCRI.D010INC~1 by 8192 in tablespace PSAPCRI700X"
Triggering SQL statement...: "CL_IUICOBJD_CONFIG_CN=========CP "
Internal call code.........: "[REPO/*/STIN/LREF/CL_IUICOBJD_CONFIG_CN=========C
Please check the entries in the system log (Transaction SM21).
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
"DBIF_REPO_SQL_ERROR" " "
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
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
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
4. Details about the conditions under which the error occurred or which
actions and input led to the error.