IMPORT ABAP IS RUNNING FOR LONG TIME

[Former Member]

Hi All,

We have started our AS migration ECC 6.0 from windows mssql as db to linux maxdb as db.

we have taken export from the source system successfully now while importing into target system.

import abap had run more than a day in the same phase, there were no logs every thing was fine, then we thought of restarting the system, after restarting the system there were few errors. but still running the same job with out any change

here i paste the logs

i have manually started db with startdb command after system restart.

ImportMonitor.console.log

Loading of 'D010TAB' import package: ERROR

Import Monitor jobs: running 9, waiting 71, completed 52, failed 1, total 133.

Loading of 'SAPAPPL2_4' import package: ERROR

Loading of 'SAPAPPL0_14' import package: ERROR

Import Monitor jobs: running 6, waiting 71, completed 52, failed 4, total 133.Loading of 'SAPAPPL0_15' import package: ERROR

Import Monitor jobs: running 6, waiting 71, completed 52, failed 4, total 133.

Loading of 'SAPAPPL2_5' import package: ERROR

Import Monitor jobs: running 4, waiting 71, completed 52, failed 6, total 133.

Import Monitor jobs: running 4, waiting 71, completed 52, failed 6, total 133.

Loading of 'SAPAPPL2_10' import package: ERROR

Import Monitor jobs: running 4, waiting 71, completed 52, failed 6, total 133.

Loading of 'SAPAPPL2_13' import package: ERROR

Import Monitor jobs: running 3, waiting 71, completed 52, failed 7, total 133.

Loading of 'SAPAPPL0_6' import package: ERROR

Import Monitor jobs: running 2, waiting 71, completed 52, failed 8, total 133.

Loading of 'SAPAPPL2_12' import package: ERROR

Import Monitor jobs: running 1, waiting 71, completed 52, failed 9, total 133.

Loading of 'SAPAPPL2_14' import package: ERROR

Import Monitor jobs: running 0, waiting 71, completed 52, failed 10, total 133.

Import Monitor jobs: running 1, waiting 70, completed 52, failed 10, total 133.

Import Monitor jobs: running 2, waiting 69, completed 52, failed 10, total 133.

Import Monitor jobs: running 3, waiting 68, completed 52, failed 10, total 133.

Import Monitor jobs: running 4, waiting 67, completed 52, failed 10, total 133.

Import Monitor jobs: running 5, waiting 66, completed 52, failed 10, total 133.

Import Monitor jobs: running 6, waiting 65, completed 52, failed 10, total 133.

Import Monitor jobs: running 7, waiting 64, completed 52, failed 10, total 133.

Import Monitor jobs: running 8, waiting 63, completed 52, failed 10, total 133.

Import Monitor jobs: running 9, waiting 62, completed 52, failed 10, total 133.

Import Monitor jobs: running 10, waiting 61, completed 52, failed 10, total 133.

SAPAPPL2_14.log

usr/sap/TE1/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP

/usr/sap/TE1/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jan 23 2008 17:39:05

/usr/sap/TE1/SYS/exe/run/R3load -i SAPAPPL2_14.cmd -dbcodepage 4103 -k 1G5fdEM50DmIrBzjt6TE5Pae -l SAPAPPL2_14.log -nolog -c 10000

(DB) INFO: connected to DB

(DB) INFO: The MaxDB logwriter is switched off#20110621032216

(GSI) INFO: dbname = "TE1 "

(GSI) INFO: vname = "ADABAS D "

(GSI) INFO: hostname = "sgwp-s-relte1 "

(GSI) INFO: sysname = "Linux"

(GSI) INFO: nodename = "sgwp-s-relte1"

(GSI) INFO: release = "2.6.32.12-0.7-xen"

(GSI) INFO: version = "#1 SMP 2010-05-20 11:14:20 +0200"

(GSI) INFO: machine = "x86_64"

(TSK) ERROR: file /tmp/sapinst_instdir/ERP/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/SAPAPPL2_14.TSK.bck already seems to exist

a previous run may not have been finished cleanly

file /tmp/sapinst_instdir/ERP/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/SAPAPPL2_14.TSK possibly corrupted

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

