-24994: ERR_RTE - runtime environment error

[Former Member]

Hi All,

We are facing a great problem with MaxDB, if we start the service of maxdb first it will run after starting the SAP server or maxdb into online mode; the MaxDB service automatically going offline mode.

what might be the problem, if we try manually any db_online and systab_load its giving the below error

• -24994: ERR_RTE - runtime environment error,1, connection broken*.

Can i have solution to this problem? Any body has the solution let me know.....

Thanks &Regards,

Sridhar

[antonio_nunes1]

Hi, this could be missing environment variables at OS level for user <SID>adm

It happens with some frequence in Microsoft Windows 2008

[Former Member]

After applying the patch of MaxDB. The datbase came into the online mode and server is running fine.

[markus_doehr2]

Please post the logfiles

knldiag

knldiag.err

and if you post the logs here please put code tags (the << >> sign next to the underline button) around your logfiles, this will make them being readable much easier.

Markus

[Former Member]

Hi Markus,

Thanks for your quick response,the log files are as follows:

knldiag:

2009-01-26 15:56:29 0x1650 31 SrvTasks Permanently reserved 33 servertasks for 'Backup / Restore'.

2009-01-26 15:56:29 0x1650 31 SrvTasks Permanently reserved 2 servertasks for 'Backup / Restore'.

2009-01-26 15:56:29 0x153C 3 RunTime State changed from STARTING to ADMIN

2009-01-26 15:56:29 0x1650 31 SrvTasks Permanently reserved 1 servertasks for 'Savepoint'.

2009-01-26 15:56:29 0x153C 19601 DBSTATE SERVERDB is ready

============================================ begin of write cycle ==================

2009-01-26 15:56:29 0x15AC 19633 CONNECT Connect req. (T305, Node:'', PID:4884)

2009-01-26 16:05:21 0x115C 19633 CONNECT Connect req. (T37, Node:'', PID:3640)

2009-01-26 16:05:21 0x115C 19633 CONNECT Connect req. (T38, Node:'', PID:3640)

2009-01-26 16:05:21 0x115C 19615 VOLUMEIO Attaching volume 'E:\sapdb\PIP\sapdata\DISKD0001'

2009-01-26 16:05:21 0x498 19613 DBSTATE I/O thread for 'E:\sapdb\PIP\sapdata\DISKD0001' started

2009-01-26 16:05:21 0x115C 19616 VOLUMEIO Detaching volume 'E:\sapdb\PIP\sapdata\DISKD0001'

2009-01-26 16:05:21 0x498 19614 DBSTATE I/O thread for 'E:\sapdb\PIP\sapdata\DISKD0001' stopped

2009-01-26 16:05:21 0x115C 19615 VOLUMEIO Attaching volume 'E:\sapdb\PIP\sapdata\DISKD0001'

2009-01-26 16:05:21 0x147C 19613 DBSTATE I/O thread for 'E:\sapdb\PIP\sapdata\DISKD0001' started

2009-01-26 16:05:21 0x115C 19616 VOLUMEIO Detaching volume 'E:\sapdb\PIP\sapdata\DISKD0001'

2009-01-26 16:05:21 0x147C 19614 DBSTATE I/O thread for 'E:\sapdb\PIP\sapdata\DISKD0001' stopped

2009-01-26 16:05:21 0x115C 19615 VOLUMEIO Attaching volume 'D:\sapdb\PIP\saplog\DISKL001'

2009-01-26 16:05:21 0x7A0 19613 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL001' started

2009-01-26 16:05:21 0x115C 19615 VOLUMEIO Attaching volume 'D:\sapdb\PIP\saplog\DISKL002'

2009-01-26 16:05:21 0xECC 19613 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL002' started

2009-01-26 16:05:21 0x115C 19616 VOLUMEIO Detaching volume 'D:\sapdb\PIP\saplog\DISKL001'

2009-01-26 16:05:21 0x7A0 19614 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL001' stopped

2009-01-26 16:05:21 0x115C 19616 VOLUMEIO Detaching volume 'D:\sapdb\PIP\saplog\DISKL002'

2009-01-26 16:05:21 0xECC 19614 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL002' stopped

2009-01-26 16:05:21 0x115C 19677 CONNECT Client has released connection, T38

2009-01-26 16:05:21 0x115C 19651 CONNECT Connection released, T38

2009-01-26 16:05:21 0x115C 19677 CONNECT Client has released connection, T37

2009-01-26 16:05:21 0x115C 19651 CONNECT Connection released, T37

2009-01-26 16:06:15 0x115C 19633 CONNECT Connect req. (T39, Node:'', PID:5576)

2009-01-26 16:06:15 0x115C 19615 VOLUMEIO Attaching volume 'E:\sapdb\PIP\sapdata\DISKD0001'

2009-01-26 16:06:15 0x12CC 19613 DBSTATE I/O thread for 'E:\sapdb\PIP\sapdata\DISKD0001' started

2009-01-26 16:06:15 0x115C 19616 VOLUMEIO Detaching volume 'E:\sapdb\PIP\sapdata\DISKD0001'

2009-01-26 16:06:15 0x12CC 19614 DBSTATE I/O thread for 'E:\sapdb\PIP\sapdata\DISKD0001' stopped

2009-01-26 16:06:15 0x115C 19615 VOLUMEIO Attaching volume 'D:\sapdb\PIP\saplog\DISKL001'

2009-01-26 16:06:15 0x300 19613 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL001' started

2009-01-26 16:06:15 0x115C 19615 VOLUMEIO Attaching volume 'D:\sapdb\PIP\saplog\DISKL002'

2009-01-26 16:06:15 0x17C4 19613 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL002' started

2009-01-26 16:06:15 0x115C 19616 VOLUMEIO Detaching volume 'D:\sapdb\PIP\saplog\DISKL001'

2009-01-26 16:06:15 0x300 19614 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL001' stopped

2009-01-26 16:06:15 0x115C 19616 VOLUMEIO Detaching volume 'D:\sapdb\PIP\saplog\DISKL002'

2009-01-26 16:06:15 0x17C4 19614 DBSTATE I/O thread for 'D:\sapdb\PIP\saplog\DISKL002' stopped

2009-01-26 16:06:15 0x115C 19677 CONNECT Client has released connection, T39

2009-01-26 16:06:15 0x115C 19651 CONNECT Connection released, T39

-

---

current write position -

---

knldiag.err:

2009-01-26 13:24:12 --- Starting GMT 2009-01-26 05:24:12 7.6.00 Build 035-123-139-084

2009-01-26 13:31:13 --- Starting GMT 2009-01-26 05:31:13 7.6.00 Build 035-123-139-084

2009-01-26 13:39:58 --- Starting GMT 2009-01-26 05:39:58 7.6.00 Build 035-123-139-084

2009-01-26 13:53:38 --- Starting GMT 2009-01-26 05:53:38 7.6.00 Build 035-123-139-084

2009-01-26 13:57:52 ___ Stopping GMT 2009-01-26 05:57:52 7.6.00 Build 035-123-139-084

2009-01-26 13:57:55 --- Starting GMT 2009-01-26 05:57:55 7.6.00 Build 035-123-139-084

2009-01-26 14:01:35 --- Starting GMT 2009-01-26 06:01:35 7.6.00 Build 035-123-139-084

2009-01-26 14:13:08 --- Starting GMT 2009-01-26 06:13:08 7.6.00 Build 035-123-139-084

2009-01-26 15:15:56 --- Starting GMT 2009-01-26 07:15:56 SLOW 7.6.00 Build 035-123-139-084

2009-01-26 15:17:09 0xF84 ERR 20000 SAPDBErr Container_Vector.hpp:245

2009-01-26 15:17:09 0xF84 ERR 20000 SAPDBErr 2009-01-26 15:17:09 SAPDBErr Error 20000

2009-01-26 15:17:09 0xF84 ERR 20000 SAPDBErr Assertion of state n < m_Size failed!

2009-01-26 15:17:09 0xF84 ERR 18196 DBCRASH vabort:Emergency Shutdown, Container_Vector.hpp: 245

2009-01-26 15:21:23 --- Starting GMT 2009-01-26 07:21:23 7.6.00 Build 035-123-139-084

2009-01-26 15:48:54 --- Starting GMT 2009-01-26 07:48:54 7.6.00 Build 035-123-139-084

2009-01-26 15:53:21 --- Starting GMT 2009-01-26 07:53:21 7.6.00 Build 035-123-139-084

2009-01-26 15:56:25 --- Starting GMT 2009-01-26 07:56:25 7.6.00 Build 035-123-139-084

Please give me some idea to solve this problem.

Thanks & Regards,

Sridhar

[markus_doehr2]

> 2009-01-26 15:15:56 --- Starting GMT 2009-01-26 07:15:56 SLOW 7.6.00 Build 035-123-139-084

> 2009-01-26 15:17:09 0xF84 ERR 20000 SAPDBErr Container_Vector.hpp:245

> 2009-01-26 15:17:09 0xF84 ERR 20000 SAPDBErr 2009-01-26 15:17:09 SAPDBErr Error 20000

> 2009-01-26 15:17:09 0xF84 ERR 20000 SAPDBErr Assertion of state n < m_Size failed!

> 2009-01-26 15:17:09 0xF84 ERR 18196 DBCRASH vabort:Emergency Shutdown, Container_Vector.hpp: 245

You are using an ANCIENT database build...

I have unfortunately no idea what's causing that error... Are you a SAP customer? If yes, I'd open an OSS call.

Markus

[Former Member]

Hi Markus,

We have the MaxDB server with 7.6.0.0.35 version, one of the guy from SAP support check the Log files, MaxDB status he suggested us to apply the support package for maxDB.

we have doubt which one we have to apply.... i mean 7.7 or 7.6.04.12, 7.6.04.16 or some else..Please let me know ehich one we have to apply...

We have SAP customerID ..but we are working on client system, we have to get confirmation from them.

Thanks & Regards,

Sridhar

[markus_doehr2]

> we have doubt which one we have to apply.... i mean 7.7 or 7.6.04.12, 7.6.04.16 or some else..Please let me know ehich one we have to apply...

I would use 7.6.05.12 (or 7.6.05.14 when available).

Markus