Skip Headers
Oracle® Database Appliance Getting Started Guide
Release 2.10 for Linux x86-64

E22692-36
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Oracle Database Appliance Postinstallation Tasks

This chapter describes the following administrative tasks that you must complete after you have deployed the software but before the system is operational:

Changing the Oracle Installation Owner Passwords

You must change the default administrative account passwords after installation to secure your system. During deployment, you should have changed the password of the root user. After deployment, change the Oracle Grid Infrastructure installation owner (grid) and Oracle Database installation owner (oracle) account passwords (welcome1) to passwords that comply with your enterprise user security protocols. Also change the database system privileges and secure other open database accounts such as the SYS, SYSTEM, DBSNMP, and other roles.

See Also:

Changing the IPMI 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. If you completed a custom deployment and configured IPMI, then 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. For example:

    [grid@appliance]$ /u01/app/11.2.0.4/grid/bin/crsctl set css ipmiadmin racadm
    $ IPMI BMC password:
    CRS-4229: The IPMI information change was successful
    

Note:

Do not change the default password until after you have completed software deployment on Oracle Database Appliance. If you change the password before deployment completes, then you might 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 or use Oracle ASR configured on another server in the same network as your appliance.

To support Oracle ASR, your Oracle Database Appliance hardware must be associated with a Support Identifier (SI) in My Oracle Support. For details, see "Validate ASR Systems in My Oracle Support" in Oracle Auto Service Request Installation and Operations Guide.

You can configure Oracle ASR during a Custom deployment. You can also configure Oracle ASR after deployment (either Typical or Custom) using the oakcli configure asr command (described in Appendix D). 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. Alternatively, you can reconfigure SNMP Version 2 Oracle ASR from either an internal or external SNMP Version 3 Oracle ASR. To reconfigure SNMP Version 2 Oracle ASR from internal SNMP Version 3 Oracle ASR, complete these steps:

  1. Run the following two commands to delete the SNMP Version 3 user:

    cd /opt/SUNWswasr/bin/
    asr delete_snmpv3_user
    
  2. Run oakcli configure asr and choose the deinstall option.

  3. Run oakcli configure asr and choose the internal option to configure internal SNMP Version 2 Oracle ASR.

To reconfigure SNMP Version 2 Oracle ASR from external SNMP Version 3 Oracle ASR, complete these steps:

  1. Run the following two commands to delete engine IDs from the external ASR manager, where ASRmgr is the location where the ASR manager is currently installed:

    cd /ASRmgr/SUNWswasr/bin/
    asr delete_engine_id -e engineId1 ,engineId2
    
  2. Run oakcli configure asr and choose the deinstall option.

  3. Run the oakcli configure asr command and choose the external option to configure external SNMP Version 2 Oracle ASR.

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

See also:

Appendix D, "Oracle Appliance Manager Command-Line Interface" for more information about the Oracle Appliance Manager commands mentioned in this section.

About Oracle Database Appliance Server Patches

All patching of Oracle Database Appliance is done with the regular Oracle Database Appliance Patch-Set Bundle. The Patch-Set Bundle provides all relevant patches for the entire system, including:

  • BIOS

  • Hardware drivers

  • Oracle Linux

  • Oracle ILOM

  • Oracle Database clone binaries

  • Oracle Grid Infrastructure clone binaries

When the regular Oracle Database Appliance Patch Set Bundle is available, log on to My Oracle Support as the registered Oracle Database Appliance software owner. Follow the instructions in My Oracle Support note 888888.1 as well as the instructions in the patch README file for information about patching the system.

Infrastructure patches (OS, Firmware, Oracle ILOM, and so on) will require a short downtime of Oracle Database Appliance while the patch is being applied. Oracle Appliance Manager verifies that a patch meets all prerequisite requirements to prevent you from installing patches in the wrong order. For example, you cannot just patch the GI without first updating the infrastructure.

Caution:

You must use an Oracle Database Appliance patch bundle to patch Oracle Database Appliance. Do not use Oracle Grid Infrastructure, Oracle Database patches, or Linux distribution patches. If you use patches that are not intended for Oracle Database Appliance, or if you use Opatch or a similar patching tool, then Oracle Database Appliance inventory is not updated, and you cannot complete future patch updates.

Checking for Patches on My Oracle Support

Note 888888.1 on My Oracle Support provides information about patches and updates for Oracle Database Appliance. To check for patches that apply to your system:

  1. Log on to My Oracle Support at:

    https://support.oracle.com
    
  2. Search for note 888888.1.

  3. If patches are available for your software, follow the directions in note 888888.1 to download and apply them.

Patching Oracle Database Appliance Software with Oracle Appliance Manager

The following steps and example outline the general procedure to patch the software on Oracle Database Appliance. Read the specific patch Readme and any help information for details on how to apply each particular patch.

  1. Log in to My Oracle Support using the Support Identifier of the registered software owner of Oracle Database Appliance.

    https://support.oracle.com
    
  2. Check the information in My Oracle Support note 888888.1 to identify, download, and apply the patch on your system. The patching procedure for a given patch bundle might differ from the standard procedure.

    Under Patch Search, select Oracle Database Appliance from the Product list and the patch release number from the Release list. Click Search. Then select the patch or patches and click Download.

  3. Log in as root.

  4. Move the patch to a temporary directory (for example, to /tmp) on each node of Oracle Database Appliance.

  5. To unpack the patch, run the oakcli unpack -package command on each node. Use the following command syntax, where path is the absolute path to the patch file:

    # cd /opt/oracle/oak/bin
    # ./oakcli unpack -package path
    

    For example, if you copy the patch file p16760967_27000_Linux-x86-64.zip to /tmp, then run oakcli unpack -package as follows:

    On Node 0:

    # cd /opt/oracle/oak/bin
    # ./oakcli unpack -package /tmp/p16760967_27000_Linux-x86-64.zip
    

    On Node 1:

    # cd /opt/oracle/oak/bin
    # ./oakcli unpack -package /tmp/p16760967_27000_Linux-x86-64.zip
    
  6. To install the patch, run the oakcli update -patch command on Node 0. Use the following command syntax, where version is the patch update version number:

    # cd /opt/oracle/oak/bin
    # ./oakcli update -patch version
    

    For example, to update to patch 2.7.0.0.0, run the oakcli update -patch command on Node 0 as follows:

    # cd /opt/oracle/oak/bin
    # ./oakcli update -patch 2.7.0.0.0
    

    Some patches, particularly Grid Infrastructure patches, will install themselves on both nodes automatically. The output displayed by the patch process advises you if the patch is being installed on one of both nodes. If the patch is only installed on Node 0, then repeat the oakcli update -patch command on Node 1.