Descriptions of JMX Admin MBeans and Methods for the Oracle BI Systems Management API

Patching Oracle Business Intelligence Systems 23-5 Complete the tasks that are described in the following sections to apply a patch: ■ Section 23.3.1, Step 1: Stop System Component Processes for Oracle BI EE ■ Section 23.3.2, Step 2: Invoke OPatch with -rollback Option ■ Section 23.3.3, Step 3: Start System Component Processes for Oracle BI EE ■ Section 23.3.4, Step 4: Redeploy J2EE Applications

23.3.1 Step 1: Stop System Component Processes for Oracle BI EE

For details, see Section 4.1, About Starting and Stopping Oracle Business Intelligence.

23.3.2 Step 2: Invoke OPatch with -rollback Option

You must invoke OPatch with the -rollback option for each Oracle home while specifying the ID of the patch to be undone. To invoke OPatch with the -rollback option: 1. Display a command window and navigate to the location of the OPatch executable. The OPatch utility is located in the ORACLE_HOMEORACLE_ INSTANCEOPatch directory on UNIX operating systems or ORACLE_ HOME\ORACLE_INSTANCE\OPatch directory on Windows operating systems. For example, the directory on Windows might be: D:\OBI11g\Oracle_BI1\OPatch 2. Run the OPatch utility with the -rollback option using the following command syntax: opatch rollback -id patch_id -oh oracle_home For example, you might use the following command: opatch rollback -id 123456 -oh D:\OBI11g\Oracle_BI1\OPatch For more information about rolling back patches, OPatch requirements, and the options for running the utility, see: ■ Oracle Fusion Middleware Patching Guide ■ The README.txt file that was downloaded with the patch update

23.3.3 Step 3: Start System Component Processes for Oracle BI EE

For details, see Section 4.1, About Starting and Stopping Oracle Business Intelligence.

23.3.4 Step 4: Redeploy J2EE Applications

If the patch included any J2EE applications, then you must redeploy them to the Oracle WebLogic Server instances that they were running on before the patch was rolled back. To redeploy patched J2EE applications: 1. Display the Oracle WebLogic Server Administration Console. For information, see Section 2.3, Centrally Managing Oracle Business Intelligence Java Components Using the Oracle WebLogic Server Administration Console. 23-6 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

2. In the Change Center of the Administration Console, click Lock Edit to enable

you to redeploy J2EE applications.

3. In the left pane of the Administration Console, select Deployments.

4. In the right pane, select the boxes next to the J2EE applications to redeploy.

5. Click Update.

6. In the Update Application Assistant, click Finish.

7. To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately; some require a system restart. For more information, see Oracle WebLogic Server Administration Console Help system. Following completion of the rollback, the binary and JAR files that were updated by the application of the previous patch are now returned to their original state.

23.4 Determining Current Patch Levels

Each Oracle home must be patched to the same version as OPatch to ensure that Oracle BI EE functions properly. Use the OPatch lsinventory utility to determine the current patch version for any given Oracle home in the system. You can also use the utility to retrieve a full list of patches, with their corresponding IDs, for a given Oracle home. To determine the current patch levels: 1. Display a command window and navigate to the location of the OPatch executable: ORACLE_HOME\ORACLE_INSTANCE\OPatch For example: D:\OBI11g\Oracle_BI1\OPatch 2. Run the lsinventory utility using the following command syntax: Path_to_OPatchopatch lsinventory [-all] [-detail] [-patch] [-oh Oracle home location] For example: opatch lsinventory -patch -detail For information about the lsinventory options, see the user guides in the ORACLE_HOME\ORACLE_INSTANCE\OPatch\docs directory. 3. To run the lsinventory utility against other Oracle homes, repeat the previous steps for each Oracle home. For more information, see Oracle Fusion Middleware Patching Guide. 24 Moving Between Environments 24-1 24 Moving Between Environments You can move Oracle Business Intelligence to a new environment or from a test to a production environment, as described in the following list: ■ You can move or migrate Oracle Business Intelligence to a new environment by re-creating an existing Oracle BI system in a different location to the one in which it was originally installed. The objective is to re-create an identical deployment on different hardware. You might want to move to a new environment for the following reasons: – To move the system as a whole onto more powerful hardware. – To move to a different operating system. – To move into a different physical location. Moving is sometimes performed after a system has been upgraded. Upgrade is not covered in this guide. For complete information, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence. ■ Moving from a test environment to a production environment involves developing and testing applications in a test environment, and then rolling out the test applications and optionally test data, in the production environment on the same operating system. This can also include moving from a single- to a multiple-computer environment. See also Managing the Repository Lifecycle in a Multiuser Development Environment in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for information about moving repositories from test to production environments. For information, see Moving Oracle Business Intelligence to a Production Environment in Oracle Fusion Middleware Administrators Guide. The pasteBinary script is used when moving to production environments. This script is not supported with Oracle Business Intelligence installations that were installed on 64-bit operating systems using the Enterprise Installation type. In addition, Oracle Business Intelligence supports whole server migration, in which a WebLogic Server instance is migrated to a different physical computer upon failure, either manually or automatically. For complete information, see the chapter on Whole Server Migration in Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server. 24-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 25 Backup and Recovery of Oracle Business Intelligence Systems 25-1 25 Backup and Recovery of Oracle Business Intelligence Systems Backup and recovery refers to the various strategies and procedures involved in guarding against hardware failures and data loss and in reconstructing data should loss occur. Backup and recovery for Oracle Business Intelligence is fully described in Backup and Recovery Recommendations for Oracle Business Intelligence in Oracle Fusion Middleware Administrators Guide.