HP NonStop SQL/MX Messages Manual page 427

Table of Contents

Advertisement

MXCI Messages (15000 through 15999)
Recovery. Use the INFO SERVICE command to verify that the specific service is still
operational. See lower-level error messages issued with this message. Also, see
information about this error in the EMS collector for MXCS service event messages,
which is specified on the mxoas start command with $0 as the default.
SQL 15329
15329 Could not get the status for all DSs on the SERVICE.
Cause. The lower level cannot return status for all the data sources on the service.
The system could be busy.
Effect. The operation fails.
Recovery. Use the INFO SERVICE command to verify that the specific service is still
operational. See lower-level error messages issued with this message. Also see
information about this error in the EMS collector for MXCS service event messages,
which is specified on the mxoas start command with $0 as the default.
SQL 15330
15330 Could not get the status for the next DS in the list.
Cause. The lower level cannot return status for the next data source on the service.
The system could be busy.
Effect. The operation fails.
Recovery. Use the INFO SERVICE command to verify that the specific service is still
operational or the INFO DS * command to verify that the DS still exists. See lower-
level error messages issued with this message. Also, see information about this error
in the EMS collector for MXCS service event messages, which is specified on the
mxoas start command with $0 as the default.
SQL 15331
15331 CFG Trace file name is too long. Should be limited to
30 char.
Cause. The file name given for the trace file is to long.
Effect. The operation fails.
Recovery. Enter the command, specifying a shorter trace file name.
HP NonStop SQL/MX Messages Manual—640324-001
15 -39

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents