Month: December 2013

Pre Requisites

1. Download the installer at the target server. It should have following files.

 

2. Take Back up of application & DB

3. Make sure target server have enough resources, like free space 10 GB.

Instructions

1)      Unzip zipped installer files.

2)   Stop following services:

1. Weblogic servers
2. Node manager
3. OPMN

3)      Start a VNC session & login to it with application user.

4)      Update application

1. Change directory to the Disk1 folder inside the unpacked archive folder.
2. ./runInstaller & wait till the installer opens.

      c. Click “Next” button.

1. Select “Skip Software Updates” & Click “Next” button

1. Select “Software Only Install” & Click “Next” button

1. Wait for the “Prerequisite Checks” to complete & click “Next” button.

1. Specify existing “Oracle Middleware Home” & “Oracle Home Directory” & then click “Next” button.

1. Select “Weblogic Server” & click “Next” button.

1. Click “Install” button to begin installation.

1. Wait till installation completes & then click “Next” button.

Click “Finish” on complete screen.

5)      Update Schemas

1. Validation of DB objects

• Execute following to know invalid objects.

SELECT owner, object_name FROM all_objects WHERE status=’INVALID’;

• Connect to DB as “sys” and run following command to validate “invalid” objects.

SQL>@?/rdbms/admin/utlrp.sql

• Execute following to know there are no invalid objects left.

SELECT owner, object_name FROM all_objects WHERE status=’INVALID’;

• Take note of any invalid objects. The existence of invalid database objects may prevent the upgrade from completing successfully.
• If there are still invalid objects left, use procedure “dbms_utility.compile_schema”

e.g.

SQL> execute

dbms_utility.compile_schema(‘PS7_SOAINFRA’);

PL/SQL procedure successfully completed

• Switch to VNC session.
• Set “ORACLE_HOME” & “JAVA_HOME”

e.g

export ORACLE_HOME=/obiee/Oracle/Middleware/Oracle_BI1

export JAVA_HOME=/obiee/Oracle/Middleware/Oracle_BI1/jdk

export PATH=$ORACLE_HOME/bin:$PATH:$ORACLE_HOME/OPatch:$JAVA_HOME

echo $PATH

Run “Patch Set Assistant “ or PSA

cd <oracle_common>/bin/

./psa

e.g

cd /obiee/Oracle/Middleware/oracle_common/bin/

./psa

Click “Next” button

1. Select “Oracle Business Intelligence”

1. Select both checkboxes & then click “Next” button

1. Create password file for “sys” user
2. Provide DB details to connect to DB (Connect String, DBA username,  DBA password) & click “Connect”
3. Once connected to DB, select MDS schema from drop down on same screen. e.g. MC_MDS
4. Provide Schema password & click “Next”

1. On next screen, BIPLATFORM should be selected in drop down, confirm(edit schema password, if required) & click “Next” e.g. MC_BIPLATFORM

1. Click “Next” button.

1. Click “Upgrade” button

1. Wait till 100% completed & then click “Next” button

1. Make a note of log file path & click “Close” button.

6)      Update system components

This step is required for any system component that is associated with a WebLogic domain. In some cases (for example, Oracle Web Tier and Oracle Internet Directory), you can choose to create system components that are not associated with any domain; in these cases, you do not have to perform this procedure.

Start following services

• Weblogic Admin server
• OPMN

If scheduler component doesn’t come up in OPMN services, do following changes suggested in Oracle Doc ID: 1585798.1 to fix this issue.

• Take a backup copy of opmn.xml in the <Middleware_home>/instance/instance1/config/OPMN/opmn directory.
• Open opmn.xml for editing.
• Change its contents from, for example:

 

<process-type id=”OracleBISchedulerComponent” module-id=”CUSTOM”> 

– <module-data> 

– <category id=”start-parameters”>   

     <data id=”start-executable”  value=”$ORACLE_HOME/bifoundation/server/bin/bischeduler.sh” /> 

– <!–  enable console log to be able to see process startup error   –> f(clean);   

    <data id=”no-stdio”  value=”false” /> 

</category> 

– <category id=”stop-parameters”>

 <data id=”stop-executable”  value=”integrator” />

</category>

– <category id=”ping-parameters”>

  <data id=”ping-type”  value=”integrator” />

</category>

– <category id=”ready-parameters”>

  <data id=”use-ping-for-ready”  value=”true” />

</category> 

</module-data>

 <start timeout=”600″  retry=”1″  />

  <stop timeout=”120″ />

   <restart timeout=”720″ retry=”1″ /> 

</process-type>

To

<process-type id=”OracleBISchedulerComponent” module-id=”CUSTOM”>

