> We enabled the precompiler trace ( long trace ) for our > application and found that, "SQLCODE: -602 System > error: AK Datapart too short" error in precompiler trace file > for FETCH statements. For some Fetch statement, mfIndex init > is negative ( mfIndex init : -32757 ) and in such cases, > our application dumps core and we have "ERR -11607 COMMUNIC > sql03_receive: illegal reference: 0" error logged in appldiag file. > > For the above mentioned communication and system error, > SAPDB error messages pdf file says that the database is in > inconsistent state and we have to shutdown the database and > contact the SAP LABS. This is happening in our client place. > So please help us to solve the problem.
The problems happen only on the client side and don't affect the server, so there is no need to shutdown the database. The paragraph about 'inconsisten state' only applies to messages between -10000 and -9000. > 3. In which case will we get "System error: AK Datapart > too short" and "COMMUNIC sql03_receive: illegal reference: 0" error ? 'AK Datapart to short' is generally an error in the client runtime where incorrect network packets are sent to the server. 'illegal reference: 0' could happen if a connection has been closed (possibly because of the unexpected error -602) and another call is made to the communication layer. You might want to check the error codes after every precompiler statement. It is probably an error in the precompiler runtime, but you might be able to prevent the crash. Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
