maxdb give Kernel error after upgrade from 7.3 to 7.5

[former_member260782]

Hi, our DBA is running into problems after upgrading from 7.3 to 7.5. When we attempt to start the DB we get this error:

dbmcli -d sd3 -u XXXXXX,XXXXXX db_online

ERR

-24994,ERR_RTE: runtime environment error

1,Check knldiag! Kernel died before reaching ADMIN state

The details of the error in knldiag are:

2008-07-02 14:22:39 19 11554 COMMUNIC UKT8 attached big comseg at 0x700000060000000

2008-07-02 14:22:39 19 11555 COMMUNIC UKT8 big comseg ends at 0x7000000601803F8

2008-07-02 14:22:39 16 ERR 20152 RTE UNIX change owner with chown(knltrace,964,202) failed: Not owner

2008-07-02 14:22:39 16 11000 vdevsize 'knltrace', 666 failed

2008-07-02 14:22:39 16 ERR 11202 vdiagini vdevsize of kernel trace file unsuccsessful

2008-07-02 14:22:39 16 ERR 11599 BTRACE -

---

> Emergency Stack Back Trace <----

As said, he performed the upgrade and now we can't start the DB, anybody that had the same issue?

We run on AIX 5.3 and from the unix side, nothing changed. After 7.5 we plan on going to 7.6 but that is in the stars I guess...

We posted a high message with SAP and since over 10 hours nobody picked the message up... we are getting kind of desperate... Any pointers are appreciated...

thanks

[markus_doehr2 · Accepted solution]

> 2008-07-02 14:22:39 16 ERR 20152 RTE UNIX change owner with chown(knltrace,964,202) failed: Not owner

> 2008-07-02 14:22:39 16 11000 vdevsize 'knltrace', 666 failed

> 2008-07-02 14:22:39 16 ERR 11202 vdiagini vdevsize of kernel trace file unsuccsessful

> 2008-07-02 14:22:39 16 ERR 11599 BTRACE -

---

> Emergency Stack Back Trace <----

>

> We posted a high message with SAP and since over 10 hours nobody picked the message up... we are getting kind of desperate... Any pointers are appreciated...

>

Is the knltrace file (usually /sapdb/data/wrk/<SID>/knltrace) on an NFS directory?

Markus

[former_member260782 · Accepted solution]

Thanks for your input and I checked, nothing from the sapdb is mounted on nfs. We have some other directories nfs mounted, but they are software repository etc.

thank you

[markus_doehr2 · Accepted solution]

> Thanks for your input and I checked, nothing from the sapdb is mounted on nfs. We have some other directories nfs mounted, but they are software repository etc.

Ok - so what permission has this file? Does it exist?

Markus

[former_member229109 · Accepted solution]

Hollo Thomas,

please see my with reply above & update the thread with aditional:

information.

THank you & best regards, Natalia Khlopina

[former_member229109]

Hello Thomas,

-> If you run the database update using the database update tool, the permissions/ownership will be set correctly for the database software & the permissions/ownership of the database log files will be also changed correctly.

Please check the upgrade log in the /sapdb/data/wrk

-> Please check the ownership of the files in the database RUNDIRECTORY.

For example, if the database owner:group of your database is sdb:sdba, then

-rw-rw---- 1 sdb sdba u2026. knltrace

-> Please update the thread with the output of the following commands :

sdbregview -l

xinstinfo SD3

id sdb

ls -l <runditectory>

< rundirectory is the database parameter value and by default is /sapdb/data/wrk/SD3 >

more /etc/opt/sdb

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Thomas,

be aware that the Databaseowner changes to sdb and group sdba!

Check the rights of your files.

I think you have to add user sqd<SID> to group sdba.

Check Note:

669711

Check for Bad Indexes after Upgrade.

There is an Document "Upgrade to MaxDB by MySQL Version 7.5.00" in the Servicemarketplace.

Regards

Manuel