|Product:||Syniti Data Replication, DBMoto|
|Summary:||Under certain conditions, the temporary JRPL files used by Syniti DR/DBMoto on the IBM i can end up in a locked state. Syniti DR/DBMoto is unable to delete the locked files, so you must delete them explicitly on the IBM i system.|
JRPL files are temporary files used by Syniti DR/DBMoto when running on IBM i systems. Every time Syniti DR/DBMoto runs a mirroring replication, the JRPL files are deleted and recreated.
If there is a lock on the files, then Syniti DR/DBMoto cannot delete them, and you need to delete them by hand.
In situations such as the following:
- IBM i system is busy and you get a timeout error
- IBM i system is subjected to an abrupt shutdown
you might see an error message like the following in the Syniti DR/DBMoto log, denoting that a JRPL file is locked.
System.Data.Sql400.Sql400Exception: ODBS Execute Error: Error occurred while opening file JRPL0353. [SQLCODE: -443 SQLSTATE: 38501]
at iu.a(p5 A_0, Boolean A_1)
at iu.a(Boolean& A_0)
at iu.a(p5 A_0, Boolean& A_1)
or “JRPLXXXX in library DBMOTOLIB in use.”
The JRPL files should be deleted from the IBM i system using the IBM i console. First, stop the Syniti DR Replication Agent/DBMoto Data Replicator, and make sure that you are using only one instance of Syniti DR/DBMoto. You will not lose any transaction information by deleting the JRPL files used by Syniti DR/DBMoto because the Replication Agent/Data Replicator always starts from the last processed transaction, and the files are deleted and recreated for each mirroring event.
If the files are locked because of a timeout error, you should also use the Management Center to edit the connection properties of the IBM i connection to increase the init timeout value for the connection and ensure that the command timeout is set to -1.