What exactly is telling you the users are "locked"? Are you getting some kind of error message? If so, what is it?
When you set a user password to blank within the database (in the USERS table), you actually have to set it to the encrypted value for blank, not literally to NULL. Assuming you are not authenticating using LDAP, the following should work.
1. Login to Query Analyzer or Enterprise Manager and locate the site admin schema.
2. Run the following query (reset password to blank. The code below is meant for encrypted null string): UPDATE USERS SET USER_PASSWORD = 'DEF:2jmj7l5rSw0yVb/vlWAYkK/YBwk=' WHERE USER_ID = <user_id>;
NOTE: Please make sure that <user_id> is replaced with a site admin's user ID.
3. Login to Site Administration using the username whose password was updated in step 2 and leave the password field empty.
[If this post solves or helps solve your issue, mark the thread as solved and give KUDOS to the author for their assistance.]
(Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.)
I beleive this is due to the qcsiteadmin_db password mismatch. I also tried unlocking the user at backend Oracle, and started the QC again, but when QC comes up, the user qcsiteadmin_db gets locked again (TIMED). I beleive this is due to multiple tries with the mismatch password and it gets locked.
The site admin schema is default : qcsiteadmin_db
1) How to set the password and sync up with database and JBoss?
2) The siteadmin.xml file has an encrypted password in the format "TWO:23-23-23...."
I beleive this is causing the issue. siteadmin and qc are locked now and could not login to both.
Have faced this issue before and found that the issue resides within LDAP.
We just reconfigured the connection of LDAP and waited for sometime for the configuration to commit and everything was back to normal. We too thought that the issue resides with the ORACLE database and did also the steps you mentioned but the issue reoccur from time to time.
Also in another instance, we faced this issue with MSSQL databse. Also we found the in the MSSQL DB properties that the users were locked, there is an option ther to unock them but also the isue reoccur from time to time. Uninstall/reinstall the patch solved our issue.
The steps should be pretty much similar to Oracle or MSSQL. THe issue mainly here is synching up the siteadmin.xml with the correct password. If anyone could advise how to sync up the password of user (qcsiteadmin_db) in database with that of QC uses (qcsiteadmin_db) , it should fix it.
in the siteadmin.xml the passord set there is encrypted. And it is a coomon issue to forget the password set for the siteadmin especially if you don't use the default "tdtdtd". We use "TXT" to set the actual password the same as the one set in the db (plain text). :)
We started the "Database to Repository" feature for our migration. the size of the project QC gave is about ~14 GB.
We had enough disk space (200 GB) so we started running it. But even after 8 hours of execution, the export of Database to Repository job did not finish. I guess it is not even writing any more to the file system, the free space in the disk is not reducing. Looks like it is in hung state...
Can we stop the QC and restart as it is not moving? If doing so would it affect the QC system? any ideas?