Rocket Software UniVerse 11.3.1 U2 Data Replication User Guide

Adding a publishing group

Configuration phrases, on page 34 .

Adding a publishing group

After you have defined the replication systems, add a publishing group.

1. In XAdmin, from the U2 Resource pane, select the publisher server. From the Admin Tasks pane, expand

Replication then double-click Configuration.

The Replication pane appears.

2. Click the

Replication Group tab.

3. To add a publishing group, from the Publishing Groups area, click Add.

4. In the dialog box that appears, enter the ID of the publishing group in the

Group ID field.

5. Specify the publishing account by selecting the account where the files you want to publish reside from the Account list.

6. To define replication level, select the level of replication you want from the

Level list. You can select either

ACCOUNT or FILE replication.

If you select ACCOUNT, replication will occur at the account level for the account you selected.

This means every file in that account will be replicated.

If you select

FILE, only the files selected in the Files area will be replicated for the account you selected.

7. To add files to the publishing group, in the Files area, click Add.

A dialog box appears with all the files for your account listed. If you selected

ACCOUNT in step

5, you can still select specific files for reasons such as making them sub-writable. If you selected

FILE in step 5, select the specific files that you want to publish.

When you are done adding files, click Finish.

8. By default, both the Data and the Dict cells of the file are selected. If you do not want to publish the data portion of the file, clear the

Data check box (cell). If you do not want to publish the dictionary portion of the file, clear the

Dict check box (cell).

9. If you want to make any of the files that you selected sub-writeable, select the cell for that file.

A check mark appears in the SUB_WRITABLE column. Making a file sub-writable allows you to edit or change them on the subscriber without error.

10. If you are using account-level replication, select files to exclude from U2 Data Replication. To specify any files that are excluded, in the Excluded Files area, click Add.

Select the specific files that you want to exclude, and click

Finish.

Chapter 3: Administering U2 Data Replication

11. Set any of the configuration parameters necessary for your environment in the

Configuration

area.

For detailed information about these configuration parameters, see

12. Click

Finish.

Adding a subscribing group

Previous topic:

Defining replication systems

Adding a publishing group, on page

Adding a subscribing group

After you have added a publishing group, add a subscribing group.

1. In XAdmin, from the U2 Resource pane, select the subscriber server. From the Admin Tasks pane, expand

Replication then double-click Configuration.

The Replication pane appears.

2. Click the

Replication Group tab.

3. Decide whether you to manually add a subscribing group or you want to import the configuration from the one you set in the publishing server, as described in

45 . To add one manually, continue to the next step. To import the configuration, click

Import.

a. In the dialog box that appears, select the server where you set up the publishing group.

b. Select the version number.

Select whether you want to merge or replace the subscribing configuration file with the remote one.

d. Click Finish.

The configuration is imported, and the values are automatically populated in the dialog box that appears.

e. Verify that your configuration is correct, and click Finish.

You have successfully added a subscribing group, and can move on to

Verifying the account defaults, on page 47 .

4. To add a subscribing group, from the Subscribing Groups area, click Add.

5. In the dialog box that appears, select the publishing system from which this subscribing system is receiving data from the

From System list.

6. Select the group ID from the publishing system in the Group ID list.

When you select the group ID, XAdmin populates the file list and configuration parameters from the same group ID on the publishing system.

7. Select the account to which you want to replicate data in the Into Account field. XAdmin automatically populates the Account Path field.

8. Click the file you want to receive. You can select multiple files by clicking the file while holding down the CTRL key.

9. By default, both the Data and the Dict cells of the file are selected. If you do not want to receive the data portion of the file, clear the Data check box (cell). If you do not want to receive the dictionary portion of the file, clear the Dict check box (cell).

10. If you want to be able to update the file on the subscribing system, select the SUB_WRITEABLE check box (cell).

11. If you are using account-level replication, select files to exclude from U2 Data Replication. To specify any files that are excluded, in the Excluded Files area, click Add.

Select the specific files that you want to exclude, and click

Finish.

12. In the Distributions area, click the value in the Type field, then select the ellipsis button (...) that appears.

Optional: Changing a replication group definition

13. In the dialog box that appears, select the type of replication mode you want and the account for the subscriber.

When choosing Realtime or Immediate subscribing, the subscribing system can optionally be defined as a standby system. This can be done by selecting the

Hot Standby check box. A standby system can also be optionally configured for delayed standby replication.

When selecting the

Hot Standby check box, a Delayed Time Period field appears. Enter the amount of time you want to delay the updates on the subscriber in minutes. When using delayed standby replication, the updates are immediately sent to the subscriber but are not applied until the delayed time period has elapsed.

Click

Finish.

14. Set any of the configuration parameters necessary for your environment in the

Configuration

area.

For detailed information about these configuration parameters, see

Configuration phrases, on page 34 .

15. Click Finish.

Optional: Changing a replication group definition

Previous topic:

Adding a publishing group

Adding a subscribing group, on page 46 and

Optional: Changing a replication group definition

You can change a replication group definition without having to stop and restart UniVerse.

1. In XAdmin, from the U2 Resource pane, select the subscriber server. From the Admin Tasks pane, expand Replication then double-click Configuration.

2. From the

Replication Group tab, select the group that you want to update, then click Detail.

3. Make the appropriate changes, as described in

Adding a publishing group, on page 45 , then click

Finish.

After making your changes, you may need to resubscribe the group to update the subscriber system’s configuration.

Verifying the account defaults

Previous topic:

Adding a subscribing group

Verifying the account defaults

You can view the account defaults to see which files are automatically included (replicated) and excluded.

1. In XAdmin, from the U2 Resource pane, select a server. From the Admin Tasks pane, expand

Replication then double-click Configuration.

The Replication pane appears.

2. Click the

Account Default tab.

The Files area displays all of the default files that are included in the replication process. The

Excluded Files area displays all of the automatically excluded files.

Optional: If you want to include or exclude a file, click Add next to Files or Excluded Files.

In the dialog box that appears, enter the file name, and select any applicable specifications –

Data, Dict, and/or SUB_WRITEABLE.

When you are done, click

Finish.

Optional: Changing a replication group definition

Starting replication

Chapter 3: Administering U2 Data Replication

Previous topic:

For detailed information about this command, see reconfig command, on page 76 .

Starting replication

After you have defined the replication systems and added both a publishing and subscribing group, you can start replication.

1. In XAdmin, from the U2 Resource pane, select the publishing or subscribing server. From the

Admin Tasks pane, expand

Replication then double-click Configuration.

The Replication pane appears.

2. Click the

Replication Tool tab.

3. From the Functions section, select the type of administrator option that you want to execute.

▪ Report – Reports the current status of a replication. This command is useful after a failure or failover occurs. For detailed information about this command, see

report command, on page

▪ Sync – Synchronizes subscribing systems to their publishing systems. The publishing system establishes a connection to the subscribing system and invokes the subscribing process.

UniVerse or UniData reads and transfers replication logs from the publishing system to the subscribing system. The subscribing system then applies the updates to the database. For detailed information about this commands, see

sync command, on page 74

▪ Reconfig – Reconfigures the replication configuration while UniData or UniVerse is running.

▪ Suspend – Suspends a live replication. In a suspended mode, UniVerse or UniData interrupts the connection between the publisher and the subscriber. The publishing system saves the replication log files to the replication logs reserve file rather than transferring them to the subscribing systems. The subscribing system and all replication writer processes stop after they finish updating existing logs in the replication buffer. For detailed information about this

command, see suspend command, on page 73

▪ Failover – Changes the replication direction on a local system, either from the local system to the publishing system or subscribing system, or changes the subscribing source distribution.

For detailed information about this command, see failover command, on page 75 .

▪ Reset – The reset command clears saved replication logs in the replication log reserve file. Use the reset command after you copy or store database files, since the remaining replication logs

are no longer useful. For detailed information about this command, see reset command, on page 77

▪ Enable – Enables replication.

▪ Disable – Disables replication. For more information, see

Disabling replication, on page 11

4. The choices in the

Options section become available based on which function you select. Select the appropriate options for this replication.

5. Select whether you want a target definition of All or Selected.

A target is a replication, a replication group, or a distribution of a replication group. A replication is all data replicated from a remote system to the local system, or from a local system to a remote system. A target definition of ALL represents all replications on the system. One command can have multiple targets.

If you want to execute the command against all targets, leave All selected in the Targets area.

If you want to select the replication to execute the command against, select the

Selected option in the

Targets area of the replication tool dialog box, then click Add. In the dialog box that appears, enter the target information, then click

Finish.

6. Start the replication process by selecting Execute.

Diagnosis utility

Any output from the command appears in the

Status box.

Previous topic:

Verifying the account defaults

Listing replication files, on page 66 .

Diagnosis utility

The diagnosis utility is used by U2 support for diagnosing problems encountered with U2 Data

Replication. With the utility, you can view information such as the current configuration, groups, semaphores, and other general information that can help you troubleshoot any issues you have with replication.

To access the diagnosis utility, in XAdmin, select the server you want to diagnose. From the

Admin

Tasks pane, expand Replication, then double-click Configuration. Click the Diagnosis Utility tab.

You can use the command line to display the same information as the diagnosis utility. For more information, see

Administering U2 Data Replication through the command line

You can define publishing and subscribing groups and change their definitions directly from the command line

To administer U2 Data Replication from the command line, perform the following tasks:

•

Defining subscribing groups from the command line

Define a subscribing replication group from the command line.

•

Defining publishing groups from the command line

Define a publishing replication group from the command line.

•

Changing a replication group definition from the command line

Reconfigure U2 Data Replication from the command line.

Defining subscribing groups from the command line

Define a subscribing replication group from the command line.

1. Log on to the subscribing system.

2. Edit the repsys file, located in the uvhome directory. Define all replication systems in the replication environment to which U2 Data Replication may connect.

3. Edit the repconfig file located in the the uvhome directory.

Define all the replication groups you want to replicate from the publisher. Make sure you use the same group name used on the publisher.

▪ Copy the file list of the group from the publisher.

▪ Define the publishing system according to the definition on the publisher.

▪ Define the subscribing system, and define the replication type.

▪ If you are going to use this system as a standby subscriber, define all other distributions of the group and their replication types, according to the definition on the publisher.

Chapter 3: Administering U2 Data Replication

▪ Set the replication group configurable parameters.

▪ Define the subscribing account path in replication.

4. Create the subscribing account, then copy all files from the publishing system to the subscribing system.

5. Restart UniVerse, or execute the uv_repadmin reconfig command to load the replication group definition and allocate system resources.

Administering U2 Data Replication through the command line

Defining publishing groups from the command line

Define a publishing replication group from the command line.

1. Log on to the publishing system.

2. Edit the repsys file, located in the uvhome directory. Define all replication systems in the replication environment to which U2 Data Replication may connect.

3. Edit the repconfig file, located in the uvhome directory.

For each replication group, define the following information:

▪ Assign a unique replication group name.

▪ Define the replication level.

▪ Define the location of the publishing account.

▪ Define excluded files for account-level replication.

▪ Define all files belonging to the file-level replication group.

▪ Define the distribution for the group, including the publishing system and all subscribing systems to which it replicates.

▪ Define the replication type for each of the distribution systems.

▪ Set the replication group configurable parameters.

4. Restart UniVerse, or execute the uv_repadmin reconfig command.

Administering U2 Data Replication through the command line

Changing a replication group definition from the command line

Reconfigure U2 Data Replication from the command line.

1. Log on to the replication system you want to reconfigure.

2. Make your changes in the repsys and repconfig files.

3. Synchronize the reconfigured group from its publisher or to its subscriber.

4. Execute the

RECONFIG command to request that the replication manager reconfigure the replication group.

The replication manager executes the uv -admin -L command to block writes to the database.

The replication manager requests that all replication groups suspend replication.

The replication manager reads the new repconfig and repsys files, and compares them to the original file.

The replication manager checks the consistency of the definition, and checks each of the groups that are changing to see if there are any replication logs not synchronized to its subscribers.

Monitoring U2 Data Replication

The replication manager reallocates shared memory segments, reloads the replication configurations, and the Inode and device number of each replication object.

The replication manager executes the uv -admin -U command to resume processing.

If you selected the AUTORESUME option, the replication manager synchronizes and resumes all realtime and immediate replication groups to its publishers and subscribers. If you did not select the

AUTORESUME option, you should synchronize manually.

Administering U2 Data Replication through the command line

Monitoring U2 Data Replication

There are two main ways of monitoring the status of U2 Data Replication:

▪ Using XAdmin, as described

Monitoring replication through XAdmin, on page 51 .

▪ Using the REPLOGGER, as described in

Monitoring replication with REPLOGGER, on page 58

Monitoring replication through XAdmin

The replication monitoring tool monitors connection status, data transferring, and whether the publisher and subscriber systems are synchronized.

1. To access the replication monitor, in XAdmin, select the publishing server. From the Admin Tasks pane, expand

Replication, then double-click Performance and double-click Status.

Two tabs appear: the Replication Performance Monitor tab and the Replication Status

Monitor tab. These tabs work together to monitor replication.

You can monitor two types of replication:

▪ Publishing replication – the data replication from the local system to a remote subscribing system, including all replication groups involved. A publishing system can have more than one publishing replication defined.

▪ Subscribing replication – the data replication from a remote publishing system to the local system, including all replication groups involved. A subscribing system can have more than one subscribing replication defined.

Optional: You can perform the previous step again but for the subscribing server. This step is not required, but can be useful because you can see how the publisher and the subscriber communicate with each other.

3. Click the

Replication Performance Monitor tab.

a. Select the name of the replication you want to monitor from the Replications list.

Each replication is assigned a unique name on one system, consisting of the replication type and the remote system name. A replication type can be one of the following:

▪ Immediate

▪ Standby immediate

▪ Realtime

▪ Standby realtime

▪ Deferred

Note: If a replication has failed over, it still belongs to the same replication as it did before the failover, but the name changes.

Chapter 3: Administering U2 Data Replication b. Select the number of seconds to refresh the monitor in the

Interval in seconds field. The default interval is 3 seconds.

Next to the Server Control field, click

Start Test Period.

d. Next to the Interval in seconds field, click Start.

The replication group status table displays the current status of each replication group belonging to the replication you specify. The following example shows the replication group status table.

e. Select a row, then below the table, select either

Buffer Usage, Data Volume, or Latency

Split to view the extended results displayed below the table.

The following example shows the replication group status table with Buffer Usage selected.

The following example shows the replication group status table with

Data Volume selected.

The following example shows the replication group status table with Latency Split selected.

Monitoring replication through XAdmin f.

By default, the table displayed with General selected. You can also view the table by test period by selecting TP Split from above the table.

The following example shows the results displayed using the TP Split option.

4. Click the Replication Status Monitor tab.

a. Select the name of the replication you want to monitor from the

Replications list.

b. Select the number of seconds to refresh the monitor in the Interval in seconds field. The default interval is 3 seconds.

Next to the Interval in seconds field, click Start.

Two traffic lights appear along with details about the replication, as displayed in the following example.

For more information about what this table displays, see

The Replication Status Monitor tab, on page 54

Chapter 3: Administering U2 Data Replication

Optional: If you opened the Replication Performance Monitor tab and the Replication Status

Monitor tab for both the publisher and the subscriber, repeat the previous two steps to start both tests.

The Replication Status Monitor tab

The following table describe the functionality from the

Replication Status Monitor tab.

Field/Area

Replication Status

Sync Status

Replication Details

Description

The replication status indicates whether the publisher and subscriber are connected. The status can be one of the following:

▪ Green – The publisher and subscriber are connected for all groups involved in the replication.

▪ Yellow – At least one of the replication groups has been suspended by an administrator.

▪ Red – At least one of the replication groups has been terminated abnormally.

The sync status indicates whether the subscribing database is synchronized with the publishing database. The status can be one of the following:

▪ Green – The publishing and subscribing databases are synchronized.

▪ Yellow – There are pending updates that have not been applied to the subscribing database.

Provides specific details about replication as described below.

The Replication Status Monitor tab

Field/Area Description

Packet

Received

The number of packets received from the other party of the replication.

Types of packets include data packets, confirmation packets, heartbeat packets, and other control packets. Monitoring this information indicates whether the physical connection between the publishing database and the subscribing database is satisfactory. This number is cumulative from the last time UniVerse was started or U2 Data Replication was reconfigured.

Packet Sent The number of packets that have been sent to the other party of the replication. Types of packets include data packets, confirmation packets, heartbeat packets and other control packets. Monitoring this information indicates whether the physical connection between the publishing database and the subscribing database is satisfactory. This number is cumulative from the last time UniVerse was started or U2 Data Replication was reconfigured.

Subscriber

Received

The number of data records that have been received by the subscriber. This number is cumulative from the last time UniVerse was started or U2 Data

Replication was reconfigured.

Subscriber

Committed

Note: When monitoring a publishing replication this number may be out of date if the replication status is not green.

The number of data records that have been committed on the subscribing database. This number is cumulative from the last time UniVerse was started or U2 Data Replication was reconfigured.

Publisher

Committed

TP Total

CGTPs

Resolved

Disablement

Disk Pct

Max Replog

Size

Current

Replog Size

Replication group status table

Note: When monitoring a publishing replication this number may be out of date if the replication status is not green.

The number of data records that have been committed on the publishing database. This number is cumulative from the last time UniVerse was started or U2 Data Replication was reconfigured.

The sum of all transactions committed in the replication groups on the local system. This number is cumulative from the last time UniVerse was started or U2 Data Replication was reconfigured.

The sum of all transactions committed across more than one replication group on the local system. This number is cumulative from the last time

UniVerse was started or U2 Data Replication was reconfigured.

The replication log disk percentage defined by the uvconfig file parameter REP_DISABLE_DISK_PCT.

The limit the replication log file size can reach before U2 Data Replication is disabled.

The total replication log file size for all replication groups.

The replication group status table displays the current status of each replication group belonging to the replication you specify. See the following table for a description of each column of this table.

The following table describes the columns in the replication group status table.

Column

Group name

Description

The name of the replication group.

Chapter 3: Administering U2 Data Replication

Column

Connection

Status

In-Sync

Description

The connection status between the publishing system and the subscribing system in the group. The status can be one of the following:

▪ Green – The publisher and subscriber are connected in this group.

▪ Yellow – The replication group has been suspended by an administrator.

▪ Red – The replication group has terminated abnormally.

Indicates whether the subscribing files are synchronized with the publishing files in the group. The in-sync status can be one of the following:

▪ Green – The publishing and subscribing databases are synchronized.

▪ Yellow – There are pending updates in this replication group that have not been applied to the subscribing database.

Rep. Status The current replication group status.

▪ REP_RUNNING – The replication is running.

▪ REP_SYNCING – The replication is performing synchronization.

▪ REP_SUSPENDED – The replication is suspended.

▪ REP_DO_SUSPEND – The replication is in the process of suspending.

▪ REP_EXIT – The replication is suspended due to an abnormal termination.

The status can be one of the following on the subscribing system:

▪ SUB_STOP – The replication is stopped.

▪ SUB_EXIT – The subscribing system has exited abnormally.

▪ SUB_SHUTDOWN – The replication on the subscribing system has been shut down.

▪ SUB_RUNNING – The replication on the subscribing system is running.

▪ SUB_DO_RECONFIG – A reconfiguration process is occurring on the subscribing system.

▪ SUB_DO_SUSPEND – The replication is suspended on the subscribing system.

▪ SUB_SYNCING – The replication is performing synchronization on the subscribing system.

▪ SUB_RESYNCING – The replication is performing resynchronization on the subscribing system.

#Recv’d

▪ SUB_DO_FAILOVER – The subscribing system is performing a failover.

Changed By The event or reason that caused the replication status to change. If the status changed due to an exception, this column displays the error category and error code. A detailed error string is available in the tool tips. See the following table for a description of each of the events.

The number of packets received in the group. Monitoring this number indicates if the physical connection between the publishing system and subscribing system is satisfactory.

#Sent The number of packets sent in the group. Monitoring this number indicates if the physical connection between the publishing system and subscribing system is satisfactory. This number is cumulative from the last time UniVerse was started or U2

Data Replication was reconfigured.

The Replication Status Monitor tab

Column Description

Data

Replicated

SubGot

SubAvail

The total amount of data, in bytes, replicated in the group. On a publishing system this field represents the total amount of data sent out. On a subscribing system, this field represents the total amount of data received from the publishing system. This number is cumulative from the last time UniVerse was started or U2 Data Replication was reconfigured.

The log sequential number of the latest replication log received by the subscribing system. This number is cumulative from the last time UniVerse was started or U2 Data

Replication was reconfigured.

The log has been loaded into the replication buffer and is available for the replication writer processes.

SubDone The log sequential number of the latest replication log committed to the subscribing database. This number is cumulative from the last time UniVerse was started or U2

Data Replication was reconfigured.

PubDone The log sequential number of the latest replication log committed to the publishing database. This number is cumulative from the last time UniVerse was started or U2

Data Replication was reconfigured.

#TP The number of transactions resolved in this group, including cross-group transactions.

This number is cumulative from the last time UniVerse was started or U2 Data

Replication was reconfigured.

Data

Transfer

The total amount of transferred data that has been replicated.

Data Size The total size of data replicated.

Pacing

Level

Total

Degradation

Total Rep

Log Size

The replication pacing level in a group, as defined in the REP_PACING parameter in the repconfig file.

The total group pacing weight since the UniVerse system has started or U2 Data

Replication was reconfigured.

The current replication log file size including LEF and LRF.

The following table describes the valid events of reasons that appear in the Changed By column that can cause a change in the replication status.

Event/Reason

AUTO_SYNC

CGTP_SUSPEND

CM_REQUEST

DBA_ORDER

ENABLE

FAILOVER

PUB_REQUEST

PUB_STARTUP

RECONFIG

REMOTE_REQ

REP_DISABLED

SCHEDULED

Description

Replication is automatically resuming.

Cross-group transaction processing is suspended.

Checkpoint manager is requested (RFS only).

The system administrator issued a request resulting in a change of status.

Replication is enabled.

A failover has occurred.

A request was sent from the publishing system, or an event occurred on the publishing system resulting in a change of status.

The publishing system started.

Replication is reconfiguring.

A subscribing system can request to execute a

SYNC command on the publishing system.

Replication is disabled.

The repmanager process can only schedule a

SYNC command for deferred replication.

Chapter 3: Administering U2 Data Replication

Event/Reason

SUB_REQUEST

SYNCDONE

SYS_STARTUP

Description

A request was sent from the subscribing system, or an event occurred on the subscribing system resulting in a change of status.

A synchronization process succeeded.

The UniVerse system started.

Monitoring replication with REPLOGGER

REPLOGGER is a BASIC program that allows you to monitor replication. REPLOGGER collects information from the replication system using the replication administration uvreptool and writes the information to a sequential log file. The information logged by REPLOGGER describes how the replication system performs over a period of time. Using REPLOGGER helps you understand and analyze how your replication system responds to changing workloads. REPLOGGER can produce a large amount of data, so to aid in analyzing and visualizing the data, a Java tool called the U2

Replication Analyzer is available on github to graph the result sets.

To run the BASIC program, perform the following steps.

Note: You must be a super user to run REPLOGGER. REPLOGGER should be run on the subscriber.

1. At the ECL or TCL prompt, enter

REPLOGGER.

The REPLOGGER BASIC program starts and prompts you to enter the following information:

▪ the number of replication groups; if this is a single machine replication, this number should be doubled because it counts both publisher and subscriber

▪ whether to clear previous logs

▪ the capturing interval time, in seconds

▪ the maximum log file size, in megabytes

You can alternatively enter the answers to the prompts directly in the command line when starting REPLOGGER, as shown in the following example:

REPLOGGER 1 y 2 100

2. After you enter the prompts, press Enter.

The REPLOGGER BASIC program starts. The results are written to the rep_monitor.log file in the current account.

The following is an example of REPLOGGER executed in a Linux environment.

Current working directory is /disk1/u2test/test81_97837/testRFS.

:REPLOGGER

Replication Logging Tool. Ver 2.1

Program Starts: 12:02:03 04 Nov 2015

Please enter the number of replication groups:

Clear the previous logs:(y/n)

Old logs have been cleared.

Enter the capturing interval in seconds:

Enter the maximum log file size in Mega Bytes(MBs):

?100

Replication action trigger

Replication Logging Tool. Ver 2.1

Program Starts: 12:02:03 04 Nov 2015

Waiting for data...

Press Ctrl+C to exit.

[root@den-ci125 testRFS]# cat rep_monitor.log

GROUP.NO DATE.TIME PUB.DONE SUB.GOT SUB.AVAIL SUB.DONE LIEFSTART

LEFNO.START LEFNO.LAST LEFPOS.START LEFPOS.END USER.TIME(%) SYS.TIME(%) TCA.MODULO

TOTAL.PG TCA.FILE.ACCESS TCR.CREATE TCR.DROP

0 10:36:22 14 SEP 2015 44935 44935 44936 44523 0 1 1 0 0 2 21 2457 4096 0 0 0

0 10:36:25 14 SEP 2015 49306 49306 49307 46947 0 1 1 0 0 1 25 2457 4096 0 0 0

0 10:36:28 14 SEP 2015 52541 52541 52542 48404 0 1 1 0 0 1 24 2457 4096 0 0 0

0 10:36:32 14 SEP 2015 54991 54991 54992 49544 0 1 1 0 0 1 28 2457 4096 0 0 0

0 10:36:35 14 SEP 2015 57275 57275 57276 50600 0 1 1 0 0 2 29 2457 4096 0 0 0

0 10:36:38 14 SEP 2015 59157 59157 59158 51464 0 1 1 0 0 2 31 2457 4096 0 0 0

0 10:36:41 14 SEP 2015 60001 60001 60002 52303 0 1 1 0 0 1 33 2457 4096 0 0 0

0 10:36:44 14 SEP 2015 60001 60001 60002 53059 0 1 1 0 0 1 36 2457 4096 0 0 0

0 10:36:47 14 SEP 2015 60001 60001 60002 53854 0 1 1 0 0 1 46 2457 4096 0 0 0

0 10:36:50 14 SEP 2015 60001 60001 60002 54737 0 1 1 0 0 1 46 2457 4096 0 0 0

0 10:36:54 14 SEP 2015 60001 60001 60002 55531 0 1 1 0 0 2 46 2457 4096 0 0 0

0 10:36:57 14 SEP 2015 60001 60001 60002 56312 0 1 1 0 0 2 46 2457 4096 0 0 0

0 10:37:00 14 SEP 2015 60001 60001 60002 57029 0 1 1 0 0 1 46 2457 4096 0 0 0

0 10:37:03 14 SEP 2015 60001 60001 60002 57748 0 1 1 0 0 1 47 2457 4096 0 0 0

0 10:37:06 14 SEP 2015 60001 60001 60002 58414 0 1 1 0 0 1 46 2457 4096 0 0 0

0 10:37:09 14 SEP 2015 60001 60001 60002 59091 0 1 1 0 0 1 48 2457 4096 0 0 0

0 10:37:12 14 SEP 2015 60001 60001 60002 59705 0 1 1 0 0 1 18 2457 4096 0 0 0

0 10:37:15 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:19 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:22 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:25 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:28 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:31 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:34 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:37 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 1 2457 4096 0 0 0

0 10:37:40 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

0 10:37:43 14 SEP 2015 60001 60001 60002 60001 0 1 1 0 0 0 0 2457 4096 0 0 0

[root@den-ci125 testRFS]#

Replication action trigger

A replication action trigger allows you to define an action to take should replication abnormally terminate, making the replication status indicator red. The repmanager process initializes the action defined in the trigger whenever it receives a replication exception notice.

The replication action trigger is a shell script on UNIX platforms, or a batch program on Windows platforms. Define the full path to the trigger using the EXCEPTION_ACTION clause in the repsys file.

For example, if you define a replication action trigger as

UVRepExceptionAction.sh in the / usr/u2 directory, set the EXCEPTION_ACTION clause as:

EXCEPTION_ACTION=/usr/u2/UVRepExceptionAction.sh

U2 Data Replication passes parameters to the replication action trigger through environment variables. You can use the following environment variables in the replication action trigger program:

▪ UNIREP_REMOTESYS – the remote system name of the replication.

▪ UNIREP_REPTYPE – the type of replication.

▪ UNIREP_GRPNAME – the replication group name where the exception occurred.

Chapter 3: Administering U2 Data Replication

▪ UNIREP_ERRCODE – the exception error code.

▪ UNIREP_ERRSTRING – the exception error string.

If a replication contains multiple replication groups, U2 Data Replication treats the interruption of each group as a separate event, and executes the trigger for that group. If a single group belongs to multiple replications, each interruption of the replication triggers the replication action trigger to run.

UNIREP_REMOTESYS and UNIREP_REPTYPE define the replication where the exception occurred.

We recommend using the replication action trigger to automatically ping or email the system administrator to advise that an exception occurred. We do not recommend using it to automatically failover to a standby system.

Note that the replication action trigger only executes if an unexpected event that suspends U2 Data

Replication occurs. If a system administrator executes a command that suspends U2 Data Replication, the replication action trigger is not invoked.

When the replication action trigger is executed, the repmanager process writes a message similar to the following example in the rm.log:

Execute Replication Exception Action program <program_path>

Replication action trigger example

The following example illustrates a replication action trigger shell script in UniVerse. The example is similar to the replication action trigger for UniData.

#!/bin/sh

# Replication Status Code that returned by uv_repadmin report command

# Disclaimer of Warranties. Rocket Software disclaims to the fullest extent authorized

# by law any and all other warranties, whether express or implied, including, without

# limitation, any implied warranties

# of merchantability or fitness for a particular purpose. Without limitation of the

# foregoing, Rocket Software expressly does not warrant that:

# (a) the software will meet your requirements [or expectations];

# (b) the software or the software content] will be free of bugs, errors, viruses or

# other defects;

# (c) any results, output, or data provided through or generated by the software will

# be accurate, up-to-date, complete or reliable;

# (d) the software will be compatible with third party software;

# (e) any errors in the software will be corrected.

# 1.3.1 JDS 25/02/14 First Proposed Customer Release

# 1.3.2 JDS 20/05/15 Corrected check to be /.uvhome not .uvhome

# 1.3.5 JDS 03/06/15 Change to all_synced check for disablement

# 1.4.7 JDS 16/01/16 Spelling Change and Corrected Check for Sync Failure Subject

# in Email

# 1.4.8 JDS 27/01/16 Change to ignore publishing group errors on Recovery

# This is for sites with mixed publishing and subscribing groups

# On the same machine

# Publishing group Status Codes export PUB_STOP=1 #/* group is normally stopped */ export PUB_EXIT=2 #/* group has quit abnormally.*/ export PUB_SHUTDOWN=3 #/* group is doing shutdown */ export PUB_RUNNING=4 #/* group is in running mode */ export PUB_DO_RECONFIG=5 #/* group is doing reconfigure */ export PUB_DO_FAILOVER=7 #/* group is doing failover */

Replication action trigger example

# Publishing Replication Status Codes export REP_RUNNING=11 #/* replication is in running mode */ export REP_SUSPENDED=12 #/* replication is in suspension mode */ export REP_SYNCING=13 #/* replication is in syncing mode */ export REP_DO_SUSPEND=14 #/* replication is doing suspend */ export REP_DO_SYNC=15 #/* replication is doing sync */ export REP_EXIT=16 #/* replication exit */ export REP_DISABLED=17 #/* replication disabled */

# Subscribing Replication/group status codes.

export SUB_STOP=21 #/* group is normally stopped */ export SUB_EXIT=22 #/* group has quit abnormally.*/ export SUB_SHUTDOWN=23 #/* group is doing shutdown */ export SUB_RUNNING=24 #/* replication is in running mode */ export SUB_DO_RECONFIG=25 #/* group is doing reconfigure */ export SUB_DO_SUSPEND=27 #/* replication is suspending */ export SUB_SYNCING=28 #/* replication is doing sync */ export SUB_DO_FAILOVER=29 #/* group is doing failover */ export SUB_RESYNCING=30 #/* group is doing re-syncing */

# Script Version export REP_EXCEP_SCRIPT_VERSION=1.4.8

export debugrequest=0 export versionrequest=0 while getopts ":xv" opt; do case $opt in x ) debugrequest=1 ;; v ) versionrequest=1 ;; esac done if [ $debugrequest = 1 ] then

set -x fi if [ $versionrequest = 1 ] then

echo "Script Version is :"$REP_EXCEP_SCRIPT_VERSION

exit 0 fi

# Check UVHOME uvhome="$UVHOME" if [ "$uvhome" = "" ] then

export UVHOME=`cat /.uvhome` fi uvbin="$UVBIN" if [ "$uvbin" = "" ] then

export UVBIN=$UVHOME/bin fi

# Number of minutes to check before running script again export PUBCHECKMIN=2 export SUBCHECKMIN=2 export DISCHECKMIN=2

# Sleep is in seconds not minutes export RESYNCSLEEP=120

# export MAILRECS="[email protected],[email protected]"

# Show exception time export dstring=`date` export reportfilename=$UVHOME'/RepExcept.errlog' export scriptrunningname=$UVHOME'/RepExcept.running' if [ -f $scriptrunningname ] then

Chapter 3: Administering U2 Data Replication

echo $scriptrunningname" found script already running - exiting"

exit 5 fi echo "Run Started at :"$dstring > $scriptrunningname echo "UniVerse Replication Exception called at:"$dstring > $reportfilename echo "Script Version is:"$REP_EXCEP_SCRIPT_VERSION >> $reportfilename export machinename=`uname -a | awk '{print $2}'` echo "Run on machine "$machinename >> $reportfilename echo "Is this the publisher or subscriber" >> $reportfilename export cmd="$UVBIN/uv_repadmin report $UNIREP_REMOTESYS"

$cmd returncode=$?

echo "returncode=$returncode" >> $reportfilename export publisher=0 export subscriber=0 export disabled=0 if [ $returncode -lt 17 ] then

publisher=1 fi if [ $returncode -gt 17 ] then

subscriber=1 fi if [ $returncode = "17" ] then