<module-data>

<category id=”start-parameters”>

<data id=”start-executable” value=”$ORACLE_HOME/bifoundation/server/bin/bischeduler.sh” />

<!–  enable console log to be able to see process startup error

–>

<data id=”no-stdio” value=”false” />

</category>

<category id=”ping-parameters”>

<data id=”ping-url” value=”/”/>

</category>

<category id=”restart-parameters”>

 <data id=”reverseping-timeout” value=”345″/>

 <data id=”no-reverseping-failed-ping-limit” value=”3″/>

 <data id=”reverseping-failed-ping-limit” value=”6″/>

</category>

</module-data>

<start timeout=”300″ retry=”3″/>

<stop timeout=”300″/>

<restart timeout=”300″ retry=”3″/>

<ping timeout=”60″ interval=”600″/>

</process-type>

Re-start OBIEE with the following command:

./opmnctl startall

1. Set  ORACLE_HOME  environment variable

e.g.

export ORACLE_HOME=/obiee/Oracle/Middleware/Oracle_BI1

cd $ORACLE_HOME/opmn/bin

./upgradenonj2eeapp.sh

-oracleInstance Instance_Home_Location

-adminHost WebLogic_Server_Host_Name

-adminPort administration_server_port_number

-adminUsername administration_server_user

-adminProtocol ts3

Note:

• If weblogic is running on SSL port, use “ts3”, if non-SSL use “t3” as adminProtocol
• While running command, it may ask for weblogic password, please provide.

e.g.

cd /obiee/Oracle/Middleware/Oracle_BI1/opmn/bin/

./upgradenonj2eeapp.sh -oracleInstance /obiee/Oracle/Middleware/instances/instance1  -adminHost tseasobi001 -adminPort 7001 -adminUsername weblogic -adminProtocol t3

7)      Update libraries

For each WebLogic Server domain, you must run the upgradeJRF() WLST command to update the shared libraries in your domain.

1. Stop following services:

• Weblogic servers
• Node manager
• OPMN

cd oracle_common/common/bin

./wlst.sh

e.g
cd /obiee/Oracle/Middleware/oracle_common/common/bin

1. Run the upgradeJRF() command on the node or system where the Administration Server is located for each domain you want to update. Your domain location is passed as a parameter.

 

wlst> upgradeJRF(‘/DOMAIN_HOME’)

e.g

upgradeJRF(‘/obiee/Oracle/Middleware/user_projects/domains/bifoundation_domain’)

 

8)      Update configurations and stores

For each WebLogic Server domain, you must run the upgradeOpss() WLST command to update your configurations and stores from previous releases to Release 11.1.1.7.0 configurations and stores using a system-jazn-data file.

Note:

When running upgradeOpss for 11.1.1.7.0, you may receive a “File Not Found” error message for the audit-store.xml file. This error message can be ignored. The audit-store.xml file is provided after running the upgradeOpss script.

 

Run following from WLST, just like previous step.

wls:/offline> upgradeOpss(jpsConfig=’<path to jps-config.xml’, jaznData=’< path to system-jazn-data.xml>’)

 

Look for success message “Upgrade of opss configuration and security stores is done.”

e.g

upgradeOpss(jpsConfig=’/obiee/Oracle/Middleware/user_projects/domains/bifoundation_domain/config/fmwconfig/jps-config.xml’,jaznData=’/obiee/Oracle/Middleware/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml’)

 

9)      Update presentation Catalog

1. Stop following services

• OPMN Presentation

1. Take back up of “instanceconfig.xml”

ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_obipsn

E,g

/obiee/Oracle/Middleware/instances/instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips/instanceconfig.xml

1. Change the UpgradeAndExit option to true in the instanceconfig.xml file.

Change it to the following:

<Catalog>

<UpgradeAndExit>true</UpgradeAndExit>

</Catalog>

1. Start following services

• OPMN Presentation

cd /obiee/Oracle/Middleware/instances/instance1/bin

• opmnctl startproc ias-component=coreapplication_obipsn

e.g.

./opmnctl startproc ias-component= coreapplication_obips1

1. Edit the instanceconfig.xml file again and change the upgradeAndExit option back to false.
2. Restart following services

• OPMN Presentation

10)   Enabling bicontentserver Features

1. Stop following services:

• Weblogic servers
• Node manager
• OPMN

1. Switch to VNC session.
2. Start the Configuration Wizard.

• cd WLHOME/common/bin
• ./config.sh

e.g.

cd /obiee/Oracle/Middleware/wlserver_10.3/common/bin

./config.sh

1. On the Welcome screen, select “Extend an existing WebLogic domain” & click “Next” button.

1. On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.

1. On the Select Extension Source screen, select “Extend my domain using an existing extension template” and select the following:

ORACLE_HOME/common/templates/applications/oracle.bicontentserver_template_11.1.1.jar

 

 Continue with the remainder of the Configuration Wizard screens to apply this template.

 Ignore error with OWSM schema if you are not using that component. 

 

After the template is applied

Start following services:

• Node manager
• Weblogic servers
• OPMN

11)   Enabling Oracle Business Intelligence Composer Features

1. Stop following services:

• Weblogic servers
• Node manager
• OPMN

1. Switch to VNC session.
2. cd WLHOME/common/bin

where WLHOME is the directory in which WebLogic Server is installed.

e.g

cd /obiee/Oracle/Middleware/wlserver_10.3/common/bin

1. ./config.sh
2. On the Welcome screen, select “Extend an existing WebLogic domain”.
3. On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.
4. On the Select Extension Source screen, select “Extend my domain using an existing extension template” and enter the location of the “oracle.bicomposer_template_11.1.1.jar file”
5. ORACLE_HOME/common/templates/applications/oracle.bicomposer_template_11.1.1.jar
6. If composer is already installed, use below.

 

1. Continue with the remainder of the Configuration Wizard screens to apply this template.
2. Ignore error with OWSM schema as we are not using that component.
3. Start following services:

• Weblogic servers
• Node manager
• OPMN

12)   Enabling JBIPS Features for the Smartview Client

To enable the Oracle BI JBIPS configuration template features for the Smartview client

1. Stop following services:

• Weblogic servers
• Node manager
• OPMN

1. Switch to VNC session.
2. cd WLHOME/common/bin

./config.sh

1. On the Welcome screen, select “Extend an existing WebLogic domain”.
2. On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.
3. On the Select Extension Source screen, select “Extend my domain automatically to support the following added products” and select Oracle JBIPS 11.1.1.7.0.

Continue with the remainder of the Configuration Wizard screens to apply this template.

 Ignore error with OWSM schema as we are not using that component.

Start following services:

• Weblogic servers
• Node manager
• OPMN

You should see “jbips (11.1.1)” Enterprise Application and the JBIPS shared libraries in the list of deployed modules in the Weblogic Administration Console.

13)   1.7.1 Running the Configuration Assistant to Update the Domain

1. Make sure only following services are running.

• Node Manager
• Admin server

1. Switch to VNC session
2. ORACLE_HOME/bin/config.sh

1. On the Welcome and Prerequisite Checks screens, click Next.

On the Create, Scale Out, or Extend screen, select Update BI Domain.

Specify the host name, port number, user name, and password for the Administration Server on the system to upgrade.

1. Click Next.

1. On the Update BI Domain Details screen, verify that appropriate directories are specified for each of the Home fields.

Click Next.

The progress of the upgrade process is shown on the Configuration Process screen.

When the upgrade process is complete, click Next.

Note:  if starting managed server task is taking too much time, you can start it from back end & then it should show green check on VNC progress screen in some time.

Click Finish

 

It may open browser window, ignore it.

14)   Manually Enabling BI Composer

1. Login to EM console

e.g. http://IP:7001/em

1. From left hand side pane, navigate to “Business Intelligence” -> “Core Applications”
2. Click on “Lock & Edit Configuration”
3. Expand “Weblogic  Domain” from left hand side pane
4. Right click on managed server, Open System MBean Browser.

 

1. Once it opens, click on find button.
2. Select “MBean” from down and enter “oracle.biee.admin:type=BIDomain.BIInstance.PresentationConfiguration,biInstance=coreapplication,group=Service” in search box and search for it
3. Look for attribute BIComposerEnabled in right hand side pane & set its value to be “true”

 Apply

Restart

• OPMN services

15)   Create boot.properties for admin and managed server.

16)   Verify version

1. Login to EM console

e.g. http://IP:7001/em

From menu, navigate to “Help” -> “About Enterprise Manager”

17)   Verify analytics

1. Login to Analytics

e.g.https://IP:9704/analytics

References:

• http://docs.oracle.com/cd/E28280_01/upgrade.1111/e16452/bi_plan.htm#BABECJJH
• Oracle Doc ID 1585798.1 : OBIEE 11g: Error: “[nQSError: 46066] Operation Cancelled. [[PRIMARY_POOL RetrieveColumnInfo From Table S_NQ_JOB Exchange” Scheduler does not Start after Install
• http://www.rittmanmead.com/2013/04/upgrading-obiee-to-11-1-1-7/