8 Managing Oracle Databases

Manage the Oracle Databases on your Oracle Database Appliance. For an Oracle Database Appliance Virtualized Platform, see the oakcli commands for managing the databases.

Administrative Groups and Users on Oracle Database Appliance

Oracle Database Appliance Web Console deployment creates operating system groups and users whose members are granted system administration privileges on the appliance.

During configuration, two administrative accounts are created for Oracle Database Appliance: the user grid, with a user ID (UID) of 1001, and the user oracle, with a UID of 1000. The user grid is the Oracle Grid Infrastructure installation owner. The user oracle is the Oracle Database installation owner, and the owner of all Oracle Database homes (Oracle homes). By default, these users are members of operating system groups whose members are granted privileges to start up and administer Oracle Database and Oracle Automatic Storage Management.

The following table describes the Oracle system privileges groups, and information about the operating system authentication groups:

Table 8-1 Operating System Groups and Users on Oracle Database Appliance

Oracle System Privileges Group Name Group ID (GID) grid is a member oracle is a member

Oracle Inventory group (OINSTALL)

oinstall

1001

yes (primary group)

yes (primary group

OSOPER for dbaoper group

dbaoper

1002

yes

yes

OSDBA group

dba

1003

no

yes

OSASM Group for Oracle ASM

asmadmin

1004

yes

no

OSOPER for ASM group

asmoper

1005

yes

no

OSDBA for ASM group

asmdba

1006

yes

yes

To change the Group Name and GID from the default values on Oracle Database Appliance bare metal platforms, change the default values from the Web Console during the deployment. If you create an initial database during deployment, then the password for the SYS and SYSTEM users is the Master Password that you set in the Web Console.

To change the Group Name and GID from the default values on the Oracle Database Appliance X7-2-HA Virtualized Platform, use the -advance parameter with the command oakcli deploy. If you create an initial database during deployment, then the password for the SYS and SYSTEM users is the ROOT password from the Configurator.

Note:

Change the password for both users as soon as possible after configuration to prevent unauthorized access to your database using these privileged accounts.

Data Migration and Management and Oracle Database Appliance

Oracle Database Appliance supports the use of standard Oracle Database loading and migration tools.

If you are loading data or migrating data from an existing database to Oracle Database Appliance, then you can use the standard Oracle Database loading and migration tools. These tools include the following:

  • Oracle GoldenGate

  • SQL*Loader

  • Oracle Data Pump

  • transportable tablespaces

  • RMAN

You can also use the RMAN utility to back up and recover databases on Oracle Database Appliance.

Working with Databases

Use the Web Console to display a list of databases, database details, and create and delete databases.

  • Viewing Databases
    Use the Oracle Appliance Manager Web Console to display a list of Oracle databases and database details, create, upgrade, and delete a database in Oracle Database Appliance.
  • Creating a Database
    Use the Oracle Appliance Manager Web Console to create a database in Oracle Database Appliance.
  • Creating an Instance Only Database
    Create an instance only database from the command-line interface.
  • Upgrading a Database
    Use the Oracle Appliance Manager Web Console to upgrade an Oracle database to a different database home version.
  • Deleting a Database
    Use the Oracle Appliance Manager Web Console to delete an Oracle database.

Viewing Databases

Use the Oracle Appliance Manager Web Console to display a list of Oracle databases and database details, create, upgrade, and delete a database in Oracle Database Appliance.

On the Oracle Database Appliance Virtualized Platform, see the command oakcli list databases.
  1. Log into the Web Console:
    https://host name or ip-address:7093/mgmt/index.html
  2. Click the Database tab.
  3. (Optional) Click the database name, in blue font, to display more details about the database.
  4. (Optional) Click Actions next to a database entry to view more details, upgrade or delete the database.

Creating a Database

Use the Oracle Appliance Manager Web Console to create a database in Oracle Database Appliance.

Note:

For Oracle Database Appliance X7-2-HA Virtualized Platforms, see the command oakcli create database to create additional databases.

The Web Console provides a quick and easy method of creating new databases. The Create New Database page in the Web Console is populated with default options for most of the configuration options. Drop-down lists enable you to quickly view and select from a list of available options. You can use the drop-down list to create a new database Oracle Database Home (ORACLE_HOME) for the database or select an existing ORACLE_HOME that you created earlier.

Note:

You cannot mix Oracle Database Standard Edition and Enterprise Edition databases on the same appliance. Your license determines the determines the database edition that you are eligible to create in the appliance.

Oracle Database 12.x is supported on both Oracle Automatic Storage Management (Oracle ASM) and Oracle ASM Cluster file system (ACFS). Oracle Database 11.2 is only supported on Oracle ACFS. When databases are created in Oracle ACFS, each database is configured with its own Oracle ACFS file system for the datafiles and uses the following naming convention: /u02/app/db user/oradata/db unique name. The default size of this mount point is 100 GB.

The fields in the Web Console adjust, depending on which database version you select. For example, if you select database version 11.2.0.4.x, the storage field does not appear in the Web Console because Oracle ACFS is the only option available.
  1. Log into the Web Console:
    https://host-ip-address:7093/mgmt/index.html
  2. Click the Database tab.
  3. Verify that Auto Refresh Disabled appears on the page.
  4. Click Create Database to display the Create New Database page.
  5. Enter the following information on the Create New Database page to configure the database:
    1. In the DB Name field, enter a name for the database. The name db1 appears in the field as an example of a database name, but the field is not populated. You must enter a name.
      The name must contain lowercase alphanumeric characters and cannot exceed 8 characters. The Oracle system identifier (SID) is always set to the database name.
    2. (Optional) In the DB Unique Name field, enter a name to define a unique name for the database.
    3. In the Use Existing DB Home field, select Yes or No.
    4. In the DB Version field, select a database bundle patch number from the drop-down list.
      Available database versions with available clones appear in the list in descending order. Supported versions that are not available in the repository appear in light gray font at the bottom of the list. Search is available for the list. To add a supported version to the repository, download the clone file.
    5. For the CDB option on Oracle Database version 12, select Yes or No, depending on whether or not you want the database to be a container database (CDB). The default is Yes. This option is not available for Oracle Database version 11.
    6. In the PDB Name field, enter a name for the pluggable database (PDB). This field is not available for Oracle Database version 11.
      Alphanumeric characters and underscore (_) are valid. The name must begin with an alphanumeric character and cannot exceed 30 characters. The name pdb1 appears in the field in italic text as an example, but it is not populated. You must enter a name.
    7. In the PDB Admin User field, enter a name. This field is not available for Oracle Database version 11.
      The field shows pdbadmin as an example, you must enter a name. Alphanumeric characters and underscore (_) are valid.
    8. In the Database Edition field, enter the edition for which you have a license, either Enterprise Edition or Standard Edition.
    9. In the Shape field, select a database shape from the drop-down list. The shape determines the number of cores and total memory allocated to the database. The default is odb1 (1 Core, 8 GB Memory).
    10. In the Database Class field, select a database class from the drop-down list. If an option is not available in the list, it is not supported for the database edition on the Oracle Database Appliance or the version that you selected. The default is OLTP.
    11. In the Storage field, select ACFS or ASM from the drop-down list. The default is Oracle ACFS. For Oracle Database version 11, Oracle ACFS is the only option and the field does not appear in the Web Console.
    12. For the Configure EM Express or Configure EM Console option, select Yes or No. The default is No.
      Select Yes to configure the Oracle Enterprise Manager Database Express (EM Express) console for Oracle Database 12.x or the Database Control Console (DB Console) for Oracle Database 11.2.0.4. Selecting Yes enables you to use the console to manage the database.
    13. In the Password field, enter the password for the SYS, SYSTEM, and PDB Admin.
      The password must begin with an alpha character and cannot exceed 30 characters. Quotation marks are not allowed.
    14. In the Confirm Password field, enter the password again to confirm.
    15. In the Characterset field, select an option from the drop-down list. The default is AL32UTF8.
    16. In the National Characterset field, select an option from the drop-down list. The default is AL16UTF16.
    17. In the Language field, select a database language from the drop-down list. The default is American.
    18. In the Territory field, select a territory or location for the database from the drop-down list. The default is America.

    The image shows the fields completed to create a new database. The DB Name is db1 and the DB Unique Name is db1-1. Use Existing DB Home is No and the DB version is 12.2.0.1.170814. The Database Edition is Enterprise Edition, the shape is odb1 (1 Core, 6.0 GB Memory), the Database Class is OLTP, and the Storage is ACFS. database is a container database. The pluggable database (PDB) name is pdb1 and the PDB Admin User is pdbadmin. The Characterset is AL32UTF8, the National Characterset is AL16UTF16, the Language is American, the Territory is America. The database is not configured for EM Console.

  6. Click Create. When prompted, click Yes to confirm that you want to start the job to create the database.
The job is submitted and a confirmation page appears with a link to the job. Click the link to view the job progress, tasks, and status.

After you close the Job confirmation page, you can click the Activity tab to monitor the job progress. Click the job number to view the tasks and status details. Click Refresh to refresh the page. If you are creating other configuration or provisioning jobs, do not turn on auto refresh. When auto refresh is turned on, your input is lost if the page refreshes before you submit your configuration.

Creating an Instance Only Database

Create an instance only database from the command-line interface.

Note:

If you provisioned the appliance without creating an initial database, then you must create a new Oracle home. If the version of the database home is different from the migrated database, create a new database home for the migrated database. You might want to create a database home specifically for the migrated database.

This example creates an instance only database named PRODDB with database version 12.1.0.2.160719 and a new database home.

  1. Use the odacli list-dbhomes command to display a list of database homes and verify that a database home exists for the database version.
    Note the ID if you want to use an existing database home or if you want to get more details. Use the odacli describe-dbhomes command to get greater details about a specific database home.
    # odacli list-dbhomes
ID                                   Name               DB Version  
------------------------------------ -----------------  ----------  
b727bf80-c99e-4846-ac1f-28a81a725df6 OraDB12102_home1  12.1.0.2 
    
(continued)
Home Location
-----------------------------------------
/u01/app/orauser/product/12.1.0.2/dbhome_1
  2. Create a database home if a database home does not exist for the database version.
    If you want to create a database home for specifically for the migrated database, you can use the odacli create-dbhome command, or you can create the database home when you create the database. The example creates a database home for database version 12.1.0.2.
    # odacli  create-dbhome -v 12.1.0.2
  3. Create an instance only database. You can use an existing database home ID or you can create a database home when creating the database.

    To create an instance only database named PRODDB with database version 12.1.0.2 that uses an existing database home with ID b727bf80-c99e-4846-ac1f-28a81a725df6:

    #odacli create-database -n PRODDB -v 12.1.0.2 -io -m -dh b727bf80-c99e-4846-ac1f-28a81a725df6

    To create an instance only database named PRODDB with database version 12.1.0.2 and a database home:

    #odacli create-database -n PRODDB -v 12.1.0.2 -io -m

Upgrading a Database

Use the Oracle Appliance Manager Web Console to upgrade an Oracle database to a different database home version.

Before upgrading to a different database home, you must upload the RDBMS database version to the repository and create the database home.
  1. Log into the Web Console:
    https://host name or ip-address:7093/mgmt/index.html
  2. Click the Database tab.
  3. Click Actions next to the database that you want, then select Upgrade.
  4. Select the destination database home version from the list of available versions, then click Upgrade.

Deleting a Database

Use the Oracle Appliance Manager Web Console to delete an Oracle database.

  1. Log into the Web Console:
    https://host name or ip-address:7093/mgmt/index.html
  2. Click the Database tab.
  3. Click Actions next to the database that you want, then select Delete.
  4. Confirm the action.

Working with Database Homes

Use the Web Console to display a list of database homes, details, and create and delete database homes.

About Managing Multiple Oracle Homes on Oracle Database Appliance

Create and manage one or more Oracle home directories and Oracle databases on Oracle Database Appliance.

Oracle home is the directory in which you install Oracle Database binaries, and from which Oracle Database runs. Oracle Database Appliance supports multiple Oracle homes, including support of different release Oracle Database homes. You can create multiple Oracle databases on a given Oracle home. Use Oracle Appliance Manager Web Console to create and manage multiple Oracle homes and databases on Oracle Database Appliance. Oracle Database Appliance Manager automatically creates an Oracle Database Oracle home that is compliant with Oracle’s Optimal Flexible Architecture (OFA) standards.

Note:

For Oracle Database Appliance X7-2-HA Virtualized Platforms, use the command oakcli create dbhome or the command oakcli delete dbhome to manage database homes. The Web Console is not available for virtualized platforms.

Check the Oracle Database Appliance Release Notes to obtain information about the specific Oracle software releases supported for your Oracle Database Appliance platform.

When you use ODACLI commands to create multiple homes on Oracle Database Appliance, the commands start the Oracle Home cloning process. In Oracle Database Appliance deployments, the user oracle is the default software installation owner.

Note:

If you are not upgrading from an earlier release, then download the Oracle Database Appliance software for the Oracle Database version that you want to install.

For Oracle Database Appliance X7-2-HA Virtualized Platforms, see the command oakcli create database to create additional databases.

You can use the Web Console or the command-line interface to create and manage databases.

Note:

For Oracle Database Appliance X7-2-HA Virtualized Platforms, use the command oakcli create database to create and manage databases. The Web Console is not available for virtualized platforms.

Use ODACLI commands to create, list, describe, and delete databases on Oracle Database Appliance. The odacli create-database command enables you to create a database with minimal user input. When you run this command without any additional options, the command creates a new database home (ORACLE_HOME). You can create a database in an existing home by using the --dbhomeid option. To find the dbhomeid, use the odacli list-dbhomes command.

Alternatively, you can use the Web Console to create list, describe and delete databases and database homes. You can display a list of all Database Homes that includes the database home name, ID, version, the date and time that the database home was created and the location on the same page. You can also create and delete database homes on the Web Console.

Caution:

Do not apply Oracle Database patches directly to Oracle Databases on Oracle Database Appliance. Only use Oracle Database Appliance patch bundles, which are tested to work across the whole software stack. If a one-off database patch is required, it may be applied to the Oracle Home. When you apply the Oracle Database Appliance patch bundle, it may cause a conflict during future patching events and you might need to roll back and then re-apply the patch.

Related Topics

Downloading an RDBMS Clone File

Download an Oracle Database Appliance RDBMS Clone file onto your local machine to create a new database home.

To create Oracle Databases on Oracle Database Appliance, you must first upload the version-specific RDBMS clone file into the Oracle Database Appliance repository. The Oracle Database Appliance RDBMS clone files are available in My Oracle Support (MOS).

The following software clone files contain the Oracle Database software images for Oracle Database Appliance:

  • Use the Oracle 12.2.0.1.x RDBMS Software Clone file to create any new 12.2 database homes.

  • Use the Oracle 12.1.0.2.x RDBMS Software Clone file to create any new 12.1 database homes.

  • Use the Oracle 11.2.0.4.x  RDBMS Software Clone file for creating any new 11.2 database homes.

The Oracle Database Appliance Release Notes contains a list of the patch numbers and links to patches.

  1. From an external client machine, log on to My Oracle Support.
  2. Select the Oracle Database Appliance RDBMS Clone patch for the supported Oracle Database version.
  3. Click Download to download the zip file onto your external client.
  4. Use either a Secure Copy (scp) command or a USB storage device to copy the file from the external client to dom0 on Node0. Use the /tmp directory as the target location.

    Note:

    If you use a USB drive to transfer the file, then format it first as FAT32, ext3, or ext4. NTFS file formats are not supported.

  5. Unzip the patch bundle, then use the command odacli update-repository as root user to update the repository. 
    # cd /tmp
# unzip p23494992_122110_Linux-x86-64.zip
# odacli update-repository -fileName /tmp/oda-sm-12.2.1.1.0-170814-DB-12.2.1.0.zip

Related Topics

Viewing Database Homes

Use the Web Console to display a list of database homes and database home details, including databases associated with a DB home.

  1. Log in to the Web Console:
    https://ip-address:7093/mgmt/index.html
  2. Click the Database tab.
  3. Click Database Home on the left menu to view all database homes. The name, ID, version, location and date and time stamp of when the database home was created appears on the page.
  4. (Optional) Click Actions next to a database home entry, then View Databases to see the databases that are associated with the database home.

Creating a Database Home

Use the Web Console to create database homes in Oracle Database Appliance.

The Create New Database page in the Web Console is populated with default options for most of the configuration options. Drop-down lists enable you to quickly view and select from a list of available options. You can use the drop-down list to create a new database Oracle Database Home (ORACLE_HOME) for the database or select an existing ORACLE_HOME that you created earlier.

Before you can create a database home, the Oracle Database Appliance RDBMS Clone file image must be in the repository.
  1. Log in to the Web Console:
    https://ip-address:7093/mgmt/index.html
  2. Click the Database tab, then click Database Home.
  3. Click Create Database Home.
  4. Select a database version from the list of available versions, then select the database edition, either Enterprise Edition or Standard Edition, per your licensing agreement.
  5. Click Create. When prompted, click Yes to confirm that you want to start the job.

Deleting a Database Home

Use the Web Console to delete an Oracle database home.

You can delete a database home (DB Home) if it is not associated with any databases.
  1. Log into the Web Console:
    https://host name or ip-address:7093/mgmt/index.html
  2. Click the Database tab.
  3. Click Database Home on the left menu to view all database homes. The name, ID, version, location and date and time stamp of when the database home was created appears on the page.
  4. Click Actions next to a database home entry, then Delete, and then confirm the action to delete a database home.

Migrating Databases

Review these topics to learn how to prepare for and migrate an entire database to your Oracle Database Appliance.

  • About Migrating Databases
    You can migrate an entire active container database (CDB) or non-CDB database to an Oracle Database Appliance machine by using the RMAN duplicate command.
  • Configuring a Static Listener
    Configure a static listener before you duplicate a database.
  • Migrating a Database
    Use the RMAN Duplicate command to migrate the entire database to the appliance.
  • Registering a Database
    Use the odacli register-database command to register the migrated database with the appliance.

About Migrating Databases

You can migrate an entire active container database (CDB) or non-CDB database to an Oracle Database Appliance machine by using the RMAN duplicate command.

When using RMAN Duplicate, ensure to have network connectivity from source and target databases:

  • Source database: The existing database to be migrated.

  • Target database: The new database created on an Oracle Database Appliance environment.

If you do not have network connectivity between the source and the target environments, you can use the offline migration method. Offline migration uses RMAN backup sets for duplication, which does not require connectivity to the primary database.

At a high level, the procedure involves the following steps:

  1. Deploy or update Oracle Database Appliance to the latest version.

    Confirm that the provisioning completed successfully.

    • If you have a bare metal platform, use the command odacli list-jobs and the command odacli describe-job to verify the status.

    • If you have a virtualized platform, use the command oakcli list-jobs and the command oakcli describe-job to verify the status.

  2. Create an instance only database from the command-line interface.

    • If you have a bare metal platform, use the command odacli create-database with the instanceonly flag on an Oracle Database Appliance machine. The new database is the target database.

    • If you have a virtualized platform, use the command oakcli create-database with the instanceonly flag on an Oracle Database Appliance machine. The new database is the target database.

    Creating an instance only database also creates the following:

    • ACFS Filesystem used to store the database files

    • Directory structures that are required by the database instance/rman duplicate command

    • Password file for the SYS user

  3. Configure a static listener.

  4. Migrate the existing database to the target database using the backup and restore operations.

  5. Register the migrated database with the appliance.

Configuring a Static Listener

Configure a static listener before you duplicate a database.

The static listener is only required when using RMAN Duplicate command.

Perform the following steps to manually configure the listener.ora file:

  1. Log in as a grid user.
  2. Navigate to /u01/app/12.1.0.2/grid/network/admin/ directory.
  3. Edit the default listener.ora file and append the static database entry. 
    SID_LIST_LISTENER=
   (SID_LIST=
      (SID_DESC=
         (GLOBAL_DBNAME=db_unique_name with domain)
         (ORACLE_HOME=db home)
         (SID_NAME=db unique name)
          (ENVS="TNS_ADMIN=database home/network/admin"))
 )

    For example, the following file is edited for a 12.1.0.2 database named PRODDB in the example.com domain:

    SID_LIST_LISTENER=
 (SID_LIST=
    (SID_DESC=
      (GLOBAL_DBNAME=PRODDB.example.com)
       (ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/dbhome_2)
       (SID_NAME=PRODDB)
            (ENVS="TNS_ADMIN=/u01/app/oracle/product/12.1.0.2/dbhome_2/network/admin"))
 )
  4. Save the file.
  5. Restart the listener. 
    srvctl stop listener -l listener
srvctl start listener -l listener

Migrating a Database

Use the RMAN Duplicate command to migrate the entire database to the appliance.

Before migrating the database, verify that a network connection exists between the source and destination databases.
  1. Verify that the sysdba connection to the auxiliary database is working. Use the password that you defined when you created the database with the --instanceonly flag.  
    sqlplus sys/password@hostname:PORT/GLOBAL_DBNAME as sysdba << EOF
select 1 from dual;
exit;
EOF

    The following example uses the Welcome_12 password for myhost on port 1521 for PRODDB.example.com.

    sqlplus sys/Welcome_12@myhost:1521/PRODDB.example.com as sysdba << EOF
select 1 from dual;
exit;
EOF
  2. As oracle user, set the ORACLE_HOME and ORACLE_SID environment variables. 
    ORACLE_HOME=path of Oracle Home against which the AUX DB is created 
ORACLE_SID=database unique name
  3. Display a list of all database storage configured on the appliance and database storage identifiers (ID).

    Use the odacli list-dbstorages to display the storage IDs for all configured filesystems.

    # odacli list-dbstorages  
ID Type                               DBUnique  Name         Status 
------------------------------------  --------  ----------- ---------- 
68d13446-f26c-49ee-ab75-a393732aa88a   Asm       rdb1       Configured 
ff2023d9-338d-4cff-8bb4-e73a89e32ce4   Acfs      PRODDB     Configured
  4. Display the database storage details, including the DATA, RECO and REDO locations, for each database storage ID.

    For example, use the odacli describe-dbstorage command to display information about the ACFS storage for ID 9fe39332-cc1a-4b4b-8393-165524a6ef6b.

    # odacli describe-dbstorage -i ff2023d9-338d-4cff-8bb4-e73a89e32ce4
DBStorage details 
---------------------------------------------------------------- 
ID: ff2023d9-338d-4cff-8bb4-e73a89e32ce4
DB Name: PRODDB 
DBUnique Name: PRODDB 
DB Resource ID: c5b77384-634e-4dc8-b10b-fa2831d2c59b 
Storage Type: Acfs 
DATA Location: /u02/app/oracle/oradata/PRODDB 
RECO Location: /u03/app/oracle/fast_recovery_area/ 
REDO Location: /u03/app/oracle/redo/ 
State: ResourceState(status=Configured) 
Created: November 22, 2016 12:07:12 PM SGT 
UpdatedTime: November 22, 2016 12:26:39 PM SGT
  5. Duplicate the database.
    Use the RMAN duplicate database command to duplicate the database.
    rman target sys/Welcome__12@source database hostname:PORT
(Continued)
/Service Name auxiliary sys/Welcome_12@Hostname of the target database:1521/service name 
RUN { 
SET NEWNAME FOR DATABASE TO NEW; 
duplicate target database to PRODDB from active database 
SPFILE 
SET cluster_database 'false' 
SET audit_file_dest '/u01/app/oracle/admin/PRODDB/adump' 
SET db_create_file_dest '/u02/app/oracle/oradata/PRODDB' 
SET db_create_online_log_dest_1 '/u03/app/oracle/redo' 
SET db_recovery_file_dest '/u03/app/oracle/fast_recovery_area' 
SET control_files '/tmp/control_PRODDB.ctl' nofilenamecheck; 
}

Registering a Database

Use the odacli register-database command to register the migrated database with the appliance.

The dbclass, dbshape, servicename and password are mandatory for registering the database. The dbclass and dbshape determine the sga_target and pga_target settings. The database init.ora parameters are reset as part of the odacli register-database command. Review the init.ora parameters after registration and ensure that the parameters set correctly.

Note:

For a standby database, open the standby database in READ ONLY mode before executing the odacli register-database command.

  1. If you have Oracle Database version 12.1 with SQL patches, ensure that the sqlpatches are in the Oracle Database Appliance environment. If the patches are not in the environment, copy the $OH/sqlpatch directories from the source database home to the $OH in Oracle Database Appliance before executing the odacli register-database command
    The odacli register-database command invokes the datapatch utility for applying the post patch SQLs. If the source database has any sqlpatches applied that are not present in the Oracle Database Appliance environment, then the datapatch will fail.
  2. If you have Oracle Database version 11.2 with SQL patches, you must roll back any patches applied to the source database that are not part of the installed Oracle Database Bundle patch (BP).
  3. Register the database with Oracle Database Appliance. 
    odacli register-database -c OLTP -s odb1 -sn proddb.example.com -p
Password for SYS:
{
  "jobId" : "317b430f-ad5f-42ae-bb07-13f053d266e2",
  "status" : "Created",
  "message" : null,
  "reports" : [ ],
  "createTimestamp" : "August 08, 2016 05:55:49 AM EDT",
  "description" : "Database service registration with 
                   db service name: proddb.example.com",
  "updatedTime" : "August 08, 2016 05:55:49 AM EDT"
}
rpandrap: ]# odacli describe-job -i "317b430f-ad5f-42ae-bb07-13f053d266e2"

Job details
----------------------------------------------------------------
            ID: 317b430f-ad5f-42ae-bb07-13f053d266e2
   Description: Database service registration with
             db service name: proddb.example.com
        Status: Success
       Created: November 23, 2016 5:55:49 AM EDT
       Message:

Task Name                       Start Time                  
----------------------------- ------------------------------ 
restore control file           November 23, 2016 5:55:49 AM EDT 
move spfile to right location  November 23, 2016 5:56:08 AM EDT  
register DB with clusterware   November 23, 2016 5:56:13 AM EDT  
reset db parameters            November 23, 2016 5:57:05 AM EDT  
Running DataPatch              November 23, 2016 5:57:36 AM EDT  

(Continued)
  End Time                     Status
------------------------------- --------
November 23, 2016 5:56:08 AM EDT   Success
November 23, 2016 5:56:13 AM EDT   Success
November 23, 2016 5:57:05 AM EDT   Success
November 23, 2016 5:57:36 AM EDT   Success
November 23, 2016 5:57:49 AM EDT   Success
  4. Use the odacli list-databases command to view the registered database.

About Managing Multiple Database Instances Using Instance Caging

Use instance caging to manage your system resources on Oracle Database Appliance.

Oracle Database provides a method for managing CPU allocations on a multi-CPU server that runs multiple database instances. This method is called instance caging. Instance caging uses an initialization parameter to limit the number of CPUs that an instance can use simultaneously.

