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-12
SQL 20039
Cause. You used the add-move-boundary-range syntax instead of partition-
identification to identify a partition to be moved, dropped, or reused, but you did
not specify the exact partition range.
Effect. The operation fails.
Recovery. Reissue the request with the correct partition range. Consider using the
partition-identification syntax instead.
SQL 20040
Cause. The utility subsystem that retrieves data from the file system failed because no
file name was specified to the subsystem.
Effect. The operation fails.
Recovery. None. This is an internal error. Contact your service provider.
SQL 20041
Cause. The utility subsystem that retrieves data from the file system failed with an
unexpected error.
Effect. The operation fails.
Recovery. See the Guardian Procedure Errors and Messages Manual to diagnose
and correct the problem.
SQL 20042
Where $0~string0 is the corresponding column name.
Cause. You attempted to import UCS2 character data in binary mode.
Effect. The operation fails.
Recovery. Prepare the UCS2 data in a UCS2 data file and import it in delimited mode.
20039 For the MOVE, DROP, and REUSE requests, the key range
must specify an exact partition range.
20040 An internal error occurred - file name not specified
while getting file label information.
20041 File system error error number was encountered.
20042 Importing binary data to UCS2 character column
$0~string0 is not allowed.