This chapter describes the following administrative tasks that you must complete after you have deployed the software but before the system is operational:
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, if you created an initial database during deployment, change the passwords for open database accounts such as the SYS, SYSTEM, DBSNMP users and other roles. The default password for the SYS and SYSTEM users is welcome1.
See Also:
Oracle Database Appliance Security Guide, Oracle Database Concepts, and Oracle Database Security Guide for information about the required configuration and best practices to secure database systemsOracle 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:
Log in as the user grid.
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:
$ /u01/app/12.1.0.2/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.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 ASR Manager or use Oracle ASR Manager 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 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 oakcli test asr command. Review your Oracle ASR configuration with the oakcli show asr command.