Since errors cause a rollback in the consolidated database by default, it is difficult to create a log of errors and their resolutions within the consolidated database due to the rollback. The report_error and report_odbc_error events let you create a proper record of user-defined script errors because they are invoked on a different database connection than the synchronization. These error-reporting scripts are invoked immediately after the error-handling scripts are invoked, and are immediately followed by a commit.

The error-reporting scripts get invoked for all SQL errors that occur in user defined scripts. When errors occur in user-defined scripts, the MobiLink server rolls back the transaction in the consolidated database, logs the error, and aborts the synchronization.

If your consolidated DBMS supports an out-of-band (outside of the current database connection) mechanism for reporting activity from SQL, consider using that mechanism instead of the error-reporting scripts defined by MobiLink.

See:

• handle_error connection event
• handle_odbc_error connection event
• report_error connection event
• report_odbc_error connection event

 Example

INSERT INTO errors
VALUES( 
  CURRENT DATE,
  {ml s.action_code},
  {ml s.error_code},
  {ml s.error_message},
  {ml s.username},
  {ml s.table} );