/usr/sap/TE1/SYS/exe/run/R3load: END OF LOG: 20110621032217

We have done few other systems migration but never faced this king of situation.

please help me in solving this issue

Thanks in advance

Vardhan.

[markus_doehr2]

> Compiled Jan 23 2008 17:39:05

Your R3load is ancient, always use the latest tools to export and import the database, don't use the ones that come with the DVDs, they are too old.

> (TSK) ERROR: file /tmp/sapinst_instdir/ERP/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/SAPAPPL2_14.TSK.bck already seems to exist

> a previous run may not have been finished cleanly

> file /tmp/sapinst_instdir/ERP/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/SAPAPPL2_14.TSK possibly corrupted

I suggest:

- start the import from scratch (delete the system and start over)

- select "start migration monitor manually" during sapinst

- when sapinst requests you to start the import

--> download the latest kernel for the target platform (Linux and MaxDB)

--> exchange R3load and lib_dbsl with the newest versions available

--> configure import options "-c 50000 -merge_bck -loadprocedure fast -force_repeat -para_cnt <number-of-import-processes>" (see also Note 1464560 - FAQ: R3load in MaxDB)

I just want to let you know that you need to buy a migration service before doing production migrations to make sure, everything is in place and properly configured. For the target database MaxDB there's also a migration service available, experts will help you to tune the system during the import phase, watch the system and help to configure the target system.

If you do the migration alone and not through a certified migration consultant the SAP support may bill OSS calls:

Note 82478 - SAP system OS/DB migration

Check also

Note 1007129 - FAQ: DB migration with MaxDB as target

Markus

[Former Member]

But Markus, isn'that a bug ?

[Former Member]

Hi Vardhan,

Restarting the system during the import phase causes inconsistencies. Hence the errors:

ERROR: file /tmp/sapinst_instdir/ERP/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/SAPAPPL2_14.TSK.bck already seems to exist

a previous run may not have been finished cleanly

file /tmp/sapinst_instdir/ERP/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/SAPAPPL2_14.TSK possibly corrupted

For a non-productive system, a risk could have been taken by delteing the TSK.bck file and rerunning the import. But the ideal way would be to restart the import from scratch. The import process could take time depnding upon the size of export. Few pointers to check the long running import job:

- check if proper/recommended JDK is used

- any issues with the database (out of space etc)

- issues on the file system level

Regards,

Srikishan

[Former Member]

Hi Srikishan,

Thanks for the reply, sorry for the late reply,

I have deleted that system and kicked off new import with the same export.

now again in same import abap phase it is running for more than two days in same job.

there are no errors specified in the logs.

this is my disk allocation.

Filesystem Size Used Avail Use% Mounted on

/dev/xvda3 389G 143G 227G 39% /

There is enough disk space.

Thanks!

Vardhan.

[Former Member]

Hi ,

Issue solved .

Disk space was more but.

data size was less

so we increased the data size.

Every thing is fine now.

http://wiki.sdn.sap.com/wiki/display/MaxDB/Dataareafull

we referred the following ling

Thanks!

Vardhan.

[Former Member]

Hi Vardhan,

I'm having the same issue 'Import ABAP step never ends' . I tried to connect the link you mentioned

( http://wiki.sdn.sap.com/wiki/display/MaxDB/Dataareafull) but the link is not working,looks like it may not valid now. Could you please share any other working link or if you can write  few steps how to increase the data size? would be great help.

Thank you,

Nagraj

[Former Member]

Hi Nagraj,

In my case.. to replicate the issue

I have logged in to database using DBMCLI  from Commandprompt/Putty

Dbmcli on SID > db_connect

i got an error data area full.

You can also use the following DBMCLI command to add a new data volume:

dbmcli -d <database_name> -u <dbm_user>,<password>  

db_addvolume DATA <volume_name> <volume_type> <volume_size>

i have added it by using below mentioned command

db_addvolume   DATA   /sapdb/SID/sapdata/DISKD00XX    F   <SIZE>

Where XX is new file number <SIZE> is the size you want to add.

F is Volume type

Please refer the below mentioned link, for further clarification

http://wiki.sdn.sap.com/wiki/display/MaxDB/Data+area+full

Thanks,

Vardhan.