PB 10.5 login issue with Oracle 11

The user could log into sqlplus.  I make sure each user has sqlplus on their machines just in case. As for the error, it's a typical ORA-01017: invalid username/password; login denied.  I've been scratching my head because we can log onto machines set up two-three years ago, but only I can log into the new one. My main problem is that my user is at a location 50 miles from my office so I can't get a peek.  We're trying to recreate the error on a new machine in my office  but probably won't get it ready until the weekend.  It's not pressing at the moment since I'm not adding many new users, but it's unique enough to present a challenge.  Thanks for your help.

Ok Now I assume that you are using ODBC drivers for connectivity. Why don't you use Oracle Native Drivers for connectivity? can you please paste the code where are initializing SQLCA parameters?

For example:
// Profile Test
SQLCA.DBMS = "O90 Oracle9i (9.0.1)"
SQLCA.LogPass = <********>
SQLCA.ServerName = "TEST"
SQLCA.LogId = "scott"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PBCatalogOwner='scott',TableCriteria=',scott'"

Regards,
Sandeep

Thanks Sandeep,
I'll be performing another set up today at one of the other campuses.  If I'm lucky the new user will have the same issue and I'll try your solution.  Hopefully I can report back Tuesday as to the success.  

Thanks,
Terry Byrnes

Make sure the oracle home is set properly on each client.

Thanks Lordain, but that isn't the problem.  The user can log in using a user/pass combination created when we were using Oracle 8.  Both old and new Users can log into Sqlplus.  It has something to do with the Powerbuilder app and I'm leaning toward one of the ini files and how they refer to various database types.  

I also know something we encountered in the past when using oracle 8 DBMS drivers on an oracle 10 database.

You could also try to change the line:
SQLCA.DBMS = "O90 Oracle9i (9.0.1)"
TO:
SQLCA.DBMS = "O10 Oracle10g (10.1.0)"

I doubt it is your problem since it is working for some and not others unless they are using different operating systems but as long as it detects and WindowsNT!.

I know it is a long shot but something to rule out.

I think I may have found the main clue.  In the Oracle table, dba_users, is the item password_versions.  Looking at the original users, simply have 10g listed as their value.  The new users with the problems have both 10g and 11g.  From what I can find out, it seems that a new encryption is used on the 11g users - they work fine through Oracle products like SQLPlus, but the problem occurs with other vendors products, though I only know that my powerbuilder app is affected.  I haven't confirmed this with other products.  I'll look for info regarding Oracle password protection and see if there is a parameter to specify between 11g and the other versions - I think that may solve the issue.

Thanks to everyone who contributed...I'll let you all know if this fixes it.