| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.1) for Linux Part Number B15793-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.1) for Linux Part Number B15793-02 |
|
|
View PDF |
You might have an existing Database that you might want to use for storing Oracle Collaboration Suite data. You can use the Enable existing 10g Database to Collaboration Suite Database option during the installation process to do so. This option seeds the Oracle Collaboration Suite schemas in the specified Database and then registers the Database within Oracle Internet Directory so that the applications can be configured against this Database for a subsequent Applications tier installation.
Note:
Enabling databases is currently not supported for Real Application Clusters with RAW storage type.This chapter contains the following sections:
To be able to install Oracle Collaboration Suite in an existing database, you must complete the following requirements:
System requirements
Refer to Chapter 2 for detailed information.
Oracle Collaboration Suite 10g Infrastructure requirements
You need an operational Oracle Internet Directory to register your database.
Database requirements
You need Oracle Database 10g (10.1.0.4.2) for the Oracle Collaboration Suite installation to be successful. If you have an earlier version of database, for example Oracle Database 10g (10.1.0.2) or Oracle Database 10g (10.1.0.3) or Oracle Database 10(10.1.0.3), then you must apply the Oracle Database 10g Release 1 (10.1.0.4.2) patch set to this existing database.
Refer to Section 5.2.1 for detailed information on applying the patch set.
Character set requirements
The Oracle Database 10g (10.1.0.4.2) you select must be configured with the AL32UTF8 character set, which is the supported character set for Oracle Collaboration Suite. However, for upgrade from a previous release, the UTF8 character set is also supported, although the AL32UTF8 character set is recommended.
You may either choose another database with a supported character set or migrate the Database character set following the procedures in the Globalization Support white paper available at:
http://www.oracle.com/technology/tech/globalization/pdf/TWP_AppDev_Unicode_10gR2.pdf
Note:
When choosing the Enable existing 10g Database to Collaboration Suite Database option during installation, ensure that Oracle Enterprise Manager has been installed into the ORACLE_HOME of the Database. This is required for the installation to finish successfully.Also, currently, you cannot enable a custom Database as Oracle Collaboration Suite Database, if the custom Database connection string (the value of orclNetDescString, as registered in Oracle Internet Directory) is longer than 256 characters and the environment variable TNS_ADMIN is not set prior to the installation.
This section contains the following topics:
You need Oracle Database 10g (10.1.0.4.2) for the Oracle Collaboration Suite installation to be successful. If you have an earlier version of database, for example Oracle Database 10g (10.1.0.2) or Oracle Database 10g (10.1.0.3), then you must apply the Oracle Database 10g Release 1 (10.1.0.4.2) patch set to this existing Database.
This section contains the following topics:
The following are the system requirements for this patch set:
Linux
Oracle Database 10g (10.1.0.2) or later
Complete the following preinstallation tasks before installing the patch set:
Review Known Preinstallation Issues
Review the information in the following sections. If any of the issues apply to your Oracle installation, then follow the instructions before installing the patch set:
Adding a Second Node to An Existing Single-Node Oracle Real Application Clusters Installation
Upgrading Installations that use Physical or Logical Standby Databases
Upgrading Oracle Workspace Manager and Oracle Messaging Gateway
Upgrading Installations that use Java Virtual Machine or Oracle interMedia
Adding a Second Node to An Existing Single-Node Oracle Real Application Clusters Installation
If you installed Oracle Real Application Clusters, 10g release 1 (10.1.0.2 or 10.1.0.3) on a single node and created a database during the installation, then the initialization parameter DB_RECOVERY_FILE_DEST might be set incorrectly if you made the following choices:
You specified a local directory path for the Oracle home directory.
You chose the General Purpose, Data Warehousing, or Transaction Processing database configuration option.
You chose not to enable automated backups.
If you made these choices, then the DB_RECOVERY_FILE_DEST parameter incorrectly specifies a directory on the local file system (either $ORACLE_BASE/flash_recovery_area or $ORACLE_HOME/flash_recovery_area, depending on your environment settings). Because this directory is not shared, this setting prevents you from adding another node to your Oracle Real Application Clusters installation.
Note:
This problem does not occur if you choose the Custom installation type or choose the Advanced database configuration option during the installation or use the DBCA to create an Oracle Real Application Clusters database after you have installed the software.This issue is tracked with Oracle bug 3480750.
Upgrading to or Installing Release Oracle Database 10g Release (10.1.0.4.2) on a Fujitsu PRIMECLUSTER System
For information on how to upgrade to or install Oracle Database 10g release 1 (10.1.0.4.2) on a Fujitsu PRIMECLUSTER system, refer to the following documents:
Document 263719.1 available on the OracleMetaLink Web site:
SMAWrac10g.readme.html, available on the Fujitsu Web site:
http://uc.fujitsu.com/Oracle/downloads/SMAWrac10g.readme.html
Upgrading Oracle E-Business Suite Databases
If you are an Oracle E-Business Suite customer and you want to upgrade your Oracle E-Business Suite release 11i database server to this patch set, then you must check the latest certification status and Interoperability Notes available on the OracleMetaLink Web site:
Upgrading Installations that use Physical or Logical Standby Databases
Before applying this patch set to an Oracle Database 10g release 1 (10.1.0.2 or 10.1.0.3) installation that uses one or more physical or logical standby databases, review the following OracleMetaLink documents:
For information about physical standby databases, review document 278641.1.
For information about logical standby databases, review document 278643.1.
These documents are available on the OracleMetaLink Web site:
Rolling Upgrades Using Oracle Data Guard SQL Apply
If you use logical standby databases, then you can use Oracle Data Guard SQL Apply to perform rolling upgrades to upgrade Oracle Database 10release 1 (10.1.0.2) Oracle Database 10g release 1 (10.1.0.3) to release 1 (10.1.0.4.2). During a rolling upgrade, you can run different releases of the Oracle software on the primary and logical standby databases while you upgrade them one at a time. If you do this, then you will incur minimal downtime on the primary database. For information and instructions on rolling upgrades with logical standby databases, review document 300479.1, available on the OracleMetaLink Web site:
Upgrading Preconfigured Standard Edition Databases
If you are using an Oracle Database 10g release 1 (10.1.0.2 or 10.1.0.3) preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:
Oracle Data Mining
Oracle OLAP Catalog
Oracle OLAP Analytic Workspace
Oracle OLAP API
Spatial
The catpatch.sql script does not run the patch scripts for these components. It sets the component STATUS to OPTION OFF in the DBA_REGISTRY view. The original versions of the dictionary objects for the components remain in the database, but the catpatch.sql script does not apply the patch to them.
Upgrading Oracle Workspace Manager and Oracle Messaging Gateway
Oracle Workspace Manager and Oracle Messaging Gateway are not upgraded by this patch set installation. If the Oracle Database 10g release 1 (10.1.0.2 or 10.1.0.3) installation includes these components, then upgrade them separately with patches specific to these products.
Upgrading Installations that use Java Virtual Machine or Oracle interMedia
If any of the databases use Java Virtual Machine or Oracle interMedia, then install the Oracle Database 10g Products installation type from the Oracle Database 10g Companion DVD before installing the 10.1.0.4.2 patch set.
For information about installing the Oracle Database 10g Products installation type from the Companion DVD, refer to the Oracle Database 10g Installation Guide or the Oracle Database 10g Companion CD Installation Guide available at
This installation type includes the Natively Compiled Java Libraries (NCOMP) files to improve Java performance. If you do not install the NCOMP files, then the "ORA-29558:JAccelerator (NCOMP) not installed" error occurs when a database that uses Java VM is upgraded to the patch release.
Upgrading Oracle Cluster Ready Services
The Oracle Cluster Ready Services software (CRS) must be at the same or newer level as the Oracle software in the Oracle Real Application Clusters Oracle home. Therefore, you should always upgrade CRS before you upgrade Oracle Real Application Clusters.
However, before you upgrade CRS to 10.1.0.4.2, you must apply the patch for Oracle bug 3671865 to all the release 10.1.0.2 Oracle Real Application Clusters Oracle home directories that are part of your cluster database environment. This patch is required so that 10.1.0.2 Oracle Real Application Clusters Oracle homes can operate with the upgraded 10.1.0.4.2 CRS software.
You must apply this patch to the Oracle Real Application Clusters Oracle homes even if you later upgrade the Oracle homes to 10.1.0.4.2 after you upgrade CRS.
Identify the Oracle Database Installation
This is not a complete software distribution. You must install it in an existing Oracle Database 10g Oracle home. To identify Oracle home directories, view the /var/opt/oracle/oratab/etc/oratab/etc/oratab/etc/oratab file.
If you are installing this patch set on an existing Oracle Real Applications Cluster 10g release 10.1.0.2 or 10.1.0.3 10.1.0.2 or 10.1.0.3 10.1.0.2 10.1.0.2 installation, then you must run Oracle Universal Installer from the same node from which the Oracle Database software was installed.
Check Postrelease Updates
Before installing this patch set in a production environment, review document 263719.1, ALERT: Oracle 10g Release 1 (10.1) Support Status and Alerts, available on the OracleMetaLink Web site:
To locate this document:
Log on to OracleMetaLink.
Click Advanced at the top of the OracleMetaLink page.
Enter 263719.1 in the Document ID field, then click Submit.
This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.
Extract the Installation Software
To extract the patch set installation software:
Extract the appropriate patch set from the Oracle Collaboration Suite Supplemental DVD to a directory that is not the Oracle home directory or under the Oracle home directory.
Enter the following command to unzip and extract the installation files:
$ unzip patchset_name.zip
In the preceding command, patch set_name represents the appropriate patch set for your platform.
Set the ORACLE_HOME and ORACLE_SID Environment Variables
Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:
Bourne, Bash, or Korn shell:
$ ORACLE_HOME=oracle_home $ ORACLE_SID=sid $ export ORACLE_HOME ORACLE_SID
C shell:
% setenv ORACLE_HOME oracle_home % setenv ORACLE_SID sid
In these examples, oracle_home is the Oracle home directory where the Oracle Database 10g installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.
Shut Down Oracle Databases
Shut down any existing Oracle Database instances with normal or immediate priority. On Oracle Real Application Clusters systems, shut down all instances on each node.
If Automatic Storage Management (ASM) is running, then shut down all databases that use ASM, then shut down the ASM instance on each node of the cluster.
Note:
If you are using CRS, then you must shut down all Oracle Database instances on all cluster nodes before applying the patch set to the CRS installation. All Oracle Database instances are restarted during the CRS patch set installation. After the CRS patch set installation is complete, you must shut down all Oracle Database and ASM instances running in the Oracle Real Application Clusters Oracle home before patching the Oracle Real Application Clusters Oracle home.Stop All Processes
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.
Note:
If you shut down ASM instances, then you must first shut down all database instances that use ASM, even if these databases run from different Oracle homes.If you are upgrading a single instance installation, then shut down the following Oracle Database 10g services before installing the patch set:
Note:
You must perform these steps in the order listed.Shut down any processes in the Oracle home that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus.
Note:
Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.Shut down all database instances.
Shut down the ASM instance, if the ASM instance is running in the Oracle home to be patched.
Shut down all listeners.
Shut down the Oracle Cluster Synchronization Services (CSS) daemon as the root user:
# /etc/init.d/init.cssd stop
If you are upgrading a CRS installation, then shut down the following Oracle Database 10g services before installing the patch set:
Note:
You must perform these steps in the order listed.Shut down any processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.
Note:
Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.Shut down all Oracle Real Application Clusters instances on all nodes. To shut down all Oracle Real Application Clusters instances for a database, enter the following command where db_name is the name of the database:
$ oracle_home/bin/srvctl stop database -d db_name
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
$ oracle_home/bin/srvctl stop asm -n node
Stop all node applications on all nodes. To stop node applications running on a node, enter the following command, where node is the name of the node where the applications are running:
$ oracle_home/bin/srvctl stop nodeapps -n node
Shut down the CRS process by entering the following command on all nodes as the root user:
# /etc/init.d/init.crs stop
Note:
If the CRS installation is not on a shared Oracle home, then you can upgrade the CRS installation one node at a time. To do this, perform the preceding steps only on the first node that you are upgrading, then follow the instructions on the installer screen.If you are upgrading an Oracle Real Application Clusters installation and node applications are running in the Oracle Real Application Clusters Oracle home, then shut down the following Oracle Database 10g services before installing the patch set:
Note:
You must perform these steps in the order listed.Shut down any processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.
Note:
Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage.Shut down all Oracle Real Application Clusters instances on all nodes. To shut down all Oracle Real Application Clusters instances for a database, enter the following command where db_name is the name of the database:
$ oracle_home/bin/srvctl stop database -d db_name
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command, where node is the name of the node where the ASM instance is running:
$ oracle_home/bin/srvctl stop asm -n node
Stop all node applications on all nodes. To stop node applications running on a node, enter the following command, where node is the name of the node where the applications are running:
$ oracle_home/bin/srvctl stop nodeapps -n node
Back Up the System
Oracle recommends that you create a backup of the Oracle Database 10g installation before you install the patch set. After the patch set is installed, there is no way to remove it.
You can install the patch set either interactively or noninteractively. Refer to one of the following sections for information about how to complete the installation:
To install the patch set interactively, refer to Installing the Oracle Database 10g Patch Set Interactively.
To install the patch set noninteractively, refer to Installing the Oracle Database 10g Patch Set Noninteractively.
Installing the Oracle Database 10g Patch Set Interactively
To install the Oracle Database 10g patch set interactively:
Note:
If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle Database 10g release (10.1.0.2 or 10.1.0.3) installation, then Oracle Universal Installer displays a warning dialog with the following error:There are no patches that need to be applied from the patchset Oracle Database 10g Patchset 2 10.1.0.4.2
The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation.
Log in as the oracle user.
If you are not installing the software on the local system, then enter the following command to direct X applications to display on the local system:
Bourne, Bash, or Korn shell:
$ DISPLAY=local_host:0.0 ; export DISPLAY
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).
Enter the following commands to start Oracle Universal Installer, where patchset_directory is the directory where you unzipped the patch set software:
% cd patchset_directory/Disk1 % ./runInstaller
Note:
To install the Oracle9i globalization support locale definition files, then enter the following commands to run Oracle Universal Installer:% ./runInstaller oracle.rsf.nlsrtl_rsf:b_cr9idata=true
On the Welcome screen, click Next.
On the Specify File Locations screen, click Browse next to the Path field in the Source section.
Select the products.xml file from the stage directory where you unpacked the patch set files, then click Next. For example:
directory_path/stage/products.xml
In the Name field in the Destination section, select from the drop-down list the name of the Oracle home that you want to update, then click Next.
If you are installing the patch set on an Oracle Real Application Clusters cluster, then click Next when the Selected Nodes screen appears.
Note:
The Selected Nodes screen lists the existing Oracle Real Application Clusters 10g release 1 nodes. The first node in the list is the node from where the Oracle Real Application Clusters 10g release 1 software was installed. You must install the patch set software from this node. If this is not the node where you are running Oracle Universal Installer, then exit Oracle Universal Installer and install the patch set software from the first node in the list of nodes.Alternatively, reset the node order as follows:
Exit Oracle Universal Installer.
Enter a command similar to the following, where the node that you want to install the patch set from is the first node in the list of nodes:
$ runInstaller -updateNodeList "CLUSTER_NODES=node2, node1,node3" -local ORACLE_HOME=oracle_home_path
In this example, the Oracle Real Application Clusters 10g release 1 software was installed from node1, but the patch set will be installed from node2.
Start Oracle Universal Installer from the first node in the list.
On the Summary screen, click Install.
This screen lists all the patches available for installation.
When prompted, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle Real Application Clusters installation, then run the root.sh script on each node of the cluster.
Note:
If you are applying this patch set to a CRS installation:If you shut down all CRS services on all nodes as described in Section 5.2.1.2 before starting the installation, then complete all the steps except the first step in the instructions displayed by the installer screen.
If you did not shut down all CRS services on all nodes, then complete all the steps in the instructions displayed by the installer screen.
In either case, you will not be prompted to run the root.sh script.
The CRS installation instructions displayed by the installer screen are also available in the CRS_HOME/install/readme.txt file.
On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.
Installing the Oracle Database 10g Patch Set Noninteractively
To install the Oracle Database 10g patch set noninteractively
Copy the response file template provided in the response directory where you unpacked the patch set archive file.
Edit the values for all fields labeled as <Value Required> as described by the comments and examples in the template.
Note:
To install the Oracle9i globalization support locale definition files, then set theb_cr9idata variable to True in the response file.
For Oracle Real Application Clusters installations, make sure the CLUSTER_NODES variable specifies all the nodes used in the original Oracle Real Application Clusters installation.
To run Oracle Universal Installer, enter a command similar to the following, where response_file is the full path to the response file that you edited:
% ./runInstaller -silent -responseFile response_file
After the installation, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle Real Application Clusters installation, then run the root.sh script on each node of the cluster.
Note:
If you are applying this patch set to a CRS installation:If you shut down all CRS services on all nodes as described in Section 5.2.1.2 before starting the installation, then complete all the steps except the first step in the CRS_HOME/install/readme.txt file.
If you did not shut down all CRS services on all nodes, then complete all the steps in the CRS_HOME/install/readme.txt file.
Review the information in this section before using the upgraded software. This section lists required and optional postinstallation tasks, depending on the installation type and the products that you want to use.
Upgrading Release 9.2 and Earlier Databases Directly to Oracle Database 10g Release 1 (10.1.0.4.2)
Running the configPatch.pl Script on an Oracle Real Application Clusters (Oracle RAC)
Oracle Enterprise Manager Postinstallation Steps for Database Console
Upgrading Release 9.2 and Earlier Databases Directly to Oracle Database 10g Release 1 (10.1.0.4.2)
After you have installed the patch set software, use one of the following methods to upgrade Oracle Databases from a previous release, as described in the Oracle Database Upgrade Guide:
Run the u0902000.sql, u0900010.sql, u0801070.sql, or u0800060.sql upgrade scripts. These scripts are installed in the $ORACLE_HOME/rdbms/admin directory.
Use the Database Upgrade Assistant to perform the upgrades. If you are upgrading an Oracle Real Application Clusters database, then the Database Upgrade Assistant might display the following message:
The database databasename does not have the cluster configuration and also is not listed in the registry of remote cluster nodes. Do you want the Database Upgrade Assistant to continue upgrading it as noncluster database?
If this message appears, then do one of the following:
From the database Oracle home, run the srvctl command to add the database configuration information to the Oracle Cluster Register (OCR). See the Oracle Real Application Clusters Administrator's Guide
On all nodes of the cluster, add the following entry to the oratab file:
databasename:oraclehome:N
Upgrading an Oracle9i Database to Oracle Database 10g
If you upgrade an Oracle9i database to Oracle Database 10g release 1, then Oracle Flashback features using a timestamp may fail. To work around this problem, enter the following SQL script from the Oracle Database 10g database:
SQL> DELETE FROM smon_scn_time WHERE orig_thread <> 0; SQL> COMMIT;
This issue is tracked with Oracle bug 3994270.
Upgrading a Release 9.2 Database Not Using OLS
To avoid errors when you are upgrading an Oracle9i Release 2 preconfigured database but are not using Oracle Label Security (OLS), complete the following steps.:
Use Oracle Universal Installer release 9.2 to install OLS using the Custom installation type.
Run the $ORACLE_HOME/rdbms/admin/catnools.sql script from the SQLPlus interface with the SYSDBA privilege to remove OLS components from the database.
Required Postinstallation Tasks
Review the Check Tablespace Sizes and Set Parameter Values section and complete the steps in the Upgrade the Release 10.1 Database section after you have installed the patch set software.
Check Tablespace Sizes and Set Parameter Values
Review the following sections before upgrading a database.
Check SYSTEM Tablespace Size
If JServer is part of the installation, then ensure that at least 10 MB of free space is allocated to the SYSTEM tablespace.
Check XDB Tablespace Size
For Oracle Real Application Clusters installations, ensure that at least 50 MB of free space is allocated to the XDB tablespace.
Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters, as follows:
Start the database:
SQL> STARTUP
If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
SQL> SHOW PARAMETER PFILE;
This command displays the name and location of the server parameter file or the initialization parameter file.
Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE SQL> SHOW PARAMETER JAVA_POOL_SIZE
If the system is using a server parameter file:
If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
If the system uses an initialization parameter file, then, if necessary, change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).
Ensure that the value of the SGA_TARGET initialization parameter size is greater than the sum of the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters.
Shut down the database:
SQL> SHUTDOWN
Upgrade the Release 10.1 Database
After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:
Note:
If you do not run thecatpatch.sql script, as described in this section, and start up a database for normal operation, then "ORA-13516: SWRF Operation failed: CATPROC not valid" errors will occur.Log in as the Oracle software owner user.
For Oracle Real Application Clusters installations, start node applications on each node of the cluster as follows:
$ srvctl start nodeapps -n nodename
If you are using ASM, then start the ASM instance.
For single-instance installations, start the listener, as follows:
$ lsnrctl start
Note:
If you are using the Oracle OLAP option, then make sure that the listener is running.For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog SQL> CONNECT / AS SYSDBA
For Oracle Real Application Clusters installations:
Start the database, where db_name is the database name and inst_name is the local instance name:
$ srvctl start instance -d db_name -i inst_name
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog SQL> CONNECT / AS SYSDBA
Set the CLUSTER_DATABASE initialization parameter to FALSE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
Shut down the database:
SQL> SHUTDOWN
Enter the following SQL*Plus commands:
SQL> STARTUP UPGRADE SQL> SPOOL patch.log SQL> @?/rdbms/admin/catpatch.sql SQL> SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script. This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catpatch.sql script after correcting any problems.
Restart the database:
SQL> SHUTDOWN SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @?/rdbms/admin/utlrp.sql
Note:
When the 10.1.0.4.2 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 42 invalid objects after theutlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.
Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following:
BIN$4lzljWIt9gfgMFeM2hVSoA==$0
If you are using the Oracle Recovery Manager catalog, then enter the following command:
$ rman catalog username/password@alias RMAN> UPGRADE CATALOG;
For Oracle Real Application Clusters installations:
Set the CLUSTER_DATABASE initialization parameter to TRUE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
Restart the database:
SQL> SHUTDOWN SQL> STARTUP
Start any services that you want to use:
srvctl start service -d db_name -s service_name
Running the configPatch.pl Script on an Oracle Real Application Clusters (Oracle RAC)
The configPatch.pl script updates the Oracle Enterprise Manager Database Control files. Although Oracle Universal Installer copies the configPatch.pl script to all the Oracle homes on the cluster, it runs the script only on the node running Oracle Universal Installer.
If you install this patch on an Oracle Real Application Clusters installation that does not use a shared Oracle home directory, then you must manually run the $ORACLE_HOME/sysman/install/configPatch.pl script on each node of the cluster, except on the node from which you ran Oracle Universal Installer.
Note:
These instructions do not apply to Oracle Real Application Clusters installations where the nodes of the cluster share the same Oracle home.Resetting the DBMS_SCHEDULER Time Zone
If you created a preconfigured database during the Oracle Database 10g release 1 installation, then specify the local time zone, as follows:
Start SQL*Plus:
$ sqlplus "/ AS SYSDBA"
If necessary, start the database:
SQL> STARTUP
Enter the following command:
SQL> SELECT TZNAME FROM V$TIMEZONE_NAMES;
The output from this command lists the different time zone settings for the TZNAME attribute.
From the output of the preceding command, identify the time zone for your location.
Reset the DEFAULT_TIMEZONE attribute for the scheduler, where timezone is the time zone that you identified in the previous step:
SQL> BEGIN
DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('DEFAULT_TIMEZONE','timezone');
END ;
/
The DEFAULT_TIMEZONE attribute determines the time zone that the maintenance windows use.
This issue is tracked with Oracle bug 3721687.
Oracle Enterprise Manager Postinstallation Steps for Database Console
If you upgraded a release 10.1.0.2 or 10.1.0.3 database configured to use Oracle Enterprise Manager Database Console to release 10.1.0.4.2, then you must perform the following steps:
Note:
On Oracle Real Application Clusters, perform these steps on each node of the cluster.Enter the following command:
SQL> SELECT TZNAME FROM V$TIMEZONE_NAMES;
The output from this command lists the different time zone settings for the TZNAME attribute.
Set the TZ environment variable to your time zone:
Bourne, Bash, or Korn shell:
$ TZ=timezone; export TZ
C shell:
% setenv TZ timezone
Set the ORACLE_SID environment variable:
Bourne, Bash, or Korn shell:
$ ORACLE_SID=sid ; export ORACLE_SID
C shell:
% setenv ORACLE_SID sid
If you tried unsuccessfully to start the Database Console after you upgraded the database, then enter the following command:
$ oracle_home/bin/emctl stop dbconsole
Enter the following command:
$ oracle_home/bin/emctl resetTZ agent
This command updates the $ORACLE_HOME/hostname_sid/sysman/config/emd.properties file to match the value of the TZ environment variable. It also returns the command required in Step 7.
Connect to the database as an Enterprise Manager Repository user (SYSMAN):
$ sqlplus SYSMAN/sysman_password
Note:
Alternatively, you can connect as theSYS user with SYSDBA privileges, as follows:
$ sqlplus SYS/sys_password AS SYSDBA
After you connect as the SYS user, alter the session to run as SYSMAN:
SQL> ALTER SESSION SET current_schema = SYSMAN;
Enter the command displayed in Step 5, for example:
SQL> EXEC MGMT_TARGET.SET_AGENT_TZRGN('host_name.domain_name:1830','PST8PDT')
SQL> COMMIT
Exit SQL*Plus.
SQL> EXIT;
Start Oracle Enterprise Manager Database Console:
$ emctl start dbconsole
This issue is tracked with Oracle bug 4132656.
Automatically Restarting Oracle Notification Service
For Oracle Database 10g release 1 (10.1.0.2) installations, the Oracle Notification Service (ONS) AUTO_START parameter is set to 0 on each node of the cluster. For this reason, CRS does not automatically start ONS when the node is restarted.
To work around this issue, perform the following steps as the CRS owner for each ONS resource:
Change directory to the crs_home/crs/public directory.
Use the following command to create a file containing the profile resources:
$ crs_home/bin/crs_stat -p ora.nodename.ons > ora.nodename.ons.cap
Enter the following command to change the AUTO_START parameter value to 1 in the ora.nodename.ons.cap file:
$ crs_home/bin/crs_profile -update ora.nodename.ons -o as=1
Enter the following command to update the resource profile:
$ crs_home/bin/crs_register -u ora.nodename.ons
This issue is tracked with Oracle bug 4011834.
Caution:
To use your existing Oracle 10g Database as an Oracle Collaboration Suite Database, you must run the Metadata Repository Creation Assistant (MRCA) PRIOR to running Oracle Universal Installer and choosing the Enable existing 10g Database to Collaboration Suite Database option.This section contains the following topics:
Before you start to install Oracle Collaboration Suite in an existing Database, ensure that the kernel parameters are set as listed in Table 5-1.
Table 5-1 Database Configuration Parameters and Their Minimum Values for Installing Oracle Collaboration Suite in an Existing Database
| Kernel Parameter | Minimum Value of the Parameter |
|---|---|
pga_aggregate_target |
203423744 |
db_cache_size |
150994944 |
session_max_open_files |
50 |
processes |
250 |
sga_max_size |
629145600 |
aq_tm_processes |
1 |
db_recovery_file_dest_size |
2147483648 |
star_transformation_enabled |
TRUE |
sga_target |
629145600 |
compatible |
10.1.0.4.2 |
shared_pool_size |
184549376 |
sessions |
400 |
job_queue_processes |
10 |
java_pool_size |
125829120 |
dml_locks |
200 |
max_commit_propagation_delay |
0 |
dispatchers |
(PROTOCOL=TCP) (SERVICE={SID}XDB) |
open_cursors |
400 |
db_block_size |
8192 |
remote_login_passwordfile |
EXCLUSIVE |
undo_management |
AUTO |
db_file_multiblock_read_count |
32 |
Perform the steps listed in Table 5-2 to install Oracle Collaboration Suite in an existing database.
Note:
Oracle Universal Installer uses the/etc/hosts file to determine the host name. The host name that you specified in the hosts file may or may not be fully qualified. However, host names that are not fully qualified may not be usable outside the domain.
For example, if the fully-qualified domain name for a server is myserver.acme.uk, and the hosts file only registers the name myserver, then clients in the acme.co.uk domain have no trouble communicating with this host. However connections made by users in the acme.co.de domain may fail.
Also, ensure that the host name that you specify corresponds exactly to the host name you have, whether fully qualified or not.
Table 5-2 Screens for Installing Oracle Collaboration Suite in an Existing Database
| Step | Screen | Action |
|---|---|---|
| 1. | None | Start the installer.
Refer to Section 3.4 for more information about starting the installer. |
| 2. | Select Installation Method | Select Advanced Installation.
Note Click Next. |
| 3. | Specify Inventory Directory and Credentials
(Advanced installation only) |
This screen appears only if this is the first installation of any Oracle product on this computer.Enter the full path of the inventory directory. Enter a directory that is different from the Oracle home directory for the product files.Example: var/opt/oracle/oraInventory
Enter the name of the operating system group that will have write permission for the inventory directory.Example: Click Next. |
| 4. | Run orainstRoot.sh
(Advanced installation only) |
This screen appears only if this is the first installation of any Oracle product on this computer.Run the orainstRoot.sh script in a different shell as the root user. The script is located in the oraInventory directory.After running the script, click Continue. |
| 5. | Specify File Locations
(Advanced installation only) |
Enter the full path of the Source directory in the Path field for Source.
Enter a name to identify the Oracle home in the Name field for Destination. The name cannot contain spaces and has a maximum length of 16 characters.Example: Enter the full path to the destination directory in the Path field for Destination. This is the Oracle home. If the directory does not exist, the installer creates it. To create the directory beforehand, create it as the Do not create the directory as the Click Next. |
| 6. | Specify Hardware Cluster Installation Mode
(Advanced installation only) |
This screen appears only if the computer is part of a hardware cluster.Select the computers in the hardware cluster where you want to install the Infrastructure. You can select multiple computers, or you can just select the current computer.Click Next. |
| 7. | Select a Product to Install
(Advanced installation only) |
Select Oracle Collaboration Suite Infrastructure 10.1.1.0.2.
Refer to Section 1.8 for more information about how to install support for support for additional languages. Click Next. |
| 8. | Select Installation Type
(Advanced installation only) |
The options displayed on this screen depend on what you select in the Select Product to Install screen.The installation types for Infrastructure are:
Select Enable existing Oracle 10g Database to Oracle Collaboration Suite Database and click Next. |
| 9. | Product-Specific Prerequisite Checks
(Advanced installation only) |
The installer verifies requirements such as memory, disk space, and operating system version. If any check fails, make the required changes and click Retry. Refer to Chapter 2 for the list of hardware and software requirements.
Click Next. |
| 10. | Language Selection
(Advanced installation only) |
This screen enables you to select the language in which Oracle Collaboration Suite components will run.
Select the required language or languages from the Available Languages list and add them to the Selected Languages list. Click Next. |
| 11. | Specify Oracle Internet Directory
(Advanced installation only) |
Host: Enter the name of the computer where Oracle Internet Directory is running.
Port: Enter the port number at which Oracle Internet Directory is listening. If you do not know the port number, refer to Section 8.5. Use SSL to connect to Oracle Internet Directory: Select this option if you want Oracle Collaboration Suite components to use only SSL to connect to Oracle Internet Directory. Click Next. |
| 12. | Oracle Internet Directory
(Advanced installation only) |
Username: Enter the user name to use to log in to Oracle Internet Directory.
Password: Enter the user password. Click Next. Note: Use |
| 13. | Specify Database Identification
(Advanced installation only) |
Username: Enter a database administrator name to log in to the existing database against which you want to install Oracle Collaboration Suite.
Password: Enter the password for the database administrator account you specified in the Username field. Hostname and Port: Enter the host name of the computer where the database that you want to use is installed. Also, specify the port that this database is using, as follows:
Service Name: Enter the service name for the database you want to use. SID: Enter the system identifier for the existing database that you want to use. Typically this is the same as the global database name, but without the domain name. Click Next. |
| 14. | Specify Database File Storage Option
(Advanced installation only) |
Select the storage mechanism that you would like to use for your database files.
To store the database files on a file system, select File System. For Oracle RAC installations, the file system that you choose must be a cluster file system or be on a certified network attached storage (NAS) device. To store the database files in an automatic storage management (ASM) disk group, select Automatic Storage Management. ASM disk groups are created by specifying one or more disk devices that will be managed by a separate Oracle ASM instance. For Oracle RAC installations, the disk devices that you add to the ASM disk group must be shared by all nodes of the cluster. Note: To be able to use ASM, Cluster daemons must be running and should be started by using the To store the database files on raw devices (raw partitions or raw volumes), select Raw Devices. To select this option, the required raw devices must already exist. For Oracle RAC installations, you must create the raw devices on disk devices that are shared by all nodes of the cluster. Click Next. Note: Depending on the option that you select in this screen, the following screen might differ from the one listed in the next step. |
| 15. | Specify Database File Location
(Advanced installation only) |
Directory for Database Files: Specify the location of the directory where you would like to store the Database files.
Note: For best database performance, Oracle recommends that you install database files (data files, control files, and redo logs) and the database on separate disks. Click Next. |
| 16. | Specify Database Schema Passwords
(Advanced installation only) |
Set passwords for privileged database accounts, which are used for database management and postinstallation tasks. Refer to Section 4.3.8 for rules on setting passwords for these accounts.
Set passwords for privileged Oracle Collaboration Suite Application accounts. The rules for setting the passwords that apply to the SYS and SYSTEM users also apply to these schemas. Click Next. |
| 17. | Summary | Verify your selections and click Install. |
| 18. | Install Progress | This screen displays the progress of the installation. |
| 19. | Run root.sh |
Note: Do not run the root.sh script until this dialog appears.
|
| 20. | Configuration Assistants | This screen shows the progress of the configuration assistants. Configuration assistants configure components. |
| 21. | End of Installation | Click Exit to quit the installer. |
Note:
If no information is displayed when you click Release Information at the end of this installation, then refer to:http://Infrastructure_host:infra_port_number/relnotes/toc.htm
