Creating DB schemas in default tablespace is frowned upon by most DBAs. Foundation Pack creates two schemas as part of its installation. 1. AIA schema 2. JMSUSER schema. These two schemas are created in default tablespace of the Database. Quite a few times I received dejected emails from end-users, complaining that FP installer neither allows them to decide where they want to create the schemas nor allows them to input pre-created AIA schemas. That’s not fully correct. In fact, there is a workaround.
Create two schemas with aia/aia and jmsuser/jmsuser credentials (passwords can be changed post install). Create the schemas in the tablespace as desired by you. Then launch FP installer, and provide the same database details. In the install log you would see below error:
Executing commands
[sql] Failed to execute: create user aia identified by aia
[sql] java.sql.SQLException: ORA-01920: user name 'AIA' conflicts with another user or role name
[sql] 7 of 8 SQL statements executed successfully
[echo] ----Creating jmsuser database schema--------------
[sql] Executing commands
[sql] Failed to execute: create user jmsuser identified by jmsuser
[sql] java.sql.SQLException: ORA-01920: user name 'JMSUSER' conflicts with another user or role name
[sql] 5 of 6 SQL statements executed successfully
Don’t panic! This error is not malicious. Your FP Installer will use the existing users created by you.
You can use this approach on almost all AIA products from AIA for Comms 2.0 to AIA FP 2.3….even for Cluster installations!!
