Creating the Required Oracle Analytics Server Schemas

When upgrading, you must create the required schemas. You can use the Repository Creation Utility (RCU) to create customized schemas or, optionally, you can use the Upgrade Assistant to create schemas using the default schema settings. This procedure describes how to create schemas using the RCU. Information about using the Upgrade Assistant to create schemas is covered in the upgrade procedures.

To create the required schemas:

1. Optional: If you wish to confirm the schemas which are present in your existing domain, then connect to the database as a user with DBA privileges, and run the following code from SQL*Plus:

   SET LINE 120
   COLUMN MRC_NAME FORMAT A14
   COLUMN COMP_ID FORMAT A20
   COLUMN VERSION FORMAT A12
   COLUMN STATUS FORMAT A9
   COLUMN UPGRADED FORMAT A8
   SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;
   

2. Verify that a certified JDK already exists on your system by running java -version from the command line.
   Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:
   • (Linux) setenv JAVA_HOME=c:/home/Oracle/Java/jdk1.8.0_131
   • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_131
   Add $JAVA_HOME/bin to $PATH.
3. Go to the oracle_common/bin directory:
   • (Linux) NEW_ORACLE_HOME/oracle_common/bin
   • (Windows) NEW_ORACLE_HOME\oracle_common\bin
4. Start the RCU:
   • (Linux) ./rcu
   • (Windows) rcu.bat
5. On the Welcome screen, click Next.
6. On the Create Repository screen, select Create Repository and then select System Load and Product Load.
   If you do not have DBA privileges, select Prepare Scripts for System Load. This will generate a SQL script containing all the same SQL statements and blocks that would have been called if the RCU were to process the actions for the selected components. After the script is generated, a user with the necessary SYS or SYSDBA privileges can run the script to complete the system load phase.

   Click Next.

7. On the Database Connection Details screen, select the Database Type and enter the connection information for the database that hosts the schemas.
   If the prerequisite check is successful, click OK to continue to the next screen. If the check fails, review the details you entered and try again.
8. On the Select Components screen:
   1. Specify the custom prefix you want to use to identify the Oracle Fusion Middleware schemas.
      The custom prefix is used to logically group these schemas together for use in this domain. For the purposes of this guide, use the prefix FMW12214.
      Note the custom prefix that you have specified on this screen. You will need this later, during the domain creation process.
   2. Select AS Common Schemas and BIPLATFORM.
      When you select AS Common Schemas and BIPLATFORM, all of the schemas in this section are automatically selected. If the schemas in this section are not automatically selected, then select the required schemas.

      Common Infrastructure Services schema, also known as STB schema, is automatically created. You cannot select or deselect an STB schema. STB schema enables you to retrieve information from the RCU during domain configuration.

9. In the Checking Prerequisites dialog, verify that the prerequisites check is successful, then click OK.
10. On the Schema Passwords screen, specify the passwords for your schema owners.
    Make a note of the passwords you enter on this screen as you will need this information while configuring your product installation.
11. On the Map Tablespaces screen, configure the required tablespace mapping for the schemas you want to create.
    Click Next, then click OK in the confirmation dialog. When the progress dialog shows the tablespace creation is complete, click OK.
    You see the Encrypt Tablespace check box only if you have enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box on the Map Tablespaces screen to encrypt all new tablespaces that the RCU creates.
12. Verify the information on the Summary screen and click Create to begin schema creation.
    This screen contains information about the log files that were created from this RCU operation. Click on the name of a particular log file to view the contents of that file.
13. Review the information on the Completion Summary screen to verify that the operation is completed successfully. Click Close to complete the schema creation.

Database Connection Details

Provide the connection information for the database that hosts the schemas.

Table 3-2 Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

Option	Description and Example
Host Name	Specify the name of the server where your database is running in the following format: examplehost.exampledomain.com For Oracle RAC databases, specify the VIP name or one of the node names in this field.
Port	Specify the port number for your database. The default port number for Oracle databases is 1521.
Service Name	Specify the service name for the database. Typically, the service name is the same as the global database name. For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: examplehost.exampledomain.com
Username	Enter the user name for your database. The default user name is SYS.
Password	Enter the password for your database user.
Role	Select the database user's role from the drop-down list: Normal or SYSDBA

Table 3-3 Connection Credentials for MySQL Databases

Option	Description and Example
Host Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
Port	Specify the port number for your database.
Database Name	Specify the name of your database.
Username	Specify the name of a user with administrator privileges.
Password	Enter the password for your database user.

Table 3-4 Connection Credentials for Microsoft SQL Server Databases

Option	Description and Example
Unicode Support	Select Yes or No from the drop-down list.
Server Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running. MSSQL named instances: A named instance is identified by the network name of the computer and the instance name that you specify during installation. The client must specify both the server name and the instance name when connecting.
Port	Specify the port number for your database.
Database Name	Specify the name of your database.
Username	Specify the name of a user with administrator privileges.
Password	Enter the password for your database user.

Table 3-5 Connection Credentials for IBM DB2 Databases

Option	Description and Example
Server Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
Port	Specify the port number for your database.
Database Name	Specify the name of your database.
Username	Specify the name of a user with DB Owner privileges. The default user name for IBM DB2 databases is db2inst1.
Password	Enter the password for your database user.