Removing an application group that uses single-threading - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

Before you begin, replication processes must be ended for all data groups associated with the application group and all procedures associated with the application group must have a status indicating completed, completed with errors, or acknowledged.

When deleting an application group in which all resource groups are configured for single-threaded database apply processing, default values will delete the application group and its procedures and resource groups, but will keep its data groups and related configuration. You can choose to also delete the related configuration, which consists of associated data groups, data group entries, data group policies, and audit results.

Implications of keeping related data groups: The shipped default value for the Include related (RELATED) parameter on the command used in these instructions allows the related data groups and their configured data group entries, policies, and audit results to remain in the instance. This is so that you can more easily continue replicating the affected data either by moving the data groups to a different application group or by managing the data groups without an application group. Either choice requires additional actions after deleting an application group. The additional actions are identified in the instructions below.

To delete an application group when all of its resource groups use single-threading, do the following:

  1. From the MIMIX Basic Main Menu, type 1 (Work with application groups) and press Enter.

  2. The Work with Application Groups display appears. Do one of the following:

    • To keep the related configuration, type 4 (Delete) next to the application group you want and Press Enter. When a confirmation display appears, press Enter.

    • To delete the related configuration, type 4 (Delete) next to the application group you want and press F4 (Prompt). On the Delete Application Group Def. (DLTAGDFN) display, specify *YES for the Include related prompt and press Enter.

    Important!If you kept the related data groups, perform the remaining steps below.

  3. You can manage the kept data groups in one of the following ways:

    • By moving the data groups into a different application group. The application group must have the same two nodes in its recovery domain and node roles that match the data group’s nodes and replication direction. This is the preferred action and is best practice. From the native user interface, you can use Deleting an application group.
      Note: An easier way to do this is to use the Move to Application Group action for the data group from the Data Groups Not in an Application Group tab of the Replication Configuration window in the Assure UI portal.
    • By managing the data groups without an application group. If you choose this, complete Step 4.

  4. Ensure that the data groups to be used without an application group can be switched. The MIMIX model switch framework is preferred over switching individual data groups. Do the following:

    1. To use model switch framework, identify the default model switch framework within policies and ensure that you have the framework configured. If necessary, contact your Certified MIMIX Consultant for assistance with configuring the MIMIX Model Switch Framework.

    2. Update your runbook or user-created instructions to indicate that you must use the Start Data Group (STRDG) and End Data Group (ENDDG) commands to control replication and to indicate how switching will be performed (model switch framework or the Switch Data Group (SWTDG) command).

  5. Consider disabling the data groups if you do not need to start replication for them right away either because you need to validate an appropriate application group or need to configure model switch framework. This will prevent the data groups from starting with the next Start MIMIX request.