SQL/MP Messages Manual

File-System Messages
HP NonStop SQL/MP Messages Manual427720-006
16-2
SQL 197
Cause. You attempted an operation that generated a call to a SQL/MP component,
and an SQL error occurred in that component. The following situations are possible
causes of this error:
A startup error occurred during the initiation of a SQL/MP process. For example,
the operation you attempted tried to start an SQLCAT process, but the initiation of
the process failed.
The SQLCAT object file on $SYSTEM.SYSTEM is not licensed. SQLCAT must be
licensed to update to the catalog tables.
An SQL versioning error occurred. You attempted to perform an operation that is
not allowed on the version of SQL/MP running on your system. For example, you
attempted to purge a program that is registered in a catalog whose version is later
than the version of SQL/MP you are running.
You attempted an operation that involved the OSS name server sending a request
to the SQLCAT process. The SQLCAT process was unable to complete the
request. For example, you entered an rm command to delete an OSS SQL
program. The rm command caused the OSS name server to send a drop program
request to SQLCAT; however, SQLCAT was not able to perform the request
because it did not have write access to the catalog.
Effect. The operation fails.
Recovery. Analyze the operation you attempted to determine the possible cause.
First, check whether you have the proper authority to perform the operation. For SQL
versioning errors, see the SQL/MP Version Management Guide for operations that are
allowed on different versions of SQL/MP. Check the SQLCAT object file
($SYSTEM.SYSTEM.SQLCAT) to ensure that it is installed and licensed on your
system.
SQL 578
Cause. The block size specified is too large.
Effect. The requested operation is not performed.
Recovery. Reduce the block size specified on the file creation request to an
acceptable value. For format I files, the largest allowed value is 4096 bytes.
197 An SQL error occurred.
578 The block size specified is too large.