Chapter 81 RDF Messages

Cause  A file-system error occurred. The message includes both the file-system error number and the name of the file that caused the error.

Effect  Variable; depends upon which file-system error occurred.

Recovery  If this message is issued by an updater process, filename is the name of the volume on the primary system for which the updater is responsible. In such a case consult Table 5-1 of the NonStop RDF/IMP, IMPX, and ZLT System Management Manual to determine the appropriate recovery actions.

Cause  The process that issued this message encountered the specified file system error while attempting to communicate with the specified process.

Effect  Variable; depends upon the process and the particular error, it may be retried or it may cause RDF to abort.

Recovery  Correct the error reported in the message and, if aborted, restart RDF.

Cause  In response to a START RDF command, RDF attempted to execute the designated program file ( program ). The program in that file, however, had a different version number ( received ) than was expected ( expected ). You have installed the wrong version of RDF.

Effect  RDF stops.

Recovery  Install the correct version of RDF on all systems, and then restart RDF.

Cause  The updater has sent a request for permission to read the undo list, but the purger has not yet given the updater permission.

Effect  The updater waits until the purger has completed building the undo list.

Recovery  Informational message only; no corrective action is needed unless the purger is reporting problems.

Cause  The purger has detected that all the updaters have stopped, but at least one updater stopped prematurely and did not stop at the specified timestamp.

Effect  The updaters are stopped, but the backup database is not in a consistent state corresponding to the stop update timestamp.

Recovery  Restart the updaters. If you still need to bring the backup database to a consistent state, do as follows. Wait for the updaters to catch up and then issue a new stop-update-to-time command, specifying a new timestamp.

Cause  A file-system error occurred while RDF was attempting to open a file or process.

Effect  Variable; depends upon which file-system error occurred and which file or process was to be opened. If this error is issued by a process other than an updater against any file other than the EMS event log, then RDF will shut down, except in the following cases:

Recovery  If this message is issued by an updater process, consult Table 5-2 of the NonStop RDF/IMP, IMPX, and ZLT System Management Manual to determine the appropriate recovery actions.

Cause  The monitor process has stopped itself and all RDF processing as the result of an operator-initiated stop or a catastrophic failure.

Effect  The monitor sends a stop message to all RDF processes, and they all successfully shut down.

Recovery  If the operator issued a STOP TMF or STOP RDF command, this message is merely informational and no recovery is required. If this message is unexpected, check the EMS event log to determine the cause of the failure. You can attempt to correct the underlying problem, and then restart RDF. If you do that, however, you should select a convenient time at which to stop TMF and verify that the primary and backup databases are synchronized. You should also consult the EMS event log to determine whether the shutdown and startup proceeded without error. If that is not the case, no recovery is possible.

	NOTE: If TMF dumps any audit trail files to disk while RDF is stopped, you must either restore the dumped files to disk or resynchronize the primary and backup databases before restarting RDF.

Cause  The extractor detected that TMF has not been started.

Effect  RDF cannot run if TMF is not also running. Normally, RDFCOM will discover that TMF has not been started and will prevent RDF from starting. In the case of RDF event 707, TMF was running when RDFCOM verified that TMF was started, but TMF was then stopped before the extractor was started. If the extractor detects that TMF is not started, the extractor aborts itself, and the monitor aborts the receiver and itself.

Recovery  Start TMF before trying to start RDF.

Cause  An internal error has been detected in RDFCOM.

Effect  RDFCOM aborts.

Recovery  This is an internal error. Contact your service provider.

Cause  An RDF process has successfully changed the logfile to the specified EMS Event Collector.

Effect  Messages are now logged to the new collector.

Recovery  Informational message only; no corrective action is needed.

Cause  An RDF process tried to obtain audit trail information from the TMF management process pair (TMP) on the primary system, but the TMP was not accessible. The probable cause is that TMF is not currently running. RDF requires that TMF be up and running on the primary and all backup nodes.

Effect  The RDF process abends.

Recovery  Start TMF on the affected node.

Cause  The updater failed to obtain process information about itself. This is a fatal error.

Effect  The updater process abends.

Recovery  This is an internal error. Contact your service provider.

Cause  The process encountered an error while attempting to create an RDF process. The error fields reported in the message are the upper and lower bytes of the status returned by the NEWPROCESS system procedure followed by the file-name of the program that was to be run.

Effect  The process is not started, and RDF shuts down.

Recovery  Consult the description of the NEWPROCESS procedure errors in the Guardian Procedure Errors and Messages Manual to determine the cause of the failure. Once the underlying cause is corrected, RDF can be restarted.

Cause  The primary process of an RDF NonStop process pair encountered an error while attempting to create its backup process. The error fields reported in the message are the upper and lower bytes of the status returned by the NEWPROCESS system procedure followed by the file-name of the program that was to be run.

This error will occur if one or more parameters in the configuration file are incorrect, if the required processor is not running, or if there are insufficient resources.

Effect  The backup process is not started. The primary continues to run, but will be vulnerable to a CPU failure. The primary will try to create its backup repeatedly until it succeeds.

Recovery  Consult the description of the NEWPROCESS procedure errors in the Guardian Procedure Errors and Messages Manual to determine the cause of the failure. Once the underlying cause is corrected, the backup process can be created.

Cause  A call to the checkpoint procedure failed, and the backup process of a process pair is still running. The message includes the number of the file-system error that was encountered when the primary process was trying to communicate with the backup process.

Effect  The backup process is stopped, and a new one is created after about 15 seconds.

Recovery  Informational message only; no corrective action is needed. Consult the description of the NEWPROCESS procedure errors in the Guardian Procedure Errors and Messages Manual to determine the cause of the failure. If possible, correct the underlying cause to avoid its reoccurrence.

Cause  The primary process of a NonStop process pair has stopped. This probably was the result of an operator inadvertently issuing a STOP command from TACL.

Effect  The backup process takes over, but not in fault-tolerant mode, until the primary process can be re-created.

Recovery  Informational message only; no corrective action is needed.

Cause  The primary process of a process pair has abended.

Effect  The backup process takes over, but not in fault-tolerant mode, until the primary process can be re-created.

Recovery  Scan the EMS event log to determine why the process abended. An INSPECT SAVEABEND file should have been created in the volume and subvolume where you placed the RDF software. You should save that file for problem resolution by your service provider.

Cause  The primary CPU of a process pair has stopped.

Effect  The backup process takes over, but not in fault-tolerant mode. The primary process will be re-created after its CPU is reloaded.

Recovery  Reload the downed processor.

Cause  The original backup process of a process pair has successfully created a backup process in the configured primary processor and has successfully switched processing to that process.

Effect  The process pair is switching primary and backup roles so that the primary process is now running in the CPU configured as the primary processor.

Recovery  Informational message only; no corrective action is needed.

Cause  A CHECKPOINT call from the primary process of a process pair to its backup process failed because of a parameter error. This message indicates a programming problem within RDF. The message includes the status word returned by the CHECKPOINT procedure.

Effect  The backup process is stopped, and a new one is created after about 15 seconds.

Recovery  Informational message only; no corrective action is needed. You should, however, contact your service provider and explain that this error occurred.

Cause  The extractor detected an error in block sequence numbers in the TMF audit trail. The sequence numbers show that a single block is missing.

Effect  This is only a warning. Normal processing continues. It is possible, however, that the backup database is no longer consistent with the primary database.

