Chapter 6 ALLBASE/SQL Error Messages 2207-2412

Table/View !.! already exists. (DBERR 2207)

The table or view you specified in the CREATE TABLE or CREATE VIEW statement already exists in the DBEnvironment.

Create the table or view with a different name (same owner) or different owner name (same table or view name).

Column ! not found in table/view !.!. (DBERR 2208)

The column name you specified was not found in the specified table or view.

Check your spelling. If you still receive this error, use the ISQL INFO command or ask your database administrator to check SYSTEM.COLUMN to make sure that the specified column does exist in the table.

Duplicate column !. (DBERR 2209)

You specified a column name twice in the CREATE TABLE or CREATE INDEX statement or you specified a column already existing in the table in the ALTER TABLE statement.

Issue the command again, specifying unique column names.

Ambiguous column !. (DBERR 2210)

The column you specified in the query exists in more than one table specified in the query.

Execute your query again, specifying the table name as well as the column name.

Column ! not found. (DBERR 2211)

The column you specified in the query does not exist in any of the specified tables.

Check your spelling. If you still receive this error ask your database administrator to check the SYSTEM.COLUMN view to make sure that the specified column does exist.

Index ! not found in table !.!. (DBERR 2212)

A non-existent index was specified in the DROP INDEX statement

or

the index specified in the DROP command is not associated with the specified table.

Check your spelling. If you still receive this error, ask your database administrator to check the SYSTEM.INDEX view to make sure that the specified index does exist in the specified table.

Duplicate index !. (DBERR 2213)

The index you named in the CREATE INDEX statement already exists for the specified table.

Create the index with another name or DROP the old index before you create the new one.

Unrecognizable command or module !.!(!) not found. (DBERR 2214)

One of two error conditions has occurred. Either the command you entered is not recognizable or the module specified cannot be found.

Check your spelling. Ask your database administrator to check the SYSTEM.SECTION view to make sure that the module exists in the DBEnvironment to which the application is connected.

Module !.!(!) already exists. (DBERR 2215)

You tried to PREPARE a module or declare a cursor which already exists.

Issue the command again, specifying a unique module name. Use another integer or give the command a different name. Ask your Database Administrator to check the SYSTEM.SECTION view for names of existing modules.

Module !.! not found. (DBERR 2216)

You tried to execute the OPEN CURSOR statement or the DROP MODULE statement on a non-existent section

or

the module in the DROP MODULE statement does not exist.

Check your spelling. If you still receive this error, ask your Database Administrator to check the SYSTEM.SECTION view to make sure that the module exists in the specified DBEnvironment.

TempSpace name ! already defined. (DBERR 2218)

You tried to create a TEMPSPACE that was already created in this DBEnvironment.

Issue the CREATE TEMPSPACE statement again, specifying a unique logical tempspace name.

TempSpace name ! not found. (DBERR 2219)

You tried to access a TEMPSPACE that does not exist in this DBEnvironment by using the DROP TEMPSPACE statement.

Check your spelling. Check the SYSTEM.TEMPSPACE table to make sure that the specified TEMPSPACE does exist.

Duplicate column found in sort column list. (DBERR 2220)

The ORDER BY clause in the SELECT statement contains more than one reference to the same column. The command is not executed.

Remove the duplicate column and execute the command again.

Duplicate column found in insert column list. (DBERR 2221)

The column list in the INSERT statement contains more than one reference to the same column.

Remove the duplicate column and execute the command again.

Table name required to drop index !.!. (DBERR 2222)

You attempted to drop an index with an ambiguous name. The same index name was used in creating indexes on two tables with the same owner.

Use the syntax DROP INDEX IndexName FROM [Owner.]TableName to specify which table's index should be dropped.

Index !.! not found. (DBERR 2223)

A non-existent index was specified in the DROP INDEX statement without an associated table.

Check your spelling. If you still receive this error, ask your database administrator to check the SYSTEM.INDEX view to make sure that the specified index does exist.

! !.! must have same owner as table !.!. (DBERR 2224)

Different owners were given for the named INDEX, CONSTRAINT, or RULE and the named table, or the default table owner was different from the specified INDEX, CONSTRAINT, or RULE owner in the CREATE INDEX, DROP INDEX, DROP CONSTRAINT, CREATE RULE, or DROP RULE statement.

If both owners were specified, check your spelling. If the table owner was not specified, either specify one or drop the specification of the INDEX, CONSTRAINT, or RULE owner. If you still receive this error, ask your database administrator to check the SYSTEM.INDEX view, SYSTEM.CONSTRAINT view, or SYSTEM.RULE view to determine the correct owner.

Out of disc space for all TempSpaces. (DBERR 2225)

There is not enough space in the device to support your sorting operation.

Use a different device or contact your database administrator to add more space to the current device.

Duplicate SCHEMA !. (DBERR 2227 )

There are existing objects already owned by the AuthorizationName specified.

Make sure the AuthorizationName specified is neither an owner of existing objects in the DBEnvironment nor a grantor of authority on existing objects. To check ownership, query SYSTEM.TABLE and SYSTEM.GROUP. To check authorities, query SYSTEM.TABAUTH and SYSTEM.COLAUTH.

Duplicate column ! found in joined table. (DBERR 2228)

With an explicit three or more table join, a result table (which participates in a subsequent join clause) has been produced and it has more than one column with the same column name. This same column name is either specified as a join column in the "ON SearchCondition" clause of the explicit join, or if a NATURAL...JOIN has been specified, the column has been chosen by ALLBASE/SQL as a join column.

