Using Oracle EBS with a Split Configuration Database Tier on 11gR2 [ID 946413.1]

Using Oracle EBS with a Split Configuration Database Tier on 11gR2 [ID 946413.1]
		Modified 31-AUG-2011 Type WHITE PAPER Status PUBLISHED

View Change log Using Oracle E-Business Suite with a Split Configuration Database Tier on Oracle 11g Release 2 August 2011 This document describes how to use Oracle E-Business Suite Release 11i with a split configuration database tier on Oracle Release 11g (11.2.0.x). Attention This procedure currently applies to the Linux x86-64, Oracle Solaris x86-64, HP Itanium, and Windows x64 operating systems only. The most current version of this document is Note 946413.1 on My Oracle Support. There is a change log at the end of this document. Section 1: Introduction Oracle E-Business Suite architecture and migration overview Section 2: Prerequisites Tasks to perform before migrating the Oracle E-Business Suite database Section 3: Migration Procedure Steps to migrate the database Section 4: Post-migration Tasks Tasks to complete the migration process Section 5: Validation Tasks Tasks to validate proper configuration of the split configuration system Conventions Convention Meaning Application Tier Machines running Forms, Web, and other servers. Also called middle tier. Database Tier Machines running Oracle E-Business Suite database. APPLMGR User who owns the E-Business Suite file system (APPL_TOP and application tier technology stack). ORACLE User who owns the database file system (Database ORACLE_HOME and files). CONTEXT_NAME The CONTEXT_NAME variable specifies the name of the Applications context that is used by AutoConfig. The default is [SID]_[hostname]. For systems installed with Rapid Install 11.5.8 or earlier, the context name will typically be [SID]. CONTEXT_FILE The default location for the application tier context file is: [APPL_TOP]/admin/[CONTEXT_NAME].xml APPSpwd Oracle E-Business Suite database user password. Monospace Text Represents command line text. Type this command exactly as shown. [ ] Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do not type the angle brackets. \ The backslash character is entered at the end of a command line to indicate continuation of the command on the next line. (Unix) Section 1: Introduction Oracle E-Business Suite is made up of a three-tier architecture, where a tier is a logical grouping of services that may be distributed across one or more physical machines. Note Refer to Oracle Applications Concepts for a complete description of the Oracle E-Business Suite architecture and definition of terms. An Oracle E-Business Suite Release 11i deployment where the platform used for the application tier is different from the platform used for the database tier is an example of a mixed platform, or split configuration, architecture. This enables use of database platforms that do not support the application tier components of Oracle E-Business Suite. The steps in the following sections guide you through the process of migrating an Oracle E-Business Suite database from the source platform to the target split configuration database tier platform. Section 2: Prerequisites This section describes the requirements for Oracle E-Business Suite releases, software component versions, and patch installation that must be met before the database is migrated to 11.2.0.1 or later on the split configuration database tier platform. Make any necessary software version upgrades Software Minimum Version Location Details Oracle E-Business Suite Release 11.5.10 CU2 Database tier and application tier Your system must be Release 11.5.10.2. AutoConfig Latest version with 10202042 (for Windows 2008) Database tier and application tier Implement AutoConfig or upgrade to the latest version. SeeUsing AutoConfig to Manage System Configurations with Oracle Applications 11i (My Oracle Support Note 165195.1). If you are on Windows 2008, apply patch patch 10202042 Database 11.2.0.1 Database tier The original (source) database must be 11.2.0.1 or higher. See My Oracle Support Note 881505.1, Interoperability Notes: Oracle E-Business Suite Release 11i with Oracle 11g Release 2 (11.2.0) to upgrade the database to 11.2.0.x. See My Oracle Support for more information on certified database versions for your operating system. Create the RDBMS ORACLE_HOME on the target machine Install Oracle 11g Database Release 11.2.0.1 or later on the target machine. Perform all steps in the Database Installation subsection of Section 1 in My Oracle Support Note 881505.1, Interoperability Notes: Oracle E-Business Suite Release 11i with Oracle 11g Release 2 (11.2.0). Attention A full backup of the Oracle E-Business Suite system should be taken before carrying out the migration to the target machine, over and above normal backup procedures. Section 3: Migration Procedure Perform the steps below to migrate the E-Business Suite database from the original platform to the target platform. Note The Oracle E-Business Suite system will be unavailable during the migration process. Shut down the application tier services Log on to each machine in the application tier and stop the Oracle E-Business Suite services. $ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME] $ adstpall.sh apps/[APPSpwd] De-register the original database server machine De-register the original database server machine from the AutoConfig repository in the Applications database. As the ORACLE user, log on to the machine with the existing database and run the following commands: $ cd [RDBMS ORACLE_HOME]/appsutil/bin $ perl adgentns.pl appspass=[APPSpwd] \ contextfile=[CONTEXT_FILE] -removeserver Export OLAP analytical workspaces (conditional) Note All customers who are migrating from a 32-bit platform to a 64-bit platform (specifically corresponding to steps 6a and 6b below) must migrate OLAP analytical workspaces by performing this step. Perform the detailed steps 1-4 as documented in My Oracle Support Note 352306.1, Upgrading OLAP from 32 to 64 bits, to export OLAP analytical workspaces on the source machine. Copy the export files to the target machine. Create a .trc file to use as template to re-create the control files on the target machine Run the following command on the source database to create a .trc file, which you will use to recreate the control files on the target machine in a later step. $ sqlplus /nolog SQL> connect / as sysdba SQL> alter database backup controlfile to trace Shut down the original (source) database Perform a SHUTDOWN NORMAL on the source database, and stop the database listener. (Option A) Migrate Linux 32-bit database to Linux x86-64 Perform the following steps to move the Linux 32-bit database to Linux x86-64: Copy the database (.dbf) files from the source machine to the target machine Copy the database configuration files (including init.ora) Modify the configuration files as specified in the database documentation. This includes setting _system_trig_enabled=false Start up the database Recreate the database control files Migrate the database from 32-bit to 64-bit (recompile pl/sql modules and change the word size) by running utlirp.sql and utlrp.sql (in ORACLE_HOME/rdbms/admin/). Refer to the usage and notes sections in each of these scripts for instructions on how to run them. Remove _system_trig_enabled=false from init.ora Shutdown and restart the database normally (Option B) Migrate Windows 32-bit database to Windows x64 Perform the following steps to move the Windows 32-bit database to Windows x64: Copy the database (.dbf) files from the source machine to the target machine Copy the database configuration files (including init.ora) Modify the configuration files as specified in the database documentation. This includes setting _system_trig_enabled=false Start up the database Recreate the database control files Migrate the database from 32-bit to 64-bit (recompile pl/sql modules and change the word size) by running utlirp.sql and utlrp.sql (in ORACLE_HOME/rdbms/admin/). Refer to the usage and notes sections in each of these scripts for instructions on how to run them. Remove _system_trig_enabled=false from init.ora Shutdown and restart the database normally (Option C) Migrate HP PA-RISC database to HP Itanium Follow these steps to migrate the database from HP PA-RISC to HP Itanium: Copy the database (.dbf) files from the source machine to the target machine Copy the database configuration files (including init.ora) If the directories where the source and target database files reside are the same, copy the database control files. Otherwise, recreate the database control files. (Option D) Migrate database on other platforms to Linux x86-64, Solaris x86-64, HP Itanium, or Windows x64 In the case where the source database operating system and architecture is different from that of the target operating system, the source database must be exported and then imported into the newly created target database. For this scenario, follow the procedure described in My Oracle Support Note 557738.1, Export/Import Process for Oracle E-Business Suite Release 11i Database Instances Using Oracle Database 11g Release 1 or 2, to migrate the database. Note Omit the step (in Note 557738.1) of creating the 11g RDBMS Oracle home on the target machine. This step was performed as part of the Prerequisite section of this document, before the system downtime. Import OLAP analytical workspaces (Conditional) If you exported OLAP analytical workspaces, perform detailed steps 7-8 as documented in My Oracle Support Note 352306.1 to import OLAP analytical workspaces that were previously exported from the source machine. Re-create Java system (Conditional) If you have performed a full database migration with step 6a or 6b above, re-create the Java system by using SQL*Plus to connect to the database as SYSDBA and running the following command: SQL> connect / as sysdba; SQL> create or replace java system; Section 4: Post-Migration Tasks If you performed Option A, B, or C in step 5 of Section 3, perform these additional interoperability steps on the new database. Natively recompile PL/SQL code (optional) If you are on a UNIX/Linux platform, you can choose to run Oracle E-Business Suite 11i PL/SQL database objects in natively compiled mode with Oracle Database 11g. See the "Compiling PL/SQL Program Units for Native Execution" section of Chapter 12 of Oracle Database PL/SQL Language Reference 11g Release 2 (11.2). When modifying the initialization parameters pertaining to the PL/SQL native compilation, usedocument 216205.1, on My Oracle Support as a guideline. Start the new database listener If the Oracle Net listener for the database instance in the new Oracle home has not already been started, you must start it now. Since AutoConfig has not yet been implemented, start the listener with the lsnrctl executable (UNIX/Linux) or the Services applet (Windows). See the Oracle Database Net Services Administrator's Guide 11g Release 2 (11.2) for more information. Implement and run AutoConfig on the database server node Implement and run AutoConfig in the new Oracle home on the database server node. If the database listener of the new Oracle home is defined differently than the old Oracle home, you must also run AutoConfig on each application tier server node to update the system with the new listener. See Using AutoConfig to Manage System Configurations with Oracle Applications 11i on My Oracle Support for instructions on how to implement and run AutoConfig. Shut down all processes, including the database and the listener, and restart them to load the new environment settings. Re-create custom database links If the Oracle Net listener in the 11.2.0 Oracle home is defined differently than the one used by the old Oracle home, you must re-create any custom self-referential database links that exist in the Applications database instance. To check for the existence of database links, use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following query: $ sqlplus apps/[apps password] SQL> select db_link from dba_db_links; The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist, should have been updated with the new port number by AutoConfig in a previous step. If you have custom self-referential database links in the database instance, use the following commands to drop and recreate them: $ sqlplus apps/[apps password] SQL> drop database link [custom database link]; SQL> create database link [custom database link] connect to [user] identified by [password] using '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=[hostname]) (PORT=[portnumber]))(CONNECT_DATA=(SID=[ORACLE_SID])))'; where [custom database link], [user], [password],[hostname], and [ORACLE_SID] are all as they were in the source database link definition, and [port number] is the port number of the new Oracle Net listener for the database instance. Reconfigure the application tier to connect to the target database machine Log on to each application tier machine and perform the following steps: Update the application tier context file Update the following variables in the Applications context file to match the target database configuration: Variable Name Value s_dbhost New database hostname s_dbdomain New database domain name s_dbport New database listener port. s_apps_jdbc_connect_descriptor NULL s_isDB NO Run AutoConfig on the application tier Make sure that the new database and listener are running, and run AutoConfig on the application tier: $ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME] $ adautocfg.sh Start all application tier services Restart all services on the application tier. $ adstrtal.sh apps/[APPSpwd] Recreate Concurrent Manager Service (Windows only) (conditional) If the database resided locally before migration, the Concurrent Manager Service has been configured with a dependency on the local Oracle service. Since the Oracle database is now on a separate tier, this dependency should be removed using: $ cd %COMMON_TOP%\admin\install\[Context_Hostname] $ adsvcm.cmd -deinstall After executing the commands, make sure the service has been removed on the service panel. Users should then re-create the Concurrent Manager Service with: $ adsvcm.cmd [APPS user]/[APPS password] After executing the commands, make sure the service has been added on the service panel and does not include the dependency on the local Oracle service. Section 5: Validation Tasks Verify that the application tier is configured to use the new 11g database: Verify the database server hostname and database release version Go to the Oracle E-Business Suite Rapid Install Portal, and log on to the E-Business Suite home page as the sysadmin user. Select a responsibility (such as the System Administrator responsibility). Click on any form, such as the Concurrent->Requests form. From the Help menu click "About Oracle Applications", and verify that the server hostname and release version correspond to those of the target database. Run Diagnostics for HTML-based Applications (Self-service) Return to the E-Business Suite home page and select the System Administration responsibility. Click on each link in the Diagnostics section. Run CRM Diagnostics Return to the E-Business Suite home page and select the CRM HTML Administrator responsibility. Click on Diagnostics, and select the Basic tab. Click on Run All Groups, and examine the test results.

Change Log
Date	Description
October 7, 2009	First creation
April 26, 2010	Added instructions for Solaris x86-64 Modified references from MetaLink to My Oracle Support
May 25, 2010	Added instructions for Windows x64
July 19, 2010	Added instructions for HP Itanium
November 15, 2010	Added instructions to re-create java system Split up the migration of OLAP into 2 separate steps
December 3, 2010	Added patch 10202042 for Windows 2008 OS
August 30, 2011	Fixed Section 3 Step 8 to refer to 6a and 6b

Note 946413.1 by Oracle Applications Development
Copyright 2009 Oracle Corporation
Last modified: Tuesday, August 30, 2011

Related Products Oracle E-Business Suite > Applications Technology > Technology Components > Oracle Applications Technology Stack

Back to top