These release notes support Version 1.3.0 of the ptx/CTC software intended for use with NUMA-QTM systems. ptx/CTC manages mission-critical applications during and after cluster transitions.
Read this document before you install or run this release of ptx/CTC.
This version of ptx/CTC can be used with all NUMA-Q clustered systems.
The following products must be installed on your system to use this release of ptx/CTC:
DYNIX/ptx® V4.6.0 or later
ptx/CLUSTERS V2.3.0 or later
ptx/SVM V2.3.0 or later, if using ptx/CTC for ptx/SVM failover.
ptx/TCP/IP V4.7.0 or later, if using ptx/CTC for IP failover.
ptx/CFS V1.2.0 or later, if using ptx/CTC for CFS object failover.
For installation instructions, refer to the DYNIX/ptx and Layered Products Software Installation Release Notes. ptx/CTC V1.3.0 is automatically installed when ptx/CLUSTERS V2.3.0 is installed.
The following documentation is available on the online documentation CD and at http://webdocs.sequent.com/:
This section lists the following problem report summaries:
The numbers in parentheses identify the problems in the problem-tracking system.
The following problems have been fixed in ptx/CTC V1.3.0.
(250690) The SVMPRIVDG method should only have attempted vxdg -C -x import.
(250680) Setting delay>0 caused a WLU to not deploy.
This section lists open problems in this release of ptx/CTC.
Workaround. Do not give two ptx/CTC objects the same name.
Workaround. If you enter the ctcadm command at the UNIX shell prompt, it will accept standard input as arguments. The acceptable arguments should follow the syntax for the ctcadm command, as described in the ctcadm man page. An invalid syntax will terminate the interactive mode.
Workaround. Since the ctcadm command is run as root, the root environment is inherited by ctcadm when it performs operations such as start, stop, and verify. Perform failover tests manually with the root environment by first typing su - root.
Workaround. Always install ptx/CLUSTERS and ptx/CTC together. If you have already installed ptx/CLUSTERS, re-install ptx/CTC from the CD-ROM so that the menus will reappear.
Workaround. Ignore the messages.
Workaround. Stop ptx/CTC, set the database location, and then restart ptx/CTC. This procedure is described in the ptx/CTC Administration Guide, in the section titled "Creating Your ptx/CTC Configuration."
The ptx/CTC database retains knowledge of old node names. This occurs if you permanently remove nodes from the cluster or rename a node in the cluster. This causes extraneous messages in the EESlog file.