Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3533 Replication fails when unlogged operations are used
  3. DERBY-3551

Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.4.1.3, 10.5.1.1
    • Fix Version/s: 10.4.1.3, 10.5.1.1
    • Component/s: Replication
    • Labels:
      None

      Description

      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

        Attachments

        1. runscript_import.sql
          0.9 kB
          V.Narayanan
        2. Derby3551_3.stat
          0.5 kB
          V.Narayanan
        3. Derby3551_3.diff
          7 kB
          V.Narayanan
        4. Derby3551_2.stat
          0.5 kB
          V.Narayanan
        5. Derby3551_2.diff
          7 kB
          V.Narayanan
        6. Derby3551_1.stat
          0.3 kB
          V.Narayanan
        7. Derby3551_1.diff
          3 kB
          V.Narayanan

          Activity

            People

            • Assignee:
              narayanan V.Narayanan
              Reporter:
              narayanan V.Narayanan
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: