| Oracle® Application Server High Availability Guide 10g Release 2 (10.1.2) B14003-05 |
|
 Previous |
 Next |
| Oracle® Application Server High Availability Guide 10g Release 2 (10.1.2) B14003-05 |
|
Previous |
Next |
This chapter describes how to transform non-highly available installations to OracleAS Cluster (Identity Management) topologies.
This chapter assumes that you have read Chapter 19, "Transforming Non-Highly Available Topologies to Highly Available".
Section 20.1, "Overview of Transformation to OracleAS Cluster (Identity Management)"
Section 20.2, "Software, Hardware, and Documentation Requirements"
You can transform your source topology to an OracleAS Cluster (Identity Management) topology or to a distributed OracleAS Cluster (Identity Management) topology. In both versions, you transform the source OracleAS Metadata Repository to a Real Application Clusters database, and the Oracle Identity Management components to an OracleAS Cluster (Identity Management).
In an OracleAS Cluster (Identity Management) topology, the Oracle Identity Management components run from the same Oracle home. See Figure 19-1.
In a distributed OracleAS Cluster (Identity Management) topology, Oracle Internet Directory and Oracle Directory Integration and Provisioning run from one Oracle home on one set of nodes, and OracleAS Single Sign-On and Oracle Delegated Administration Services run from a different Oracle home on a different set of nodes. See Figure 19-2.
The starting, or source, configuration is the same for both transformations. The source configuration is described in Section 19.1, "Source Configuration".
In general, you perform the following steps to transform a non-highly available installation to an OracleAS Cluster (Identity Management) topology:
Transform the OracleAS Metadata Repository from a single-instance database to a Real Application Clusters database.
Transform the Oracle Identity Management components to run in an OracleAS Cluster (Identity Management). This includes configuring the components to use the virtual server names on load balancers, and installing additional instances.
Configure the middle tiers to use the virtual server names and Real Application Clusters database.
Before starting the transformation, check that you have the required software and hardware:
Additional nodes to run the Oracle Identity Management components
Additional nodes and clusterware to run the database as a Real Application Clusters database
External load balancers to distribute requests to the Oracle Identity Management and middle-tier nodes
For the OracleAS Cluster (Identity Management) topology, you need one load balancer.
For the distributed OracleAS Cluster (Identity Management) topology, you typically need two load balancers to send requests to two different sets of nodes located on opposite sides of a firewall. However, if your network topology allows it, you might be able to use one load balancer for both sets of nodes.
Oracle Database distribution CD-ROMs for installing the Real Application Clusters database
Oracle Application Server distribution CD-ROMs for installing additional instances of Oracle Application Server
Patches listed in Table 20-1. You can download the patches from OracleMetaLink (http://metalink.oracle.com).
Table 20-1 Required Downloads
| If you are running this database | You need these patches |
|---|---|
|
Oracle9i Release 2 (9.2) Database on UNIX |
|
|
Oracle9i Release 2 (9.2) Database on Windows |
|
|
Oracle Database 10g Release 1 (10.1) |
|
The detailed steps below specify when you apply the patches.
Documents Referenced by the Transformation Procedure
Some steps in the transformation procedure refer to the Oracle documentation listed in Table 20-2. To perform the transformation procedure, you must have these documents.
You can access these documents on Oracle Technology Network (http://www.oracle.com/technology/documentation), or on your Oracle distribution CD-ROMs.
Table 20-2 Documents Needed
| Product | Guides Needed |
|---|---|
|
Oracle Database |
If you are running Oracle9i Release 2 (9.2) Database, you need these guides:
You can find these guides on Oracle Technology Network: If you are running Oracle9i Release 2 (9.2) Database on Windows, you also need these notes from OracleMetaLink:
If you are running Oracle Database 10g Release 1 (10.1), you need these guides:
You can find these guides on Oracle Technology Network: |
|
Oracle Application Server |
|
To perform the transformation, follow these steps:
Step 1: Check Requirements for High Availability
Step 2: Back Up Your Environment
Step 3: Convert the Database to a Real Application Clusters Database
Step 4: Change the Source Oracle Identity Management to Use the OracleAS Metadata Repository in the Real Application Clusters Database
Step 5: Transform the Source Oracle Identity Management to Use the Virtual Server Names Configured on the Load Balancer
Step 6: (Distributed OracleAS Cluster (Identity Management) Case Only) Install OracleAS Single Sign-On and Oracle Delegated Administration Services
Step 7: Change the Middle Tier to Use the Virtual Server Names on the Load Balancer
Step 8: Install Additional Oracle Identity Management Instances
Step 9: Verify That All the Components Are Working
Step 10: Decommission the Oracle Homes That Are No Longer Used
|
Tip: It is possible to perform the transformation steps in two stages, instead of performing all the steps in one session. See Section 20.4, "Planning the Transformation" for details. |
Figure 20-1 shows these steps graphically for transformation to OracleAS Cluster (Identity Management). Figure 20-2 shows the steps for transformation to distributed OracleAS Cluster (Identity Management). Steps 1 and 2 are omitted from the figures.
Figure 20-1 Transforming to OracleAS Cluster (Identity Management)
Figure 20-2 Transforming to Distributed OracleAS Cluster (Identity Management)
When you are performing the transformation steps, the system is not available. If you are concerned about downtime, you can perform the transformation steps over two sessions. This would give you two shorter downtime periods, as opposed to one longer downtime period.
If you want to perform the steps in two sessions:
Perform steps 1 through 4 in the first session. At the end of step 4, the OracleAS Metadata Repository runs on a Real Application Clusters database, and Oracle Identity Management components are using that database.
Perform the rest of the steps in the second session.
Table 20-3 and Table 20-4 show the approximate duration of downtimes in the first and second sessions. These values are based on performing the transformation steps on Red Hat Enterprise Linux AS/ES 3.0, with Oracle Database 10g Release 1 (10.1.0.4) and Oracle Cluster File System. If you are using a different configuration, your downtimes may be different.
Table 20-3 Approximate Downtimes for Transformation Steps in the First Session
| Step | Downtime (approximate) |
|---|---|
|
Step 3, Convert the Database to a Real Application Clusters Database Note: This downtime number assumes a base OracleAS Metadata Repository database used by one middle tier and default applications only. If you have multiple middle tiers, and have added users, applications, and data used by the applications to the OracleAS Metadata Repository database, then you might experience a longer downtime. |
120 minutes |
|
Step 4, Change the Source Oracle Identity Management to Use the OracleAS Metadata Repository in the Real Application Clusters Database |
20 minutes |
|
Total |
140 minutes |
Table 20-4 Approximate Downtimes for Transformation Steps in the Second Session
| Step | Downtime (approximate) |
|---|---|
|
Step 5, Transform the Source Oracle Identity Management to Use the Virtual Server Names Configured on the Load Balancer |
30 minutes |
|
Step 6, (Distributed OracleAS Cluster (Identity Management) Case Only) Install OracleAS Single Sign-On and Oracle Delegated Administration Services |
35 minutes |
|
Step 7, Change the Middle Tier to Use the Virtual Server Names on the Load Balancer |
7 minutes |
|
Total |
72 minutes |
Note that the downtime numbers do not include the following steps because they do not incur any downtime:
performing steps 1 and 2
installing the Oracle home for the Real Application Clusters database
downloading patches and other software
taking backups of your source environment
configuring your load balancers
This section provides details on the transformation steps. Most of the steps include a figure showing what the topology looks like at the end of the step.
Step 1 Check Requirements for High Availability
Ensure that your system meets the requirements for creating a highly available topology. The requirements are listed in these guides:
Oracle Application Server Installation Guide, available on Disk 1 of the Oracle Application Server distribution. In particular, be sure to read the "Installing in High Availability Environments: OracleAS Cluster (Identity Management)" chapter.
For Oracle9i Real Application Clusters database requirements, see the Oracle9i Installation Guide.
For Oracle Database 10g Real Application Clusters requirements, see the Oracle Real Application Clusters Installation and Configuration Guide.
In addition, check the latest certification information for Real Application Clusters on OracleMetaLink (http://metalink.oracle.com):
Step 2 Back Up Your Environment
Before starting the transformation process, back up your environment so that you can restore the original environment in case of errors during the transformation process.
You should back up these installations:
OracleAS Metadata Repository database, including data files
Oracle Identity Management
Oracle Application Server middle tiers
You should also test your backups (by performing a restore operation) to ensure that these backups are valid. This exercise gives you the following benefits: you get practice in restoring from backup files, and a faster recovery means a shorter downtime.
The following steps show how to stop the Oracle Application Server processes and how to perform a simple backup using the tar command.
|
Downtime 1 Starts: The next step starts the first downtime. |
Stop all middle tier processes. MT_ORACLE_HOME indicates the Oracle home for your middle tier. You need to stop all middle tiers in your environment.
> MT_ORACLE_HOME/opmn/bin/opmnctl stopall > MT_ORACLE_HOME/bin/emctl stop iasconsole
Stop Oracle Identity Management processes. IM_ORACLE_HOME indicates the Oracle home for the Oracle Identity Management.
> IM_ORACLE_HOME/opmn/bin/opmnctl stopall > IM_ORACLE_HOME/bin/emctl stop iasconsole
Stop the OracleAS Metadata Repository database. SRC_MR_ORACLE_HOME indicates the Oracle home for the source OracleAS Metadata Repository.
> SRC_MR_ORACLE_HOME/bin/sqlplus /nolog
SQL> connect / as sysdba
SQL> shutdown
SQL> exit
Stop the database console:
> SRC_MR_ORACLE_HOME/bin/emctl stop dbconsole > SRC_MR_ORACLE_HOME/bin/emctl stop agent
Stop the listener:
> SRC_MR_ORACLE_HOME/bin/lsnrctl stop
Windows: in the Services panel, stop the database service.
Back up your environment. You can use any backup tools.
The following example shows how to use the tar command to back up the OracleAS Metadata Repository and Oracle Identity Management homes. If you are using tar, you need to become the root user.
> su Password: root_password # tar -cvfp SRC_MR_ORACLE_HOME mr.tar # tar -cvfp IM_ORACLE_HOME im.tar
You can use other backup and recovery mechanisms. For example, you can use the OracleAS Backup and Recovery Tool to perform the backup and restore operations. See the Oracle Application Server Administrator's Guide for details on using this tool.
Step 3 Convert the Database to a Real Application Clusters Database
After this step, your environment should look like this (Figure 20-3):
Figure 20-3 Step 3: Converting the Single-Instance Database to a Real Application Clusters Database
This step is divided into three sections based on the database platform and database version. Follow only the section appropriate for your database:
"Step 3A: Converting an Oracle9i Database on UNIX Platforms"
"Step 3B: Converting an Oracle Database 10g on UNIX Platforms"
Step 3A: Converting an Oracle9i Database on UNIX Platforms
This section describes how to convert a single-instance Oracle9i Database to a Real Application Clusters database that uses raw devices as its storage type.
Perform pre-installation steps listed in the following sections:
| Item | Name |
|---|---|
| Book | Oracle9i Real Application Clusters Setup and Configuration
This book is available in the Oracle9i Database documentation set. |
| Chapter | 10, "Converting to Real Application Clusters from Single-Instance Oracle Databases" |
| Section | In the section "Single Instance on a Cluster Running from non-Cluster Installed Oracle Home", perform the steps in these subsections:
Note: Do not run the "Install Oracle Software" step at this time. You will run it later. |
Create a file to associate OracleAS Metadata Repository tablespaces with raw devices, and set the DBCA_RAW_CONFIG environment variable to point to this file. Details:
Create the file. In the file, each line specifies a tablespace and corresponding raw device in the following format:
tablespace = raw_device
For a list of tablespaces required by the OracleAS Metadata Repository, see:
| Item | Name |
|---|---|
| Book | Oracle Application Server Metadata Repository Creation Assistant User's Guide
This guide is available on Disk 1 of the Oracle Application Server distribution. |
| Chapter | 1, "OracleAS Metadata Repository Creation Assistant Overview and Requirements" |
| Section | "Tablespace Sizes" |
|
Note: Make sure that theDCM and the Oracle Internet Directory tablespaces (OLTS_ATTRSTORE, OLTS_BATTRSTORE, OLTS_CT_STORE, OLTS_DEFAULT, OLTS_SVRMGSTORE) have at least 200 MB of free space. |
Example: The following lines show the contents of a file that you can use for the DBCA_RAW_CONFIG environment variable. In the example, "asdb" is the database SID, and "imha-dg" is the name of the disk group.
system=/dev/vx/rdsk/imha-dg/asdb_system_raw_1024m sysaux=dev/vx/rdsk/imha-dg/asdb_sysaux_raw_1024m undotbs1=/dev/vx/rdsk/imha-dg/asdb_undotbs1_raw_500m undotbs2=/dev/vx/rdsk/imha-dg/asdb_undotbs2_raw_500m temp=/dev/vx/rdsk/imha-dg/asdb_temp_raw_250m example=/dev/vx/rdsk/imha-dg/asdb_example_raw_160m users=/dev/vx/rdsk/imha-dg/asdb_users_raw_120m redo1_1=/dev/vx/rdsk/imha-dg/asdb_redo1_1_raw_120m redo1_2=/dev/vx/rdsk/imha-dg/asdb_redo1_2_raw_120m redo1_3=/dev/vx/rdsk/imha-dg/asdb_redo1_3_raw_120m redo2_1=/dev/vx/rdsk/imha-dg/asdb_redo2_1_raw_120m redo2_2=/dev/vx/rdsk/imha-dg/asdb_redo2_2_raw_120m redo2_3=/dev/vx/rdsk/imha-dg/asdb_redo2_3_raw_120m control1=/dev/vx/rdsk/imha-dg/asdb_control1_raw_110m control2=/dev/vx/rdsk/imha-dg/asdb_control2_raw_110m control3=/dev/vx/rdsk/imha-dg/asdb_control3_raw_110m spfile=/dev/vx/rdsk/imha-dg/asdb_spfile_raw_5m pwdfile=/dev/vx/rdsk/imha-dg/asdb_pwdfile_raw_5m cwmlite=/dev/vx/rdsk/imha-dg/asdb_cwmlite_raw_100m xdb=/dev/vx/rdsk/imha-dg/asdb_xdb_raw_50m odm=/dev/vx/rdsk/imha-dg/asdb_odm_raw_280m indx=/dev/vx/rdsk/imha-dg/asdb_indx_raw_70m tools=/dev/vx/rdsk/imha-dg/asdb_tools_raw_12m drsys=/dev/vx/rdsk/imha-dg/asdb_drsys_raw_250m PORTAL=/dev/vx/rdsk/imha-dg/asdb_portal_raw_128m PORTAL_DOC=/dev/vx/rdsk/imha-dg/asdb_portaldoc_raw_64m PORTAL_IDX=/dev/vx/rdsk/imha-dg/asdb_portalidx_raw_64m PORTAL_LOG=/dev/vx/rdsk/imha-dg/asdb_portallog_raw_64m DCM=/dev/vx/rdsk/imha-dg/asdb_dcm_raw_500m OCATS=/dev/vx/rdsk/imha-dg/asdb_ocats_raw_300m DISCO_PTM5_CACHE=/dev/vx/rdsk/imha-dg/asdb_discoptm5cache_raw_64m DISCO_PTM5_META=/dev/vx/rdsk/imha-dg/asdb_discoptm5meta_raw_64m WCRSYS_TS=/dev/vx/rdsk/imha-dg/asdb_wcrsysts_raw_64m UDDISYS_TS=/dev/vx/rdsk/imha-dg/asdb_uddisysts_raw_64m OLTS_ATTRSTORE=/dev/vx/rdsk/imha-dg/asdb_oltsattrstore_raw_500m OLTS_BATTRSTORE=/dev/vx/rdsk/imha-dg/asdb_oltsbttrstore_raw_500m OLTS_CT_STORE=/dev/vx/rdsk/imha-dg/asdb_oltsctstore_raw_500m OLTS_DEFAULT=/dev/vx/rdsk/imha-dg/asdb_oltsdefault_raw_500m OLTS_SVRMGSTORE=/dev/vx/rdsk/imha-dg/asdb_oltssvrmgstore_raw_256m IAS_META=/dev/vx/rdsk/imha-dg/asdb_iasmeta1_raw_500m DSGATEWAY_TAB=/dev/vx/rdsk/imha-dg/asdb_dsgatewaytab_raw_64m b2b_dt=/dev/vx/rdsk/imha-dg/asdb_b2bdt_raw_256m b2b_rt=/dev/vx/rdsk/imha-dg/asdb_b2brt_raw_256m b2b_idx=/dev/vx/rdsk/imha-dg/asdb_b2bidx_raw_128m b2b_lob=/dev/vx/rdsk/imha-dg/asdb_b2blob_raw_128m osssys=/dev/vx/rdsk/imha-dg/asdb_osssys_raw_800m
Set the DBCA_RAW_CONFIG environment variable to point to the file that you created. For example:
Bourne or Korn shell:
> DBCA_RAW_CONFIG=/fullpath/to/rawconfig/file
> export DBCA_RAW_CONFIG
C shell:
> setenv DBCA_RAW_CONFIG /fullpath/to/rawconfig/file
Install the Oracle9i Release 2 (9.2.0.1) software on local disks. In the installer:
Specify a different Oracle home from the one running the single-instance database.
Select "Database Configuration: Software Only" because you are not creating the database yet.
Apply the Oracle9i Release 2 (9.2.0.6) patch set (patch number 3948480). Perform these steps:
In the README file for the patch set, perform the steps in the section "Before You Install This Patch Set" if they apply to you.
If you are running the Real Application Clusters database in a Sun Clusterware environment, apply the Oracle UNIX Distributed Lock Manager (UDLM) 3.3.4.8 patch. This patch is included in the patch set. The installation instructions are in the Disk1/racpatch/README.udlm file.
Install the 9.2.0.6 patch set.
Perform the steps in the section "Required Post-Installation Tasks" in the README, up to, but not including, the section "Upgrade the Database". You have not created the database yet. You will do this later.
Back up your original single-instance database using DBCA to create a database template from the original database. To perform this step, see:
| Item | Name |
|---|---|
| Book | Oracle9i Real Application Clusters Setup and Configuration
This book is available in the Oracle9i Database documentation set. |
| Chapter | 10, "Converting to Real Application Clusters from Single-Instance Oracle Databases" |
| Section | "Back up the Original Single-Instance Database" |
Select the OFA (Oracle Flexible Architecture) option, because the target machines may not have the same file structure.
DBCA generates two files, template_name.dbc and template_name.dfb, in the SRC_ORACLE_HOME/assistants/dbca/templates directory.
Copy the files generated in the previous step to the RAC_ORACLE_HOME/assistants/dbca/templates directory. RAC_ORACLE_HOME refers to the directory where you installed the database software in step 3.
On the Real Application Clusters node where you installed the database Oracle home (step 3), run Net configuration assistant and perform a typical installation.
> cd RAC_ORACLE_HOME/bin
> netca
Select the "Typical Installation" option, and accept the default values in all the screens.
Start the Global Services Daemon (GSD) on both nodes in the Real Application Clusters database.
> cd RAC_ORACLE_HOME/bin
> gsdctl start
On the Real Application Clusters node where you installed the database Oracle home (step 3), run DBCA on the target node to create a database using the template you created in step 5.
> cd RAC_ORACLE_HOME/bin
> dbca
Notes:
When DBCA displays a list of templates from which you can create a new database, select the template that you created earlier.
Enter a global database name and the SID that are the same as the ones on the single-instance database.
Make sure raw devices and filenames are correct. Check that the paths are full paths and there are no trailing spaces. Make any corrections as necessary.
If you get error "PLS-00302: component 'VALIDATE_COMPONENTS' must be declared", you can ignore this error because you will run rdbms/admin/catpatch.sql later to upgrade the newly created database to 9.2.0.6.
If you get PRKR-1005 or PRKC-1018 errors, you need to stop and restart the GSD daemon on both nodes.
> cd RAC_ORACLE_HOME/bin
> gsdctl stop
> gsdctl start
Upgrade the database to 9.2.0.6 using the downloaded 9.2.0.6 patch set by performing the steps in the section "Upgrade the Database" in the README for the patch set. One of the steps in this section is to run the rdbms/admin/catpatch.sql script.
Apply patch 4015165 to the newly upgraded database.
Unlock all the database accounts listed in IM_ORACLE_HOME/config/unlock.sql. Note that this file is in the Oracle home for the Oracle Identity Management, not in the database Oracle home.
To unlock the accounts without changing the passwords, perform these steps:
Log into the database as the SYS user.
> sqlplus SYS/password as sysdba
Run the following commands for each user listed in the IM_ORACLE_HOME/config/unlock.sql file:
Determine the password for the user.
SQL> select password from dba_users where username = 'username';
Replace username with the name of the account.
Run the "alter user" command.
SQL> alter user username identified by values 'password' account unlock;
Replace username with the name of the account.
Replace password with the password determined from the previous step.
|
Note: Do not change the passwords for these accounts. |
Step 3B: Converting an Oracle Database 10g on UNIX Platforms
This section describes how to convert a single-instance Oracle Database 10g to a Real Application Clusters database that uses OCFS as its storage type.
Perform pre-installation tasks for your platform.
For example, on Linux, you would perform the steps in the following sections in the "Pre-Installation Tasks for RAC on Linux" chapter in the Oracle Real Application Clusters Installation and Configuration Guide.
"Check Hardware Requirements"
"Check Network Requirements"
"Check Software Requirements"
"Create Required UNIX Group and Users"
"Configure Kernel Parameters and Shell Limits"
"Identify Required Software Directories"
"Identity or Create an Oracle Base Directory"
"Create the CRS Home Directory"
"Create Directories for Oracle CRS, Database, or Recovery Files"
"Verify that the Required Software is Running"
This step is required only if you are running on Linux and you intend to use the Oracle Cluster File System. If you are running on other platforms, or if you are using other file management systems (such as raw devices or ASM), you may skip this step.
Install Oracle Cluster File System (OCFS) using the instructions in:
| Item | Name |
|---|---|
| Book | OCFS Userguide
This guide is available here: |
| Section | "Storage with Oracle Cluster File System" |
Overview of installing OCFS:
Install the OCFS software which you downloaded earlier.
Generate the /etc/ocfs.conf file on both nodes of the cluster using ocfstool.
As root user, run load_ocfs to load the OCFS module. You do not need to reboot the nodes if you run this command.
Create partitions and format OCFS mount points.
Install Cluster Ready Services (CRS) using the instructions in:
| Item | Name |
|---|---|
| Book | Oracle Real Application Clusters Installation and Configuration Guide
This book is available in the Oracle Database 10g documentation set. |
| Chapter | 9, "Installing Cluster Ready Services on UNIX" |
Patch CRS to version 10.1.0.4.
Shut down all the database processes from the database Oracle home.
Shut down all crs and ocssd processes.
On UNIX, you have to run the commands as the root user.
> su Password: root_password # /etc/init.d/init.crsd stop To stop the crs process # /etc/init.d/init.cssd stop To stop the css process
On Windows, these are services that you can stop using the Services panel. In the Services panel, you want to stop the OracleCRService and OracleCSService services.
Apply the 10.1.0.4 patch set (patch number 4163362) to the CRS home. See the README file in the patch set for details.
Install the Real Application Clusters database software following the steps in the guide listed below:
| Item | Name |
|---|---|
| Book | Oracle Database 10g Quick Installation Guide for your platform
This book is available in the Oracle Database 10g documentation set. |
| Section | "Install Oracle Database 10g"
Note: In the Select Database Configuration screen, do not create a starter database. You will create the database later. |
Create listeners on the Real Application Clusters nodes.
Make sure all crs and ocssd processes are running.
Start the Net configuration assistant.
> cd RAC_ORACLE_HOME/bin
> netca
In the Net configuration assistant, enter the virtual IPs of the nodes in the cluster.
In the Net configuration assistant, create a listener for each of the two database instances.
Install products from the Companion CD for the Oracle Database 10g. The Companion CD contains two sets of products:
Oracle Database 10g Products
Oracle Database 10g Companion Products
You need to install the first set of products. This includes the Oracle Database examples, natively compiled Java libraries for Oracle JVM and Oracle interMedia, Oracle Text supplied knowledge bases, and Legato Single Server Version.
For installation steps, see:
| Item | Name |
|---|---|
| Book | Oracle Database Companion CD Installation Guide for your platform
This book is available in the Oracle Database 10g documentation set. |
Create the database from template. To perform this step, refer to:
| Item | Name |
|---|---|
| Book | Oracle Real Application Clusters Installation and Configuration Guide
This book is available in the Oracle Database 10g documentation set. |
| Appendix | D, "Converting to Real Application Clusters from Single-Instance Databases" |
Note that the global database name and SID for the Real Application Clusters database must be the same as those of the single-instance database.
Follow the steps in these sections:
"Back up the Original Single-Instance Database"
"Perform the Pre-Installation Steps"
"Copy the Preconfigured Database Image"
"Install Oracle Database 10g Software with Real Application Clusters"
At this time, you would get an error while creating the database because the installer expects catpatch.sql to be run. You can ignore the error and proceed to complete the database creation. You will run catpatch.sql when you apply the patch in the next step.
Patch the Real Application Clusters database software to version 10.1.0.4. This is the same patch set that you downloaded in step 4.
Ensure that the database processes are shut down.
Ensure that the CRS processes (crs and ocssd) are running.
Apply the patch. Follow the steps in the README file for the patch set.
Perform the post-installation steps listed in patchnote.htm.
Typically, you do not have to run the steps for "Resetting the DBMS_SCHEDULER Time Zone". If your system is set to a time zone other than UTC, you would not be able to start dbconsole. It would show you this message:
Timezone mismatch: The agentTZRegion value (UTC) in /scratch/oracleas/radb/host1.mydomain.com_radb/sysman/config/emd.properties does not match the current environment TZ setting(PST8PDT). The dbconsole cannot run with this mismatch. If UTC is the correct timezone, set your timezone environment variable to UTC and repeat the 'emctl start dbconsole' operation. If UTC is not the correct timezone, make sure that the timezone in your environment is correct, and then run the following command in your local Oracle Home: 'emctl resetTZ agent' The output of this command will include detailed instructions to follow, to correct the mismatch.
Follow the steps mentioned and you should be able to start your dbconsole after that.
Unlock all the database accounts listed in IM_ORACLE_HOME/config/unlock.sql. Note that this file is in the Oracle home for the Oracle Identity Management, not in the database Oracle home.
To unlock the accounts without changing the passwords, perform these steps:
Log into the database as the SYS user.
> sqlplus SYS/password as sysdba
Run the following commands for each user listed in the IM_ORACLE_HOME/config/unlock.sql file:
Determine the password for the user.
SQL> select password from dba_users where username = 'username';
Replace username with the name of the account.
Run the "alter user" command.
SQL> alter user username identified by values 'password' account unlock;
Replace username with the name of the account.
Replace password with the password determined from the previous step.
|
Note: Do not change the passwords for these accounts. |
Step 3C: Converting an Oracle 10g Database on Windows
This section describes how to convert a single-instance Oracle 10g Database on Windows to a Real Application Clusters database that uses OCFS as its storage type.
Perform pre-installation tasks for your platform. The tasks are listed in the following guide:
Install Cluster Ready Services (CRS) using the instructions in:
| Item | Name |
|---|---|
| Book | Oracle Real Application Clusters Installation and Configuration Guide
This book is available in the Oracle Database 10g documentation set. |
| Chapter | 10, "Installing Cluster Ready Services on Windows"
Additional things to check:
|
Install the Real Application Clusters database software. You can follow the steps in the guide listed below:
| Item | Name |
|---|---|
| Book | Oracle Real Application Clusters Installation and Configuration Guide
This book is available in the Oracle Database 10g documentation set. |
| Chapter | 11, "Installing Oracle Database 10g with Real Application Clusters"
Notes:
|
Install products from the Companion CD for the Oracle Database 10g. The Companion CD contains two sets of products:
Oracle Database 10g Products
Oracle Database 10g Companion Products
You need to install the first set of products. This includes the Oracle Database examples, natively compiled Java libraries for Oracle JVM and Oracle interMedia, Oracle Text supplied knowledge bases, and Legato Single Server Version.
For installation steps, see:
| Item | Name |
|---|---|
| Book | Oracle Database Companion CD Installation Guide for your platform
This book is available in the Oracle Database 10g documentation set. |
Configure virtual IP for the Real Application Clusters database.
Start up the Virtual IP configuration assistant:
RAC_ORACLE_HOME\bin\vipca.bat
In the Network Interfaces screen, which enables you to select network interfaces from a list, select both private and public interfaces.
On the IP Address screen, enter the virtual IP alias name and press Tab. The Virtual IP configuration assistant should automatically fill in the value for virtual IP address. Verify that the value is correct.
The subnet masks should also be automatically filled in. Change them if they are not correct.
Complete the rest of the screens in the Virtual IP configuration assistant. It should create and start the VIP, GSD, and Oracle Notification Service (ONS) services.
Create listeners on the Real Application Clusters nodes.
Start the Net configuration assistant.
RAC_ORACLE_HOME\bin\netca
Select Cluster Configuration.
Select to configure Both Nodes of the Cluster.
Select Listener Configuration.
Select Add a Listener.
Enter a name for the listener.
Select TCP as the protocol.
Select 1521 as the standard port (unless it is already in use).
Select No when asked to configure another listener.
Create a listener for both nodes in the cluster.
Add "LDAP," to the NAMES.DIRECTORY_PATH line in the RAC_ORACLE_HOME\network\admin\sqlnet.ora file. Do this for both nodes in the cluster. The line should look like the following:
NAMES.DIRECTORY_PATH=(LDAP,TNSNAMES,ONAMES,HOSTNAME)
Patch CRS to version 10.1.0.4.
Make sure that the ORACLE_HOME and ORACLE_SID environment variables are set.
Shut down all the database processes from the database Oracle home.
Shut down all crs and ocssd processes.
On UNIX, you have to run the commands as the root user.
> su Password: root_password # /etc/init.d/init.crsd stop To stop the crs process # /etc/init.d/init.cssd stop To stop the css process
On Windows, these are services that you can stop using the Services panel. In the Services panel, you want to stop the OracleCRService and OracleCSService services.
Apply the 10.1.0.4 patch set (patch number 4163362) to the CRS home. See the README file in the patch set for details.
Check the message window at the end of the installer to see if there are any extra steps that you have to run.
Patch the Real Application Clusters database software to version 10.1.0.4. This is the same patch set that you downloaded in step 8.
Make sure that the ORACLE_HOME and ORACLE_SID environment variables are set.
Ensure that the database processes are shut down.
Ensure that the CRS processes (crs and ocssd) are running.
Apply the patch. Follow the steps in the README file for the patch set.
Check the message window at the end of the installer to see if there are any extra steps that you have to run.
You need not perform the post-installation steps listed in patchnote.htm yet, because you have not created the database yet. You perform these steps after creating the database.
Create the database from template.
Note that the global database name and SID for the Real Application Clusters database must be the same as those of the single-instance database.
Shut down the Oracle Application Server environment:
Shut down the middle tiers.
Shut down the Oracle Identity Management components.
Shut down the OracleAS Metadata Repository database.
Perform the steps in these subsections:
| Item | Name |
|---|---|
| Book | Oracle Real Application Clusters Installation and Configuration Guide
This book is available in the Oracle Database 10g documentation set. |
| Appendix | D, "Converting to Real Application Clusters from Single-Instance Databases" |
| Section | "Back up the Original Single-Instance Database"
This section creates template files in the |
| Section | "Copy the Preconfigured Database Image"
Copy the template files generated in the backup section to the |
Create the database using DBCA:
Check that CRS, the database listener, and all other services related to the cluster are running.
Start up DBCA on one of the nodes in the cluster:
RAC_ORACLE_HOME\bin\dbca
Welcome screen: select Oracle Real Application Clusters Database.
Operations screen: select Create a Database.
Node Selection screen: select both nodes in the cluster.
Database Templates screen: select the templates that you created from the single-instance database.
Database Identification screen: enter the same global database name and SID as for the single-instance database.
Management Options screen: select Configure the Database with Enterprise Manager, and select Use Database Control for Database Management.
Database Credentials screen: create passwords for the administration accounts.
Storage Options screen: select the storage system that you are using.
Database File Locations screen: select Use Common Location for All Database Files, and enter a directory on the shared storage for the data files.
Recovery Configuration screen: select Specify Flash Recovery Area, and enter a directory on the shared storage for the flash recovery files.
Database Content screen: select No Scripts to Run.
Database Services screen: click Next.
Initialization Parameters screen: click the All Initialization Parameters button, and ensure that the cluster_database parameter is set to true.
Database Storage screen: review and set up any database storage parameters that you want for the Real Application Clusters database.
Creation Option screen: select Create Database and click Finish to create the database.
Click OK at the end to start the two instances on both nodes of the cluster.
Perform the post-installation steps listed in patchnote.htm of the 10.1.0.4 patch set. Be sure you run catpatch.sql and utlrp.sql.
Typically, you do not have to run the steps for "Resetting the DBMS_SCHEDULER Time Zone". See step 9 for details.
Unlock all the database accounts listed in IM_ORACLE_HOME\config\unlock.sql. Note that this file is in the Oracle home for the Oracle Identity Management, not in the database Oracle home.
To unlock the accounts without changing the passwords, perform these steps:
Log into the database as the SYS user.
> sqlplus SYS/password as sysdba
Run the following commands for each user listed in the IM_ORACLE_HOME\config\unlock.sql file:
Determine the password for the user.
SQL> select password from dba_users where username = 'username';
Replace username with the name of the account.
Run the "alter user" command.
SQL> alter user username identified by values 'password' account unlock;
Replace username with the name of the account.
Replace password with the password determined from the previous step.
|
Note: Do not change the passwords for these accounts. |
Step 3D: Converting an Oracle9i Database on Windows
This procedure describes how to convert a single-instance Oracle9i database to a Real Application Clusters database that uses raw devices as its storage type.
This configuration installs the Oracle home on a local NTFS drive of each node in the Real Application Clusters and the Oracle raw data files on shared logical partitions.
|
If you are installing on a cluster with three or more nodes: Due to known Oracle Universal Installer issues when installing on clusters with three or more nodes, it is recommended that you install the 2.2.0.18 version of the OUI so that you can perform a cluster installation of the database software.The alternative is to perform individual installations on each node, which would put an installation inventory on each node. If you choose to perform individual installations, you should be aware of the following:
In addition, you may encounter patch issues with some non-Oracle services that may be running on the cluster nodes. Typically the Microsoft Service Distributed Transaction Coordinator (MSDTC) can interact with Oracle software during installation. It is recommended that you stop this service and set it to manual start on all nodes in the cluster (using the Services dialog). After the installation, if you require the MSDTC service, you can restart it and set it to auto start. |
Ensure that you have a certified combination of operating system, Oracle software version, and storage option. You can find the latest certification information on OracleMetaLink (http://metalink.oracle.com).
Note that Microsoft Cluster Software (MSCS) is not required for Real Application Clusters databases because the Oracle Clusterware provides the clustering. However, the Oracle Clusterware can coexist with MSCS as long as the quorum and shared disks are physically separated and mutually exclusive.
Unzip the patches into staging directories. You can then apply the patches from the staging directories. The steps in this procedure assume the following staging directories:
Table 20-5 Staging Directories Used in this Procedure
| Patch | Staging Directory |
|---|---|
|
Oracle9i 9.2.0.6 patch set |
|
|
Windows CFS and Clusterware patch |
|
Subsequent steps in the procedure incorporate the application of these patches with the installation for a new cluster. Review all README instructions before proceeding.
Ensure that the external (public) hostnames are defined in your DNS (directory network services) and that the correct IP addresses resolve for all nodes in the cluster.
Ensure that all external and internal (private) hostnames are defined in the WIN_HOME\System32\drivers\etc\hosts file on all nodes of the cluster. For example, the hosts file for a two-node cluster may look like this:
135.1.136.52 racnode1 135.1.136.53 racnode2 10.10.10.11 racnode1.san 10.10.10.12 racnode2.san
The ".san" depends on whether you are using the default name for the private interconnect or if you modified it.
Note that some vendors also require the setup of the LMHOSTS file. Check your vendor documentation for details.
Test your cluster configuration by pinging all hostnames from each node. Ensure that the hostnames are correctly resolved.
Check that the temporary directories are defined in Windows. Oracle Universal Installer uses the temporary directories.
The TEMP and TMP directories should be the same across all nodes in the cluster. By default, these settings are defined as %USERPROFILE%\Local Settings\Temp and %USERPROFILE%\Local Settings\Tmp in the Environment Settings of My Computer. It is recommended that you redefine these as DRIVE_LETTER:\temp and DRIVE_LETTER:\tmp. For example: C:\temp and C:\tmp for all nodes.
Check access to other nodes in the cluster.
To perform installation and administrative tasks, you should use either the same local administrative username and password on every node in a cluster, or use a domain username with local administrative privileges on all nodes. All nodes must be in the same domain.
Ensure that each node has administrative access to the WIN_HOME, ORACLE_HOME, and temp directories within the Windows environment by running the following command at the command prompt:
> NET USE \\host_name\C$
where host_name is the public network name for the other nodes. If you plan to install the ORACLE_HOME onto another drive location than C, change the administrative share to the appropriate value as well (for example, D$ instead of C$).
For example, if your WIN_HOME is on the C drive and you plan to install the ORACLE_HOME onto the E drive of all nodes, you would run the following from a command prompt on node 1 of a four-node cluster:
> NET USE \\node2\C$ > NET USE \\node3\C$ > NET USE \\node4\C$ > NET USE \\node2\E$ > NET USE \\node3\E$ > NET USE \\node4\E$
Repeat these commands on each node within the cluster. If the privileges are set up correctly, the commands should return with a success message:
The command completed successfully
If you receive errors, resolve them before proceeding.
Run clustercheck.exe to perform a final cluster check.
From a command prompt window, run the clustercheck.exe program located in the staging directory of the unzipped patch 3973928 (that is, under the 3973928\Disk1\preinstall_rac\clustercheck directory). This program performs the following tasks:
It prompts you for the public and private hostnames and requires you to verify the IP address resolution.
It checks the shared disk array, environment variables, and permissions necessary for proper cluster installation and operation.
It creates a subdirectory called opsm in the temporary directory specified by your environment settings (DRIVE_LETTER:\temp if you changed it as specified in step 6).
It creates a log file called OraInfoCoord.log. This log will contain any errors encountered in the check. You should see the following at the end of the log file and within the command prompt window where you ran clustercheck.exe:
ORACLE CLUSTER CHECK WAS SUCCESSFUL
You must correct any errors before proceeding. If you have any issues with clustercheck, see OracleMetaLink Note 186130.1: "Clustercheck.exe Fails with Windows Error 183".
Prepare the logical drives.
Oracle instances in Real Application Clusters write data onto the raw devices to update the control file, server parameter file, each datafile, and each redo log file. All instances in the cluster share these files. In addition, Oracle Application Server components also use the raw devices.
Database Configuration Assistant (DBCA) expects the raw devices to be configured in a specific way. Table 20-6 lists the tablespaces and the expected symbolic link names for the OracleAS Metadata Repository database.
Table 20-6 Filenames Expected by DBCA for Tablespaces
| Tablespace | Filename Expected by DBCA |
|---|---|
|
SYSTEM tablespace |
|
|
USERS tablespace |
|
|
TEMP tablespace |
|
|
UNDOTBS tablespace Thread 1 |
|
|
UNDOTBS tablespace Thread 2 |
|
|
CWMLITE tablespace |
|
|
EXAMPLE tablespace |
|
|
INDX tablespace |
|
|
TOOLS tablespace |
|
|
DRSYS tablespace |
|
|
XML tablespace |
|
|
ODM tablespace |
|
|
First control file |
|
|
Second control file |
|
|
Redo Thread 1 Log 1 |
|
|
Redo Thread 1 Log 2 |
|
|
Redo Thread 2 Log 1 |
|
|
Redo Thread 2 Log 2 |
|
|
spfile |
|
|
srvcfg |
|
Notes:
For the number of redo log files, check the .dbc file created as a part of the template from the source database. If it shows three redo log files, it means that the Real Application Clusters database should have three redo log groups, each with at least two threads.
For the minimum datafile size for each tablespace (for both database and Oracle Application Server tablespaces), check the .dbc file created as a part of the template from the source database.
For the rest of the Oracle Application Server-specific tablespaces, create corresponding raw partitions. You would be prompted to name them once you run the Cluster setup wizard. There is no fixed naming convention for them.
Run the Oracle Cluster setup wizard. You have to run this only on one node and the software will be correctly transferred to the other nodes in the cluster.
Expand the Windows CFS and Clusterware patch (3973928) into a staging directory, such as E:\installs\osd9206. This creates another subdirectory such as E:\installs\osd9206\3973928. This patch contains a full clustersetup release.
Launch the Oracle Cluster Setup Wizard. Within a command prompt window, navigate to the E:\installs\osd9206\3973928\preinstall_rac\clustersetup directory and run clustersetup.
In the Welcome page, click Next.
The first time the Wizard is run, the only option is to create a cluster. Click Next.
Select Use private network for interconnect and click Next.
In the Network Configuration screen, enter the cluster name and the public hostnames for all nodes. The private hostnames will be automatically entered as public_name.san. If you want to provide a different name to the private hostnames, you can modify it. Also make sure that the hosts file has the exact same private hostnames as those mentioned in this Network Configuration screen. If not, you would not be able to start the cluster services. Click Next.
In the Cluster File System Options screen, select No CFS. Click Next.
In the Disk Configuration screen, click the Create Oracle Symbolic Links button.
In the Oracle Object Link Manager window, select an empty row from the Symbolic Link column, and type in the desired datafile link name. Press Enter to save.
Repeat to assign all symbolic link names required (as listed in Table 20-6).
Click the Apply button to commit the changes. When the progress bar at the bottom of the screen stops moving, choose Close.
In the Disk Configuration screen, assign the Voting disk to the logical drive you labeled as srvcfg in the previous step by highlighting the corresponding partition. Click Next.
In the VIA Detection screen, select Yes or No, depending on your Virtual Interface Architecture (VIA) hardware configuration. Contact your cluster hardware vendor if you are unsure. Click Next.
The Install Location screen appears. It defaults to the WIN_HOME\system32\osd9i directory. Accept the default and click Finish.
The Cluster Setup window appears. It shows the progress on installing the cluster files and creating the cluster services on all nodes. If no errors occur, the Oracle Cluster Setup Wizard completes and closes automatically.
If the cluster setup does not run properly, check for errors in the log files under WIN_HOME\system32\osd9i. If any hardware or operating system configuration changes are made, it is recommended that you remove and reinstall the cluster software (deinstallation is not supported). See OracleMetaLink Note 230290.1: "WIN RAC: How to Remove a Failed OCFS Install" for more information on this procedure. It would be the same for raw devices except you will not have an ocfs.sys file for a "No CFS" installation.
Check the clusterware setup. The following services should be running on all nodes in the cluster:
Oracle Object Service
OracleCMService9i
Install the 2.2.0.18 OUI.
Unzip the Oracle Universal Installer 2.2.0.18 (patch number 2878462) into a staging directory such as E:\oui22018.
Within a command prompt window, navigate to E:\oui22018\Disk1\install\win32. Run setup.exe.
In the OUI Welcome screen, click Next.
In the Cluster Node Selection screen, highlight all nodes and click Next. If you are performing individual installations for each node, select the local node only.
|
Note: If at any time in the installation of the software you do not see all nodes in the cluster within the Cluster Node Selection screen, there is something wrong with your cluster configuration and you have to go back and troubleshoot your cluster setup. You can perform clusterware diagnostics by executing:ORACLE_HOME\bin\lsnodes -v Analyze its output, resolve the problem, and then rerun the checks. |
In the File Location screen, ensure the correct source path is being used. In the Destination field, enter the Oracle home for the desired Oracle home for the database, such as C:\oracle\ora92.
In the Installation Types screen, select Minimum installation (2.2.0.18 OUI only) and click Next. (This screen enables you to install both the Software Packager and the OUI 2.2.0.18 or a subset.)
In the Summary screen, check that all nodes are listed and click Next.
The progress screen appears. When the 2.2.0.18 Oracle Universal Installer is installed, click Exit.
If you are performing individual installations, repeat on all nodes.
Install Oracle 9.2.0.1 Database software.
Launch Oracle Universal Installer.
In the Welcome screen, click Next.
In the Node Selection screen, highlight all nodes where the Oracle database software will be installed. Click Next. If you are performing individual installations, select only the local node.
In the File Location screen, in the Destination section, enter the same directory where you installed Oracle Universal Installer 2.2.0.18 in the previous step (step 11(e)). Click Next.
In the Available Products screen, select Oracle9i Database and click Next.
In the Installation Type screen, select Enterprise Edition. The selection on this screen refers to the installation operation, not the database configuration. Click Next.
In the Database Configuration screen, select Software Only. Click Next.
In the Oracle Services for Microsoft Transaction Server screen, enter a port number for this service or leave at default value if you are unsure. Click Next.
In the Summary screen, review the information. Double-check the temporary space available on the drive from which you are installing and then click Install.
If you are performing individual installations, repeat the previous steps for all other nodes in the cluster.
Oracle Universal Installer installs the Oracle9i software on the local node, copies this information to the other selected nodes, and makes the required registry changes on all selected nodes. This can take some time, an hour or more depending on your computers and network environment. During the installation process, the installer does not display all the messages indicating components are being installed on other nodes, so the installation may appear to be hung. In this case, I/O activity may be the only indication that the process is continuing. If necessary, check each node's activity using Task Manager. You can also check the progress by periodically reviewing the Properties on the Oracle home directory in Windows Explorer to see if the size is growing.
Note: There is a known bug with the installer where it fails to find crlogdr.exe or other files when installing from Disk 3. These files are located in Disk 1 under the preinstall_rac subdirectory. See OracleMetaLink Note 211685.1: "Oracle 9.2 Install on Windows Halts With Error: "file not found CRLOGDR.EXE"" for more information.
Patch the database to 9.2.0.6.
The 9.2.0.6 patchset uses the 10g version of Oracle Universal Installer. Therefore you will be installing the 10g Oracle Universal Installer along with the 9.2.0.6 patch.
Navigate to E:\installs\9206\disk1 directory (where you unzipped the 9.2.0.6 patchset) and run setup.exe.
In the Welcome screen, click Next.
In the File Location screen, ensure the correct source path is being used. In the Destination field, enter the desired Oracle home for the database, such as C:\oracle\ora92. Click Next.
In the Cluster Node Selection screen, you should see a list of all the cluster nodes. Click Next. If you previously performed an installation on an individual node, you should see only the local node.
Note: If the Cluster Node Selection screen does not appear, see OracleMetaLink Note 270048.1: "Node Selection Screen Does Not Show The Nodenames Installing 9205 (OUI 10g)" for the workaround.
In the Available Products screen, check all products you want to upgrade to 9.2.0.6 or just accept the default (all already installed products with a lower version than 9.2.0.6 are checked for you). Click Next.
In the Summary screen, click Install.
The progress screen appears. At the end of the installation, click Exit to complete patch installation.
Reboot all nodes in the cluster before proceeding. Ensure all services start on all nodes.
Patch the remaining clusterware.
You will copy all files from the staging clusterware patch directory (E:\installs\osd9206\3973928 in our example). You may want to rename the extension of the files to keep the original version (for example, rename the original copy of the file as filename.orig).
To patch the GSD from E:\installs\osd9206\3973928\srvm\gsd, copy these files into the following directories:
%ORACLE_HOME%\bin\orasrvm.dll %ORACLE_HOME%\bin\gsd.exe %ORACLE_HOME%\bin\gsdservice.exe %ORACLE_HOME%\jlib\srvm.jar
Install the GSD service by running the following command on all nodes:
> ORACLE_HOME\bin\gsdservice -install
To change the service startup, select Start > Settings > Control Panel > Administrative Tools > Services. If OracleGSDService service startup fails, then select OracleGSDService and select Properties from the Action menu and a tabbed Properties page appears. Select the "Log On" tab and select "Log On As" > "This Account". Enter the username and password for an operating system user in the Local Administrators and ORA_DBA groups. Perform this step on each node. See OracleMetaLink Note 213416.1: "RAC: Troubleshooting Windows NT/2000 Service Hangs" for detailed information.
To patch the DBCA utilities from E:\installs\osd9206\3973928\srvm\dbca, copy these files into the following directories:
%ORACLE_HOME%\assistants\jlib\assistantsCommon.jar %ORACLE_HOME%\assistants\dbca\jlib\dbca.jar
To patch the OLM files from E:\installs\osd9206\3973928\Disk1\preinstall_rac\olm, copy the files listed below into both of these directories: %ORACLE_HOME%\bin and %ORACLE_HOME%\olm.
crlogdr.exe DeleteDisk.exe ExportSYMLinks.exe GUIOracleOBJManager.exe ImportSYMLinks.exe LetterDelete.exe LogPartFormat.exe OracleObjManager.exe OracleObjService.exe oraoobjlib.dll readme.txt
Reinstall the Oracle Object Service by running the following commands on all nodes in the cluster:
> OracleOBJService.exe /remove > OracleOBJService.exe /install
Use the Services control panel to start the service, or reboot the nodes.
Increase the priority of the CM Service.
This is an optional step that you can do now or at any time after the installation and configuration are complete. This will not affect the installation process if you choose to configure this at a later date. It is, however, recommended for all production clusters and any Real Application Clusters systems that will be highly loaded.
The CM Service requires a small addition to the registry on all nodes to give the service a higher priority within the Windows. See OracleMetaLink Note 255481.1: "Changing Priority of CMSRVR (OracleCMService9i) on Windows" for the procedure.
After making this registry change, it is important that you restart the CM Service on all nodes to enable this change.
Create cluster listener on each node.
To create listeners on the Real Application Clusters nodes:
Start the Net configuration assistant.
> RAC_ORACLE_HOME\bin\netca
Select Cluster Configuration.
Select to configure Both Nodes of the Cluster.
Select Listener Configuration.
Select Add a Listener.
Enter a name for the listener.
Select TCP as the protocol.
Select 1521 as the standard port (unless it is already in use).
Select No when asked to configure another listener.
Create a listener for both nodes in the cluster.
Back up your original single-instance database using DBCA to create a database template from the original database. To perform this step, see:
| Item | Name |
|---|---|
| Book | Oracle9i Real Application Clusters Setup and Configuration
This book is available in the Oracle9i Database documentation set. |
| Chapter | 10, "Converting to Real Application Clusters from Single-Instance Oracle Databases" |
| Section | "Back up the Original Single-Instance Database" |
Select the OFA (Oracle Flexible Architecture) option, because the target machines may not have the same file structure.
DBCA generates two files, template_name.dbc and template_name.dfb, in the SRC_ORACLE_HOME/assistants/dbca/templates directory.
Copy the files generated in the previous step to the RAC_ORACLE_HOME\assistants\dbca\templates directory. RAC_ORACLE_HOME refers to the directory where you installed the database software in step 12.
Create the Real Application Clusters database using DBCA.
Edit the dbca.bat file as described in OracleMetaLink Note 232239.1: "DBCA Tips and Pitfalls in a Windows RAC Environment" so that it generates a log file. See the section titled "Trace DBCA During Database Creation". This log file provides more complete error information if problems arise.
Run the global services daemon (GSD) in the foreground as described in the same OracleMetaLink note referenced in the previous step (Note 232239.1). See the section "Run the global services daemon (GSD) in the Foreground".
Open a new command prompt window and run DBCA as follows:
> cd %ORACLE_HOME\bin > dbca > C:\dbca_trace.txt
In the Welcome screen, select Cluster Database Option.
In the Operations screen, select Create a Database.
In the Node Selection screen, select both nodes in the cluster.
In the Database Templates screen, select the templates that you created from the single-instance database.
In the Database Identification screen, enter the same global database name and SID as for the single-instance database.
In the Connections option screen, select Dedicated Server.
In the Initialization Parameters screen, click the All Initialization Parameters button, and ensure that the cluster_database parameter is set to true.
The Database storage screen enables you to enter a file name for each tablespace in your database. The screen displays a table with two columns: File Name and File directories. The filenames correspond to the symbolic links created by the Cluster Setup Wizard (step 10i). You may have to modify the filenames to match the Oracle Application Server-specific symbolic names and their directories. Table 20-7 shows an example of how the table should look.
Table 20-7 Example of Filenames and Directories for Tablespaces
| Filename | File Directory |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note that this is just an example. The names and the sizes may be different depending on the names of the Oracle symbolic links (created previously) and the actual sizes of the raw partitions.
Also, on this screen, ensure that you have the correct number of Redo Log groups and corresponding raw partitions.
In the Creation Options screen, select Create database.
In the DBCA summary screen, review the information and click OK.
Notes on creating a database using DBCA:
The database creation can take some time, and the progress may seem slow or hung, especially during the creation of the Java server components and at the end when the database service is created on the remote nodes and the other threads of redo are created. You can check the progress by checking Task Manager and seeing the CPU activity, or by checking the alert log for redo log switching.
DBCA may hang at 95-99%. This is usually due to a problem with creating and enabling the second thread of redo and then bringing the database up in cluster mode. Check the alert logs on both nodes for any errors. If you do not see any errors, open a SQL*Plus session on node 1 and connect as a sysdba user. Select on the v$thread view to see how many threads are open. If there is only one, check the redo logs (v$log, v$logfile) to see if the second thread of redo logs is physically present. If not, run the appropriate scripts manually. Currently, this is the ORACLE_HOME\admin\db_name\scripts\postDBCreation.sql script. You can also check the progress of the run by reviewing the logs in the ORACLE_HOME\admin\db_name\create directory.
If you have issues with any service hangs, see OracleMetaLink Note 213416.1: "RAC: Troubleshooting Windows NT/2000 Service Hangs".
During the database creation process, you may see the following error:
ORA-29807 specified operator does not exist
This is a known issue (bug 2925665). You can click the Ignore button to continue. Once DBCA has completed database creation, run the %ORACLE_HOME%\rdbms\admin\prvtxml.plb script as the SYS user. You should also run the utlrp.sql script to ensure that there are no invalid objects in the database.
Unlock all the database accounts listed in IM_ORACLE_HOME/config/unlock.sql. Note that this file is in the Oracle home for the Oracle Identity Management, not in the database Oracle home.
To unlock the accounts without changing the passwords, perform these steps:
Log into the database as the SYS user.
> sqlplus SYS/password as sysdba
Run the following commands for each user listed in the IM_ORACLE_HOME/config/unlock.sql file:
Determine the password for the user.
SQL> select password from dba_users where username = 'username';
Replace username with the name of the account.
Run the "alter user" command.
SQL> alter user username identified by values 'password' account unlock;
Replace username with the name of the account.
Replace password with the password determined from the previous step.
|
Note: Do not change the passwords for these accounts. |
Step 4 Change the Source Oracle Identity Management to Use the OracleAS Metadata Repository in the Real Application Clusters Database
In this step, you configure the Oracle Identity Management to use the OracleAS Metadata Repository running in the new Real Application Clusters database.
Figure 20-4 Step 4: Change Oracle Identity Management to Use the Real Application Clusters Database
If you installed the Real Application Clusters database on the same nodes as the single-instance database, skip this step and go to step 2.
If you installed the Real Application Clusters database on different nodes from the single-instance database, perform the steps in these sections.
| Item | Name |
|---|---|
| Book | Oracle Application Server Administrator's Guide
This book is available in the Oracle Application Server documentation set. |
| Chapter | 9, "Changing Infrastructure Services" |
| Section | In the section "Changing the Metadata Repository Used by Identity Management", perform the steps in these tasks:
|
Restart Oracle Identity Management and check that you can access Oracle Identity Management components.
Shut down Oracle Identity Management.
> IM_ORACLE_HOME/bin/emctl stop iasconsole > IM_ORACLE_HOME/opmn/bin/opmnctl stopall
Start Oracle Identity Management.
> IM_ORACLE_HOME/opmn/bin/opmnctl startall > IM_ORACLE_HOME/bin/emctl start iasconsole
Some components, such as Log Loader, are not started when you run the "opmnctl startall" command. To check for components that are not started, you can run the following command:
> IM_ORACLE_HOME/opmn/bin/opmnctl status
For the components that are not started, you can start them with the following command:
> IM_ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=component
where component specifies the component that you want to start. For example, to start Log Loader, run this command:
> IM_ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=LogLoader
If a component failed to start because of user error (for example, invalid password), check that the user passwords in Oracle Internet Directory and the database are the same. If they are different, use SQL*Plus to change the password in the database to match the password in Oracle Internet Directory. See these sections in the Oracle Application Server Administrator's Guide for details:
Example: to determine the password for DCM in Oracle Internet Directory, perform these steps:
Start Oracle Directory Manager.
UNIX: run IM_ORACLE_HOME/bin/oidadmin.
Windows: select Start > Programs > Oracle - OracleHomeName > Integrated Management Tools > Oracle Directory Manager.
Connect to Oracle Internet Directory through the load balancer's LDAP virtual server name, and log in as the superuser ("cn=orcladmin").
In Oracle Directory Manager, expand the following:
Entry Management > cn=OracleContext > cn=Products > cn=IAS > cn=Infrastructure Databases > DatabaseName (ASDB) > orclResourceName=DCM
Select orclResourceName=DCM in the left frame, and select the Properties tab in the right frame. Note the password in the orclpasswordattribute field.
If you installed the Real Application Clusters database on different nodes from the single-instance database, you can skip this step and go to step 4. You can skip this step because you have already done it in step 1.
If you installed the Real Application Clusters database on the same nodes as the single-instance database, you need to perform this step.
Make Oracle Identity Management Real Application Clusters-aware.
Shut down Oracle Identity Management.
> IM_ORACLE_HOME/bin/emctl stop iasconsole > IM_ORACLE_HOME/opmn/bin/opmnctl stopall
Update IM_ORACLE_HOME/network/admin/tnsnames.ora to add all the nodes in the Real Application Clusters in the file.
For example, if your original tnsnames.ora file looks like this:
ASDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL=TCP)(HOST=clusternode1.mydomain.com)(PORT=1521))
)
(CONNECT_DATA =
(SERVICE_NAME = asdb.mydomain.com)
)
)
You would add the "clusternode2" line to the file:
ASDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL=TCP)(HOST=clusternode1.mydomain.com)(PORT=1521))
(ADDRESS = (PROTOCOL=TCP)(HOST=clusternode2.mydomain.com)(PORT=1521))
)
(CONNECT_DATA =
(SERVICE_NAME = asdb.mydomain.com)
)
)
Start Oracle Identity Management.
> IM_ORACLE_HOME/opmn/bin/opmnctl startall > IM_ORACLE_HOME/bin/emctl start iasconsole
Test the Oracle Identity Management components.
Test OracleAS Single Sign-On by accessing its URL: http://node2.mydomain.com:7777/pls/orasso.
node2.mydomain.com:7777 refers to the physical hostname of the machine running OracleAS Single Sign-On. In Figure 20-4, this is Node 2.
Validate that everything is working.
Test Oracle Delegated Administration Services by accessing its URL: http://node2.mydomain.com:7777/oiddas.
node2.mydomain.com:7777 refers to the physical hostname of the machine running Oracle Delegated Administration Services. In Figure 20-4, this is Node 2.
Validate that everything is working.
|
Downtime 1 Ends: This ends the first downtime. At this point, the OracleAS Metadata Repository now runs on a Real Application Clusters database, and Oracle Identity Management components are using that database. |
Step 5 Transform the Source Oracle Identity Management to Use the Virtual Server Names Configured on the Load Balancer
In this step, you transform the source Oracle Identity Management to use the virtual server names configured on the load balancer.
This step has two subsections. Follow the steps according to the transformation you want to perform:
If you are transforming to an OracleAS Cluster (Identity Management), perform the steps in "Step 5A: OracleAS Cluster (Identity Management) Case".
If you are transforming to a distributed OracleAS Cluster (Identity Management), where Oracle Internet Directory / Oracle Directory Integration and Provisioning run on one Oracle home, and OracleAS Single Sign-On / Oracle Delegated Administration Services run on another Oracle home, perform the steps in "Step 5B: Distributed OracleAS Cluster (Identity Management) Case".
Step 5A: OracleAS Cluster (Identity Management) Case
Perform these steps if you are transforming to an OracleAS Cluster (Identity Management). After this step, your environment should look like this:
Figure 20-5 Step 5 (OracleAS Cluster (Identity Management) Case): Configuring the Source Oracle Identity Management to Use the Virtual Server Name on the Load Balancer
|
Downtime 2 Starts: The next step starts the second downtime. |
Set up the load balancer.
Perform the steps in the following section:
| Item | Name |
|---|---|
| Book | Oracle Application Server Installation Guide
This book is available on Disk 1 of the Oracle Application Server distribution. |
| Chapter | "Installing in High Availability Environments: OracleAS Cluster (Identity Management)" |
| Section | "Pre-Installation Steps for OracleAS Cluster (Identity Management)" |
Configure a virtual server name on the load balancer for LDAP connections. For this virtual server, you need to configure two ports: one for SSL and one for non-SSL connections.
|
Note: These are the same ports that Oracle Internet Directory is using on the original node. Ensure that these ports are available on the nodes on which you will be installing additional instances of Oracle Internet Directory (you perform the additional installations in step 8: "Install Additional Oracle Identity Management Instances"). |
Configure a virtual server name on the load balancer for HTTP connections. For this virtual server, you need to configure two ports: one for SSL and one for non-SSL.
Configure the virtual server to direct requests only to the original node initially. After you install Oracle Identity Management on the second node, then you can add that node to the virtual server.
Make the following changes to Oracle Internet Directory.
Reload OPMN configuration.
> IM_ORACLE_HOME/opmn/bin/opmnctl reload
Start Oracle Internet Directory.
> IM_ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID
Check that Oracle Internet Directory is up and running.
> IM_ORACLE_HOME/bin/ldapbind -p oid_nonssl_port > IM_ORACLE_HOME/bin/ldapbind -p oid_ssl_port -U 1
These command should return a "bind successful" message.
Configure Oracle Internet Directory to use the load balancer's virtual server name.
Shut down Oracle Identity Management components.
> IM_ORACLE_HOME/opmn/bin/opmnctl stopall
Update the following lines in the IM_ORACLE_HOME/config/ias.properties file to use the virtual server name and port.
OIDhost=virtual_server_name OIDport=virtual_server_port
Start Oracle Identity Management components.
> IM_ORACLE_HOME/opmn/bin/opmnctl startall
Check that Oracle Internet Directory is up and running.
> IM_ORACLE_HOME/bin/ldapbind -p oid_nonssl_port > IM_ORACLE_HOME/bin/ldapbind -p oid_ssl_port -U 1
These commands should return a "bind successful" message.
Configure OracleAS Single Sign-On to use the virtual server name for Oracle Internet Directory.
Check that the LD_LIBRARY_PATH (or equivalent) environment variable includes the IM_ORACLE_HOME/lib directory. The environment variable that you need to set depends on your platform. See the following section for details:
| Item | Name |
|---|---|
| Book | Oracle Application Server Administrator's Guide
This guide is available in the Oracle Application Server documentation set. |
| Chapter | 1, "Getting Started After Installing Oracle Application Server" |
| Section | 1.1, "Task 1: Set Up Environment Variables" |
Update OracleAS Single Sign-On (enter the following command on one line).
> IM_ORACLE_HOME/jdk/bin/java -jar IM_ORACLE_HOME/sso/lib/ossoca.jar reassoc -repos IM_ORACLE_HOME
Make the following changes for OracleAS Single Sign-On.
Update the following lines in the IM_ORACLE_HOME/Apache/Apache/conf/httpd.conf file to use the virtual server name and port.
ServerName virtual_server_name Port virtual_server_port
For example:
ServerName sso.mydomain.com Port 7777
Run the following command to update the information in DCM.
> IM_ORACLE_HOME/dcm/bin/dcmctl updateConfig -v -d
Configure OracleAS Single Sign-On to accept authentication from the externally published address of the OracleAS Single Sign-On server. This configuration updates the information in the OracleAS Metadata Repository.
> IM_ORACLE_HOME/sso/bin/ssocfg.sh protocol virtual_server_name virtual_server_port
For example:
> IM_ORACLE_HOME/sso/bin/ssocfg.sh http sso.mydomain.com 7777
Re-register mod_osso to use the virtual server name and port (enter the following command on one line).
> IM_ORACLE_HOME/sso/bin/ssoreg.sh -oracle_home_path im_oracle_home_path -site_name virtual_server_name -config_mod_osso TRUE -mod_osso_url http://virtual_server_name:port
For example:
> IM_ORACLE_HOME/sso/bin/ssoreg.sh -oracle_home_path im_oracle_home_path -site_name sso.mydomain.com -config_mod_osso TRUE -mod_osso_url http://sso.mydomain.com:7777
For Oracle Delegated Administration Services, change the URL for Oracle Delegated Administration Services to use the virtual server name and port.
Start Oracle Directory Manager.
Connect to Oracle Internet Directory using the virtual server name and port. Log in as the superuser: cn=orcladmin.
Expand the following entries: Entry Management > cn=OracleContext > cn=Products > cn=DAS > cn=OperationalURLs.
Change the orcldasurlbase attribute to http://virtual_server_name:port. For example: http://sso.mydomain.com:7777.
Stop and restart the Oracle Identity Management and middle-tier components, and test that the components are working.
Stop Oracle Identity Management.
> IM_ORACLE_HOME/opmn/bin/opmnctl stopall > IM_ORACLE_HOME/bin/emctl stop iasconsole
Start Oracle Identity Management.
> IM_ORACLE_HOME/opmn/bin/opmnctl startall > IM_ORACLE_HOME/bin/emctl start iasconsole
Test Oracle Identity Management components.
Test Oracle Delegated Administration Services by accessing its URL, http://virtual_server_name:port/oiddas, and try to perform some operations. Example: http://sso.mydomain.com:7777/oiddas.
Test OracleAS Single Sign-On by accessing its URL, http://virtual_server_name:port/pls/orasso, and try to perform some operations. Example: http://sso.mydomain.com:7777/pls/orasso.
Test middle-tier components. For example, to test OracleAS Portal, access its URL, http://portalhost.mydomain.com:7777/pls/portal, and try to perform some operations.
Create a Distributed Configuration Management cluster and make the Oracle Identity Management instance a member of the cluster.
> IM_ORACLE_HOME/dcm/bin/dcmctl createcluster clustername > IM_ORACLE_HOME/dcm/bin/dcmctl joincluster clustername > IM_ORACLE_HOME/dcm/bin/dcmctl listcomponents
Stop and restart the Oracle Identity Management components, and test that the components are working. Make sure that the OC4J_SECURITY component is restarted. See step 5 for details.
Step 5B: Distributed OracleAS Cluster (Identity Management) Case
After this step, your environment should look like this:
Figure 20-6 Step 5 (Distributed OracleAS Cluster (Identity Management) Case): Configuring the Source Oracle Identity Management to Use the Virtual Server Name on the Load Balancer
Set up the load balancer.
Perform the pre-installation steps in the following section:
| Item | Name |
|---|---|
| Book | Oracle Application Server Installation Guide
This book is available on Disk 1 of the Oracle Application Server distribution. |
| Chapter | "Installing in High Availability Environments: OracleAS Cluster (Identity Management)" |
| Section | "Pre-Installation Steps for OracleAS Cluster (Identity Management)" |
Configure a virtual server name on the load balancer for LDAP connections. For this virtual server, you need to configure two ports: one for SSL and one for non-SSL connections.
|
Note: These are the same ports that Oracle Internet Directory is using on the original node. Ensure that these ports are available on the nodes on which you will be installing additional instances of Oracle Internet Directory (you perform the additional installations in step 8: "Install Additional Oracle Identity Management Instances"). |
Configure a virtual server name on the load balancer for HTTP connections. For this virtual server, you need to configure two ports: one for SSL and one for non-SSL.
Configure the virtual server to direct requests only to the original node initially. After you install Oracle Identity Management on the second node, then you can add that node to the virtual server.
|
Downtime 2 Starts: The next step starts the second downtime. |
Disable OracleAS Single Sign-On and Oracle Delegated Administration Services on the first Oracle Identity Management node.
Start up Application Server Control Console.
Display the home page for the Oracle Identity Management instance.
Select the checkbox for OC4J_SECURITY and click Enable/Disable Components. This displays the Enable/Disable Components page.
On the Enable/Disable Components page, select both OC4J_SECURITY and HTTP_Server, Single Sign-On:orasso in the Enabled Components box and click Move All to move them to the Disabled Components box. There should be three items in the Disabled Components box:
home
OC4J_SECURITY
HTTP_Server, Single Sign-On:orasso
Click OK.
On the Warning page, which warns you that the components to be disabled will be stopped, click Yes. This stops the components and disables them as well.
When you return to the instance home page, you should see only two components: Internet Directory and Management.
Stop all the Oracle Identity Management components except for Oracle Internet Directory. One way of doing this is to stop all components, then start up Oracle Internet Directory.
Stop Oracle Identity Management components.
> IM_ORACLE_HOME/opmn/bin/opmnctl stopall
Start the OPMN daemon.
> IM_ORACLE_HOME/opmn/bin/opmnctl start
Start Oracle Internet Directory.
> IM_ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OID
Check that Oracle Internet Directory is up and running.
> IM_ORACLE_HOME/bin/ldapbind -p oid_nonssl_port > IM_ORACLE_HOME/bin/ldapbind -p oid_ssl_port -U 1
These commands should return a "bind successful" message.
Make the following changes to Oracle Internet Directory.
Reload the OPMN configuration.
> IM_ORACLE_HOME/opmn/bin/opmnctl reload
IM_ORACLE_HOME refers to the original Oracle home for Oracle Identity Management.
Configure Oracle Internet Directory to use the load balancer's virtual server name.
Shut down Oracle Identity Management components.
> IM_ORACLE_HOME/opmn/bin/opmnctl stopall
Update the following lines in the IM_ORACLE_HOME/config/ias.properties file to use the virtual server name and port.
OIDhost=virtual_server_name OIDport=virtual_server_port
Start Oracle Identity Management components.
> IM_ORACLE_HOME/opmn/bin/opmnctl startall
Check that Oracle Internet Directory is up and running.
> IM_ORACLE_HOME/bin/ldapbind -p oid_nonssl_port > IM_ORACLE_HOME/bin/ldapbind -p oid_ssl_port -U 1
These commands should return a "bind successful" message.
Create a Distributed Configuration Management cluster and make the Oracle Identity Management instance a member of the cluster.
> IM_ORACLE_HOME/dcm/bin/dcmctl createcluster clustername > IM_ORACLE_HOME/dcm/bin/dcmctl joincluster clustername > IM_ORACLE_HOME/dcm/bin/dcmctl listcomponents
Step 6 (Distributed OracleAS Cluster (Identity Management) Case Only) Install OracleAS Single Sign-On and Oracle Delegated Administration Services
This step applies only if you are transforming to a distributed OracleAS Cluster (Identity Management). If you are transforming to an OracleAS Cluster (Identity Management), skip this step.
After this step, your configuration should look like this (Figure 20-7):
Figure 20-7 Step 6: Installing New Instance for OracleAS Single Sign-On and Oracle Delegated Administration Services
For distributed OracleAS Cluster (Identity Management), you need to install OracleAS Single Sign-On and Oracle Delegated Administration Services in a new Oracle home.
Make the following selections in the installer:
In the Select a Product to Install screen, select Oracle Application Server Infrastructure.
In the Select Installation Type screen, select Identity Management.
In the Select Configuration Options screen, select OracleAS Single Sign-On, Oracle Delegated Administration Services, and High Availability and Replication.
In the Select High Availability Option screen, select OracleAS Cluster (Identity Management).
In the Create or Join an Oracle Application Server Cluster (Identity Management) screen, select Create a New Oracle Application Server Cluster.
In the Specify New Oracle Application Server Cluster Name screen, enter a new name for the cluster.
In the Specify LDAP Virtual Host and Ports screen, enter the virtual hostname configured on the load balancer for LDAP traffic (that is, for Oracle Internet Directory). For the port number, enter the port number associated with the virtual hostname.
In the Specify HTTP Listen Port, Load Balancer Host and Port screen:
In the HTTP Listener Port field, enter the port number that you want to use for Oracle HTTP Server.
In the HTTP Load Balancer Hostname and Port fields, enter the HTTP virtual hostname configured on the load balancer and the port number configured for the virtual hostname.
Step 7 Change the Middle Tier to Use the Virtual Server Names on the Load Balancer
You need to reconfigure the middle tiers to use the load balancer's virtual server names when accessing Oracle Identity Management components.
After this step, your environment should look like either Figure 20-8 or Figure 20-9 (for the distributed case).
Figure 20-8 Step 7 (OracleAS Cluster (Identity Management) Case): Configure the Middle Tiers to Use Virtual Server Names Configured on the Load Balancer
Figure 20-9 Step 7 (Distributed Case): Configure the Middle Tiers to Use Virtual Server Names Configured on the Load Balancer
Shut down the middle tiers. If your middle tiers use their own OracleAS Metadata Repository, shut it down too.
> MT_ORACLE_HOME/opmn/bin/opmnctl stopall > MT_ORACLE_HOME/bin/emctl stop iasconsole
Change the Oracle Internet Directory configuration in the middle tier's Oracle home to use the virtual server name and port. You can do this by updating these lines in the MT_ORACLE_HOME/config/ias.properties file.
OIDhost=virtual_server_name OIDport=virtual_server_port
If your middle tier uses a different OracleAS Metadata Repository, make the same updates in the OracleAS Metadata Repository's Oracle home.
Start the middle tier.
If the middle tier uses a different OracleAS Metadata Repository from Oracle Identity Management, start this OracleAS Metadata Repository.
Start the middle tier instance.
> MT_ORACLE_HOME/opmn/bin/opmnctl startall > MT_ORACLE_HOME/bin/emctl start iasconsole
Configure the middle tier to use the reconfigured Oracle Identity Management. You can do this by following the steps in this section:
| Item | Name |
|---|---|
| Book | Oracle Application Server Administrator's Guide
This book is available in the Oracle Application Server documentation set. |
| Chapter | 9, "Changing Infrastructure Services" |
| Section | "Moving Identity Management to a New Host" |
| Task | Task 3: "Change Middle-Tier Instances to the New Identity Management" |
Repeat this procedure for each middle tier.
|
Downtime 2 Ends: This ends the second downtime. |
Step 8 Install Additional Oracle Identity Management Instances
You need additional instances to create multiple active instances in the OracleAS Cluster (Identity Management). After this step, you should have a highly available environment shown in either Figure 20-10 or Figure 20-11 (distributed case).
Figure 20-10 Step 8 (OracleAS Cluster (Identity Management) Case): Install Additional Instances
Figure 20-11 Step 8 (Distributed Case): Install Additional Instances
On the first Oracle Identity Management instance, make sure Oracle Internet Directory is running.
Make sure the OracleAS Metadata Repository and listener are running.
Make sure that the load balancer is configured to direct traffic only to the first Oracle Identity Management instance.
Create a staticports.ini file that contains the ports used by the first Oracle Identity Management instance.
Install instances in OracleAS Cluster (Identity Management). You can use the steps in the following chapter:
| Item | Name |
|---|---|
| Book | Oracle Application Server Installation Guide
This book is available on Disk 1 of the Oracle Application Server distribution. |
| Chapter | "Installing in High Availability Environments: OracleAS Cluster (Identity Management)" |
| Section | "Installing OracleAS Cluster (Identity Management) on Subsequent Nodes"
Notes:
|
Reconfigure the load balancer to route requests to the new instance.
If you install additional instances, you configure the load balancer to point to the instance after installing the instance.
Step 9 Verify That All the Components Are Working
Verify that the Oracle Identity Management and middle-tier components are working.
Test Oracle Identity Management components.
Test Oracle Delegated Administration Services by accessing its URL, http://virtual_server_name:port/oiddas, and try to perform some operations. Example: http://sso.mydomain.com:7777/oiddas.
Test OracleAS Single Sign-On by accessing its URL, http://virtual_server_name:port/pls/orasso, and try to perform some operations. Example: http://sso.mydomain.com:7777/pls/orasso.
Test middle-tier components. For example, to test OracleAS Portal, access its URL, http://portalhost.mydomain.com:7777/pls/portal, and try to perform some operations.
Step 10 Decommission the Oracle Homes That Are No Longer Used
At the end of the transformation procedure, you no longer need the source Oracle home for the OracleAS Metadata Repository database. If you are not using this Oracle home for other purposes (that is, if you were using this Oracle home only for the OracleAS Metadata Repository database), then you can deinstall it. See the "Removing Oracle Software" chapter in the Oracle Database Installation Guide for details.
