The reason for the crash might be that I started the db with db_online -s. After starting it with the normal Kernel everything was fine. The restore from an older version should work (and it did) without any problem. Sometimes you have to load sysem tables. Thanx
Kevin Wilson wrote:
You should have upgraded the .25 server which would have upgraded your server instance data.
Also, if you are going to upgrade then you should at least go to latest version of the 7.3 series. I took a .29 server to .34 without issue using the upgrade util provided by SAP.
-----Original Message----- From: Georg Thome To: [EMAIL PROTECTED] Sent: 8/11/2003 3:25 AM Subject: db 7.3.4.25->7.3.4.27 crash
Hi all,
after the installation of 7.3.4.27 and a restore of a database which was previously running on 7.3.4.25 I get an emergency shutdown every few minutes. I think the shutdown depends on the applications which are connecting and using the different kind of data. The zipped diag history path is a little bit to large to post in here.
We have it running on - SuSE 7.3 - Kernel 2.4.16 - sofware raid for data and log as raw devices
Does a verify of the devspaces help or do you have any other suggestions?
2003-08-11 09:57:28 4458 ERR 53000 B*TREE BD450_CHECK: wrong Index; 0 2003-08-11 09:57:28 4458 ERR 11599 BTRACE ----> Emergency Stack Back Trace <---- ... ... 2003-08-11 09:57:28 4458 12820 EXCEPT calling ak dump for T45 2003-08-11 09:57:28 4458 ERR 11196 DBCRASH vabort:Emergency Shutdown, Task: 45 2003-08-11 09:57:28 4458 12696 DBSTATE Change DbState to 'KILL'(28) 2003-08-11 09:57:28 4416 12825 TASKING state 28 before shutkill(1) 2003-08-11 09:57:28 4416 12825 TASKING state 28 before shutkill(1) 2003-08-11 09:57:28 4458 12697 DBSTATE Resuming tracewriter 2003-08-11 09:57:28 4458 12825 TASKING state 28 before shutkill(1) 2003-08-11 09:57:28 4458 WNG 11824 COMMUNIC Releasing T38 database shutdown
Thanx
Georg
****************May the sapdb be with you****************
This e-mail may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you are not the intended recipient and have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal from your system. Thank you for your co-operation.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
****************May the source be with you****************
This e-mail may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you are not the intended recipient and have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal from your system. Thank you for your co-operation.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
