-24994,ERR_RTE: runtime environment error? Please advice.

[Former Member]

UPDATE AT BOTTOM

Hello experts,

My provider moved on the last feb,9; after this my db refuses to connect simple Henplus shell:

Hen*Plus> connect jdbc:sapdb://localhost/TGOO

HenPlus II connecting

url 'jdbc:sapdb://localhost/TGOO'

driver version 7.6

SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/TGOO [Cannot connect to host localhost [Connection refused], -813.].

============ authorization required ===

Username: tgoo

Password:

com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/TGOO [Cannot connect to host localhost [Connection refused], -813.].

I wanted to check wether the db was online and running:

~ $ dbmcli -n localhost -d TGOO -u dbm,dbm db_state

OK

State

OFFLINE

Ok, it's offline. let's start it:

~ $ dbmcli -n localhost -d TGOO -u dbm,dbm db_online

ERR

-24994,ERR_RTE: runtime environment error

1,Database TGOO already started

I'm running Sap MaxDB 1.5.0 on Gentoo Linux

What is going on here? I tried searching without results.

Knldiag can't fit into this msg. Last lines follows:

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: '+++++++++++++++++++++++++++++++++++++++++++++++++'

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: '+++++++++++++++++++ Kernel Forked +++++++++++++++'

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: 'TGOO'

2012-02-10 11:40:23 1 12771 INFO Process ID: 5649

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: '+++++++++++++++++++++++++++++++++++++++++++++++++'

(manymany lines)

2012-02-10 11:40:23 7 206 RTE Kernel state changed from STARTING to ADMIN

======================================= end of startup part ====================

2012-02-10 11:40:23 7 11570 startup complete

2012-02-10 11:40:26 8 11561 COMMUNIC Connecting T73 local 5575

2012-02-10 11:40:26 15 11561 COMMUNIC Connected T73 local 5575

2012-02-10 11:40:26 15 11560 COMMUNIC Releasing T73

2012-02-10 11:40:26 15 12929 TASKING Task T73 started

2012-02-10 11:40:26 15 11007 COMMUNIC wait for connection T73

2012-02-10 11:40:26 8 11561 COMMUNIC Connecting T73 local 5575

2012-02-10 11:40:26 15 11561 COMMUNIC Connected T73 local 5575

2012-02-10 11:40:26 15 11560 COMMUNIC Releasing T73

2012-02-10 11:40:26 15 12929 TASKING Task T73 started

2012-02-10 11:40:26 15 11007 COMMUNIC wait for connection T73

-

---

current write position -

---

Db seems on ADMIN state, not offline.

Can anybody please give me a clue?

This was meant to be back in PROduction once moved.

MaxM

UPDATE

(Updated at bottom)

Original question follows:

Hello experts,

My provider moved on the last feb,9; after this my db refuses to connect simple Henplus shell:

Hen*Plus> connect jdbc:sapdb://localhost/TGOO

HenPlus II connecting

url 'jdbc:sapdb://localhost/TGOO'

driver version 7.6

SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/TGOO [Cannot connect to host localhost [Connection refused], -813.].

============ authorization required ===

Username: tgoo

Password:

com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/TGOO [Cannot connect to host localhost [Connection refused], -813.].

I wanted to check wether the db was online and running:

~ $ dbmcli -n localhost -d TGOO -u dbm,dbm db_state

OK

State

OFFLINE

Ok, it's offline. let's start it:

~ $ dbmcli -n localhost -d TGOO -u dbm,dbm db_online

ERR

-24994,ERR_RTE: runtime environment error

1,Database TGOO already started

I'm running Sap MaxDB 1.5.0 on Gentoo Linux

What is going on here? I tried searching without results.

Knldiag can't fit into this msg. Last lines follows:

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: '+++++++++++++++++++++++++++++++++++++++++++++++++'

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: '+++++++++++++++++++ Kernel Forked +++++++++++++++'

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: 'TGOO'

2012-02-10 11:40:23 1 12771 INFO Process ID: 5649

2012-02-10 11:40:23 1 12769 INFO Starting SERVERDB: '+++++++++++++++++++++++++++++++++++++++++++++++++'

(manymany lines)

2012-02-10 11:40:23 7 206 RTE Kernel state changed from STARTING to ADMIN

======================================= end of startup part ====================

2012-02-10 11:40:23 7 11570 startup complete

