[
https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581983#action_12581983
]
Kim Haase commented on DERBY-3551:
----------------------------------
Just checking -- based on all the comments on this issue, it seems that what we
ended up with was NOT a new system procedure after all, but the implementation
of a check when the startMaster command is run --
"Check if any unlogged operations are currently running, if yes unfreeze and
throw an exception
saying that replication cannot be started since the database has unlogged
operations running"
Is that correct? If so, I'm guessing the information should be added to the
description of the startMaster command as part of DERBY-3169.
> Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()
> ----------------------------------------------------------
>
> Key: DERBY-3551
> URL: https://issues.apache.org/jira/browse/DERBY-3551
> Project: Derby
> Issue Type: Sub-task
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Fix For: 10.5.0.0
>
> Attachments: Derby3551_1.diff, Derby3551_1.stat, Derby3551_2.diff,
> Derby3551_2.stat, Derby3551_3.diff, Derby3551_3.stat, runscript_import.sql
>
>
> Jorgen says-
> I suggest that the replication step in which the master database is frozen is
> replaced by a new system procedure to solve index and import:
> Old: SYSCS_UTIL.SYSCS_FREEZE_DATABASE()
> New: SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()
> The new system procedure should:
> 1) Freeze the database
> 2) Check if there are any ongoing transactions with unlogged operations. If
> so - unfreeze and abort. Otherwise:
> 3) Enable logging of unlogged operations
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
