5 Oracle Database Appliance Postinstallation Tasks

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

Topics:

Changing the Oracle Installation Owner Passwords

You must change the default administrative account passwords after installation 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 set to welcome1. 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 IPMI User Name and Password

If you completed a custom deployment and configured IPMI, then change the default user name and password.

Oracle Clusterware supports the Intelligent Platform Management Interface (IPMI), an industry-standard protocol that can isolate a failed node from the rest of the cluster. IPMI can restart a problematic node without cooperation from either Oracle Clusterware or from the operating system.

Configuring IPMI is an option when performing a custom deployment of Oracle Database Appliance. Change the default user name and password using the following procedure:

  1. Log in as the user grid.
  2. Enter the command crsctl set css ipmiadmin username , where username is the new name for the IPMI administrator account. Provide a new password when prompted. You must enable IPMI version 1.5 first. For example: 
    $ ipmitool -I open sunoem cli "set /SP/services/ipmi v1_5_sessions=enabled"
$ /u01/app/12.1.0.2/grid/bin/crsctl set css ipmiadmin racadm
$ IPMI BMC password:CRS-4229: The IPMI information change was successful $ ipmitool -I open sunoem cli "set /SP/services/ipmi v1_5_sessions=disabled"
$ IPMI BMC password:
CRS-4229: The IPMI information change was successful

Caution:

Do not change the default passwords until after you deploy software on Oracle Database Appliance. If you change the passwords before deployment completes, then you may encounter configuration errors.

Configuring Oracle Auto Service Request

Oracle Auto Service Request (Oracle ASR) is a secure support feature that automatically generates a service request for specific hardware faults. Oracle ASR can improve system availability through expedited diagnostics and priority service request handling.

You can configure Oracle ASR on Oracle Database Appliance to use its own Oracle ASR Manager (internal Oracle ASR) or use Oracle ASR Manager configured on another server in the same network as your appliance (external Oracle ASR). If you already have Oracle ASR Manager configured in your environment, you can register Oracle Database Appliance with your existing Oracle ASR Manager.

Note:

With an internal Oracle ASR Manager, an alert is not sent when the server goes down. An external Oracle ASR Manager is recommended because if a critical event occurs on Oracle Database Appliance with an external Oracle ASR Manager, an alert can still be sent to Oracle.

ASR uses ILOM telemetry sources to detect fault events on Oracle Database Appliance hardware. ILOM provides fault information, power and environmental, and CPU and memory fault information from the service processor.

To support Oracle ASR, your Oracle Database Appliance hardware must be associated with a Support Identifier (SI) in My Oracle Support.

You can configure Oracle ASR during initial deployment by choosing the Custom configuration option. You can also configure Oracle ASR after deployment (either Typical or Custom) using the oakcli configure asr command. The command prompts for input and, after you provide all of the required information, completes the Oracle ASR configuration.

An Oracle ASR configuration requires you to enter your My Oracle Support account user name and password. If a proxy server is required for Internet access to Oracle, then you must also provide the name of the proxy server. You can optionally configure Oracle ASR to use Simple Network Management Protocol (SNMP) Version 2 or SNMP Version 3.

To confirm that you have a working Oracle ASR configured, run the command oakcli test asr. Review your Oracle ASR configuration with the command oakcli show asr.

Note:

For fault coverage details, see the Oracle ASR Fault Coverage for Engineered Systems: Oracle Database Appliance (ODA) document: http://docs.oracle.com/cd/E37710_01/doc.41/e55818/toc.htm

Shutdown the VNC Server

After successfully deploying Oracle Database Appliance, shutdown your VNC server.

As part of deploying Oracle Database Appliance, you used VNC.
  • Shutdown the VNC server on the port on Node 0.
    # vncserver -kill: 5901