When writing a three or more table join with explicit join syntax make sure that for any single result table participating in a join, there are no duplicate column names which will be named as a join column. To ensure this, make each join clause a NATURAL...JOIN or a JOIN...USING (ColumnList), except for the final join, which may contain these types or a JOIN...ON SearchCondition3 clause. Otherwise, ensure that each join clause is a JOIN...ON SearchCondition3 clause.

Duplicate column ! found in USING clause of JOIN. (DBERR 2229)

There is more than one column with the same name in the USING (ColumnList) clause of an explicit join.

Remove the duplicate column name from the USING ( ColumnList) clause of the explicit join.

Maximum number of parameters (!) exceeded in procedure !.!. (DBERR 2230)

The number of parameters you specified in the CREATE PROCEDURE statement was greater than the maximum number allowed.

Issue the CREATE PROCEDURE statement again, limiting the number of parameters to 255 or fewer.

Procedure parameter data type may not be a LONG data type. (DBERR 2231)

You specified a LONG data type as the parameter data type in a CREATE PROCEDURE statement.

Issue the statement again, specifying only a valid (non-LONG) data type for each parameter.

Duplicate parameter !. (DBERR 2232)

You specified a parameter name twice in the CREATE PROCEDURE statement.

Issue the statement again, specifying unique parameter names.

OUTPUT specified for a parameter not declared as OUTPUT. (DBERR 2233)

In the EXECUTE PROCEDURE statement, you specified OUTPUT for a non- OUTPUT parameter.

Re-issue the EXECUTE PROCEDURE statement, specifying OUTPUT only for parameters that were declared as OUTPUT parameters in the CREATE PROCEDURE statement. If necessary, recreate the procedure specifying OUTPUT for this parameter.

No value was provided for non-nullable parameter ! in procedure !.!. (DBERR 2234)

A parameter declared as NOT NULL in the CREATE PROCEDURE statement was not provided with a value in the EXECUTE PROCEDURE statement.

Re-issue the EXECUTE PROCEDURE statement, providing a value for each parameter declared as NOT NULL.

Error occurred executing procedure !.! statement !. (DBERR 2235)

An error occurred during procedure execution.

Refer to the accompanying error message. Use the statement number to determine which procedure statement caused the error.

Doubly defined LABEL !. (DBERR 2236)

You used the same label more than once in a CREATE PROCEDURE statement.

Remove the duplicate label definition, and reissue the CREATE PROCEDURE statement.

Undefined LABEL !. (DBERR 2237)

You refer to an undefined label in a GOTO statement in the CREATE PROCEDURE statement.

Define the label within the CREATE PROCEDURE statement.

Error occurred during evaluation of the condition in an IF or WHILE statement or the expression in a parameter or variable assignment. Procedure execution terminated. (DBERR 2238)

An error occurred in evaluating the condition or expression.

Refer to the accompanying error message for additional information.

Procedure !.! not found. (DBERR 2239)

The procedure you specified in the statement does not exist in the DBEnvironment.

Check your spelling of the procedure name and the procedure's owner name against the content of the CATALOG.PROCEDURE view. If you still receive this error, ask your database administrator to check the SYSTEM.PROCEDURE view to make sure the specified procedure does exist.

Procedure !.! already exists. (DBERR 2240)

The procedure you specified in the CREATE PROCEDURE statement already exists in the DBEnvironment.

Create the procedure with a different name and/or owner name.

Too many parameter values provided for procedure !.!. (DBERR 2241)

In the EXECUTE PROCEDURE statement, you provided a greater number of parameter values than the number of parameters in the procedure.

Check the procedure specification or the parameter descriptions in SYSTEM.PARAMETER. Reissue the EXECUTE PROCEDURE statement, providing no more parameter values than the number in the procedure.

Error(s) occurred processing statement ! during procedure creation/validation. (DBERR 2242)

One or more errors occurred while processing an SQL statement in a procedure. The statement was not stored as an invalid section, since it can never be validated. The procedure was not created.

Use the statement number in the message to determine which procedure statement generated the error. Refer to the accompanying messages for more information.

Execution of procedure of !.! was invalidated. (DBERR 2243)

The procedure executed a statement that invalidated any further execution of the procedure, such as DROP PROCEDURE or TRANSFER OWNERSHIP of the procedure.

Modify the procedure definition if you did not intend to invalidate the procedure during its execution. Otherwise, no action is required.

Invalid parameter name ! provided for procedure !.!. (DBERR 2244)

The name of a parameter in the EXECUTE PROCEDURE statement is not defined in the parameter list of the CREATE PROCEDURE statement.

Check the parameter lists of both the EXECUTE PROCEDURE statement and the CREATE PROCEDURE statement and ensure that the two lists match. Then reissue the EXECUTE PROCEDURE statement.

OUTPUT ONLY specified for a parameter not declared as OUTPUT ONLY. (DBERR 2245)

You specified OUTPUT ONLY for a parameter in an EXECUTE PROCEDURE statement, but the parameter was not declared OUTPUT ONLY in the CREATE PROCEDURE statement.

Re-issue the EXECUTE PROCEDURE statement, specifying OUTPUT instead of OUTPUT ONLY. Be sure to initialize the parameter value.

Number of items in select list does not match number of result columns for procedure. (DBERR 2246)

The select list in a procedure SELECT statement with no INTO clause is incompatible with the format specified in the WITH RESULT clause of the CREATE PROCEDURE statement.

Re-write the CREATE PROCEDURE statement, either omitting the WITH RESULT clause, or ensuring that all multiple row result sets returned from the procedure are compatible with the format specified.

The KEEP option is not allowed for a procedure cursor. (DBERR 2247)

