CLST-01101: assigning default private interconnect name string for node string

Cause: A private interconnect name was not specified. The node name was used as a default instead.

Action: Verify that the node name refers to IP addresses on the private interconnect. Using a non-private network can cause performance and stability issues.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

CLST-01102: assigning default host name string for node string

Cause: A host name for the node was not specified. The node name was used as a default instead.

Action: If the node name is not equal to the host name, the host name must be supplied to clscfg. Failure to do so will cause the Cluster Ready Services daemons not to function.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading

CLST-01105: An existing configuration was detected. It was not overwritten.

Cause: An existing configuration was detected, and clscfg chose not to overwrite it.

Action: This message may be ignored if it is seen as part of starting any node other than the first one. The -force option can be used to override this decision, but if it is used when there are active cluster members, failure CLSS-0101 and data integrity issues are likely.

Solution doesn't works for you?
POST your error in our discussion panel here.
Our DBA team will be happy to help you :)
Continue Reading
1 2 3 12