DB import - failing packages on unicode conversion

[symon_braunbaer]

Dear experts,

I am finally doing the import of the unicode system and I am facing a problem with 2 failing packages.

They are nametab tables. Here is the error from the log file:

(SQL) INFO: Searching for SQL file SQLFiles.LST

(SQL) INFO: SQLFiles.LST not found

(SQL) INFO: Searching for SQL file /<export_dir>/ABAP/DB/SQLFiles.LST

(SQL) INFO: found /<export_dir>/ABAP/DB/SQLFiles.LST

(SQL) INFO: Trying to open /<export_dir>/ABAP/DB/SQLFiles.LST

(SQL) INFO: /<export_dir>/ABAP/DB/SQLFiles.LST opened

(SQL) INFO: Searching for SQL file SSEXC.SQL

(SQL) INFO: SSEXC.SQL not found

(SQL) INFO: Searching for SQL file /<export_dir>/ABAP/DB/ORA/SSEXC.SQL

(SQL) INFO: found /<export_dir>/ABAP/DB/ORA/SSEXC.SQL

(SQL) INFO: Trying to open /<export_dir>/ABAP/DB/ORA/SSEXC.SQL

(SQL) INFO: /<export_dir>/ABAP/DB/ORA/SSEXC.SQL opened

(DB) INFO: DDXTT created #20150804130134

(RFF) ERROR: no entry for table "DDXTT" in "/<export_dir>/ABAP/DATA/DDXTT.TOC", aborting the task

(DB) INFO: disconnected from DB

/usr/sap/<SID>/SYS/exe/uc/sunx86_64/R3load: job finished with 1 error(s)

/usr/sap/<SID>/SYS/exe/uc/sunx86_64/R3load: END OF LOG: 20150804130134

When I check the file /<export_dir>/ABAP/DATA/DDXTT.TOC

vn: R7.20/V1.6

id: b5b471f500000043

cp: 4103

data_with_checksum

tab: [HEADER]

fil: DDXTT.001 1024

1 1

eot: #0 rows 20150724092718

tab: DDXTT_1B

eot: #0 rows 20150724092732

eof: #20150724092732

It doesn't contain an entry for table DDXTT, but for table DDXTT_1B !!! Does anyone have a clue

what is going on? I have checked on other systems and table DDXTT_1B is not existing, and table

DDXTT is completely empty.

I have also exactly the same problem for table DDXTT_CONV_UC, in the corresponding TOC file

it is listed as:

tab: DDXTT_2B

eot: #0 rows 20150724112153

I thought of a bug in R3load, but I am using kernel 7.21 EXT patch 402 and R3load patch 419.

I only found SAP notes about trouble with earlier kernel patches, like note 1905316 for example

which mentions patch 134 of this kernel.

Also, when I was generating the unicode nametabs in the non-unicode system, it went all fine

and there were no errors...

So what to do now ? I can think of two possible solutions, except for repeating the export:

1) Modify the .TSK file and set the line D DDXTT I err to status ok. I think this should be OK, as

the table is empty anyway.

2) Modify the .TOC file and change DDXTT_1B to DDXTT, as table DDXTT_1B is not existing.

PLEASE kindly help me to sort out this issue! Many thanks in advance!

[former_member186845]

Hello Symon Braunbaer,

The issue you are facing can happen when you use an old version of kernel to run the export and import. When you execute the export with an old kernel version, it can cause issues during the creation of <package>.TOC and <package>.STR files, which impacts the import.

All the tables from SAPNTAB should be into SAPSDIC or SAPNTAB packaged (depending of SAP system NetWeaver version).

Regards,

Henrique Girardi

SAP Active Global Support

-------------------------------------

#2081285 - How to enter good search terms to an SAP search?

https://service.sap.com/sap/support/notes/2081285

Software Provisioning Manager Troubleshooting documents:

http://scn.sap.com/docs/DOC-62646

Find us:

https://www.facebook.com/SapProductSupport

https://twitter.com/SAPSupportHelp

[Former Member]

Hello Symon,

My reply will probably come too late for you.

As James says, it's not a Oracle problem. For me it seems to be a bug in the R3load and this should be reported to SAP.

In order for you to move forward, all you need to do is set the entries to "ign" in the .TSK file and then your import will complete. The entries will be flagged in the invalid_objects.txt files and the end of operations via sapinst.

As you have correctly seen, there are no entries exported for these two tables as there is a intricate table exchange during the export DDXTT_1B / DDXTT_2B (where the number represents a bytes).

Note 932779 explains this is further detail using the DDN* tables as an example.

I hope this sheds a bit of light on your problem and the way forward.

Kind Regards,

Amerjit

[JamesZ]

Hi,

I assume you are using SWPM/SAPINST to do the import, then I have to say this is not an oracle problem. You may reach sap bc-ins-mig support team or post your question in sap netweaver forum?

Best regards,

James