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

[leif_almgren]

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:

[lbreddemann]

Hi Almgren,

did you install it into a VMWare machine or directly to a standard XP installation?

Did you perhabs connect via Terminal Services?

KR Lars

[leif_almgren]

This problem is no longer an issue, since I solved it by ditching Max-DB, but thanks for your input anyway. The answer is that I installed it directly on a XP machine, and I did not connect using Terminal Services.

/Leif

[leif_almgren]

Thought it was solved, but it was only partly solved (see second post).

[leif_almgren]

Did a complete re-install but still the same problem as in post #2 above. No error in KNLDIAG.ERR. No database files were created.

Also, again not possible to initialize the instance manually (using the parameters already set by the install procedure).

I'm stuck...

[Former Member]

Hi,

Could you finally solve this issue?

Regards

[leif_almgren]

No, I never solved the problem and went with SQL Server instead.

[former_member229109]

Hello Almgren,

-> Before to run the command::

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

The database should be created & activated < initialized > first.

-> "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...""

At that point the question about why the database was not initialized has to be checked ...

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

I was not able to display this thread.

But as you have '-' in the name of the database server =>

you have the similar issue as in the threads::

& the solution/workaround could be the same as in those threads.

Thank you and best regards, Natalia Khlopina

Edited by: Natalia Khlopina on Apr 25, 2008 1:20 PM

Edited by: Natalia Khlopina on Apr 25, 2008 7:29 PM

[leif_almgren]

See my reply above, but I appreciate your input and maybe the problem was the "dash" sign in the computer name. Will remember that if I ever get into the same situation again.

I have now flagged this one as answered.

/Leif

[leif_almgren]

I will partly answer myself, hope this info will be of use for others as well. The trick was to increase the virtual memory size. After this, it was at least possible to initialize the instance using the Database Manager.

The Netweaver install still stops on phase 15 though, with this error in XCMDOUT.LOG:

> Subprocess starts at 20070323110941

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

Execute Session Command : exit

> Subprocess stops at 20070323110943

> Subprocess call failed

ERR

-24961,ERR_STATE: cannot determine current db state

There are no errors in KNLDIAG.ERR this time. Also, I am unable to put the db instance online using the Database Manager, I get the same error about unknown state of the database.

I will try a complete re-install, so that the DB instance will be created by the install procedure and not manually.