WAS 6.40 SP9 installation, MaxDB problem?

[Former Member]

Hello,

I'm trying to install the preview version of WAS J2EE Server 6.40 SP9 from the SDN Downloads. I'm stuck at step nr. 5 (activating the database).

From other very helpful posts in this forum I've got an idea on where to look for error messages, but couldn't find anything on my system.

The failing command (from XCMDOUT.LOG) is

-

---

> Subprocess starts at 20050208080231

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n Home-Off -d J2E -u CONTRO

L,********

Execute Session Command : util_connect

Execute Session Command : exit

> Subprocess stops at 20050208080233

ERR

-24988,ERR_SQL: sql error

1,database not running

-

---

I get no error message in knldiag.err.

After restarting my system I try to bring the database online, but without luck:

-

---

> dbmcli -d J2E -u control,control db_enum

OK

J2E c:\sapdb\j2e\db 7.5.0.18 fast offline

J2E c:\sapdb\j2e\db 7.5.0.18 quick offline

J2E c:\sapdb\j2e\db 7.5.0.18 slow offline

> dbmcli -d J2E -u control,control db_online

ERR

-24988,ERR_SQL: sql error

1,database not running

> dbmcli -d J2E -u control,control db_enum

OK

J2E c:\sapdb\j2e\db 7.5.0.18 fast running

J2E c:\sapdb\j2e\db 7.5.0.18 quick offline

J2E c:\sapdb\j2e\db 7.5.0.18 slow offline

> dbmcli -d J2E -u control,control db_online

ERR

-24961,ERR_STATE: cannot determine current db state

-

---

The last line in knldiag says

DBSTATE SERVERDB is ready

without any error message before.

Can somebody give me a hint on what's going wrong?

The system runs on Win XP Professional SP2, j2sdk 1.4.2_07.

Many thanks!

Christian.

[roland_mallmann · Accepted solution]

Hi Christian,

I've taken the liberty of moving your post to the MaxDB/liveCache forum, obviously because you've got a MaxDB error.

Could you please issue the following command for me (and enter the output in your answer):

dbmcli -d J2E -u control,control db_state

You might try again to restart the database, by issueing:

dbmcli -d J2E -u control,control db_offline (wait for the 'OK')

dbmcli -d J2E -u control,control db_online

Kind regards,

Roland

[Former Member · Accepted solution]

Hi Roland,

I agree that this problem seems to be a MaxDB issue.

I submitted the db_online command earlier this morning after a reboot. Taking the database offline seems to be impossible:

> dbmcli -d J2E -u control,control db_state

OK

State

UNKNOWN

> dbmcli -d J2E -u control,control db_offline

ERR

-24961,ERR_STATE: cannot determine current db state

[roland_mallmann · Accepted solution]

Hi Christian,

can you issue the following commands:

x_cons J2E sh state

x_cons J2E sh act

Regards,

Roland

[Former Member · Accepted solution]

> x_cons J2E sh state

13426 ERROR: XCons: Opening Kernel Shared Segment of Server DB J2E failed, rc = 2

> x_cons J2E sh act

13426 ERROR: XCons: Opening Kernel Shared Segment of Server DB J2E failed, rc = 2

[roland_mallmann · Accepted solution]

Christian, can you send me the dbm.prt and knldiag file from your J2E instance? Please send them to: roland.mallmann@sap.com

Can you see a 'kernel.exe' process in the Windows Task Manager? If yes, does it show something abnormal?

[Former Member · Accepted solution]

Hi Roland,

yes, there is a kernel.exe process, running for user SYSTEM. It doesn't look abnormal in any way.

I send you the files now. Thank you very much for your support!

Best regards,

Christian.

[roland_mallmann · Accepted solution]

Hi Christian,

I got the files you sent me. Interesting is that the knldiag's last entry is:

2005-02-08 08:05:25 0xC70 19601 DBSTATE SERVERDB is ready

> Is that the <b>current</b> knldiag file, or a previously copied version of knldiag?

---

Could you issue the following for me:

x_show

Regards,

Roland

[Former Member · Accepted solution]

Hi Roland,

this was the current file. I think at this time I issued the "db_online" command after a reboot.

x_show gives:

SERVERDBs:

- .M750018 [Stopped]

- .M750018 (quick) [Stopped]

- .M750018 (slow) [Stopped]

- .M750018 (test) [Stopped]

- J2E [Running]

- J2E (quick) [Stopped]

- J2E (slow) [Stopped]

- J2E (test) [Stopped]

XSERVER is active.

These looks like the Windows services running. When I look up there, also only "SAPDB: J2E" is running, but not the others. But they only run after reboot when I issue the "db_online" command.

Best regards,

Christian.

[roland_mallmann · Accepted solution]

Hi again,

ok, next requests:

1. Can you send me the Application Eventviewer Log of your system (by mail)?

2. Please issue the following:

- dbmcli -d J2E db_enum

- dbmcli -d J2E inst_enum

- dbmcli -d J2E dbm_version

Kind regards,

Roland

[Former Member · Accepted solution]

Hello Roland,

here are the commands with their output:

> dbmcli -d J2E db_enum

OK

J2E c:\sapdb\j2e\db 7.5.0.18 fast running

J2E c:\sapdb\j2e\db 7.5.0.18 quick offline

J2E c:\sapdb\j2e\db 7.5.0.18 slow offline

> dbmcli -d J2E inst_enum

OK

7.5.0.18 c:\sapdb\j2e\db

> dbmcli -d J2E dbm_version

OK

VERSION = 7.5.0

BUILD = DBMServer 7.5.0 Build 018-123-079-776

OS = WIN32

INSTROOT = c:\sapdb\j2e\db

LOGON = True

CODE = UTF8

SWAP = full

UNICODE = YES

INSTANCE = OLTP

SYSNAME = Windows XP

I send you the application log by mail, but I also already looked up there and found nothing special.

Best regards,

Christian.

[roland_mallmann · Accepted solution]

Hi Christian,

next test, try to connect to the DB using:

dbmcli -d J2E -u control,control util_execute diagnose vtrace default on

-> Please let us know the outcome.

---

Secondly, I'd like you to try and start the kernel directly, by:

0. Stop the SAP DB: J2E Service

1. Goto the directory named 'c:\sapdb\j2e\db\pgm'

2. Edit the environment using: set DBROOT=c:\sapdb\j2e\db

3. Call 'kernel J2E'. (A popup screen will appear for a short while, after which a trafficlight symbol will appear in the tasklist at the bottom right of the Windows bar).

4. Let us know the output of the following: dbmcli -d J2E -u control,control db_state.

Regards,

Roland

[Former Member · Accepted solution]

Hi Roland,

1)

> dbmcli -d J2E -u control,control util_execute diagnose vtrace default on

ERR

-24988,ERR_SQL: sql error

1,database not running

2)

The traffic light shows yellow. The db_state command prints

OK

State

ADMIN

3) When I issue the command from 1) again, it says OK.

Regards,

Christian.

[roland_mallmann · Accepted solution]

Hi Christian,

thanks again.

Can you tell me with which user the SAP DB: J2E service is started? To find out, take a look at the properties of that service, tab 'Log On'.

Is it the Local Systemaccount or another user?

Is your user a local admin?

Can you set the user in that tab to your user and try to start the database normally (dbmcli ... db_online)?

Regards,

Roland

[Former Member · Accepted solution]

Hi Roland,

the service was installed with the user SYSTEM. I am using a local administrator.

I changed the service user to my user and tried again running "kernel" manually and bringing the database online. This makes no difference as far as I can see.

But when I run "kernel J2E" from the command line I get an error messages when issueing the db_online command:

ERR

-24895,ERR_SHUTDOWN: shutdown of database occured

-71,connection broken

and messages in knldiag:

Connect req. (T4, Node:'', PID:1868)

Attaching volume 'C:\sapdb\J2E\sapdata\DISKD0001'

Could not open volume 'C:\sapdb\J2E\sapdata\DISKD0001', rc = 2

Attach error on Data volume 1: could not open volume

RestartFilesystem failed with 'I/O error'

ERROR 'disk_not_accessibl' CAUSED EMERGENCY SHUTDOWN

The mentioned file does not exist.

Do you think this is a permission problem? But as long as I don't start kernel from the command line it also runs under the SYSTEM account.

Best regards,

Christian.

[Former Member · Accepted solution]

Hi Roland,

I tried another thing:

1) gave my user all rights for folder c:\sapdb\j2e\sapdata and subfolders, files. This was already the case through group of administrators, but it is worth a try.

2) removed read-only attribute of this folder. This was set from the installation routine.

3) started "kernel J2E" from command line, but with DBROOT set to c:\sapdb\j2e\db (otherwise it searches in the wrong directory for a DLL)

4) retry WAS installation routine. Now it tries to execute "db_activate SUPERDBA,ADMIN" and takes much longer. I get some success messages and a green light for the database tray icon.

Now the installation proceeds. I will report later what happens when I try to start the database without starting "kernel J2E" manually.

I can't say if step 1) or 2) above solved the problem or the manuell starting of the kernel.

Thank you very much for your help so far!

Best regards,

Christian.

[roland_mallmann · Accepted solution]

Hi Christian,

ok, I'm sorry, I told you to issue the db_online command, it should have been the 'db_admin' (or 'db_cold') command. No real problem though.

The error thrown when issueing the db_online command is normal, because very probably the initialization of the database hasn't been done yet, i.e. not datavolumes were created.

Let's start from the beginning.

1. Make sure your instance J2E isn't running anymore.

Take a look at the Windows Task Manager to see if a 'kernel.exe' is still there. If yes, we need to stop it. (If you last started the kernel manually (i.e. 'kernel J2E'), then you'd still have a traffic light symbol in the Windows taskbar, bottom right).

2. Make sure your user is used for the SAP DB: J2E service and <b>not</b> the SYSTEM user.

3. Try and start the database into mode admin using:

dbmcli -d J2E -u control,control db_admin

Please let us know the results of this.

Regards,

Roland

Message was edited by: Roland Mallmann

[roland_mallmann · Accepted solution]

Hi Christian,

I didn't see your last entry (from Feb 8, 2005 5:52 PM) as I was writing my last answer at roughly the same time.

Please let me know if everything works normally afterwards. Please try to adminster your MaxDB instance using the Database Manager GUi for example, that should tell you (and us) if the installation is working like it should.

If it does work normally, then we very probably won't really find the cause for the problem(s) anymore.

Regards,

Roland