Oracle Database Appliance software configuration defaults.
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 |
|
Review the table to see the groups and default users created when you deploy the appliance. All passwords are set to the Master password that you define during deployment.
Oracle Groups and Users Configurations
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 |
|
The tables in this section show the sizes for DATA, RECO, REDO, and FLASH disk groups on various configurations of Oracle Database Appliance.
Each table row has values for either normal or for high redundancy levels. The disk capacities shown in the tables vary, because they are derived by converting disk hardware terabytes (based on 1 kilobyte equals 1,000 bytes) into data storage terabytes (based on 1 kilobyte equals 1,024 bytes).
The space calculated with a storage expansion shelf approximately doubles the space mentioned in these tables.
Note:
The storage expansion shelf can only be used with Oracle Database Appliance X6-2-HA, X5-2, X4-2, and X3-2.
Table A-3 Approximate Database Disk Group Sizes for Oracle Database Appliance X5-2 and X6-2-HA
| Sizing | X5-2 (GB), 4 TB | X5-2 (GB), 8 TB | X6-2-HA (GB), 8 TB |
|---|---|---|---|
|
HDD Size |
3,816 |
7,631 |
7,631 |
|
Total HDD |
61,056 |
122,096 |
122,096 |
|
Total SSD (REDO Disk Group) |
744 |
744 |
744 |
|
Total SSD (FLASH Disk Group) |
1,492 |
1,492 |
1,492 |
|
Total HDD with High Redundancy |
20,352 |
40,699 |
40,699 |
|
Total HDD with Normal Redundancy |
30,528 |
61,048 |
61,048 |
|
DATA Disk Group with High Redundancy - External Backup |
15,315 |
30,626 |
30,626 |
|
RECO Disk Group with High Redundancy - External Backup |
2,493 |
4,986 |
4,986 |
|
DATA Disk Group with High Redundancy - Local Backup |
7,473 |
16,407 |
16,407 |
|
RECO Disk Group with High Redundancy - Local Backup |
9,906 |
21,748 |
21,748 |
|
DATA Disk Group with Normal Redundancy - External Backup |
24,513 |
49,220 |
49,220 |
|
RECO Disk Group with Normal Redundancy - External Backup |
4,007 |
8,013 |
8,013 |
|
DATA Disk Group with Normal Redundancy - Local Backup |
12,307 |
24,610 |
24,610 |
|
RECO Disk Group with Normal Redundancy - Local Backup |
15,920 |
32,623 |
32,623 |
|
REDO Disk Group |
248 |
248 |
248 |
|
FLASH Disk Group |
746 |
746 |
746 |
Note:
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-4 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. The REDO Disk Group is always High Redundancy. The FLASH Disk Group is always Normal Redundancy.
See Also:
Oracle Automatic Storage Management Administrator's Guide, "Managing Capacity in Disk Groups" for more information about determining the amount of free space in your Oracle Database Appliance disk groups for Oracle ASM. The tables in this topic only provide the raw disk information.
The table shows the usage storage available 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 you use the reserve storage capacity, then the system continues to run, and it is protected through ASM mirroring. However, in the event of a second disk failure, the system is then running in a non-protected and degraded mode. In this event, you must replace disks immediately. Refer to Oracle Automatic Storage Management Administrator’s Guide for more information about ASM disk group capacity.
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 |
Related Topics
Review this section to understand Oracle Database Appliance storage architecture and options and how to determine usable storage.
Use Oracle Automatic Storage Management (Oracle ASM) or Oracle Automatic Storage Management Cluster File System (Oracle ACFS) 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 data files 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 data files, and an Oracle ACFS file system is created from RECO diskgroup for redo and fast recovery area for all databases.
Parent topic: Storage on Oracle Database Appliance
Review 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-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 |
+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
Parent topic: Storage on Oracle Database Appliance
The Oracle ACFS file systems are automatically created when you create a database on Oracle Database Appliance.
When you use Oracle ACFS for database storage, the following is 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.
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
Parent topic: Storage on Oracle Database Appliance
Review to see the configuration options for Oracle Database Appliance.
Table A-7 System Configuration for Oracle Database Appliance
| Item | Value |
|---|---|
|
Oracle Linux with the Red Hat-compatible kernel |
Oracle Linux 6.9 with kernel-4.1.12-112.14.1.el6uek.x86_64 |
|
Oracle Database release |
12.1.0.2.180417, 11.2.0.4.180417 Oracle Database Enterprise Edition, Oracle Database Standard Edition 2, Oracle Database Standard Edition 1, Oracle Database Standard Edition |
|
SCAN port number |
1521 |
|
Oracle Enterprise Edition DB control port |
1158 To access Enterprise Manager , enter the following URL string, where
|
Change the administrative account passwords to secure your system.
During deployment, the root and database users SYS, SYSTEM and PDBADMIN are set to the master password. After deployment, the oracle and grid passwords are also set to the master password, which is welcome1.
Note:
Change the passwords to comply with your enterprise user security protocols.
Refer to the Oracle Database Appliance Security Guide and Oracle Database Security Guide for information about the required configuration and best practices to secure database systems.