cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with installation of NW 7.0 EHP3 (Linux + DB2)

0 Kudos

Hello.

I am doing a fresh installation of NW 7.0 EHP3. Currently I am stuck at phase Import ABAP. I dont know how to fix this...

I've found this SNOTE that seems to be the exact problem:

https://launchpad.support.sap.com/#/notes/0001970577

"To perform the merge manually:

execute the following command in sapinst_instdir, where the TSK and TSK.bck files are existing, with <sid>adm user for every failed packages (TABART) separately:

on Windows: "R3load.exe -merge_only <SAPTABART>.TSK"
on Unix: "R3load -merge_only <SAPTABART>.TSK

or

to perform the merge by migration monitor automatically:

insert the parameter "-merge_bck" into migration monitor property file, if it was not set:

stop sapinst incl. migration monitor if it is was started manually
insert the R3load parameter "-merge_bck" into <export/import>_monitor_cmd.properties into the line: loadArgs=
like: loadArgs=-stop_on_error -merge_bck
restart sapinst incl. migration monitor if it is was started manually."

So tried both but none of that worked.

problem are 3 files

SAPNTAB.TSK
SAPSSEXC.TSK
SAPSPROT.TSK

manual merge:

> R3load -merge_only SAPNTAB.TSK
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
R3load: START OF LOG: 20190715120734

R3load: sccsid @(#) $Id: //bas/722_STACK/src/R3ld/R3load/R3ldmain.c#2 $ SAP
R3load: version R7.20/V1.6 [UNICODE]
Compiled Sep 20 2016 16:34:00
R3load -merge_only SAPNTAB.TSK

(PRC) INFO: working directory "/sapcommon/sapinst/LES/sapinst_instdir/NW703/AS-ABAP/DB6/CENTRAL"
(TSK) WARNING: user requested automatic merge of SAPNTAB.TSK and SAPNTAB.TSK.bck
This may indicate that there is already a job processing
the same task file
Merging the task and .bck files can be dangerous if somebody
fiddled with the files or file system errors occurred

R3load: job completed
R3load: END OF LOG: 20190715120734

And same for

SAPSSEXC.TSK
SAPSPROT.TSK

I even edited import_monitor_cmd.properties according to "import_monitor_cmd.properties"

> cat import_monitor_cmd.properties
dbType=DB6
importDirs=/sapcommon/media/INEX_LOGO/export/51043228/DATA_UNITS/EXP1:/sapcommon/media/INEX_LOGO/export/51043228/DATA_UNITS/EXP2:/sapcommon/media/INEX_LOGO/export/51043228/DATA_UNITS/EXP3
installDir=/sapcommon/sapinst/LES/sapinst_instdir/NW703/AS-ABAP/DB6/CENTRAL
orderBy=
r3loadExe=/usr/sap/LES/SYS/exe/run/R3load
tskFiles=yes
extFiles=no
dbCodepage=4103
jobNum=3
monitorTimeout=30
loadArgs=-stop_on_error -merge_bck -loadprocedure fast LOAD:COMPRESS_ALL:DEF_CRT
trace=all

Of course I've stopped SWPM while doing this.

When I run it again, I end with the same error...

And what's interesting is that when I check log files in the printscreen (import_monitor.log)

INFO: 2019-07-12 20:28:59
Import Monitor is started.

CONFIG: 2019-07-12 20:28:59
Application options:
dbCodepage=4103
dbType=DB6
extFiles=no
importDirs=/sapcommon/media/INEX_LOGO/export/51043228/DATA_UNITS/EXP1:/sapcommon/media/INEX_LOGO/export/51043228/DATA_UNITS/EXP2:/sapcommon/media/INEX_LOGO/export/51043228/DATA_UNITS/EXP3
installDir=/sapcommon/sapinst/LES/sapinst_instdir/NW703/AS-ABAP/DB6/CENTRAL
jobNum=3
loadArgs=-stop_on_error -loadprocedure fast LOAD:COMPRESS_ALL:DEF_CRT
monitorTimeout=30
orderBy=
r3loadExe=/usr/sap/LES/SYS/exe/run/R3load
sapinst=
trace=all
tskFiles=yes

in loadArgs there is no "-merge_bck" even though I have eddited "import_monitor_cmd.properties" and put "-merge_bck" into "loadArgs" as described in SNOTE 1970577

this is from monitor_cmd.properties (just loadArgs listed here, rest of config is not interesting in this case I guess):

loadArgs=-stop_on_error -merge_bck -loadprocedure fast LOAD:COMPRESS_ALL:DEF_CRT

I would be glad for some tips.

Thank you.

Accepted Solutions (0)

Answers (2)

Answers (2)

alichtenau
Advisor
Advisor

Good morning Tomáš,

I assume you noticed below three files from import_monitor.log:

  • SAPNTAB.TSK
  • SAPSSEXC.TSK
  • SAPSPROT.TSK

Can you please attach the respective *.log files? They contain the error for the cancellation.


Many thanks and best regards,
Andreas

0 Kudos

Hello.


Thanks for the response 🙂

Here it is:

> cat SAPNTAB.TSK
T SVERS C ok
P SVERS~0 C ok
D SVERS I ok
T DDNTF C ok
P DDNTF~0 C ok

> cat SAPSSEXC.TSK
T AAB_ID_PROP C ok
P AAB_ID_PROP~0 C ok
D AAB_ID_PROP I ok
T AAB_ID_PROPT C ok
P AAB_ID_PROPT~0 C ok

> cat SAPSSEXC.TSK
T AAB_ID_PROP C ok
P AAB_ID_PROP~0 C ok
D AAB_ID_PROP I ok
T AAB_ID_PROPT C ok
P AAB_ID_PROPT~0 C ok
sosnsap066:lesadm 55> cat SAPSPROT.TSK
T /SDF/DB6ALRTCFG C ok
P /SDF/DB6ALRTCFG~0 C ok
D /SDF/DB6ALRTCFG I ok
T /SDF/DB6PMCD C ok
P /SDF/DB6PMCD~0 C ok
D /SDF/DB6PMCD I ok
T /SDF/DB6PMCN C ok
P /SDF/DB6PMCN~0 C ok
D /SDF/DB6PMCN I ok
T /SDF/DB6PMHT_HD C ok
P /SDF/DB6PMHT_HD~0 C ok
D /SDF/DB6PMHT_HD I ok
T /SDF/DB6PMHXP C ok
P /SDF/DB6PMHXP~0 C ok
D /SDF/DB6PMHXP I ok
T /SDF/DB6PMPROT C ok
P /SDF/DB6PMPROT~0 C ok
D /SDF/DB6PMPROT I ok
T ADAA C ok
P ADAA~0 C ok
D ADAA I ok
T ADACACHE C ok
P ADACACHE~0 C ok
D ADACACHE I ok
T AMASCH C ok
P AMASCH~0 C ok
D AMASCH I ok
T AMASTA C ok
P AMASTA~0 C ok
D AMASTA I ok
T AMASUR C ok
P AMASUR~0 C ok
D AMASUR I ok
T AMATR C ok
P AMATR~0 C ok
D AMATR I ok
T AMATRT C ok
P AMATRT~0 C ok
D AMATRT I ok
T AMDES C ok
P AMDES~0 C ok
D AMDES I ok
T AMDS C ok
P AMDS~0 C ok
I AMDS~1 C ok
D AMDS I ok
T AMDT C ok
P AMDT~0 C ok
D AMDT I ok
T AMESISTA C ok
P AMESISTA~0 C ok
D AMESISTA I ok
T AMESISUB C ok
P AMESISUB~0 C ok
D AMESISUB I ok
T AMHD C ok
P AMHD~0 C ok
I AMHD~RID C ok
I AMHD~STA C ok
I AMHD~USR C ok
D AMHD I ok
T AMHDT C ok
P AMHDT~0 C ok
I AMHDT~PID C ok
I AMHDT~PTX C ok
D AMHDT I ok
T AMIDC C ok
P AMIDC~0 C ok
D AMIDC I ok
T AMIDT C ok
P AMIDT~0 C ok
D AMIDT I ok
T AMIDTP C ok
P AMIDTP~0 C ok
D AMIDTP I ok
T AMPRO C ok
P AMPRO~0 C ok
D AMPRO I ok
T AMRFC C ok
P AMRFC~0 C ok
D AMRFC I ok
T AMSK C ok
P AMSK~0 C ok
D AMSK I ok
T AMSP C ok
P AMSP~0 C ok
D AMSP I ok
T AMSSU C ok
P AMSSU~0 C ok
D AMSSU I ok
T AMSTA C ok
P AMSTA~0 C ok
D AMSTA I ok
T AMSTANO C ok
P AMSTANO~0 C ok
D AMSTANO I ok
T AMSUR C ok
P AMSUR~0 C ok
D AMSUR I ok
T AMTINFO C ok
P AMTINFO~0 C ok
D AMTINFO I ok
T AMTSU C ok
P AMTSU~0 C ok
D AMTSU I ok
T ATCKONTEXT C ok
P ATCKONTEXT~0 C ok
D ATCKONTEXT I ok
T AUT_D_ARCH_HIST C ok
P AUT_D_ARCH_HIST~0 C ok
D AUT_D_ARCH_HIST I ok
T AUT_D_DBTABLOG C ok
P AUT_D_DBTABLOG~0 C ok
I AUT_D_DBTABLOG~KEY C ok
D AUT_D_DBTABLOG I ok
T BAL_AMODAL C ok
P BAL_AMODAL~0 C ok
D BAL_AMODAL I ok
T BAL_INDX C ok
P BAL_INDX~0 C ok
D BAL_INDX I ok
T BGRFC_EVENT_PARM C ok
P BGRFC_EVENT_PARM~0 C ok
D BGRFC_EVENT_PARM I ok
T BTCDELAY C ok
P BTCDELAY~0 C ok
D BTCDELAY I ok
T CCCFLOW C ok
P CCCFLOW~0 C ok
D CCCFLOW I ok
T CCOPTION C ok
P CCOPTION~0 C ok
D CCOPTION I ok
T CCPROCTAB C ok
P CCPROCTAB~0 C ok
D CCPROCTAB I ok
T CCPROF C ok
P CCPROF~0 C ok
D CCPROF I ok
T CCSELKEY C ok
P CCSELKEY~0 C ok
D CCSELKEY I ok
T CCSELTAB C ok
P CCSELTAB~0 C ok
I CCSELTAB~STA C ok
D CCSELTAB I ok
T DB6ALRTCFG C ok
P DB6ALRTCFG~0 C ok
D DB6ALRTCFG I ok
T DB6ALRTCT C ok
P DB6ALRTCT~0 C ok
D DB6ALRTCT I ok
T DB6ALRTMSG C ok
P DB6ALRTMSG~0 C ok
D DB6ALRTMSG I ok
T DB6AUDITDT C ok
P DB6AUDITDT~0 C ok
D DB6AUDITDT I ok
T DB6AUDITHD C ok
P DB6AUDITHD~0 C ok
D DB6AUDITHD I ok
T DB6GSDTBS C ok
P DB6GSDTBS~0 C ok
D DB6GSDTBS I ok
T DB6HISTBS C ok
P DB6HISTBS~0 C ok
I DB6HISTBS~02 C ok

I was running out of time, so I was trying how to "hack it".

Before my hack, this looked different, it crashed with error after "failed: 3"

  • SAPNTAB.TSK
  • SAPSSEXC.TSK
  • SAPSPROT.TSK

Error produced also

SAPNTAB.TSK.bck ( also for SAPSSEXC.TSK and SAPSPROT.TSK)

I tried to rename SAPNTAB.TSK.bck to SAPNTAB.TSK.bck_test and it didnt end in such a fast error.

It helped and count went to somethink like 18 completed abd 11 failed. I did my hack with renaming again and managed to get to 25 comleted and just 4 failed.

But my hack doesnt work anymore, so I can' move further.

Keep in mind that my hacks could have modified

SAPNTAB.TSK
SAPSSEXC.TSK
SAPSPROT.TSK

Ive posted how those files look like now, not before my hacks. Maybe they were same, but I can't tell that with certainty.

The hack was, again, to rename <FILE_NAME>.TSK.bck (these bck versions of files were produced by errors) to something else, in my case <FILE_NAME>.TSK.bck_test.

0 Kudos

I hope my answer did not dissapear...

I guess also my answers need moderation? Little bit annoying for all of my posts in this thread to be moderated (delay between me posting and people seeying it).

alichtenau
Advisor
Advisor
0 Kudos

Hi Tomáš,

did you check why it failed?
Can you please attach the respective *.log file of the *.TSK file?


Maybe the error was simple and "hacking" was not even necessary. 🙂

Cheers,
Andreas