Neoview Messages Manual (Volume 1) (R2.4)

Cause NO ACTION referential action is specified in the referential definition and the
CONTROL QUERY DEFAULT value for REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT
is ‘SYSTEM.’
Effect The NO ACTION referential action has RESTRICT referential action semantics. It is
recorded as NO ACTION in the metadata table.
Recovery To alter the behavior of the NO ACTION referential action, set the appropriate
value for the REF_CONSTRAINT_NO_ACTION_LIKE_RESTRICT default.
SQL 1304
1304 SQL/MX could not obtain the location of the system schema tables.
Cause The HP Neoview platform location of the system schema tables could not be obtained
from the anchor file.
Effect The operation fails. This message will be accompanied by one or more other messages
detailing the reason for the failure.
Recovery Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition.
SQL 1305
1305 The specified schema location subvolume is already in use by schema
schema.
subvolume
is the HP Neoview platform subvolume name specified in the LOCATION
clause of the CREATE SCHEMA command.
schema is the ANSI name of an existing schema that already uses subvolume as a
schema subvolume.
Cause In a CREATE SCHEMA command, you specified subvolume in the LOCATION
clause; however, this subvolume is already being used as schema subvolume by schema.
Effect The statement fails unless it includes the optional REUSE clause to allow reuse of the
same schema subvolume name. If the REUSE clause is used, this is a warning message and
the schema is created successfully. The warning can be issued repeatedly for a single CREATE
SCHEMA command if multiple schemas already exist with subvolume as the schema
subvolume.
Recovery Only schemas that are RDF replicated to another segment should have the same
subvolume names as their corresponding schemas on the other segment. To create these, use
the optional REUSE clause in the CREATE SCHEMA statement. All other schemas should
have unique subvolume names. Schemas that are, or will be, related as RDF primary and
backup schemas must have identical schema names and subvolumes on the primary and
backup segments.
SQL 1306
1306 SQL/MX was not able to generate a unique schema location for schema
schema.
schema
is the ANSI name of the schema specified in the CREATE SCHEMA command.
Cause In a CREATE SCHEMA command, you did not specify a LOCATION clause, so the
HP Neoview database software was unable to generate a schema subvolume name that is not
already being used by existing schemas.
Effect The operation fails.
Recovery Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition.
53