The KEEP option was included on an OPEN cursor command, but the cursor was defined on an EXECUTE PROCEDURE statement.

Re-issue the OPEN command, omitting the KEEP option.

The ADVANCE statement is allowed only for a procedure cursor. (DBERR 2248)

The ADVANCE statement was issued against a cursor, but the cursor was not defined on an EXECUTE PROCEDURE statement.

There is no need for the ADVANCE statement for a non-procedure cursor. Use the OPEN, FETCH, and CLOSE statements.

Duplicate column found in update set columns. (DBERR 2249)

The same column was specified twice in the SET clause of the UPDATE statement.

Remove one of the duplicate column assignments.

CHECK constraint ! on column ! references other columns. (DBERR 2250)

The named CHECK constraint you defined on a single column contains references to other columns.

Either remove the references to the other columns, or make the check constraint a table level check constraint.

CHECK constraint ! contains host variables. (DBERR 2251)

You defined the named CHECK constraint with host variables in it.

Remove the host variable from your CHECK constraint.

CHECK constraint ! contains aggregate functions. (DBERR 2252)

You defined the named CHECK constraint with aggregate functions in it.

Remove the aggregate from your CHECK constraint.

CHECK constraint ! contains subqueries. (DBERR 2253)

You defined the named CHECK constraint with subqueries in it.

Remove the subquery from your CHECK constraint.

Table CHECK constraint violated. (DBERR 2254)

A table CHECK constraint on the target table of the INSERT or UPDATE was violated during its execution.

Identify the constraint violated and determine the proper value for the INSERT or UPDATE.

View CHECK OPTION constraint violated. (DBERR 2255)

A check constraint on the view named for the INSERT or UPDATE was violated during its execution.

Identify the view definition violated (under the topmost WITH CHECK OPTION view) and determine the proper value for the INSERT or UPDATE.

CHECK constraint ! invalid. (DBERR 2256)

The named CHECK constraint will not be executable and so is not valid.

Identify the problem with the CHECK constraint by examining the error or errors prior to this one. Correct the problem of those errors in order to make the CHECK constraint executable.

View defined WITH CHECK OPTION contains non-updatable query. (DBERR 2257)

The view definition cannot be part of a WITH CHECK OPTION since no INSERT or UPDATE can be applied to the view.

Either remove the WITH CHECK OPTION clause or modify the view definition to make it updatable. Refer to the ALLBASE/SQL Reference Manual for a definition of updatable views.

!.! (!) is not a procedure cursor. (DBERR 2258)

The USING clause was included in a CLOSE cursor statement, but the cursor was not defined on an EXECUTE PROCEDURE statement.

Re-issue the CLOSE statement, omitting the USING clause, or re-issue the CLOSE statement with the USING clause, specifying the correct cursor name.

The RESULT option is allowed only for a procedure returning results. (DBERR 2258)

The RESULT option was specified in a DESCRIBE statement, but the statement described is not an EXECUTE PROCEDURE statement.

For statements other than EXECUTE PROCEDURE, the DESCRIBE RESULT statement is not necessary. If the sqlmproc field of the SQLDA is 0 after DESCRIBE OUTPUT, there is no need to DESCRIBE RESULT.

Unnamed CHECK constraint on column ! references other columns. (DBERR 2260)

You defined an unnamed CHECK constraint on a single column contains references to other columns.

Identify the unnamed constraint which fits this condition and either remove the references to the other columns or make the check constraint a table level check constraint.

Unnamed CHECK constraint contains host variables. (DBERR 2261)

You defined an unnamed CHECK constraint with host variables in it.

Identify the unnamed constraint which fits this condition and remove the host variables from that CHECK constraint.

Unnamed CHECK constraint contains aggregate functions. (DBERR 2262)

You defined an unnamed CHECK constraint with aggregate functions in it.

Identify the unnamed constraint which fits this condition and remove the aggregate functions from that CHECK constraint.

Unnamed CHECK constraint contains subqueries. (DBERR 2263)

You defined an unnamed CHECK constraint with subqueries in it.

Identify the unnamed constraint which fits this condition and remove the subqueries from it.

Input value provided for OUTPUT ONLY parameter. (DBERR 2264)

In the EXECUTE PROCEDURE statement, an actual parameter was provided for an OUTPUT ONLY parameter, but OUTPUT ONLY was not specified.

Re-issue the EXECUTE PROCEDURE statement, either omitting the actual parameter completely, or passing an OUTPUT ONLY host variable for the actual parameter.

DEFAULT value provided for OUTPUT ONLY parameter !. (DBERR 2265)

In the CREATE PROCEDURE statement, a default value was provided for an OUTPUT ONLY parameter.

Re-issue the CREATE PROCEDURE statement, either omitting the default value, or specifying OUTPUT rather than OUTPUT ONLY.

Unnamed CHECK constraint invalid. (DBERR 2266)

An unnamed CHECK constraint will not be executable and so is not valid.

Identify the unnamed constraint which fits this condition and identify the problem with this CHECK constraint by examining the error or errors prior to this one. Correct the problem of those errors in order to make the CHECK constraint executable.

Column ! must allow nulls since table !.! is not empty. (DBERR 2267)

A NOT NULL specification in an ALTER TABLE statements requires that the table be empty, or that a non-null DEFAULT clause be used.

Include a non-null DEFAULT clause.

CONSTRAINT !.! for table ! not found. (DBERR 2268)

ConstraintID specified is not a valid constraintID stored in the database.

Re-issue the DROP CONSTRAINT statement with a valid ConstraintID.

