BasisError: 1900 means e_shutdown. This can occur if a transaction is running and a shutdown is wanted.
First the shutdown tries to wait for open write transactions but after REQUEST_TIMEOUT time a "shutdown quick" is forced which writes a savepoint and terminates the database. In this case a running transaction got the signal to shutdown and must rollback its work. During the rollback the shutdown process goes on and terminates the datacache. The rollbacking transaction access the datacache and receives e_shutdown. During rollback no errors are allowed so the rollbacking transaction causes the emergency shutdown. The next restart will complete the rollback of this aborted rollbacking transaction so the data is consistent. This error can be ignored ! In >V7.4 this cannot occur because the savepoint triggered for shutdown immediately terminates the kernel after savepoint end without switching off the cache before. So in >V7.4 the error 1900(e_shutdown) cannot occut. Kind regards Uwe -----Urspr�ngliche Nachricht----- Von: ajit [mailto:[EMAIL PROTECTED] Gesendet: Montag, 17. November 2003 18:00 An: [EMAIL PROTECTED] Betreff: Database crash Hi, I'm running sapdb 7.3.30 the db crashed with the following in the error log. 2003-11-08 07:51:12 0x674 ERR 18431 MESSAGES Could not write to event log, rc = 31 2003-11-08 08:14:22 --- Starting --- 2003-11-17 19:11:04 0x7BC ERR 52000 LOG Pos: Log: 231827.1061 2003-11-17 19:11:04 0x7BC ERR 52000 LOG BasisError: 1900 2003-11-17 19:11:04 0x7BC ERR 52000 LOG LogType=18,0 2003-11-17 19:11:04 0x7BC ERR 52050 SHUTDOWN rollback/shutdown 2003-11-17 19:11:04 0x7B4 ERR 53017 I/O SYSDEV DEVNO: 1 2003-11-17 19:11:04 0x7B4 ERR 53016 I/O E:/sapdb/data/SYSTEM01 2003-11-17 19:11:04 0x7BC ERR 52050 SHUTDOWN *** EMERGENCY ***: 1900 2003-11-17 19:17:57 --- Starting --- A few days prior to this the param logmode was changed from dual to single.(however it was not restarted so the param has not taken affect). Other than that it has been under normal operation. After the crash the db hangs when trying to bring it into db_warm/db_online Could someone pls advice as to the cause of crash and possible fixes. regards, Ajit -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
