Vaibhav Kadam
asked on
Adadmin not accepting apps password
After database and apps upgrade adadmin not accepting apps password
Upgrade paths
Db-from 11.1.0.7 to 12.1.0.2
apps-from R12.1.1 to R12.1.3
adadmin show below issues;-
After upgrading database 11.1.07 to 12.1.0.2 adadmin not accepting apps password
ORA-01017: invalid username/password; logon denied
occurred while executing the SQL statement:
CONNECT APPLSYS/*****
Error: The given ORACLE password is not the correct password.
Please re-enter the ORACLE username and password.
Upgrade paths
Db-from 11.1.0.7 to 12.1.0.2
apps-from R12.1.1 to R12.1.3
adadmin show below issues;-
After upgrading database 11.1.07 to 12.1.0.2 adadmin not accepting apps password
ORA-01017: invalid username/password; logon denied
occurred while executing the SQL statement:
CONNECT APPLSYS/*****
Error: The given ORACLE password is not the correct password.
Please re-enter the ORACLE username and password.
Correct, passwords are case sensitive from 11 onwards.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Mark Geerlings has the right idea here.
If your 11g has SEC_CASE_SENSITIVE_LOGON = false and your 12c is set to TRUE, then case sensitivity can be your problem.
The fundamental issue may be the disconnect between defaults and capabilities pertaining to this.
Another thing to look at is, using a DBA privileged account, to examine the password_versions field of ....uh...well, it's either in dba_users or user$, I can't quite recall. User$, I think. If it just says 10G (regardless of whther your DB is 10G, 11G or 12C), then it is NOT case-sensitive password. If it says "10G 11G 12C", then it is case-sensitive.
If you need it to be case-insensitive, follow Mark's steps for resetting the SEC_CASE_SENSITIVE_LOGON.
Also, check your sqlnet.ora file and set the allowed_logon_version_serv
Regards,
JT
If your 11g has SEC_CASE_SENSITIVE_LOGON = false and your 12c is set to TRUE, then case sensitivity can be your problem.
The fundamental issue may be the disconnect between defaults and capabilities pertaining to this.
Another thing to look at is, using a DBA privileged account, to examine the password_versions field of ....uh...well, it's either in dba_users or user$, I can't quite recall. User$, I think. If it just says 10G (regardless of whther your DB is 10G, 11G or 12C), then it is NOT case-sensitive password. If it says "10G 11G 12C", then it is case-sensitive.
If you need it to be case-insensitive, follow Mark's steps for resetting the SEC_CASE_SENSITIVE_LOGON.
Also, check your sqlnet.ora file and set the allowed_logon_version_serv
Regards,
JT
For a minimal test to remove apps as the problem, try connecting as that user using sqlplus and see if you still get an invalid password. Make sure the case is correct.