Skip to Content
0
Mar 23, 2007 at 09:22 AM

Max-DB cannot determine current db state (NW2004s install)

30 Views

I am installing the J2EE WAS with Max-DB on a developer workstation with Windows XP SP2, and have the following problem during phase 15 (create database instance):

From XCMDOUT.LOG:

-


> Subprocess starts at 20070323092239

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n nwd-dx6100 -d J2E -u CONTROL,******** db_state

Execute Session Command : exit

> Subprocess stops at 20070323092240

> Subprocess call failed

ERR

-24961,ERR_STATE: The operational state of the database instance could not be determined

-24994,ERR_RTE: Runtime environment error

no_id_provided_by_rte,no_text_provided_by_rte

From KNLDIAG.ERR:

-


2007-03-23 09:50:11 --- Starting GMT 2007-03-23 08:50:11 7.6.00 Build 035-123-139-084

2007-03-23 09:50:13 0xC00 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\J2E\sapdata\DISKD0001', rc = 2

2007-03-23 09:50:13 0xED8 ERR 20027 IOMan Attach error on data volume 1: could not open volume

2007-03-23 09:50:13 0xED8 ERR 3 Admin Database state: OFFLINE

2007-03-23 09:50:13 0xED8 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2007-03-23 09:50:13 0xED8 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2007-03-23 09:50:13 0xB90 ERR 7 Messages Begin of dump of registered messages

2007-03-23 09:50:13 0xB90 ERR 10 Messages abort dump of registered messages

2007-03-23 09:50:13 0xB90 ERR 8 Messages End of the message list registry dump

2007-03-23 09:50:13 0x2BC ERR 20125 RTE Database automatic restart failed

There are no files in directory c:\sapdb\J2E\sapdata, I would expect to find the DISKD001 etc files there.

I also tried uring the Database Manager tool to manually initialize the instance. This process also fails at the step "Starting the db instance", and I get the same error about "-24961 The operational state of the database instance could not be determined..."

Anyone has a clue what to do next? There was another thread about the same problem, but that problem was mysteriously solved without explanation:

NW2004s WAS 7.0 NSP fail in step 11