ODBC Server Reference Manual

Managing Customized Catalogs
HP NonStop ODBC Server Reference Manual—429151-002
7-35
CLEANUP Statement
USERCAT VALIDATE also produces a list of all exceptions detected.
CLEANUP Statement
Use the CLEANUP statement to drop temporary objects. Although the NonStop ODBC
Server drops temporary objects at the end of each session, if the objects are not
dropped, you must drop them manually.
Although the NonStop ODBC Server does not notify you when temporary objects are
not dropped, you will know when to drop temporary objects if you try to create a
temporary object that you know should not exist, and you receive an error message
saying that the object already exists.
Use CLEANUP to drop temporary objects for any of the following:
•
A customized database
•
One user or all users
•
One session for a user or all sessions for that user
Syntax
CLEANUP has the following syntax:
logical-database-name
is an alphanumeric string up to 60 characters in length that specifies the logical
name of the NonStop ODBC Server customized database to clean up.
If you omit logical-database-name, the current database is used by default.
logical-user-name
specifies the owner of the temporary objects to be dropped. The
logical-user-name is a group name followed by a username, as described in
Section 3, CORE SQL Language, or Section 4, Transact-SQL Language. The
logical-user-name can be any NOS_USERNAME found in the ZNSUS
mapping table.
If you omit logical-user-name, temporary objects for all users are dropped.
session-id
is the internally generated session ID of the current session. It is used to qualify all
temporary objects created during that session. Normally, a NonStop ODBC Server
user session issues a CLEANUP statement for any temporary tables created
during the session.
CLEANUP [ logical-database-name [ USER logical-user-name
[ SESSION session-id ]]]