Saturday, August 20, 2011

Issue : HRMS Patching in R12 facing below issue." ORA-01017: invalid username/password; logon denied"

While Performing HRMS Patching in R12 facing below issue.

Details :

RELEASE_NAME

--------------------------------------------------

12.1.1

DB :

11.2.0.1.0

OS :

Linux auohspten04 2.6.18-92.1.17.0.2.el5 #1 SMP Tue Nov 18 05:20:06 EST 2008 x86_64

cat: /etc/redhat-lsb: read error [Is a directory]

Enterprise Linux Enterprise Linux Server release 5.2 (Carthage)

Activity: Patch 10281212 (ALL) ==> Release 12.1 HRMS RUP4

Issue :

Patch failed and here is the terminal Output:

NOTE: If you do not currently have certain types of files installed

"u10281212us.log" [readonly] 5005L, 286643C

Time is: Sat Aug 20 2011 22:37:16

FAILED: file otlouk1drp.sql on worker 1 for product ota username OTA.

Time is: Sat Aug 20 2011 22:39:06

ATTENTION: All workers either have failed or are waiting:

FAILED: file otlouk1drp.sql on worker 1.

FAILED: file sspdlcon.sql on worker 2.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Current time is: Sat Aug 20 2011 22:39:06

Checked the Log files :

From adwork001.log :

"adwork001.log" [readonly] 179L, 4550C

Connecting to APPS......Connected successfully.

Time when worker started job: Sat Aug 20 2011 22:37:17

Start time for file is: Sat Aug 20 2011 22:37:17

Connecting to OTA......Unable to connect.

AD Worker error:

The following ORACLE error:

ORA-01017: invalid username/password; logon denied

occurred while executing the SQL statement:

CONNECT OTA/*****

from adwork002.log :

Start time for file is: Sat Aug 20 2011 22:37:17

Connecting to OTA......Unable to connect.

AD Worker error:

The following ORACLE error:

ORA-01017: invalid username/password; logon denied

occurred while executing the SQL statement:

CONNECT OTA/*****

Time when worker failed: Sat Aug 20 2011 22:38:57

Connecting to APPS......Connected successfully.

Manager says to quit.

Investigation & Workarounds:-

----------------------

Tried to connect as OTA & SSP users from backend terminals

$ sqlplus OTA/xxxxxx

SQL*Plus: Release 10.1.0.5.0 - Production on Sun Aug 21 01:21:04 2011

Copyright (c) 1982, 2005, Oracle. All rights reserved.

ERROR:

ORA-01017: invalid username/password; logon denied

Enter user-name:

$ sqlplus SSA/xxxxxx

SQL*Plus: Release 10.1.0.5.0 - Production on Sun Aug 21 01:22:01 2011

Copyright (c) 1982, 2005, Oracle. All rights reserved.

ERROR:

ORA-01017: invalid username/password; logon denied

Enter user-name:

Shows that none of the above two users getting connected...

Tried to change the passwords to apps using FNDCPASS:

FNDCPASS apps/xxxxxx 0 Y system/Y6bMC8me ORACLE OTA xxxxxxx

FNDCPASS apps/xxxxxx 0 Y system/Y6bMC8me ORACLE SSP xxxxxxx

Note : These are Apps DB accounts so, used "ORACLE" as mode for FNDCPASS utility.

Verify the logs and see if the password properly updated.

Now again verifying from backend sql prompt

SQL> conn OTA/xxxxxx

SQL> sho user

USER is "OTA"

SQL> conn SSP/xxxxxx

Connected.

SQL> sho user

USER is "SSP"

Worked...

Trial 1:-

----------

Now using adctrl tried to restart the failed workers ...

Still facing same issue....

Next: Upon investigation found that Patch was still picking old passwords from cache. Its not able to get the newly updated passwords.

Final Solution: Started the patch from scratch which now picked correctly updated new passwords and patch successfully got applied.

Learning:-

------------

Whenever facing such user account connectivity issues. Though we fix the issue we need to make sure that the whole patch need to be restarted again to get things affected.

Note: Before doing that make sure your patch has no side effects to restart from beginning.

Estimate how much more downtime this will turn out?

In case you are planning in Production. Make sure you gather all the knowledge in Non-Prod Iteration and proactively change the passwords before applying in Production..

This will certainly save your time and effort.

>>>> Have a happy reading <<<<<

Thanks

Kiran G

No comments:

Post a Comment