PRIMARY KEY can not be dropped since it is referenced by a FOREIGN KEY. (DBERR 2269)

PRIMARY KEY constraints can only be dropped when they are not being referenced by any FOREIGN KEY.

Verify whether you want to drop the FOREIGN KEY references before executing this statement again.

PRIMARY KEY already exists in table !.!. (DBERR 2270)

A PRIMARY KEY is already defined in the table, and only 1 PRIMARY KEY is allowed in a table.

You may want to drop the defined PRIMARY KEY if it is not the intended PRIMARY KEY for this table.

Referenced table in foreign key cannot be a view (!.!). (DBERR 2275)

The table named in a REFERENCES clause was a view.

Change the table to the base table on which the view is based.

User/group ! is using ! authority to support a foreign key. (DBERR 2276)

You attempted to revoke an authority which is currently depended on by the specified user, class or group (directly or indirectly) to authorize a foreign key.

Re-issue the revoke with CASCADE specified, or have your DBA or the owner of the foreign key remove the table in which the foreign key resides, or remove the foreign key (using DROP TABLE or DROP CONSTRAINT) and then reissue the revoke.

Table !.! does not have a primary key, or number of columns in primary key does not match number in foreign key. (DBERR 2277)

The table specified in a REFERENCES clause without a column list has no PRIMARY KEY to use as an implicit column list, or the number of columns in the PRIMARY KEY does not match the number specified in the foreign key list.

Specify a column list with the table referenced, or check the number of columns in the primary key of the table referenced.

Referenced column list does not match any UNIQUE or PRIMARY KEY constraint in table !.!. (DBERR 2278)

The column list given for a table in a REFERENCES clause does not match any candidate key defined on the table.

Check the order of the columns, as they must exactly match the order of the candidate key columns. Specify a referenced column list in the same order as some candidate key in the referenced table.

User ! does not have ! authority on needed columns of table/view !.!. (DBERR 2279)

You do not have the authority to access the columns of a table.

Check with the database administrator for the needed authority, sign on as a user with the required authority.

PRIMARY KEY/UNIQUE constraint with HASH index can not be dropped. (DBERR 2280)

You attempted to drop a constraint that was used in the HASH ON CONSTRAINT clause in the CREATE TABLE statement. These constraints cannot be dropped without dropping the whole table.

Check the constraint type in SYSTEM.CONSTRAINT and ensure that the type of the constraint is not "H", for hash.

Maximum number of columns allowed in a UNIQUE/PRIMARY KEY/FOREIGN KEY is !. (DBERR 2281)

The unique or referential constraint exceeds the maximum number of columns allowed in a unique or referential constraint.

Define the unique or referential constraint on columns within this limit.

UNIQUE/PRIMARY KEY/FOREIGN KEY length exceeds maximum length (! bytes). (DBERR 2282)

Key length exceeds the maximum.

Define referential constraints which are within the key length limit specified in the database administrator guide.

Duplicate column name ! in UNIQUE/PRIMARY KEY/FOREIGN KEY column list. (DBERR 2283)

You specified a column name more than once in a column list of a unique or referential constraint.

Re-issue the CREATE TABLE statement without duplicate column names in the UNIQUE/PRIMARY KEY/FOREIGN KEY column lists.

Invalid data type ! found in column ! specified in a UNIQUE/PRIMARY KEY/FOREIGN KEY constraint column list. (DBERR 2284)

A column found in a unique or foreign key column list is of an invalid data type.

Re-issue the statement using columns of the allowed data types in your constraints.

FOREIGN KEY column ! data type ! doesn't match data type ! of referenced column. (DBERR 2285)

A pair of corresponding columns in the referencing column list and referenced column list of a foreign key constraint have data types which are incompatible for referential constraints.

Check the data types of the corresponding columns in your foreign key constraint declarations and make sure they are the same data type.

UNIQUE/PRIMARY KEY/FOREIGN KEY column ! not defined in CREATE/ALTER TABLE. (DBERR 2286)

The named column appears in an integrity constraint but was not defined in the CREATE TABLE.

Re-issue the command with referential constraints defined on columns being defined in the statement.

Cannot drop a table with a UNIQUE/PRIMARY KEY constraint supporting another table's FOREIGN KEY constraint. (DBERR 2287)

You tried to drop a table with a UNIQUE or PRIMARY KEY constraint. This constraint supports a foreign key in another table.

You cannot drop the table until the foreign key reference is dropped.

Unique constraints with identical unique column lists specified. (DBERR 2288)

Table contains duplicate unique constraints.

Re-issue command without redundant unique constraints.

User ! is using membership in group ! to support a foreign key. (DBERR 2289)

You attempted to remove the specified user from a group, and that user has created a foreign key using authorities granted to the group.

Locate and drop the tables created by the user with foreign keys, then reissue the REMOVE FROM GROUP.

Group ! is being used to support a foreign key. (DBERR 2290)

The group or its members own a table containing a foreign key, and that foreign key was allowed to exist due to authorities granted to the group. Dropping the group would remove the authority for the foreign key.

Locate and drop the tables with foreign keys created by group members, then reissue the DROP GROUP.

2291 Constraint !.! already exists. (DBERR 2291)

A constraint by the specified name already exists, and therefore the CREATE TABLE/TRANSFER OWNERSHIP statement cannot be completed.

If TRANSFER OWNERSHIP, transfer the table to a different user. If CREATE TABLE, reissue the command with unique constraint names. Or, drop the table with the conflicting constraint name.

INSERT/UPDATE/DELETE statement had no effect due to execution errors. (DBERR 2292)

No rows were added, altered or removed by your statement because of an error during execution. Examine the accompanying error messages to determine the cause.