Recovery  Informational message only; no corrective action is needed. Tell your database administrator, however, that this error occurred. The database administrator should consider checking the synchronization of the primary and backup databases.

Cause  The extractor detected an error in block sequence numbers in the TMF audit trail. The sequence numbers show that multiple blocks are missing.

Effect  This is only a warning. Normal processing continues. It is possible, however, that the backup database is no longer consistent with the primary database.

Recovery  Informational message only; no corrective action is needed. Tell your database administrator, however, that this error occurred. The database administrator should consider checking the synchronization of the primary and backup databases.

Cause  The extractor has requested that the specified audit trail file be restored.

Effect  The extractor waits until the audit trail file is restored.

Recovery  If you are dumping audit trails to tape and you have already mounted the correct tape, then this an informational message. If you have not mounted the tape, check the EMS log to see what tape the TMF product requires and mount that tape.

Cause  The extractor encountered an irrecoverable error at the designated relative byte address (rba) in the designated TMF audit trail file. This message indicates an internal RDF or TMF error.

Effect  This is a catastrophic error; the extractor abends, and RDF stops.

Recovery  Because this message indicates a system error, you should preserve the indicated audit trail file for further analysis by your service provider.

Cause  The purger has determined that all updaters have processed through to the end of the image trail and the RDF takeover operation has completed.

Effect  Normal purger shutdown processing continues. When the purger stops, the takeover operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  The purger has determined that at least one updater process terminated prematurely, without processing through to the end of the image trail. The premature updater shutdown may have resulted from a double CPU failure or a STOP command entered manually from TACL. Because the updater might not have processed all image audit, the RDF TAKEOVER operation cannot be considered complete. Scan the EMS event log for RDF message 726: this message identifies the updater process that did not complete TAKEOVER processing.

Effect  Normal purger shutdown processing continues.

Recovery  Restart the takeover operation by issuing an RDFCOM TAKEOVER command.

Cause  The purger has determined that the updater process indicated in this message did not complete its RDF takeover processing. That updater may have stopped prematurely because of a double CPU failure or a STOP command entered manually from TACL.

Effect  The updater responsible for the volume named in the message did not complete RDF takeover processing.

Recovery  When you have determined why the updater stopped prematurely and have corrected the problem, reissue the RDFCOM TAKEOVER command.

Cause  The specified file should exist on disk, but it does not.

Effect  The extractor abends.

Recovery  This is an internal error. Contact your service provider.

Cause  The CPU of the backup process of a process pair failed.

Effect  The primary process continues to run, but not in fault-tolerant mode.

Recovery  Reload the downed processor. The backup process is re-created when the processor is reloaded.

Cause  An attempt to alter the priority of an RDF process to the indicated priority failed.

Effect  The process continues to run at its current priority.

Recovery  Informational message only; no corrective action is needed. Reissue the ALTER command.

Cause  The operator successfully changed the priority of an RDF process to priority.

Effect  The process runs at the new priority.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a START RDF command.

Effect  The RDF monitor process is running and starting up the other RDF processes.

Recovery  Informational message only; no corrective action is needed.

Cause  An updater process encountered an error while attempting to create an exception file. The message includes the file-system error number and the name of the exception file that the updater was trying to create.

Effect  This is a catastrophic error; the updater abends, and RDF stops.

Recovery  Determine the cause of the error, correct the condition, and then restart RDF.

Cause  The updater has found a Stop-RDF-Updater record in the image trail. This special record is generated in the TMF audit trail on the primary node when an SQL DDL operation WITH SHARED ACCESS involving the specified file has completed. Each updater will stop when it reaches this record in the image trail.

Effect  The updaters stop.

Recovery  When all updaters have stopped, you must perform the same SQL DDL operation on the RDF backup node that was originally done on the primary node. When this operation has been performed, start the updaters again with the START UPDATE command.

	NOTE: You must not start the updaters until you have performed the DDL operation. Otherwise, you will corrupt your database on the RDF backup node.

Cause  An RDF process received a message that does not apply to it. This message is a warning that indicates a possible problem in the configuration file, a programming problem within RDF, or that a process outside of RDF tried to communicate with an RDF process. Whenever possible, this message includes the offending process name or process id as well as the program file name.

Effect  The message type is reported with no other effect.

Recovery  Informational message only; no corrective action is needed. To see if the message resulted from an incorrect configuration file, examine the configuration file and verify that all necessary parameters have been specified correctly. Report this error to your service provider.

Cause  The purger logs this message after successful completion of an RDF takeover operation. If all data volumes on the primary system are configured to the MAT, then the reported position is the end of the last record received from the extractor. If any data volumes on the primary system are configured to auxiliary audit trails, then the reported position is the end of the last commit or abort record received from the extractor for which no data from any auxiliary audit trail is missing.

Effect  The MAT position is used for two purposes:

Recovery  Informational message only; no corrective action is needed.

Cause  The updater could not obtain information about the specified file. Before an updater can apply audit records to a file, it must obtain information about the file. The probable reason why information could not be obtained is that the file has not been created yet.

Effect  The updater delays for 30 seconds and then tries to obtain the information again.

Recovery  If the specified file is an SQL table, then you must create that table on the remote node. If the specified file is an Enscribe file, the file may not exist on the RDF backup node yet. If you have just created the file on the primary node, then the updater has probably sent the creation audit record to the disk process, but the file has not yet been created. In this case, this message is informational; when the file is created, the updater will be able to obtain the information it needs and continue processing.

Cause  When the extractor is starting or restarting, it sends a request to the receiver to obtain its starting position in the TMF audit trail. The extractor issues event 737, indicating that the extractor is attempting to become synchronized with the receiver by requesting this starting position.

Effect  The extractor attempts to become synchronized with the receiver.

Recovery  Informational message only; no corrective action is needed.

Cause  This message indicates that te receiver has sent the extractor a starting position in the TMF audit trail, and the extractor has thereby become synchronized with the receiver.

Effect  The extractor is synchronized with the receiver.

Recovery  Informational message only; no corrective action is needed.

Cause  An updater was unable to create a file on its UPDATEVOLUME disk. The message includes both the file-system error number and the name of the file the updater attempted to create.

Effect  Consult Table 5-3 of the NonStop RDF/IMP, IMPX, and ZLT System Management Manual to determine the effect of this error.

Recovery  Consult Table 5-3 of the NonStop RDF/IMP, IMPX, and ZLT System Management Manual to determine the appropriate recovery actions.

Cause  This warning message is issued when a create operation for the primary partition of a partitioned file must map one or more of the file’s secondary partitions to a volume that does not match any of the volumes protected by RDF on the primary node. This message is also issued when the creation of a file with alternate keys is attempted and the corresponding alternate key file does not match any of the volumes protected by RDF on the primary node.

Effect  The create operation fails and is skipped.

Recovery  For partitioned files and files with alternate keys, if any partition or alternate key file is on a volume protected by RDF, then all partitions and alternate key files must be on volumes protected by RDF. Either the file must be redefined on the primary node, or the other volume must be made protected by RDF. In the latter case, the backup file must then be resynchronized with the primary file.

Cause  The receiver has received a message from the extractor that is out of order. When this event occurs, the extractor automatically reestablishes synchronization with the receiver. If the extractor has several outstanding requests to the receiver and the first is found to be out of order, the receiver rejects each subsequent request with this same error. When the extractor reestablishes synchronization, normal processing resumes.

