cancel
Showing results for 
Search instead for 
Did you mean: 

Installation halts - probably because of sapdb.inf

Former Member
0 Kudos

Hello fellow SAP admins

I'm trying to install SAP solution manager/netweaver 7.0 on a Sun Sparc T2000 with Solaris 10. The installation works fine until I get to phase 13 of 47: "Create database schema". I don't get an error message, but the installation halts and I can read the following from the promt:

"File sapdb.inf does exist. Will use the commands in file sapdb.inf."

Everything seems to work and I cannot locate logfiles that tell me otherwise.

XCMDOUT.log ends with the following:

> Subprocess starts at 20080513084428

Execute Command : /sapdb/programs/bin/dbmcli -n SunT2000 -d BDS -u control,********

Start subprocess as user with uid: root

Execute Session Command : sql_connect superdba,********

Execute Session Command : sql_execute SELECT VALUE FROM DBPARAMETERS WHERE DESCRIPTION='_UNICODE'

Execute Session Command : exit

> Subprocess stops at 20080513084430

OK

OK

END

'YES'

Any ideas?

NB: You can find a similiar unsolved post by David Ingersoll from Mar 31, 2008 3:30 PM by searching the term "sapdb.inf".

Thanks in advance..

/Peter

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi

I too faced with the same problem while installing in XP. Actually the reason behind the issue is unimmaginable. I had used a special character '@' in my master password during installation. First i tried abcd1234 as my master password it wouldnt go with the password policy of my system so i changed it to Abcd@123$. so it got stuck during the create database schema step (step 15) and we had no clue of what could be the reason. Luckyly i got to know from sdn that '@' could be the problem. so If in case you face any such issue in future please make sure that there are no special characters in ur master password, atleast not the '@' symbol..

Acknowledge if it helps..and let us know how u solved it and mark if answered

Thanks

Md. Yusuf

Former Member
0 Kudos

Can you check the available space let while installation is in progress

vmstat 1 333

and see the available size of memory.

markus_doehr2
Active Contributor
0 Kudos

> "File sapdb.inf does exist. Will use the commands in file sapdb.inf."

This is not a problem but just an information.

- Has there been an installation before on the system? Are you trying to add a second one?

- Did you setup a project file according to note 724713 - parameter settings for Solaris 10?

Markus

Former Member
0 Kudos

Thanks for your fast replies.

I agree. I don't receive an error message. The question is of course what keeps the installation from proceeding.

- I'm about to install the only SAP system on the server

- Yes, I have followed sap note 724713. The installation runs under the project user.root (if the command 'ps -eo user,pid,ppid,project,args' is called). The only difference from the note is that the 'sapadm' user did not exist and is therefore not added to the project. (The users are: <sid>adm,<db_sid> and db software owner)

Output example from 'ps -eo user,pid,ppid,project,args':

root 1097 1096 user.root /sap/tmp/sapinst_exe.1096.1210759752/sapinstexe

root 1104 1102 user.root /usr/j2se/jre/bin/java -Xmx256M -cp /sap/tmp/sa

/Peter

markus_doehr2
Active Contributor
0 Kudos

Hi Peter,

this is really strange...

What do you see when you execute

ptree