disabled=1 fi if [ $publisher = 1 ] then

echo "System is a publisher" >> $reportfilename fi if [ $subscriber = 1 ] then

echo "System is a subscriber" >> $reportfilename fi if [ $disabled = 1 ] then

echo "Replication is Disabled !" >> $reportfilename fi

# Check Last Run Time and avoid running multiple times export checkfilename=$UVHOME'/RepExcept.runtime' export ddatetime=`date +"%Y %j %H %M"` ddatetime=`echo $ddatetime | sed 's/ //g'` export run_check=0 if [ ! -f $checkfilename ] then

# Put the current date time into the log file

echo $ddatetime > $checkfilename

run_check=1 else

ldatetime=`cat $checkfilename`

if [ $publisher = 1 ]

then

tdatetime=`expr $ldatetime + $PUBCHECKMIN`

if [ $subscriber = 1 ]

then

tdatetime=`expr $ldatetime + $SUBCHECKMIN`

if [ $disabled = 1 ]

then

Replication action trigger example

tdatetime=`expr $ldatetime + $DISCHECKMIN`

echo "Last run at "$ldatetime >> $reportfilename

echo "Current "$ddatetime >> $reportfilename

echo "Next "$tdatetime >> $reportfilenane

if [ $ddatetime -gt $tdatetime ]

then

run_check=1

echo $ddatetime > $checkfilename

fi fi echo "Run Check "$run_check >> $reportfilename if [ $run_check = 0 ] then

rm $scriptrunningname

exit fi

# Show environment variables passed from replication system echo "UNIREP_REMOTESYS="$UNIREP_REMOTESYS >> $reportfilename echo "UNIREP_REPTYPE="$UNIREP_REPTYPE >> $reportfilename echo "UNIREP_GRPNAME="$UNIREP_GRPNAME >> $reportfilename echo "UNIREP_ERRCODE="$UNIREP_ERRCODE >> $reportfilename echo "UNIREP_ERRSTRING="$UNIREP_ERRSTRING >> $reportfilename echo "UVBIN=$UVBIN" >> $reportfilename echo "Return Error Codes" >> $reportfilename echo "NO ERROR=0" >> $reportfilename echo "PUB_STOP="$PUB_STOP >> $reportfilename echo "PUB_EXIT="$PUB_EXIT >> $reportfilename echo "PUB_SHUTDOWN="$PUB_SHUTDOWN >> $reportfilename echo "PUB_RUNNING="$PUB_RUNNING >> $reportfilename echo "PUB_DO_RECONFIG="$PUB_DO_RECONFIG >> $reportfilename echo "PUB_DO_FAILOVER="$PUB_DO_FAILOVER >> $reportfilename echo "REP_RUNNING="$REP_RUNNING >> $reportfilename echo "REP_SUSPENDED="$REP_SUSPENDED >> $reportfilename echo "REP_SYNCING="$REP_SYNCING >> $reportfilename echo "REP_DO_SUSPEND="$REP_DO_SUSPEND >> $reportfilename echo "REP_DO_SYNC="$REP_DO_SYNC >> $reportfilename echo "REP_EXIT="$REP_EXIT >> $reportfilename echo "REP_DISABLED="$REP_DISABLED >> $reportfilename echo "SUB_STOP="$SUB_STOP >> $reportfilename echo "SUB_EXIT="$SUB_EXIT >> $reportfilename echo "SUB_SHUTDOWN="$SUB_SHUTDOWN >> $reportfilename echo "SUB_RUNNING="$SUB_RUNNING >> $reportfilename echo "SUB_DO_RECONFIG="$SUB_DO_RECONFIG >> $reportfilename echo "SUB_DO_SUSPEND="$SUB_DO_SUSPEND >> $reportfilename echo "SUB_SYNCING="$SUB_SYNCING >> $reportfilename echo "SUB_DO_FAILOVER="$SUB_DO_FAILOVER >> $reportfilename echo "SUB_RESYNCING="$SUB_RESYNCING >> $reportfilename

# Run uv_repadmin report command export cmd="$UVBIN/uv_repadmin report -detail $UNIREP_REMOTESYS" echo "Now running:"$cmd >> $reportfilename

$cmd >> $reportfilename echo "showuv" >> $reportfilename

$UVBIN/showuv >> $reportfilename echo "Please See "$reportfilename" for more information" >> $reportfilename

# SendMail of Failure echo "Attempting First SendMail" >> $reportfilename if [ $disabled = 1 ] then

echo "Subject: REPLICATION DISABLED" | cat - $reportfilename | /usr/lib/sendmail

-F $machinename -t $MAILRECS

echo "Replication Disabled Email Sent" >> $reportfilename

Chapter 3: Administering U2 Data Replication else

echo "Subject: REPLICATION SUSPENDED" | cat - $reportfilename | /usr/lib/sendmail

-F $machinename -t $MAILRECS

echo "Replication Suspended Email Sent" >> $reportfilename fi if [ $publisher = 1 ] then

echo "System Reported it was a publisher no need to try sync" >> $reportfilename

rm $scriptrunningname

exit 0 fi if [ $disabled = 1 ] then

echo "System Reported Replication was disabled no need to try sync" >>

$reportfilename

rm $scriptrunningname

exit 0 fi

# Check all groups are suspended before proceeding

# Not Needed for Publisher or if Replication is disabled export all_suspended=0 export try=0 while [ $all_suspended = 0 -a $try -lt 10 ] do

sleep 5

all_suspended=1

menu_str="2\n0\n0\n0\n\n\n"

for grpname in `printf $menu_str | $UVBIN/uvreptool | grep "^Group" |

awk '{print $3}'`; do

if [ $all_suspended ]

then

# Run uv_repadmin report command

export cmd="$UVBIN/uv_repadmin REPORT GROUP $grpname DISTRIB $UNIREP_REMOTESYS"

echo "Try Counter is "$try >> $reportfilename

echo "Now running:"$cmd >> $reportfilename

$cmd

returncode=$?

echo "returncode=$returncode" >> $reportfilename

if [ $returncode -gt 30 ]

then

# Report command failed

echo "Report command failed, exit." >> $reportfilename

exit 2

rm $scriptrunningname

elif [ $returncode = $REP_SUSPENDED -o $returncode = $SUB_STOP -o

$returncode = $SUB_EXIT ]

then

echo "Group $grpname is suspended." >> $ filename

else

all_suspended=0

done

try=`expr $try + 1` done if [ $all_suspended = 0 ] then

echo "Number of Try's Exceeded to Confirm All Groups Suspended" >> $reportfilename

echo "Subject: UNABLE TO CONFIRM SUSPENSION OF ALL GROUPS (NO SYNC

WILL BE ATTEMPTED)" | cat - $reportfilename | /usr/lib/sendmail

-F $machinename -t $MAILRECS

echo "Unable to confirm suspension email sent" >> $reportfilename

Replication action trigger example

rm $scriptrunningname

