Post-Installation Tasks

Specifies steps to perform after the installation.

After you run Oracle Universal Installer perform the following post-installation steps:

  • After you install Oracle Airlines Data Model, obtain the IP Patch. The IP Patch includes additional documentation. To obtain the IP Patch and for the latest information about Oracle Airlines Data Model patch sets, go to My Oracle Support at https://support.oracle.com.

  • Review the Security chapter in the Oracle Airlines Data Model Implementation and Operations Guide.

Related Topics

Unlocking the OADM_SYS Account

Describes how to unlock the OADM_SYS account and set a password on this account.

Unlocking the OADM_SYS Account

At the end of the installation, the OADM_SYS account is locked. To unlock this account:

  1. Connect to the database with a DBA ID.

    Note:

    The password is case sensitive.

  2. Unlock the account and set the password by issuing the following SQL statement: 
    alter user oadm_sys account unlock identified by <password>;

    WARNING:

    Enter a password for the OADM_SYS account that is secure, according to the password guidelines described in Oracle Database 2 Day DBA. Do not to use OADM_SYS as a password.

Related Topics

Unlocking the OADM_SAMPLE Account

Describes how to unlock the OADM_SAMPLE account.

Unlocking the OADM_SAMPLE Account

At the end of the installation of the Oracle Airlines Data Model sample reports, the OADM_SAMPLE account is locked. To unlock this account:

  1. Connect to the Database with a DBA ID.

    Note:

    The password is case sensitive.

  2. Unlock the account and set the password by issuing the following SQL statement: 
    alter user oadm_sample account unlock identified by <password>;

    WARNING:

    Enter a password for the OADM_SAMPLE account that is secure, according to the password guidelines described in Oracle Database 2 Day DBA. Do not to use OADM_SAMPLE as a password.

Related Topics

Recompiling OLAP Views

Describes how to recompile the OLAP Views.

Recompiling OLAP Views

After you unlock the OADM_SAMPLE account, login with this account and execute the following statements to recompile the OLAP views in the sample schema:

ALTER VIEW CUST_RVN_VIEW_OLAPC COMPILE;
ALTER VIEW CUST_RVN_VIEW_FIN COMPILE;

Limiting User Privileges When You have Installed the Sample Reports

By default, when you perform a Sample Reports type of Oracle Airlines Data Model installation, the sample reports connect to oadm_sys schema directly. For security reasons, you may want to grant only select privileges to users who work with these reports.

Limiting User Privileges

To grant only select privileges, perform the following steps:

  1. Create a dedicated reporting user (for example, OADM_Report).
  2. Grant select privilege for all Oracle Airlines Data Model tables required for reporting to the user you created in Step 1. Thus, grant the select privilege for all Oracle Airlines Data Model tables which start with one of the following prefixes: DWA, DWB, DWD, DWR, DWL.
  3. Create a view (or synonym) in OADM_Report schema, pointing to the OADM_SYS tables.
  4. In the Oracle Business Intelligence Suite Extended Edition repository, change the connection information to point to the new schema.

Configuring the Working OLAP Environment

To set up a working OLAP environment for an Oracle Airlines Data Model warehouse, configure the database with the specified parameter and configuration settings.

