11 Upgrading from 9.0.3.1 to 9.0.4.1

Preparing the System for Patching

If database archiving is turned on for the Infrastructure database, ensure that the /<sid>/arch partition is present and has the correct permissions.

Applying the Patch

After downloading and unzipping the database 9.0.1.4 patch set, refer to the patch set README file for instructions on how to apply the patch set. Ensure that you perform the following:

• Apply the database 9.0.1.4 patch set to the Infrastructure database on the database-tier. This involves applying the Oracle Universal Installer (OUI)-driven patch and postintallation steps.

• Apply the database 9.0.1.4 patch set to the Infrastructure mid-tier on the middle-tier. This involves applying the OUI-driven patch. Postinstallation steps are not required.

Issues During Patching

If you are unable to find the correct components during the OUI installation, ensure that the inventory.xml file contains the correct Oracle home path. If not, correct the Oracle home path and rerun OUI.

Preparing the System for Patching

Use the following to prepare the system for patching.

1. From the Infrastructure database Oracle home, as the owner of the Infrastructure database Oracle home, launch the oidadmin program.

2. Perform the following to determine if you must continue with the rest of these steps or if you can skip to step 13:

   1. Log in to the Infrastructure database Oracle home as the user of that Oracle home.

   2. Run the following script:

      $ $ORACLE_HOME/sso/bin/ssocfg.sh http <midtier_hostname> <sso_port_number>
      
      

      If the command is successful, then skip to step 13. If not, proceed to step 3.

3. Navigate to the OrclResouceName=ORASSO directory by expanding the following folders:

   +Oracle Internet Directory Servers
    +orcladmin@<hostname>:<portnumber>
     +Entry management
      +cn=OracleContext
       +cn=Products
        +cn=IAS
         +cn=IAS Infrastructure Databases
          +orclReferenceName=<service_name>
           +orclResourceName=ORASSO
   
   

   The following window displays:

   
   

4. Click the Local Access tab.

   The following window displays:

   
   

5. In the Structural Access Items (Entry Level Operations) pane, select Everyone, then click Delete.

   The following window displays:

   
   

6. In the same pane, select the remaining item, then click Create Like.

   The following window displays:

   
   

7. Click the By Whom tab. In the A Specific Entry field, perform the following:

   • change infraoidsso to infradb

   • change <midtier_hostname> to <dbtier_hostname>

   • click OK

8. In the Structural Access Items (Entry Level Operations) pane, click Create.

   The following window displays:

   
   

9. Select Everyone to add Everyone back to the Structural Access Items (Entry Level Operations) pane.

   The following window displays:

   
   

10. In the Access Rights tab, set all permissions to Deny for Everyone.

11. Repeat steps 5 to 10 for the Content Access Items (Attribute Level Operations) pane.

12. After repeating the steps for the Content Access Items (Attribute Level Operations) pane, click Apply and exit the oidadmin program.

13. Shut down all instances on both the Infrastructure database and Infrastructure mid-tier.

14. Back up the <infra_db_oracle_home>/config/ias.properties file.

15. Open the <infra_db_oracle_home>/config/ias.properties file and change the OID host name to <local_host_name>.

16. Restore the <infra_db_oracle_home>/config/ias.properties file after this patch is done

Applying the Patch

Apply the patch to both the Infrastructure database and Infrastructure mid-tier Oracle homes. Ensure you have performed the following:

1. Completed the steps in the "Preinstallation Requirements" section on both the Infrastructure database and the Infrastructure mid-tier.

2. Ran OUI on both the Infrastructure database and the Infrastructure mid-tier.

Issues During Patching

The following are possible issues during patching:

• When running OUI, the OID Configuration Assistant fails and indicates that there are OID processes running.

  Workaround: Check if there are OID processes running by using the ps -ef|grep oid command. If the processes are not running, use sqlplus to log into the Infrastructure database as ods/ods. Use the select * from ods_process command to check if there are any rows in that table. If there are, clean up the ods_process table. Commit, then exit sqlplus. Rerun the OID Configuration Assistant.

• When running OUI, after the OID Configuration Assistant completes, it will try to start the OID server. OID might not start the first time.

  Workaround: Click Retry and OID should start.

• OID Configuration Assistant failure will cause DCM Configuration Assistant to fail.

  Workaround: After the OID Configuration Assistant runs successfully, rerun the DCM Configuration Assistant.

Issues During Patching

When running OUI, you might encounter the following error:

You do not have permission to write to the /tupgds/oracle/oraInventory inventory. Installtion cannot continue: Permission denied.

Check the /etc/oraInst.loc file to verify that the entries are pointing to the correct Oracle home. If not, change the entries to point to the correct Oracle home, then rerun OUI.

Preparing the System for Patching

Complete the following steps for the Email and Files Infostore Oracle homes:

• Run the following commands to change the libctxx9.so link:

  $ cd $ORACLE_HOME/ctx/lib/$ rm libctxx9.so
  $ ln -s $ORACLE_HOME/lib/libctxx9.so libctxx9.so
  
  

• If database archiving is turned on, ensure that the /<sid>/arch partition is present and has the correct permissions.

Applying the Patch

Refer to the release notes for the patch set requirements. You can skip running the oidpatchca.sh script because the Infostore Oracle homes do not contain OID.

• Apply database 9.2.0.3 patch set to the Email Infostore Oracle home.

• Apply database 9.2.0.3 patch set to the Files Infostore Oracle home.

Issues During Patching

The following are possible issues during patching:

• When running OUI, you might encounter the following:

  You do not have permission to write to the /tupgds/oracle/oraInventory inventory. Installtion cannot continue: Permission denied.
  
  

  Workaround: Check the /etc/oraInst.loc file to verify that the entries are correct. If not, change the entries to point to the correct Oracle home, then rerun OUI.

• During the postinstallation steps, you might encounter the following error when running catpatch.sql:

  SP2-0310: unable to open file "/tupgdf/oracle/product/920/rdbms/admin/catlbac.sql"
  SP2-0310: unable to open file "/tupgdf/oracle/product/920/rdbms/admin/catsa.sql"
  SP2-0310: unable to open file "/tupgdf/oracle/product/920/rdbms/admin/catlabel.sql"
  
  

  Workaround: You can ignore this error.

• During the postinstallation steps, you might encounter the following error when running utlrp.sql:

  ERROR at line 1:
  ORA-04045: errors during recompilation/revalidation of LBACSYS.LBAC_EVENTS 
  ORA-06508: PL/SQL: could not find program unit being called ORA-06512: at line 2 
  ORA-06508: PL/SQL: could not find program unit being called 
  ORA-06512: at line 2
  Error when alter olapsys.
  
  

  Workaround: Apply the following workaround in sqlplus, then rerun utlrp.sql:

  ALTER SYSTEM SET "_system_trig_enabled"=FALSE;
  
  

  Refer to bug number 2014072.

Installing Calendar Server (9.0.4) Using the General Availability Release

Use the following to install the release 9.0.4 Calendar Server on the database-tier using the general availability release:

1. Shut down the release 9.0.3 Calendar Server.

2. Back up the release 9.0.3 Calendar Server Oracle home and the oraInventory directory under the ORACLE_BASE directory.

3. Move the oraInventory directory as oraInventory.903.

   The release 9.0.3 ORACLE_BASE variable (XYYYYc/collab) remains the same for the release 9.0.4 Calendar Server.

4. Change the ORACLE_HOME variable to point to the following directory: /XYYYYc/collab/product/ocsmt_904.

5. Ensure that Infrastructure database and Infrastructure mid-tier are running.

6. Ensure that the /etc/oraInst.loc directory points to the ORACLE_BASE directory for release 9.0.4 Oracle Collaboration Suite mid-tier components.

7. Install the release 9.0.4 Oracle Collaboration Suite mid-tier components using the general availability release and configure it ONLY for the Calendar Server on the database-tier. Ensure that you configure it with the new iAS instance name (XYYYYc_mtcal_u) and a different Calendar node ID, while still associating it with the newly upgraded OID.

   The following is a possible issue during installation of Oracle Collaboration Suite mid-tier components:

   When running the Calendar Server Configuration Assistant for the first time, it will fail and you will encounter the following error:

   Invalid Administrator Password
   
   

   Workaround: Rerun the Calendar Server Configuration Assistant.

8. Add the release 9.0.3 ORACLE_HOME variable into the release 9.0.4 $ORACLE_BASE/oraInventory/ContentsXML/inventory.xml directory with a new index number.

Performing the Calendar Server Upgrade

Use the following to upgrade Calendar Server.

1. Perform pre-upgrade tasks after completing the installation:

   1. From the 9.0.4 Oracle home, in the $ORACLE_HOME/ocal/upgrade directory, run the ocalPreUpg.sh script as the root user. This changes the ownership of your Oracle Calendar 5.x installation.

   2. Change the ownership of /<sid>/calendardb/db directory and /<sid>/collab/product/ocsmt_903/calendarserver directory to the owner of the 9.0.4 Calendar Server Oracle home.

2. Ensure the following before running the upgrade assistant tool:

   • The destination Oracle home has not been modified since it was installed.The source and destination instances of Oracle Collaboration Suite are not running.The Enterprise Manager Web site is not running.

3. Run the ocsua.sh script from the $ORACLE_HOME/upgrade directory. Select only to upgrade ÒOracle Calendar ServerÓ and ÒOracle Calendar application system.Ó

   • If you encounter the following error:

     Upgrading "Oracle Enterprise Manager"
     Current active EMD home is /tyhooc/collab/product/ocsmt_904
     Current active EMD home is /tyhooc/collab/product/ocsmt_904
     Upgrading /tyhooc/collab/product/ocsmt_904/sysman/emd/targets.xml
     *****Error upgrading /tyhooc/collab/product/ocsmt_904/sysman/emd/targets.xml. Check log file for details.
     null
     null
     Upgrade finished with status: Failure
     
     

     Workaround: You can ignore this error because the targets.xml file in the source Calendar Oracle home is empty.

   • You will see the following post-upgrade note after running the ocsua.sh script:

     You must now complete the the following post-upgrade tasks:
     [Oracle9iAS Web Cache] The following files or directories may need to be upgraded manually if they were customized in old Oracle home: 1) /tyhooc/collab/product/ocsmt_903/webcache/internal.xml, 2) /tyhooc/collab/product/ocsmt_903/webcache/wallets
     
     

     Workaround: Certified Configurations do not customize Web Cache. This step is required only if any customization was done to the Web Cache configurations after initial deployments.

4. Start up the release 9.0.4 Calendar Server processes and ensure you can log in to the Calendar Server using the thick client using the same user ID as the 9.0.3 Calendar Server. All the Calendar data should be intact. After the upgrade, all the port numbers and node ID for the release 9.0.4 Calendar Server will be the same as those in the release 9.0.3 Calendar Server.

Installing a Oracle Collaboration Suite 9.0.4 Middle-Tier Using the General Availability Release

Use the following to install a new release 9.0.4 middle-tier using the General Availability release.

Performing Middle-Tier Upgrades

Use the following section to upgrade the middle-tier.