error "-24994" while creating database

[Former Member]

Hello,

we want to run maxdb7.5.0.38 on opensuse10.3 but creating a database fails with the error:

"

0x000022b1 ERR -24994 DBM ERR_RTE: runtime environment error

0x000022b1 ERR -24994 DBM 1,Check knldiag! Kernel died before reaching ADMIN state

"

We installed maxdb via rpm's and the error occurs while the command "db_start". It's a pity that there are no files under /var/opt/sdb/data/wrk/TEST (TEST is the name of the instance we want to create), only the directory has been created but no files inside.

The content of the file /var/opt/sdb/data/wrk/dbmsrv_infra01.prt is as follows:

2008-07-04 11:38:01 0x000022aa 0 DBM command param_rmfile

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put LOG_MIRRORED NO

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put CACHE_SIZE 50000

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put CAT_CACHE_SUPPLY 1300

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put SEQUENCE_CACHE 6

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put MAXCPU 1

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put MAXUSERTASKS 120

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put SESSION_TIMEOUT 60

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put REQUEST_TIMEOUT 30

2008-07-04 11:38:01 0x000022aa 0 DBM command param_put MAXDATAVOLUMES 20

2008-07-04 11:38:01 0x000022aa 0 DBM command param_checkall

2008-07-04 11:38:01 0x000022aa 0 DBM command param_commitsession

2008-07-04 11:38:01 0x000022aa 0 DBM command param_adddevspace 1 DATA /devspace/TEST/DISKD0001 F 25000

2008-07-04 11:38:01 0x000022aa 0 DBM command param_adddevspace 1 LOG /devspace/TEST/DISKL001 F 51200

2008-07-04 11:38:01 0x000022b1 0 DBM command db_start

2008-07-04 11:38:01 0x000022b1 ERR -24994 DBM ERR_RTE: runtime environment error

0x000022b1 ERR -24994 DBM 1,Check knldiag! Kernel died before reaching ADMIN state

The directory /devspace/TEST is also empty.

The script which we use is copied from another dbservers where it works well (same MaxDB 7.5.0.38 but with older suse linux, or opensuse10.3_64bit)

It doesn't matter if we use a script or webdbm, the error is the same.

It tells me to check knldiag, but there is no knldiag in the /var/opt/... as I mentioned earlier....????

any help appreciated....GERD...

[antonio_voce · Accepted solution]

Hi dear ,

read carefully the oss note 790879 - SAP Web AS 6.40 SR1 Installation on UNIX: MaxDB

There is the solution to your problem.

Reward if it help you !

Antonio.

[Former Member · Accepted solution]

Hello Antonio,

finally I found the oss note, but I couldn't find any hint to solve the problem. We don't use any SAP software (only MaxDB as standalone rdbms). The links in the document to several sap notes cannot be opened, since we're no SAP customer.

regards ....GERD....

[antonio_voce · Accepted solution]

Dear

why you don't find anything in the oss note i give you ?

here is an extract of the oss note :

20 Jul 05 Linux: Error with MaxDB 7.5 lower than Build 25

Prequisites

If you started the installation with Linux Distribution SLES9 or higher, Red Hat EL 3.0 or higher, when using Linux kernel 2.6 or the NTPL implementation with MaxDB RDBMS CD 7.5 lower than build 25, you get the error message shown below.

Problem

In installation log XCMDOUT.LOG you can see that db_online or db_start have aborted with the following error message:

ERR

-24994,ERR_RTE: runtime environment error

1,Check knldiag! Kernel died before reaching ADMIN state

Solution

You can avoid this error by using MaxDB RDBMS CD 7.5 build 28 or higher, as described above in section 2 "Pre-Installation".

If the error has already occurred, do the following:

1. Stop SAPinst.

2. Install MaxDB database software 7.5 build 25 or higher with SDBINST.

3. Start SAPinst and continue the installation.

[Former Member · Accepted solution]

Hi Antonio,

the funny thing is that he has 7.5.00.38, which should already be high enough, shouldn't it?

Regards,

Marc-Philip

Edited by: Marc-Philip Werner on Jul 7, 2008 4:54 PM

[antonio_voce · Accepted solution]

yes...you are right

so it is typical for opening an OSS MESSAGE TO SAP.... but unfortunately they don't have sap....

[Former Member · Accepted solution]

Hi Antonio,

no OSS ticket necessary. The OSS note that I linked to states "SLES 10 does not support Linux Kernel 2.4.1. As a result, you can only run current releases as of MaxDB 7.5.00 (64 bit) and 7.6 and you can no longer run MaxDB Versions 7.3.00 to 7.5.00 (32 bit) created under SLES 8."

Hence, he must either downgrade his OS to SLES 9 or use a more recent version of MaxDB.

Regards,

Marc-Philip

[Former Member · Accepted solution]

Hello Marc-Philip, hello Antonio,

since we're getting closer to a solution, there's only one question open.

You referenced this note which tells that SLES10 doesn't support this kernel version and therefore the OS or the MaxDB version needs to be changed.

Does this also belong to opensuse10.3, which we are using ?

Is there a possibility to get this OSS note without having a SAP login ?

thanks in advance....GERD....

[markus_doehr2 · Accepted solution]

Yes - SLES 10 is based on OpenSuSE (with some more "enterprise patches").

The problem is, that those old versions of MaxDB use a different thread implementation (Linuxthreads). Newer distributions (such as SLES 10) use NTPL, those are not compatible. On SLES 9 (which uses also kernel 2.6) there was the option of setting the environment variable LD_ASSUME_KERNEL=2.4.1 to "emulate" that behaviour. This is gone in SLES 10.

Markus

[Former Member · Accepted solution]

Hello to all,

thanks for your support, everybody earned some reward points.....

[Former Member]

I suspect a permission problem. Please run sdbverify as root and post the output.

Regards,

Marc-Philip

[Former Member]

Hi Marc-Philip,

I can't find sdbverify....We installed the following rpm's:

infra01:/opt/sdb/7500/pgm # rpm -qa | grep max

maxdb-scriptif-7.5.0.38-1

maxdb-web-7.5.0.38-1

maxdb-ind-7.5.0.38-1

maxdb-callif-7.5.0.38-1

maxdb-srv75-7.5.0.38-1

Where can I get "sdbverify" ?

[Former Member]

Hi Gerd,

sdbverify is in <IndepProgPath>/bin. To find this, take the output of

 dbmcli dbm_getpath IndepProgPath 

and append bin/sdbverify. Execute it as root (taken from OSS note 546737).

HTH,

Marc-Philip

Edited by: Marc-Philip Werner on Jul 7, 2008 12:00 PM

[Former Member]

Hello Marc-Philip,

thanks for your hint, but there's no sdbverify:

infra01:/var/opt/sdb/data/wrk # cd /opt/sdb/programs/bin/

infra01:/opt/sdb/programs/bin # ./dbmcli dbm_getpath IndepProgPath

OK

/opt/sdb/programs

infra01:/opt/sdb/programs/bin # ./sdbverify

-bash: ./sdbverify: Datei oder Verzeichnis nicht gefunden

As mentioned earlier we've installed MaxDB 7.5.0.38 with the following rpm's:

infra01:/opt/sdb/programs/bin # rpm -qa | grep max

maxdb-scriptif-7.5.0.38-1

maxdb-web-7.5.0.38-1

maxdb-ind-7.5.0.38-1

maxdb-callif-7.5.0.38-1

maxdb-srv75-7.5.0.38-1

[Former Member]

Hi Gerd,

as you installed rpm packages, you have no sdbverify. Sorry. Let's try something else.

Please provide the following:

• content of file /etc/opt/sdb

• permissions of folder /devspace/TEST

• permissions of folder /var/opt/sdb/data/wrk/TEST

• permissions of /opt/sdb/7500/pgm/dbmsrv

• permissions of /opt/sdb/7500/pgm/kernel

Regards,

Marc-Philip

[Former Member]

Hello,

here's the information:

infra01:/opt/postgres/data/base> cat /etc/opt/sdb

[Globals]

IndepData=/var/opt/sdb/data

IndepPrograms=/opt/sdb/programs

SdbOwner=sdb

SdbGroup=sdba

infra01:/opt/postgres/data/base> ll /devspace/

insgesamt 20

drwx------ 2 sdb sdba 16384 3. Jul 05:54 lost+found

drwxrwxrwx 2 sdb sdba 4096 4. Jul 11:35 TEST

infra01:/usr/bin # ll /var/opt/sdb/data/wrk/

insgesamt 100

-rw-rw---- 1 sdb sdba 6920 4. Jul 11:39 dbmsrv_infra01.prt

drwxrwx--- 2 sdb sdba 4096 4. Jul 11:30 .M750038

-rw-rw---- 1 sdb sdba 4 4. Jul 11:30 niserver_infra01.pid

-rw-rw---- 1 sdb sdba 149 4. Jul 11:30 niserver_infra01.prot

-rw-rw---- 1 sdb sdba 192 4. Jul 11:30 niserver_infra01.trace

drwxrwx--- 2 sdb sdba 4096 4. Jul 11:35 sdb

drwxrwx--- 2 sdb sdba 4096 4. Jul 13:14 TEST

-rw-r----- 1 sdb sdba 65536 4. Jul 11:30 xserver_infra01.prt

infra01:/usr/bin # ll /opt/sdb/7500/pgm/dbmsrv

-r-sr-s--x 1 sdb sdba 4258763 17. Aug 2006 /opt/sdb/7500/pgm/dbmsrv

infra01:/usr/bin # ll /opt/sdb/7500/pgm/kernel

-r-xr-x--- 1 sdb sdba 13012362 17. Aug 2006 /opt/sdb/7500/pgm/kernel

byeGERD

[Former Member]

Hi Gerd,

permissions seem to look okay.

Hmm, we're now entering an area that I'm not so familiar with, but could you please check OSS note [788272|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=788272]?

It looks like your having a problem with the thread model that your MaxDB software is compiled with.

HTH,

Marc-Philip