[ https://issues.apache.org/jira/browse/DERBY-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083346#comment-13083346 ]
Rick Hillegas commented on DERBY-5381: -------------------------------------- Possible solutions include: 1) Build replication of the sqlj operations. This might involve streaming jar file contents into the log for master databases. 2) Disallow the sqlj operations on master databases. > Replication should replicate jar file operations from the master to the slave. > ------------------------------------------------------------------------------ > > Key: DERBY-5381 > URL: https://issues.apache.org/jira/browse/DERBY-5381 > Project: Derby > Issue Type: Improvement > Components: Replication > Affects Versions: 10.9.0.0 > Reporter: Rick Hillegas > > Derby does not replicate calls to the sqlj jar procedures (install_jar, > replace_jar, remove_jar). This limitation is described in the Server Guide in > the section titled "Starting and running replication". If jar files are added > or updated on the master database, then user-defined functions, procedures, > and UDTs may break after failover to the slave. This can be a serious problem > for applications which exploit both replication and user-defined schema > objects. For such applications, automatic failover is difficult if not > impossible. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira