Table DDXTT deleted after "force conversion" trying to solve CONV ENTRY found in it

[Former Member]

Hi guys,

During the upgrade of an ERP system (SAP ECC 6.0 - EHP4 for ERP 6.0 NW701) we had the following error in phase PARCONV_TRANS in module MAIN_TRANSEXEC.

Error Message: Conversion entries have been found in 'T:\\SUM\abap\log\TBATGCHK.LOG' - the file is attached to the body of this post.

SAPuptroubleticket pointed to NCONV00 and NCONV02 logs  (both files also attached) which said that various index and tables were not present in the database.

After some research to solve the problem we found nothing and when in SE14 we forced the conversion for table DDXTT, and repeated the phase

Now the error is the following and we can't do much in ABAP 'cause it's giving DUMPS everywhere, I'm attaching the file DBSQL_TABLE_UNKNOWN.txt

All the files are in the zip folder.

Can you help me please?

Thanks,

Pedro Gonçalves

DBSQL_TABLE_UNKNOWN.txt.zip

NCONV00.txt.zip

DDXTTCNT.txt.zip

[Former Member · Accepted solution]

Hi Pedro,

Were you able to get a solution for your issue?

Thanks,

Manas

[Former Member · Accepted solution]

Sorry Manas for answering this late.

Yes, my probem was solved

In fact I was having problems in 2 tables:

DDXTT

SUSAGE

1) Table DDXTT was missing after we forced its adjustment, but because table QCMDDXTT during upgrade accomodates its data, I was able to re-create table DDXTT from the latter and have it populated with its data also.

2) As for table SUSAGE because it stopped on step 5 of the conversion, it was in dictionary but not in database, its data was in QCM8SUSAGE table, so...

a) I backed up QCM8SUSAGE data into a new table I created for that (BKSUSAGE)

b) I droped and created SUSAGE again with same structure as QCM8SUSAGE.

You see, in this moment of the conversion, table SUSAGE changes its 2 last columns datatype from FLOAT to Decimal FLOAT, so QCM8SUSAGE already has those columns datatype changed, and that's why I have re-created SUSAGE based on the structure of QCM8SUSAGE instead of QCMSUSAGE which has the last 2 fields still in FLOAT datatype.

3) Then I followed the correct answer from SCN's thread 3874258 - Error on Table QCM8TARCHE during MAIN_TRANSEXEC... | SCN

Solution:

se14 -> susage -> unlock table -> yes

se14 -> Extras -> Invalid temp.

-> Select QCM8USAGE and QCMSUSAGE -> Delete

se11 -> susage -> activate

4) Click to Repeat the process in SUM

All Good now!

PS: I also read through the following notes:

2219528 - Upgrade issue due to conversion error for table SUSAGE

1248769 - Inconsistency between database and ABAP Dictionary

[Former Member]

HI Pedro,

Looks like the table got deleted from the database. if you are doing it in your test system you can try creating this in DB in SE14 and try.

thanks,

manas

[Former Member]

Thanks Manas,

The problem is that although it's a test system, it has valuable data, that must be preserved no matter what.

1) Looking through some SAP notes, I found that in the upgrade process the table DDXTT unloads data to table QCMDDXTT, so looking to the upgrade DDXTTCNT.LOG it states the following:

1 ETQ000 ==================================================

1 ETQ399 Executing SQL script '..\var\DDXTTCNT.XQL'.

2 ETQ399 Connecting to database 'mss'.

3 ETQ398 SQL: SELECT MODEFLAG, COUNT(*) FROM DDXTT GROUP BY MODEFLAG

4 ETQ393 START SELRESULT01>>

4 ETQ010 Date & Time: 20160711170356 

4 ETQ394 "V","10240"

4 ETQ394 "A","526043"

4 ETQ394 "X","3133"

4 ETQ394 "W","37"

4 ETQ394 "F","14190"

4 ETQ395 END SELRESULT01>>

1 ETQ000 ==================================================

4 ETQ010 Date & Time: 20160711170357 

1 ETQ003 exit code: "0"

2) Now, because table DDXTT is not in the database anymore, being locked and all, with a restart log pending... I did the same select statement against that QCMDDXTT table, and guess what? It's a spitting image of the DDXTT.

So, now my question is, can I re-create table DDXTT and load it with QCMDDXTT data which holds the same data it had before it was deleted?

If so, please guide me trough the commands I have to do achieve that via MSSQL SERVER STUDIO sql query.

Thanks,

Pedro

[Former Member]

Hi Pedro,

In this situation my approach will be to restore the pre-downtime backup, proceed and then fix the issue which occured during PARCONV_TRANS and avoid doing any conversion manually in SE14.

But before doing that I will definitely try to create the Table in DB using SE14 and see if that helps.

You may also want to open a message with SAP.

Thanks,

Manas

[Former Member]

here are the other files.

Thanks in advance.

Pedro Gonçalves

NCONV02.txt.zip

TBATGCHK.txt.zip

SAPup_troubleticket.txt.zip

[manish_singh13]

Hi Pedro,

Could you please upload latest PARCONV phase log entries also.

Thanks,

Manish

[Former Member]

Ofcourse Manish,

It's attached.

Thanks.

PARCONV.txt.zip

[Former Member]

Hi Pedro,

What do you see when you do the Database & Runtime Consistency check for DDXTT in SE14.

Thanks,

Manas

[Former Member]

Hi Manas,

Database Object Check = Table is not created in the database

As for Runtime Object Check = it shows me the following

Thanks,

Pedro