How to install FMW on 12c -
1. Limitation - Cannot run RCU directly on CDB database, may receive below error and the RCU creation will fail with the below error in rcu log:
ORA-65096 invalid common user or role name with RCU
File:/…/…/rcuHome/rcu/integration/../mds_user.sql
Cause - cannot Run RCU on CDB database directly. Create PDB for running Fusion Middleware separately.
Solution -Create separate PDB for FMW install as shown below:
CON_ID DBID CON_UID GUID
---------- ---------- ---------- --------------------------------
NAME OPEN_MODE RES
------------------------------ ---------- ---
OPEN_TIME
---------------------------------------------------------------------------
CREATE_SCN TOTAL_SIZE
---------- ----------
3 3925402302 3925402302 0815A8F30BE5186FE0538C02A8C0712E
PDB01 MOUNTED
1910872 0
SQL> alter pluggable database PDB01 open read write;
Pluggable database altered.
SQL> SELECT name, open_mode FROM v$pdbs;
NAME OPEN_MODE
------------------------------ ----------
PDB$SEED READ ONLY
PDB01 READ WRITE
Issue 2 -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error: XATRANS Views are not installed on this Database. This is required by the OIM Schema
Action: Install view XAVIEWS as SYS user on this Database.
Refer to the Oracle Database Release Documentation for installation details.
Solution - Fix the issue by installing the package on the PDB database as shown below -
[oracle@prac12c admin]$ sqlplus /nolog
SQL*Plus: Release 12.1.0.1.0 Production on Sun Dec 7 21:10:57 2014
Copyright (c) 1982, 2013, Oracle. All rights reserved.
SQL> connect SYS@PDB01 as sysdba
Enter password:
Connected.
SQL> @?/rdbms/admin/xaview.sql
DROP VIEW d$xatrans$
*
ERROR at line 1:
ORA-00942: table or view does not exist
DROP VIEW d$pending_xatrans$
*
ERROR at line 1:
ORA-00942: table or view does not exist
View created.
Synonym created.
View created.
Synonym created.
Issue 3 -
The 'Secure Files' option is not set in the target database. Please set the db_securefile parmater to 'PERMITTED' before continuing.
Solution -
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_securefile string PREFERRED
SQL> alter system set db_securefile=PERMITTED scope=BOTH;
System altered.
SQL> sho parameter db_securefile
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_securefile string PERMITTED