2012-02-10 11:40:26 8 11561 COMMUNIC Connecting T73 local 5575

2012-02-10 11:40:26 15 11561 COMMUNIC Connected T73 local 5575

2012-02-10 11:40:26 15 11560 COMMUNIC Releasing T73

2012-02-10 11:40:26 15 12929 TASKING Task T73 started

2012-02-10 11:40:26 15 11007 COMMUNIC wait for connection T73

2012-02-10 11:40:26 8 11561 COMMUNIC Connecting T73 local 5575

2012-02-10 11:40:26 15 11561 COMMUNIC Connected T73 local 5575

2012-02-10 11:40:26 15 11560 COMMUNIC Releasing T73

2012-02-10 11:40:26 15 12929 TASKING Task T73 started

2012-02-10 11:40:26 15 11007 COMMUNIC wait for connection T73

-

---

current write position -

---

Db seems on ADMIN state, not offline.

Can anybody please give me a clue?

This was meant to be back in PROduction once moved.

UPDATE

Ipotethically, should I apply what follows:

maxdb@pimpamplum ~ $ ls -l /home1/maxdb/sdb/data/pid

total 4

-rw-r----- 1 maxdb sdba 5 Feb 10 11:40 TGOO

drwxrwx--- 2 maxdb sdba 48 Nov 29 2005 serverpids

maxdb@pimpamplum ~ $ ls -l /home1/maxdb/sdb/data/ppid

total 4

-rw-r----- 1 maxdb sdba 5 Feb 10 11:40 TGOO

maxdb@pimpamplum ~ $ ls -l /home1/maxdb/sdb/data/fifo

total 0

prwww- 1 maxdb sdba 0 Feb 10 11:40 TGOO

prw-rw---- 1 maxdb sdba 0 Feb 9 10:06 xserver_pimpamplum_logger

prw-rw---- 1 maxdb sdba 0 Jul 3 2010 xserver_pimpamplum_update

maxdb@pimpamplum ~ $ ps -efe | grep kernel

maxdb 12915 12712 0 17:37 pts/1 00:00:00 grep kernel

maxdb@pimpamplum ~ $ ps -efe | grep sdb

maxdb 12917 12712 0 17:37 pts/1 00:00:00 grep sdb

maxdb@pimpamplum ~ $ more /etc/opt/sdb

[Globals]

IndepData=/home1/maxdb/sdb/data

IndepPrograms=/home1/maxdb/sdb/programs

SdbOwner=maxdb

SdbGroup=sdba

maxdb@pimpamplum ~ $ uname -a

Linux pimpamplum 2.6.12min #1 SMP Mon Nov 28 13:57:10 CET 2005 x86_64 Intel(R) Xeon(TM) CPU 3.00GHz GenuineIntel GNU/Linux

maxdb@pimpamplum ~ $ more /sapdb/data/pid/TGOO

/sapdb/data/pid/TGOO: No such file or directory

maxdb@pimpamplum ~ $ more /home1/maxdb/sdb/data/pid/TGOO

5649

maxdb@pimpamplum ~ $ ps -efe | grep 5649

www 5649 5152 0 Feb10 ? 00:00:00 /usr/sbin/apache

maxdb 12935 12712 0 17:42 pts/1 00:00:00 grep 5649

... and now?

mv /home1/maxdb/sdb/data/pid/TGOO /home1/maxdb/sdb/data/pid/TGOO.old ?

<ARE THERE database kernel processes active?? ++ delete /home1/maxdb/sdb/data/pid/TGOO.old later??>

dbmcli etc db_admin to restart the database TGOO??

---

taken from earlier sample Natalia Khlopin @ Re: MaxDB killed by Power Outage! Posted: Mar 22, 2011 7:23 PM in response to: Jan Bronee in response to: Jan Bronee on )

---

MaxM

Edited by: MMemory on Feb 13, 2012 5:44 PM

[former_member229109]

Hello,

from posted information is not clear what is your problem.

Please post the output of the commands:

dbmcli inst_enum

dbmcli db_enum

xinstinfo <DB-SID>

ps -efe | grep sdb

Regards, Natalia Khlopina

[Former Member]

Hello Natalia,

thanks for your reply.

here are the outputs:

>inst_enum

OK

7.5.0.31 /home1/maxdb/sdb/7500

---

dbmcli on TGOO>db_enum

