Quote:
Originally Posted by sknmail@rediffmail.com  After writing above email, I found that there was error while running update_password.sh as a part of dbpatch_55.sql, so my passwords were not reset as CU4 standard password. So I resolved the problem and again re-ran dbpatch_55.sql again. So we have to take care that if for some reason update_password.sh file didn't get executed as part of dbpatch_55, then the problem I mentioned can happen.
- Suresh |
I ran into the same issue (thanks for pointing out that possibility!). It turned out that the reason for the update_password.cmd failing was a missing classpath entry. Even if you do not forget to run gc3env.cmd (as I did the first time), the classpath to the Oracle JDBC driver is not set. The subsequent failure of the update_password.cmd does not turn up in the logfile of dbpatch_55.sql; instead, the log file sais the passwords were updated. Sheez, I feel like a detective by now...