are there any child processes of sapinst? (please put the output in

You have a knldiag and/or knldiag.err file there?

Markus

Former Member
0 Kudos

Here goes:

'ptree' returs (amongst other):


982   /usr/lib/ssh/sshd
    985   /usr/lib/ssh/sshd
      987   -sh
        1004  bash
          1093  ksh
            1094  bash
              1096  ./sapinst
                1097  /sap/tmp/sapinst_exe.1096.1210759752/sapinstexe

sapdb/data/wrk includes a number of files, amongst other MaxDBServer_install-13.05.2008-08.26.log which end by:


MSG: net install registry size = 214322 bytes
MSG: wrote install registry (277768 bytes)
STDOUT: installation of MaxDB Server finished successfully Tu, May 13, 2008 at
08:26:14
MSG: packagedata of package Base not changed
MSG: packagedata of package SQLDBC not changed
MSG: packagedata of package SQLDBC 76 not changed
MSG: packagedata of package Fastload API not changed
MSG: packagedata of package PCR 7300 not changed
MSG: packagedata of package PCR 7301 not changed
MSG: packagedata of package PCR 7403 not changed
MSG: packagedata of package PCR 7500 not changed
MSG: packagedata of package SAP Utilities not changed
MSG: packagedata of package DB Analyzer not changed
MSG: packagedata of package JDBC not changed
MSG: packagedata of package Server Utilities not changed
MSG: packagedata of package Database Kernel changed
MSG: packagedata of package Redist Python not changed
MSG: packagedata of package Loader not changed
MSG: packagedata of package Messages not changed
MSG: packagedata of package ODBC not changed
MSG: writing 19 packages
MSG: net install registry size = 214695 bytes
MSG: wrote install registry (278425 bytes)
MSG: install registry successfully unlocked

/sapdb/data/wrk/<SID> have both knldiag and knldiag.err

knldiag ends like this:


2008-05-13 08:44:30    13     11561 COMMUNIC Connecting T109 local 325
2008-05-13 08:44:30    30     12929 TASKING  Task T109 started
2008-05-13 08:44:30    30     11007 COMMUNIC wait for connection T109
2008-05-13 08:44:30    30     11561 COMMUNIC Connected  T109 local 325
2008-05-13 08:44:30    30     11560 COMMUNIC Releasing  T109
2008-05-13 08:44:30    30     12827 COMMUNIC wait for connection T109
2008-05-13 13:35:22     8     12852 DBSTATE  Caught STOP signal
2008-05-13 13:35:22     8     12696 DBSTATE  Change DbState to 'STOP'(28)
2008-05-13 13:35:22     8     12697 DBSTATE  Resuming tracewriter
2008-05-13 13:35:22    24     12825 TASKING  state 28 before shutkill(1)
2008-05-13 13:35:22     7     12696 DBSTATE  Change DbState to 'TRACE_WRITER_WA
IT'(28)
2008-05-13 13:35:22    24     12825 TASKING  state 28 before shutkill(1)
2008-05-13 13:35:22    24     12825 TASKING  state 28 before shutkill(1)
2008-05-13 13:35:22    24     20000 Trace    Start flush kernel trace
2008-05-13 13:35:27    29     12825 TASKING  state 28 before shutkill(1)
2008-05-13 13:35:27    29     12768          UKT6 stopped
2008-05-13 13:35:27    24     20001 Trace    Stop flush kernel trace
2008-05-13 13:35:27    24     12619 TASKING  Releasing tracewriter
2008-05-13 13:35:27     1     12611 DBSTATE  SERVERDB is being stopped
+++++++++++++++++++++++++++++++++++++++ Kernel Exit +++++++++++++++++++++++++++
+
2008-05-13 13:35:31     0     12845 DBSTATE  Kernel exited normal
2008-05-13 13:35:31     0     12696 DBSTATE  Change DbState to 'OFFLINE '(28)
--------------------------------------- current write position ----------------

knldiag.err file:


--------------------------------------------------------------------------------
Date       Time       TID Typ MsgID Label    Message-Text
--------------------------------------------------------------------------------
2008-05-13 08:27:48                          --- Starting GMT 2008-05-13 06:27:48           7.6.00   Build 035-123-139-084
2008-05-13 13:35:31                          ___ Stopping GMT 2008-05-13 11:35:31           7.6.00   Build 035-123-139-084

markus_doehr2
Active Contributor
0 Kudos

Everything looks good!

And you get now an error window in sapinst - or does it just sits there and doing nothing? Did you create the users (<sid>adm, sqd<sid>, sdb) beforehand?

Markus

Former Member
0 Kudos

I don't get an error message, the installation just doesn't seem to continue.

The <sid>adm and sqd<sid> users are added automatically by the installation.

I added the sdb user manually beforehand (to install the MaxDB software).

/Peter

markus_doehr2
Active Contributor
0 Kudos

You did install the SAPDB software manually before? Usually this is done by sapinst...

Markus

Former Member
0 Kudos

hi Peter,

I'm also facing the same problem but i'm installing in windows XP. could you please let me know how u solved in ur case.. It would be of very much help for others too.

Thanks

Md. Yusuf

Former Member
0 Kudos

Check sapinst.log and paste the content related to the error

Former Member
0 Kudos

Unfortunately I don't get an error message. The installation simply seems to halt.

The sapinst.log file ends like this:

INFO 2008-05-13 13:38:23.161

Execute step CreateDbSchema of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|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|Sdb_Schema_Dial

ogs|ind|ind|ind|ind|4|0|Sdb_Schema|ind|ind|ind|ind|1|0.

INFO 2008-05-13 13:38:46.318

Working directory changed to /sap/tmp/sapinst_exe.421.1210678577.

INFO 2008-05-13 13:38:46.328

Working directory changed to /sap/tmp/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS.

INFO 2008-05-13 13:38:46.378

Working directory changed to /sap/tmp/sapinst_exe.421.1210678577.

INFO 2008-05-13 13:38:46.407

Working directory changed to /sap/tmp/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS.

INFO 2008-05-13 13:38:46.790

Working directory changed to /sap/tmp/sapinst_exe.421.1210678577.

INFO 2008-05-13 13:38:46.849

Working directory changed to /sap/tmp/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS.

~

~

/Peter