OK

TGOO /home1/maxdb/sdb/7500 7.5.0.31 fast offline

TGOO /home1/maxdb/sdb/7500 7.5.0.31 quick offline

TGOO /home1/maxdb/sdb/7500 7.5.0.31 slow offline

---

maxdb@localhost ~ $ xinstinfo TGOO

IndepData : /home1/maxdb/sdb/data

IndepPrograms : /home1/maxdb/sdb/programs

InstallationPath : /home1/maxdb/sdb/7500

Kernelversion : KERNEL 7.5.0 BUILD 031-123-104-253

Rundirectory : /home1/maxdb/sdb/data/wrk/TGOO

maxdb@localhost ~ $ ps -efe | grep sdb

maxdb 14231 14211 0 09:10 pts/1 00:00:00 grep sdb

I cannot connect anymore and I can't get it online.

MaxM

(I learnt something in the last two years, but still I'm a novice - Plus, apart from the last time I messed it up two years ago, this db has been up and running since 08/2005 without interruptions! not bad, really).

[former_member229109]

Hello MaxM,

from the provided iformation, I assummed that the database server was shutdown when the database was online.

And there are some rutime information which was not clean up properly.

There were some known issues in the past, you have old version.

But as it's working fine for 2y online with your applications => fine.

But still recommend to plan the database update to new releases.

To fix the reported issue;

• Check that the database kernel processes are not running first:

"ps -efe | grep sdb"

"ps -efe | grep kernel"

• According the output of your commands & "db_enum" the database kernel is not running

=>

in /home1/maxdb/sdb/data/pid and /home1/maxdb/sdb/data/ppid

rename < mv> the TGOO file to TGOO.old

then restart the database using dbm command "db_online".

Regards, Natalia Khlopina

Regards, Natalia Khlopina

[Former Member]

Thank you Natalia,

the db started and that is good.

~ # mv /home1/maxdb/sdb/data/ppid/TGOO /home1/maxdb/sdb/data/ppid/TGOO.old

~ # mv /home1/maxdb/sdb/data/pid/TGOO /home1/maxdb/sdb/data/pid/TGOO.old

~ $ dbmcli -d TGOO -u dbm,dbm

dbmcli on TGOO>db_online

OK

think it's ok now, you agree?

--- (check)>

~ # ps -efe | grep sdb

maxdb 16831 1 0 11:53 ? 00:00:00 /home1/maxdb/sdb/7500/pgm/kernel TGOO

maxdb 16835 16831 0 11:53 ? 00:00:03 /home1/maxdb/sdb/7500/pgm/kernel TGOO

root 16926 16557 0 12:06 pts/0 00:00:00 grep sdb

~ # ps -efe | grep kernel

maxdb 16831 1 0 11:53 ? 00:00:00 /home1/maxdb/sdb/7500/pgm/kernel TGOO

maxdb 16835 16831 0 11:53 ? 00:00:03 /home1/maxdb/sdb/7500/pgm/kernel TGOO

root 16928 16557 0 12:07 pts/0 00:00:00 grep kernel

maxdb@pimpamplum ~ $ dbmcli -d TGOO -u dbm,dbm

dbmcli on TGOO>db_enum

OK

TGOO /home1/maxdb/sdb/7500 7.5.0.31 fast running

TGOO /home1/maxdb/sdb/7500 7.5.0.31 quick offline

TGOO /home1/maxdb/sdb/7500 7.5.0.31 slow offline

This solved the 'db offline' issue - thanks again.

Still, I'm unable to connect maybe due to somthing wrong elsewhere:

Hen*Plus> connect jdbc:sapdb://localhost/TGOO

HenPlus II connecting

url 'jdbc:sapdb://localhost/TGOO'

driver version 7.6

SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/TGOO [Cannot connect to host localhost [Connection refused], -813.].

============ authorization required ===

Username: ok

Password: ok

com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to jdbc:sapdb://localhost/TGOO [Cannot connect to host localhost [Connection refused], -813.].

... has this any sense? I don't know where to address my efforts. The server changed its public IP - Are there drivers to be reconfigured? reinstalled? (Again, forgive my ignorance / newbiness I'm reading manuals and manuals and manuals and on...

Cheers

Max M

SOLVED: we had a firewall issue.

Edited by: MMemory on Feb 20, 2012 4:23 PM