Add databases to the cloud that are smaller than 100MB and do not have dbspaces.
The database must be version 10 or later.
The user ID and password for a database user:
For version 12 and earlier databases, the user must have DBA authority.
For version 17 and later databases, the user must have the equivalent of the SYS_AUTH_DBA_ROLE compatibility role.
The user ID is stored in the cloud and is used later to connect to the database to perform administrative tasks. The password is discarded once the database has been added to the cloud.
The cloud user must have the AddDatabase cloud privilege.
Conform to the database requirements.
If a database is larger than 100 MB or has dbspaces, then use the Cloud Add Database utility (dbcloudadd) instead.
A database is always upgraded when it is added to the cloud. By default, the database is upgraded to a version 17 database. When upgrading to a version 16 or later database, the default in the Cloud Console is to set the system procedures to execute with the privileges of the invoker.
When specifying a name for the database in the cloud, ensure that it is a unique name among all tenant databases in the cloud and that it conforms to the tenant database name restrictions.
The database is uploaded, upgraded, and prepared to run in the cloud. The database is restarted in the cloud unless it is configured to autostart.
To ensure the availability of your database, set up mirroring. Mirroring involves two cloud servers running the primary and mirror databases, and one cloud server running as the arbiter, which negotiates which database is the read-write copy.