Effect  The receiver directs the extractor to reestablish synchronization.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor encountered an error in audit processing.

Effect  The extractor abends, thereby stopping the other RDF processes.

Recovery  Save the SAVEABEND file and the audit trail file, and consult your service provider. You must reinitialize RDF.

Cause  A fatal error occurred in RDF.

Effect  RDF stops. Error 745 will probably follow this error.

Recovery  Restart RDF and contact your service provider.

Cause  The updater was previously delayed in obtaining information about the specified file (see RDF error 736). The information has now been obtained.

Effect  The updater continues processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor encountered the specified error while attempting to convert an audit record from one version to another.

Effect  The extractor abends, thereby stopping the other RDF processes.

Recovery  This is an internal error. Contact your service provider.

Cause  A fatal error occurred during RDF subsystem initialization.

Effect  RDF stops. Error 743 should follow this message.

Recovery  Consult the EMS event log for any preceding errors that might indicate the source of the problem. If it is possible to correct the underlying problem, then RDF can be restarted.

Cause  Either TMF has not been started on the remote node, or the volume associated with this updater on the remote node has not been added as a datavol in the TMF configuration. TMF must be started on the remote node, and the volume associated with this updater on the remote node must be added as a datavol to this remote TMF configuration.

Effect  The updater will not start.

Recovery  Start TMF on the remote node and add the associated volume as a data volume in the TMF configuration. Additionally, you should start the volume for transaction processing.

Cause  The extractor detected an audit record of an unknown version.

Effect  The extractor process abends.

Recovery  This is an internal error. Contact your service provider.

Cause  The extractor detected an audit record generated by an unknown version of TMF.

Effect  The extractor abends.

Recovery  Reinitialize RDF. You might also need to resynchronize the primary and backup databases.

Cause  All RDF processes rely upon the ability to post timers by calling SIGNALTIMEOUT and take action when those timers expire. This message indicates that a call to SIGNALTIMEOUT failed because there were insufficient time list elements (TLEs) available.

Effect  The process continues to run, but recovery is required.

Recovery  Issue a STOP RDF command immediately. Then investigate why there is a shortage of TLEs in the CPU of the RDF process that could not obtain one. If you want to start RDF again while conducting this investigation, you should alter the RDF configuration of the process that could not obtain the TLE, specifying a different set of CPUs for that process.

Cause  A call to the CHECKOPEN procedure failed, and the backup process of a process pair is still running. The message includes the file-system error number encountered when the primary process tried to communicate with the backup process and the name of the file associated with the error.

Effect  The backup process is stopped, and a new one is created after about 15 seconds.

Recovery  Informational message only; no corrective action is needed. Consult the description of the CHECKPOINT procedure errors in the Guardian Procedure Calls Reference Manual to determine the cause of the failure. If possible, correct the underlying cause to avoid its reoccurrence.

Cause  The extractor detected that the relative block number (RBN) of a block of audit data in the TMF audit trail is out of sequence.

Effect  This is a catastrophic error; the extractor abends, and RDF stops.

Recovery  This message indicates an internal RDF or TMF error. You must resynchronize the primary and backup databases. Save the audit trail file, and report this error to your service provider.

Cause  The extractor detected a block of audit data that is repeated in the TMF audit trail.

Effect  The block is ignored and processing continues. It is possible, however, that the backup database is no longer consistent with the primary database.

Recovery  This message indicates an internal RDF or TMF error. Save the audit trail file, and report this error to your service provider.

Cause  The primary node processes have determined that the communications lines have been restored. The extractor is now able to communicate with the receiver.

Effect  Processing continues from the point at which the network failed.

Recovery  Informational message only; no corrective action is needed.

Cause  The primary process of a process pair stopped after creating its backup process, but before completing the backup initialization.

Effect  This is a catastrophic error; the process abends, and RDF stops.

Recovery  Restart the RDF product and report the error to your service provider.

Cause  The extractor encountered an audit record associated with a format 2 file specified in the event and the backup system is not format-2 aware.

Effect  The extractor skips the audit record and does not send it to the receiver.

Recovery  If you intend to replicate this file you must first update the backup node’s operating system to one that supports format-2 files and then resynchronize this file.

Cause  The purger has detected that all the updaters have shut down following a successful stop-update-to-time operation.

Effect  The database is now in a consistent state.

Recovery  Informational message only; no corrective action is needed.

Cause  A process is abending.

Effect  A SAVEABEND file is created, a stack trace is logged, and the process (and its backup process, if any) abends. RDF stops.

Recovery  Restart the RDF product and report the error to your service provider.

Cause  An updater has encountered an audit record associated with an Enscribe CREATE operation, an increase of MAXEXTENTS for an Enscribe file, or a PURGEDATA operation for an Enscribe file, and the file on the primary system has secondary partitions that are located on different systems in the network.

Effect  The updater skips this record. Note that if the record is associated with an Enscribe CREATE operation, no partitions of the file are created on the backup system. Therefore, if the updater subsequently encounters another audit record associated with that file, the updater pauses its processing until that file is created. Alternatively, if the record was associated with a PURGEDATA operation or an increase of MAXEXTENTS, the operation is not replicated on the backup system.

Recovery  If the record was associated with an Enscribe CREATE operation, you must manually create the file on the backup system. If the record was associated with a PURGEDATA operation or an increase of MAXEXTENTS, you must issue a STOP UPDATE command and then perform the operation manually on the backup system.

Cause  The purger has determined that the specified image file is no longer needed and has purged it.

Effect  The specified file is purged.

Recovery  Informational message only; no corrective action is needed.

Cause  The backup process of a process pair has been stopped. This probably was the result of an operator inadvertently issuing a STOP command from TACL.

Effect  A new backup will be created.

Recovery  Informational message only; no corrective action is needed.

Cause  An RDF process has determined that the existing context file belongs to an older version of RDF.

Effect  You cannot start the RDF subsystem.

Recovery  Purge all existing context and configuration files on the primary and backup systems. Then initialize the RDF subsystem.

Cause  The process reporting the error has determined that it has been installed with the wrong operating system.

Effect  The process abends.

Recovery  Install the version of the RDF product that is compatible with the installed release of the operating system.

Cause  The RDF monitor process detected an internal inconsistency regarding RDF’s understanding of an SQL shared access operation.

Effect  The monitor abends.

Recovery  This is an internal error. Contact your service provider.

Cause  The updater process has sent an audit record to the disk process that is the wrong version.

Effect  The updater abends.

Recovery  This is an internal error. Contact your service provider.

Cause  The first part of phase one of an online database synchronization operation is complete.

Effect  The extractor continues with the second part of phase one.

Recovery  Informational message only; no corrective action is needed.

Cause  The second part of phase one of an online database synchronization operation is complete.

Effect  The extractor continues with the third part of phase one.

Recovery  Informational message only; no corrective action is needed.

Cause  The third part of phase one of an online database synchronization operation is complete.

Effect  The extractor continues with phase two.

Recovery  Informational message only; no corrective action is needed.

Cause  The reporting process has filled the current image file and is ready to begin writing to the next file in the sequence. This next file is named in filename .

Effect  The reporting process rolls over to the the specified image file.

Recovery  Informational message only; no corrective action is needed.

Cause  The RDFNET process has successfully completed its initialization.

Effect  The process starts its task of performing synchronized transactions on each of the primary nodes in the RDF network of RDF primary systems.

Recovery  Informational message only; no corrective action is needed.

Cause  The receiver has successfully completed its initialization.

Effect  The receiver is prepared to receive data from the extractor.

Recovery  Informational message only; no corrective action is needed.

Cause  The receiver determined that TMF is not started on the RDF backup system.

Effect  The receiver abends.

Recovery  Start TMF on the backup system and then restart RDF.

Cause  The updater has successfully completed its initialization. The message includes the audited volume name and its corresponding update volume name.

Effect  The updater is prepared to apply updates to the database on the backup node.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor has successfully completed its initialization.

Effect  The extractor will begin reading TMF audit data and transmitting it to the receiver.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor has encountered a restart condition during an online database synchronization operation, and the current audit trail restart position sent by the receiver may lead to loss of data.

Effect  The extractor revises its restart location to an earlier point in the audit trail, thereby guaranteeing that no data will be lost.

Recovery  Informational message only; no corrective action is needed.

Cause  The receiver has terminated normal processing as the result of a STOP TMF, STOP RDF, or TAKEOVER command.

Effect  Normal RDF shutdown processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor has received a STOP SYNCH message, but is not currently involved in an online synchronization operation.

Effect  The extractor abends.

Recovery  This is an internal error. If no database synchronization operation was in progress, you must restart RDF. If a database synchronization operation was in progress, you must restart the entire operation from the beginning.

Cause  The updater has terminated normal processing as the result of a STOP TMF, STOP RDF, STOP UPDATE, or TAKEOVER command.

Effect  Normal RDF shutdown processing continues. If this message is issued as the result of a STOP UPDATE command, RDF will continue processing with updating disabled.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor has terminated normal processing as the result of a STOP TMF or STOP RDF command.

Effect  Normal RDF shutdown processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  An updater is unable to apply image records for some transactions because a TAKEOVER command was executed and the commit, abort, or data records for the transactions were not sent to the backup node. The message includes the name of the exception file containing information about the image records that were not applied.

Effect  If all the records for a transaction are not received on the backup node, the transaction is treated as if it aborted. For every image record that is not applied to the backup database, an exception record is written to the designated exception file.

Recovery  This is a normal occurrence during TAKEOVER processing. The system manager can use RDFSNOOP to list the image records that were not applied to the backup database. The backup database will be consistent after the TAKEOVER operation, but some transactions that might have committed on the primary node might not be applied to the backup database.

Cause  The extractor’s transaction status table that is used for online synchronization has overflowed. This means that more than 650,000 transactions were started during the first TMP control point interval following the RDFCOM STOP SYNCH command, and those transactions are still active.

Effect  The extractor abends.

Recovery  You must initialize RDF to a new database synchronization timestamp and then restart the entire operation from the beginning.

Cause  Phase two of a database synchronization operation involving the process that generated this message is complete.

Effect  If the process is the extractor, then all operations performed by the extractor for the database synchronization are complete, although the updaters might not have completed their work on the backup system. If the process is an updater, then the backup database is synchronized for the volume protected by the particular updater.

Recovery  Informational message only; no corrective action is needed.

Cause  The monitor or extractor process could not open the remote receiver process after a communications failure.

Effect  If the monitor or extractor process receives a file-system error 14 (process does not exist), RDF will shut down on the primary node.

Recovery  If RDF was stopped on the remote node by a STOP RDF command while the communications lines were down, simply restart RDF by issuing a START RDF command.

Cause  The operator issued an RDFCOM STOP UPDATE, TIMESTAMP command at the primary node.

Effect  Each updater applies only audit data associated with transactions that committed prior to the specified timestamp.

Recovery  Informational message only; no corrective action is needed.

Cause  A STOP UPDATE, TIMESTAMP timestamp command has been issued and the updater has completed its redo pass.

Effect  The updater is ready to commence its undo pass.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor has received notification of a STOP SYNCH command. This event represents the start of part 1 of phase one of the extractor’s work in an online database synchronization operation.

Effect  When the extractor encounters the next TMP control point record in the MAT, it enters phase one, part 1 processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The receiver or an updater has encountered the indicated error while attempting to position within an image file.

Effect  The process abends.

Recovery  Correct the problem that caused the error and then restart RDF.

Cause  An RDF process received an error from the ALLOCATESEGMENT system procedure.

Effect  This is a catastrophic error; the process abends, and RDF stops.

Recovery  Consult the description of the ALLOCATESEGMENT procedure in the Guardian Procedure Calls Reference Manual to determine the cause of the failure. Once the underlying cause is corrected, you can restart RDF.

Cause  The primary process of an RDF process pair received an error from the CHECKALLOCATESEGMENT system procedure.

Effect  This error is not fatal; processing continues. The backup process is stopped and then re-created later.

Recovery  Consult the description of the CHECKALLOCATESEGMENT procedure errors in the Guardian Procedure Errors and Messages Manual to determine the cause of the failure. Some corrective action might be required for the backup process to be re-created without repeated failures. The most likely cause is insufficient space available for swapping on the swap volume.

Cause  The backup process of a process pair was created in the specified processor.

Effect  The primary process will now run in fault-tolerant mode.

Recovery  Informational message only; no corrective action is needed.

Cause  The receiver or purger could not create the specified file due to the specified file-system error.

Effect  This is a catastrophic error; the process abends and RDF stops.

Recovery  Correct the underlying condition, and then restart RDF.

Cause  The purger process could not purge an image file that is no longer needed. The message includes the file-system error number and the name of the image file.

Effect  This is only a warning. The purger will retry the purge operation.

Recovery  Correct the underlying condition, and the purger will purge the image file in the next purge pass.

	NOTE: Under some circumstances, after the configured backup receiver process re-creates its primary and switches to that primary, it continues to hold an image file open. When the receiver no longer needs this image file and the purger tries to purge it, the purger logs RDF error 797 accompanied by file-system error 12. Whenever this error is logged, you should perform a FUP LISTOPENS filename operation to identify the opener of the file. If the backup receiver process is the opener, you can manually stop that process with a TACL STOP command; this clears the problem and the next time the receiver stops or finishes with an image file, this file will be purged.

Cause  An RDF process encountered the designated file-system error while attempting to open the specified image file.

Effect  The process abends, and RDF stops. The exception to this is an error 12 (file in use) issued when either the receiver or purger attempts to open the file. In that case, the process posts a short delay and then retries the operation, and it repeats these two steps unitl successful.

Recovery  For an error 12 associated with an image trail file, perform a FUP LISTOPENS on the file to deteremine which process currently has the designated file open. If the process that has the file open is not an RDF process, then stop that process. In all other cases, restart RDF.

Cause  An RDF process encountered an error while attempting to read an image file.

Effect  This is a catastrophic error; the process abends, and RDF stops. The message includes the error number returned by the READ system procedure, followed by the name of the file that contained the error.

Recovery  Restart RDF. If the problem persists, you might need to reinitialize RDF. Preserve the designated image file and report the problem to your service provider.

Cause  The receiver process encountered a file-system error while attempting to write to the specified file.

Effect  The message includes the error number returned by the WRITE system procedure followed by the file name. For error 43 (unable to obtain disk space for extent), the receiver retries the write operation. All other errors are fatal; the receiver abends and RDF stops.

Recovery  The only recovery from an error 43 condition is to free some disk space. You can do that by purging unused files, by using a FUP DEALLOCATE operation to deallocate unused extents (not for image files), or by using DCOM to move extents so that small free areas are combined into a larger free space.

