12 Oracle Content Services Upgrade

This chapter contains information about the process of upgrading to Oracle Collaboration Suite 10g Release 1 (10.1.2) This information includes prerequisite steps, recommendations, and information about changes in Oracle Content Services.

Oracle Collaboration Suite 10.1.2 supports upgrading from the following releases of Oracle Files and Oracle Content Services:

• Oracle Files 9.0.3.1

• Oracle Files 9.0.4.1

• Oracle Files 9.0.4.2

• Oracle Content Services 10.1.1

12.1 Preparing to Upgrade to Oracle Content Services 10.1.2

Before upgrading, you must perform the following tasks:

• Back up the database that contains the schema that you are going to use with Oracle Content Services 10.1.2

• Perform the pre-upgrade tasks described in previous chapters of this manual, including updating your database, if necessary.

• Stop all Oracle Files or Oracle Content Services processes.

• Ensure that the default Oracle Files tablespace (IFS_MAIN) has a minimum amount of free space equal to 150 percent of the currently used space. This allows the upgrade process to avoid performance issues caused by an insufficient amount of free space in the tablespace

• Configure Oracle Workflow.

The upgrade process stops if Oracle Universal Installer encounters any errors. After fixing the issues, you can restart the upgrade process and it continues from the point that it encountered the error.

12.1.1 Configuring Oracle Workflow for Oracle Content Services

Before configuring Oracle Content Services, configure Oracle Workflow by performing the following steps:

1. Log in to the Oracle Collaboration Suite Database 10g (10.1.2) as a user with appropriate privileges and enter the following command:

   drop user owf_mgr cascade;
   
   

2. From the Oracle Collaboration Suite 10g Release 1 (10.1.2) Applications tier Oracle home, run the following script:

   $ORACLE_HOME/wf/install/wfinstall.csh
   
   

   The Oracle Workflow Configuration Assistant starts.

3. Enter the following parameters in the appropriate fields.

   • Install Option: Select Server Only

   • Workflow Account: Leave the default, owf_mgr.

   • Workflow Password: Provide the same password as the Oracle Content Services schema password.

   • SYS Password: Provide the password for the database user SYS. You must supply this value.

   • TNS Connect Descriptor: Copy this value from the tnsnames.ora file, located in $ORACLE_HOME/network/admin. For example:

     (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myhost.mydomain.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=orcl.mydomain.com)))
     
     

   Do not select the Enter LDAP Parameters, Enter Mailer Parameters, or Change Tablespace options.

4. Click Submit.

5. Proceed with configuring Oracle Content Services using the Oracle Collaboration Suite Control Console.

12.2 Upgrading from Oracle Files 9.0.3.1, 9.0.4.1, or 9.0.4.2

The upgrade from Oracle Files to Oracle Content Services 10.1.2 is a full product upgrade. The upgrade process creates a new Oracle home.

For a detailed list of differences between Oracle Files and Oracle Content Services, see "What's New in Oracle Content Services in Oracle Content Services Administrator's Guide. In addition to the features described in that chapter, the following information applies to systems upgraded from Oracle Files to Oracle Content Services:

• The upgrade process migrates all users, whether or not the users are defined in Oracle Internet Directory. This is to preserve the ownership of files if a user has been removed from Oracle Internet Directory. After completing the upgrade process, change the ownership of these files in Oracle Content Services, and then remove the user accounts.

• Existing workflows are not migrated. If you have current workflows in process, finish these workflows before upgrading to Oracle Content Services 10.1.2.

• Oracle Content Services does not support folder categories. When upgrading, a document named migrated_categories_for_parent_folder is created in folders that had categories assigned to them in Oracle Files. These documents contain information about the categories. You can then use this information to create new categories, which you can assign to individual files in Oracle Content Services.

• The upgrade process recreates node configuration properties with their default values. If you have made changes to node configuration properties, you must reconfigure those properties after upgrading to Oracle Content Services 10.1.2. For more information, see "Managing Node Configurations" in Chapter 6, "Changing Oracle Content Services Configuration Settings" in Oracle Content Services Administrator's Guide.

• Items in the Archive are now organized by the date and time that they were moved into the Archive.

• Oracle Content Services supports locking files, but does not support locks on folders. Non-folder items in Oracle Files folders that are locked at the time of upgrade will be locked in the new Oracle Content Services installation.

• Oracle Content Services supports one schema per database, and one Oracle Content Services instance per Applications tier. If your existing Oracle Files installation has more than one schema per database, you must select one schema to upgrade to Oracle Content Services, and drop all other schemas when upgrading the database. For more information, see Chapter 5, "Upgrading the Oracle Collaboration Suite Database."

• The Oracle Content Services upgrade process can take a significant amount of time to complete. This depends on how many users and files exist in your current Oracle Files or Oracle Content Services installation.

• When upgrading, items in the Trash folder in Oracle Files are moved to the Files_trash subfolder of the new Trash folder in Oracle Content Services 10.1.2.

12.2.1 In 9.0.4 Oracle Files Contains Too Little Content to Merit Migration as Part of Upgrade Process

In some cases, you may have a large number of users provisioned in Oracle Internet Directory, yet very little content in Oracle Files. The process of migrating all provisioned users in time consuming and worth avoiding in cases where there is very little Files data to migrate. The following workaround can be employed if there is no Files content that requires migration or if there is so little content that it can easily be exported. If you use this workaround, all existing Files data will be lost.

1. Stop all the servers on all the middle tiers by performing the following:

   1. Setup the following variables: ORACLE_HOME=<mid tier home> PATH = $ORACLE_HOME/bin:$PATH

   2. $ORACLE_HOME/bin/opmnctl stopall

   3. As root $ORACLE_HOME/bin/ifs/files/bin/ifsctl stop

   4. From the Active EMD oracle home stop the EM server emctl stop

2. Modify targets.xml on ALL the midtiers:

   1. cd <Active EMD Oracle Home>/sysman/emd

   2. cp targets.xml targets.xml.orig

   3. Edit targets.xml and remove all target entries where "Target TYPE="oracle_ifs". For example, remove the following lines:

      <TargetTYPE="oracle_ifs"NAME="mt9041.hptok1.us.oracle.com_iFS_hptok1:1521:storedb.us.oracle.com:SOWFILES"DISPLAY_NAME="iFS_hptok1:1521:storedb.us.oracle.com:SOWFILES">

      <Property NAME="IfsRootHome" VALUE="/project/ocsd2/sow/mt9041/ohome/ifs"/>

      <Property NAME="SchemaPassword" VALUE="a847b91b39528712" ENCRYPTED="TRUE"/>

      <Property NAME="DomainName" VALUE="ifs://hptok1:1521:storedb.us.oracle.com:SOWFILES"/>

      <Property NAME="SysadminUsername" VALUE="system"/>

      <Property NAME="SysadminPassword" VALUE="0633fc23172176c17b7e2642baf7af9a" ENCRYPTED="TRUE"/>

      <Property NAME="IfsHome" VALUE="/project/ocsd2/sow/mt9041/ohome/ifs/files"/>

      <CompositeMembership>

      <MemberOf TYPE="oracle_ias" NAME="mt9041.hptok1.us.oracle.com"/>

      </CompositeMembership>

      </Target>

3. Remove the entries from Oracle Internet Directory

   1. Go to the Infra machine and connect to the OID server via $INFRA_HOME/bin/oidadmin.

   2. Login as orcladmin user

   3. Navigate to cn=IFS, cn=Products, cn=OracleContext under "Entry Management"

   4. Delete entries in this section by right-clicking and selecting "Delete"

      Sample entry:

      orclApplicationCommonName=hptok1:1521:storedb.us.oracle.com:SOWFILE,cn=IFS,cn =Products,cn=OracleContext

      Format:

      orclApplicationCommonName=<mid tier hostname>:<DB listener port>:<DBhost>:<Files schema name>,cn=IFS,cn=Products,cn=OracleContext

   5. Drop the Files schema:

      On the DB store, sqlplus as "sys as sysdba"

      SQL> drop user < FILES schema name > cascade;

      SQL> drop user < FILES schema name >$CM cascade;

      SQL> drop user < FILES schema name >$ID cascade;

      SQL> drop user < FILES schema name >$DR cascade;

   6. Drop the associated Files Schema tablespaces.

   7. Create workflow schema from only one middle tier.

      From one of the upgraded schema create the workflow schema as mentioned in the Content Services Admin Guide (Chapter 3) using ORACLEHOME/wf/install/wfinstall.csh

   8. Configure Content Services using Enterprise Manager. For more information, please see Appendix B of the Oracle Content Services Administration Guide.

12.3 Upgrading from Oracle Content Services 10.1.1

The upgrade from Oracle Content Services 10.1.1 to 10.1.2 is a schema upgrade. Oracle Content Services 10.1.2 uses the same Oracle home as Oracle Content Services 10.1.1.

Oracle Content Services 10.1.2 provides a Web user interface, WebDAV access, and Oracle Drive functionality immediately after upgrading. FTP access is not available after upgrading, and must be enabled manually.

In addition, the upgrade installs Oracle Records Management, a records management application that ships with Oracle Content Services. The application is disabled by default, and is subject to a separate license.

12.4 Post-Upgrade Tasks for Oracle Content Services

After upgrading, perform the following tasks:

• Users in an upgraded version of Oracle Internet Directory do not get provisioned into Oracle Content Services. In 10.1.2, "Everyone" should have browse access in the public group container and the user container. In the previous release, "Everyone" is denied. The ACLs for those containers are not modified during upgrade to avoid conflicts with any customized ACLs from the user. Some additional steps are required.

  1. Login into ODM as cn=orcladmin

  2. Expand Entry Management -> dc=com -> dc=<domain>, dc=<realm> (4 clicks)

  3. Click cn=Groups

  4. Click the Local Access tab

  5. Select the row containing 'Everyone'

  6. Click Edit

  7. Click Access Rights

  8. Click the Grant Column corresponding to Browse (Add, Proxy, Delete can be left as Deny)

  9. Click OK

  10. Click cn=Users

  11. Repeat step 4 through 9.

• If you are upgrading from Oracle Content Services 10.1.1, edit the IFS.SERVICE.JDBC.DriverType service configuration property. In Oracle Content Services 10.1.1, the value of this property was not recognized, and used the thin driver regardless of the value of this property. In Oracle Content Services 10.1.2, the default value is oci8 (thick driver).

• Oracle Collaboration Suite 10g Release 1 (10.1.2) includes an updated Korean lexer. After upgrading, reindex your Korean language content. For more information, see Appendix G, "Oracle Content Services Globalization Support" in Oracle Content Services Administrator's Guide.

• Oracle Content Services 10.1.2 includes two new agents, the Background Processing Agent and the Refresh Security Agent. After upgrading, configure these agents on the appropriate nodes. For more information, see Appendix E, "Server Configuration Properties" in Oracle Content Services Administrator's Guide.

• Oracle Content Services does not support setting expiration dates for users. If any Oracle Files users were marked with an expiration date after the date of the upgrade, the users will not be removed automatically by Oracle Content Services. You must remove those users manually.