Managing Oracle Exadata Databases

When you launch an Exadata DB system, an initial Database Home and database are created in that system. You can create additional Database Homes and databases in that DB system at any time by using the Console or the Oracle Cloud Infrastructure API.

When you add a database to an Exadata DB system, the database versions you can select from depend on the current patch level of that DB system. You might have to patch your DB system to add later database versions.

After you provision a database, you can move it to another Database Home. Consolidating databases under the same home can facilitate management of these resources. All databases in a given Database Home share the Oracle Database binaries and therefore, have the same database version. The Oracle-recommended way to patch a database to a version that is different from the current version is to move the database to a home running the target version. For information about patching the DB system, see Patching an Exadata DB System.


When provisioning databases, make sure your Exadata DB system has enough OCPUs enabled to support the total number of database instances on the system. Oracle recommends the following general rule: for each database, enable 1 OCPU per node. See To scale an Exadata DB system for information on scaling your OCPU count up or down.

You can also add and remove databases, and perform other management tasks on a database by using command line utilities. For information and instructions on how to use these utilities, see Managing Exadata Databases Manually.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in.

For administrators: The policy in Let database admins manage DB systems lets the specified group do everything with databases and related Database resources.

If you are new to policies, see Getting Started with Policies and Common Policies. If you want more information about writing policies for databases, see Details for the Database Service.

Using the Console

To create a new database in an existing Exadata DB system
To create a database from a backup
To move a database to another Database Home
To terminate a database

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use these API operations to manage databases.

For the complete list of APIs for the Database service, see Database Service API.

Changing the Database Passwords

The password that you specify in the Database Admin Password field when you create a new Exadata DB system or database is set as the password for the SYS, SYSTEM, TDE wallet, and PDB Admin credentials. Use the following procedures if you need to change passwords for an existing database.

Note that if you are enabling Data Guard for a database, the SYS password and the TDE wallet password of the primary and standby databases must all be the same.

To change the SYS password for an Exadata DB system database
To change the TDE wallet password for an Exadata DB system database