Wella?| actually this is a post that can apply to any use of Oracle Application Server (10.1.3.x) in conjunction with an Oracle 11g database. Starting with the 11g database, user passwords are case sensitive. Thus you can use uppercase, lowercase, or any combination thereof in your password. Unfortunately this can cause a problem when using OAS JDBC data sources and connection pools. For reasons unknown to me, OAS will always forward a lowercase representation of your password to the database for authentication. So unless you set the password for a user to all lowercase you will always get an authentication error. So make sure the passwords that get used for database authentication are lowercase!
I mentioned AIA in this post since installation of the AIADemo (in foundation pack 2.1) by default will assign an uppercase password to the SOADEMO user. That user is associated with a variety of objects and used for authentication in the a??soademoconnectionpoola?? JDBC resource that gets created when the demo is installed. By default the password is uppercase a??ORACLEa?? which you should change via the AIA_HOME/samples/AIADemo/scripts/AIADemoInstall.properties file. Locate the setting for a??soa.demo.passworda?? parameter and alter the associated value to be lowercase. This will allow the AIADemo to install without throwing a database error. Unfortunately you will run into other AIADemo installation problems unless you are installing against an AIA foundation pack instance that was upgraded. (and even then there are post install issues) However, that is an in-depth subject that is likely to appear in a future blog entry. I will say that the further issues are not related to using an 11g database.
