IBM Support

DerbyDB is at read-only mode in Symphony grid

Troubleshooting


Problem

We are using DerbyDB as the Symphony database. When DerbyDB is at normal state, it's mode is under read/write mode and plc and purger services are able to insert new data and purge old data. However, DerbyDB can fall into read-only mode sometimes and this will cause plc and purger to not function at all. What would be the recovery steps?

Symptom

In PLC dataloader logs, it was found DerbyDB has become read-only mode. For example,

java.sql.SQLException: Error for batch element #0: An SQL data change is not permitted for a read-only connection, user or database.

And, suddenly write records does not work anymore. For example,

2018-07-26 15:10:30.129 INFO com.platform.perf.dataloader.DefaultDataLoader.execute(DefaultDataLoader.java:533) Read 1 records.

2018-07-26 15:10:30.130 INFO com.platform.perf.dataloader.DefaultDataLoader.execute(DefaultDataLoader.java:547) Written 0 records.

 

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGSMK","label":"Platform Symphony"},"Component":"database, PERF","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All version","Edition":"Advanced","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
27 August 2018

UID

ibm10720315

Page Feedback