6 Oracle Database Appliance Postinstallation Tasks

Complete these administrative tasks after you have deployed software, but before the system is operational.

Related Topics

About Password Requirements on Oracle Database Appliance

Understand password requirements for multi-user access and non-multi-user access enabled systems.

Following are the password requirements on Oracle Database Appliance for various deployments.

Table 6-1 Password Requirements on Oracle Database Appliance

Component Multi-user access enabled and passwordless multi-user access-enabled system Non-multi-user access enabled system
Password Length Minimum password length is 9 characters.

Maximum password length is 30 characters.

 Minimum password length is 9 characters.

Maximum password length is 30 characters.
Password History Yes. New password cannot be the same as any previous password. Yes. New password cannot be the same as any previous password.
Password Complexity The password must contain at least two characters each from: uppercase letters, lowercase letters, numbers (0-9), and allowed special characters #, - or _. The password must have a minimum of 9 characters and a maximum of 30 characters. The password must contain at least two characters each from: uppercase letters, lowercase letters, numbers (0-9), and allowed special characters #, - or _. The password must have a minimum of 9 characters and a maximum of 30 characters.
Maximum Password Age The default is 90 days. The permitted range is 30 to 180 days, which can be configured by the user. The default is 90 days. This value is not configurable.
Account Lockout Threshold default retry attempts 3 times , Allowed Range 2 times – 5 times, user configurable None
Reset Account Lockout Counter Account is locked out when you run an ODACLI command after password has expired or after maximum retrial attempts are exceeded in the case of wrong password. You must obtain authorization from the system administrator to unlock the account. You can then change the temporary password provided by the administrator as part of authorizing an unlock of their account. Till the account is re-activated, you cannot run any ODACLI command. None
Reset Bad Attempts Counter If you have not exceeded the maximum retrial attempts and enter correct password, then the counter is reset to 0. If the maximum retrial attempts are exceeded, then the account is immediately locked and you must request for unlocking the account. Till the account is re-activated, you cannot run any ODACLI command. None
Change on first use Yes. The user account is created initially as Inactive. You must change the password on first login to make it active. Till the account is activated, you cannot run any ODACLI command. Can be set by a single oda-admin user on the first login to the BUI.

Parent topic: Oracle Database Appliance Postinstallation Tasks

Configuring CPU Core Count

