Network Configurations And Shared Access Nonstop Sql/Mp Ddl Operations; Network Validation And Considerations; Rdf Reinitialization In A Network Environment; Network Master Subsystem Initialization - HP NonStop RDF J-series RVUs Management Manual

Network Configurations and Shared Access NonStop SQL/MP DDL
Operations
Under certain circumstances after a shared access NonStop SQL/MP DDL operation, takeover
network undo processing leads to an abort with database corruption.
To avoid this problem, use this protocol when performing shared access NonStop SQL/MP DDL
operations in a network environment:
1. Issue the RDFCOM STOP RDF command on the primary system where you plan to perform
the shared access NonStop SQL/MP DDL operation.
2. From TMFCOM STATUS TRANSACTIONS, collect all the network transactions that are
currently in progress.
3. Wait until all transactions observed in step 2 have completed and are no longer listed.
4. For all other primary nodes in your RDF network, run RDFCOM STATUS RDF commands.
5. When all other RDF subsystems in the RDF network list 0:00 extractor RTD times, issue the
RDFCOM START RDF command on the system where you had stopped RDF.
6. Perform your shared access NonStop SQL/MP DDL operation on your primary system.
7. Follow the normal method for replicating shared access NonStop SQL/MP DDL operations
on your backup system.

Network Validation and Considerations

A set of rules has been devised to ensure that all RDF subsystems in your configured RDF network
are consistent with each other.
1. You must validate all non network master subsystems before validating the network master's
subsystem.
2. Because you cannot validate the network master until all non network master subsystems
have been validated, you cannot start the network master until all non network master
subsystems have been validated.
3. If you have validated a non network master, you are allowed to start that subsystem even
though the network master has not been validated.
See Appendix C (page 365)
NOTE: It is strongly recommended that you validate the configurations of all RDF subsystems
in your RDF network with the RDFCOM VALIDATE CONFIGURATION command before you
attempt to start any. This would then guarantee that your entire RDF network is configured
correctly before you start any of the individual RDF subsystems.

RDF Reinitialization in a Network Environment

For any number of reasons you might choose to stop some of your RDF network subsystems
and reinitialize them. This can be done without impacting the other subsystems in the RDF
network. When you reconfigure those subsystems after initialization, there are several
considerations.

Network Master Subsystem Initialization

When you reconfigure the subsystem, the network record must list all the non network master
systems and the information for each system in the network record must be identical to the
previous configuration. If not, validation will fail and you will not be able to start the subsystem.

Non-Network Master Subsystem Initialization

If you reconfigure the RDF subsystem of a non-network master:
for the error messages that can occur during validation steps.

Network Configurations and Shared Access NonStop SQL/MP DDL Operations

303