Previous Next JavaScript must be enabled to correctly display this content

## A Oracle Database Appliance Software Configuration Defaults

Oracle Database Appliance software configuration defaults.

- Directory Paths for Oracle Database Appliance
  Understand the storage and mount configuration file paths for Oracle Database Appliance.
- Port Numbers and Protocols of Oracle Database Appliance Components
  Understand the port numbers and protocols of Oracle Database Appliance components.
- Location of Log Files
  Log files are available for actions performed in the command-line interface and Browser User Interface and are useful when you need to track and debug jobs.
- Oracle Groups and User Configurations for Oracle Database Appliance
  Review the groups and default users created when you deploy the appliance. All passwords are set to the password that you define during deployment.

### Directory Paths for Oracle Database Appliance

Understand the storage and mount configuration file paths for Oracle Database Appliance.

Directory Paths for Oracle Database Appliance

Oracle homes on Oracle Database Appliance follow Optimal Flexible Architecture guidelines.

Item | Directory Path
--- | ---
Grid home | `/u01/app/release-specific_name/gi owner`
Grid base | `/u01/app/gi owner`
Oracle home | `/u01/app/odaorahome/rdbms owner/product/rdbms_version/dbhome_home_sequence_number`
Oracle base | `/u01/app/odaorabase/rdbms owner`
Oracle Inventory | `/u01/app/oraInventory`
Java Runtime Environment (JRE) | `/opt/oracle/dcs/java/release_specific_JRE_version/`
Java SDK | `/opt/oracle/dcs/odajavasdk/`
Oracle ACFS file system | `/opt/oracle/oak/pkgrepos/orapkgs/clones` Starting with Oracle Database Appliance release 19.12, a new Oracle ACFS file system is created to store the Oracle Database and Oracle Grid Infrastructure clone files. The DATA disk group provides a space of 150 GB for the file system.

Parent topic: Oracle Database Appliance Software Configuration Defaults

### Port Numbers and Protocols of Oracle Database Appliance Components

Understand the port numbers and protocols of Oracle Database Appliance components.

Table A-1 Port Numbers and Protocols of Oracle Database Appliance Components

Component | Description | Default Port Number | Protocol | Network
--- | --- | --- | --- | ---
BUI | A web-based application to administer and manage the Oracle Database Appliance. | 7093 | TCP | public
dcs-agent | The DCS agent is a REST application that performs various operations on the appliance. | 7070, 7071 | TCP | public and private
dcs-admin | This application performs lifecycle management operations on the DCS agent, DCS controller, ODACLI, and other components. | 7060 | TCP | public and private
MySQL | The metadata store used by DCS agent. | 3306 | TCP | private
Oracle HAMI | Oracle High Availability Metadata Infrastructure service providing distributed services required by DCS including locking and synchronizing configuration details in the cluster. | 22001 | TCP | private
oakd | Managing the storage components of Oracle Database Appliance. | Dynamic | TCP | private
Oracle ASR Manager | Oracle Auto Service Request. Refer to Oracle Auto Service Request documentation for other ports used by ASR Manager. | 16161 | TCP | public
Oracle ILOM/IPMI | Oracle ILOM for Oracle Database Appliance servers. | 623 | UDP | public
Oracle Database listeners | Database listeners, including local listener and SCAN listener. | 1521 | TCP | public
Oracle ASM Listener | Oracle ASM listener | 1525 | TCP | private
EM Express | Oracle Enterprise Manager Database Express (EM Express). | 5500 and increment one per database | TCP | public
ssh | SSH connection to the Oracle Database Appliance servers. | 22 | SSH over TCP | public and private
VNC Server | The VNC server created by KVM for KVM virtual guest machines | 5900+ | TCP | localhost (127.0.0.1)
NFS | The central repository on bare metal system is shared by the DB Systems using NFS. Refer to the Oracle Linux documentation to identify ports used by NFS. | 2049 - nfs | TCP | private

Note: IP addresses of the private network that Oracle Database Appliance uses are 192.168.16.0/24 and 192.168.17.0/24.

Related Topics

- Port Numbers and Protocols of Oracle Components

See Also:

Oracle Real Application Clusters Installation Guide for Linux and UNIX for port numbers and protocols used by Oracle Database components

Parent topic: Oracle Database Appliance Software Configuration Defaults

