Mitsubishi Electric Melsec Q Series User Manual page 394

10
TROUBLESHOOTING
Symptom
Data such as DB buffering status, No. of
DB bufferings, DB buffer full, or DB buffer
utilization will not be stored in the tag
component which is selected in [DB
buffering settings] of [System setting].
Section 7.6.4 Setting items in DB
buffering setting
Failed to communicate with the server
computer several times after module
startup.
Though the job is cancelled, rollback is
not executed.
Failed to the stored procedure execution.
Return value, output argument, and input/
output argument of the stored procedure
cannot be acquired.
The data of the specific term is not stored
in the database.
The communication between the
database is slow.
DB buffering is not performed.
10
- 53 10.3 Troubleshooting by symptom
10.3.3 When operating the MES interface module
Table 10.21 Troubleshooting about the DB interface function
Checked item
Was the setting that enables data writing
to the tag component made in [Job
settings]?
Was the device value of the relevant tag
component manipulated in the
programmable controller CPU?
Was the programmable controller
powered ON immediately after OFF?
Is there any problem on the server
computer?
Was the stored procedure created in
Oracle 10g/11g/12c committed?
Has the stored procedure execution error
occurred?
Is the stored procedure which returns a
result set executed by SQL Server 2008/
2012/2014/2016/2017?
Does the buffered data exist in the
Manually resend buffer?
When [Immediate sending] is selected in
[Operation of recovery from network
disconnection] of [System settings] - [DB
buffering settings], the data whose trigger
condition is met is send regardless of
whether the data exist.
Is the proper driver for ODBC data source
selected when using Microsoft SQL
Server?
Has trigger buffer full occurred?
(From the previous page)
Corrective action
• Select another tag component, or check the
[Job settings] and disable data writing to the
relevant tag component.
• Specify another device. Or do not manipulate
the relevant device value in the
programmable controller CPU.
• Turn OFF the programmable controller, and
after several minutes, turn it ON.
• Restart the server computer.
• Do not commit in the stored procedure
created in Oracle 10g/11g/12c.
• Check that the settings of the stored
procedure name, return values, and
arguments are correct.
• Check that reserved terms of the database
are not used for the stored procedure name.
• Modify the stored procedure not to return the
result set. (Return value, output argument,
and input/output argument of a stored
procedure which returns a result set cannot
be acquired.)
• While the DB buffering is being performed,
resend the buffered data.
• Select any of the following in "Create New
Data Source".
®
SQL Server 2000:
"SQL Server"
®
SQL Server 2005,
®
SQL Server 2008:
"SQL Server Native Client"
®
SQL Server 2008 R2,
®
SQL Server 2012,
®
SQL Server 2014,
®
SQL Server 2016,
®
SQL Server 2017:
"SQL Server Native Client 11.0"
• Correct the setting so the trigger interval is
longer than the processing time of action.
Section 6.1.5 Trigger buffering function