This appendix provides the Oracle Database Appliance software configuration defaults.
Topics:
Oracle homes on Oracle Database Appliance follow Optimal Flexible Architecture guidelines.
Table A-1 Directory Paths for Oracle Database Appliance
Item | Directory Path |
---|---|
Grid home |
|
Grid base |
|
Oracle home |
|
Oracle base |
|
Oracle Inventory |
|
Oracle Groups and Users Configurations When Using the Web Console
The table shows the groups and default users when you use the Web Console to deploy the appliance. All passwords are set to the Master password that you define during deployment.
Table A-2 Oracle Groups and Users Configuration for Oracle Database Appliance
Groups and Users | Default Value |
---|---|
Oracle Grid Infrastructure installation owner |
|
Oracle Database installation owner |
|
Oracle Database system administrator |
|
Oracle Database generic administrator |
|
Oracle Inventory system privileges group |
|
Oracle ASM Administrators system privileges |
|
Oracle ASM Users system privileges |
|
Oracle ASM Operator system privileges |
|
Oracle Database Administrators system privileges |
|
Oracle Database Operator system privileges |
|
Oracle Groups and Users Configurations When Using the Command-line Interface
When you use odacli create-appliance
and a JSON file to deploy the appliance, the following options are supported:
Role separation: Enables you to create six (6) groups and two (2) users. You can customize groupname
, username
, and UID
.
Without role separation: Enables you to create two (2) groups and one (1) user. You can customize groupname
, username
, and UID
For information about job role separation, see https://docs.oracle.com/database/121/CWSOL/usrgrps.htm#CWSOL763.
Use Oracle Automatic Storage Management Cluster File System (Oracle ACFS) or Oracle Automatic Storage Management (Oracle ASM) for database files storage.
Database file systems are used exclusively for storing database files, and they include a DATA file system for database data files and a RECO file system for storing archive files and backups. Oracle Database Appliance supports Oracle ACFS and Oracle ASM database file storage. You determine the type of database storage when you create the database.
About Oracle ASM Database Storage
Use Oracle ASM with Oracle Database 12c release 1 (12.1.0.2).
With Oracle ASM, database datafiles are stored in DATA diskgroup. Redo and archive files are in RECO diskgroup.
About Oracle ACFS Database Storage
Use Oracle ACFS with Oracle Database 12c release 1 (12.1.0.2) or Oracle Database 11g release 2 (11.2.0.4).
With Oracle ACFS, an Oracle ACFS file system is created from DATA diskgroup for each database to store datafiles, and an Oracle ACFS file system is created from RECO diskgroup for redo and fast recovery area for all databases.
This topic describes the Oracle ASM Cluster file system (ACFS) mount points for Oracle Database Appliance.
If you select Oracle Automatic Storage Management (Oracle ASM) for database storage when you create a database, then an Oracle ASM Cluster file system (ACFS) is not created. All files are in an Oracle ASM diskgroup.
If you select Oracle ACFS for database storage, then each database has its own Oracle ACFS mount point:
DATA diskgroup: /u02/app/oracleuser/oradata/db_name
RECO diskgroup: /u03/app/oracleuser
.
With Oracle ACFS, the following are created:
A 100G ACFS is created from +DATA diskgroup for each database. This Oracle ACFS automatically extends the space on demand.
A common Oracle ACFS with 25% of +RECO diskgroup is created with auto extension on. This file system is used for fast recovery area and redo logs for all databases.
Table A-3 Oracle ACFS Mount Points and Related Oracle ASM Disk Groups and Volume Information
File System | Oracle ASM Disk Group | Oracle ASM Dynamic Volume | Mount Point |
---|---|---|---|
DATA |
+DATA |
For example: |
For example: |
RECO |
+RECO |
|
This mount point is shared by all databases for For For redo logs, the path is: |
Example A-1 Oracle ACFS Storage Space
When the Oracle ACFS file systems are created, they do not initially consume all of the storage in the appliance. Space is preserved for additional repositories, or in some cases, database files stored directly in Oracle ASM. You can check for available storage space in your file systems by running the operating system command df -k
as shown in the following example.
# df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroupSys-LogVolRoot 30963708 14203568 15187276 49% / tmpfs 65952292 647800 65304492 1% /dev/shm /dev/sda1 495844 43872 426372 10% /boot /dev/mapper/VolGroupSys-LogVolOpt 61927420 18594420 40187272 32% /opt /dev/mapper/VolGroupSys-LogVolU01 103212320 49621560 48347880 51% /u01 /dev/asm/reco-62 76546048 1469676 75076372 2% /u03/app/oracle /dev/asm/datrdb2-268 104857600 3872368 100985232 4% /u02/app/oracle/oradata/rdb2 /dev/asm/datndb11-268 104857600 247160 104610440 1% /u02/app/oracle/oradata/ndb11 /dev/asm/datndb12-268 104857600 247160 104610440 1% /u02/app/oracle/oradata/ndb12
Table A-4 System Configuration for Oracle Database Appliance
Item | Value |
---|---|
Oracle Linux with the Red Hat-compatible kernel |
Oracle Linux 6.7 with kernel-uek-2.6.39-400.276.1.el6uek.x86_64 |
Oracle Grid Infrastructure and Oracle Database release (initial release) |
Release 12.1.2.7: Oracle Database Standard Edition 2 (12.1.0.2), Oracle Database Enterprise Edition (12.1.0.2 , 11.2.0.4 ) |
Oracle Enterprise Manager Express |
1158 To access Oracle Enterprise Manager, enter the following URL string, where
|