6-4 SQL Execution Failure Log
This section describes the SQL Execution Failure Log used to trace the execution failures of the
DB Connection Service due to a DB-caused factor.
6-4-1 Overview
You can check the SQL statements and error information when transmission of an SQL
statement failed due to a problem* of the DB itself.
* For example,
ï‚– Because the column names of the table have been changed, they do not match the column names of an
SQL statement sent from the DB Connection Service.
ï‚– A value to insert is outside the valid range of the data type of the column.
You can record this log by setting SQL execution failure log to Record in the DB Connection
Service Setting of Sysmac Studio.
This log is saved as SQL Execution Failure Log files on the SD Memory Card mounted in the
CPU Unit. When no SD Memory Card is mounted in the CPU Unit, you cannot record the SQL
Execution Failure Log.
You can check the contents of this log in the SQL Execution Failure Log Tab Page of the
Operation Log Window in Sysmac Studio.
6-4-2 Application Procedure
Use the SQL Execution Failure Log according to the following procedure.
Step Reference
1. Set the SQL Execution Failure Log. Refer to 6-4-3 Setting the SQL Execution Failure Log.
↓
2. Check the SQL Execution Failure Log. Refer to 6-6 Checking the Operation Logs.
6-4-3 Setting the SQL Execution Failure Log
Double-click DB Connection Service Settings under Configurations and Setup - Host
Connection Settings - DB Connection in the Multiview Explorer. Then, set the following in the
Service Setting.