Dump on DBIF_RSQL_INVALID_RSQL se14 pooled table adjustment

Question

I have been trying to adjust table T157T in SE14 and I get a short dump that says:
Runtime Error          DBIF_RSQL_INVALID_RSQL
Exception              CX_SY_OPEN_SQL_DB
Occurred on     08.03.2008 at   15:06:58
Error in the module RSQL accessing the database interface.
What happened?
Error in ABAP application program.
The current ABAP program "%_T002S0" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was neither caught nor passed along using a RAISING clause, in the procedure "DATA_COPY"  "(FORM)".
Since the caller of the procedure could not have expected this exception to occur, the running program was terminated.
The reason for the exception is:
The data read during a SELECT access could not be inserted into the target field. Either conversion is not supported for the target field's type or the
target field is too short to accept the value or the data are not in a form that the target field can accept
How to correct the error
The exception must either be prevented, caught within the procedure "DATA_COPY"
"(FORM)", or declared in the procedure's RAISING clause. To prevent the exception, note the following:
Check the entries in the developer trace (Transaction ST11) This contains details about the type and length of the database field, and the field in ABAP in which the database field should
have been placed.
Assistance will be greatly appreciated and rewarded.
Regards.

Answer 1

DURING ADJUST THERE ARE PRIMARLY MANY STEPS INVOLVED
LOCKING THE TABLE
1.CREATING A TABLE WITH SAME NAME SPACE Q*
2.CREATING THE STRCUTRE OF THE TABLE
3.DELETING INDEXES
4.MOVING THE DATA FROM TABLE ORIGINAL TO TEMP TABLE.
5.DELETING THE TABLE OLD
6.CREATING NEW STRUCTURE WITH ORGINAL NAME.
7.MOVING THE DATA.
8.DELETING ALL THE TEMP TABLE & STRUCTURES.
UNLOCKING THE TABLE
U R ERROR PRETAINS TO EITHER DURING THE DATA_COPY U R SELECT QUERIE RUNS IN LOOPS
SO THE AUM-->> AUTOMATIC UNDO MANAGEMENT IS NOT SO ADEQUATELY SUPPORTED
SO IT TRIES TO RETAIN THE RECORD BUT IT COULDNT RETAIN BECAUSE OF IT NON AVAILBILITY OF BUFFERS SO SEE THE AUM-->> REDO PARAMETERS ARE AT HIGHEST AND THEN TRY YOUR ACIVITY U CAN ALSO GET THE LOG PARAMETERS IN ALERT.LOG FILE IN THE BACKEND ASK UR BASIS CONSULTANT TO LOOK INTO IT.
REGARDS
DEVANAND