Rusanov wrote : >Hello, I'm use MaxDB Version: '7.5.00.05 Build 005-121-054-885' Windows 2000 >(WIN32) >I have problem, my database crash
>I execute my perl script and my database crash >if I execute my perl script once more, I have error message >DBD::ODBC::st execute failed: [SAP AG][SQLOD32 DLL][SAP DB] General >error;-9041 POS(1) System error: BD Index not access >ible. (SQL-HY000)(DBD: st_execute/SQLExecute err=-1) at ./add_result.pl line >48. >executing: err = -1, errstr = [SAP AG][SQLOD32 DLL][SAP DB] General >error;-9041 POS(1) System error: BD Index not access >ible. (SQL-HY000)(DBD: st_execute/SQLExecute err=-1) at ./add_result.pl line >48. >Having tested the procedure, I've found the >reason of crash. If I comment call LAB.get_reagent4device in >LAB.add_unplanned_test >, the crash is not happening. >my eventlog >Event Type: Error >Event Source: SAPDB:Labtest >Event Category: Fast >Event ID: 18006 >Date: 24.12.2003 >Time: 12:57:06 >User: NT AUTHORITY\SYSTEM >Computer: UFO >Description: >SAPDB - Labtest : >- ERROR TID: 0x4F4 PID: 0x8DC MsgID: 18006 > EXCEPTION:0xc0000005 Addr:0x5fc1fa ( 0:0x22:0:0 ) >Event Type: Error >Event Source: SAPDB:Labtest >Event Category: Fast >Event ID: 18245 >Date: 24.12.2003 >Time: 12:57:09 >User: NT AUTHORITY\SYSTEM >Computer: UFO >Description: >SAPDB - Labtest : > - ERROR TID: 0x4F4 PID: 0x8DC MsgID: 18245 > Kernel aborts, > (view diagnostic file: 'knldiag') This is a bug that is caused by accessing the system tables inside a db-procedure. In your example SELECT APPLNODEID FROM SYSDBA.TRANSACTIONS T, DOMAIN.CONNECTPARAMETERS C WHERE T.SESSION = C.SESSION; causes the problem. This will be fixed with one of the next versions. The error -9041 is a consequence of the crash, because indexes are not recovered automatically but have to be rebuild explicitely (DBMGUI->Recovery->Index). Thanks for mailing the bug, Thomas -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
