Database Reference
In-Depth Information
With regard to the policy-managed database configuration, the RAC configuration type and the selection or
creation of a new spool pool is the only different requirement in comparison with a typical admin-based database.
The rest of the database creation steps remain unchanged.
Upgrading a Policy-Managed Database
A direct upgrade of a pre-12c admin-managed database to a 12c policy-managed database is not supported; this will
have to be a combo upgrade/migration process. The following steps are required:
1.
Upgrade the existing pre-12c admin-managed database to 12c.
2.
After successful upgrade, migrate the database to policy-managed using the
srvctl
modify
command, as demonstrated in the subsequent section.
Migrating an Admin-Managed Database to a Policy-Managed Database
This section provides the essential background required to convert an admin-managed database to a policy-managed
database. The following is a practical step-by-step conversion procedure:
1.
Verify and save the existing configuration settings of an admin-managed database plus all
its services:
$ srvctl config database -d
<dbname>
$ srvctl status database -d <dbname>
$ srvctl config service -d
<dbname>
$ srvctl status service -d <dbname>
2.
As the GI/cluster administrator (user), create a new server pool specifying MIN/MAX
servers to the pool in order to place the policy-managed database. Alternatively, a
preexisting/defined server pool can also be used. Use the following example to create a
new server pool:
$ srvctl add srvpool -serverpool
srvpl_pbd
-MIN 0 -MAX 4 -servers
node1,node2,node3,node4 - category <name> -verbose
$ srvctl config srvpool—serverpool
srvpl_pub
—to verify the details
3.
Stop and migrate the database to the newly created server pool to complete the conversion
process:
$ srvctl stop database -d
<dbname>
$ srvctl modify database -d
<dbname>
-serverpool srvpl_pbd
The preceding srvctl modify command converts an admin-managed to a policy-managed database and places
the database into the new policy-managed server pool, named
srvpl_pbd
.
4.
Start and verify the database after the conversion using the following examples:
$ srvctl start database -d
<dbname>
$ srvctl config database -d
<dbname>
