on 02-27-2009 3:07 PM
Hello everyone,
Wow, I had no idea what I was getting myself into with this SAP install. After about 1.5 days of the "Import
ABAP" phase, I am now at "completed 110, failed 1, total 112." As usual, the applicable log excerpts and
system information are listed below. Once again, a big thank you to everyone for helping make this install
a relatively painless and informative exercise.
sapinst.log
[root@xa4-myexaserv AS]# tail -15 sapinst.log
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20070708 (JIT enabled)
J9VM - 20070530_2352_LHdSMr
JIT - r7_level20070315_1745)
Import Monitor jobs: running 1, waiting 1, completed 110, failed 0, total 112.
Loading of 'T100' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 110, failed 1, total 112.
WARNING[E] 2009-02-27 09:28:02.986
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s)
import_monitor.java.log, import_monitor.log.
ERROR 2009-02-27 09:28:03.199
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 .
import_monitor.java.log
[root@xa4-myexaserv AS]# tail import_monitor.java.log
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20070708 (JIT enabled)
J9VM - 20070530_2352_LHdSMr
JIT - r7_level20070315_1745)
Import Monitor jobs: running 1, waiting 1, completed 110, failed 0, total 112.
Loading of 'T100' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 110, failed 1, total 112.
[root@xa4-myexaserv AS]#
import_monitor.log
[root@xa4-myexaserv AS]# tail -n 34 import_monitor.log
INFO: 2009-02-27 09:27:32 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of '/tmp/sapinst_instdir/ERP/SYSTEM/ADA/CENTRAL/AS/DDLADA.TPL' template file is
successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2009-02-27 09:27:33
Data codepage 4103 is determined using TOC file '/tmp/sapInstall/51034985_1/EXP1/DATA/D021T.TOC' for
package 'D021T'.
TRACE: 2009-02-27 09:27:33 com.sap.inst.migmon.LoadTask run
Loading of 'T100' import package is started.
TRACE: 2009-02-27 09:27:33 com.sap.inst.migmon.LoadTask processPackage
Loading of 'T100' import package into database:
/usr/sap/XA4/SYS/exe/run/R3load -i T100.cmd -dbcodepage 4103 -l T100.log -nolog -c 10000
ERROR: 2009-02-27 09:27:34 com.sap.inst.migmon.LoadTask run
Loading of 'T100' import package is interrupted with R3load error.
Process '/usr/sap/XA4/SYS/exe/run/R3load -i T100.cmd -dbcodepage 4103 -l T100.log -nolog -c 10000' exited with return code 2.
For mode details see 'T100.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: 2009-02-27 09:28:02
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-02-27 09:28:02
1 error(s) during processing of packages.
INFO: 2009-02-27 09:28:02
Import Monitor is stopped.
T100.log
[root@xa4-myexaserv AS]# tail -n 38 T100.log
(DB) INFO: COSS~1 created#20090227042904
(DB) INFO: COSS~2 created#20090227043030
(DB) INFO: COSS~9 created#20090227043148
(DB) INFO: DD04L~1 created#20090227043326
(DB) INFO: TPR_XREF_D~OBJ created#20090227043547
DbSl Trace: EXECUTE on connection 0, rc=-10807 (Connection down: [6] connection broken server state
6 )
ERROR : Execute for create index SCPRSKEYS~01 on SCPRSKEYS failed (dbrc=99).
(SQL error -10807)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "SCPRSKEYS~01" ON "SCPRSKEYS" ( "TABLENAME" , "FIRST_KEYFIELD" )
/usr/sap/XA4/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/XA4/SYS/exe/run/R3load: END OF LOG: 20090227045841
/usr/sap/XA4/SYS/exe/run/R3load: START OF LOG: 20090227092733
/usr/sap/XA4/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/XA4/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 17:39:05
/usr/sap/XA4/SYS/exe/run/R3load -i T100.cmd -dbcodepage 4103 -l T100.log -nolog -c 10000
DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:database not running: no
request pipe))
(DB) ERROR: db_connect rc = 256
DbSl Trace: Connect to database failed, rc = -10709 (Connection failed (RTE:database not running: no
request pipe))
(DB) ERROR: DbSlErrorMsg rc = 99
/usr/sap/XA4/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/XA4/SYS/exe/run/R3load: END OF LOG: 20090227092734
System Info:
RHEL 5.2 x86_64
NW_7.0_SR3_Kernel_WINDOWS__LNX_X86
RDBMS_MAXDB_7.6.03_Build_09
SAP_ERP_6.0_SR3_IDES_Inst._Master
IBMJava2-AMD64-142-SDK-1.4.2-9.0.x86_64
-
Please let me know if I left anything important out. Once again, thanks for all the help.
Zach
your database is either:
1. down
2. full
3. malfunctioning
check MaxDB status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the tardy response; I have been going through notes and documentation to try and help myself.
Checking the state of the database....
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4 db_state
OK
State
OFFLINE
Starting the database....
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4 db_start
OK
Checkign the state of the database again....
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4 db_state
OK
State
ADMIN
I'm still receiving the same error message from T100.log. It's entirely possible that I need to add another
data volume. How can I check the memory utilization of the database? I'm receiving the following error
when I try to read the memory utilization.
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4 info DATA
ERR
-24988,ERR_SQL: SQL error
-101,SQL statement not available in this DB mode
Thank you for all the help,
Zach
Edited by: Zachary Shay on Mar 3, 2009 4:26 PM
I've put the database into the proper mode....
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4 db_state -v
OK
State
ONLINE
Log Full = No
Database Full = No
But am still getting the following error when the install attempts the Import ABAP:
An excerpt from the T100.log....
/usr/sap/XA4/SYS/exe/run/R3load: START OF LOG: 20090303110406
/usr/sap/XA4/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/XA4/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 17:39:05
/usr/sap/XA4/SYS/exe/run/R3load -i T100.cmd -dbcodepage 4103 -l T100.log -nolog -c 10000
(DB) INFO: connected to DB
(DB) INFO: The MaxDB logwriter is switched off#20090303110407
ERROR : Execute for create index TPR_XREF_D~OBJ on TPR_XREF_D failed (dbrc=102).
(SQL error -955)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "TPR_XREF_D~OBJ" ON "TPR_XREF_D" ( "OBJECTNAME" , "OBJECTTYPE" )
/usr/sap/XA4/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/XA4/SYS/exe/run/R3load: END OF LOG: 20090303110407
Any suggestions? Thanks,
Zach
Verifying the database state....
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4 db_state
OK
State
ONLINE
Running the database cleanup....
[sdb@xa4-myexaserv bin]$ ./sqlcli -u DEFAULT
Welcome to the MaxDB interactive terminal.
Type: \h for help with commands
\q to quit
sqlcli=> drop index 'TPR_XREF_D~OBJ'
* -10709: Connection failed (RTE:Database name is missing) SQLSTATE:
Zach
Here is some additional information regarding the memory usage in the database....
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4 info DATA
OK
END
Name | Value
Devspace Name = /sapdb/XA4/sapdata/DISKD0001
Total Space (KB) = 15769600
Used Space (KB) = 13240520
Used Space (%) = 83
Free Space (KB) = 2529080
Free Space (%) = 17
Devspace Name = /sapdb/XA4/sapdata/DISKD0002
Total Space (KB) = 15769600
Used Space (KB) = 13398416
Used Space (%) = 84
Free Space (KB) = 2371184
Free Space (%) = 16
Devspace Name = /sapdb/XA4/sapdata/DISKD0003
Total Space (KB) = 15769600
Used Space (KB) = 13619904
Used Space (%) = 86
Free Space (KB) = 2149696
Free Space (%) = 14
Devspace Name = /sapdb/XA4/sapdata/DISKD0004
Total Space (KB) = 15769600
Used Space (KB) = 13758400
Used Space (%) = 87
Free Space (KB) = 2011200
Free Space (%) = 13
Devspace Name = /sapdb/XA4/sapdata/DISKD0005
Total Space (KB) = 15769600
Used Space (KB) = 13422728
Used Space (%) = 85
Free Space (KB) = 2346872
Free Space (%) = 15
Devspace Name = /sapdb/XA4/sapdata/DISKD0006
Total Space (KB) = 15769600
Used Space (KB) = 13611256
Used Space (%) = 86
Free Space (KB) = 2158344
Free Space (%) = 14
Devspace Name = /sapdb/XA4/sapdata/DISKD0007
Total Space (KB) = 15769600
Used Space (KB) = 13470920
Used Space (%) = 85
Free Space (KB) = 2298680
Free Space (%) = 15
Devspace Name = /sapdb/XA4/sapdata/DISKD0008
Total Space (KB) = 15769600
Used Space (KB) = 13427912
Used Space (%) = 85
Free Space (KB) = 2341688
Free Space (%) = 15
Devspace Name = /sapdb/XA4/sapdata/DISKD0009
Total Space (KB) = 15769600
Used Space (KB) = 13258640
Used Space (%) = 84
Free Space (KB) = 2510960
Free Space (%) = 16
Devspace Name = /sapdb/XA4/sapdata/DISKD0010
Total Space (KB) = 15769600
Used Space (KB) = 13378208
Used Space (%) = 84
Free Space (KB) = 2391392
Free Space (%) = 16
Devspace Name = /sapdb/XA4/sapdata/DISKD0011
Total Space (KB) = 15769600
Used Space (KB) = 13547208
Used Space (%) = 85
Free Space (KB) = 2222392
Free Space (%) = 15
Devspace Name = /sapdb/XA4/sapdata/DISKD0012
Total Space (KB) = 15769600
Used Space (KB) = 13351640
Used Space (%) = 84
Free Space (KB) = 2417960
Free Space (%) = 16
Devspace Name = /sapdb/XA4/sapdata/DISKD0013
Total Space (KB) = 15769600
Used Space (KB) = 13078160
Used Space (%) = 82
Free Space (KB) = 2691440
Free Space (%) = 18
Devspace Name = /sapdb/XA4/sapdata/DISKD0014
Total Space (KB) = 15769600
Used Space (KB) = 13628752
Used Space (%) = 86
Free Space (KB) = 2140848
Free Space (%) = 14
Devspace Name = /sapdb/XA4/sapdata/DISKD0015
Total Space (KB) = 15769600
Used Space (KB) = 13596104
Used Space (%) = 86
Free Space (KB) = 2173496
Free Space (%) = 14
Devspace Name = /sapdb/XA4/sapdata/DISKD0016
Total Space (KB) = 15769600
Used Space (KB) = 13739128
Used Space (%) = 87
Free Space (KB) = 2030472
Free Space (%) = 13
Hello Hannes,
Thank you for the help. I've modified the dbmcli command to your specs:
[sdb@xa4-myexaserv bin]$ ./dbmcli -u control,****** -d XA4 -uSQL sapXA4,******
./dbmcli on XA4>drop index 'TPR_XREF_D~OBJ'
ERR
-24977,ERR_COMMAND: Unknown DBM command "drop"
I've double check that the database is up and running. Also, is there a note that lists the error codes of MaxDB? I hate to waste the time of forum participators when I can look something up myself.
Thanks,
Zach
> [sdb@xa4-myexaserv bin]$ ./sqlcli -u DEFAULT
>
> Welcome to the MaxDB interactive terminal.
>
> Type: \h for help with commands
> \q to quit
>
> sqlcli=> drop index 'TPR_XREF_D~OBJ'
> * -10709: Connection failed (RTE:Database name is missing) SQLSTATE:
>
use a CAPITAL U:
./sqlcli -U DEFAULT
Markus
Markus,
Thank you for the help. I've attempted your solution also...one thing to note, I assumed that the code after
DEFAULT was just a parsing error.
Here is the result from this attempt:
[sdb@xa4-myexaserv bin]$ ./sqlcli -U DEFAULT
Welcome to the MaxDB interactive terminal.
Type: \h for help with commands
\q to quit
sqlcli=> drop index 'TPR_XREF_D~OBJ'
* -10757: XUSER error (the USERKEY is unknown) SQLSTATE:
Once again, thank you for all the help,
Zach
Tried to edit this post, but the forum didn't allow it....
Here is a link for error codes:
https://wiki.sdn.sap.com/wiki/display/MaxDB/MaxDBerrornumbers
-Zach
Hannes,
[sdb@xa4-myexaserv bin]$ ./dbmcli -u control,****** -d XA4 -uSQL sapXA4,******
./dbmcli on XA4>db_execute drop index 'TPR_XREF_D~OBJ'
ERR
-24988,ERR_SQL: SQL error
-5006,Missing identifier
SQL Studio's documentation indicates there should be an error position to show where the missing identifier
should be.
Going through some of the logs I noticed that TPR_XREF_D and TPR_XREF_D~OBJ are created properly
in the SAPAPPL2_10. Excerpt from SAPAPPL2_10.TSK....
[root@xa4-myexaserv AS]# cat SAPAPPL2_10.TSK | grep TPR_XREF_D
T TPR_XREF_D C ok
P TPR_XREF_D~0 C ok
D TPR_XREF_D I ok
I TPR_XREF_D~OBJ C ok
...if those entities were created in SAPAPPL2_10, why would the logs indicate that the index was trying to
be created again during the T100. That would explain the -955 (duplicate entry error), but does this
command indicate that the table TPR_XREF_D doesn't exist?
[sdb@xa4-myexaserv bin]$ ./dbmcli -u control,****** -d XA4 -uSQL sapXA4,******
./dbmcli on XA4>db_execute select * from TPR_XREF_D
ERR
-24988,ERR_SQL: SQL error
-4004,Unknown table name:TPR_XREF_D
---
[sdb@xa4-myexaserv bin]$ ./dbmcli -u superdba,****** -d XA4
./dbmcli on XA4>db_execute select * from TPR_XREF_D
ERR
-24988,ERR_SQL: SQL error
-4004,Unknown table name:TPR_XREF_D
---
I ran the command as different users to make sure the "Unknown table name" error was not due to a permissions error.
-Zach
Markus,
That did make a difference with being able to pull up the table (I'm assuming a permissions issue). It
appears that the ~ within the index name requires the token be enclosed with quotes. When I specify the
index with single tick quotes, the specified index isn't recognized as a valid identifier. So I tried with double
quotes....this approach seems to have brought success with removing the duplicate index. I am going to
try and start the install over again from where it last failed.
sqlcli XA4=> drop index TPR_XREF_D~OBJ on TPR_XREF_D
* -3014: POS(22) Invalid end of SQL statement SQLSTATE: 42000
* -3014: POS(22) Invalid end of SQL statement SQLSTATE: 42000
sqlcli XA4=> drop index 'TPR_XREF_D~OBJ' ON TPR_XREF_D
* -5006: POS(13) Missing identifier SQLSTATE: 42000
* -5006: POS(13) Missing identifier SQLSTATE: 42000
sqlcli XA4=> drop index "TPR_XREF_D~OBJ" on TPR_XREF_D
0 rows affected (2 msec)
sqlcli XA4=> drop index "TPR_XREF_D~OBJ" on TPR_XREF_D
* -4011: POS(13) Unknown index name:TPR_XREF_D~OBJ SQLSTATE: I4011
* -4011: POS(13) Unknown index name:TPR_XREF_D~OBJ SQLSTATE: I4011
I'll post again once I confirm the problem is corrected. Thank you!
-Zach
Hello all,
Thank you for the help with this issue. For whatever reason the system was trying to create that index twice and deleting the index before it was duplicated fixed the error outright. The big confusion came from I was instructed that superdba was the "root" user of the database...since that is not the case (demonstrated by the lack of permissions to view a particular table), that assumption led to me believing the table hosting the index didn't exist.
Once again, thank you all for the help.
-Zach
I've experienced the same import Abap error, changed my JRE1.6 to JRE1.4.2 worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.