Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
ORA-28001 the password was expired error when trying to start BI Scheduler 'coreapplication_obisch1'
Hi,
Our OBIEE service went down and we started them again but status of following two was down
1. bi_server1
2. coreapplication
Upon investigation, I found that OPMN status was down for so I started it using 'opmnctl start'. This brought back bi_server1 but coreapplication was still down.
I found that only BI Sched is down so I looked in 'nqscheduler.log' and the last entry is of ORA28001 (password expired). I've contacted my dba and he is looking into it.
My little concern is that, once my dba changes the password, will I need to enter newly changed password somewhere in OBIEE or everything will work automatically?
I'm attaching following two snips
1. BI Sched error from logs
2. Current state of OBIEE
Please excuse my little knowledge about OBIEE administration.
Thanks,
ARK
Answers
-
b01cfbd1-38ad-496a-968e-accfb21666ab wrote:My little concern is that, once my dba changes the password, will I need to enter newly changed password somewhere in OBIEE or everything will work automatically?
As always: "It depends". If he's just reacivating the same password and it doesn't change....no obviously you won't need to change anything.
If he does change it then yes you'll need to change the password because that's actually the password which was used by/during the run of RCU to create all the repository tables which are used for the OBI backend unless someone was trying to be smart and moved thing around.
You said all your OBI servers were restarted....if your actual RCU user password expired and is about to be changed - have fun changing that because if you restart the WLS bits then they also won't come back up anymore.
All in all: tell him to give the user the SAME password and NEVER expire it again. There'^s a reason one uses technical user accounts with non-expiring password for infrastructure work. Namely that precisely situations like your don't arise.
0 -
Hi Christian,
Thank you for the swift reply. I've asked him to revert it to the old one and not change it.
I'll update once the changes are made. Thanks again.
0 -
Any time
0 -
Hi -
In case you do need to change a database password, have a look at the below discussion. We are working on an approach for this ...
Regards,
Charles
0