Cannot find some .TOC file in TDSHL homogeneous DB copy

[Former Member]

We are at the import stage of a homogeneous DB copy for an ABAP only BW

system.

This homogeneous copy is a part of a TDMS shell creation.

In import_monitor.log we see errors as follows:

ERROR: 2010-12-29 21:55:19 com.sap.inst.migmon.LoadTask run

Loading of 'SAPDDIM' import package is interrupted with exception.

java.io.FileNotFoundException: DATA/SAPDDIM.TOC

at com.sap.inst.migmon.LoadTask.writePathEntry

(LoadTask.java:1029)

at com.sap.inst.migmon.LoadTask.createCommandFile

(LoadTask.java:736)

at com.sap.inst.migmon.LoadTask.processPackage

(LoadTask.java:318)

at com.sap.inst.migmon.LoadTask.run(LoadTask.java:195)

at java.lang.Thread.run(Thread.java:534)

at com.sap.inst.lib.util.ThreadDispatcher$ThreadWrapper.run

(ThreadDispatcher.java:113)

ERROR: 2010-12-29 21:55:19 com.sap.inst.migmon.LoadTask run

Loading of 'SAPDFACT' import package is interrupted with exception.

java.io.FileNotFoundException: DATA/SAPDFACT.TOC

at com.sap.inst.migmon.LoadTask.writePathEntry

(LoadTask.java:1029)

at com.sap.inst.migmon.LoadTask.createCommandFile

(LoadTask.java:736)

at com.sap.inst.migmon.LoadTask.processPackage

(LoadTask.java:318)

at com.sap.inst.migmon.LoadTask.run(LoadTask.java:195)

at java.lang.Thread.run(Thread.java:534)

at com.sap.inst.lib.util.ThreadDispatcher$ThreadWrapper.run

(ThreadDispatcher.java:113)

In the exported dump directory, we truly cannot find above TOC files.

We did not have any ERROR during the export phase.

According to my experience, this might be caused by the fact that this ABAP BW system has a JAVA add-on

on a different server with a dfferent SID than the ABAP SID -- but the JAVA DB is in the same database as the ABAP but with a different schema. Therefore when we do export source system->central system->ABAP based, those TOC files could not be created. However I do not have the document created in my previous project, I cannot verify my impression.

Are SAPDDIM and SAPDFACT standard SAP objects?

Please help input your opinions.

Thanks!

[Former Member · Accepted solution]

Hi,

The reason for this behaviour is that there was no data to be exported (due to the exclusion used by tdms) for this goup.

This results sometimes in the issue that no TOC files are being created.

You can copy an exisiting toc file for the run -> rename it to the approbriate name and then remove the table references from within this new toc file! -> restart the import.

!!! Do not change the STR file!!

That should work.

Best Regards

Joerg

[Former Member]

Hi,

I faced this error and SAP support asked me to remove few rows in SAPDFACT.TSK and SAPDDIM.TSK.

Edit the SAPDFACT.TSK and SAPDDIM.TSK files to remove all the lines starting with "D" and try to re-execute the imports.

Regards

AnoopKrishnan

Edited by: Anoop Raveendran on Dec 31, 2010 1:11 PM

[Former Member]

Pankaj and Anoop:

Thank you for help!

Will this removal of D line cause any data inconsistency?

We have a quite few packages with the same problem:

SAPZPC11

SAPZIIAR

SAPZIFAJ

SAPZIFAE

SAPZPSRV

...

We will follow your instruction and do again.

Our DMIS_CNT is at SP15. Both sender and target are NW701.

Happy New Year!

[Former Member]

Pankaj and Anoop:

1) I have removed all lines starting with 'D ' in the problem *.TSK files and run again.

However, it's still looking for the non-existing *.TOC file. Here is the log:

/usr/sap/QAS/SYS/exe/run/R3load: START OF LOG: 20101231190309

/usr/sap/QAS/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/

R3ldmain.c#5 $ SAP

/usr/sap/QAS/SYS/exe/run/R3load: version R7.01/V1.4

Compiled Feb 24 2009 21:41:52

/usr/sap/QAS/SYS/exe/run/R3load -i SAPZPVAL.cmd -dbcodepage 1100 -l SAPZPVAL.log

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(TFH) ERROR: Unable to open /shellexport/ABAP/DATA/SAPZPVAL.TOC

(TFH) ERROR: OS error message: No such file or directory

/usr/sap/QAS/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/QAS/SYS/exe/run/R3load: END OF LOG: 20101231190309

2) Therefore I create a dummy file as follows:

touch /shellexport/ABAP/DATA/SAPZPVAL.TOC

However, it fails again with logs as follows:

/usr/sap/QAS/SYS/exe/run/R3load: START OF LOG: 20101231190359

/usr/sap/QAS/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/

R3ldmain.c#5 $ SAP

/usr/sap/QAS/SYS/exe/run/R3load: version R7.01/V1.4

Compiled Feb 24 2009 21:41:52

/usr/sap/QAS/SYS/exe/run/R3load -i SAPZPVAL.cmd -dbcodepage 1100 -l SAPZPVAL.log

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(RD) ERROR: unexpected end of file "/shellexport/ABAP/DATA/SAPZPVAL.TOC"

/usr/sap/QAS/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/QAS/SYS/exe/run/R3load: END OF LOG: 20101231190359

3) here is the TSK file

more SAPZPVAL.TSK (new, without lines starting with D)

T /BIC/AZPD_IVAL00 C xeq

P /BIC/AZPD_IVAL00~0 C xeq

T /BIC/AZPD_IVAL40 C xeq

P /BIC/AZPD_IVAL40~0 C xeq

more backup_TSK/SAPZPVAL.TSK (old, w/ the lines starting with D)

T /BIC/AZPD_IVAL00 C xeq

D /BIC/AZPD_IVAL00 I xeq

P /BIC/AZPD_IVAL00~0 C xeq

T /BIC/AZPD_IVAL40 C xeq

D /BIC/AZPD_IVAL40 I xeq

P /BIC/AZPD_IVAL40~0 C xeq

In the import_monitor.log, we see:

TRACE: 2011-01-02 18:21:29 com.sap.inst.migmon.LoadTask run

Loading of 'SAPZPVAL' import package is started.

INFO: 2011-01-02 18:21:29 com.sap.inst.migmon.LoadTask processPackage

Task file '/oracle/backup2/W7C/sapinst_instdir/SAPZPVAL.TSK' from package 'SAPZP

VAL' contains no tasks with data type (D).

4) We have multiple packages with the same ERROR. So far none of them is fixed by removing the D lines.

Above are just examples.

5) BTW, DbSl Trace: ORA-1403 when accessing table SAPUSER is NOT a concern here because the logs

of some successfully imported packages also have the same message.

Could you please tell whether you had the same situation? ?

Thanks!

[Former Member]

Hi,

I am not sure about other packages, but the issue with SAPDDIM and SAPDFACT should go way after removing those "D" rows.

Please ensure that you have gone through all the pre-processing tasks for BW system export mentioned in the system copy guide.

Also i would suggest opening up a OSS message with SAP.

Regards

AnoopKrishnan

[Former Member]

So many packages should not have this issue, I think there is something else wrong. I think the exports didnt happen correctly. Please review your exports steps to see if everything happened correctly.

Also let me know the size of export dump.

[Former Member]

Pankaj and Anoop:

The export dump size is 17GB. The sender total DB sizes 15TB.

The export is free of any error.

Thanks!

[Former Member]

How much total time did it take to do the exports? I am doubting that the size of exports is too small.

[Former Member]

The total time from starting import_monitor.sh to all packages exported was 4.5 hours.

Thanks!

[Former Member]

cc122010:

When importing , make sure that in your import_monitor_cmd.properties, ddlFile= .../ExportDump/ABAP/DB/ORA/DDLORA.TPL,

not ddlFile=.../sapinst_inst/DDLORA.TPL.

Regards.

[Former Member]

During exports did you carry out the step to create DDL statements as mentioned in System copy guide for BI system. If not then that could be a reason for the problem.

[Former Member]

Pankaj:

Thanks for replying.

We have done TDSHL for the same TDMS sender two times: one with the execution of SMIGR_CREATE_DDL and one without the execution of SMIGR_CREATE_DDL.

The result of the export is the same:

1) if the data classes (tablespaces) have ONLY /BI0/* or /BIC/* tables, no *.TOC files generated for those data classes (tablespaces);

2) if the data classes have /BI0/* or /BIC/* tables AS WELL AS other tables, the generated *.TOC files does NOT contain

any /BIC/* or /BI0/* tables except /BIC/E100094 which is the only exception.

Please advise. Thanks!

[Former Member]

In which SP release of TDMS_CNT component is your sender and receiver system. To permanently solve this you may consider upgrading to SP 16 of TDMS_CNT.

As you are already in middle of the Shell package and facing this error in import step it is recommended that you search of corresponding <tabart>.TSK file for each error about <tabart>.TOC file and then remove all the text lines starting with 'D' -

D <OBJECT> I xeq lines can be removed in the corresponding <tabart>.tsk (in your case SAPDDIM.TSK and SAPDFACT.TSK)

Once this is done proceed with import.

P.S: this change needs to be done in the TSK files generated for the import process and not for the export.