add database

Syntax

add database -connect connect_identifier 
            [-region region_name]
            [-gdspool gdspool_name]
            [-pwd password]
            [-savename]
            [-cpu_threshold cpu] 
            [-disk_threshold disk]
            [-validate_network]

Options

Table 2-5 GDSCTL add database Options

Option	Description
`-connect connect_identifier`	Specify an Oracle Net connect descriptor or net service name that resolves to a connect descriptor for the database being added.
`-cpu_threshold cpu`	Specifies CPU Utilization percentage threshold.
`-disk_threshold disk`	Specifies the average latency in milliseconds of a synchronous single-block read.
`-gdspool gdspool_name`	The Global Data Services pool to which the database belongs.
`-pwd password`	The password for the GSMUSER. If `-pwd` is not specified, then you are prompted for the password.
`-region region_name`	The Global Data Services region to which the database belongs.
`-savename`	Specify this option to store a net service name specified with the `-connect` option in the Global Data Services catalog, rather than the connect descriptor mapped to that net service name.
`-validate_network`	This flag enables several network validation checks, including checking network connectivity between hosts and checking VNCR entries are valid.

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 Global Data Services catalog database as a user with the pool administrator privileges, using the connect command before running this command.
If -savename is not specified, then GDSCTL replaces what you specify for the net service name with the full connection string before saving the configuration to the catalog.
The default for GDSCTL is for autovncr to be enabled for the catalog. If autovncr has been disabled for the catalog, before configuring Global Data Services pools and adding databases to the Global Data Services configuration, the nodes where those databases run must be part of the valid node checking for registration (VNCR) list for database registration. Use the add invitednode (add invitedsubnet) command to define the valid nodes.

Example

Adds database DB1 to the WEST region and Global Data Services pool MYREADERFARM.

GDSCTL> add database -connect 127.0.0.1:1521:db1 -region west -gdspool
   myreaderfarm

Adds a database using myalias instead of the IP address connection string.

GDSCTL> add database -connect myalias -gdspool myreaderfarm

Exceptions or Error Codes

GDSCTL returns the errors listed below if you use this command incorrectly.

Table 2-6 GDSCTL add database Exceptions or Error Codes

Exception	Description
`ERROR-44866`	If a pool already contains an Oracle Data Guard broker configuration, then GDSCTL returns an error; you must add databases using Oracle Data Guard in this case. That is, if a pool contains an Oracle Data Guard broker configuration, then additional databases can only be added to the pool by adding them to that Data Guard broker configuration.
`ERROR-44868`	If the database being added is part of a Oracle Data Guard broker configuration, then GDSCTL returns an error; you must use the add brokerconfig command in this case.