SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

Utility Messages (20000 through 23099)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
19-45
SQL 20173
Cause. SQL detected an internal error.
Effect. SQL is unable to process the statement.
Recovery. None This is an internal error. Contact your service provider.
SQL 20174
Cause. SQL detected an internal error.
Effect. The operation fails.
Recovery. None. Contact your service provider.
SQL 20175
Cause. SQL detected an internal error.
Effect. The operation fails.
Recovery. None. Contact your service provider.
SQL 20176
Where utility name of utility that is running, for example—PURGEDATA.
Where object-name is the name of the table, view, synonym, trigger, and so on.
Where operation type of operation that is currently holding the DDL lock. One of the
following: “DP”—DUP, “PI”—Populate index, “PD”—Purgedata, “RC”—Recovery,
“RF”—Refresh, “VA”—Validate, “TR”—Transform.
Cause. You attempted to execute a utility or alter the DDL of an object while a
concurrent utility or DDL operation was being performed on the object, its parent, or its
dependent.
20173 A transaction must be started before executing this
request.
20174 An internal error occurred - A valid SQLNode is
expected.
20175 An internal error occurred - trying to commit or
rollback a transaction that does not exist.
20176 A concurrent utility or DDL operation (operation) is
being performed on object object-name. It must complete
before the requested utility operation can run.