Frank Schimmelpfennig wrote: > > Hello, > > I faced a SYSERROR -9999 on a MaxDB 7.6 instance (7.6.00 Build > 012-123-102-632 on Windows Server 2003 Std.Edt. SP1) when I tried to > update > a record in a user table: > > UPDATE calling_modules > SET ver_id = (SELECT ver_id FROM snr_versions WHERE release_no = > '1.3.2') > WHERE module_name = 'SNR_PUT_INCREMENT' > // > > or > > UPDATE calling_modules > SET ver_id = 6 > WHERE module_name = 'SNR_PUT_INCREMENT' > // > > or > > UPDATE calling_modules > SET ver_id = 6 > WHERE mod_id = 16 > // > > All three variants of the SQL statement led to the same error message.Here > are the knldiag.err entries: > > 2005-12-05 16:18:19 0xA74 ERR 51080 SYSERROR -9999 Otherwise unknown > errorcode > 2005-12-05 16:18:19 0xA74 ERR 51080 SYSERROR -9999 Otherwise unknown > errorcode > 2005-12-05 16:20:09 0xA74 ERR 51080 SYSERROR -9999 Otherwise unknown > errorcode > > Is there someone who has an idea what is going on?
Not really. But perhaps the table definition and/or view definition and the foreign key / triggers concerned + a vtrace 1. Start the trace: dbmcli -d <dbname> -u <dbm,dbm> db_execute diagnose vtrace default on 2. Execute some SQL 3. Flush the trace: dbmcli -d <dbname> -u <dbm,dbm> db_execute diagnose vtrace flush or more simply dbmcli -d <dbname> -u <dbm,dbm> trace_flush 4. Create the text representation: dbmcli -d <dbname> -u <dbm,dbm> trace_prot akb 5. Copy the text representation to a local file: dbmgetf -d <dbname> -u <dbm,dbm> -k KNLTRCPRT -f <local file name> 6. Stop writing of the trace: dbmcli -d <dbname> -u <dbm,dbm> db_execute diagnose vtrace default off. Be sure to do this after you found the problem. Writing the VTrace will degrade the performance. Note that the VTrace options will survive a restart. But pleas change a little bit: - switch on not only default, but default select update - do not use only AKB, but AKBM Elke SAP Labs Berlin > > Thanks in advance! > > kind regards > Frank > > > -- > 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]
