Windows2000/2003
ETERNUS SF Replicator 2.5 Messages Guide
B1WD-0931-01ENZ0 (00)
i
Preface Purpose
This manual explains the messages of ETERNUS SF Replicator (referred to as Replicator) on Windows2000
and Windows2003 operating systems.
Audience
This manual is targeted at system administrators responsible for managing and maintaining business
critical applications and their related data.
Related Manuals
The set of manuals related to Replicator are as follows:
• ETERNUS SF Replicator Installation Guide
This manual explains the process of installation and configuration of Replicator.
• ETERNUS SF Replicator Administrator Guide
This manual explains the process of disk mirroring during normal operations of Replicator.
• ETERNUS SF Replicator Messages Guide (This manual)
This manual explains the messages of Replicator.
• ETERNUS SF Replicator Common Console Guide
This manual explains the process of installation and configuration of Console option.
A Note Regarding Descriptions
• Microsoft(R) Windows(R) 2000 Server and Microsoft(R) Windows(R) 2000 Advanced Server are
referred to as Windows2000.
• Microsoft(R) Windows(R) Server 2003 Standard Edition and Microsoft(R) Windows(R) Server 2003
Enterprise Edition are referred to as Windows2003.
• ETERNUS SF Replicator is referred to as Replicator.
• The symbol NOTE is used to describe items related to actual working of the system, points to
note, actions not to be taken and items which are strongly recommended for smooth operations.
Trademarks
• Windows is a registered trademark of Microsoft Corporation in the United States and other
countries.
• All other mentioned services and/or products are registered trademarks of other companies as the
case maybe.
COPYRIGHT
Copyright (C) 2002-2007 FUJITSU LIMITED. All rights reserved.
Copyright (C) 2004-2007 Softek Storage Solutions Corporation, International Business Machines
Corporation. All rights reserved.
The information contained in this manual is the licensed property of FUJITSU LIMITED and Softek Storage
Solutions Corporation, International Business Machines Corporation. Use of the information contained
herein is restricted pursuant to the terms and conditions of a license agreement.
Contents Preface .......................................................................................................................................ii Contents....................................................................................................................................iii Messages....................................................................................................................................1
BABGET........................................................................................................................................1 BABOFLOW..................................................................................................................................1 BABROFLOW ...............................................................................................................................1 BADAUTH.....................................................................................................................................2 BADDEVID ...................................................................................................................................2 BADHDR .......................................................................................................................................2 BADHOSTNAM ............................................................................................................................3 BADKEY........................................................................................................................................3 BADTUNABLE .............................................................................................................................3 BACKAGAIN.................................................................................................................................4 BACKEND.....................................................................................................................................4 BACKREFR...................................................................................................................................4 BACKFRESH ................................................................................................................................4 BACKTERM ..................................................................................................................................4 CFGBDKEY...................................................................................................................................5 CFGERR........................................................................................................................................5 CFGFILE.......................................................................................................................................5 CFGPROB .....................................................................................................................................6 CHKSUM.......................................................................................................................................6 CHUNKDELAY.............................................................................................................................6 CHUNKSZ.....................................................................................................................................7 CMDIGNORE................................................................................................................................7 COMPRESSVAL............................................................................................................................7 CPOFF...........................................................................................................................................8 CPOFFAGAIN ...............................................................................................................................8 CPON.............................................................................................................................................8 CPONAGAIN.................................................................................................................................8 CPONERR .....................................................................................................................................9 CPSTARTAGAIN...........................................................................................................................9 CPSTOPAGAIN.............................................................................................................................9 CTLOPEN .....................................................................................................................................9 DEVLOCK ...................................................................................................................................10 DEVMISS ....................................................................................................................................10 DISMOUNT.................................................................................................................................10 DRVBACK ................................................................................................................................... 11 DRVREFR.................................................................................................................................... 11 DRVDELDEV .............................................................................................................................. 11 DRVERR......................................................................................................................................12 EXEC ...........................................................................................................................................12 FILE ............................................................................................................................................12 FREFREND.................................................................................................................................13 FREFRESH .................................................................................................................................13 FREFREND2...............................................................................................................................13 FREFRESH2 ...............................................................................................................................13 IODELAY.....................................................................................................................................13 JRNFILDEL ................................................................................................................................14 JRNINIT......................................................................................................................................14 JRNMAGIC .................................................................................................................................14 JRNMISS.....................................................................................................................................15
iii
JRNOPEN ...................................................................................................................................15 JRNPATH ....................................................................................................................................15 JRNSPACE..................................................................................................................................16 JRNUNLOCK..............................................................................................................................16 LGDOPEN...................................................................................................................................16 LICGENERR ...............................................................................................................................17 LOCSIZ........................................................................................................................................17 MALLOC .....................................................................................................................................17 MIGRATE....................................................................................................................................18 MIR2SMAL..................................................................................................................................18 MIRDEVID..................................................................................................................................18 MIRDISABLE..............................................................................................................................19 MIRMISMTCH............................................................................................................................19 MIRMISS.....................................................................................................................................19 MIRSIZ ........................................................................................................................................20 MIRSTAT.....................................................................................................................................20 NETBROKE ................................................................................................................................20 NETPROB ...................................................................................................................................21 NETTIMEO .................................................................................................................................21 NOCONFIG.................................................................................................................................21 NODEVS......................................................................................................................................21 NOGROUP ..................................................................................................................................22 NOHRT........................................................................................................................................22 NOPMD .......................................................................................................................................22 NORMAL.....................................................................................................................................22 NORMD.......................................................................................................................................23 OPEN...........................................................................................................................................23 OPENEVENT..............................................................................................................................23 PASSTHRUU .................................................................................................................................24 PMDAGAIN.................................................................................................................................24 PMDEXIT....................................................................................................................................24 PROTDEV ...................................................................................................................................24 PSADDGRP.................................................................................................................................25 PSBADHDR.................................................................................................................................25 PSCREATE..................................................................................................................................25 PSCREAT_SUCCESS .................................................................................................................26 PSERROR....................................................................................................................................26 PSNOROOM................................................................................................................................26 PSRDGATTR ...............................................................................................................................27 PSWTDATTR...............................................................................................................................27 PSWTGATTR...............................................................................................................................27 PSWTHRDB ................................................................................................................................28 PSWTLRDB.................................................................................................................................28 READERR ...................................................................................................................................29 REPMD........................................................................................................................................29 REFRAGAIN ...............................................................................................................................29 REFRBACK.................................................................................................................................29 REFRESH....................................................................................................................................30 RREFRESH .................................................................................................................................30 REFRESHC.................................................................................................................................30 REFREND ...................................................................................................................................30 REFRENDC.................................................................................................................................30 REFRTERM ................................................................................................................................30 REMWAKEUP.............................................................................................................................31 REFRETIMEO ............................................................................................................................31 REFRETIMEOUT .......................................................................................................................31 RMDAEND..................................................................................................................................31 RMDASTART ..............................................................................................................................32
RMDEXIT....................................................................................................................................32 RMDAEXIT .................................................................................................................................32 RMDSTART.................................................................................................................................32 RSYNCCPOFF ............................................................................................................................32 SEEKERR....................................................................................................................................33 SOCKACCEPT ............................................................................................................................33 SOCKCONNECT.........................................................................................................................33 SOCKCREAT...............................................................................................................................34 SOCKINIT...................................................................................................................................34 SOCKLISTEN .............................................................................................................................34 SOCKRECONN...........................................................................................................................35 SOCKSETB .................................................................................................................................35 SOCKNOTME .............................................................................................................................35 SOCKSETNONB.........................................................................................................................36 STARTGRP..................................................................................................................................36 STAT ............................................................................................................................................36 STOPGRP....................................................................................................................................37 SYSCFGERR ...............................................................................................................................37
v
Messages BABGET
PMD unable to get data from driver for device [%s1], reason code [%s2]
Type WARNING
Parameter %s1: Source partition
%s2: Error code of WindowsAPI
Description A problem was encountered when copying data from the BAB.
Action Stop mirroring process and execute the refresh processing
BABOFLOW BAB exhausted during normal operation [%s]
Type WARNING
Parameter %s: Replication group number
Description This message indicates a BAB overflow.
Action Use the Configuration Tool to reconfigure the BABSIZE parameter or other system parameters so
they are consistent with your system usage.
BABROFLOW BAB exhausted during refresh operation [%s]
Type WARNING
Parameter %s: Replication group number
Description This message indicates a BAB overflow.
Action Use the Configuration Tool to reconfigure the BABSIZE parameter or other system parameters so
they are consistent with your system usage.
1
BADAUTH Received bad authentication or config path from [%s1]: %s2
Type FATAL
Parameter %s1: Source system name
%s2: Target system name
Description This message indicates a discrepancy between the primary and secondary system configuration
files.
Action Check the files on both systems. Recopy the files from the primary to secondary system.
BADDEVID Received write command with bad device ID %s
Type FATAL
Parameter %s: Device ID
Description The RMD on the secondary system received a “write” command that contained a bad device ID.
Action Contact Technical Support.
BADHDR Invalid magic number in BAB entry header.
Type FATAL
Description Replicator Windows found a bad BAB entry header for the indicated device.
Action Contact Technical Support.
BADHOSTNAM Configuration file [%s1] network hostname [%s2] cannot be resolved.
Type FATAL
Parameter %s1: Configurationfile name
%s2: Source system / Target system name
Description There is either a network or configuration file problem.
Action Resolve the inconsistency between the network configuration and Replicator configuration.
BADKEY Key <key> is invalid in %s
Type FATAL
Parameter %s: キーParameter
Description There is a syntax error in the parameter indicated in <keyname> in the configuration file.
Action Correct the configuration file. Remember to copy the updated configuration file to the secondary
system.
BADTUNABLE [%s ] is not a valid tunable parameter name
Type WARNING
Parameter %s: Key
Description An invalid tunable parameter name was specified in the configuration file.
Action Check the configuration file and specify a valid tunable parameter name.
3
BACKAGAIN Backfresh operation already running. Use killbackfresh first.
Type WARNING
Description A backfresh is running so another backfresh is not accepted.
Action Let the current backfresh complete, or kill the current backfresh and then restart the backfresh.
BACKEND Backfresh operation completed
Type INFO
Description The backfresh operation has terminated.
BACKREFR Backfresh operation cannot be started. Logical group is currently in refresh mode
Type WARNING
Description The backfresh operation has not been allowed because a refresh operation is in progress.
Action Terminate the refresh operation first if you need to perform a backfresh operation. Normally, the
refresh operation should be allowed to complete to insure data integrity.
BACKFRESH Backfresh operation started.
Type INFO
Description Notification that backfresh has started.
BACKTERM Backfresh operation terminated.
Type INFO
Description A killbackfresh was issued or some event caused the backfresh operation to terminate.
CFGBDKEY Configuration file [%s1] line [%s2] has an unrecognized keyword [%s3].
Type FATAL
Parameter %s1: Configurationfile name
%s2: Line number
%s3: キー
Description An invalid parameter name (keyword) was used in the configuration file.
Action Replace the invalid keyword with a valid one in the configuration file. Remember to copy the
updated file to the secondary system.
CFGERR Configuration file [%s1] error at or before line [%s2].
Type FATAL
Parameter %s1: Configurationfile name
%s2: Line number
Description There is a problem with a specific line in the configuration file.
Action Verify and fix the information in the configuration file. Remember to copy the updated file to the
secondary system.
CFGFILE Unable to read config file [%s]
Type FATAL
Parameter %s: Configurationfile name
Description The configuration file is unable to read due to error message specified in <syserrormsg>.
Action Fix the error caused by <syserrormsg>.
5
CFGPROB Encountered a configuration problem at startup.
Type FATAL
Description This message indicates a problem occurred during the handshake between the primary and
secondary systems. There may be a discrepancy between the configuration files on the primary
and secondary systems.
Action Verify the configuration files and recopy the file from the primary system to the secondary one, if
necessary.
CHKSUM Failed computing device [%s] checksum
Type FATAL
Parameter %s: Device name
Description A checksum operation failed on the indicated device. Checksum is used during a Checksum Refresh to compare all blocks on the primary system against those on the secondary one to
identify deltas. Only those blocks that have been modified on the primary are sent to the
secondary system.
Action Contact Technical Support
CHUNKDELAY CHUNKDELAY parameter outside of range: [%s1] (Max: [%s2] Min: [%s3])
Type WARNING
Parameter %S1: Specified value
%s2: Minimum value
%s3: Maximum value
Description The CHUNKDELAY tunable parameter was specified incorrectly.
Action Use the Configuration Tool to reset CHUNKDELAY to a value within the minimum and maximum
value.
CHUNKSZ CHUNKSIZE parameter outside of range: [%s1] (Max: [%s2] Min: [%s3])
Type WARNING
Parameter %s1: Specified value
%s2: Minimum value
%s3: Maximum value
Description The CHUNKSIZE tunable parameter was specified incorrectly.
Action Use the Configuration Tool to reset CHUNKSIZE to a value within the minimum and maximum
value.
CMDIGNORE %s command ignored. '%s' is currently running in a 'uninitialized' state and is unable to accomodate
the '%s' request.
Type WARNING
Parameter %s: コマンド名
Description A command has been typed, but the current operating state cannot run the command.
Action Put Replicator in the correct state for the command and then reissue the command.
COMPRESSVAL COMPRESSION parameter value must be [off | 0] or [on | 1].
Type WARNING
Description The COMPRESSION parameter was specified incorrectly.
Action Set the COMPRESSION parameter to either 0 (off) or 1 (on).
7
CPOFF [%s] successfully transitioned out of checkpoint mode.
Type INFO
Parameter %s: Replication group number
Description The indicated Replication Group switched out of checkpoint mode successfully.
CPOFFAGAIN [%s] is NOT in or is transitioning out of checkpoint mode
Type WARNING
Parameter %s: Replication group number
Description The Replication Group indicated has not been placed in checkpoint mode as expected.
Action Check your checkpoint script code.
CPON [%s] is in checkpoint mode
Type INFO
Parameter %s: Replication group number
Description The indicated Replication Group has been placed in checkpoint mode as expected.
CPONAGAIN [%s] is already in or is transitioning to checkpoint mode
Type INFO
Parameter %s: Replication group number
Description The Mobility Group indicated was already in checkpoint mode when another checkpoint operation
was run.
CPONERR [%s] DID NOT transition to checkpoint mode due to error(s)
Type WARNING
Parameter %s: Replication group number
Description The indicated Mobility Group has not switched to checkpoint because of errors.
Action Examine your checkpoint script for possible errors. Check your checkpoint script code.
CPSTARTAGAIN [%s] is currently transitioning to checkpoint mode
Type INFO
Parameter %s: Replication group number
Description The Mobility Group indicated is switching to checkpoint mode.
CPSTOPAGAIN [%s] is currently transitioning from checkpoint mode
Type INFO
Parameter %s: Replication group number
Description The Mobility Group indicated is switching out of checkpoint mode.
CTLOPEN Unable to open master control device: %s
Type FATAL
Parameter %s: System error message
Description There is a configuration, operating system, or hardware error.
Action Refer to the system error message for possible actions.
9
DEVLOCK Could not lock device [%s1]: %s2
Type FATAL
Parameter %s1: Device name
%s2: System error message
Description The lock on the volume could not be obtained.
Action Use the dtcanalyzer utility to discover what is preventing the lock.
DEVMISS Profile in config file [%s1] prior to line [%s2] missing data device specification
Type FATAL
Parameter %s1: Configurationfile name
%s2: Line number
Description The dtc device profile in the configuration file is missing or unreadable.
Action Correct or add the device path in the configuration file.
DISMOUNT Failed to 'dismount' device [%s1] from group [%s2]
Type FATAL
Parameter %s1: Device name
%s2: Replication group number
Description The dismount of the volume failed.
Action Look at the Windows System event log to determine the problem.
DRVBACK Logical Group driver state is 'backfresh' conflicting with current operational state of daemons.
Logical Group daemons exiting.
Type WARNING
Description The logical grop is in a backfresh state, yet the driver in another state.
Action Correct the driver state using dtcoverride.
DRVREFR Logical Group driver state is 'refresh' conflicting with current operational state of daemons.
Logical Group daemons exiting.
Type WARNING
Description The Mobility Group is in a refresh state, yet the driver in another state.
Action Correct the driver state using dtcoverride.
DRVDELDEV Driver failed to delete device %s1 from group %s2
Type FATAL
Parameter %s1: Device name
%s2: Replication group number
Description Replicator Windows could not delete the device from the Mobility Group as requested. The device
may be busy.
Action Make sure the device is not busy, and then attempt to delete the device from the Replication
Group again.
11
DRVERR Got driver error in [%s]
Type FATAL
Parameter %s: System error message
Description Driver encounters errors due to operation <operation_name> with <driver_error_msg>. This error is
generally caused by the kernel being low on memory resources.
Action Stop some of the applications that are running and try again.
EXEC Failed to exec a subprocess [%s]
Type WARNING
Parameter %s: System error message
Description This error indicates a pathname or permission problem.
Action Check the pathname in the configuration file and file permissions.
FILE Failed opening file [%s]
Type FATAL
Parameter %s: System error message
Description This error indicates a pathname or permission problem.
Action Check the pathname in the configuration file and file permissions.
FREFREND Full Refresh phase 1 completed
Type INFO
Description The first phase of the full refresh has completed.
FREFRESH Full Refresh phase 1 started
Type INFO
Description The first phase of the full refresh has started.
FREFREND2 Full Refresh phase 2 completed
Type INFO
Description The second phase of the full refresh has completed.
FREFRESH2 Full Refresh phase 2 started
Type INFO
Description The second phase of the full refresh has started.
IODELAY IODELAY parameter outside of range: [%s1] (Max: [%s2] Min: [%s3])
Type WARNING
Parameter %s1: Specified value
%s2: Maximum value
%s3: Minimum value
Description The IODELAY tunable parameter was specified incorrectly.
Action Use the Configuration Tool to reset IODELAY to a value within the minimum and maximum value.
13
JRNFILDEL Journal file %s delete failed: %s
Type FATAL
Parameter %s: Journal file name
Description The journal file specified is not available for deletion.
Action Perform a checksum refresh.
JRNINIT Secondary journal initialization failed
Type FATAL
Description The Secondary journal has an initialization error.
Action Contact Technical Support to fix possible problems (the journal path is not set properly or the
journal partition is not writable).
JRNMAGIC Secondary journal file [%s] contains bad magic value in header
Type FATAL
Parameter %s: Journal file name
Description The journal file has been corrupted.
Action Create a new journal file and update the path to it in the configuration file. Remember to copy the
updated configuration file to the secondary system.
JRNMISS Config file %s1 near line %s2 does not contain a secondary journal entry
Type FATAL
Parameter %s1: Configuration file name
%s2: Line number
Description The indicated configuration file does not contain the expected journal file entry.
Action Check the configuration file on both primary and secondary systems and ensure that it contains a
reference to a journal file.
JRNOPEN Unable to open secondary journal [%s]
Type FATAL
Parameter %s: Journal file name
Description Replicator Windows is unable to open the indicated journal file.
Action Ensure that the journal file exists and has the correct permissions.
JRNPATH Unable to locate secondary journal path [%s]
Type FATAL
Parameter %s: Journal file name
Description Replicator Windows is unable to open the indicated journal file.
Action Open the configuration file on both primary and secondary systems and ensure that it contains a
valid path to a journal file.
15
JRNSPACE Out of space writing to secondary journal [%s]
Type FATAL
Parameter %s: Journal file name
Description The indicated journal file has run out of disk space on the secondary system. This error may have
occurred because too much data was being mirrored during a checkpoint operation.
Action Increase the amount of disk space available to the journal file area on the secondary system.
JRNUNLOCK Secondary journal [%s1] unlock failure by: %s2
Type WARNING
Parameter %s1: Journal file name
%s2: System error message
Description The Secondary journal has an unlock failure from <RMD name>.
Action Restart PMD/RMD with Full Refresh.
LGDOPEN Unable to open logical group device [%s1]: %s2. Kill logical group PMD if it's running.
Type FATAL
Parameter %s1: Device name
%s2: System error code
Description Replicator Windows cannot open the indicated Mobility Group device.
Action Check your configuration files to ensure that they contain a valid device specification for the
Mobility Group. If your configuration files are correct.
LICGENERR License error.
Type FATAL
Description There is a problem with the license key.
Action Check the DTC.lic file.
LOCSIZ Primary data device [%s1] open/ioctl failure: %s2
Type FATAL
Parameter %s1: Device name
%s2: System error message
Description The primary device could not be opened or is not answering.
Action Review the Softek configuration to insure that the source disks are defined correctly.
MALLOC Failed to allocate %s bytes of memory.
Type FATAL
Parameter %s: Amount of memory
Description The system’s virtual memory is exhausted. This is a general memory allocation error.
Action Reduce the value on the CHUNKSIZE tunable parameter and check quotas for runaway processes.
17
MIGRATE Driver migrate failure for logical group [%s1]: %s2
Type FATAL
Parameter %s1: Replication group number
%s2: System error message
Description No specific diagnostics.
Action Contact Technical Support
MIR2SMAL Config [%s1] primary's local data disk [%s2] larger than secondary's disk [%s3] (%s4 vs %s4)
Type FATAL
Parameter %s1: Configuration file name
%s2: Source partition
%s3: Target partition
%s4: Disk size
Description The source and target disks are not the same size. The mirror device on the secondary system is
smaller than the local data device.
Action Reconfigure the mirror device to be the same size as the local data device.
MIRDEVID Bad device id [%s]. Device not found in group device list
Type FATAL
Parameter %s: Device ID
Description The device id is not in the known device list.
Action Insure that the disks being copied are still present on the system.
MIRDISABLE Mirroring has been disabled by file [%s] being present. Use reco command with '-d'.
Type FATAL
Parameter %s: s###.offfile name
Description The dtcrmdreco command prohibits mirroring to the secondary mirror devices.
Action Type the dtcrmdreco -d command to delete this file.
MIRMISMTCH Configuration mismatch between primary and secondary for disk PROFILE: %s
Type FATAL
Parameter %s: Target partition
Description The configuration file indicated has changed. The secondary device specification in the
configuration files on the primary and secondary systems do not match.
Action Restore the configuration file so that the mirror device specification in the primary and secondary
configuration files match.
MIRMISS Profile in config file [%s1] prior to line %s2 missing mirror device specification
Type FATAL
Parameter %s1: Configurationfile name
%s2: Line number
Description There is no secondary device specification in the configuration file, so Replicator Windows cannot
replicate data.
Action Use the Configuration Tool to include a secondary device specification in the configuration file.
Remember to copy the updated file to the secondary system.
19
MIRSIZ Secondary mirror device [%s1] %s2
Type FATAL
Parameter %s1: Device name
%s2: System error code
Description Replicator Windows failed to open the secondary device specified in the configuration file.
Action Check the device information.
MIRSTAT Secondary mirror device [%s1] stat failure: %s2
Type FATAL
Parameter %s1: Target partition
%s2: System error code
Description This message indicates a possible error in the secondary device definition in the configuration file.
Or, the mirror device on the secondary may have failed.
Action Make sure the secondary device is specified correctly in the configuration file. Check the health of
the mirror device and the secondary system.
NETBROKE Lost connection to [%s].
Type FATAL
Parameter %s: Source system / Target system name
Description The network connection to the indicated host system was lost.
Action No ACTION required — self-correcting when the network connection is re-established.
NETPROB Encountered a network initialization problem at startup
Type FATAL
Description There is a possible network problem eplication.
Action Check the network.
NETTIMEO Timeout communicating on network connection [%s] <-> [%s]. Check link and/or remote service.
Type WARNING
Parameter %s: Socket error code
Description There is a possible network problem.
Action Check the network.
NOCONFIG Could not find config files for target logical group(s)
Type WARNING
Description Replicator Windows could not find the configuration files for the Replication Group.
Action Ensure that the configuration files exist on the primary or secondary systems.
NODEVS Config file: %s contains no device profiles.
Type FATAL
Parameter %s: Configurationfile name
Description The configuration file has no devices defined.
Action Add devices to the configuration file using the configtool.
21
NOGROUP Target groups not started. Use start command.
Type WARNING
Description This message is informational. The intended Mobility Group was not started.
Action Use the dtcstart <group #>command to start the Replication Group.
NOHRT Could not get HRT for device: %s1, device id: %s2
Type FATAL
Parameter %s1: Device name
%s2: Device number
Description Could not find the high resolution table entry for the volume.
Action Restart the Replication Group.
NOPMD Checkpoint issued for primary group: %s but PMD is not running
Type WARNING
Parameter %s: Replication group number
Description Replicator Windows can locate the correct configuration file, but the PMD appears not to be
running. It must be running for Replicator Windows to function properly.
Action Use the dtclaunchpmds command to start the PMD.
NORMAL PMD (Primary Mirror Daemon) is in normal mode
Type INFO
Description The Primary Mirror Daemon is in Normal mode.
NORMD Checkpoint issued for secondary group: %s but RMD is not running
Type WARNING
Parameter %s: Replication group number
Description Checkpoint is on the secondary system, but the RMD appears not to be running.
Action Use the dtclaunchpmds command from the primary system to start the PMD and RMD launchpmds.
OPEN Could not open device [%s1]: %s2
Type WARNING
Parameter %s1: Device name
%s2: System error message
Description Replicator Windows could not open the device.
Action Use the system error text to help you determine actions.
OPENEVENT Could not open NT event [%s1]: %s2
Type FATAL
Parameter %s1: Event message
%s2: System error code
Description The eventlog could not be opened.
Action Check that Replicator Windows was installed correctly.
23
PASSTHRU Logical group is in driver PASSTHRU mode. PMD exiting.
Type WARNING
Description The indicated Mobility Group is now in PassThru mode. Replicator Windows is only writing updates
to the local data device, and not mirroring to the mirror data device.
PMDAGAIN Logical Group PMD already running. Use killpmds first.
Type WARNING
Description The PMD was already running when a dtclaunchpmds command was run.
Action Type the dtckillpmds command, and then re-type the dtclaunchpmds command.
PMDEXIT PMD (Primary Mirror Daemon) exited
Type INFO
Description The PMD terminated normally.
PROTDEV Invalid device id [%s] in protocol header
Type FATAL
Parameter %s: Device ID
Description The device id is not a valid for this protocol.
Action Check the device status.
PSADDGRP Failed to add group %s1 to pstore %s2
Type FATAL
Parameter %s1: Replication group number
%s2: Psorefile name
Description Replicator Windows attempted to add the Mobility Group to the Pstore and failed.
Action Contact Technical Support
PSBADHDR Bad header in pstore [%s] - this pstore is invalid
Type WARNING
Parameter %s: Pstorefile name
Description The pstore has been corrupted and is not valid store.
Action Delete and reinitialize the pstore by restarting the Replication Group.
PSCREATE Failed to create pstore %s
Type FATAL
Parameter %s: Pstorefile name
Description Replicator Windows failed to initialize the Pstore.
Action Ensure that the Pstore specification is valid in the configuration file and retry the operation.
25
PSCREAT_SUCCESS Initialized pstore %s1 for group %s2. This pstore can support up to a maximum of %s3 devices.
Type INFO
Parameter %s1: Pstorefile name
%s2: Replication group number
%s3: Number of volumes
Description Replicator Windows initialized the Pstore for the Replication Group.
PSERROR Pstore error: %s
Type FATAL
Parameter %s: Pstorefile name
Description There is a problem with the indicated Pstore.
Action Use the configuration tool to make sure you have configured the Pstore correctly.
PSNOROOM Pstore [%s1] full. Cannot add Device [%s2]. Reinitialize pstore.
Type FATAL
Parameter %s1: Pstorefile name
%s2: Device name
Description The pstore size is not sufficient to hold the specified volume store.
Action Delete and reinitialize the pstore.
PSRDGATTR Failed to read attributes for group %s1 from pstore %s2
Type FATAL
Parameter %s1: Replication group number
%s2: Pstorefile name
Description Replicator Windows could not write Replication Group’s attributes (for example, state information
and tunable parameters) to the Pstore.
Action Check the configuration file for the Mobility Group to make sure that the Pstore has been
configured correctly.
PSWTDATTR Failed to write attributes for device %s1 to pstore %s2
Type FATAL
Parameter %s1: Device name
%s2: Pstorefile name
Description Replicator Windows could not write the device’s attributes to the Pstore.
Action Contact Technical Support
PSWTGATTR Failed to write attributes for group %s1 to pstore %s2
Type FATAL
Parameter %s1: Device name
%s2: Pstorefile name
Description Replicator Windows could not write the Replication Group’s attributes to the Pstore.
Action Contact Technical Support
27
PSWTHRDB Failed to write HRT for device %s1 to pstore %s2
Type FATAL
Parameter %s1: Device name
%s2: Pstorefile name
Description Replicator Windows could not write to the Pstore for the device indicated. Replicator Windows
keeps track of changes when it is in tracking mode and writes the changes to the Pstore on a
controlled shutdown of the product.
Action Contact Technical Support
PSWTLRDB Failed to write LRT for device %s1 to pstore %s2
Type FATAL
Parameter %s1: Device name
%s2: Pstorefile name
Description Replicator Windows could not write to the Pstore for the indicated device. The Pstore is updated
with I/O operations so that a Smart Refresh can be done if needed.
Action Contact Technical Support
READERR Read error on [%s1], offset [%s2] length [%s3]: %s4
Type FATAL
Parameter %s1: Device name
%s2: Offset
%s3: Length
%s4: System error message
Description Replicator Windows encountered a read error for an unknown reason.
Action Refer to the system error message for possible actions.
REPMD PMD_%s exited with non-fatal status, automated relaunch underway
Type WARNING
Parameter %s: Replication group number
Description The PMD has exited and is being relaunched.
REFRAGAIN Refresh operation already running. Use killrefresh first.
Type WARNING
Description A refresh was requested, but one is already running.
Action If the current refresh is the correct type, then do nothing. Otherwise, kill the current refresh
operation and start the correct one.
REFRBACK Refresh operation cannot be started. Logical group is in backfresh mode
Type WARNING
Description A backfresh is running. Any other refresh request cannot be accepted.
Action Wait backfresh terminated.
29
REFRESH Refresh operation started
Type INFO
Description The refresh operation has started.
RREFRESH Refresh operation restarted
Type INFO
Description Refresh operation restarted.
REFRESHC Checksum Refresh operation started
Type INFO
Description Checksum Refresh operation started.
REFREND Refresh operation completed.
Type INFO
Description The refresh operation completed successfully.
REFRENDC Checksum Refresh operation completed
Type INFO
Description Checksum Refresh operation completed.
REFRTERM Refresh operation terminated.
Type INFO
Description The refresh operation ended by a network failure or explicit command.
REMWAKEUP %s
Type WARNING
Description Wakeup the secondary system.
REFRETIMEO Refresh operation timed out. Increase REFRESHTIMEOUT (current: %s secs.). Run launchrefresh
for group.
Type WARNING
Parameter %s: Interval time
Description The refresh has timed out because the REFRESHTIMEOUT threshold has been reached.
Action Adjust the timeout parameter and relaunch the refresh operation.
REFRETIMEOUT REFRTIMEOUT parameter outside of range: [%s1] (Max: [%s2] Min: [%s3])
Type WARNING
Parameter %s1: Specified value
%s2: Maximum value
%s3: Minimum value
Description The specified timeout value is not in the valid range.
Action Adjust the timeout value using a valid parameter.
RMDAEND RMDA (Remote Mirror Apply Daemon) ended - applying journal(s) to mirror(s)
Type INFO
Description Changes in the journal file have been applied to the mirror device on the secondary system.
31
RMDASTART RMDA (Remote Mirror Apply Daemon) started - applying journal(s) to mirror(s)
Type INFO
Description Changes in the journal file are in the process of being applied to the mirror or secondary system.
RMDEXIT RMD (Remote Mirror Daemon) exited
Type INFO
Description The RMD was terminated after processing.
RMDAEXIT RMDA (Remote Mirror Apply Daemon) exited - applying journal(s) to mirror(s)
Type INFO
Description The RMD exited which may be a normal situation.
RMDSTART RMD (Remote Mirror Daemon) started
Type INFO
Description Replicator Windows has initialized the RMD.
RSYNCCPOFF Cannot transition from checkpoint mode during a rsync operation [%s]
Type WARNING
Parameter %s: Process name
Description A checkpoint request cannot be run during a refresh.
Action Retry the checkpoint operation after the refresh operation has finished.
SEEKERR Seek error on [%s1], offset: %s2: %s1
Type FATAL
Parameter %s1: Device name
%s2: Offset
Description A SEEK system call failed.
Action Contact Technical Support
SOCKACCEPT Failed accepting socket on listener descriptor %d: %s
Type FATAL
Parameter %s: Socket name
Description The secondary server failed to accept the bind request.
Action Check the secondary server to ensure it is available and the network is operational.
SOCKCONNECT Failed connecting socket to server [%s1 -> %s2:%s3]: %s4
Type WARNING
Parameter %s1: Souce system
%s2: Target system
%s3: Port number
%s4: Socket error
Description The specified socket failed to connect to the server named.
Action Check that the secondary server is available.
33
SOCKCREAT Failed creating socket : %s
Type FATAL
Parameter System error message
Description The named socket could not be created.
Action Check that the IP address is available.
SOCKINIT Failed initializing socket : %s
Type FATAL
Parameter %s: System error message
Description The socket initialization process failed.
Action Comare the network definition to the Softek configuration, also check system log for error
considerations.
SOCKLISTEN Failed listening on socket %s1: %s2
Type FATAL
Parameter %s1: Socket name
%s2: System error message
Description The attempt to listen on the socket address failed.
Action Check the configuration to insure you have a valid IP addresses.
SOCKRECONN Failed connecting socket to server [%s1 -> %s2:%s3]: %s4 - Retrying connection
Type WARNING
Parameter %s1: Source system
%s2: Target system
%s3: Port number
%s4: Socket error
Description The socket to server connection failed and a retry is in progress.
SOCKSETB Failed setting socket to blocking: %s1 %s2
Type FATAL
Parameter %s1: Socket name
%s2: System error message
Description Blocking was not able to be turned on for the specified socket.
Action Contact Technical Suppot
SOCKNOTME Hostname/IP [%s] does not resolve to this machine
Type FATAL
Parameter %s: Host name
Description The IP address did not exist on this machine.
Action Review the configuration and adjust accordingly.
35
SOCKSETNONB Failed setting socket to non-blocking: %s1 %s2
Type FATAL
Parameter %s1: Socket name
%s2: System error message
Description Non-blocking was not able to be turned on for the specified socket.
Action Contact Technical Suppot
STARTGRP Failed to start group %s
Type FATAL
Parameter %s: Replication group number
Description Replicator Windows failed to start the indicated Replication Group.
Action This error should be informational since the underlying error has already been reported. This can
happen for a variety of reasons, including that the Mobility Group is already started. You can type
the dtcinfo command.
STAT stat error on [%s1]: %s2
Type FATAL
Parameter %s1: file name
%s2: System error message
Description For the given reason, a STAT(2) system call on the indicated file failed.
Action This should be informational since the underlying error has already been reported.
STOPGRP Failed to stop group %s
Type FATAL
Parameter %s: Replication group number
Description The Replication Group was unable to be stopped.
Action Review the log and the system log to diagnose the issue.
SYSCFGERR System config file error: %s
Type FATAL
Parameter %s: System error message
Description There is an error in the system configuration file.
Action Check the configuration file.
37