Cause  An RDF process has detected an internal inconsistency.

Effect  This error should never occur and is fatal to RDF.

Recovery  Restart RDF. If the problem persists, reinitialize RDF and report the error to your service provider.

Cause  An RDF process has encountered a bad header in an image file.

Effect  A bad header indicates that the image file has been corrupted. This is a catastrophic error; the process abends, and RDF stops.

Recovery  Restart RDF. If the problem persists, reinitialize RDF and report the error to your service provider.

Cause  The RDFNET process has encountered the specified error on the specified file.

Effect  The RDFNET process aborts its current transaction, posts a timer, and waits for that timer to expire before attempting a new transaction.

Recovery  Determine the cause of the error and then take appropriate corrective action.

Cause  The RDFNET process has encountered the specified error on the specified file.

Effect  The RDFNET process aborts its current transaction, posts a timer, and waits for that timer to expire before attempting a new transaction.

Recovery  Determine the cause of the error and then take appropriate corrective action.

Cause  The RDFNET process has encountered the specified error on the specified file.

Effect  The RDFNET process aborts its current transaction, posts a timer, and waits for that timer to expire before attempting a new transaction.

Recovery  Determine the cause of the error and then take appropriate corrective action.

Cause  The RDFNET process has terminated normal processing as the result of a STOP TMF or STOP RDF command."

Effect  Normal RDF shutdown processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a START UPDATE command.

Effect  RDF starts updating the backup database.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a STOP UPDATE command.

Effect  RDF stops updating the backup database.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a STOP RDF command.

Effect  The RDF process stops normally.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a TMFCOM STOP TMF command at the primary node.

Effect  The RDF process stops normally.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a TAKEOVER command.

Effect  RDF starts a TAKEOVER operation.

Recovery  Informational message only; no corrective action is needed.

Cause  The updater encountered a file-system error while attempting to communicate with the receiver or purger. The file-system error number and the name of the receiver or purger are included in the message.

Effect  This is a catastrophic error; the updater abends, and RDF stops.

Recovery  Determine the cause of the error. If the receiver or purger did not abend, correct the condition, then restart RDF.

Cause  This message is reported by updater processes when the number of concurrent file opens exceeds the capacity of the table in which the updater maintains information about file opens.

Effect  The updater will close idle files (if any) and continue. If there are no idle files, then the updater will close all files and establish a restart point from which processing can continue. In the latter case, there will be a performance degradation.

Recovery  Informational message only; no corrective action is needed. If the condition persists, however, your database administrator should consider moving some of the files protected by TMF on the primary node volume to another volume, and adding another updater to back up the new volume. If you do that, you must synchronize the affected volumes on the primary and backup nodes.

Cause  The primary process has stopped for some reason, perhaps a cpu failure.

Effect  The backup process of the process pair (in the designated cpu) has taken over.

Recovery  Informational message only; no corrective action is needed. You should, however, determine why the primary process stopped, and take corrective action if necessary.

Cause  A new primary process has been created by the backup process, and the backup process has switched control to that primary process.

Effect  The primary process of the process pair (in the designated cpu) has taken over.

Recovery  Informational message only; no corrective action is needed.

Cause  The receiver or purger process encountered an error while attempting to perform a setmode operation on the specified file.

Effect  The process abends.

Recovery  Correct the problem that led to the error and then restart RDF.

Cause  The operator issued a STOP UPDATE command, and the updater is stopping normally. This message is issued only by updater processes.

Effect  The updater stops.

Recovery  Informational message only; no corrective action is needed.

Cause  While working on an online database synchronization operation, the extractor encountered an RDF-Stop-Updaters audit record. This indicates that an SQL DDL operation with SHARED ACCESS altered the database on the primary system,

Effect  The SQL DDL operation has altered the primary database from what was being duplicated to the backup system, thereby invalidating the online synchronization operation. The extractor abends.

Recovery  You must initialize RDF to a new database synchronization timestamp and then restart the entire operation from the beginning.

Cause  The extractor has stopped unexpectedly.

Effect  This message is issued by the RDF monitor. The monitor sends an abort request to all remaining RDF processes to stop RDF.

Recovery  A subsequent warm start of RDF might be possible, but the success of the restart depends on the nature of the failure that caused the original process to stop.

Cause  The receiver has stopped unexpectedly.

Effect  This message is issued by the RDF monitor. The monitor sends an abort request to all remaining RDF processes to stop RDF.

Recovery  A subsequent warm start of RDF might be possible, but the success of the restart depends on the nature of the failure that caused the original process to stop.

Cause  An updater has stopped unexpectedly.

Effect  This message is issued by the RDF monitor. The monitor sends an abort request to all remaining RDF processes to stop RDF.

Recovery  A subsequent warm start of RDF will probably be successful, but the success of the restart depends on the nature of the failure that caused the original updater process to stop.

Cause  An RDF process is being shut down by the RDF monitor following the premature loss of another RDF process.

Effect  The process stops normally.

Recovery  Scan the EMS event log to determine the original cause of the failure. It might be possible to restart RDF.

Cause  This network transaction was committed in the audit trail on the primary system after the first network transaction marked for undo. It can be kept because it committed prior to the first network transaction marked for undo on a different node in the RDF network. Please note, however, that this transaction could still be undone during final checking for business consistency across all backup nodes.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The RDF monitor was unable to find an extractor configuration record when performing a START RDF command.

Effect  The START operation fails and RDF shuts down.

Recovery  Use the SET and ADD commands to create an extractor configuration record and then retry the START RDF command.

Cause  The RDF monitor was unable to find a receiver configuration record when executing a START RDF command.

Effect  The START operation fails and RDF shuts down.

Recovery  Use the SET and ADD commands to create a receiver configuration record and then retry the START RDF command.

Cause  The RDF monitor was unable to find an updater configuration record when performing a START RDF command.

Effect  The START operation fails and RDF shuts down.

Recovery  Use the SET and ADD commands to create one or more updater configuration records.

Cause  The RDF process is not compatible with the audit format being generated by TMF.

Effect  RDF stops.

Recovery  Restart RDF under the correct version of the operating system and/or TMF.

Cause  The primary process of a process pair has detected a problem in communicating with the backup process. An earlier message will have indicated the communications problem.

Effect  Because of the severity of the problem, the primary process attempts to stop the backup process. If the backup process stops, the primary process then attempts to create a new backup process.

Recovery  Informational message only; no corrective action is needed.

Cause  This message indicates that the monitor detected an RDF takeover operation was executed on the RDF backup system.

Effect  This is a catastrophic error and will cause RDF to abort.

Recovery  You must reinitialize the RDF subsystem and you might need to resynchronize your backup database with the primary database.

Cause  The RDF monitor is attempting to stop a process on the backup node but cannot do so because the communications lines are down.

Effect  If a STOP RDF command was being processed, the RDF monitor continues with the shutdown, and all processes on the primary node will stop. The backup processes will remain running.

Recovery  To stop the RDF processes on the backup node, you must run RDFCOM on the backup node and issue a second STOP RDF command. Once all the processes have stopped, RDF can be restarted when the network is restored.

Cause  An RDF process is terminating abnormally.

Effect  The equivalent of an INSPECT TRACE is written and the process abends.

Recovery  This message gives your service provider information about the state of a process that is terminating abnormally. You might be able to correct the underlying problem and restart RDF. Otherwise you must reinitialize RDF.

Cause  The RDFNET process obtained the specified error while attempting to open the specified file.

Effect  The RDFNET process restarts.

Recovery  Determine the underlying cause and take appropriate corrective action.

Cause  The extractor encountered an audit record that it did not recognize.

Effect  This is a fatal error; RDF shuts down.

Recovery  This message probably is the result of running on a primary node that has had an audit trail created for a version of TMF that RDF does not support. The message could also mean that the audit trail file was corrupted by some program other than TMF, or that an irrecoverable system error has occurred. In any event, you will have to reinitialize the TMF and RDF subsystems. Save the audit trail, and report this error to your service provider.

Cause  This message is issued by the purger process if it has to terminate the current purge pass for one of a variety of reasons. The reason codes see the internal conditions that may be of use to support and development personnel.

Effect  The purger terminates the current purge pass. A new purge pass is initiated after PURGETIME minutes.

Recovery  Informational message only; no corrective action is needed. Under normal conditions, this message should be logged infrequently. If the event appears regularly and if the purger stops purging files, it could be an indication of throughput problems between the extractor and receiver processes. If this message persists, and the purger has stopped purging old image files, and the extractor has not fallen behind, contact your service provider.

Cause  The operator issued one of the following commands: ALTER, INITIALIZE RDF, START RDF, START UPDATE, STOP RDF, STOP UPDATE, or TAKEOVER.

Effect  The RDF command is executed.

Recovery  Informational message only; no corrective action is needed.

Cause  TMF reports that the specified data volume is not enabled. This may be the result of an earlier failure and the volume is still recovering, or the user has disabled the volume in TMFCOM.

Effect  The updater is unable to apply updates to this volume until the volume is enabled. The updater retries the operation every minute until the volume is enabled.

Recovery  If the volume is recovering, the updater resumes processing once the volume becomes enabled. If the data volume has been manually disabled, you must enable it to allow the updater to resume operations.

Cause  An updater restart is performed under a variety of circumstances, such as a failure in the primary CPU of the updater, a failure in the primary CPU of the corresponding disk process, or various file errors. The reason for the updater restart can be determined from previous messages. During an updater restart, file-system errors 10, 11, and 71 are not reported by the updater because they probably represent database operations that have already been performed.

Effect  The updater restarts and continues processing.

Recovery  Perform any corrective actions suggested by the preceding messages in the RDF message log (actions such as reloading the appropriate CPU, or correcting the underlying file error condition).

Cause  The RDFNET process has terminated unexpectedly.

Effect  This message is issued by the RDF monitor. The monitor sends an abort message to all remaining RDF processes to stop RDF.

Recovery  Determine the reason why the RDFNET process stopped, correct the problem, and then restart RDF. If the problem persists, contact your service provider.

Cause  The extractor was unable to find the designated audit trail file. Usually this occurs because TMF purged the audit trail file while RDF was stopped. When RDF is running, it prevents TMF from purging audit trail files until the extractor has read them, even if the extractor is running far behind TMF (the extractor has a large RTD value) and TMF has performed several rollovers. Use the STATUS RDF command to display the extractor’s current RTD value.

Effect  The extractor tries to open the audit trail file indefinitely unless an irrecoverable error occurs on the file.

Recovery  Restore the audit trail file from tape by using SNOOP RESTOREAUDIT. If copies of the audit trail have not been maintained, you will have to reinitialize RDF and resynchronize the primary and backup databases.

Cause  A user-specified process, identified by procname, is already in use when the monitor tries to start an RDF process with this same name.

Effect  The monitor shuts down RDF in an orderly manner.

Recovery  If you can stop the process and give it another name, you can then simply restart RDF; otherwise, you will have to alter the name of the RDF process so that the name does not conflict with other process names.

Cause  The monitor was unable to send shutdown messages to an updater because of the indicated file-system error.

Effect  The monitor terminates the attempt to send STOP UPDATE messages to any other updaters. It then sends an ABORT RDF message to all the other RDF processes and waits for them to stop.

Recovery  If any updaters have not shutdown after the monitor has sent ABORT RDF messages, then you may have to terminate the surviving updaters manually using a TACL STOP command.

Cause  You issued a START RDF command, but the monitor detected that RDF has already processed a TAKEOVER command.

Effect  The START RDF command fails.

Recovery  The backup database is consistent and ready for use as a backup contingency database. Perform the rest of your installation-specific operations for switching to the backup node (for example, rerouting communications and starting applications). If you performed the takeover operation inadvertently, you will need to issue an INITIALIZE RDF command and resynchronize the databases.

Cause  The receiver has received audit from the extractor that does not match the version of audit that the receiver expects.

Effect  The monitor terminates the attempt to send STOP UPDATE messages to any other updaters. It then sends an ABORT RDF message to all the other RDF processes and waits for them to stop.

Recovery  If any updaters have not shut down after the monitor has sent the ABORT RDF messages, then you might have to stop the surviving updaters manually using TACL STOP commands.

Cause  The updater that generated this message has completed phase one of the online synchronization operation for its volume on the backup system.

Effect  The updater starts phase two of the online synchronization operation.

Recovery  Informational message only; no corrective action is needed.

Cause  The updater that generated this message has completed its synchronization work for RDF initialization to an initialization timestamp.

Effect  The updater resumes its normal processing.

Recovery  Informational message only; no corrective action is needed.

Cause  When the updater completed its RDF Takeover operation, it had not yet completed its role in an online database synchronization.

Effect  The database might not be in a consistent state.

Recovery  There is no recovery. If you lose your primary system during an online database synchronization, the backup database has not yet been synchronized, and its data therefore might not be consistent.

Cause  When the updater completed its RDF Takeover operation, it had not yet completed its role in an INITIALIZE RDF...INITTIME operation.

Effect  The database might not be in a consistent state.

Recovery  There is no recovery. If you lose your primary system while the updaters are trying to catch up from an INITIALIZE RDF...INITTIME operation, the backup database has not yet been synchronized, and the data in it therefore might not be consistent.

Cause  The extractor has sent the maximum number of messages to the receiver and has not received any replies for at least five minutes.

Effect  The extractor cannot proceed any further.

Recovery  This is not an RDF problem. You should investigate your Expand network and take corrective action. If necessary, you can issue a STOP RDF command on both the primary and backup systems to stop the RDF processes in an orderly fashion.

Cause  TMF was stopped during an RDF online database synchronization operation, before the extractor had completed its phase one processing.

Effect  The extractor abends because the database synchronization operation can no longer succeed.

Recovery  You must reinitialize the RDF product and restart the online database synchronization operation.

Cause  TMF was stopped during an RDF online database synchronization operation, after the extractor had completed its phase one, part 1 processing.

Effect  The extractor completes phases one and two of its database synchronization processing and then shuts down in response to the TMF shutdown audit record.

Recovery  Informational message only; no corrective action is needed. When you restart the RDF product, ensure that the duplicate database tables and files have been moved to the backup system before you start the updaters.

Cause  The RDF product cannot support an environment where transactions involving the RDF primary system have originated on more than 48 different nodes. The receiver has encountered transactions that have originated on more than 48 nodes.

Effect  The receiver abends and the RDF system aborts.

Recovery  Recovery is not possible. Contact your service provider.

Cause  In determining what transactions need to be undone, the internal table of transactions has become filled.

Effect  RDF aborts.

Recovery  Contact your service provider for assistance with recovering from this situation.

