PowerBuilder · Database exception
What does ORA-01017 via PowerBuilder After Oracle Case-Sensitive Logon Change mean in PowerBuilder?
PowerBuilder connections that worked against an older Oracle server start failing with ORA-01017 ('invalid username/password; logon denied') surfaced through SQLCA.SQLDBCode after a migration to Oracle 11g or later, because Oracle 11g defaults SEC_CASE_SENSITIVE_LOGON to true while credentials were originally created and stored in lowercase. PowerBuilder's connection code sending the password in a different case than it was defined in now fails authentication where it previously succeeded.
PowerBuilder connections that worked against an older Oracle server start failing with ORA-01017 ('invalid username/password; logon denied') surfaced through SQLCA.SQLDBCode after a migration to Oracle 11g or later, because Oracle 11g defaults SEC_CASE_SENSITIVE_LOGON to true while credentials were originally created and stored in lowercase. PowerBuilder's connection code sending the password in a different case than it was defined in now fails authentication where it previously succeeded.
Check DBA_USERS.PASSWORD_VERSIONS on the Oracle side to confirm whether the account's password hash predates case-sensitive logons, and either reset the password under the new case-sensitive rules or ensure the DBParm/connection code passes credentials in the exact case they were created with. Don't assume the credentials are wrong outright; verify the case-sensitivity change first when this appears right after an Oracle version upgrade.