Determine the row(s) causing the error and remove them from the statement's field of effect before reissuing the command. This can be done by restricting the WHERE clause of an UPDATE, DELETE, or format 2 INSERT, or removing the offending rows from a bulk insert.

FOREIGN KEY constraint violated. (DBERR 2293)

The statement you issued attempted to modify the data in a way not allowed by a referential constraint on the target table. You cannot delete or modify a primary key row if a foreign key row references it. You cannot insert or modify a foreign key row if there will be no matching primary key row unless the rows contain NULL values.

Determine the row causing the violation by examining the constraints of the target table, and reissue the statement with restrictions so that the offending rows are not within it.

UNIQUE/PRIMARY KEY column ! must specify NOT NULL. (DBERR 2294)

You must define all columns in a UNIQUE/PRIMARY KEY in the CREATE TABLE statement as NOT NULL.

Re-issue the CREATE TABLE specifying NOT NULL for all columns in a UNIQUE/PRIMARY KEY constraint.

Index uniqueness or UNIQUE/PRIMARY KEY/FOREIGN KEY constraint violated. (DBERR 2295)

You tried to insert a duplicate key value into a column used in a unique index or a unique constraint, or you attempted to insert, update, or delete a unique constraint or foreign key constraint in a manner which would leave a foreign key value without a matching primary key value.

A foreign key value may be set to NULL until the correct primary key value is placed in the unique constraint it references; or a duplicate unique constraint/unique index violation can be determined. Once this is done, the command may be reissued without the offending rows.

Data type for LIKE predicate column must be CHAR or VARCHAR. (DBERR 2296)

The data type of the LIKE predicate column is not a CHAR or VARCHAR.

Modify the query to have a CHAR or VARCHAR data type column on the LIKE predicate.

FOREIGN KEY column ! data type DECIMAL(!,!) doesn't match PRIMARY KEY data type DECIMAL(!,!). (DBERR 2297)

You entered a value in the referencing column which has a different precision and scale than the precision and scale of the PRIMARY KEY referenced column.

Check the precision and scale of the PRIMARY KEY and change the value entered in the referencing column to match it.

User ! does not have ! authorization. (DBERR 2300)

The DBEUserID under which the command was executed does not have the authority (DBA, RESOURCE, or CONNECT) to execute the command.

Contact your database administrator to get the required authority or sign on as a user who does have the required authority.

User ! does not have ! authority on !.!. (DBERR 2301)

The DBEUserID does not have the required table or view authority to execute the command.

Contact your database administrator to get the required authority or sign on as a user who does have the required authority.

User ! does not have ! authority on column !.!.!. (DBERR 2302)

You do not have the specified authority needed to access the column. UPDATE is needed in the UPDATE statement, or REFERENCES is needed in the CREATE TABLE statement.

Contact your database administrator to get the required authority or sign on as a user who does have the required authority.

User ! does not have OWNER or DBA authority. (DBERR 2303)

The command requires either OWNER or DBA authority.

Refer to the ALLBASE/SQL Database Administration Guide and the ALLBASE/SQL Reference Manual for statements requiring special authority. Contact your database administrator to get the required authority.

Cannot revoke DBA authority from session owner !. (DBERR 2304)

You tried to REVOKE DBA authority from yourself.

Refer to the ALLBASE/SQL Database Administration Guide for additional information on when you can revoke DBA authority.

Use REVOKE ! to revoke GRANT !. (DBERR 2305)

The DBEUserID was granted the specified authority (UPDATE or REFERENCES) on all columns using the GRANT statement without specifying column names. You tried to revoke the authority on individual columns in the table.

Revoke the authority on all columns using the REVOKE statement without specifying column names. If you want the user to have the authority on some columns of the table, issue the GRANT statement specifying the appropriate column names.

Special GRANT/REVOKE disallowed for reserved user !. (DBERR 2306)

The DBEUserID specified in the GRANT or REVOKE statement is a reserved user (PUBLIC, TEMP, SYSTEM, HPRDBSS). The GRANT or REVOKE statement is ignored.

Refer to the ALLBASE/SQL Database Administration Guide explanation of reserved users and their purposes.

User ! does not have OWNER authority. (DBERR 2307)

The TRANSFER OWNERSHIP and DROP VIEW statements are not allowed on system views.

No action is necessary. Refer to the ALLBASE/SQL Database Administration Guide for additional information on system views.

Reserved user ! cannot be added to a group. (DBERR 2308)

You attempted to add a RESERVED user (PUBLIC, SYSTEM, TEMP, or HPRDBSS) to a group using the ADD GROUP statement.

No action is necessary. Refer to the ALLBASE/SQL Database Administration Guide for an explanation of reserved users and their purposes.

User ! neither has DBA authority nor is a member of group !. (DBERR 2309)

The AuthorizationName is different than the DBEUserID executing the CREATE SCHEMA statement. You do not have DBA authority, nor are you a member of a group whose name is the AuthorizationName specified in the CREATE SCHEMA statement.

Ensure that you have proper authorization to execute the CREATE SCHEMA statement.

User ! does not have DBA authority. (DBERR 2310)

GRANT with BY clause done by someone without DBA authority.

This command requires DBA authority to be performed.

Group ! not found. (DBERR 2311)

The group name specified in the DROP GROUP, ADD TO GROUP, or REMOVE FROM GROUP statement, does not exist in the DBEnvironment.

Check your spelling. If you still receive this error, ask your database administrator to check the SYSTEM.GROUP view to determine if the group exists in the DBEnvironment.

User or group ! already exists. (DBERR 2312)

The user or group name specified in the CREATE GROUP statement already exists in the DBEnvironment.

Issue the command again, specifying a unique user or group name.

User ! not found in group !. (DBERR 2313)

The DBEUserID specified in the REMOVE FROM GROUP statement does not exist in the specified group.

Check your spelling. If you still receive this error, ask your database administrator to check the SYSTEM.GROUP view to make sure that the specified user does exist in the group.

User ! already a member of group !. (DBERR 2314)

The DBEUserID in the ADD command is already a member of the group.

No action is necessary.

User or group ! conflicts with existing !. (DBERR 2315)

The group name specified in the CREATE GROUP statement is already being used as a DBEUserID or group name in the manner specified in the second parameter; or a CONNECT was attempted with a DBEUserID equivalent to an existing group name.

Remove the existing usage before re-issuing the CREATE GROUP, or issue it with a different group name; or drop the group to permit the connection; or do not attempt to CONNECT with that DBEUserID.

User or group ! owns object(s) in the DBEnvironment. (DBERR 2316)

The DBEUserID or group specified in the DROP command is the owner name of either tables, views, modules, or groups in the DBEnvironment.

Drop the objects or transfer ownership to another DBEUserID or group before dropping the user or group.

User or group ! is (indirect) member of group !. (DBERR 2317)

You tried to add a group (or user) to a group which is already a member of the group you tried to add.

No action is necessary. If you specified more than one user or group in the ADD TO GROUP statement, the valid names were processed and the invalid names were ignored.

Cannot add group ! to itself. (DBERR 2318)

You tried to add a group (or user) to itself.

Issue the command again, specifying a set of unique group or user names which does not include the target group name.

Cannot remove group ! from itself. (DBERR 2319)

You tried to remove a group from itself.

Issue the command again, specifying a set of group names which does not include the target group name.

CONNECT disallowed. Group ! already exists. (DBERR 2321)

A group name that is the same as your DBEUserID name exists in the DBEnvironment.

Login using a different login id. Ask your database administrator to change the group name to something different from your login id so that this problem will not occur in the future.

User ! already has ! authorization on !.! from a different grantor. (DBERR 2322)

Attempted to GRANT the specified authority to a user who has the authority from another grantor already, and you would not be able to revoke that authority.

Repeat the GRANT without that user and/or authorization.

User ! already has ! authorization on !.!.! from a different grantor. (DBERR 2323)

Attempted to GRANT the specified authority to a user who has the authority from another grantor already, and you would not be able to revoke that authority.

Repeat the GRANT without that user and/or authorization.

Cannot revoke ! authorization from ! on !.! without CASCADE. (DBERR 2324)

Attempted to REVOKE the specified authority from a user who has used the grantability of that authority to grant to another user.

Use REVOKE CASCADE if you wish to remove all the grants that user has cascaded on the authority, or get a DBA to perform the revoke on that user (this will leave all of that user's grants intact). The DBA should use the BY option of the REVOKE statement to avoid an orphaned privilege.

Cannot revoke ! authorization from user ! on !.!.! without CASCADE. (DBERR 2325)

Attempted to REVOKE the specified authority from a user who has used the grantability of that authority to grant to another user.

Use REVOKE CASCADE if you wish to remove all the grants that user has cascaded on the authority, or get a DBA to perform the revoke on that user (this will leave all of that user's grants intact).

GRANT of ! authority to ! on !.! causes a cycle. (DBERR 2326)

Attempted to GRANT the specified authority which would cause a cycle of grants in the authority list.

Examine the chain of grants to determine if the cycle can be broken, or have someone else perform the grant (if their doing so would not cause a cycle).

GRANT of ! authority to ! on !.!.! causes a cycle. (DBERR 2327)

Attempted to GRANT the specified authority which would cause a cycle of grants in the authority list.

Examine the chain of grants to determine if the cycle can be broken, or have someone else perform the grant (if their doing so would not cause a cycle).

User ! does not have direct OWNER, DBA, or GRANTABLE ! authority on !.!. (DBERR 2328)

Attempted to GRANT the specified authority WITH GRANT OPTION, but did not have the direct authority needed to do so.

To grant WITH GRANT OPTION, the user must be authorized to grant directly, not through group membership. Have the system administrator or table owner grant you the authority with the grant option directly, or perform the grant you wish done.

User ! does not have direct OWNER, DBA, or GRANTABLE ! authority on !.!.!. (DBERR 2329)

Attempted to GRANT the specified authority WITH GRANT OPTION, but did not have the direct authority needed to do so.

To grant WITH GRANT OPTION, the user must be authorized to grant directly, not through group membership. Have the system administrator or table owner grant you the authority with the grant option directly, or perform the grant you wish done.

Group ! not allowed to grant privileges. (DBERR 2330)

Between the time the GRANT was compiled and executed, the user performing the GRANT became a group. GRANTs cannot be performed by groups, due to the need to store the user name of the grantor.

Drop the group or re-perform the GRANT with a valid user name.

Group ! cannot be granted privileges WITH GRANT OPTION. (DBERR 2331)

You attempted to grant WITH GRANT OPTION to a group.

Repeat the grant without the specified group, or without WITH GRANT OPTION.

User not authorized to revoke ! on !.! from user/group !. (DBERR 2332)

You are not the OWNER, DBA, or grantor of the specified privilege on the specified table to the specified user/group.

Have the system administrator determine the grantor of the privilege and have that person perform the revoke, or have the table owner or a DBA perform the revoke.

User not authorized to revoke ! on !.!.! from user !. (DBERR 2333)

You are not the OWNER, DBA, or grantor of the specified privilege on the specified column to the specified user/group.

Have the system administrator determine the grantor of the privilege and have that person perform the revoke, or have the table owner or a DBA perform the revoke.

GRANT/REVOKE of ALTER/INDEX/REFERENCES authority not allowed on a view (!.!). (DBERR 2334)

You attempted to GRANT or REVOKE one of the privileges ALTER, INDEX, or REFERENCES on the specified view.

Repeat the command without any of the privileges listed above.

User ! already has ! authorization on !.! with a different grantability. (DBERR 2335)

You attempted to re-grant an authority with a different grantability (WITH GRANT OPTION was specified on only one of the grants).

Re-issue the grant without the specified authorization, or revoke the specified authorization and then reissue the grant.

User ! already has ! authorization on !.!.! with a different grantability. (DBERR 2336)

You attempted to re-grant an authority with a different grantability (WITH GRANT OPTION was specified on only one of the grants).

Re-issue the grant without the specified authorization, or revoke the specified authorization and then reissue the grant.

User ! already has ! authorization on columns of !.! with a different grantability. (DBERR 2337)

You attempted to grant a table level authority with a different grantability from an existing column level authority which this would override (WITH GRANT OPTION was specified on only one of the grants).

Re-issue the grant without the specified authorization, or revoke the specified authorization and then reissue the grant.

User ! does not have OWNER, DBA, or direct GRANTABLE ! authority on !.!. (DBERR 2338)

You attempted to perform a GRANT WITH GRANT OPTION or REVOKE of the specified authority without having the authority to do so.

You need to have OWNER, DBA, or have been granted the authority WITH GRANT OPTION in order to perform a GRANT WITH GRANT OPTION or REVOKE of the authority.

User ! does not have OWNER, DBA, or direct GRANTABLE ! authority on !.!.!. (DBERR 2339)

You attempted to perform a GRANT WITH GRANT OPTION or REVOKE of the specified authority without having the authority to do so.

You need to have OWNER, DBA, or have been granted the authority WITH GRANT OPTION in order to perform a GRANT WITH GRANT OPTION or REVOKE of the authority.

User ! already has ! authorization on columns of !.! from a different grantor. (DBERR 2340)

You attempted to GRANT the specified authority on the table level, and were unable to override column level authorities on that table from another grantor.

Only the DBA, OWNER, or direct grantor can override column level authorities with table level authority. Have such a user perform your grant, or reissue your grant without the specified user and/or authority.

TRANSFER OWNERSHIP of !.! to ! causes a cycle of ! authority. (DBERR 2341)

Attempted to transfer a table upon which the specified authority existed, and that transfer would cause a cycle of grants in the authority list for that authority on that table.

Examine the chain of grants to determine if the cycle can be broken, or transfer the table to a different user (if doing so would not cause a cycle).

TRANSFER OWNERSHIP of !.! to ! causes a cycle of ! authority on column !. (DBERR 2342)

Attempted to transfer a table upon which the specified authority existed, and that transfer would cause a cycle of grants in the authority list for that authority on that table.

Examine the chain of grants to determine if the cycle can be broken, or transfer the table to a different user (if doing so would not cause a cycle).

User ! does not have authority to install modules for owner !. (DBERR 2343)

The user specified does not have the required authority.

Use the GRANT INSTALL AS OwnerID TO DBEUserID statement to give the proper authority to the user.

User ! does not explicit INSTALL AS ! authority. (DBERR 2346)

The user specified does not have INSTALL authority for this owner.

Use the GRANT INSTALL statement to grant INSTALL AS authority to the user.

User ! does not have INSTALL ! authority. (DBERR 2347)

The user specified does not have any INSTALL authority.

Use the GRANT INSTALL AS OwnerID TO DBEUserID statement to grant INSTALL authority to the user.

!

A RAISE ERROR statement was specified without an error number or with an error number of 2350.

See the Section "User Defined Error Messages" in the "Introduction" for discussion of RAISE ERROR generated errors. Examine the error text to determine the action to take.

RULE !.! WHERE condition invalid. (DBERR 2352)

The named RULE definition's WHERE condition will not be executable and so is not valid.

Identify the problem with the RULE definition by examining the error or errors accompanying this one. Correct the problem of those errors in order to make the RULE's WHERE condition executable.

RULE !.! EXECUTE PROCEDURE invalid. (DBERR 2353)

The named rule definition's EXECUTE PROCEDURE clause will not be executable and so is not valid.

Identify the problem with the rule definition by examining the error or errors accompanying this one. Correct the problem identified in those errors in order to make the rule's EXECUTE PROCEDURE clause executable.

Rule !.! not found. (DBERR 2354)

The named rule was not found.

Re-issue your DROP RULE statement after verifying that the proper rule was named.

Rule ! not found on table !.!. (DBERR 2355)

The named rule was not found on the named table.

Re-issue your DROP RULE statement after verifying that the proper table and rule were named, or issue the statement without the table name.

Rule !.! already exists. (DBERR 2356)

The name of the rule given in the CREATE RULE statement is the name of an existing rule. or a TRANSFER OWNERSHIP on a table has resulted in a duplicate rule name.

Issue the CREATE RULE statement with a rule name unique for the table owner.

Name ! used for both OLD and NEW in rule !.!. (DBERR 2357)

You specified the same correlation name for both the OLD and NEW correlation names.

Reissue the statement using the default correlation names or with distinct OLD and NEW correlation names.

Duplicate column ! in update column list of rule !.!. (DBERR 2358)

You specified the named column more than once in the UPDATE statement type column list of your CREATE RULE statement.

Re-issue your CREATE RULE statement after checking that no column name is specified more than once in the UPDATE statement type column list.

Error number cannot be NULL for RAISE ERROR. (DBERR 2360)

The error number given to the RAISE ERROR statement had the NULL value.

Check the value given to the RAISE ERROR statement and ensure that it is not null.

Error number must be positive for RAISE ERROR. (DBERR 2361)

The error number given to the RAISE ERROR statement was negative or zero.

Check the value given to the RAISE ERROR statement and ensure that it is greater than zero.

Error number for RAISE ERROR must have data type INTEGER or SMALLINT. (DBERR 2362)

The error number for RAISE ERROR was an invalid data type.

Ensure that the data type of the error number is INTEGER or SMALLINT.

Error text cannot be NULL for RAISE ERROR. (DBERR 2363)

The error text given to the RAISE ERROR statement had the NULL value.

Check the value given to the RAISE ERROR statement and ensure that it is not null.

Error text for RAISE ERROR must have data type CHAR or VARCHAR. (DBERR 2364)

The error text for RAISE ERROR was an invalid data type.

Ensure that the data type of the error text is CHAR or VARCHAR.

Deadlock detected causing rollback query. (DBERR 2365)

Deadlock occurred.

Determine the cause of the deadlock and take appropriate actions to correct the problem. See "Resolving Conflicts among Concurrent Transactions" in the chapter "Currency Control through Locks and Isolation Levels" in the ALLBASE/SQL Reference Manual.

Timeout expired (! seconds) causing rollback query. (DBERR 2366)

The timeout expired.

No action is required.

RENAME COLUMN is not allowed on a check constraint column. (DBERR 2367)

A RENAME COLUMN statement was issued for a check constraint column.

Check constraints on a renamed column will be disallowed. Determine if an incorrect column was renamed or take other appropriate action.

Rule firing invalidated current section (!.!(!)). (DBERR 2370)

Upon completion of a rule, the current section was found to be invalidated by actions taken by the rule.

Check the rules fired by the current statement and determine if the procedures they invoke invalidate sections; or take no action.

Rule firing invalidated user's statement. (DBERR 2371)

Upon completion of the rules fired by the user's statement, the statement was found to be invalidated by actions taken by the rules.

Check the rules fired by the current statement and determine if the procedures they invoke invalidate sections; or take no action.

Maximum rule firing depth (!) exceeded. (DBERR 2372)

Rules chained to a depth greater than the allowed maximum.

Determine the cause of exceeding the maximum rule depth; or take no action.

Procedure executed by rule executed ! statement. (DBERR 2373)

A procedure invoked by a rule executed a COMMIT, ROLLBACK, or SAVEPOINT statement.

Alter the procedure to not invoke such statements when fired by a rule, or invoke a different procedure from the rule.

User ! does not have the authority to create HPODBSS table/view. (DBERR 2390)

You attempted to create a table or view with an owner name of HPODBSS.

Replace HPODBSS with a non-reserved name and reissue the statement.

Maximum number of columns (!) exceeded on table/view !.!. (DBERR 2400)

The number of columns you specified in the ALTER TABLE, CREATE TABLE, or CREATE VIEW statement was greater than the maximum number of columns allowable.

Issue the command again ensuring that the total number of columns does not exceed 1023.

Maximum number of tables per module exceeded. (DBERR 2402)

The maximum number of tables for a SELECT statement has been exceeded.

Issue the command again, specifying no more than 31 tables.

Maximum number of concurrent transactions exceeded. (DBERR 2404)

The maximum number of concurrent transactions has been exceeded.

Retry the begin transaction statement again. If it fails, ask your database administrator for assistance.

Index ! on table !.! has more than ! columns. (DBERR 2405)

The index you specified contains more than 16 columns.

Check the CREATE INDEX statement to make sure that the number of columns specified is less than or equal to 16.

SelectList contains more than ! columns. (DBERR 2406)

The number of items in the select list exceeded the maximum number allowable.

Check your SELECT statement to make sure that the number of items in the select list is equal to or less than 1024.

Length of column ! in table !.! exceeds ! bytes. (DBERR 2407)

The number of bytes in the specified column exceeded the maximum number allowable.

Issue the CREATE TABLE statement again with the maximum number of bytes or less.

Tuple length of table !.! exceeds ! bytes. (DBERR 2408)

You attempted to create a table with a minimum tuple length greater than the maximum allowed.

Reduce the minimum tuple length of the table and reissue the statement.

Length of index ! on table !.! exceeds ! bytes. (DBERR 2409)

The index you attempted to create exceeds the maximum key length.

Recreate your index using a column or combination of columns that is less than the maximum number of bytes.

Tuple exceeded maximum length. (DBERR 2410)

The maximum tuple length of 4,000 bytes has been exceeded.

Check your input source (e.g. load file) and the original CREATE TABLE statement to make sure that each tuple is less than or equal to 4,000 bytes long.

Number of sort columns (!) exceeds maximum !. (DBERR 2411)

The ORDER BY, GROUP BY, or DISTINCT clause of the SELECT statement specifies a number of columns which exceeded the maximum allowable.

Issue the command again, specifying no more than the maximum number of sort columns. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.

Index exceeded maximum length. (DBERR 2412)

The maximum index length of 1024 bytes has been exceeded

or

the ORDER BY or GROUP BY clause uses a column greater than 1024 bytes.

Check your input source (e.g. load file) and the original CREATE INDEX command to make sure that each index entry is less than or equal to 1024 bytes long

or

reduce the size of the column used by the ORDER BY or GROUP BY to less than 1010 bytes.