KFAA30562-E

The HADB user having the authorization identifier specified in the DROP USER statement cannot be deleted. <SQLSTATE: 42K19>

aa....aa: Cause of the error

• users cannot delete themselves: The user attempted to delete his or her own account.

• users cannot delete schemas they own: The user owns schemas.

• the user is connected to the HADB server: The user is connected to the HADB server.

• the user grants access privileges to other users: The user has granted access privileges to other HADB users.

• the user is the auditor: The user has the audit privilege.

S:

Ignores this SQL statement. Alternatively, the system invalidates this transaction.

Action:

Take the following action depending on the cause of error displayed in aa....aa:

• If aa....aa is users cannot delete themselves:

  A user cannot delete an HADB user assigned one's own authorization identifier. Specify an authorization identifier that belongs to another HADB user.

  To delete an HADB user assigned one's own authorization identifier, ask another HADB user with the DBA privilege to execute the DROP USER statement.

• If aa....aa is users cannot delete schemas they own:

  The DROP USER statement resulted in an error because the HADB user subject to deletion owns schemas. Check if the schemas, tables, and indexes owned by the HADB user with the specified authorization identifier can be deleted.

  If the tables owned by the HADB user are deleted by executing the DROP USER statement, the viewed tables and foreign keys of other schemas are affected as described below.

  • Viewed tables (viewed tables of other schemas) that depend on a table deleted by executing the DROP USER statement are deleted (or invalidated).

  • Foreign keys (foreign keys of other schemas) whose referenced table is deleted by executing the DROP USER statement are deleted.

  If there is no problem with the above influence, execute the DROP USER statement with CASCADE specified for drop behavior or without specifying the drop behavior. For details about the drop behavior specification, see Specification format and rules for the DROP USER statement in the manual HADB SQL Reference.

• If aa....aa is the user is connected to the HADB server:

  An HADB user assigned an authorization identifier currently connected to the HADB server cannot be deleted. Execute the DROP USER statement after the specified authorization identifier has been disconnected from the HADB server.

  If you want to delete the HADB user immediately, use the adbcancel command to forcibly disconnect the target authorization identifier from the HADB server.

• If aa....aa is the user grants access privileges to other users:

  The DROP USER statement resulted in an error because the HADB user subject to deletion has granted access privileges to other HADB users. Take one of the following corrective actions:

  • Revoke all access privileges granted to other HADB users by the HADB user whose authorization identifier is to be deleted. Then, re-execute the DROP USER statement.

  • Make sure that no problem occurs even if all access privileges granted to other HADB users are revoked by the HADB user whose authorization identifier is to be deleted. Then, re-execute the DROP USER statement with CASCADE specified for the drop behavior.

• If aa....aa is the user is the auditor:

  An HADB user who has the audit privilege cannot be deleted. Revoke the audit privilege, and then delete the HADB user. An HADB user who has the audit admin privilege must revoke the audit privilege.