Oracle Database Appliance is delivered with all cores on each server enabled. Follow this procedure to reduce the number of cores, if required.

  1. To reduce the number of cores, run the following command on Node 0 only:
    Set the cores in multiples of 2, for example, 12:
    [root@oak1 opt]# /opt/oracle/dcs/bin/odacli modify-cpucore --cores 12
    When you run the command, the nodes are restarted to apply the changes.
  2. Check if the job completed successfully:
    [root@oak1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID
  3. Verify that the core count is updated on both nodes:
    [root@oak1 opt]# /opt/oracle/dcs/bin/odacli describe-cpucore

Parent topic: Oracle Database Appliance Postinstallation Tasks

Modifying Oracle ASM Listener Port After Deployment

Understand how you can modify Oracle ASM listener port on Oracle Database Appliance after deployment.

Modifying Oracle ASM listener port using ODACLI commands

In earlier Oracle Database Appliance releases, you provisioned your bare metal system with Oracle ASM listener port 1525 as the default and as the Oracle ASM discovery address port from DB systems. Starting with Oracle Database Appliance release 19.24, you can customize Oracle ASM listener port number as a postinstallation task. All DB systems that you provision after changing the Oracle ASM listener port number use the new Oracle ASM port number.

Use the following command to modify the Oracle ASM listener port number:
odacli modify-asmport -p any_unused_port_between_1024_and_65536
For example:
# odacli modify-asmport -p 1528

Note:

You can run the odacli modify-asmport command only on deployments where the bare metal system is on Oracle Database Appliance release 19.24 or later and the DB system is on release 19.24 or later and you use the Oracle AI Database 26ai clones available with Oracle Database Appliance release 19.29.

Important:

When you run the odacli modify-asmport command in an Oracle Data Guard enabled environment on a standby system where MAX PROTECTION is enabled, Oracle Clusterware is restarted on the standby system. This may impact the downtime of the primary system. Ensure that you take these factors into consideration when you change the Oracle ASM port on either the primary or standby systems, or both.

Modifying Oracle ASM listener port using BUI

Follow these steps:
  1. Log into the Browser User Interface:

    https://host-ip-address:7093/mgmt/index.html

  2. Click Appliance.
  3. In the Basic Information page, Click Modify ASM Port to change the Oracle ASM listener port.
  4. In the Modify ASM Port dialog box, specify the ASM Port and click Modify.
  5. Click Refresh ASM Port to view the update.

Related Topics

Parent topic: Oracle Database Appliance Postinstallation Tasks

Securing Oracle ILOM Service Processors

Change the Oracle ILOM default password after completing Oracle Database Appliance deployment.

Do not change the default password until after you have completed software deployment on the Oracle Database Appliance.

Changing Oracle ILOM Password from the Console

  1. In the Oracle ILOM console, from the Administration menu, select User Management, and then navigate to the User Accounts subtab.

  2. Select root user and click Edit.

  3. Change the root user password.

Changing Oracle ILOM Password Using CLI Commands

  1. Connect to the Oracle ILOM service processor (SP) through SSH:

    # ssh -l root SP-ipaddr

  2. Set the new password:

    -> set /SP/users/root password=new_password
Changing password for user /SP/users/root/password...
Enter new password again: *********
New password was successfully set for user /SP/users/root

Parent topic: Oracle Database Appliance Postinstallation Tasks

Changing Oracle Database Appliance Passwords

After deploying your appliance, ensure that you change the following passwords for securing your system.

Changing the Oracle Installation Owner Passwords

During deployment, the root and database users SYS, SYSTEM and PDBADMIN are set to the system password. After deployment, the oracle and grid passwords are also set to the system password. 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.

Changing the oda-admin User Password through the Command-Line

  1. Log in to the appliance as root.

  2. Run the odacli set-credential command to reset the password. Enter the new password when prompted. 

    # odacli set-credential --username oda-admin
Enter 'user' password: 
Retype 'user' password:

Changing the the oda-admin User Password through the Browser User Interface

  1. Log into the Browser User Interface using the user name oda-admin.

  2. Click About, then User Settings in the upper right corner of the Browser User Interface.

  3. Enter the password in the Password field and the Password Confirmation field, then click Submit.

    A confirmation message is displayed.

  4. Click About, then click Sign Out.

  5. Log back into the Browser User Interface with the new password.

Note:

The oda-admin password expiration period is 90 days.

Parent topic: Oracle Database Appliance Postinstallation Tasks

Changing the DNS Server Address on Oracle Database Appliance

If the DNS server in the data center changes, understand how you can update the DNS entries on on Oracle Database Appliance server so that the network functions correctly.

Follow these steps to change the DNS server address on Oracle Database Appliance:

  1. Log in as the root user.
  2. Open the /etc/resolv.conf file in a text editor.
  3. Locate the name server setting for the DNS server and change it to the new value. For example: 
    search        example.com
nameserver    10.7.7.3
  4. Save the file and close the editor.

Parent topic: Oracle Database Appliance Postinstallation Tasks

Managing Power Consumption on Oracle Database Appliance X11

Understand how you can manage power consumption on Oracle Database Appliance X11.

Important:

This feature is applicable only for Oracle Database Appliance X11 hardware models.
The power consumption management feature on Oracle Database Appliance enables you to reduce power usage on supported AMD EPYC-based Oracle Database Appliance systems. Power can be managed in two ways:
  • Power saving mode which reduces power usage by placing the system into a dedicated power saving mode.
  • CPU power limits which enforce a maximum platform power envelope, applied uniformly across all CPU sockets.

Note:

Host System Management Port (HSMP) support must be enabled in the system BIOS. On recent firmware, this is enabled by default, but on earlier systems you may need to enable it and restart the system. Refer to the Enabling HSMP on Oracle Database Appliance X11 Systems in this chapter.

The following sections describe these power management options.

Parent topic: Oracle Database Appliance Postinstallation Tasks

Managing Power Consumption Mode

Oracle Database Appliance X11 supports power consumption management.

With power saving mode, you can:
  • Enable or disable power saving mode manually when reduced power usage is desired.
  • Create recurring schedules so the system automatically enters power saving mode during defined time windows.
  • Allow the system to automatically exit power saving mode when workload activity increases, so the system does not remain in power saving mode during periods of increased demand.
  • Leverage persistent configurations so that schedules persist after restarts and are automatically reapplied.
The system can exit power saving mode in three ways:
  • Manual intervention by explicitly disabling power saving mode.
  • Schedule expiry when the configured duration of an active schedule ends.
  • System activity when monitored workload crosses predefined thresholds and the system automatically exits power saving mode.

Parent topic: Managing Power Consumption on Oracle Database Appliance X11

Managing Power Consumption Schedules

You can automate transitions into and out of power saving mode on Oracle Database Appliance by configuring schedules that specify when the system should enter or exit power saving mode.

Creating Schedules

Schedules must include the following information:
  • Start Time: The time when power saving mode should begin. Input format is YYYY-MM-DDTHH:MM. The start time you specify must be at least 10 minutes later than the current time.
  • Duration: The number of minutes or hours that power saving mode will remain active after the start time.
  • Frequency: How often the schedule recurs. Acceptable values are:
    • DAILY – Every day at the specified time.
    • WEEKLY – Once per week on the same day and time.

When configuring schedules for power saving mode, the time zone is automatically detected and the system time zone is used. You need not specify a time zone when creating schedules.

Schedule Conflict Management

When adding schedules, understand the following:
  • Overlapping Schedules: Newly created schedules are validated to ensure that their active periods do not conflict with existing schedules. If a proposed new schedule overlaps with any current schedule, the operation is rejected, and an error is displayed.
  • Removal of Schedules: You can remove individual schedules by their assigned IDs or remove all schedules at once. The node name must be specified to remove all schedules.

Automatic Exit From Power Saving Mode

When in power saving mode, Oracle Database Appliance continuously monitors CPU, disk, and network utilization. If sustained activity exceeds predefined workload thresholds for longer than five minutes, the system automatically exits power saving mode. Power saving mode is resumed at the next scheduled window. Activity is characterized by any of the following:
  • CPU utilization exceeds 30%
  • I/O utilization exceeds 30%
  • Throughput on the network exceeds 200 MB/sec

Automatic transition based on workload does not reset the power limit to the platform default. It only affects the power saving mode, manual or scheduled.

Parent topic: Managing Power Consumption on Oracle Database Appliance X11

Managing CPU Power Limits

CPU power limits allow you to cap the maximum CPU power consumption on Oracle Database Appliance.

Unlike power consumption mode, CPU power limits do not place the system into a dedicated power consumption mode. Instead, they enforce a configured maximum platform power envelope, applied uniformly across all CPU sockets on the node. Use CPU power limits when you want to keep CPU power consumption within a defined limit for operational, energy, or compliance requirements.

With CPU power limits, you can:
  • Set a maximum CPU power limit for the node.
  • Apply the same power limit uniformly across all CPU sockets to ensure balanced system operation.
  • Leverage persistent configuration so that power limit settings persist after restarts and are automatically reapplied.

The configured power limit must be within supported platform-specific bounds. On supported AMD platforms, supported CPU power limits are set symmetrically across CPU sockets, in increments of 20W, and cannot be set below 50% of the total supported power limit for the platform.

Parent topic: Managing Power Consumption on Oracle Database Appliance X11

Viewing Power Consumption State

You can view the current power consumption state on Oracle Database Appliance before making configuration changes.

Viewing current power consumption helps you review whether power saving mode is currently active, the schedules that are currently configured, and the CPU power limit that is currently set. Power consumption state can be viewed using ODACLI or BUI. These interfaces also allow you to review schedule information, current power saving mode state, configured CPU power limits, and power state transitions.

Parent topic: Managing Power Consumption on Oracle Database Appliance X11

Enabling HSMP on Oracle Database Appliance X11 Systems

Understand how you can enable HSMP on Oracle Database Appliance X11 systems.

Note:

When patching an existing Oracle Database Appliance X11 system to Oracle Database Appliance release 19.31, the patching process automatically enables HSMP in the BIOS configuration and installs the necessary AMD E-SMI: EPYC™ System management Interface In-band Library RPMs.
If HSMP is not already enabled on your Oracle Database Appliance X11 system , run these steps on each node as the root user:
  1. Verify HSMP status:
    # lsmod | grep -i amd_hsmp

    If the module is loaded, HSMP is already enabled and you can skip the remaining steps in this procedure.

  2. Export the current BIOS configuration:
    # ubiosconfig export all -f --expert -y -x /tmp/bios-export.xml

    Check the exported file for <HSMP_Support>Disabled</HSMP_Support>.

  3. Modify the BIOS configuration to enable HSMP:
    # sed -i.bak 's|<HSMP_Support>Disabled</HSMP_Support>|<HSMP_Support>Enabled</HSMP_Support>|g' /tmp/bios-export.xml
  4. Import the updated BIOS configuration:
    # ubiosconfig import all -f --expert -y -x /tmp/bios-export.xml
  5. Restart the system:
    # reboot
  6. Verify the HSMP status after the restart:
    # lsmod | grep -i amd_hsmp
# ubiosconfig export all -f --expert -y -x /tmp/bios-export-new.xml
# grep "<HSMP_Support>Enabled</HSMP_Support>" /tmp/bios-export-new.xml

Parent topic: Managing Power Consumption on Oracle Database Appliance X11

Managing Power Consumption Using ODACLI Commands

Oracle Database Appliance X11 supports power consumption management using ODACLI commands.

Note:

The ODACLI commands and processes for configuring and managing power saving mode can only be run by users with root privileges or the ODA-ADMINISTRATOR role in multi-user access configurations. Unprivileged users are not permitted to run these operations.
To enable power saving mode on Oracle Database Appliance X11 hardware models:
# odacli enable-power-saving-mode --node-name odan1
Job details
----------------------------------------------------------------
                     ID:  78c0a6f3-fd7a-4530-8c9f-3cd6bcd413d1
            Description:  Enable Power Saving Mode on odan1
                 Status:  Success
                Created:  April 16, 2026 09:26:33 UTC
                Message:

Task Name                                Node Name                 Start Time                               End Time                   Status
---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- 
Persist mode metadata                    odan1          April 16, 2026 09:26:33 UTC              April 16, 2026 09:26:34 UTC              Success
Set CPU data fabric pstate to 'LOWEST'   odan1          April 16, 2026 09:26:33 UTC              April 16, 2026 09:26:33 UTC              Success
Set CPU efficiency mode to               odan1          April 16, 2026 09:26:33 UTC              April 16, 2026 09:26:33 UTC              Success
'POWER_EFFICIENT'
Start metric collection                  odan1          April 16, 2026 09:26:34 UTC              April 16, 2026 09:26:34 UTC              Success
To disable power saving mode on Oracle Database Appliance X11 hardware models:
# odacli disable-power-saving-mode --node-name odan1
Job details
----------------------------------------------------------------
                     ID:  78c0a6f3-fd7a-4530-8c9f-3cd6bcd413d1
            Description:  Disable Power Saving Mode on odan1
                 Status:  Success
                Created:  April 16, 2026 09:26:33 UTC
                Message:

Task Name                                Node Name                 Start Time                               End Time                        Status
---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- 
Persist mode metadata                     odan1                    April 16, 2026 09:26:33 UTC              April 16, 2026 09:26:34 UTC      Success
Set CPU data fabric pstate to 'HIGHEST'   odan1                    April 16, 2026 09:26:33 UTC              April 16, 2026 09:26:33 UTC      Success
Set CPU efficiency mode to                odan1                    April 16, 2026 09:26:33 UTC              April 16, 2026 09:26:33 UTC      Success
'HIGH_PERFORMANCE'
Stop metric collection                    odan1                    April 16, 2026 09:26:34 UTC              April 16, 2026 09:26:34 UTC      Success
To display details about power saving mode on Oracle Database Appliance X11 hardware models:
# odacli describe-power-saving-mode
Node
----
odan1

Status
------
        Power Saving Mode:  Disabled
          Effective Since:  May 04, 2026 04:28
              Schedule ID:  No schedule active

Power Usage and Limits (2 sockets)
----------------------------------
  Power Limit Max (Watts):  480
      Power Limit (Watts):  480
    Current Power (Watts):  189

Upcoming Schedule
-----------------
          Next Activation:  May 04, 2026 05:08
        Next Deactivation:  May 04, 2026 05:28

Power Saving Schedules
----------------------
ID                                    Day Of Week   Start     Duration      Next Activation           Next Deactivation
------------------------------------  ------------  --------  ------------  ------------------------  ------------------------
2d41ac94-a23e-4ce3-8801-ecbbfa7b849e  All           05:08     20 min        May 04, 2026 05:08        May 04, 2026 05:28
5820e4a7-acf4-42db-9e1e-7d322a7d54b4  Monday        05:28     45 min        May 04, 2026 05:28        May 04, 2026 06:13

Node
----
odan2

Status
------
        Power Saving Mode:  Disabled
          Effective Since:  --
              Schedule ID:  No schedule active

Power Usage and Limits (2 sockets)
----------------------------------
  Power Limit Max (Watts):  480
      Power Limit (Watts):  480
    Current Power (Watts):  173

Upcoming Schedule
-----------------
          Next Activation:  May 04, 2026 05:18
        Next Deactivation:  May 04, 2026 05:48

Power Saving Schedules
----------------------
ID                                    Day Of Week   Start     Duration      Next Activation           Next Deactivation
------------------------------------  ------------  --------  ------------  ------------------------  ------------------------
30874fda-88f5-40d3-93d9-050e162784b3  All           05:18     30 min        May 04, 2026 05:18        May 04, 2026 05:48
d7e6ef26-9bb9-406b-9ed8-c70402038e86  Monday        05:49     1 hr          May 04, 2026 05:49        May 04, 2026 06:49
To set power limit on Oracle Database Appliance X11 hardware models:
# odacli modify-power-saving-mode --set-power-limit 400 --node-name odan1
Job details
----------------------------------------------------------------
                     ID:  c5fab199-8096-493d-a6cf-ad5fc83dbc7b
            Description:  Modify power limit on odan1
                 Status:  Success
                Created:  April 16, 2026 09:28:17 UTC
                Message:

Task Name                                Node Name                 Start Time                               End Time                                 Status
---------------------------------------- ------------------------- ---------------------------------------- ---------------------------------------- ----------------
Persist power limit                      odan1                     April 16, 2026 09:28:18 UTC              April 16, 2026 09:28:18 UTC              Success
Set power limit to 400W                  odan1                     April 16, 2026 09:28:18 UTC              April 16, 2026 09:28:18 UTC              Success
To add power saving mode schedule on Oracle Database Appliance X11:
# odacli modify-power-saving-mode --add-schedule --start-date-time 2026-04-18T02:30 --duration-minutes 180 --frequency WEEKLY --node-name odan1
Job details
----------------------------------------------------------------
                     ID:  b55007e0-879a-48a9-8d09-472b427763cf
            Description:  Add power saving mode schedule on odan1
                 Status:  Success
                Created:  April 16, 2026 09:28:17 UTC
                Message:

Task Name                                Node Name                 Start Time                               End Time                                 Status
---------------------------------------- ------------------------- ---------------------------------------- ----------------------------------- ----------------
Persist schedule metadata                 odan1                     April 16, 2026 09:28:18 UTC              April 16, 2026 09:28:18 UTC              Success
To remove power saving mode schedule on Oracle Database Appliance X11:
# odacli modify-power-saving-mode --remove-schedule --schedule-ids a3dc6a9e-6d26-441c-878b-6616cc62fa23
Job details
----------------------------------------------------------------
                     ID:  3ed13169-9dd6-44a6-842a-a6eb584b7f3f
            Description:  Remove power saving mode schedules with id(s): a3dc6a9e-6d26-441c-878b-6616cc62fa23
                 Status:  Success
                Created:  April 16, 2026 09:28:17 UTC
                Message:

Task Name                                Node Name                 Start Time                               End Time                                 Status
---------------------------------------- ------------------------- ---------------------------------------- ----------------------------------- ----------------
Remove schedule metadata                 odan1                       April 16, 2026 09:28:18 UTC              April 16, 2026 09:28:18 UTC              Success

Parent topic: Managing Power Consumption on Oracle Database Appliance X11

Managing Power Consumption Using BUI

Oracle Database Appliance X11 supports power consumption management using BUI.

The Browser User Interface (BUI) enables you to view current power consumption status, review schedule information, and apply configuration changes in a graphical environment. Here, you can:
  • View whether power saving mode is currently active
  • Modify or remove schedules
  • Set or adjust platform power limits
  • The BUI alerts you if any conflicting configurations are attempted.
Follow these steps:
  1. Log into the Browser User Interface: 
    https://host-ip-address:7093/mgmt/index.html
  2. Click the Appliance tab, and then click Power Management.
  3. You can view power usage status, schedule, and other details for Oracle Database Appliance X11 hardware model.
  4. If the power saving mode is disabled, then click Enable to enable power saving mode.
  5. To disable power saving mode, click Disable.
  6. To modify power saving mode, click Modify.

    Select to add or remove schedules in the Select Schedule Mode drop down list.

    To add a schedule, select Add New Schedule in the Select Schedule Mode drop down list, and then specify the start date and time, time duration in hours and minutes, and the frequency.

    To remove a schedule, select Remove Selected Schedules in the Select Schedule Mode drop down list, and then select the schedule to be removed in the Schedule IDs to Remove drop down list.

    To remove all schedules, select Remove All Schedules in the Select Schedule Mode drop down list.

    You can set the Power Limit in the range of half of the maximum to the maximum power limit of the hardware model, in watts.

  7. Click Yes to submit the job.

Parent topic: Managing Power Consumption on Oracle Database Appliance X11