cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Error during a SAP Installation - Import ABAP (SAPAPPL2)

joo_migueldimas
Active Participant

on ‎08-10-2011 2:49 AM

0 Kudos

Hello,

Iu00B4m facing with an error during an installation of SAP ECC 6.0 SR3... in phase Import ABAP.

I checked sapinst.log:

INFO 2011-08-10 02:04:27.328
Working directory changed to Z:\usr\sap\SAPinst\ERP\SYSTEM\DB4\CENTRAL\AS.

INFO 2011-08-10 02:04:27.348
Removed environment variable JANITOR_400 from current process environment.

INFO 2011-08-10 02:04:27.578
Output of Z:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.

WARNING 2011-08-10 02:08:03.879
Execution of the command "Z:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output: 
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20110312 (JIT enabled)
J9VM - 20110202_74499_BHdSMr
JIT  - 20090210_1447ifx2_r8
GC   - 200902_24)

Import Monitor jobs: running 1, waiting 1, completed 26, failed 0, total 28.
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.

WARNING[E] 2011-08-10 02:08:03.889
CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR 2011-08-10 02:08:04.29
FCO-00011  The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .

In import_monitor.log I see this:

TRACE: 2011-08-10 02:02:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -nojournal

ERROR: 2011-08-10 02:05:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is interrupted with R3load error.
Process '/usr/sap/DEV/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -nojournal' exited with return code -1.
For mode details see 'SAPAPPL2.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

WARNING: 2011-08-10 02:06:15
Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2011-08-10 02:06:15
1 error(s) during processing of packages.

INFO: 2011-08-10 02:06:15
Import Monitor is stopped.

(this message has continuation...)

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (1)

Answers (1)

joo_migueldimas
Active Participant
‎08-10-2011 2:55 AM
0 Kudos

(... continuation)

After I checked the SAPAPPL2.log:

/usr/sap/DEV/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#21 $ SAP
/usr/sap/DEV/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Nov 13 2010 04:30:39
/usr/sap/DEV/SYS/exe/run/R3load -i SAPAPPL2.cmd -dbcodepage 4102 -l SAPAPPL2.log -nojournal 

INFO:  XDNLevelTraceSetLocation: Trace set to: XDNTrace.000824.*
(DB) INFO: connected to DB
(DB) ERROR: DDL statement failed
 (CREATE TABLE "/ASU/CONTENT" ( "SCENARIO" GRAPHIC(20) CCSID 13488 DEFAULT ' ' NOT NULL , "VERSION" GRAPHIC(14) CCSID 13488 DEFAULT ' ' NOT NULL , "GUID" GRAPHIC(32) CCSID 13488 DEFAULT ' ' NOT NULL , "OBJ_TYPE" GRAPHIC(4) CCSID 13488 DEFAULT ' ' NOT NULL , "OBJ_NAME" GRAPHIC(40) CCSID 13488 DEFAULT ' ' NOT NULL , "EXEC_TYPE" GRAPHIC(1) CCSID 13488 DEFAULT ' ' NOT NULL , "EXEC_PHASE" GRAPHIC(1) CCSID 13488 DEFAULT ' ' NOT NULL , "EXEC_SEVERITY" GRAPHIC(1) CCSID 13488 DEFAULT '0' NOT NULL , "EXEC_RUNTIME" GRAPHIC(1) CCSID 13488 DEFAULT '0' NOT NULL , "EXEC_ORDER" GRAPHIC(3) CCSID 13488 DEFAULT '000' NOT NULL , "DESCR_FILENAME" GRAPHIC(255) CCSID 13488 DEFAULT ' ' NOT NULL , "DESCR_MIMETYPE" GRAPHIC(128) CCSID 13488 DEFAULT ' ' NOT NULL , "BDS_DOC_ID" GRAPHIC(42) CCSID 13488 DEFAULT ' ' NOT NULL , "NOTE" GRAPHIC(10) CCSID 13488 DEFAULT '0000000000' NOT NULL , "NOTE_SP_LEVEL" GRAPHIC(10) CCSID 13488 DEFAULT ' ' NOT NULL , "RELFROM" GRAPHIC(10) CCSID 13488 DEFAULT ' ' NOT NULL , "RELFROM_LEVEL" GRAPHIC(10) CCSID 13488 DEFAULT ' ' NOT NULL , "RELTO" GRAPHIC(10) CCSID 13488 DEFAULT ' ' NOT NULL , "RELTO_LEVEL" GRAPHIC(10) CCSID 13488 DEFAULT ' ' NOT NULL , "APPLICATION" GRAPHIC(24) CCSID 13488 DEFAULT ' ' NOT NULL , "COMPONENT" GRAPHIC(30) CCSID 13488 DEFAULT ' ' NOT NULL , "DEP_OBJ_TYPE" GRAPHIC(4) CCSID 13488 DEFAULT ' ' NOT NULL , "DEP_OBJ_NAME" GRAPHIC(40) CCSID 13488 DEFAULT ' ' NOT NULL  ) )
 DbSlExecute: rc = 102
  (SQL error -601)
  error message returned by DbSl:
/ASU/CONTENT in R3DEVDATA  type *FILE    already exists. MSGID= Job=002736/SAPADM/QJVAEXEC
(IMP) INFO: import of /ASU/CONTENT completed (0 rows) #20110810020534

...
...

Table /BEV3/CHA_KOND in R3DEVDATA already has a primary key. MSGID= Job=002736/SAPADM/QJVAEXEC
(DB) ERROR: DDL statement failed
 (CREATE TABLE "/BEV3/CHA_STAT" ( "MANDT" GRAPHIC(3) CCSID 13488 DEFAULT '000' NOT NULL , "DRKGR" GRAPHIC(10) CCSID 13488 DEFAULT ' ' NOT NULL , "TABNAME" GRAPHIC(30) CCSID 13488 DEFAULT ' ' NOT NULL , "FIELDNAME" GRAPHIC(30) CCSID 13488 DEFAULT ' ' NOT NULL  ) )
 DbSlExecute: rc = 102
  (SQL error -601)
  error message returned by DbSl:
/BEV3/CHA_STAT in R3DEVDATA  type *FILE    already exists. MSGID= Job=002736/SAPADM/QJVAEXEC
(IMP) ERROR: DbSlEndModify failed
  rc = 26, table "/BEV3/CHA_STAT"
(DB) ERROR: DDL statement failed
 (ALTER TABLE "/BEV3/CHA_STAT" ADD CONSTRAINT "/BEV3/CHA_STAT+0" PRIMARY KEY ( "MANDT", "DRKGR", "TABNAME", "FIELDNAME" ) )
 DbSlExecute: rc = 99
  (SQL error -624)
  error message returned by DbSl:
Table /BEV3/CHA_STAT in R3DEVDATA already has a primary key. MSGID= Job=002736/SAPADM/QJVAEXEC
(DB) ERROR: DDL statement failed
 (CREATE TABLE "/BEV3/CHBFLDSTAT" ( "MANDT" GRAPHIC(3) CCSID 13488 DEFAULT '000' NOT NULL , "YVORGE" GRAPHIC(4) CCSID 13488 DEFAULT '0000' NOT NULL , "VBKLASSE" GRAPHIC(4) CCSID 13488 DEFAULT ' ' NOT NULL , "VBAKTION" GRAPHIC(10) CCSID 13488 DEFAULT ' ' NOT NULL , "RGIDENT" GRAPHIC(6) CCSID 13488 DEFAULT '000000' NOT NULL , "MUSTER" GRAPHIC(1) CCSID 13488 DEFAULT ' ' NOT NULL , "DYNPRO" GRAPHIC(4) CCSID 13488 DEFAULT '0000' NOT NULL , "FELD" GRAPHIC(61) CCSID 13488 DEFAULT ' ' NOT NULL , "INVISIBLE" GRAPHIC(1) CCSID 13488 DEFAULT '0' NOT NULL , "REQUIRED" GRAPHIC(1) CCSID 13488 DEFAULT '0' NOT NULL , "INPUTT" GRAPHIC(1) CCSID 13488 DEFAULT '0' NOT NULL , "YVERNAM" GRAPHIC(12) CCSID 13488 DEFAULT ' ' NOT NULL , "YVERSDA" GRAPHIC(8) CCSID 13488 DEFAULT '00000000' NOT NULL , "YVAENAM" GRAPHIC(12) CCSID 13488 DEFAULT ' ' NOT NULL , "YVLAEDA" GRAPHIC(8) CCSID 13488 DEFAULT '00000000' NOT NULL  ) )
 DbSlExecute: rc = 102
  (SQL error -601)
  error message returned by DbSl:
/BEV3/CHBFLDSTAT in R3DEVDATA  type *FILE    already exists. MSGID= Job=002736/SAPADM/QJVAEXEC

I almost forgot, I´m performing this sap installation on IBM i (DB4 and i5/OS)

Can you help me please how can I solve this error?!

Thank you very much

Best regards,

João Dimas - Portugal

Show replies
Show replies
Former Member
‎08-10-2011 6:45 AM
0 Kudos

Hi João,

I would guess, that you might have repeated and crashed the installation, as it claims, that these tables do exist already. You should test this with the following SQL:

select * from r3devdata/"/ASU/CONTENT"

Then the log file does not show the "true state of the DB" and therefore you need to do somethng. As every manual patch is pretty risky, when you are not used to, I will not explain any ideas here.

I will stop now with answers as this would be a consulting task, where it is obvious, that some knowledge in the project is currently missing.

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

joo_migueldimas
Active Participant
‎08-10-2011 11:31 AM
0 Kudos

Hello Volker,

Yes, you´re right! I had this issue and what I did was deleted the SAPAPPL2.TSK.bck and SAPAPPL2.TSK files from sapinst_dir.

I retried the installation and now it show me this error!

I did that because I read some threads here in SDN which has this solution... for example the next thread:

The Neelabha Banerjee sugestion...!

Other thread:

Markus Doehr... he sugested to merge... I tried this but without success and so I cleanup.

Any tip? Can someone help me please!

Kind regards,

João Dimas - Portugal

former_member204746
Active Contributor
‎08-10-2011 2:53 PM
0 Kudos

I would delete the database and restart from scratch.

joo_migueldimas
Active Participant
‎08-10-2011 3:48 PM
0 Kudos

Hello Eric,

How can I do that? It is possible to walk back through the installation?

If so, could you guide me please...

Thank you

João Dimas - Portugal

former_member204746
Active Contributor
‎08-10-2011 6:47 PM
0 Kudos

Hi,

check at the end of the installation guide, it contains the uninstall steps.

joo_migueldimas
Active Participant
‎09-02-2011 11:13 AM
0 Kudos

Ok guys, finally this error was solved!

Some problems occurred during this specific task (SAPAPPL2.tsk) which is the task that is responsible for creating tables on database.

I opened a SAP message... and after some changes, we concluded that error was related to some problems in user permissions during the process of recording tables and in other two system parameters, in OS400, the QJOBMSGQMX and QJOBMSGQFL.

The QJOBMSGQFL (Job message queue full action) it had the value *PRTWRAP and I changed it to *WRAP

The QJOBMSGQMX (Maximum size of job message queue) it had the value 16 and I changed it to 64.

I changed both system parameters values, in the following way (with the command: WRKSYSVAL):

wrksysval QJOBMSGQFL
...
wrksysval QJOBMSGQMX

After all these changes, I delete the old installation/database and I restart it from the scratch.

Kind regards,

João Dimas - Portugal

Former Member
‎09-02-2011 11:21 AM
0 Kudos

Thanks a lot for sharing the solution !

Ask a Question