Configuring the Working OLAP Environment

  • Set sga_target to 35% of available memory.

  • Set pga_aggregate_target to 35% of available memory

  • Set olap_page_pool_size=0. (This specifies dynamic page pool.)

  • Set _olap_page_pool_hi=30 (that is, lower than default of 50).

  • Set _olap_parallel_update_threshold and _olap_parallel_update_small_threshold to a high value (for example, ~2Gb.. 2147483647). These settings turn off parallel update for the analytic workspace.

  • Set memory_max_target to value greater than SGA and PGA settings. This is maximum amount of memory used for both SGA and PGA. The SGA and PGA settings specified are the minimum settings. (Note that failure to set memory_max_target leads to failure of instance startup (the next time these settings are validated which occurs if spfile had an older and distinct setting for memory_max_target).

The following statements illustrate changing these settings:

alter system set sga_target=1365M scope=spfile;
alter system set pga_aggregate_target=1365M scope=spfile;
alter system set memory_max_target=3030M scope=spfile;
alter system set olap_page_pool_size=0 scope=spfile;
alter system set "_olap_parallel_update_small_threshold"=2147483647 scope=spfile;
alter system set "_olap_page_pool_hi"=30 scope=spfile;
alter system set job_queue_processes=5 scope=spfile;
shutdown immediate;
startup;

Re-Enabling Oracle Database Vault

Describes the process of re-enabling Oracle Database Vault if before installing you disabled Oracle Database Vault, and then you want to re-enable Oracle Database Vault.

Re-Enabling Oracle Database Vault

If you are using Oracle Database Vault and disabled this option before installation then re-enable Oracle Database Vault by taking the following steps:

  1. Shutdown the Database, Database Control console process, and listener. For example on UNIX, ensure that the environment variables, ORACLE_HOME, ORACLE_SID, and PATH are correctly set. Log in to SQL*Plus as user SYS with the SYSOPER privilege and shut down the database. Then from the command line, stop the Database Control console process and listener. For example: 
    sqlplus sys as sysoper
Enter password: password
SQL> SHUTDOWN IMMEDIATE
SQL> EXIT
$ emctl stop dbconsole
$ lsnrctl stop listener_name

    For Oracle RAC installations, shut down each database instance as follows:

    $ srvctl stop database -d db_name

    Note:

    In Oracle Database 12c, Oracle Enterprise Manager Database Express is built into the Oracle database. It requires no special installation or management.

  2. Enable Oracle Database Vault: 
    cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk dv_on
make -f ins_rdbms.mk ioracle
  3. Startup the Database, Database Control console process, and listener. For example, on UNIX, Log in to SQL*Plus as user SYS with the SYSOPER privilege and restart the instance. Then from the command line, restart the Database Control console process and listener. For example: 
    sqlplus sys as sysoper
Enter password: password
SQL> STARTUP
SQL> EXIT
$ emctl start dbconsole
$ lsnrctl start listener_name

    For Oracle RAC installations, restart each instance as follows:

    $ srvctl start database -d db_name
  4. For Oracle RAC installations, repeat these steps for each node on which the database is installed.

Related Topics

Ensuring That Oracle Airlines Data Model Objects Are Valid

Describes recompiling all objects in oadm_sys schema.

Recompiling Objects in OADM_SYS

To ensure that all Oracle Airlines Data Model objects are valid, log in to the database with a DBA id and password and recompile all objects in OADM_SYS by issuing the following SQL statements:

exec utl_recomp.recomp_serial('OADM_SYS');

Ensuring That PGA_AGGREGATE_TARGET is Set to the Proper Value

To improve performance ensure that the PGA_AGGREGATE_TARGET is set to the proper value.

The value specified for PGA_AGGREGATE_TARGET depends on the physical RAM of your Database Server.

Setting PGA_AGGREGATE_TARGET

Ensure that the WORKAREA_SIZE_POLICY parameter is set to AUTO.

Note:

Setting PGA_AGGREGATE_TARGET to a nonzero value has the effect of automatically setting the WORKAREA_SIZE_POLICY parameter to AUTO.

See Also:

For information on tuning the PGA_AGGREGATE_TARGET initialization parameter, see Oracle Database Performance Tuning Guide

Installing Oracle Business Intelligence Suite Extended Edition Catalog for Oracle Airlines Data Model

After Oracle Business Intelligence Suite Extended Edition is installed, follow these steps to install an Oracle Business Intelligence Suite Extended Edition catalog for Oracle Airlines Data Model. If you install the Oracle Airlines Data Model sample reports, then configure the database connection information for the Catalog.

  1. Add a definition for oadm_db for the Oracle Airlines Data Model repository to use when connecting to the database. Add this definition to the file $ORACLE_HOME/network/admin/tnsnames.ora: 
    oadm_db =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname.domain)(PORT = port-number))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = SID) # Change your SID, Hostname, and Listener PortNumber
)
)

    Tip:

    Be careful to split these commands properly when you add them to the file; for example, do not add them as one long concatenated line of code.

    Note:

    If you want to use another database name, you must change the tnsname in the Oracle Business Intelligence Suite Extended Edition repository. See the Oracle Business Intelligence Suite Extended Edition documentation for directions for defining a database connection in repository.

Installing RPD and WebCat for Oracle Business Intelligence Suite Extended Edition

If you install the Oracle Airlines Data Model sample reports then deploy the Oracle Airlines Data Model RPD and webcat on the Oracle Business Intelligence Suite Extended Edition instance.

Installing RPD and WebCat

After you use the installer to install the sample reports you can find the RPD file and the webcat file in the directory $ORACLE_HOME/oadm/report, in the following files:

oadm.rpd

oadmwebcat.zip

Before you deploy the webcat, unzip oadmwebcat.zip.

Perform the following steps to deploy the Oracle Airlines Data Model RPD and webcat:

  1. Use your browser to open the Weblogic Enterprise Manager portal: 
    http://SERVERNAME:7001/em

    Login with the weblogic admin ID and password.

    Go to Business Intelligence --> coreapplication --> Deployment--> Repository

    and then deploy the rpd and webcat.

    Notice that when you deploy the RPD you need to provide the RPD password, you can find Oracle Airlines Data Model RPD by contacting My Oracle Support: My Oracle Support.

  2. Use your browser to open the weblogic console portal: 
    http://SERVERNAME:7001/console/login/LoginForm.jsp

    Login with your Weblogic admin ID and password. Go to your security realm and create a user named "oadm" and set a password for this user.

  3. Follow the instructions to "Refresh the User GUIDs" to update the GUIDs.

See Also:

For more information, see Oracle Fusion Middleware Administrator's Guide