Error apdapting database using database utility(transaction se11)

[Former Member]

Hello;

We have a several z* tables of an aplicattion running for a year in a production enviroment. We have to change 4 data elements used in these tables.

These elements were QUAN 4 decimals 0 and we have to pass to QUAN 4 decimals 2. I have change the data element in the devolopment enviroment by adjusting these tables with database utility(transaction se11) without problems. The values were transformed adding 2 decimals.

I try to do the same in the quality eviroment(production copy) and appears an error adapting these fields. The tables have a lot of registers (more than 100.000 ) the error DBIF_RSQL_SQL_ERROR; the table appears in the dicctionary but it is not created in the ORACLE.

Do you know how can I finish this step?. It is possible these transformation QUAN 4 decimals 0 to QUAN 4 decimals 2?? In development I have not problem.

Thanks in advanced.

[Former Member]

Moved to SAP on Oracle (thanks Thomas!)...

[ThomasZloch]

Analyse the short dump, especially section "error analysis". Look in SAP Support Portal (OSS) for notes. Restart the adjustment via SE14 (check out the info icon there), once the underlying problem is fixed.

Thomas

[Former Member]

Hi Thomas;

I have analysed the short dump; I and the "error analysis"; and debugged where it fails. ... and I can't find a solution...

I paste the code where it fails...

INSERT QCM8ZSD11 CLIENT SPECIFIED

FROM TABLE QCM8ZSD11_TAB ACCEPTING DUPLICATE KEYS.

The temporal table generated is QCM8ZSD11 and the original the ZSD11.

It fails in the 5 step.

1 Initialization

2 Dropping of indexes, renaming of original table

3 No action

4 Activation of transparent table

5 Conversion of data to new table, deletion of renamed table

6 Creation of sec. indexes

Adjustment terminated in step 5

Initial table Table type Status

ZSD11 Transparent Renamed

Renamed original table

QCMZSD11 transparent Existent

Tgt.table

ZSD11 Transparent Renamed

Thanks in advanced.

[ThomasZloch]

Well, the problem must be named somewhere, can you paste the "error analysis" part of the short dump as well? Maybe there is not enough disk space to hold the temporary QCM8-Table, a typical problem of step 5.

Thomas

[Former Member]

Thanks Thomas;

I'll paste it:

-

---

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 problem has arisen because, within the database interface,

one of the data buffers made available for the INSERT (UPDATE)

is longer than the maximum defined in the database.

On the other hand, it may be that the length in the NAMETAB

does not match the maximum length defined in the database.

(In this case, the length in the NAMETAB is longer.)

-

---

Thanks in advanced.

[Former Member]

Do you know how can I increase this parameter??

[ThomasZloch]

Sorry, we have left the area of ABAP expertise here

I'll ask moderators to move your question to

You could also open a message to SAP in the Support Portal if all else fails.

Thomas

[fidel_vales]

Hello,

The part of the dump is not clear, it does not indicates the problem.

I'd suggest two things

1) zip the complete dump and upload it somewhere in the web (rapidshare, megaupload or ....) so we can look at the complete dump (and you do not overload the forum)

2) take a look at the system log of the server where the problem happened. Should be some other information at the same of the dump that could bring some light