Instance caging and Oracle Database Resource Manager (the Resource Manager) work together to support your desired service levels across multiple instances. Consolidation can minimize idle resources, maximize efficiency, and lower costs.

Oracle Database Appliance templates are already tuned for the size of each database instance workload. They are designed to run on a specific number of cores. Instance caging ensures that each database workload is restricted to the set of cores allocated by the template, enabling multiple databases to run concurrently with no performance degradation, up to the capacity of Oracle Database Appliance. You can select database template sizes larger than your current needs to provide for planned growth.

Note:

Oracle strongly recommends that you use the Oracle Database Appliance templates, because they implement best practices and are configured specifically for Oracle Database Appliance.

The Oracle Database Appliance Manager interface refers to the database sizing templates as database classes.

By default, instance caging is not enabled on Oracle Database Appliance. To enable instance caging, set the initialization parameter, RESOURCE_MANAGER_PLAN, for each database on Oracle Database Appliance. The parameter specifies the plan to be used by the Resource Manager for the current instance. Setting this parameter directs the Resource Manager to allocate core resources among databases. If a plan is not specified with this parameter, then the Resource Manager and instance caging are not enabled.

Instance caging allocation of core resources is enabled in accordance with the Oracle Database Appliance database template size that you select for each database. The CPU_COUNT initialization parameter is set in the template. Use the CPU_COUNT setting that matches the size of each database to consolidate, and follow the standard instructions for configuring instance caging.

Oracle EM Express and DB Console

You can use Oracle Enterprise Manager Database Express (EM Express), or the Database Control Console (DB Console) to manage your database.

The EM Express console is available for Oracle Database 12.2.0.1 or 12.1.0.2. The DB Console is available for Oracle Database 11.2.0.4. Both consoles are web-based tools for managing Oracle Databases.

The EM Express console provides the following features:

  • Support for basic administrative tasks, such as storage and user management

  • Comprehensive solutions for performance diagnostics and tuning

  • Performance advisors in a graphic user interface

  • Oracle Database utilities in a graphic user interface, such as SQL*Loader and Oracle Recovery Manager (RMAN)

EM Express is built inside the database server and cannot perform actions outside the database.