Cause  While attempting to write the list of transactions that need to be undone to the ZTXUNDO file, that file could not be opened.

Effect  RDF aborts.

Recovery  If the operation involves an RDF takeover, take corrective action to enable the file to be opened and then reissue the TAKEOVER command. If the operation involves a stop-update-to-time operation, take corrective action to enable the file to be opened and then restart RDF. Note that if you still want to bring the backup database into a consistent state, you must issue a new STOP UPDATE <timestamp> command specifying a new timestamp.

Cause  The named RDF process has encountered an error condition that requires that its last transaction be aborted, but the transaction has already been aborted.

Effect  The process restarts and continues processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The purger process is ready to start the task of determining what image files it can purge.

Effect  The purger process purges any image trail files that are no longer required by RDF.

Recovery  Informational message only; no corrective action is needed.

Cause  The named RDF process has encountered an error when attempting to ends its current transaction.

Effect  The process aborts the current transaction, restarts and continues processing.

Recovery  Informational message only; no corrective action is needed.

Cause  A network takeover operation has completed but, for this particular node in the RDF network, there is no safe MAT position with which you can issue a File Recovery operation on your primary system should that node become available again.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The named RDF process has encountered the specified error while attempting to begin a new transaction.

Effect  The process either restarts or abends, depending on the error.

Recovery  Consult the description of BEGINTRANSACTION errors in the HP NonStop TMF Application Programmer’s Guide and take appropriate corrective action, if necessary.

Cause  The named RDF process has encountered the specified error while attempting to begin a new transaction.

Effect  The process abends and RDF aborts.

Recovery  Consult the description of BEGINTRANSACTION errors in the HP NonStop TMF Application Programmer’s Guide and take appropriate corrective action.

Cause  The extractor has fallen behind the configured extractor RTDWARNING threshold.

Effect  The extractor continues normal processing.

Recovery  Informational message only; no corrective action is needed. You should, however, try to determine why the extractor has fallen behind and take corrective action if necessary.

Cause  The specified updater has fallen behind the configured updater RTDWARNING threshold.

Effect  The updater continues normal processing.

Recovery  Informational message only; no corrective action is needed. You should, however, try to determine why the updater has fallen behind and take corrective action if necessary.

Cause  The RDF monitor process was unable to find the RDFNET configuration record when performing a START RDF command.

Effect  The START RDF operation fails and RDF shuts down.

Recovery  Restart RDF. If the record is still missing, you may have to reinitialize RDF.

Cause  The updater has encountered audit data associated with an SQL Shared Access DDL operation during undo processing for a stop-update-to-time operation.

Effect  The updater terminates immediately, and the stop-update-to-time operation is unsuccessful. This happened because you had a transaction on your primary system that started before your SQL Shared Access DDL operation and was still active after the operation.

Recovery  Restart the updaters. If you need to bring the backup database into a stable state, you must restart the stop-update-to-time operation specifying a time that is later than the previously-specified one.

Cause  The purger configuration record is not in the RDF configuration file.

Effect  The reporting process abends and RDF aborts.

Recovery  Restart RDF. If the problem persists, contact your service provider.

Cause  The purger process has terminated unexpectedly.

Effect  RDF aborts.

Recovery  Determine why the purger stopped, and then restart RDF. If the problem persists, contact your service provider.

Cause  The purger process has stopped.

Effect  RDF continues to shut down.

Recovery  Informational message only; no corrective action is needed.

Cause  The updater has terminated its redo pass and is now starting an undo pass to back out changes for audit data that was applied and must now be undone. If the updater is involved in an RDF takeover operation, it must undo changes previously made that were associated with transactions on the primary system whose final outcome is unknown. If the updater was involved in a stop-update-to-time operation, it must undo any changes previously made for transactions on the primary system that were not resolved when the shutdown timestamp was reached.

Effect  The updater commences undo processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The list of transactions that must be undone exceeds the maximum number of transactions that can be undone in a single undo pass.

Effect  The updater commences an additional undo pass.

Recovery  Informational message only; no corrective action is needed.

Cause  The purger could not find any image files in the image trail subvolume.

Effect  The purger abends, causing RDF to shut down.

Recovery  This is an internal error. Report this to your service provider.

Cause  An application has attempted an RDF lockstep operation but you have not configured your RDF subsystem for lockstep operations.

Effect  No lockstep operations can take place, and the lockstep gateway process abends.

Recovery  This is a warning. If you want lockstep operations, you must stop RDF and create a new RDF configuration with the RDF LOCKSTEPVOL attribute set.

Cause  The purger has started as the result of a START RDF command.

Effect  The purger commences normal processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified error occurred while attempting to allocate an extended segment.

Effect  The affected process abends and RDF aborts.

Recovery  Try to determine why the segment could not be allocated. Take appropriate corrective action and restart RDF.

Cause  The updater process has detected that the file format and the audit format do not agree. The event shows the file format and the audit format.

Effect  The process abends and RDF aborts.

Recovery  You must alter or recreate the file with the correct file format and tghen restart RDF.

Cause  This is an imagetrail safe position.

Effect  None.

Recovery  Informational message only; no corrective action is needed. This message is for historical purposes about a pending undo pass.

Cause  This is the first transaction that requires network undo with respect to local processing. Please note, however, that some transactions preceding it might also require undo for business consistency across all backup nodes. The transid is listed in internal format.

Effect  None.

Recovery  Informational message only; no corrective action is needed. This message is for historical purposes about a network undo pass.

Cause  The purger process has found a file in an image trail subvolume where the file name either does not contain a valid file sequence number or the filecode is not 720.

Effect  The purger process will not process any more files in that particular subvolume. The operation will be attempted again after PURGETIME minutes.

Recovery  The file being reported was not created by RDF and is not part ofn the RDF environment. It must be manually purged or renamed out of the image subvolume before the purger process can continue normal processing.

Cause  The specified file on the backup system does not have its audit attribute set.

Effect  The updater waits until the audit attribute is turned on.

Recovery  Turn on the audit attribute for the specified file.

Cause  A takeover command was issued while a stop-update-to-time operation was in progress.

Effect  The process abends and RDF aborts.

Recovery  You must reissue the Takeover command. That ensures the stop-update-to-time operation is aborted and the RDF subsystem is prepared to execute the takeover operation.

Cause  The named RDF process has encountered a restart condition and must abort its current transaction.

Effect  The process aborts the transaction and restarts.

Recovery  Informational message only; no corrective action is needed. You must examine the event log to determine why the process is restarting and if any recovery action is required.

Cause  The named RDF process' current transaction has been aborted by TMF and the disk process.

Effect  The process restarts.

Recovery  Informational message only; no corrective action is needed. You must examine the event log to determine why the process is restarting and if any recovery action is required.

Cause  The updater is configured to a virtual SMF disk that consists of more than 15 physical disks. This configuration is not supported by the RDF product.

Effect  The updater abends and the RDF subsystem shuts down.

Recovery  Reset your RDF configurations and/or your SMF configuration so that the updaters are either assigned to physical volumes, or your SMF virtual disks map to 15 or fewer physical volumes.

Cause  The RDFNET process encountered a condition that caused it to restart.

Effect  The process restarts and resumes normal processing.

Recovery  Examine preceding events for this process to try to determine why the process is restarting. Take corrective action if necessary.

Cause  The updater has reached the end of local takeover processing for an RDF network environment

Effect  The updater is ready to commence the next phase of undo processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The updater has reached the end of network undo takeover processing for an RDF network environment.

