DB2 10.5 for Linux, UNIX, and Windows

UNCATALOG DATABASE command

Deletes a database entry from the database directory.

Authorization

One of the following authorities:

SYSADM
SYSCTRL

Required connection

None. Directory operations affect the local directory only.

Command syntax


>>-UNCATALOG--+-DATABASE-+--database-alias---------------------><
              '-DB-------'

Command parameters

DATABASE database-alias: Specifies the alias of the database to uncatalog.

Usage notes

Only entries in the local database directory can be uncataloged. Entries in the system database directory can be deleted using the DROP DATABASE command.

To recatalog the database on the instance, use the UNCATALOG DATABASE and CATALOG DATABASE commands. command. To list the databases that are cataloged on a node, use the LIST DATABASE DIRECTORY command.

The authentication type of a database, used when communicating with an earlier server, can be changed by first uncataloging the database, and then cataloging it again with a different type.

If directory caching is enabled, database, node, and DCS directory files are cached in memory. See the information for the configuration parameter dir_cache in the GET DATABASE MANAGER CONFIGURATION command. An application's directory cache is created during its first directory lookup. Because the cache is only refreshed when the application modifies any of the directory files, directory changes made by other applications might not be effective until the application has restarted.

To refresh the CLP's directory cache, use the TERMINATE command. To refresh the database manager's shared cache, stop (db2stop) and then restart (db2start) the database manager. To refresh the directory cache for another application, stop and then restart that application.

Note: When you add a database partition to the system, all existing databases in the instance are expanded to the new database partition. However, any uncataloged database is not recognized when adding a new database partition. The uncataloged database will not be present on the new database partition. An attempt to connect to the database on the new database partition returns the error message SQL1013N.