SAPINST hanging in phase 16 - create database schema. maxDB/win

[Former Member]

I am installing the Developers Workplace on a very beefy WinXP workstation. The HD space and memory are sufficient. When running SAPINST I chose the MaxDB option (instead of SQL). The install runs until phase 16 (create database schema) and just hangs there indefinitely. It's been in that phase for almost 24 hours and still running. There are no errors, and the last log entry is from when the phase began. The task manager shows CPU activity. The MaxDB installation manager shows the components and DB instance, but beyond that I'm not sure how to tell if any progress is being made since no error has been generated.

Any suggestions?

[Former Member · Accepted solution]

How big did you make the table space? It might still be generating these.

Have you looked in Task Manager to see which processes are running and if you might be maxing out some resources (swap, memory and so on).

Just askin...

J. Haynes

Denver, CO

[Former Member]

I was not able to get to the bottom of the issue. But when I ran the installation on a cleanly created WinXP workstation (with no prior software or usage), the install completed.

The initial install was performed on an XP workstation that had been in use for quite a while, with other apps installed. So, clearly there was a conflict somewhere with other apps or OS resources. But starting fresh from an XP install seemed to work out.

[Former Member]

Hi Gurus,

I also encountered the same issue. Any update regarding this?

Best regards,

Charlie

[Former Member]

I would like to know the reason as well. I am facing the same problem. Is there any workaround

Thanks

Amit

[Former Member]

Those logs don't show anything obvious. The knldiag last lines are:

2008-01-22 12:27:55 0x121C 3 RunTime State changed from ADMIN to ONLINE

2008-01-22 12:27:55 0x121C 20217 RTE Used physical memory 397 MByte

2008-01-22 12:27:55 0x121C 20041 Admin Kernel state: 'ONLINE' reached

2008-01-22 12:27:55 0x121C 19651 CONNECT Connection released, T21

2008-01-22 12:27:55 0x121C 19633 CONNECT Connect req. (T22, Node:'', PID:1928)

2008-01-22 12:27:55 0x121C 19651 CONNECT Connection released, T22

2008-01-22 12:27:56 0x121C 19633 CONNECT Connect req. (T23, Node:'', PID:4952)

2008-01-22 12:27:56 0x121C 19651 CONNECT Connection released, T23

2008-01-22 12:28:00 0x121C 19633 CONNECT Connect req. (T24, Node:'', PID:4496)

2008-01-22 12:28:00 0x121C 19651 CONNECT Connection released, T24

2008-01-22 12:28:00 0x121C 19633 CONNECT Connect req. (T25, Node:'', PID:2336)

2008-01-22 12:28:01 0x121C 19651 CONNECT Connection released, T25

2008-01-22 12:28:01 0x121C 19633 CONNECT Connect req. (T26, Node:'', PID:2336)

2008-01-22 12:28:01 0x121C 19651 CONNECT Connection released, T26

2008-01-22 12:28:01 0x121C 19633 CONNECT Connect req. (T27, Node:'', PID:5620)

2008-01-22 12:28:02 0x121C 19651 CONNECT Connection released, T27

2008-01-22 12:28:02 0x121C 19633 CONNECT Connect req. (T28, Node:'', PID:884)

2008-01-22 12:28:02 0x121C 19651 CONNECT Connection released, T28

2008-01-22 12:28:02 0x121C 19633 CONNECT Connect req. (T29, Node:'', PID:884)

2008-01-22 12:28:02 0x121C 19651 CONNECT Connection released, T29

-

---

current write position -

---

The sapinst_dev file:

INFO 2008-01-23 14:28:52 [synxcfile.cpp:493]

CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/keydb.6.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const

Copied file 'C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/keydb.xml' to 'C:/Program Files/sapinst_instdir/NW04S/SYSTEM/DEVWP/MAXDB/keydb.6.xml'.

TRACE

getKeydbManager()->syncToFile ( ) in function CS

[Former Member]

That didn't seem to help, so maybe its not a popup issue. Any other thoughts?

This is where the sapinst log file sits indefinitely:

INFO 2008-01-23 14:28:52

Execute step CreateDbSchema of component |NW_Workplace|ind|ind|ind|ind|0|0|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_Dialogs|ind|ind|ind|ind|4|0|Sdb_Schema|ind|ind|ind|ind|1|0.

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

Edited by: David Ingersoll on Jan 23, 2008 5:39 PM

[markus_doehr2]

Step to the installation directory and sort the files, check the latest ones for any problem.

also see sapinst_dev.log for further details.

If that all does not show something obvious, check the knldiag and knlidag.err files in the MaxDB directory.

I think, sapinst send a command and is waiting for the result to appear but that does never happen.

Markus

[Former Member]

sapinst is consuming 50% CPU and 150MB RAM.

One person suggested that it might be a pop up that's hidden. But I don't see any in the task manager or by hitting alt-tab. I have seen something like this in the past but I don't recall how I was able to bring up the popup.

[markus_doehr2]

move the sapinst windows to the very side - if there´s a popup it will become visible.

Markus

[Former Member]

PerfMon looks good. Memory is not being consumed anywhere near it's max. CPU is bouncing between 50-75% (duo core 2.2Ghz)

[markus_doehr2]

What process is consuming the CPU?

Markus