Effect  The updater is ready to complete takeover processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The updater has more transactions to undo that can be undone in a single network undo pass. Therefore it is starting an additional network undo pass.

Effect  The updater starts an additional network undo pass.

Recovery  Informational message only; no corrective action is needed.

Cause  A successful takeover has completed. If you need to bring your primary database back into synchronization with your backup database, use TMF File Recovery on your primary system with the specified MAT position.

Effect  None.

Recovery  Informational message only; no corrective action is needed. Consult TMF documentation for information about TMF File Recovery to an audit-trail position (TOMATPOSITION).

Cause  The purger has been attempting to build the network undo list, but is has either encountered a network error or it has been waiting too long for information it needs.

Effect  The purger begins another attempt to build the list.

Recovery  Informational message only; no corrective action is needed. You should examine the event log to see if the purger has reported a network error and take corrective action if required. If no errors have been reported, then the purger is waiting for another purger in the RDF network to complete work. If this is the case, you have no recovery action. The local purger will retry until the remote purger has completed the required work.

Cause  The purger is ready to try to build the network undo list. This event indicates that this is the purger's first attempt or it is about to retry the operation because of a previous failure.

Effect  The purger begins another attempt to build the list.

Recovery  Informational message only; no corrective action is needed.

Cause  This is the first transaction that requires network undo with respect to business consistency across all backup nodes. All transactions that committed after this transaction are undone on this node except those transactions that can be safely kept because they actually committed before this transaction on one or more different primary nodes in the RDF network. The transaction number is listed in internal format.

Effect  None.

Recovery  Informational message only; no corrective action is needed. This message is for historical purposes about a network undo pass.

Cause  An updater has attempted to roll over to the specified image file, but that file is missing.

Effect  The updater retires until the file is restored (the event message is repeated every minute until the file has been restored).

Recovery  Restore the missing file to the image trail.

Cause  You attempted to issue a new stop-update-to-time command, but the existing ZTXUNDO list from your last stop update to time operation is still needed.

Effect  The command is aborted.

Recovery  Wait until all RDF updaters have been started and have caught up, then retry the operation. If you get this event message again, stop the RDF product, then restart it. After RDF starts, you may issue another stop-update-to-time command.

Cause  The auxiliary receiver has detected information about an SQL Shared Access DDL operation associated with the specified SNO and RBA in the master audit trail on your primary system.

Effect  The auxiliary receiver coordinates stopping its updsaters at the correct location.

Recovery  Informational message only; no corrective action is needed. When all updaters on all trails have shut down for the SQL NSA operation, you can execute the same DDL operation on your backup system. After having done so, you can restart your updaters.

Cause  You have performed a stop-update-to-time operation, but not all the volumes on the RDF primary system are up and recovered.

Effect  The operation is aborted, and the RDF subsystem aborts.

Recovery  You can restart the RDF product immediately, but you cannot perform a new stop-update-to-time operation until you have enabled all RDF protected volumes on your primary system.

Cause  The updater has reached the end of file incomplete undo takeover processing for an RDF environment.

Effect  The updater is ready to complete takeover processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The list of transactions whose audit must be undone due to file incomplete records exceeds the total number of transactions that can be undone in a single undo pass.

Effect  The updater commences an additional undo pass.

Recovery  Informational message only; no corrective action is needed.

Cause  An SQL Shared Access DDL operation was detected during the network undo phase of the RDF takeover operation.

Effect  The updater abends, and the takeover operation aborts.

Recovery  Recovery may not be possible. Contact your service provider.

Cause  The updater has detected more than the default maximum number of transactions that need to be undone. This exceeds the number of transactions that can currently be loaded into memory.

Effect  The updater abends, and the takeover operation aborts.

Recovery  If this happens during a TAKEOVER operation, reissue the TAKEOVER command. When the updater restarts the table will automatically be resized to accommodate the required number of transactions. If this happens in a stop-update-to-time operation, restart RDF and issue a new STOP UPDATE, TIMESTAMP command at a time when there are fewer transactions active.

Cause  The extractor has sent all remaining audit from the remote mirror(s) on the ZLT standby system to the backup system.

Effect  The extractor shuts down.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor is started on the ZLT standby system for ZLT processing.

Effect  The extractor reads and sends all remaining audit from the remote mirror(s) connected to the ZLT standby system to the receiver on the backup system.

Recovery  Informational message only; no corrective action is needed.

Cause  The extractor has determined that the specified remote mirror is not connected to the ZLT standby system.

Effect  The extractor abends.

Recovery  Connect all required remote mirrors to the ZLT standby system and then reissue the RDF TAKEOVER command.

Cause  All remaining audit from the ZLT standby system has been received and stored in the image trails for this receiver.

Effect  If this message comes from the master receiver, normal RDF TAKEOVER processing is ready to proceed. If this message comes from an auxiliary receiver, normal RDF TAKEOVER processing does not start until the master receiver has finished ZLT processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The master receiver has found a TMF shutdown record. The auxiliary receiver reporting this event is working to catch up to the corresponding point.

Effect  The master receiver continues to wait until all auxiliary receivers have caught up. The auxiliary receiver may continue to report this event as it continues to catch up.

Recovery  If the master receiver has been waiting for more than 30 seconds, you should check the status of all auxiliary extractors and receivers with the RDFCOM STATUS PROCESS command. If you see this event when attempting to issue an RDF TAKEOVER operation, you should manually stop all RDF processes on the backup system, and then reissue the RDFCOM TAKEOVER command.

Cause  You have completed an SQL DDL operation WITH SHARED ACCESS for a file on your primary system, but one or more updaters has terminated prematurely before having processed all required audit.

Effect  It is not yet safe for you to execute this DDL operation on the backup system.

Recovery  Issue the RDFCOM START UPDATE command. You must not execute this DDL operation on the backup database until the RDF 908 event has been logged.

Cause  The process encountered an error while attempting to create an RDF process. The error fields reported in the message are the error number and error detail returned by the PROCESS_CREATE_ system procedure followed by the file-name of the program that was to be run.

Effect  The process is not started, and RDF shuts down.

Recovery  Consult the description of the PROCESS_CREATE_ procedure in the Guardian Procedure Calls Reference Manual to determine the cause of the failure. Once the underlying cause is corrected, RDF can be restarted.

Cause  The primary process of an RDF NonStop process pair encountered an error while attempting to create its backup process. The error fields reported in the message are the error number and error detail returned by the PROCESS_CREATE_ system procedure followed by the file-name of the program that was to be run. This error will occur if one or more parameters in the configuration file are incorrect, if the required processor is not running, or if there are insufficient resources.

Effect  The backup process is not started. The primary continues to run, but will be vulnerable to a CPU failure. The primary will try to create its backup repeatedly until it succeeds.

Recovery  Consult the description of the PROCESS_CREATE_ procedure in the Guardian Procedure Calls Reference Manual to determine the cause of the failure. Once the underlying cause is corrected, the backup process can be created.

Cause  You have completed an SQL DDL operation WITH SHARED ACCESS for a file on your primary system, and all updaters have processed the required audit. It is now safe for you to execute the same DDL operation on the backup database. To obtain the name of the source file involved in the operation on the primary system, look for the last RDF 733 event, which lists the name of the file.

Effect  You must execute the DDL operation on the backup database before you restart the updaters.

Recovery  Informational message only; no corrective action is needed.