Resetting the expired database ODS and ODSM Schema password by oidpasswd Utlity In OID
When the oidmon is not starting and gives the error the we have to Check the logfile and if the password expiry is the case then we need to reset the password in the database 'just alter user ' will not cleanly reset the password so we to reset by using iodpasswd Utility
OIDMON PROCESS WILL BE DOWN due to not able to connect the database with expired password
OIDMON PROCESS is responsible of controlling the oracle OID instance ...
we need to Check the C artifacts and it status for the further investigation In this issue.....
SETP1
Check the status of the opmn of the middleware
status of OID
Processes in Instance: oid_inst1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
oid1 | oidldapd | 11143 | Alive | 834262793 | 720936 | 191:29:43 | N/A
oid1 | oidldapd | 11135 | Alive | 834262791 | 852168 | 191:29:44 | N/A
oid1 | oidldapd | 11131 | Alive | 834262790 | 724560 | 191:29:45 | N/A
oid1 | oidldapd | 10981 | Alive | 834280460 | 374644 | 191:29:51 | N/A
oid1 | oidldapd | 11139 | Alive | 834262792 | 849440 | 191:29:44 | N/A
oid1 | oidmon | N/A | Down | N/A | N/A | N/A | N/A
EMAGENT | EMAGENT | 23311 | Alive | 834288485 | 63824 | 3:08:34 | N/A
status of ovd
Processes in Instance: ovd_inst1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ovd1 | OVD | 25023 | Alive | 1354530833 | 871556 | 3:06:19 | ldap:6501,https:8899,ldaps:7501
EMAGENT | EMAGENT | 25022 | Alive | 1354530832 | 63824 | 3:06:19 | N/A
status of OHS
Processes in Instance: ohs_inst1
---------------------------+--------------------+---------+----------+---------------+-------------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------+--------------------+---------+----------+---------------+-------------+-----------+------
ohs1 | OHS | 25543 | Alive | 2145402128 | 4094100 | 3:06:01 | https:7779,https:4443,http:7777
In the OID instance we Found out that the oidmon is down and we need to bring up the Process to fix the Issue
Step 2
Check the oidmon log file for further more information the oidmon log is located at
/u03/app/oracle/admin/oid_inst1/diagnostics/logs/OID/oid1
$INSTANCE_HOME/diagnostics/logs/OID/oid1
Look for the oidmon-0000.log for the oidmon logs
In the Log file you can find the below message
[2012-09-03T20:06:21+04:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: fahmid.domain.com] [pid: 29628] [tid: 0] Guardian: Connecting to database, connect string is oiddb
[2012-09-03T20:06:21+04:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: fahmid.domain.com] [pid: 29628] [tid: 0] Guardian: [gsdsiConnect] ORA-28001, ORA-28001: the password has expired
[2012-09-03T20:06:21+04:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: fahmid.domain.com] [pid: 29628] [tid: 0] Guardian: [oidmon]: Unable to connect to database,
will retry again after 10 sec
It is Cased by the Expiry Of the database password in the OID [IDM]database for the ODS schema so check the database and verify the schema status ...
Step 3
check the user status in the database if it is expired we need to reset the password for User.. we can either use old or new Password
SQL> select username,user_id,ACCOUNT_STATUS,LOCK_DATE,EXPIRY_DATE from dba_users
check the user status in the database if it is expired we need to reset the password for User.. we can either use old or new Password
SQL> select username,user_id,ACCOUNT_STATUS,LOCK_DATE,EXPIRY_DATE from dba_users
2 where EXPIRY_DATE > sysdate -2;
USERNAME USER_ID ACCOUNT_STATUS LOCK_DATE EXPIRY_DA
--------------------- --------- -------------------------------- -----------------
ODS 84 EXPIRED 02-SEP-12
By the query conform the ODS schema password of the database had been expired and we need to reset the password of the ODS schema
Check the details for the ODSSM also
USERNAME ACCOUNT_STATUS EXPIRY_DATE PROFILE
------------------------------ -------------------------------- --------- ------------------------------------------------------
ODSSM EXPIRED 01-SEP-12 DEFAULT
Step 4
Change the password by the oidpasswd utility and
[oracle@fahmid ~]$ /u03/app/oracle/product/fmw/idm/ldap/bin/oidpasswd - help
unable to locate message file: ldap<language>.msb
If you are getting the above message unable to locate the message file then you have to set the Proper Oracle Home ...
For ODS Schema we need to set the oracle home to the idm directory under the fmw directory
export ORACLE_HOME=/u03/app/oracle/product/fmw/idm
oracle@fahmid ~]$ /u03/app/oracle/product/fmw/idm/ldap/bin/oidpasswd - help
Usage: oidpasswd connect=<Net8 Connect Descriptor> [change_oiddb_pwd=true | create_wallet=true | unlock_su_acct=true| reset_su_password=true | manage_su_acl=true]
connect: Database connect string
change_oiddb_pwd: Change OID database password (default operation)
create_wallet: Create LDAP and Replication server wallets
unlock_su_acct: Unlock OID super user account
reset_su_password: Reset OID super user password
manage_su_acl: Manage super user restriced ACL
export ORACLE_INSTANCE=/u03/app/oracle/admin/oid_inst1
set the ORACLE_INSTANCE to the oid_ist1 under the admin directory
[oracle@fahmid ~]$ /u03/app/oracle/product/fmw/idm/ldap/bin/oidpasswd connect=oiddb change_oiddb_pwd=true
current password:
new password:
confirm password:
new password must be different from the current.
Syntax $ORACLE_HOME/ldap/bin/oidpasswd conenct=<database_string> change_oiddb_pwd=true
[oracle@fahmid ~]$ /u03/app/oracle/product/fmw/idm/ldap/bin/oidpasswd connect=oiddb change_oiddb_pwd=true
current password:
new password:
confirm password:
password set
No comments:
Post a Comment