### Location of Log Files

Log files are available for actions performed in the command-line interface and Browser User Interface and are useful when you need to track and debug jobs.

You can also use the Oracle Appliance Manager Browser User Interface to view job activity, including the tasks that make up the job. The status of each task appears in the Browser User Interface and you can drill down to get greater details.

If you log a Service Request, upload all of the logs in the `/opt/oracle/dcs/log`, `/opt/oracle/dcs/da/da_repo`, and `/opt/oracle/dcs/dcscli/log` directories.

Patching Log Files

All patching-related information is logged in the `dcs-agent` log in the directory `/opt/oracle/dcs/log/`.

Error Correlation Reports

If a DCS job fails, an Error Correlation report is generated and is available in the `/opt/oracle/dcs/da/da_repo` directory.

DCS Agent Log Directories

Agent-specific activities are logged in the `dcs-agent` log.

The DCS Agent, controller, and command-line interface output are stored in the directory `/opt/oracle/dcs/log/`.

If an error occurs in the command-line interface layer, then the output will show in the `/opt/oracle/dcs/dcscli/log/dcscli.log` file first.

DCS Components Log Directories

The Oracle HAMI logs are stored in the directory `/opt/oracle/hami/base`, `/opt/oracle/hami/obase`, and `/opt/oracle/dcs/hami/log`. The Oracle HAMI logs are `hamiws_pid_n.trc`, `hamictl_timestamp_pid.log`, and `hamiwsmkwallets_pid.trc`.

The MySQL logs are stored in the log `/opt/oracle/dcs/mysql/log/mysqldb.log`. The log contains information about MySQL such as startup, shutdown, connection transaction details, and errors encountered when running MySQL.

Storage Logs

Storage-related activity is logged in the `oakd` log file.

    /opt/oracle/oak/log/hostname/oak/oakd.log

For example, `/opt/oracle/oak/log/myhost/oak/oakd.log`

Use the `odaadmcli manage diagcollect` command to collect diagnostic logs for storage components. The files are saved in the `oakdiag` directory.

    /opt/oracle/oak/log/hostname/oakdiag/file name.tar.gz

For example,`/opt/oracle/oak/log/myhost/oakdiag/oakStorage-myhost-20161120_2217.tar.gz`

Upgrade using Data Preserving Reprovisioning Logs

The `odaupgradeutil` utility logs are stored at `opt/oracle/oak/restore/log`.

Database Logs

Online logs are stored in the `/u03/app/db_user/redo/` directory.

Oracle Fast Recovery Area (FRA) is located in the `/u03/app/db_user/fast_recovery_area` directory.

Database alert logs are stored in the location `$ORACLE_BASE/diag/rdbms/database_unique_name`.

Oracle Auto Service Request (Oracle ASR) Log Files

All log files for Oracle ASR are located in the `/var/opt/asrmanager/log/` directory.

Parent topic: Oracle Database Appliance Software Configuration Defaults

### Oracle Groups and User Configurations for Oracle Database Appliance

Review the groups and default users created when you deploy the appliance. All passwords are set to the password that you define during deployment.

Default Operating System Groups and User Configurations

Table A-2 Default Operating System Groups and Users Configuration for Oracle Database Appliance

Groups and Users | Default Value
--- | ---
Oracle Grid Infrastructure installation owner | `grid`, UID 1001
Oracle Database installation owner | `oracle`, UID 1000
Oracle Database system administrator | `sys`
Oracle Database generic administrator | `system`
Oracle Inventory system privileges group | `oinstall`, GID 1001
Oracle ASM Administrators system privileges | `asmadmin`, GID 1004
Oracle ASM Users system privileges | `asmdba`, GID 1006
Oracle ASM Operator system privileges | `asmoper`, GID 1005
Oracle Database Administrators system privileges | `dba`, GID 1003
Oracle Database Operator system privileges | `dbaoper`, GID 1002

Oracle Groups and User Configurations

You can use the Browser User Interface or the `odacli create-appliance` command and a JSON file to deploy the appliance. The following configurations are supported:

- 2 Users with 6 groups (operating system role separation)

- Single User with 6 groups (no operating system role separation)

- Single user with 2 groups (no operating system role separation)

You can customize `groupname`, `username`, and `UID`.

Parent topic: Oracle Database Appliance Software Configuration Defaults