Migrating Oracle E-Business Suite to Sun Oracle Database Machine Using Oracle Data Pump

Oracle Maximum Availability Architecture White Paper June 2010

Maximum Availability Architecture
Oracle Best Practices For High Availability

3

This paper will use existing Oracle Support notes to detail the process of migrating an existing Oracle E-Business Suite Release 12 11.2 database to Sun Oracle Database Machine. The existing source system database can be RDBMS release 10.2 or higher, but this paper illustrates an example were the source system database is release 11.2. Oracle Data Pump can be used for any supported source OS platforms with the minimum requirement of the source database being on release 10.2 or higher. Oracle E-Business Suite releases certified on Sun Oracle Database Machine configuration of OEL5 with Oracle Enterprise Edition release 11.2 are: 11.5.10.2 (11i) 12.0 12.1 The primary Oracle Support note being used for this example is Export/Import Process for Oracle E-Business Suite Release 12 Database Instances Using Oracle Database 11g Release 1 or 11g Release 2 [ID 741818.1]. This paper is a Sun Oracle Database Machine specific addendum to that Support note. Any special considerations not covered in the note will be included in this paper. If you are using Oracle E-Business Suite 11i then you should follow Oracle Support note Export/import notes on Applications 11i Database 11g (ID 557738.1). The Oracle E-Business Suite Vision database that is part of the Oracle E-Business Suite Rapid Install was used for this example. The application tier nodes are not moved as part of this example and just re-directed to the new database on Sun Oracle Database machine using Autoconfig.

Preparing properly for the migration will give you the necessary knowledge and confidence to complete a successful migration. While this is a migration, upgrade resources are also referenced as much of their content applies to a migration as well, especially if the source release is less than

4

Preparing the Target Database Instance This section describes how to create the empty target database with RAC and ASM and populate it with all of the required system objects prior to running import. As detailed in Support note 741818. 5 . 3. This is the step where the outage begins.11.1. 4. See Upgrade to 11g Performance Best Practices for details. Preparing the Source System This step ensures that the required patches are installed.2)” guide. Exporting the Source Database This section describes how to create your export files and capture important information that is required to import your database. and the following additional practices: Backup the source system and application tier.2. Complete details for Oracle Data Pump can be found in the “Oracle Database Utilities. This section also discusses deciding on using a network file system or using the Oracle Database File System (DBFS) for the export dump files. Stress test with real-life data and workloads Rehearse the migration and fallback procedures In addition to the above references. Updating the Imported Database This section describes how to recreate the database objects and relationships that are not handled by the Oracle Data Pump export (expdp) and import (impdp) utilities. records any advanced queue settings and some other general preparation. the high-level steps for migrating the Oracle E-Business Suite database to Sun Oracle Database Machine are: 1. there are references throughout this paper to help you achieve a successful migration. 11g Release 2 (11. generates the target database creation script. Preserve source system performance baseline information. Create a test plan that includes the best practices outlined in the Oracle Database 11g Release 2 Upgrade Companion Note: 785351. 2. This section also details re-configuring Oracle E-Business Suite to utilize load balancing for the application connections.1. Importing This section describes how to use the Oracle Data Pump import utility to load the Oracle Applications data into the target database 5.

LANG. 9062910 . if your source system database is less than 11. the details of what was done for that note in regard to the database will be included in the “Preparing the Target Database Instance” section. 2.1 ON 11. “Interoperability Notes Oracle E-Business Suite Release 12 with Oracle Database 11g Release 2 (11.1 rapid install with the Vision database was done. The details of the system environment can be found in the appendix at Environment Details.2.UNSATISFIEDLINKERROR The same Support note.2 source systems. It does include additional details related to configuring RAC and ASM with Oracle E-Business Suite on the target Sun Oracle Database Machine.1 completely as there are steps specific to 10.2 source database. ID 1058763.2. ID 1058763.0)”.2.1 were followed and included the following application tier patches: 1.1.1 in Support note 741818.1.1 (R12.2.TXK. 6 .0. Support note 741818.1 that are not covered in this case study.ADBLDXML AND AUTOCONFIG COMPLETES WITH NJNI11:JAVA. Prior to the export process the source system database was upgraded to RDBMS 11. will be used to setup the target system 11. 7303030 . the steps in “Interoperability Notes Oracle E-Business Suite Release 12 with Oracle Database 11g Release 2 (11.2) 3.env file.12.7. That installs a file-system based database with Oracle RDBMS Enterprise Edition 11.1 rapid install so was not necessary to apply.0)”.Oracle Techstack Release Update Pack 2 for 12.2 RDBMS 4.B.1 maintenance pack Oracle E-Business Suite 12.INTEROPERABILITY PATCH FOR R12. 7651166 .2 database ORACLE_HOME. 9366993 .1. Apply patch 7120092 to the source administration server node. Standard Oracle E-Business Suite environment variables will be referenced.1. Creating new application server tiers for the target environment has to be done either before starting or after completing all the steps in this document. Thus. The Oracle EBusiness Suite environment setup is done by sourcing the <APPL_TOP>/<SID_hostname>. but this example case study shows the complete set of steps for that case.2 and 11. Thus.1 should still be reviewed for an 11. then be sure to carefully review Support note 741818. For this example an Oracle E-Business Suite release 12.1 This is already part of the 12.This example does not include any unnecessary steps that are for pre 11. This patch provides several SQL scripts that facilitate exporting and importing an Applications database instance.DELTA. This document assumes that the application server tiers are not replaced.1.

if they are not already so.For this example a working directory named /ebs/expimp was created on network file system (NFS) storage. on the source database server node. 2) the target database.sql 11 Ensure that you do not have the rebuild index parameter in the spatial indexes. 7120092.hard. An alternative to using NFS storage is to use local storage and then use the Oracle Database File System (DBFS) on the target Sun Oracle Database Machine to hold the Oracle Data Pump exported dump files. For this example the mount command used was: As root: (on all 3 systems: 1) the source database. The export/import patch. The target database instance must be created with the same tablespace structure as the source database instance. the primary applications node.2) and Support note 1054431.1 for setting up DBFS on Sun Oracle Database Machine. cd /ebs/expimp sqlplus system/welcome1 @$AU_TOP/patch/115/sql/auclondb. See Oracle Database SecureFiles and Large Objects Developer's Guide 11g Release 2 (11. On the source administration server node. To use NFS you must ensure the correct mount options are used. This working directory will contain all generated files and scripts required for the complete process.actimeo=0 As oracle user (the software owner): mkdir /ebs/expimp This mount point will be used on all three systems: the source database. use SQL*Plus to connect to the database as SYSTEM and run the $AU_TOP/patch/115/sql/auclondb.wsize=32768. and 3) the primary applications node) The details of the system environment can be found in the appendix at Environment Details. It creates aucrdb.sql script. The script converts all tablespaces except for SYSTEM to locally managed tablespaces with auto segment space management. mkdir /ebs chown oracle:dba /ebs mount dscbbg03:/export2/ /ebs –o rsize=32768. and the target database node.sql in the current directory. which you use to create the target database instance with the appropriate tablespace and file structure. To see if you have any rebuild index parameters. provides the auclondb. as the owner of the 7 .sql script.sql script which generates the aucrdb.

Patch . Follow Support note 888828.1 ORACLE_HOME. that is not necessary now.0. It is completely valid to use the SUN ORACLE DATABASE MACHINE setup installed ORACLE_HOME but you should not share that ORACLE_HOME with other applications using the same Sun Oracle Database Machine.2. This will include the latest Opatch version (see “Opatch .1]”) and also includes the Oracle E-Business Suite R12 bundle patch. “N-APPLY BUNDLE PATCH FOR RDBMS 11.1 WITH EBS RELEASE 12” is required to be applied on the 11. c. In addition to installing a new 11. use SQL*Plus to connect to the source database as sysdba and run the following command: sqlplus "/ as sysdba" @auque1 SQL> select * from dba_indexes where index_type='DOMAIN' and upper(parameters) like '%REBUILD%'. patch . If you are installing a new 11.2) Supported Versions” to ensure the latest Sun Oracle Database machine patches are applied.1 WITH EBS RELEASE 12”.2 database home.1. 8 . “Database Machine and Exadata Storage Server 11g Release 2 (11.Where Can I Find the Latest Version of Opatch? [ID 224346.2. “N-APPLY BUNDLE PATCH FOR RDBMS 11.0. b. If any rows are returned then use SQL*Plus to connect to the source database as the owner of the index and run the following command: where the parameters are dependent on the source index and can be referenced in the Oracle Database SQL Language Reference guide.source database server file system and database instance.2. If you did not previously apply the applicaiton tier patches listed under “Apply Prerequisite Patches” then you should do that now.2 ORACLE_HOME set of software on the target Sun Oracle Database Machine make sure to choose the following options: Install Software Only Real Application Clusters database installation and select all RAC nodes a. SQL> alter index <index_name> rebuild <parameters> This step is optional if you want to use the ORACLE_HOME that is installed with Sun Oracle Database Machine.0. Support note was followed and since the application tier patches were already applied previously when the source system database was upgraded to 11.2.

if a tablespace has three datafiles of size 5G due to the fact that a default E_Business Suite install does not enable AUTOEXTEND.com/otn/linux/oracle11g/R2/linux.ora file from the $ORACLE_HOME/dbs directory to the target system. see “Oracle Recommended Patches -. then you can consolidate those into a single 15G datafile. 9 . In this example there are two database instances on the target system. On the target system 11.sql Script. Download the software from http://download.zip Follow the installation steps in the “Database Examples Installation Guide” in chapter 3 to install in the Oracle Database 11g Release 2 ORACLE_HOME.sql script is in the appendix at Modified aucrdb.pl Review Sun Oracle Database Machine best practices Support notes by searching “My Oracle Support” for “Sun Database Machine Best Practices. 1.sql” and change it to use the ASM diskgroup and add “AUTOEXTEND ON” to each datafile.2 Patch Set Updates and Exadata patches.x64_11gR2_examples.1. The target database will be VISMIG and use the already created ASM diskgroups of +DATA and +RECO. “Database Machine Health Check”. DDL to create the second UNDO tablespace was also added.1]. For example.” If Sun Oracle Database Machine health has not been verified yet then follow Support note 1070954.Oracle Database” [ID 756671. Copy the source system (dscbac08) init. 2. A sample of a modified aucrdb.oracle. The uniform extent size was left at the E-Business Suite setting of 128K. Edit the script created in “Generate target database instance creation script aucrdb.d. An UNDO tablespace should be added for each instance. Patch Setup Updates also include the latest Critical Patch Update (CPU).2 ORACLE_HOME execute the following: perl $ORACLE_HOME/nls/data/old/cr9idata. The original did not have AUTOEXTEND set and the datafile paths were „?/dbf/<datafilename>‟. You can also consolidate tablespace datafiles into a single or minimal number of files if desired. 1. Check and apply the latest 11.

Note that the CLUSTER_DATABASE parameter must be unset at database creation.2. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_VISMIG))) STATUS of the LISTENER -----------------------Alias LISTENER_VISMIG Version TNSLSNR for Linux: Version 11..77.0.168)(PORT=1524))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.1. For further details on database parameter settings see Support note 396009. See the example in the appendix at Initial listener. Oracle.2. The resulting file is included in the appendix at Target Database Starting Parameter File. All rights reserved. Run netca and create VISMIG listener selecting the “Cluster Configuration”.ora initVISMIG.ora Files.On the target system (dscgigdb03) cd $ORACLE_HOME/dbs scp dscbac08:/ebs/VISSI/db/tech_st/11.2..pfile 2.1. For this example the listener was named LISTENER_VISMIG.0/ebsmig/network/admin/li stener. the appropriate ASM diskgroup and add RAC parameters. 2009.ora Listener Log File /u01/app/oracle/diag/tnslsnr/dscgigdb03/listener_vismi g/alert/log.ora on all nodes and add a static SID entry. 0 min.0 .1.204. Use a new listener port as well. This will create a listener on each RAC node with the same name and add it to the RAC Oracle Cluster Registry (OCR).2.0/dbs/initVISSI. 3.Production on 10-JUN-2010 09:52:04 Copyright (c) 1991.204. “Database Initialization Parameters for Oracle Applications Release 12” 1. Edit the file to change file system paths with the new database name of VISMIG. 2. For this example 1524 was used. 34 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /u01/app/oracle/product/11.181)(PORT=1524))) The listener supports no services The command completed successfully 10 .0 Production Start Date 10-JUN-2010 09:51:30 Uptime 0 days 0 hr. Edit $ORACLE_HOME/network/admin/listener.xml Listening Endpoints Summary. (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER_VISMIG))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10. Reload the listener on all nodes lsnrctl reload listener_vismig 4. Status the listener to make sure it is running lsnrctl status LISTENER_VISMIG LSNRCTL for Linux: Version 11.74.0.

1. Using the edited script from Modified aucrdb.0/ebsmig ORACLE_SID=VISMIG1 ORA_NLS10=$ORACLE_HOME/nls/data/9idata PATH=$ORACLE_HOME/bin:$PATH 2. note the following: The remarks section at the beginning of each script contains additional information.sql Script and the parameter file from Target Database Starting Parameter File. As you run each of the next four steps. sqlplus "/ as sysdba" @audb1120 sqlplus system/welcome1 @ausy1120 sqlplus system/welcome1 @aujv1120 11 . export export export export ORACLE_HOME=/u01/app/oracle/product/11.log.sql.sql.sql. SQL> @aucrdb. and aumsc1120. ausy1120. which copied all files from the source administration server $AU_TOP/patch/115/sql directory to the /ebs/expimp NFS mounted file system.sql SQL> exit. create the database. SQL> startup nomount. patch 7120092. Record Advanced Queue settings” step. Copy the following files from the $AU_TOP/patch/115/sql directory of the source administration server node to the working directory in the target database server node: audb1120. aujv1120. For sample output for the scripts see the Database Preparation Script Output section of the appendix. Each script creates a log file in the current directory. that you applied to the source administration server node in “Apply the Applications consolidated export/import utility patch” contains four scripts that are needed on the target database server node.2 location.ora cd /ebs/expimp sqlplus "/ as sysdba" SQL> spool aucrdb. These files were copied earlier in the “Preparing the Source System” section under the “5. The export/import patch. Ensure that the environment of your session on the target database system is set to the new ORACLE_SID of VISMIG1 and the ORACLE_HOME and ORA_NLS10 are also set to the target 11.sql. cp $ORACLE_HOME/dbs/initVISMIG.pfile $ORACLE_HOME/dbs/initVISMIG1.2.

1. dscgigdb04 is te second RAC node (see Environment Details for details).pfile file cp $ORACLE_HOME/dbs/initVISMIG1. points to the new SPFILE $ORACLE_HOME/dbs/initVISMIG1.pfile2 3.ora' from pfile='$ORACLE_HOME/dbs/initVISMIG1. that spfile='+DATA/vismig/spfilevismig.ctx_adm.ora initVISMIG1.ora $ORACLE_HOME/dbs/initVISMIG1. Set CLUSTER_DATABASE=TRUE in the databse parameter file.ora 100% 39 0.ora dscgigdb04:`pwd`/initVISMIG2.cluster_database=true 2. 'public'). Copy current database parameter file to a . Copy the database parameter file to the other node(s) with the appropriate name. File created. Copy the new .spfile.pfile2'.sqlplus system/welcome1 @aumsc1120. Create database parameter file. SQL> @adstats.ora 6. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to put the database in restricted mode and run adstats. Restart the database so it will use the SPFILE 12 .spfile $ORACLE_HOME/dbs/initVISMIG1.sql: $ sqlplus "/ as sysdba" SQL> alter system enable restricted session.sql FALSE SYSAUX TEMP sqlplus "/ as sysdba" SQL> exec ctxsys. scp initVISMIG1. In this case study.sql from the administration server node to the target database server node. SQL> exit.sql $ sqlplus "/ as sysdba" SQL> alter system disable restricted session.set_parameter('file_access_role'.0KB/s 00:00 8.ora *. Create the SPFILE create spfile='+DATA/vismig/spfilevismig. Copy $APPL_TOP/admin/adstats. Restart the database 7.ora' 5.spfile to the database parameter file cp $ORACLE_HOME/dbs/initVISMIG1. 4. $ORACLE_HOME/dbs/initVISMIG1.

Create an additional redo thread and redo logs for each database instance a. Add redo logs for other thread(s) alter database add logfile instance „VISMIG2‟ group 4 ('+DATA') size 300M.2.2. 4. Get the redo log size and maximum group number SQL> select distinct bytes/1048576 from v$log.2.0/ebsmig:N On dscgigdb04: VISMIG2:/u01/app/oracle/product/11.cd $ORACLE_HOME/dbs orapwd file=orapw${ORACLE_SID} password=welcome1 1. Verify srvctl is working for the database srvctl stop database -d VISMIG srvctl start database -d VISMIG srvctl status database -d VISMIG Instance VISMIG1 is running on node dscgigdb03 Instance VISMIG2 is running on node dscgigdb04 13 . TABLESPACE_NAME -----------------------------UNDO_TBS1 UNDO_TBS2 3.2.0/dbhome_2 a "DATA.RECO" srvctl add instance -d VISMIG -i VISMIG1 -n dscgigdb03 srvctl add instance -d VISMIG -i VISMIG2 -n dscgigdb04 5. group 6 ('+DATA') size 300M. Enable the new thread alter database enable thread 2. group 5 ('+DATA') size 300M. BYTES/1048576 ------------300 SQL> select max(group#) from v$log.0/ebsmig:N 2. c. Add the database and ORACLE_SID to /etc/oratab on each node VISMIG:/u01/app/oracle/product/11.0/ebsmig:N On dscgigdb03: VISMIG1:/u01/app/oracle/product/11. Add the database and instances to the Oracle Cluster Registry (OCR) srvctl add database -d VISMIG -o /u01/app/oracle/product/11. MAX(GROUP#) ----------3 b. Ensure an undo tablespace exists for each database instance select tablespace_name from dba_tablespaces where contents='UNDO'.

Use the script at Verify Required Packages to verify that all required operating system packages are installed and install any missing packages as described later in the Verify Required Packages section. The performance improvement was not measured as part of this paper.0 there is an additional workaround required that is described in Support note 983715. then the database doesn‟t use any HugePages and all the memory allocated to HugePages goes to waste. You can use auque2. you must record them beforehand and enable them in the target database instance afterwards. take care in sizing HugePages. “How to Configure HugePages for Oracle Database on 64bit Linux Platforms”. enabled by setting SGA_TARGET.sql to enable the settings in the target database instance.sql. which generates a script called auque2.2. IS compatible with HugePages. The Automatic Shared Memory Management feature. You should perform a backup before starting the import. Follow Support note 744769. 14 . 22.sql. The export/import patch. enabled by the MEMORY_TARGET / MEMORY_MAX_TARGET database parameters. 7120092. HugePages are not configured by default on Sun Oracle Database Machine. Note that the Automatic Memory Management feature. Thus. The target database is now prepared for an import of the Applications data. but unpublished results have indicated 10% or greater performance improvement. Ensure that when running the recommended script provided with Note 401749. They do show performance improvement for OLTP applications such as Oracle E-Business Suite. makes the shared memory segments non-swappable and reduces process startup time.1 that the database is started. For RDBMS 11. Additionally.1. Advanced Queue settings are not propagated in the target database during the export/import process.1.1. Note that HugePages that are allocated and unused means wasted memory that can‟t be used for anything else and if the DBA happens to tweak the SGA size such that it exceeds the available HugePages by a small amount. is incompatible with the use of HugePages. enabling HugePages reduces the amount of kernel memory required to map page table entries for the SGA. contains auque1. Therefore.

add the following line to the parameter file: QUERY=applsys. as the owner of the source database server file system and database instance. on the source database server node.wf_item_attribute_values:"where item_type!='WFERROR' and name != 'EVENT_MESSAGE'" See Export Parameter File for the file contents $ sqlplus system/ SQL> create directory dmpdir_exp as '/ebs/expimp'.2).1 or 11.sql. The output will be of the form: Processing object type DATABASE_EXPORT/TABLESPACE Completed 70 TABLESPACE objects in 1 seconds PARALLEL=16 This option was not compared to a non-parallel run so there is no conclusive evidence to the impact. For a detailed discussion see Support note 365459. Copy $AU_TOP/patch/115/import/auexpdp. /ebs/expimp. 7120092.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the working directory in the source database server node. The PARALLEL option is most useful for jobs with a lot of data relative to metadata.dat from the source administration server node to the working directory. A template for the export parameter file has been included as part of the export/import patch. use SQL*Plus to connect to the source database as sysdba and run the auque1. Use a text editor to modify the file to reflect the source environment and other customized parameters. in the source database server node.Copy the auque1.1. It generates auque2. Add the following two parameters to the Oracle Data Pump export parameter file: METRICS=Y The METRICS=Y option of the export parameter file will give you a number of seconds for each “Processing” step. “Parallel Capabilities of Oracle Data Pump”. On source administration server: cp $AU_TOP/patch/115/sql /ebs/expimp On the source Database system: sqlplus "/ as sysdba" @auque1 2. If your source database is Oracle Database 11g (11. 15 . Then.sql script.

$INST_TOP/admin/scripts/adstpall. Users cannot use the Applications until the import is completed.0. use the following command: expdp "'/ as sysdba'" parfile=auexpdp.pl appspass=apps contextfile=$CONTEXT_FILE -removeserver Grant the exempt access policy privilege to system by using SQL*Plus to connect to the database as SYSDBA and run the following command: sqlplus "/ as sysdba" SQL> grant EXEMPT ACCESS POLICY to system. and database name parameter will all change on the database server. Go to the working directory: cd /ebs/expimp If the source database is 10. use the following command: expdp system/ parfile=auexpdp.sh Since the database port.Shut down all Applications server processes except the database and the Net8 listener for the database.0.dat The METRICS=Y option of the export parameter file will give you a number of seconds for each “Processing” step. To avoid ORA-39213 errors.dat If the source database is 11.2.load_stylesheets Start an export session on the source database server node using the customized export parameter file. deregister the current database server node by running the following command as the owner of the Oracle RDBMS file system and current database instance: $ perl $ORACLE_HOME/appsutil/bin/adgentns. The output will be of the form: Processing object type DATABASE_EXPORT/TABLESPACE Completed 70 TABLESPACE objects in 1 seconds 16 . host.1. SID. as it is in this example.2.0 or 11. excue the following: sqlplus “/ as sysdba” SQL> execute dbms_metadata_util.

then be sure to review Support note 741818.2 and 11. in the target database server node. The following two parameters were added to the parameter file: METRICS=Y The METRICS=Y option of the export parameter file will give you a number of seconds for each “Processing” step. See Export Timings for details.log > expdpapps_time. An example of that would be: tailTime expdpapps.dat are set properly.2 source systems. It does include additional details related to configuring RAC and ASM with Oracle EBusiness Suite on the target Sun Oracle Database Machine. 17 . Use a text editor to modify the file to reflect the source environment and other customized parameters.log will then have the form: 100602 11:42:07 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER The export for the Vision database took 7:42:29 (hours:minutes:seconds).The export log does not capture timestamp information for each output line though. /ebs/expimp.1 completely as there are 10.2. The output will be of the form: Processing object type DATABASE_EXPORT/TABLESPACE Completed 70 TABLESPACE objects in 1 seconds PARALLEL=16 This option was not compared to a non-parallel run so there is no conclusive evidence to the impact.dat from the $AU_TOP/patch/115/import directory in the source administration server node to the working directory. Revoke the exempt access policy privilege from system by using SQL*Plus to connect to the database as SYSDBA and run the following command: SQL> revoke EXEMPT ACCESS POLICY from system. “Parallel Capabilities of Oracle Data Pump”. For a detailed discussion see Support note 365459. dumpfile. The PARALLEL option is most useful for jobs with a lot of data relative to metadata.1 specific steps.log The output in expdpapps_time. If your source system database is less than 11.1. Make sure that the directory. so if it‟s desired to gather complete timing information use the Timestamp Script in the appendix to prefix the export log output with a timestamp. To reiterate. and logfile parameters in auimpdp. Copy auimpdp. this example does not include any unnecessary steps that are for pre 11.

1. If the Oracle Database File System (DBFS) is being used then it is necessary to use secure copy (scp) the files into the DBFS location. “ORA-39000 ORA31640 And Ora-27054 Erorrs On Invoking Data Pump Import”. so to gather timing information use the Timestamp Script in the appendix to prefix the import log output with a timestamp.log The output in impdpapps_time. This example is using an NFS storage area that is shared between the source and target system so this step was not necessary. See DBFS Parallel Copy Script for an example script.dat The METRICS=Y option of the import parameter file will give you a number of seconds for each “Processing” step.log > impdpapps_time.log will then have the form: 100605 22:34:12 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE The import of the Vision database took 16:11:58 (hours:minutes:seconds). The output will be of the form: Processing object type DATABASE_EXPORT/TABLESPACE Completed 70 TABLESPACE objects in 1 seconds The import log does not capture timestamp information for each output line though.dat parameter file. and set the following database parameter event: event="10298 trace name context forever. An example of that would be: tailTime impdpapps. Note that if NFS is being used then follow Support note 739570.See Import Parameter File for the file contents $ sqlplus system/ SQL> create directory dmpdir_mig as '/ebs/expimp'. 6. About 40% of the time can be saved by doing parallel copies. Revoke the exempt access policy privilege from system by using SQL*Plus to connect to the database as SYSDBA and run the following command: 18 . level 32" Start an import session on the target database server node using the auimpdp. See Import Timings for details. impdp "'/ as sysdba'" parfile=auimpdp.

“tablespace … already exists" Action: Ignore Action: handled post-import under Compile invalid objects ORA-39083: Object type TABLE_STATISTICS failed to create with error: ORA-06550: line 1. Use the auque2. ORA-39083: Object type TRIGGER failed to create with error: ORA-04072: invalid trigger type Failing sql is: BEGIN DBMS_DDL. base object type <Base object type> already exists ORA-39151: Table "<table name>" exists.sql script that was generated in “Record Advanced Queue settings” of the “Preparing the Source System” section in the NFS mounted working directory /ebs/expimp. END. ORA-31684: “Object type <> already exists” ORA-39111: Dependent object type <Object Type> skipped. ORA-39083: Object type TRIGGER failed to create with error: ORA-04072: invalid trigger type Failing sql is: BEGIN DBMS_DDL. Action: Ignore Noted to give an idea of the total number of errors encountered with the Vision database import.FALSE) . All dependent metadata and data will be skipped due to table_exists_action of skip ORA-1543 errors.SQL> revoke EXEMPT ACCESS POLICY from system. END.SET_TRIGGER_FIRING_PROPERTY('"ORASSO"'. 4. 19 .'"IPR_LOGON"'.SET_TRIGGER_FIRING_PROPERTY('"B2B"'.FALSE) . column 555: PLS-00103: Encountered the symbol "~" when expecting one of the following: Action: gather index statistics manually.'"LOGOFF_TRIGGER"'.

pl Copy the appsutil. 2. /ebs/expimp. Generate the appsutil.0/ebsmig 20 .env The listeners should already be running but if they are not then start them now: srvctl start listener –l listener_vismig Copy $APPL_TOP/admin/adgrants. use SQL*Plus to connect to the target database as SYSDBA and run the auque2. SQL> @auque2.sql from the administration server node to the working directory. in the database server node.sql from the administration server node to the database server node.zip dscgigdb04:/u01/app/oracle/product/11. as the owner of the Oracle 11g file system and database instance.zip file to each DB server node ORACLE_HOME scp /ebs/VISSI/inst/apps/VISSI_haovm021/admin/out/appsutil.2.sql script to enable the Advanced Queue settings that were lost during the export/import process.env on dscgigdb04: source $ORACLE_HOME/VISMIG2_dscgigdb04.sql welcome1 CTXSYS On application administration node: 1.zip dscgigdb03:/u01/app/oracle/product/11.env file. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command: sqlplus "/ as sysdba" @adgrants. run the following command: perl $AD_TOP/bin/admkappsutil.sql Source the $ORACLE_HOME/<SID_hostname>.zip for the database tier.0/ebsmig scp /ebs/VISSI/inst/apps/VISSI_haovm021/admin/out/appsutil. cd /ebs/expimp $ sqlplus /nolog SQL> connect / as sysdba. Use SQL*Plus to connect to the database as APPS and run the script using the following command: sqlplus apps/apps @adctxprv. Example on dscgigdb03: source $ORACLE_HOME/VISMIG1_dscgigdb03.2.sql APPS Copy $AD_TOP/patch/115/sql/adctxprv.On the target database server node. The script creates a log file in the current directory.

2. Revise the listener on each database node The reason the listener requires revision is: In 11..0/ebsmig/appsutil/VISMIG1_dscgigdb03. As the APPS user..setup_clean. by editing the database context file $ORACLE_HOME/appsutil/VISMIG1_dscgigdb03. Set the value of s_virtual host_name to point to the virtual hostname for the database host.zip 6. listeners are configured at the cluster level. This means that the TNS_ADMIN directory path will be the same on all nodes.COMPLETED Attempting upload of Context file and templates to database. Generate a new context file perl $ORACLE_HOME/appsutil/bin/adbldxml.. Run autoconfig on each database node $ORACLE_HOME/appsutil/bin/adconfig.2. Using Context file : /u01/app/oracle/product/11.2.2..zip on each target database node: 4. 21 .env file has been source $ORACLE_HOME/appsutil/bin/adconfig.COMPLETED Updating rdbms version in Context file to db112 Updating rdbms type in Context file to 64 bits Configuring templates from ORACLE_HOME . Install appsutil.xml Context Value Management will now update the Context file Updating Context file. run the following command on the primary node to de-register the current configuration: SQL>exec fnd_conc_clone. unzip -o appsutil.pl The context file has been created at: /u01/app/oracle/product/11.On the target database node: 3.sh contextfile=$CONTEXT_FILE .xml <host oa_var="s_virtual_hostname">dscgig03-vip</host> <host oa_var="s_virtual_hostname">dscgig04-vip</host> 8. 9. cd $ORACLE_HOME 5.sh contextfile=/u01/app/oracle/product/11.0/ebsmig/appsutil/VISMIG1_dscg igdb03.xml Or more generically if the $ORACLE_HOME/<ORACLE_SID_hostname>.0/ebsmig/appsutil/VISMIG1_dscgigdb03. AutoConfig completed successfully... and all nodes inherit the port and environment settings.xml 7...

ora file is modified changing all occurrences of LISTENER_DSCGIGDB03 to LISTENER_VISMIG. At present.ora to point to the prior Autoconfig modified files under $ORACLE_HOME/network/admin/<context-name>/listener.ora ii. i. to match the previously netca created listener name. on dscgigdb03 the $ORACLE_HOME/network/admin/VISMIG1_dscgigdb03/listener. LISTENER_<hostname>.ora file.2. in the Autoconfig generated listener. to set up a connection to one of the instances in the Oracle RAC environment. $ORACLE_HOME/network/admin/listener. This will be addressed in a future version of AutoConfig. For the resulting files see Modified Post Autoconfig listener.The current version of AutoConfig creates a listener.0/ebsmig/network/admin/VISMIG1_dscgigd b03/listener. Set the database environment in OCR srvctl setenv database -d VISMIG -T TNS_ADMIN=$ORACLE_HOME/network/admin v. AutoConfig does not support SCAN listeners. IFILE=/u01/app/oracle/product/11. manual editing of the listener configuration file is required following the run of Autoconfig on the database nodes.ora file under the $ORACLE_HOME/network/admin/<context-name> directory with listener names of the form listener_<hostname>.ora files for the resultant files. Until then. iii.ora e. i. Due to this.ora files. On each database node modify the listener name.ora file.e. On each database node add an ifile entry to See Modified Post Autoconfig listener. Set the listener environment in OCR srvctl setenv listener -l listener_vismig –T TNS_ADMIN=$ORACLE_HOME/network/admin iv. So for example. $ORACLE_HOME/network/admin/<contextname>/listener. Edit the DB environment file and change TNS_ADMIN vi $ORACLE_HOME/${ORACLE_SID}_`hostname –s`. Make sure the listener can stopped and started with srvctl srvctl stop listener -l listener_vismig srvctl start listener -l listener_vismig 1. LISTENER_VISMIG. this post-Autoconfig workaround is required to have the listener managed by CRS via the srvctl utility.env and set TNS_ADMIN=”$ORACLE_HOME/network/admin” vi.ora. This issue will be addressed in a future version of AutoConfig by creating a user-defined context variable. Edit SID=<Instance 1> and PORT=<New listener port > in $TNS_ADMIN/tnsnames.g. different listener names on each node in the cluster. 22 .

23 . Run the script sqlplus "/ as sysdba" alter system enable restricted session.oracle. Verify the connection sqlplus system/welcome1 3. To populate the CTXSYS.pl ctx_az_obj.drv 11 Once the driver file has been generated. @adstats. use AutoPatch (adpatch) to apply it on the target administration server node.com)(PORT=1524)))(CONNECT_DATA=(SERVICE_NAME=VISMIG)))</j dbc_url> 4.us.sql sqlplus "/ as sysdba" alter system disable restricted session. use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following command: $ sqlplus apps/ SQL> exec icx_cat_sqe_pvt. perl $AU_TOP/patch/115/bin/dpost_imp.us.com)(PORT=1523)))(CONNECT_DATA=(SERVICE_NAME=VISSI)))</jd bc_url> After <jdbc_url oa_var="s_apps_jdbc_connect_descriptor">jdbc:oracle:thin:@(DESCRIPTION= (ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(H OST=dscgig03vip.sql /ebs/expimp 2. Copy $APPL_TOP/admin/adstats.sh 1. adding the instance name to the connect_data parameter. Edit the context variable in $CONTEXT_FILE.oracle. jdbc_url.2. cp $APPL_TOP/admin/adstats.sql from the administration server node to the database server node work directory.DR$SQE table. Run Autoconfig $INST_TOP/admin/scripts/adautocfg.sync_sqes_for_all_zones. Before <jdbc_url oa_var="s_apps_jdbc_connect_descriptor">jdbc:oracle:thin:@(DESCRIPTION=(AD DRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=ds cbac08.

$ sqlplus "/ as sysdba" @$ORACLE_HOME/rdbms/admin/utlrp. From the Maintain Applications Database Objects menu.sh Create DQM indexes by following these steps: Login with “operations/welcome” and then select "Trading Community Manager" 24 . use SQL*Plus to connect to the target database as SYS and run the $ORACLE_HOME/rdbms/admin/utlrp. You can allow users to access the system at this time. $INST_TOP/admin/scripts/adstrtal.On the target database server node.sql Run AD Administration (adadmin) on the target administration server node. perform the following tasks: Start all the server processes on the target Applications system. as the owner of the Oracle 11g file system and database instance.sql script to compile invalid objects.

oracle.1 was used as the basis for these steps.us.Oracle Support note 823587.com)(PORT=1524)) ) (CONNECT_DATA= (SERVICE_NAME=VISMIG) ) ) "Tools OH TWO_TASK" (s_tools_two_task) is under the “Environments” tab under “oa_environment:tools_home "iAS OH TWO_TASK" (s_weboh_twotask) is under the “Environments” tab under “oa_environment:web_home” "Apps JDBC Connect Alias" (s_apps_jdbc_connect_alias) is under the “System” tab under “oa_web_server” In the Context Editor search on the value of VISMIG_BALANCE and you should see the following after changes: 25 . To access the Context Editor: From Applications tier node $TNS_ADMIN/tnsnames.com)(PORT=1524)) (ADDRESS=(PROTOCOL=tcp)(HOST=dscgig03-vip.us.oracle.ora VISMIG_BALANCE= (DESCRIPTION= (ADDRESS_LIST= (LOAD_BALANCE=YES) (FAILOVER=YES) (ADDRESS=(PROTOCOL=tcp)(HOST=dscgig04-vip. Implement load balancing for the Oracle Applications database connections: This example uses the Context Editor.

The intent of this paper was to illustrate the steps to migrate an existing Oracle E-Business Suite installation‟s database to Sun Oracle Database Machine using Oracle Data Pump.oracle.sh A successful migration of Oracle E-Business Suite to Sun Oracle Database Machine is dependent upon thorough preparation that includes planning. Any improvements to this process will be updated in this paper and reposted to the Maximum Availability Architecture website at http://www. The process entails referring to multiple Oracle Support notes that are referenced herein with explicit examples included.com/technology/deploy/availability/htdocs/maa. and review of all the steps involved. testing. 26 .$INST_TOP/admin/scripts/adautocfg.htm.

2 $APPL_TOP /ebs/VISSI/apps/apps_st/appl $INST_TOP /ebs/VISSI/inst/apps/VISSI_haovm021 NFS mounted storage from dscbbg03:/export2/ on /ebs Compute Nodes Names: dscgigdb03 and dscgigdb04 IP Addresses .181 .com Oracle Enterprise Linux 2.1. single instance install Name: dscbac08 Oracle Enterprise Linux 2.0.204.168 .1.18-128.7 ORACLE_HOME=/ebs/VISSI/db/tech_st/11.oracle.182 ORACLE_HOME /u01/app/oracle/product/11.1.74.dscgigdb04 10.77.The hardware and software details for the test environment are as follows: Single node.74.0/ebsmig 27 .dscgigdb03 10.0.0.204.1.dscgig03-vip 10.204. x86_64 Oracle Enterprise Edition 11.1.77.169 .0.2.6.0 DB_NAME=VISSI ORACLE_SID=VISSI NFS mounted storage from dscbbg03:/export2/ on /ebs Name: haovm021.us.1 ORACLE_HOME /ebs/VISSI/apps/tech_st/10.2.21.2.18-53. x86_64 E_Business Suite Version 12.204.dscgig04-vip 10.el5.2.6.

18-128.1].1.2-44.1.el5 glibc-2.6-9.2-44.el5 gcc-4.53GHz) processors Exadata Smart Flash Cache 384 GB 12 x 1TB 7.5-34 libgcc-4.6. $ rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' \ openmotif21 xorg-x11-libs-compat binutils gcc gcc-c++ glibc \ glibc-common glibc-devel libgcc libstdc++-devel libstdc++ make \ gdbm libXp libaio libgomp sysstat compat-libstdc++-296 \ compat-libstdc++-33 package openmotif21 is not installed package xorg-x11-libs-compat is not installed binutils-2.16.1 2 Quad-Core Intel Xeon® E5540 Processors (2.0.53 GHz) 72 GB memory Disk Controller HBA with 512MB Battery Backed Write Cache 4 x 146 GB SAS 10.1.5-34 glibc-devel-2. For the latest list of required packages also see Support note Oracle Applications Installation and Upgrade Notes Release 12 (12.ORACLE_SID=VISMIG1 and VISMIG2 respectively DB_NAME=VISMIG Each with: Oracle Enterprise Linux 2.5-34 (x86_64) (x86_64) gcc-c++-4.0.el5 28 .200 RPM SATA drives NFS mounted storage from dscbbg03:/export2/ on /ebs Here is a sample check of the required packages on a fresh Sun Oracle Daatabase Machine.el5 (i686) (x86_64) (x86_64) (i386) (x86_64) (i386) (x86_64) glibc-common-2.2.000 RPM disks Dual-Port QDR InfiniBand Host Channel Adapter 4 Embedded Gigabit Ethernet Ports Storage: 3 Exadata Cells (dscgigcel05-07) Each cell with: 2 Quad-core Intel Xeon E5540 (2.2-44.1.5-34 glibc-2.5-34 glibc-devel-2.1.0.17.50.1) for Linux x86-64 [ID 761566.el5 x86_64 Oracle Enterprise Edition 11.1.

1.el5 libaio-0.rpm Preparing.0-8. 1:openmotif21 ########################################### [100%] ########################################### [100%] This script was originally generated on the source system using the $AU_TOP/patch/115/sql/auclondb.el5 sysstat-7.i386.0-8.8.el5 libXp-1.8.1. many of the tablespaces had multiple datafiles for relatively small sizes.2-44.i386.3.3.1.2-44.2 libaio-0.EL. The change of the datafile paths to the ASM „+DATA‟ diskgroup with the DB_NAME of VISMIG was done within the VI editor using the following command: : %s/?\/dbf/+DATA\/VISMIG\/DATAFILE/g 29 .0-26.3-61 For any missing or older packages.106-3.3.1.2-7.1.1.0..2-44.el5 libstdc++-4.2.oracle. Additionally.2.libgcc-4.el5 gdbm-1.1 (i386) (x86_64) (x86_64) (x86_64) (i386) (i386) (x86_64) (i386) (x86_64) (i386) (x86_64) (x86_64) (i386) (i386) (x86_64) libXp-1.81-3.el5 libgomp-4..0.1.sql script.2 libgomp-4. The source system was using the file system for the datafile paths of the form „?/dbf/<datafile-name>‟ and no AUTOEXTEND setting.2-44. ########################################### [100%] 1:xorg-x11-libs-compat ########################################### [100%] $ rpm -ivh openmotif21-2.el5 (x86_64) (i386) (x86_64) libstdc++-devel-4.el5 libstdc++-devel-4.el5 libstdc++-4.2.2-3.1 gdbm-1.96-138 compat-libstdc++-33-3.30-11. The addition of „AUTOEXTEND ON‟ and the consolidation of the datafiles was done manually.EL5..com/projects/compatoracle/files/Enterprise_Linux/ $ rpm -ivh xorg-x11-libs-compat-6.33..rpm Preparing. see http://oss.1.0.el5 make-3.0.8.2-7.106-3.2-1.1.2.el5 compat-libstdc++-296-2.2-44.0-26.3.3-61 compat-libstdc++-33-3.

dbf' SIZE 18000M AUTOEXTEND ON. REM REM Database Instance : VISSI REM Database Version : 11.2.sql REM REM DESCRIPTION REM REM Script to create a database with tablespaces and files REM similar to that of the database against which the script REM was generated.0.dbf' ) SIZE 300M . GROUP 2 ( '+DATA/VISMIG/ONLINELOG/log2.dbf' SIZE 1339M AUTOEXTEND ON UNDO TABLESPACE "UNDO_TBS1" DATAFILE '+DATA/VISMIG/datafile/undotbs1_01.dbf' ) SIZE 300M .Tablespace storage information REM . '+DATA/VISMIG/datafile/temp2_02.dbf' SIZE 3700M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE "TEMP2" TEMPFILE '+DATA/VISMIG/datafile/temp2_01.dbf' SIZE 18000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M / CREATE TEMPORARY TABLESPACE "TEMP1" TEMPFILE '+DATA/VISMIG/datafile/temp1_01.Location and size of the data files REM .0 REM Creation Date : 03-JUN-2010 08:48:23 REM REM NOTES REM BEFORE RUNNING THE SCRIPT YOU MUST REVIEW REM IT FOR THE FOLLOWING : REM .dbf' ) SIZE 300M DATAFILE '+DATA/VISMIG/datafile/SYSTEM01.1.dbf' SIZE 18000M AUTOEXTEND ON.dbf' SIZE 20491M AUTOEXTEND ON SYSAUX DATAFILE '+DATA/VISMIG/datafile/sysaux01. 30 .Rollback Segment information REM REM =========================================================================== REM ----------------------------------------------------------------------REM Create Database REM ----------------------------------------------------------------------CREATE DATABASE MAXDATAFILES 512 CHARACTER SET AL32UTF8 NATIONAL CHARACTER SET UTF8 LOGFILE GROUP 1 ( '+DATA/VISMIG/ONLINELOG/log3. GROUP 3 ( '+DATA/VISMIG/ONLINELOG/log1.REM =========================================================================== REM REM NAME REM aucrdb.Database Characterset information REM .

dbf' SIZE 5000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_OMO" DATAFILE '+DATA/VISMIG/datafile/APPS_OMO02. prompt prompt Ignore any errors related to the setting prompt of the default temporary tablespace prompt REM ----------------------------------------------------------------------REM Create Tablespaces REM ----------------------------------------------------------------------CREATE TABLESPACE "APPS_CALCLIP" DATAFILE '+DATA/VISMIG/datafile/apps_calclip.'+DATA/VISMIG/datafile/temp1_02.dbf' SIZE 906M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_DISCO_OLAP" DATAFILE '+DATA/VISMIG/datafile/disco_drake1. ALTER TABLESPACE "TEMP1" TABLESPACE GROUP "TEMP".dbf' SIZE 1200M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_DISCO" DATAFILE '+DATA/VISMIG/datafile/disco1.dbf' SIZE 18000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M / ALTER TABLESPACE "TEMP2" TABLESPACE GROUP "TEMP".dbf' SIZE 1350M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_INTERFACE" DATAFILE '+DATA/VISMIG/datafile/apps_ts_interface.dbf' SIZE 1200M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_ARCHIVE" DATAFILE '+DATA/VISMIG/datafile/archive1. ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "TEMP".dbf' SIZE 3000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K 31 .

dbf' SIZE 700M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_QUEUES" DATAFILE '+DATA/VISMIG/datafile/APPS_TS_QUEUES02.dbf' SIZE 7000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_NOLOGGING" DATAFILE '+DATA/VISMIG/datafile/nologging1.dbf' SIZE 16000M AUTOEXTEND ON.dbf' SIZE 21000M AUTOEXTEND ON.dbf' SIZE 21000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "B2B_DT" DATAFILE 32 . '+DATA/VISMIG/datafile/APPS_TS_TX_IDX02. '+DATA/VISMIG/datafile/APPS_TS_TX_DATA_02.dbf' SIZE 23000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_TX_DATA" DATAFILE '+DATA/VISMIG/datafile/APPS_TS_TX_DATA_01.SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_MEDIA" DATAFILE '+DATA/VISMIG/datafile/media1.dbf' SIZE 5000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_SEED" DATAFILE '+DATA/VISMIG/datafile/reference1.dbf' SIZE 16000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_TX_IDX" DATAFILE '+DATA/VISMIG/datafile/APPS_TS_TX_IDX01.dbf' SIZE 4000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "APPS_TS_SUMMARY" DATAFILE '+DATA/VISMIG/datafile/APPS_TS_SUMMARY02.

dbf' SIZE 13M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "B2B_RT" DATAFILE '+DATA/VISMIG/datafile/b2b_rt.dbf' SIZE 72M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "B2B_IDX" DATAFILE '+DATA/VISMIG/datafile/b2b_idx.'+DATA/VISMIG/datafile/b2b_dt.dbf' SIZE 92M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "CWMLITE" DATAFILE '+DATA/VISMIG/datafile/cwmlite01.dbf' SIZE 17M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "B2B_LOB" DATAFILE '+DATA/VISMIG/datafile/b2b_lob.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DATA" 33 .dbf' SIZE 1000M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / AUTOEXTEND ON CREATE TABLESPACE "CTXSYS" DATAFILE '+DATA/VISMIG/datafile/ctx1.dbf' SIZE 45M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "BAM" DATAFILE '+DATA/VISMIG/datafile/bam.dbf' SIZE 8M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "BIA_RTL" DATAFILE '+DATA/VISMIG/datafile/bia_rtl.

dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / 34 .dbf' SIZE 3M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DSGATEWAY_TAB" DATAFILE '+DATA/VISMIG/datafile/oss_sys01.dbf' SIZE 7M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / AUTOEXTEND ON AUTOEXTEND ON CREATE TABLESPACE "DW_AGGREGATE_IDX" DATAFILE '+DATA/VISMIG/datafile/dw_aggregate_idx.dbf' SIZE 7500M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DCM" DATAFILE '+DATA/VISMIG/datafile/dcm.dbf' SIZE 114M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DISCO_PTM5_META" DATAFILE '+DATA/VISMIG/datafile/discopltm1.dbf' SIZE 300M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DEMANTRA" DATAFILE '+DATA/VISMIG/datafile/DEMANTRA02.dbf' SIZE 100M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / AUTOEXTEND ON CREATE TABLESPACE "DW_AGGREGATE_TBS" DATAFILE '+DATA/VISMIG/datafile/dw_aggregate_tbs.dbf' SIZE 5500M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DISCO_PTM5_CACHE" DATAFILE '+DATA/VISMIG/datafile/discopltc1.DATAFILE '+DATA/VISMIG/datafile/data01.

dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_LOOKUP_TBS" DATAFILE '+DATA/VISMIG/datafile/dw_lookup_tbs.dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_DERIVED_IDX" DATAFILE '+DATA/VISMIG/datafile/dw_derived_idx.CREATE TABLESPACE "DW_BASE_IDX" DATAFILE '+DATA/VISMIG/datafile/dw_base_idx.dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_BASE_TBS" DATAFILE '+DATA/VISMIG/datafile/dw_base_tbs.dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_DM_TBS" DATAFILE '+DATA/VISMIG/datafile/dw_dm_tbs.dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_MVLOG_TBS" DATAFILE '+DATA/VISMIG/datafile/dw_mvlog_tbs.dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K 35 .dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_REFERENCE_IDX" DATAFILE '+DATA/VISMIG/datafile/dw_reference_idx.dbf' SIZE 100M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_DERIVED_TBS" DATAFILE '+DATA/VISMIG/datafile/dw_derived_tbs.

dbf' SIZE 600M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "IAS_META" DATAFILE '+DATA/VISMIG/datafile/IAS_META02.dbf' SIZE 4M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "OCATS" DATAFILE '+DATA/VISMIG/datafile/oca.dbf' SIZE 3M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "ODM_DATA" DATAFILE '+DATA/VISMIG/datafile/odm.dbf' SIZE 1500M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL 36 .dbf' SIZE 40M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / AUTOEXTEND ON AUTOEXTEND ON CREATE TABLESPACE "OLAP_BAAD" DATAFILE '+DATA/VISMIG/datafile/olap_baad01.SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "DW_REFERENCE_TBS" DATAFILE '+DATA/VISMIG/datafile/dw_reference_tbs.dbf' SIZE 300M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "MTR" DATAFILE '+DATA/VISMIG/datafile/opmtr01.dbf' SIZE 3000M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "HTMLDB" DATAFILE '+DATA/VISMIG/datafile/htmldb.dbf' SIZE 134M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "GEOR_TBS" DATAFILE '+DATA/VISMIG/datafile/apps_ts_spatial.

dbf' SIZE 15M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "OLTS_CT_STORE" DATAFILE '+DATA/VISMIG/datafile/gcats1_oid.dbf' SIZE 10M AUTOEXTEND ON 37 .dbf' SIZE 15M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "OLTS_BATTRSTORE" DATAFILE '+DATA/VISMIG/datafile/battrs1_oid.dbf' SIZE 6M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "ORABPEL" DATAFILE '+DATA/VISMIG/datafile/orabpel.UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "OLTS_ATTRSTORE" DATAFILE '+DATA/VISMIG/datafile/attrs1_oid.dbf' SIZE 3M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "OLTS_SVRMGSTORE" DATAFILE '+DATA/VISMIG/datafile/svrmg1_oid.dbf' SIZE 13M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / AUTOEXTEND ON AUTOEXTEND ON AUTOEXTEND ON AUTOEXTEND ON AUTOEXTEND ON AUTOEXTEND ON CREATE TABLESPACE "OWAPUB" DATAFILE '+DATA/VISMIG/datafile/owa1.dbf' SIZE 8M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "OLTS_DEFAULT" DATAFILE '+DATA/VISMIG/datafile/gdefault1_oid.dbf' SIZE 3M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "OPMOR" DATAFILE '+DATA/VISMIG/datafile/opmor01.

dbf' SIZE 8M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "SYNCSERVER" DATAFILE '+DATA/VISMIG/datafile/mobile01.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / 38 .dbf' SIZE 46M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "RE" DATAFILE '+DATA/VISMIG/datafile/opre01.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "TS_SALES_DATA" DATAFILE '+DATA/VISMIG/datafile/ts_sales_data.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "TS_SALES_DATA_ENGINE_X" DATAFILE '+DATA/VISMIG/datafile/ts_sales_data_engine_x.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "TS_SALES_DATA_ENGINE" DATAFILE '+DATA/VISMIG/datafile/ts_sales_data_engine.dbf' SIZE 58M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "TS_DP" DATAFILE '+DATA/VISMIG/datafile/ts_dp.EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "RBS_MIG" DATAFILE '+DATA/VISMIG/datafile/rbs_mig01.

dbf' SIZE 3700M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL / The source of this file was the single instance source database system.dbf' SIZE 300M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / REM Added for RAC CREATE UNDO TABLESPACE "UNDO_TBS2" DATAFILE '+DATA/VISMIG/datafile/undotbs2_01. ASM and RAC setup prior to the database creation. The file was then modified to accommodate the new database name of VISMIG.CREATE TABLESPACE "TS_SALES_DATA_X" DATAFILE '+DATA/VISMIG/datafile/ts_sales_data_x.dbf' SIZE 3M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "XDB" DATAFILE '+DATA/VISMIG/datafile/xdb01.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "UDDISYS_TS" DATAFILE '+DATA/VISMIG/datafile/uddisys01.dbf' SIZE 22M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "WCRSYS_TS" DATAFILE '+DATA/VISMIG/datafile/wcrsys01.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "TS_SIM" DATAFILE '+DATA/VISMIG/datafile/ts_sim.dbf' SIZE 50M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO / CREATE TABLESPACE "TS_SIM_X" DATAFILE '+DATA/VISMIG/datafile/ts_sim_x. The CLUSTER_DATABASE parameter is commented out for databse 39 .

control_files='+DATA/VISMIG/CONTROLFILE/cntrl01.sec_case_sensitive_logon=FALSE *.'+DATA/VISMIG/CONTROLFI LE/cntrl02.nls_numeric_characters='.session_cached_cursors=500 *.processes=200 *.job_queue_processes=2 *.pga_aggregate_target=1073741824 *._system_trig_enabled=true *.db_name='VISMIG' *.query_rewrite_enabled='true' *.dbf'.sga_target=1073741824 40 ._sort_elimination_cost_ratio=5 *._index_join_enabled=FALSE *._b_tree_bitmap_plans=FALSE *.log_checkpoint_timeout=1200 *.nls_comp='binary' *.parallel_max_servers=8 *.control_files='/ebs/VISSI/db/apps_st/data/cntrl01.aq_tm_processes=1 *.'/ebs/VISSI/db/apps_st/data/cntrl03.sessions=400 *.nls_language='american' *.dbf'.db_block_checking='FALSE' *._optimizer_autostats_job=FALSE *.creation.olap_page_pool_size=4194304 *.recyclebin='OFF' *.plsql_optimize_level=2 *._like_with_bind_as_equality=TRUE *.db_files=512 # Old setting #*.'+RECO/VISMIG/CONTROLFILE/cntrl03.nls_territory='america' *.dbf'.db_block_checksum='TRUE' *.2._fast_full_scan_enabled=FALSE *.db_name='VISSI' # New target *.nls_sort='binary' *.nls_date_format='DD-MON-RR' *.optimizer_secure_view_merging=FALSE *..plsql_code_type='INTERPRETED' *._sqlexec_progression_cost=2147483647 *. *.0' # Old setting #*.'/ebs/VISSI/db/apps_ st/data/cntrl02.cursor_sharing='EXACT' *.open_cursors=600 *.log_checkpoints_to_alert=TRUE *.nls_length_semantics='BYTE' *.dml_locks=10000 *.event='' *.dbf' # New target *.java_pool_size=209715200 *.parallel_min_servers=0 *.db_block_size=8192 *.' *.compatible='11.log_checkpoint_interval=100000 *._disable_fast_validate=TRUE *.dbf' *. The changes from the original file are highlighted in red and also have a comment for the “Old setting” and the “New target”.diagnostic_dest='/u01/app/oracle' *.dbf'._trace_files_public=TRUE *.log_buffer=10485760 *.max_dump_file_size='20480' *.

'/usr/tmp'.1.instance_number=2 VISMIG1.'/usr/tmp' VISMIG2.utl_file_dir='/usr/tmp'.'/usr/tmp'. DBFS has been setup and mounted on /dbfs/dbfs/ebs #!/bin/ksh # sourceDir=/ebs/expimp targetDir=/dbfs/dbfs/ebs LOG=/ebs/expimp/DBFS_parallel.utl_file_dir='/usr/tmp'.'/usr/tmp'.dmp` do time cp $fileName $targetDir >> $LOG & done Node 1 LISTENER_VISMIG=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY= LISTENER_VISMIG)))) # line added by Agent 41 .undo_management='AUTO' # Old setting #*.db_create_file_dest='+DATA' # RAC Additions #*.'/u01/app/oracle/product/11.utl_file_dir='/usr/tmp'.1 *.event="10298 trace name context forever.log # for fileName in `ls $sourceDir/*.undo_tablespace='UNDO_TBS1' VISMIG2.*.workarea_size_policy='AUTO' # # Added for ASM and Oracle Managed Files *.undo_tablespace='UNDO_TBS2' # Added for issues with NFS for import.local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOS T=dscgig04-vip)(PORT=1524))))' VISMIG1.'/ebs/VISSI/db/tech_st/11.db_recovery_file_dest='+RECO' *.thread=1 VISMIG2.undo_tablespace='UNDO_TBS' # Old setting #*.shared_pool_size=419430400 *.db_recovery_file_dest_size=500G *.instance_number=1 VISMIG2.timed_statistics=TRUE *.'/u01/app/oracle/product/11.0/ebs mig/appsutil/outbound/VISMIG_dscgigdb03'.shared_pool_reserved_size=41943040 *.thread=2 VISMIG1. For this example it is mounted on /ebs/expimp. level 32" This script can be used to copy each 1 Gb export file in parallel from the source system export location to the target system DBFS import location.'/usr/tmp' # New target VISMIG1.2.local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOS T=dscgig03-vip)(PORT=1524))))' VISMIG2.'/usr/tmp' *. This script has the following prerequisites: The source file system containing the export dump files is NFS mounted on the target Sun Oracle Database Machine.0/appsutil/o utbound/VISSI_dscbac08'.2.cluster_database=true VISMIG1.0/ebs mig/appsutil/outbound/VISMIG_dscgigdb04'. Support note 739570.

com = 0 $Header: adlsnr10RAC.ora file # # # # # # # # # # # # # Definition for RAC Database listener # LISTENER_DSCGIGDB03.us.com = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dscgig03-vip.1 for assistance.0/ebsmig) (SID_NAME = VISMIG1) ) ) # line added by Agent Node 2 LISTENER_VISMIG=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY= LISTENER_VISMIG)))) # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_ LISTENER_VISMIG=ON # line added by Agent # SID_LIST_ LISTENER_VISMIG = (SID_LIST = (SID_DESC = (ORACLE_HOME= /u01/app/oracle/product/11.12010000.oracle.us. It will be read and overwritten.ora 120.com)(PORT = 1524)(IP = FIRST))) ) ) SID_LIST_LISTENER_DSCGIGDB03.oracle.0/ebsmig)(SID_NAME = VISMIG1)) ) STARTUP_WAIT_TIME_LISTENER_DSCGIGDB03.2.2. refer to Metalink Note 387859.com = (SID_LIST = (SID_DESC = (ORACLE_HOME = /u01/app/oracle/product/11.us.ENABLE_GLOBAL_DYNAMIC_ENDPOINT_ LISTENER_VISMIG=ON # SID_LIST_ LISTENER_VISMIG = (SID_LIST = (SID_DESC = (ORACLE_HOME= /u01/app/oracle/product/11.oracle.oracle.0/ebsmig) (SID_NAME = VISMIG2) ) ) $ORACLE_HOME/network/admin/VISMIG1_dscgigdb03/listener. If you were instructed to edit this file.2 2009/09/03 16:51:27 schagant ship $ ############################################################### This file is automatically generated by AutoConfig.3.2. ############################################################### 42 . or if you are not able to use the settings created by AutoConfig.us.

com = /u01/app/oracle/product/11.oracle.com = /u01/app/oracle/product/11.com = 0 CONNECT_TIMEOUT_LISTENER_DSCGIGDB04.com = OFF IFILE=/u01/app/oracle/product/11.com = VISMIG2 ADMIN_RESTRICTIONS_LISTENER_DSCGIGDB04.oracle.us.us.12010000.com = OFF $Header: adlsnr10RAC.com = (SID_LIST = (SID_DESC = (ORACLE_HOME = /u01/app/oracle/product/11.us.oracle.us.us.2. It will be read and overwritten.com = VISMIG1 ADMIN_RESTRICTIONS_LISTENER_DSCGIGDB03.com = 10 TRACE_LEVEL_LISTENER_DSCGIGDB04.us.us.oracle.oracle.oracle. refer to Metalink Note 387859.oracle.com)(PORT = 1524)(IP = FIRST))) ) ) SID_LIST_LISTENER_DSCGIGDB04.ora 120.0/ebsmig/network/admin LOG_FILE_LISTENER_DSCGIGDB04.oracle.2 2009/09/03 16:51:27 schagant ship $ ############################################################### This file is automatically generated by AutoConfig.com = VISMIG1 TRACE_DIRECTORY_LISTENER_DSCGIGDB03.ora $ORACLE_HOME/network/admin/VISMIG2_dscgigdb04/listener. or if you are not able to use the settings created by AutoConfig.oracle.us.com = OFF LOG_DIRECTORY_LISTENER_DSCGIGDB04.oracle.2.0/ebsmig/network/admin LOG_FILE_LISTENER_DSCGIGDB03.CONNECT_TIMEOUT_LISTENER_DSCGIGDB03.oracle.us.oracle.us.us.oracle.com = /u01/app/oracle/product/11.0/ebsmig/network/admin TRACE_FILE_LISTENER_DSCGIGDB04.2.us.com = OFF SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER_DSCGIGDB03.com = /u01/app/oracle/product/11.oracle.2.0/ebsmig/network/admin TRACE_FILE_LISTENER_DSCGIGDB03.com = OFF LOG_DIRECTORY_LISTENER_DSCGIGDB03.us.3.2.com = 10 TRACE_LEVEL_LISTENER_DSCGIGDB03. ############################################################### 43 .us.us.oracle.oracle.oracle. If you were instructed to edit this file.com = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dscgig04-vip.us.2.oracle.ora file # # # # # # # # # # # # # Definition for RAC Database listener # LISTENER_DSCGIGDB04.0/ebsmig/network/admin/VISMIG1_dscgigdb03/liste ner_ifile.1 for assistance.us.us.com = VISMIG2 TRACE_DIRECTORY_LISTENER_DSCGIGDB04.us.0/ebsmig)(SID_NAME = VISMIG2)) ) STARTUP_WAIT_TIME_LISTENER_DSCGIGDB04.oracle.

2.ora $ORACLE_HOME/network/admin/VISMIG1_dscgigdb03/listener.0/ebsmig/network/admin/VISMIG1_dscgigdb03/liste ner. refer to Metalink Note 387859.com = 0 CONNECT_TIMEOUT_LISTENER_VISMIG.1 for assistance.oracle.us.ora file # File after a change all of the string # # # # # # # # # # # LISTENER_DSCGIGDB03 to LISTENER_VISMIG $Header: adlsnr10RAC.com = 10 TRACE_LEVEL_LISTENER_VISMIG.3.oracle.0/ebsmig)(SID_NAME = VISMIG1)) ) STARTUP_WAIT_TIME_LISTENER_VISMIG.com = (SID_LIST = (SID_DESC = (ORACLE_HOME = /u01/app/oracle/product/11.oracle.us.oracle.com = OFF 44 .oracle.us.oracle.SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER_DSCGIGDB04.0/ebsmig/network/admin/VISMIG2_dscgigdb04/liste ner_ifile.ora 120.us.com = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dscgig03-vip.2 2009/09/03 16:51:27 schagant ship $ ############################################################### This file is automatically generated by AutoConfig.oracle.ora file # Added the IFILE line LISTENER_VISMIG=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_VI SMIG)))) # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_VISMIG=ON # line added by Agent # Manually added to point to the Autoconfig and manually modified listener.com = OFF IFILE=/u01/app/oracle/product/11. or if you are not able to use the settings created by AutoConfig.us.2. It will be read and overwritten.com)(PORT = 1524)(IP = FIRST))) ) ) SID_LIST_LISTENER_VISMIG.us.ora IFILE=/u01/app/oracle/product/11.ora $ORACLE_HOME/network/admin/listener.us.12010000.2. ############################################################### # # Definition for RAC Database listener # LISTENER_VISMIG. If you were instructed to edit this file.

12010000.com = /u01/app/oracle/product/11.oracle.2.com = VISMIG1 TRACE_DIRECTORY_LISTENER_VISMIG.2.1 for assistance.ora $ORACLE_HOME/network/admin/VISMIG1_dscgigdb04/listener. ############################################################### # # Definition for RAC Database listener # LISTENER_VISMIG.us.us.ora file # File after a change all of the string # $ # # # # # # # # # # LISTENER_DSCGIGDB03 to LISTENER_VISMIG $Header: adlsnr10RAC.0/ebsmig)(SID_NAME = VISMIG2)) 45 .2.2 2009/09/03 16:51:27 schagant ship ############################################################### This file is automatically generated by AutoConfig.3.us.com = OFF IFILE=/u01/app/oracle/product/11.ora file LISTENER_VISMIG=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_VI SMIG)))) # line added by Agent ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_VISMIG=ON # line added by Agent # Manually added to point to the Autoconfig and manually modified listener.oracle.2.com = OFF SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER_VISMIG.0/ebsmig/network/admin/VISMIG2_dscgigdb04/liste ner. or if you are not able to use the settings created by AutoConfig.us.us.com = VISMIG1 ADMIN_RESTRICTIONS_LISTENER_VISMIG.oracle. It will be read and overwritten.oracle.oracle.us.LOG_DIRECTORY_LISTENER_VISMIG.com = /u01/app/oracle/product/11.oracle.0/ebsmig/network/admin LOG_FILE_LISTENER_VISMIG.ora # Added the IFILE line $ORACLE_HOME/network/admin/listener.0/ebsmig/network/admin/VISMIG1_dscgigdb03/liste ner_ifile.us.com)(PORT = 1524)(IP = FIRST))) ) ) SID_LIST_LISTENER_VISMIG.us. refer to Metalink Note 387859.0/ebsmig/network/admin TRACE_FILE_LISTENER_VISMIG.com = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dscgig04-vip.oracle.oracle.ora 120. If you were instructed to edit this file.oracle.us.ora IFILE=/u01/app/oracle/product/11.com = (SID_LIST = (SID_DESC = (ORACLE_HOME = /u01/app/oracle/product/11.2.

oracle.oracle..2.com = 0 CONNECT_TIMEOUT_LISTENER_VISMIG.com = OFF SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER_VISMIG.us.oracle.us.com = /u01/app/oracle/product/11.0/ebsmig/network/admin LOG_FILE_LISTENER_VISMIG.com = /u01/app/oracle/product/11.us.oracle.'YYYY-MM-DD HH24:MI:SS')||' ---' " " 3 from dual. sqlplus system/welcome1 SQL> @ausy1120 PL/SQL procedure successfully completed.oracle.us.0/ebsmig/network/admin TRACE_FILE_LISTENER_VISMIG.us. .com = OFF LOG_DIRECTORY_LISTENER_VISMIG.com = 10 TRACE_LEVEL_LISTENER_VISMIG.us.ora sqlplus "/ as sysdba" @audb1120 Connected. Commit complete.com = OFF IFILE=/u01/app/oracle/product/11.) STARTUP_WAIT_TIME_LISTENER_VISMIG. . SQL> exit.audb1120 completed at '|| 2 to_char(sysdate.audb1120 started at 2010-06-04 08:50:56 --SQL> SQL> select '--.2.com = VISMIG2 TRACE_DIRECTORY_LISTENER_VISMIG.audb1120 completed at 2010-06-04 08:56:37 --1 row selected. SQL> SQL> spool off SQL> SQL> commit.com = VISMIG2 ADMIN_RESTRICTIONS_LISTENER_VISMIG.us.oracle. ------------------------------------------------... ----------------------------------------------------------.us. PL/SQL procedure successfully completed.2..oracle.ausy1120 started at 04-JUN-2010 09:01:24 --- 46 .0/ebsmig/network/admin/VISMIG2_dscgigdb04/liste ner_ifile. --------------------------------------------------.oracle.oracle.us.

Starting initjvm.aumsc1120 completed at '|| 2 to_char(sysdate.Done with catexf. PL/SQL procedure successfully completed.aujv1120 started at 2010-06-04 09:02:46 ----------------------------------------------------. -------------------------------------------------. ------------------------------------------------.sql2010-06-04 09:18:17 --Connected. PL/SQL procedure successfully completed. … … SQL> select '--.Starting catqm. sqlplus system/welcome1 SQL> @aujv1120 Connected. Session altered.aujv1120 completed at 2010-06-04 09:05:48 --Commit complete. sqlplus system/welcome1 SQL> @aumsc1120.'---AUSY1120COMPLETEDAT'||TO_CHAR(SYSDATE. PL/SQL procedure successfully completed.ausy1120 completed at 04-JUN-2010 09:01:25 ---Commit complete.sql FALSE SYSAUX TEMP Connected. -------------------------------------------------. PL/SQL procedure successfully completed.sql 2010-06-04 09:05:48 ----------------------------------------------------.sql 2010-06-04 09:02:46 --PL/SQL procedure successfully completed. PL/SQL procedure successfully completed.'DD-MON-YYYYHH24:M -------------------------------------------------------------.'YYYY-MM-DD HH24:MI:SS')||' ---' " " 47 .aumsc1120 started at 2010-06-04 09:18:17 --- -----------------------------------------------.

1 QUERY=applsys. printf "%s " `date '+%y%m%d %H:%M:%S'` $var. #!/bin/bash # tail of a file and add a timestamp to the output # export logfile=$1 tail -f $logfile | ( while true.0 2007/07/18 20:42:38 gong noship $ directory=dmpdir_exp dumpfile=aexp%U.dmp filesize=1048576000 full=y exclude=SCHEMA:"='MDDATA'" exclude=SCHEMA:"='OLAPSYS'" exclude=SCHEMA:"='ORDSYS'" exclude=SCHEMA:"='DMSYS'" exclude=SCHEMA:"='OUTLN'" exclude=SCHEMA:"='ORDPLUGINS'" #transform=oid:n logfile=expdpapps.dat 120. echo done ) echo "done!" Total time was 7:42:29 Longest processing was for the package body objects: Completed 52696 PACKAGE_BODY objects in 10091 seconds (2:48:11) #$Header: auimpdp.1 to capture timings METRICS=y This script can be used to prepend a timestamp to a file while it is being generated. #$Header: auexpdp.0 2007/07/18 20:43:14 gong noship $ 48 .1 PARALLEL=16 # Added per note 286496. This file is named tailTime. do read var. ---------------------------------------------------.dat 120.3 from dual.log # Added per note 741818.aumsc1120 completed at 2010-06-04 09:26:43 --1 row selected. See Note 365459.wf_item_attribute_values:"where item_type!='WFERROR' and name != 'EVENT_MESSAGE'" # Added but no basis of comparison to quantify its benefit.

1 to capture timings metrics=Y Total time was 16:11:58 A summary of the longest phases is: Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT – 9 minutes Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM – 00:07:29 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE – 00:58:44 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA – 00:32:23 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT.1.otn.com/goto/maa 2.1] 3.1) for Linux x86-64 [ID 761566.04:57:23 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEX – 02:53:54 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/CONSTRAINT – 00:06:32 Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE/PACKAGE_SPEC – 00:15:50 Processing object type DATABASE_EXPORT/SCHEMA/VIEW/VIEW – 00:21:58 Processing object type DATABASE_EXPORT/SCHEMA/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT – 00:05:00 Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE_BODIES/PACKAGE/PACKAGE_BODY – 03:24:00 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/STATISTICS/TABLE_STATISTICS – 00:54:00 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX – 00:25:32 Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER – 00:06:52 1.directory=dmpdir_mig dumpfile=aexp%U.log # Set to ((number of CPU‟s) * 2) # Added but no basis of comparison to quantify its benefit. See Note 365459. Oracle Maximum Availability Architecture Web site http://www.1] Interoperability Notes EBS R12 with Database 11gR2 [ID 1058763. Oracle Applications Installation and Upgrade Notes Release 12 (12.oracle. 49 .dmp full=y transform=oid:n #exclude=tablespace #exclude=profile #exclude=user #exclude=role #exclude=system_grant #exclude=proc_system_grant #exclude=role_grant logfile=impdpapps.1 parallel=16 # Added per note 286496.

7.1] DBFS on Oracle Database Machine [ID 1054431.1] Export/import notes on Applications 11i Database 11g (ID 557738.Database Machine HealthCheck [ID 1070954. 10.Configuring 11.1] . Export/Import Process for Oracle E-Business Suite Release 12 Database Instances Using Oracle Database 11g Release 1 or 11g Release 2 [ID 741818.4.bde_chk_cbo. Steven Chan's E-Business Suite Technology Blog 11gR2 Database Certified with E-Business Suite 11i 11gR2 Database Certified with E-Business Suite 12 Upgrade to 11g Performance Best Practices Oracle 11.Healthcheck [ID 174605.1] 5.sql 12.1] 8.2 Upgrade Companion [ID 785351. 6. 9.EBS initialization parameters .1] 50 .1) Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 [ID 823587.

Sign up to vote on this title
UsefulNot useful