Weblogic password change

[Laurel]

Hi Erman!
Did you enconter the following issue ?
12.2.7
1.Shutdowned all middletier
2.started up just admin server
3.perl $FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl -action=updateAdminPassword

It went OK, no errors while it restarted nodemgr and Adminserver..
Checked that I could login OK to webconsole.
4.adstrtal.sh  -> errors starting oacore_server1, ... weblogic servers - Invalid weblogic credentials
passed

5.also admanagedsrvctl.sh did not work / invalid credentials
6.I killed all and started adstrtal.sh -> No errors all started up and EBS can login

But cannot access weblogic console and use admanagedsrvctl.sh scripts..

Tried several times to change , same result

- Exactly looks like 2178617.1, but I  am on 12.2.7 and dont have any boot.properties under the data/nodemanager/dir
- all $EBS_DOMAIN_HOME/servers/<>/security have the timestamp correct of the boot.properties..

Any hints ?

Thx alot,Laurel

[ErmanArslansOracleBlog]

See this note and ensure you did the operation properly ->

How To Change or Reset The WebLogic Administration Password In 12.2 E-Business Suite (Doc ID 1385751.1)

See this note for your issue as well ->

Running txkUpdateEBSDomain.pl -action=updateAdminPassword Command Completes Successfully, But New Weblogic Password Is Not Recognized (Doc ID 2178617.1)

[Sri]

This is very useful note id's,I could not stop saying thanks to you erman

[Laurel]

Hi Erman!
Thx!
I went trough that already and always do " by the book"´ :)
- Exactly looks like 2178617.1, but I  am on 12.2.7 and dont have any boot.properties under the data/nodemanager/dir -> not my case but very similar.
- all $EBS_DOMAIN_HOME/servers/<>/security have the timestamp correct of the boot.properties..
so the utility is updating it correctly.
I am on 12.2.7 .. Tried in 12.2.6 same way-> went fine.
So, it has to be 12.2.7..
I will log a SR . Just wanted to check with you have some ideas or if you have 12.2.7 :)
Will let you know on outcome

Br,Laurel

[ErmanArslansOracleBlog]

Okay. I see .. This may be a pure weblogic related thing.
What does the managed server 's log say?

Did you try clearing the managed server caches?

See workaround 1 documented in "SOA And OIM Managed Server Are Not Coming Up After Weblogic Admin Password Change (Doc ID 1625225.1)"