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 and Table A-4, and show 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, and Table A-4. Note that the storage expansion shelf can only be used in Oracle Database Appliance X3-2, X4-2, and X5-2.
Table A-3 Approximate Database Disk Group Sizes for Oracle Database Appliance Version 1, X3-2, and X4-2
Sizing | Version 1 (GB) | X3-2 (GB) | X4-2 (GB) |
---|---|---|---|
HDD Size |
559 |
838 |
838 |
Total HDD |
11,180 |
16,760 |
16,760 |
Total SSD (REDO Disk Group) |
272 |
744 |
744 |
Total SSD (FLASH Disk Group) |
N/A |
N/A |
N/A |
Total HDD with High Redundancy |
3,727 |
5,587 |
5,587 |
Total HDD with Normal Redundancy |
5,590 |
8,380 |
8,380 |
DATA Disk Group with High Redundancy - External Backup |
3,205 |
4,805 |
4,805 |
RECO Disk Group with High Redundancy - External Backup |
522 |
782 |
782 |
DATA Disk Group with High Redundancy - Local Backup |
1,603 |
2,402 |
2,402 |
RECO Disk Group with High Redundancy - Local Backup |
2,124 |
3,185 |
3,185 |
DATA Disk Group with Normal Redundancy - External Backup |
4,807 |
7,207 |
7,207 |
RECO Disk Group with Normal Redundancy - External Backup |
783 |
1,173 |
1,173 |
DATA Disk Group with Normal Redundancy - Local Backup |
2,404 |
3,603 |
3,603 |
RECO Disk Group with Normal Redundancy - Local Backup |
3,186 |
4,777 |
4,777 |
REDO Disk Group |
91 |
248 |
248 |
FLASH Disk Group |
N/A |
N/A |
N/A |
Note:
High Redundancy is triple-mirroring and Normal Redundancy is double-mirroring. REDO Disk Group is always High Redundancy. FLASH Disk Group 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 disk groups for Oracle ASM. Table A-3 only provides the raw disk information.Table A-4 Approximate Database Disk Group Sizes for Oracle Database Appliance X5-2
Sizing | X5-2 (GB), 4 TB | X5-2 (GB), 8 TB |
---|---|---|
HDD Size |
3,816 |
7,631 |
Total HDD |
61,056 |
122,096 |
Total SSD (REDO Disk Group) |
744 |
744 |
Total SSD (FLASH Disk Group) |
1,492 |
1,492 |
Total HDD with High Redundancy |
20,352 |
40,699 |
Total HDD with Normal Redundancy |
30,528 |
61,048 |
DATA Disk Group with High Redundancy - External Backup |
15,315 |
30,626 |
RECO Disk Group with High Redundancy - External Backup |
2,493 |
4,986 |
DATA Disk Group with High Redundancy - Local Backup |
7,473 |
16,407 |
RECO Disk Group with High Redundancy - Local Backup |
9,906 |
21,748 |
DATA Disk Group with Normal Redundancy - External Backup |
24,513 |
49,220 |
RECO Disk Group with Normal Redundancy - External Backup |
4,007 |
8,013 |
DATA Disk Group with Normal Redundancy - Local Backup |
12,307 |
24,610 |
RECO Disk Group with Normal Redundancy - Local Backup |
15,920 |
32,623 |
REDO Disk Group |
248 |
248 |
FLASH Disk Group |
746 |
746 |
Notes:
For non-CDB databases, the REDO disk group has 50% free disk space.
For CDB databases, an Oracle ACFS mount point is created per CDB database, based on the template log file size. If this is a Single Instance (SI) database, then multiply by 3. If the is an Oracle RAC database, then multiply by 4.
Accelerator volume size is 0.4% of the database DATA Oracle ACFS file system size and shared REPO Oracle ACFS file system size.
Table A-5 shows the usage storage for various configurations of Oracle Database Appliance X5-2.
The reserved storage is the amount of ASM storage required to maintain redundancy in the event of a disk failure. If a customer uses the reserve storage capacity, the system will continue to run and be protected through ASM mirroring. However, in the event of a second disk failure, the system will be running in a non-protected and degraded mode, and the disk needs to be replaced immediately.
For more ASM Disk Groups Capacity information, see:
>http://docs.oracle.com/cd/B28359_01/server.111/b31107/asmdiskgrps.htm#CHDGGGA
Table A-5 Usable Storage on Oracle Database Appliance X5-2
Sizing | Raw Value (GB) | Reserve (GB) | Usable (GB) |
---|---|---|---|
Total SSD (REDO Disk Group) (based on an estimated 190,780 GB) See the Note. |
764 |
191 |
191 |
Total SSD (FLASH Disk Group) (based on an estimated 3,816 GB) |
1,528 |
382 |
573 |
HDD Size: 8 TB |
7,631 |
||
External Backup/Normal Redundancy (86%/14% split) |
|||
DATA Disk Group with Normal Redundancy - External Backup |
105,003 |
6,563 |
49,220 |
RECO Disk Group with Normal Redundancy - External Backup |
17,093 |
1,068 |
8,013 |
External Backup/High Redundancy |
|||
DATA Disk Group with High Redundancy - External Backup |
105,003 |
13,125 |
30,626 |
RECO Disk Group with High Redundancy - External Backup |
17,093 |
2,137 |
4,986 |
Internal Backup/Normal Redundancy (43%/57% split) |
|||
DATA Disk Group with Normal Redundancy - Internal Backup |
52,501 |
3,281 |
24,610 |
RECO Disk Group with Normal Redundancy - Internal Backup |
69,595 |
4,350 |
32,623 |
Internal Backup/High Redundancy |
|||
DATA Disk Group with High Redundancy - Internal Backup |
52,501 |
3,281 |
16,407 |
RECO Disk Group with High Redundancy - Internal Backup |
69,595 |
4,350 |
21,748 |
HDD Size: 4 TB (Total: HDD Raw: 59,584 GB) |
3,816 |
||
External Backup/Normal Redundancy (86%/14% split) |
|||
DATA Disk Group with Normal Redundancy - External Backup |
52,508 |
3,282 |
24,613 |
RECO Disk Group with Normal Redundancy - External Backup |
8,548 |
534 |
4,007 |
External Backup/High Redundancy |
|||
DATA Disk Group with High Redundancy - External Backup |
52,508 |
6564 |
15,315 |
RECO Disk Group with High Redundancy - External Backup |
8,548 |
1,068 |
2,493 |
Internal Backup/Normal Redundancy (43%/57% split) |
|||
DATA Disk Group with Normal Redundancy - Internal Backup |
26,254 |
1,641 |
12,307 |
RECO Disk Group with Normal Redundancy - Internal Backup |
33,963 |
2,123 |
15,920 |
Internal Backup/High Redundancy |
|||
DATA Disk Group with High Redundancy - Internal Backup |
25,621 |
3,203 |
7,473 |
RECO Disk Group with High Redundancy - Internal Backup |
33,963 |
4,245 |
9,906 |
Oracle Database Appliance uses the Oracle Automatic Storage Management Cluster File System (Oracle ACFS) for storage of database and virtual machine files. Oracle ACFS provides both servers with concurrent access to some or all of the shared storage on Oracle Database Appliance. Oracle ACFS supports space-efficient storage snapshots, which provides fast provisioning databases and virtual machines within Oracle Database Appliance.
Three types of Oracle ACFS file systems 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, runtime images, and virtual disks.
A general-purpose cluster file system, cloudfs, is also created by default on every Oracle Database Appliance. Cloudfs can be used for general purpose storage that must be shared between the servers (for example, staging for data loads).
All Oracle ACFS file systems are created on Oracle ASM Dynamic Volumes provisioned from disk groups created in the shared disk storage pool. In a bare metal deployment, these file systems are mounted directly in the operating system hosting the databases. In a virtualized deployment, these file systems are managed and mounted directly in ODA_BASE.
The various Oracle ACFS file systems are mounted in the operating system, or in ODA_BASE (Virtualized Platform) in different locations. Table A-6 describes the various mount points and related Oracle ASM disk groups and volume information.
Table A-6 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 (Non-CDB) |
+DATA |
/dev/asm/datastore- |
/u02/app/oracle/oradata/datastore |
RECO (Non-CDB) |
+RECO |
|
|
REDO (Non-CDB) |
+REDO |
|
|
DATA (per CDB) |
+DATA |
/ |
|
RECO (per CDB) |
+RECO |
|
|
REDO (per CDB) |
+REDO |
|
|
FLASH |
+FLASH |
|
/u02/app/oracle/oradata/flashdata |
Shared Repository <name> |
+DATA or +RECO |
|
|
General ACFS Storage |
+RECO |
|
|
The Oracle 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 which preserves space for additional repositories, or in some cases, database files stored directly in Oracle ASM. In Oracle Database Appliance software releases 12.1.2.2 and earlier, the Oracle ACFS file systems do not automatically extend if they run low on space, even if storage space is still available in the shared storage pool. You can check for available storage space in your file systems by running the operating system 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
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-7 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) |
Release 12.1.2.5.0: Oracle Database 12c Release 1 (12.1.0.2) with PSU5, optionally Oracle Database 11g Release 2 (11.2.0.4) with PSU8, and Oracle Database 11g Release 2 (11.2.0.3) with PSU16 Release 12.1.2.4.0: Oracle Database 12c Release 1 (12.1.0.2) with PSU4, optionally Oracle Database 11g Release 2 (11.2.0.4) with PSU7, and Oracle Database 11g Release 2 (11.2.0.3) with PSU15 Release 12.1.2.3.0: Oracle Database 12c Release 1 (12.1.0.2) with PSU3, optionally Oracle Database 11g Release 2 (11.2.0.4) with PSU6, and Oracle Database 11g Release 2 (11.2.0.3) with PSU14 Release 12.1.2.2.0: Oracle Database 12c Release 1 (12.1.0.2) with PSU2, optionally Oracle Database 11g Release 2 (11.2.0.4) with PSU5, and Oracle Database 11g Release 2 (11.2.0.3) with PSU13 Release 12.1.2.1.0: Oracle Database 12c Release 1 (12.1.0.2) with PSU1, optionally Oracle Database 11g Release 2 (11.2.0.4) with PSU4, and Oracle Database 11g Release 2 (11.2.0.3) with PSU12 Release 12.1.2: Oracle Database 12c Release 1 (12.1.0.2.0) and optionally 11.2.0.2.12, 11.2.0.3.11, and 11.2.0.4.3 Release 2.10: Oracle Database 11g Release 2 (11.2.0.4.2 with PSU2), optionally Oracle Database 11g Release 11.2.0.2 with PSU9, and 11.2.0.2.12 and 11.2.0.3.10 Release 2.9: Oracle Database 11g Release 2 (11.2.0.2.12, 11.2.0.3.9 and 11.2.0.4.1), with DB PSU1 Release 2.8: Oracle Database 11g Release 2 (11.2.0.2.12 and 11.2.0.3.8 with PSU8, and 11.2.0.4) Release 2.7: Oracle Database 11g Release 2 (11.2.0.2.11 and 11.2.0.3.7), with PSU7 Release 2.6: Oracle Database 11g Release 2 (11.2.0.3), with PSU6 Release 2.5.5: Oracle Database 11g Release 2 (11.2.0.3), with PSU5 Release 2.5: Oracle Database 11g Release 2 (11.2.0.3), with PSU5 Release 2.4: Oracle Database 11g Release 2 (11.2.0.3), with PSU4 Release 2.3: Oracle Database 11g Release 2 (11.2.0.3), with PSU3 Release 2.2: Oracle Database 11g Release 2 (11.2.0.3), with PSU2 Release 2.1.0.3: Oracle Database 11g Release 2 (11.2.0.2), with PSU7 Release 2.1.0.3: Oracle Database 11g Release 2 (11.2.0.2), with PSU5 Release 2.1: Oracle Database 11g Release 2 (11.2.0.2), with PSU3 and patches 12639177 (ASM), 12914151 (MLR on Grid Infrastructure PSU3), and 12419331 (Database PSU3) |
1521 |
|
Oracle Enterprise Edition DB control port |
1158 Use: |