How to Update the 'oracle' User Password in a BDA Cluster if Required Prior to Mammoth Install/Upgrade/Patch
(Doc ID 1952199.1)
Last updated on NOVEMBER 01, 2017
Applies to:Big Data Appliance Integrated Software - Version 3.0.1 and later
During a Mammoth install/upgrade/patch the 'oracle' user password is required. This note provides the steps you can use to change the 'oracle' user password on each node of the cluster if that password is missing/lost/etc. and you have been given permission to change it by your system admin.
Additional tips if the 'oracle' password is missing/lost/expired/unexpectedly changed:
1. Use "chage -l" to see if the password is expired.
Output like below which shows "Account expires : never" indicates that an expired password is not the problem.
*.*.*.1: chage -l oracle
*.*.*.1: Last password change : Dec 04, 2014
*.*.*.1: Password expires : never
*.*.*.1: Password inactive : never
*.*.*.1: Account expires : never
*.*.*.1: Minimum number of days between password change : 0
*.*.*.1: Maximum number of days between password change : 99999
*.*.*.1: Number of days of warning before password expires : 7
2. Use 'passwd -S" to view the status of the 'oracle' user password:
*.*.*.1: oracle PS 2013-11-18 0 99999 7 -1 (Password set, DES crypt.)
*.*.*.n: oracle PS 2013-11-18 0 99999 7 -1 (Password set, DES crypt.)
3. As 'root' user you can check /etc/shadow which contains encrypted password as well as other information such as account or password expiration values, etc. You can search for 'oracle' within /etc/shadow and see if the value is unexpectedly/incorrectly set to the value of another user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document