The Oracle Database Appliance software configuration defaults are detailed in the following sections:
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 Users system privileges |
|
|
Oracle ASM Operator system privileges |
|
|
Oracle Database Administrators system privileges |
|
|
Oracle Database Operator system privileges |
|
Table A-3 shows the sizes for DATA, RECO, REDO, and FLASH disk groups on various configurations of Oracle Database Appliance. Each row has values for either normal or for high redundancy levels. The disk capacities shown in the table vary because they are derived by converting disk hardware terabytes (based on 1 kilobyte=1,000 bytes) into data storage terabytes (based on 1 kilobyte=1,024 bytes).
The space calculated with a storage expansion shelf approximately doubles the space mentioned in Table A-3. Note that the storage expansion shelf can only be used in Oracle Database Appliance X3-2, X4-2, and X5-2.
Table A-3 Database Disk Group Sizes for Oracle Database Appliance
| Sizing | Version 1 (GB) | X3-2 and X4-2 (GB) | X5-2 (GB) |
|---|---|---|---|
|
HDD Size |
559 |
838 |
3,600 |
|
Total HDD |
11,180 |
16,760 |
57,600 |
|
Total SSD (REDO Diskgroup) |
272 |
744 |
744 |
|
Total SSD (FLASH Diskgroup |
N/A |
N/A |
1,492 |
|
Total HDD with High Redundancy |
3,727 |
5,587 |
19,200 |
|
Total HDD with Normal Redundancy |
5,590 |
8,380 |
28,800 |
|
DATA Diskgroup with High Redundancy - External Backup |
3,205 |
4,805 |
16,512 |
|
RECO Diskgroup with High Redundancy - External Backup |
522 |
782 |
2,688 |
|
DATA Diskgroup with High Redundancy - Local Backup |
1,603 |
2,402 |
8,256 |
|
RECO Diskgroup with High Redundancy - Local Backup |
2,124 |
3,185 |
10,944 |
|
DATA Diskgroup with Normal Redundancy - External Backup |
4,807 |
7,207 |
24,768 |
|
RECO Diskgroup with Normal Redundancy - External Backup |
783 |
1,173 |
4,032 |
|
DATA Diskgroup with Normal Redundancy - Local Backup |
2,404 |
3,603 |
12,384 |
|
RECO Diskgroup with Normal Redundancy - Local Backup |
3,186 |
4,777 |
16,416 |
|
REDO Diskgroup |
91 |
248 |
248 |
|
FLASH Diskgroup |
N/A |
N/A |
746 |
Note:
High Redundancy is triple-mirroring and Normal Redundancy is double-mirroring. REDO Diskgroup is always High Redundancy. FLASH Diskgroup is always Normal Redundancy.See Also:
"Managing Capacity in Disk Groups" in Oracle Automatic Storage Management Administrator's Guide for more information about determining the amount of free space in your Oracle Database Appliance ASM diskgroups. Table A-3 only provides the raw disk information.Oracle Database Appliance uses the ASM Cluster File System (ACFS) for storage of database and virtual machine files. ACFS provides both servers with concurrent access to some or all of the shared storage on Oracle Database Appliance. ACFS supports space-efficient storage snapshots, which provides fast provisioning databases and virtual machines within Oracle Database Appliance.
There are three types of ACFS file systems that are used in Oracle Database Appliance:
Database
Shared Repositories
General Purpose Storage
Database file systems are used exclusively for storing database files, and they include a FLASH file system for storing database data files and flash cache files, a DATA file system for database data files, a RECO file system for storing archive files and backups, and a REDO file system for storing redo log files.
Shared Repositories are file systems created on Oracle Database Appliance Virtualized Platform, and they are used to store virtual machine templates, run-time images, and virtual disks.
A general purpose cluster file system, cloudfs, is also created by default on every Oracle Database Appliance, and cloudfs can be used for general purpose storage that must be shared between the servers, for example, staging for data loads.
All ACFS file systems are created on ASM Dynamic Volumes provisioned from ASM diskgroups created in the shared disk storage pool. In a bare metal deployment, these file systems are mounted directly in the OS hosting the databases. In a virtualized deployment, these file systems are managed and mounted directly in ODA_BASE.
The various ACFS file systems are mounted in the OS, or in ODA_BASE (Virtualized Platform) in different locations. Table A-4 describes the various mount points and related ASM diskgroups and volume information.
Table A-4 ACFS Mount Points and Related ASM Diskgroups and Volume Information
| File System | ASM Diskgroup | ASM Dynamic Volume | Mount Point |
|---|---|---|---|
|
DATA (Non-CDB) |
+DATA |
/dev/asm/datastore-<nnn> |
/u02/app/oracle/oradata/datastore |
|
RECO (Non-CDB) |
+RECO |
/dev/asm/datastore-<nnn> |
/u01/app/oracle/fast_recovery_area/datastore |
|
REDO (Non-CDB) |
+REDO |
/dev/asm/datastore-<nnn> |
/u01/app/oracle/oradata/datastore |
|
DATA (per CDB) |
+DATA |
/dev/asm/dat<dbname>-<nnn> |
/u02/app/oracle/oradata/dat<dbname> |
|
RECO (per CDB) |
+RECO |
/dev/asm/rco<dbname>-<nnn> |
/u01/app/oracle/fast_recovery_area/rco<dbname> |
|
REDO (per CDB) |
+REDO |
/dev/asm/rdo<dbname>-<nnn> |
/u01/app/oracle/oradata/rdo<dbname> |
|
FLASH |
+FLASH |
/dev/asm/flashdata-<nnn> |
/u02/app/oracle/oradata/flashdata |
|
Shared Repository <name> |
+DATA or +RECO |
/dev/asm/<reponame>-<nnn> |
/u01/app/sharedrepo/<reponame> |
|
General ACFS Storage |
+RECO |
/dev/asm/acfsvol-<nnn> |
/cloudfs (default) |
The ACFS file systems are automatically created when you create a shared repository, or when you create a database. However, the file systems do not initially consume all of the storage in the appliance, preserving space for additional repositories, or in some cases, database files stored directly in ASM. In Oracle Database Appliance software releases 12.1.2.2 and earlier, the ACFS file systems do not automatically extend should they run low on space, even if there is still storage space available in the shared storage pool. You can check for available storage space in your file systems by running the OS command df -h as shown in the following example.
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroupSys-LogVolRoot
30G 8.6G 20G 31% /
/dev/mapper/VolGroupSys-LogVolU01
97G 23G 70G 25% /u01
/dev/mapper/VolGroupSys-LogVolOpt
59G 6.8G 49G 13% /opt
/dev/sda1 99M 26M 68M 28% /boot
tmpfs 127G 1.2G 125G 1% /dev/shm
/dev/asm/datafsvol-352
5.0G 87M 5.0G 2% /odadatafs
/dev/asm/rdocdb1-66
5.0G 4.2G 874M 83% /u01/app/oracle/oradata/rdocdb1
/dev/asm/datcdb1-303
100G 4.2G 96G 4% /u02/app/oracle/oradata/datcdb1
/dev/asm/flashdata-138
558G 1.4G 557G 1% /u02/app/oracle/oradata/flashdata
/dev/asm/rcocdb1-352
132G 788M 132G 1% /u01/app/oracle/fast_recovery_area/rcocdb1
/dev/asm/acfsvol-352 50G 178M 50G 1% /cloudfs
/dev/asm/datastore-66
59G 4.3G 55G 8% /u01/app/oracle/oradata/datastore
/dev/asm/datastore-303
3.6T 2.1G 3.6T 1% /u02/app/oracle/oradata/datastore
/dev/asm/datastore-352
4.8T 10G 4.8T 1% /u01/app/oracle/fast_recovery_area/datastore
If you need to extend the size of one of your file systems to accommodate growth in your data, you must manually expand the pool.
See Also:
"oakcli resize dbstorage" to expand space for database files
"oakcli configure repo" to expand shared repositories
My Oracle Support note 1437717.1 "Expanding /cloudfs File System” at https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1437717.1
Table A-5 System Configuration for Oracle Database Appliance
| Item | Value |
|---|---|
|
Oracle Linux with the Red Hat compatible kernel |
Oracle Linux 5.11 UEK2 |
|
Oracle Grid Infrastructure and Oracle Database Version (initial release) |
|
|
1521 |
|
|
Oracle Enterprise Edition DB control port |
1158 Use: |