ptx/CTC V1.3.0 Release Notes


Introduction

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.


Product Compatibility

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:


Software Installation

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.


Product Documentation

The following documentation is available on the online documentation CD and at http://webdocs.sequent.com/:


Problem Reports

This section lists the following problem report summaries:

The numbers in parentheses identify the problems in the problem-tracking system.


Fixed Problems in ptx/CTC V1.3.0

The following problems have been fixed in ptx/CTC V1.3.0.


Open Problems in ptx/CTC V1.3.0

This section lists open problems in this release of ptx/CTC.

229797
Two objects of type FS can be logged to the same /usr/ctc/logs file.

Workaround. Do not give two ptx/CTC objects the same name.

233412
ctcadm interactive mode exists when an unknown command type is given.

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.

236166
ctcadm passes the environment through to the method. Subsequently, any methods that are run manually inherit a different environment than the environment that would exist during an availability transition.

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.

237168
ptx/CTC menus were not reinstalled after upgrading ptx/CLUSTERS.

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.

240975
Spurious ktlog error message appears that says node is not a cluster member.

Workaround. Ignore the messages.

241320
ctcd is missing from /etc, giving the error message, "Could not initialize, perhaps CTC_CONFIG_FILE not readable or database path not set."

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."

245887
ptx/CTC retains knowledge of old system names.

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.

Workaround:

  1. Unload (save) the ptx/CTC database to a temporary file on the system.

  2. Stop ptx/CTC on all nodes.

  3. Zero the partition where the ptx/CTC database was loaded.

  4. Restart ptx/CTC on all nodes.

  5. Reload (restore) the ptx/CTC database that was saved to the temporary file.