exit 3 fi echo "Subject: CONFIRMED SUSPENSION OF ALL GROUPS - Resync Attempt in 2 Minutes"

| cat - $reportfilename | /usr/lib/sendmail -F $machinename -t $MAILRECS echo "Confirmation suspension email sent" >> $reportfilename

# Try automatic resync and resume - only run on subscriber echo "Sleeping for $RESYNCSLEEP" >> $reportfilename sleep $RESYNCSLEEP echo "Woke up from Sleep" >> $reportfilename export all_synced=1 export group_syncing=1 menu_str="2\n0\n0\n0\n\n\n" for grp_name in `printf $menu_str | $UVBIN/uvreptool | grep "^Group"

| awk '{print $3}'`; do

cmd="$UVBIN/uv_repadmin sync -wait -verbose GROUP $grp_name

DISTRIB $UNIREP_REMOTESYS"

echo "Now running:"$cmd >> $reportfilename

$cmd >> $reportfilename

returncode=$?

echo "Return code=$returncode" >> $reportfilename

if [ $returncode = 0 ]

then

echo "Group Sync Worked" >> $reportfilename

else

export cmd="$UVBIN/uv_repadmin report GROUP $grp_name"

echo "Now running:"$cmd >> $reportfilename

$cmd

returncode=$?

echo "returncode=$returncode" >> $reportfilename

if [ $returncode = $REP_SYNCING -o $returncode = $REP_DO_SYNC -o $returncode =

$REP_RUNNING -o $returncode = $SUB_RUNNING -o $returncode = $SUB_SYNCING -o

$returncode = $SUB_RESYNCING ]

then

group_syncing=1

else

group_syncing=0

if [ $returncode -lt 17 ]

then

group_syncing=1

echo "group appears to be a publishing group so and sync failures are

ignored"

echo "group_syncing=$group_syncing" >> $reportfilename

if [ $group_syncing = 0 ]

then

echo "Group Sync Failed" >> $reportfilename

all_synced=0

sleep 1 done echo "all_synced flag = "$all_synced >> $reportfilename if [ $all_synced = 1 ] then

echo "Subject: Sync Commmands Worked - Please Check Systems" | cat

- $reportfilename | /usr/lib/sendmail -F $machinename -t $MAILRECS else

echo "Subject: SYNC COMMANDS FAILED - PLEASE CHECK SYSTEMS" | cat

- $reportfilename | /usr/lib/sendmail -F $machinename -t $MAILRECS

Chapter 3: Administering U2 Data Replication

rm $scriptrunningname

exit 4 fi rm $scriptrunningname exit 0

Listing replication files

Use the

LIST.REPLICATION.FILE command to list active replication files in your application. This command lists all replication file entries for an account or file you specify.

LIST.REPLICATION.FILE [ALL |DICT |DATA] filename[,subfile] NO.PAGE

If you specify ALL, UniVerse displays all active replication files in the current account. If the local account is an account-level replication account, this command displays the account as well.

If you specify a file name, UniVerse displays all replication files contained in the replication file table related to that file. If you do not specify ALL or filename, UniVerse obtains the file names from an active select list, or prompts for input.

LIST.REPLICATION.FILE displays the following information about replicated files:

▪ FTYPE – The type of file. Valid file types are:

▫ LF – LF directory

▫ DICT – Dictionary file

▫ DATA – Hashed file

▫ QDICT – Q-pointer dictionary file

▫ QDATA – Q-pointer data file

▫ QLF – Q-pointer LF directory

▫ ACCT – The account-level replication account

▪ FILE NAME – The VOC file name in the replication file table. If the replication file is not located in the local account, the

LIST.REPLICATION.FILE command also lists the path to the file.

▪ REPLICATION – The replication definition for the file.

▫ PUBLISHED – The file is published

▫ SUBSCRIBED – The file is subscribed

▫ EXCLUDED – The file is excluded from replication

▫ INACTIVE – The file is included in replication, but is currently disabled

▪ PRIMARY – Whether the file is considered the primary replication file.

▪ GROUP – The name of the replication group

Note: When using account-level file replication, a UniVerse distributed file (Type 27 file) and all its part files are loaded separately in a replication object table, where U2 Data Replication treats them all as separate files. The update on a distributed file is replicated through the part files. When an uvsh session updates a distributed file, or updates the distributed part file directly, the update is replicated with the part file’s name. This requires that the subscriber has the same definition of the distributed file as is on publisher system. Otherwise, data inconsistency may occur.

Replication files with multiple VOC pointers

If a file has multiple definitions in the VOC file, in the same or different account, UniVerse loads each

VOC item name in different replication file entries. When a uvsh process updates a record in the file, the process searches for the primary replication file entry in the replication file table by the i-no/d-no, beginning from the static replication file entries. If there is no match, UniVerse searches the dynamic replication file entries. UniVerse uses the first match for replication, generating a replication log in the associated replication group, and sending the VOC file name to the subscriber for publication. This

VOC name is referred to as the primary replication file.

When you issue a

DELETE.FILE command that physically deletes the file, UniVerse disables all replication file entries with the same i-no/d-no. If you delete a VOC pointer that points to the file, or a symbolic link or physical link, UniVerse only disables the corresponding replication file entry. UniVerse does not disable other replication file entries pointing to the file. If you disable the primary replication file, UniVerse uses the next matched file as the primary replication file.

When you enable a replication file, UniVerse only enables the corresponding VOC file name and account ID, it does not automatically search and enable other VOC file names that point to the same file.

When you replicate a file-level command, UniVerse uses the corresponding replication file entry for the target file regardless if it is the primary replication file or a secondary replication file. UniVerse always replicates record-level commands through the primary replication file.

If you have multiple VOC file entries for a replication file, we recommend that you define only one VOC name in the included file list so UniVerse knows which file name and which replication group to use with replication.

Error messaging

When U2 Data Replication is disabled, detailed error messages are written to the rm.log file. The following example illustrates messages written to the log when a publishing process is terminated:

Wed Oct 5 10:53:17 RM: sigchld received: pid=393236, dsig=9

Replication daemon on group 0(393236) is killed(9)!

Wed Oct 5 10:54:06 RM: Force stop group acct_grp(0)

Wed Oct 5 10:54:06 RM: kill publistener 454762

RM trying to kill 454762 by sig 9

RM: kill 454762

Wed Oct 5 10:54:06 RM: kill Publisher 393236

RM trying to kill 393236 by sig 9

RM: kill 393236

Wed Oct 5 10:52:48 2011: Fatal error from process 393236: Group=0,

Rep Error=2560:Publisher killed; OS Error=0:Error 0

Replication start disabling replication!

RM: Force RFS group commit.

Replication is Disabled!

RM: Pause database activity.

CheckPoint time before ForceCP: Wed Oct 5 10:55:53 2011

.CheckPoint time after ForceCP: Wed Oct 5 10:58:55 2011

.CP has been forced successfully.

DBpause successful.

RM: Force RFS group commit.

Stopped Publishing Group acct_grp successfully.

RM: Disable Replication.

RM: Resume database activity.

DBresume successful.

Chapter 3: Administering U2 Data Replication

Execute Replication Exception Action program

/disk1/repacct/repeventtrig.sh

Publisher killed, RM disabled replication successfully.

Refreshing the subscriber database

Complete the following steps to copy the database files from the publishing system to the subscribing system.

1. Run the uv_repadmin suspend command on either the publishing system or the subscribing system. For information on running this command, see

suspend command, on page 73 .

2. On the publishing system, run the following command: uv_repadmin reset -noresume

This clears any pending logs on the publishing system.

3. On the publishing system, run the uv —admin —L command to pause the database. If you are sure there are no applications running on the publishing system, you may skip this step. For information about the uv —admin —L command, see the UniVerse Commands Reference.

4. Copy the files you are replicating from the publishing system to the subscribing system.

5. If you paused the publishing system, run the uv —admin —U command. For information about the uv —admin —U command., see the UniVerse Commands Reference.

6. If the subscribing system is down, start UniVerse with the uv —admin —start —init command. Otherwise, run the uv_repadmin reconfig command. For information about this command, see

reconfig command, on page 76

7. Run the uv_repadmin sync on the either the publishing system or the subscribing system if

AUTORESUME is not enabled on the subscribing system. For information about this command,

see sync command, on page 74 . If AUTORESUME is enabled, U2 Data Replication will initialize

an automatic synchronization operation.

Disabling U2 Data Replication

In U2 Data Replication suspension mode, the publisher continues generating replication logs and reserves them for the next synchronization process. This feature can quickly synchronize the standby database without a lot of user intervention. However, if replication is suspended too long, either because of a subscriber system failure, or for subscriber system maintenance, the publishing system may accumulate enough replication logs to fail the replication log file system. In an extreme case, a full file system can crash the entire publisher system. For this reason, disablement of replication prior to filling the disk entirely may provide for a more graceful recovery.

Replication DISABLE mode

In replication

DISABLE mode, all replication functions stop, but the repmanager continues to run.

The following actions occur when U2 Data Replication is disabled:

▪ All replications are suspended.

▪ All publishing processes stop.

▪ The uv process stops generating replication logs.

▪ The repmanager daemon only accepts the ENABLE, RECONFIG, and STOP commands.

▪ The SYNC, SUSPEND, and RESET commands do not proceed until replication is enabled.

▪ The DISABLE mode persists after stopping and restarting UniVerse.

▪ Reconfiguring U2 Data Replication does not affect the DISABLE mode.

Replication ENABLE mode

If one of the following events occurs, U2 Data Replication automatically switches to the

DISABLE mode:

▪ The database administrator issues a DISABLE command.

▪ A fatal replication system error occurs. The error handling procedure sends a request to disable replication.

▪ UniVerse is started with uv -admin -start -disable.

When the replication manager receives a

DISABLE request, it performs the following tasks:

▪ Suspends all active replications.

▪ Sets the replication disable flag and saves it in the uvrepsys.log.

▪ Issues the uv -admin -L command.

▪ Exits the publishing processes.

▪ If the ClearLog option was specified, clears the replication log files for all replication groups.

▪ Issues the uv -admin -U command.

▪ If the disable request was issued in error handling, executes the exception action script, if defined, on the local system.

When the replication manager starts with the disable option, it loads the replication configuration, sets the replication disable flag and saves it in the uvrepsys.log, and continues running in

DISABLE mode.

Replication ENABLE mode

The replication

ENABLE mode is the normal running mode for U2 Data Replication. If U2 Data

Replication is disabled, it is enabled if the system administrator issues the

ENABLE command, or

UniVerse is started with the -init option.

When the replication manager receives an

ENABLE request, it performs the following tasks:

▪ Issues the uv -admin -L command.

▪ Clears the replication system disable flag and saves it in the uvrepsys.log file.

▪ Resets the log sequence number for all groups.

▪ Clears the replication log files.

▪ Starts the publishing processes for all publishing groups.

▪ Issues the uv -admin -U command.

▪ Issues the SYNC command to all replications if AUTORESUME is enabled.

Runtime error handling

With replication disablement, the runtime error handling of U2 Data Replication changes. If U2 Data

Replication incurs a fatal error, U2 Data Replication is disabled and continues running UniVerse in

DISABLE mode rather than crashing the publishing system.

The following system errors will result in the publishing system being disabled:

▪ When a uvudt or tm process encounters a log extension file (LEF) error when handling replication logs.

▪ When the publishing system cannot access the log reserve file (LRF).

Chapter 3: Administering U2 Data Replication

▪ When the publishing process is terminated.

▪ When the publishing process exits abnormally.

Applications continue to run in DISABLE mode.

We recommend that you write and deploy a U2 Data Replication exception action script. If U2 Data

Replication is disabled due to an unexpected event, the replication manager executes the script.

On a subscribing system, when a subscribing process or replication writer process encounters an LEF or LRF failure, U2 Data Replication is suspended.

Enabling or disabling U2 Data Replication

You can enable or disable U2 Data Replication using the following methods:

•

Enabling or disabling U2 Data Replication using uv_repadmin

Use the uv_repadmin command to enable or disable U2 Data Replication from the operating system level.

•

Enabling or disabling U2 Data Replication using uv -admin

You can use the uv -admin -start or uv -admin -stop commands to enable or disable all of UniVerse, including U2 Data Replication.

•

Enabling or disabling U2 Data Replication through XAdmin

Enable U2 Data Replication through XAdmin using the Replication pane.

Enabling or disabling U2 Data Replication using uv_repadmin

Use the uv_repadmin command to enable or disable U2 Data Replication from the operating system level.

▪ To disable U2 Data Replication, use the disable option: uv_repadmin disable [-clearlog] [-verbose]

The -clearlog option clears the replication log files. The -verbose option displays messages to the screen.

▪ To enable U2 Data Replication, use the enable option: uv_repadmin enable [-verbose]

The -verbose option displays messages to the screen.

You must be logged in as root to enable or disable U2 Data Replication.

Enabling or disabling U2 Data Replication

Enabling or disabling U2 Data Replication using uv -admin

You can use the uv -admin -start or uv -admin -stop commands to enable or disable all of

UniVerse, including U2 Data Replication.

For more information, see

Starting UniVerse daemons, on page 40 and Stopping UniVerse daemons, on page 40

Enabling or disabling U2 Data Replication

Enabling or disabling U2 Data Replication through XAdmin

Enable U2 Data Replication through XAdmin using the Replication pane.

For more detailed steps about enabling or disabling U2 Data Replication through XAdmin, see

Managing U2 Data Replication through XAdmin, on page 43

1. To enable or disable U2 Data Replication through XAdmin, from the Admin Tasks view, click

Replication, then click the Replication Tool tab.

2. To enable U2 Data Replication, click the target for which you want to enable replication, then click

Enable.

3. To disable U2 Data Replication, click the target for which you want to disable replication, then click Disable.

You must be logged in as root to enable or disable U2 Data Replication.