remove database

Removes databases from a GDS pool.

Syntax

remove database [-gdspool gdspool_name]
                {-all | -database db_name_list}
                [-force]

Options

Table 2-74 GDSCTL remove database Options

Option	Description
-all	Removes all databases in the database pool.
-database db_name_list	Specify a comma-delimited list of database names that you want to remove from the database pool. You cannot specify a database that was added through an Oracle Data Guard broker configuration; you must use Oracle Data Guard to remove these databases.
-gdspool gdspool_name	Specify the GDS pool name. If not specified, and there is only one GDS pool with access granted to the user, it will be used by default.
-force	Removes the database from the catalog even if the database is not available. Using this option can result in global services not being removed from the database.

Usage Notes

Note:

Only add a database to a GDS pool if its Oracle release, release update (RU), or recommended release update (RUR) and and datapatch level exactly match all existing database members. Never mix newer or older database binaries. If this is done, then it can cause errors and unstable services. Also, do not add or remove databases from the pool during rolling patching or upgrades. Onboard at the matched version first, verify services, and then perform rolling patching.

You must connect to the catalog database as a user with the pool administrator privileges, using the command connect before running this command.

If a pool already contains a Data Guard Broker configuration, an error is returned because a database must be removed through DGMGRL in this case.

With Oracle Globally Distributed AI Database, only an undeployed database can be removed. If a database is offline or inaccessible, it has to be first undeployed with the -force option and then removed with the -force option.

Example

Remove the database DB1 from the global service management configuration.

GDSCTL> remove database -database db1 -gdspool pool1