Manage the Oracle Databases on your Oracle Database Appliance.
Topics:
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 7-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) |
|
1001 |
yes (primary group) |
yes (primary group |
|
OSOPER for dbaoper group |
|
1002 |
yes |
yes |
|
OSDBA group |
|
1003 |
no |
yes |
|
OSASM Group for Oracle ASM |
|
1004 |
yes |
no |
|
OSOPER for ASM group |
|
1005 |
yes |
no |
|
OSDBA for ASM group |
|
1006 |
yes |
yes |
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. Change this password for both users as soon as possible after configuration to prevent unauthorized access to your database using these privileged accounts.
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.
You can use Oracle Enterprise Manager Database Express, also known as EM Express, to manage your database.
Oracle Enterprise Manager Database Express is a web-based tool for managing Oracle Database 12c. Oracle Enterprise Manager Database Express is installed with Oracle Database on the Oracle Database Appliance.
Oracle Enterprise Manager Database Express 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)
See Also:
Oracle Database 2 Day DBACreate 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 ODACLI commands 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.
Check the related Readme files or the Release Notes to obtain information about the specific Oracle software releases supported for your Oracle Database Appliance platform. For information about supported releases, refer to My Oracle Support note 888888.1.
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 software installation owner account that owns the Oracle homes.
Note:
If you are not upgrading from an earlier release, then download the Oracle Database Appliance End-User Bundle for the Oracle Database version that you want to install. See My Oracle Support note 888888.1 and 2144642.1 for more details.
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 a database.
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.
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 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.
See Also: