Skip to Content
author's profile photo Former Member
Former Member

Installation Error: IDES Database Import

Hello everyone,

Thank for all for the help so far. The forums have really helped me along in my SAP installation. This

particular error has occurred for the second time in a row.... This error happens after importing

approximately 250GB of IDES data into the sap database (MaxDB). The error logs and system info are

posted below.

-


STDOUT:

+SNIP+

INFO       2009-02-24 10:37:15.650 [sixxcstepexecute.cpp:781]
Execute step sdb_instance_start of component 
|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_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|
ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0

INFO       2009-02-24 10:37:37.597 [sixxcstepexecute.cpp:781]
Execute step sdb_instance_activate of component 
|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_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|
ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0

INFO       2009-02-24 11:53:40.381 [sixxcstepexecute.cpp:781]
Execute step sdb_instance_wait_for_backup of component 
|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_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|
ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0

INFO       2009-02-24 11:53:41.181 [sixxcstepexecute.cpp:781]
Execute step sdb_instance_load_systables of component 
|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_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|
ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0

WARNING[E] 2009-02-24 11:53:42.882 
           CJSlibModule::writeError_impl() 
The dbmcli call for action LOAD_SYSTAB failed. SOLUTION: Check the logfile XCMDOUT.LOG.

WARNING[E] 2009-02-24 11:53:42.955 
           CJSlibModule::writeError_impl() 
The dbmcli call for action LOAD_SYSTAB failed. SOLUTION: Check the logfile XCMDOUT.LOG.

*ERROR*      2009-02-24 11:53:43.207 [sixxcstepexecute.cpp:951]
FCO-00011  The step sdb_instance_load_systables 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_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|
ind|3|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|
sdb_instance_load_systables was executed with status ERROR .

XCMDOUT.LOG

+SNIP+


 Subprocess starts at 20090224103715

 Execute Command : /sapdb/programs/bin/dbmcli -n xa4-myexaserv -d XA4 -u CONTROL,******** db_start
 Start subprocess as user with uid: root

 Subprocess stops at 20090224103736

 OK

 Subprocess starts at 20090224103736

 Execute Command : /sapdb/programs/bin/dbmcli -n xa4-myexaserv -d XA4 -u CONTROL,******** db_state
 Start subprocess as user with uid: root

 Subprocess stops at 20090224103736

 OK
 State
 ADMIN

 Subprocess starts at 20090224103737

 Execute Command : /sapdb/programs/bin/dbmcli -n xa4-myexaserv -d XA4 -u CONTROL,******** db_state
 Start subprocess as user with uid: root

 Subprocess stops at 20090224103737

 OK
 State
 ADMIN

 Subprocess starts at 20090224103738

 Execute Command : /sapdb/programs/bin/dbmcli -n xa4-myexaserv -d XA4 -u CONTROL,********
 Start subprocess as user with uid: root
 Execute Session Command : util_connect
 Execute Session Command : db_activate SUPERDBA,********
 Execute Session Command : exit

 Subprocess stops at 20090224115339

 OK
 OK

 Subprocess starts at 20090224115341

 Execute Command : /sapdb/programs/bin/dbmcli -n xa4-myexaserv -d XA4 -u CONTROL,******** 
load_systab -u SUPERDBA,******** -ud ********
 Start subprocess as user with uid: root

 Subprocess stops at 20090224115342

 ERR
 -24964,ERR_EXECUTE: error in program execution
 256,/sapdb/XA4/db/bin/x_python /sapdb/XA4/db/env/lsystab.py -R /sapdb/XA4/db -d XA4 -u SUPERDBA,********
 ---------Traceback---------------
 ---------Error-------------------
 sql.SQLError: [-4008] (at 1) Unknown user name/password combination
 Traceback (most recent call last):
   File "/sapdb/XA4/db/env/lsystab.py", line 202, in ?
     connectAndInstall (install, install.__doc__)
   File "/sapdb/XA4/db/env/installib.py", line 393, in connectAndInstall
     session = connect (options)
   File "/sapdb/XA4/db/env/installib.py", line 348, in connect
     alterUserNotExclusive(options)
   File "/sapdb/XA4/db/env/installib.py", line 336, in alterUserNotExclusive
     session.release()
 AttributeError: 'NoneType' object has no attribute 'release'

-


System Information:

RHEL 5.2

SAP_ERP_6.0_SR3_IDES_Inst._Master

RDBMS_MAXDB_7.6.03_Build_09

NW_7.0_SR3_Kernel_WINDOWS__LNX_X86

Java:

[root@xa4-**** sapInstall]# java -version
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)

Python:

[root@xa4-**** sapInstall]# python -V
Python 2.4.3

-


Once again, thank you all for the help. Has there been a "sticky" post on how to format thread postings for

easy reading?

Thank you,

Zach

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Feb 24, 2009 at 08:42 PM

    there are some password issues apparently...

    how long is you superdba (or master) password?

    Markus

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Markus,

      To clarify on my original reply.

      [root@xa4-myexaserv ~]# touch te$tpa$$word
      [root@xa4-myexaserv ~]# ls -l te*
      -rw-r--r-- 1 root root 0 Feb 24 15:12 te24682word

      What's occurring here is:

      -> $tpa isn't a registered variable so bash is dropping it out of the command

      -> $$ is a special parameter in bash that evaluates to the pid of the shell

      Do you think something similar to this is happening in the x_python execution? ...this assumes that all of

      these commands are running in a bash environment. Even if this is the culprit of my error, I'm unsure why the

      following command succeeds:

      /sapdb/programs/bin/dbmcli -n xa4-myexaserv -d XA4 -u CONTROL,******** load_systab -u
      SUPERDBA,******** -ud ********

      Perhaps I am over thinking it... But I have a hard time believing that a particular script in a large installation

      would behave so differently from the rest of the installation scripts.

      Thank you for the help,

      Zach

  • author's profile photo Former Member
    Former Member
    Posted on Feb 25, 2009 at 04:39 PM

    I changed my sap master password to no longer contain $ characters and the database import proceeded

    correctly. After searching the notes and previous forum posts, I think this should be noted. There are a few

    notes that mention not using '@' in passwords because it is a database control character. Maybe there

    needs to be testing to determine what other control characters cause trouble, $/&/#/etc.

    Thanks for all the help,

    Zach

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.