Before migrating to the new platform, ensure the Target System meets all the requirements for Oracle Applications Release 11i stated on the Oracle Applications Release Notes and on the Oracle Applications Update Notes for the Target Platform
2. Verify the software versions on the Target System
Perl 5.005
JDK 1.4.2
To check
perl –v
java –version
3.Verify the database version
If your database version is lower than Oracle8i Enterprise Edition Release 8.1.7.4, upgrade it to the latest certified patchset of Oracle8i Release 8.1.7 or any higher certified version
4. Apply the latest AD Patch
Apply patch 4712852 (AD.I.5) or higher. Please refer to OracleMetaLink to obtain the latest MiniPack available for AD. The AD patch level can be found in the report generated by the following command:
sqlplus /@$AD_TOP/sql/adutconf.sql
5. Implement AutoConfig on the Application Tier
If the Source Applications System was created with Rapid Install version 11.5.8 or earlier you must migrate the System to Autoconfig. Follow the instructions on Migrating to AutoConfig on the Application Tier in document 165195.1 in OracleMetaLink. 6. Apply the latest AutoConfig Template patch
Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes. Refer to Document 165195.1 in OracleMetaLink for details of the latest Autoconfig Template rollup patch available.
7. Apply the latest Rapid Clone patch
Update the Oracle Applications file system with the latest Patches required by Rapid Clone. Refer to Document 230672.1 in OracleMetaLink for details of the latest required patches.
8.Maintain snapshot information
Run adadmin to maintain snapshot information on all nodes. Refer to the Oracle Applications Maintenance Utilities manual for more details
Section 2: Migrate Platforms with Oracle Applications 11i
1. Generate and upload the manifest of customer-specific files
a. Log in to your Source System primary administration node as the APPLMGR user and source the APPL_TOP environment file. Execute the following command to generate the customer-specific file manifest. This step should take about a minute:
perl $AD_TOP/bin/adgenpsf.pl
b. Go to http://updates.oracle.com/PlatformMigrationhttp://updates.oracle.com/PlatformMigration (use your OracleMetaLink username and password) and follow the instructions on the screen to upload the manifest file previously generated:
$APPL_TOP/admin/$TWO_TASK/out/adgenpsf.txt
2. Create the Target System APPL_TOP
Copy the middle tier file system from the Source Applications System to the Target Node by executing the following steps in the order listed. Ensure that the application tier files copied to the Target System are owned by the Target APPLMGR user. Please note that before you go ahead with this step your Source application tiers should point to target database
Note: The Source System can remain up and running until the last step of the migration.
a. Copy the APPL_TOP file system
Log on to the Source System application tier node as the APPLMGR user and copy the following application tier directories from the Source System to the Target System § § § §/util §/_pages (when that directory exists)
Attention: Copy only the directories listed, not the full COMMON_TOP
Perform above-mentioned steps on both the application tier nodes.
a. Copy the security file for JInitiator
If you wish to preserve the Source System digital signature on the migrated System, copy the identitydb.obj file from the Source System to the Target System. This file is located in the APPLMGR user's home directory on UNIX or the root directory of the %SystemDrive% on Windows.§
If you want the migrated System to have a new digital signature, remove the following file from the Target System:§
rm /admin/appltop.cer
1. Clone the AutoConfig XML context file on the Target System
The Clone Context tool will ask for all the new mount points on the Target migration node. Log on to the Target System as the APPLMGR user and run the following commands:
o cd /bin
Note: Provide the OS java location.
where: complete path where the JDK is installed. full path to the Source System Applications XML context file located in /admin on the Target System.
2. Respond to the prompts.
This will create the following Target System context file:
Provide the values required for creation of the new APPL_TOP Context file.
Do you want to use a virtual hostname for the target node (y/n) [n] ?:
Does the target system have more than one application tier server node (y/n) [y] ?:
Does the target system application tier utilize multiple domain names (y/n) [n] ?:
Target system concurrent processing node [dbnode]:sever1
Target system administration node [dbnode]:server1
Target system forms server node [webnode]:server2
Target system web server node [webnode]:server2
Is the target system APPL_TOP divided into multiple mount points (y/n) [n] ?:
Target system APPL_TOP mount point [/u01/app/oracle/sidappl]:
Target system COMMON_TOP directory [/u06/app/oracle/sidcomn]:/u01/app/oracle/sidcomn
Do you want to preserve the Display set to server:0.0 (y/n) [y] ?:n
Target system Display [server2:0.0]:
Location of the JDK on the target system [/u06/app/oracle/sidcomn/util/java/1.4/j2sdk1.4.2_04]:/usr/java14
Target system JRE_TOP [/u06/app/oracle/sidcomn/util/java/1.4/j2sdk1.4.2_04]:/ usr/java14
RC-00024: Warning: Could not find perl at expected location:
/tmp//Apache/perl/bin/perl
Please verify the integrity of the filesystem.
Perl executable location is set to:
/usr/bin/perl
Enter the Database listener port [1539]:
APPS password is required to validate database connection using database port 1539
Enter APPS Password [APPS]:abcd
Database port is 1539
Do you want the middle-tier services on the target system to have the same port values as the source system (y/n) [y] ?:
Web Listener port is 8018
Complete port information available at /u01/app/oracle/sidappl/admin/out/SID_server2/portpool.lst
UTL_FILE_DIR on database tier consists of the following directories.
1. /usr/tmp/SID
2. /usr/tmp
3. /u52/app/oracle/siddb/10.2.0/appsutil/outbound/SID_sunserver
Choose a value which will be set as APPLPTMP value on the target node [1]:1
Target system APPL_TOP of the Forms node:/u01/app/oracle/sidappl
Creating the new APPL_TOP Context file from :
/u01/app/oracle/sidappl/ad/11.5.0/admin/template/adxmlctx.tmp
The new APPL_TOP context file has been created :
/u01/app/oracle/sidappl/admin/SID_server2.xml
JDK for Solaris was found under $COMMON_TOP
Removing directory /u01/app/oracle/sidcomn/util/java/1.4/j2sdk1.4.2_04
Done.
Log file located at /u01/app/oracle/sidappl/ad/11.5.0/bin/CloneContext_11121151.log
applsid@server2$
Note: See document 216664.1 on OracleMetaLink for more information on port pool.
1. Install the Middle Tier Technology Stack
Run the Rapid Install Wizard with the -techstack option to install the iAS technology stack. Use the Target System context file created in the previous step. (on both the application tier nodes)
cd [u01/app/software/rapidwiz
./rapidwiz -techstack
Follow the instructions in the "Installation Tasks" section of Installing Oracle9i Application Server 1.0.2.2.2 with Oracle Applications 11i" (document 146468.1).
Note: Use the latest startCD available in OracleMetalink. Refer to the "Current Version of Rapid Install" section in the Oracle Applications Release Notes for details on the latest startCD Patch.
More details on how to execute rapidwiz can be found on the Oracle Applications 11i Installation Manual.
Attention: Review the log files (setup_stubs..log) under the iAS ORACLE_HOME to ensure that there are no errors
P.S: Add the entry for iAS & 8.0.6 home variables in your xml file, please make sure all the occurrence of /tmp is replaced properly by tools_oh or weboh as appropriate before proceeding further. If still not clear see the SID xml file for reference
i.e. : /u02/app/oracle/sidora/iAS /u
02/app/oracle/sidora/8.0.6/SID_server1.env /u02/app/oracle/sidora/8.0.6
Also make sure to change the perl location to point to iAS/perl please see the xml file for SDBA
1. Run AutoConfig setup phase on the Target System
Execute the INSTE8_SETUP phase of AutoConfig with the new context file. This will create the environment files required for the AutoPatch session:
o cd /bin
o ./adconfig.sh run=INSTE8_SETUP contextfile=
Note: This command does not require the environment to be sourced.
1. Download and apply the customer-specific update with AutoPatch
Within 30 minutes from the time you uploaded the manifest file at step 2.b you will receive a notification email saying that your customer specific update patch is ready. Follow the instructions in the email to download it from Oracle MetaLink. The patch should be applied on all Target System application nodes. Source the APPL_TOP environment file and follow the instructions in the README to apply the patch. AutoPatch will automatically relink the executables.
Note: Executables dependent on third party products (Ilog, Roguewave, and Quantum) might fail during relinking. This is expected and is addressed in "Section 3: Finishing Tasks". In that case, answer "yes" when adpatch asks whether to "Continue as if it were successful".
README to apply the patch
Complete the following steps to apply this patch:
To apply this patch the following steps must be completed:
1. Source the APPL_TOP environment file on the target migration system
This environment was created during the execution of AutoConfig.
See MetaLink Note 238276.1, the step entitled "Run AutoConfig on the
Target Node."
2. Unzip this patch into a patch directory.
3. Change directories to the patch directory e.g 6612518 directory created in step 2 above.
4. Run adpatch from the current directory to apply this patch using
the u6612518.drv driver:
./adpatch options=noprereq
Please note all the executables under sht product family will fail as we don’t have these on Soalris.This is taken care in the
1. Review the technology stack patch level
Identify any patches previously applied to your Source System technology stack which are not included in the "Release Versions" section of " Installing Oracle9i Application Server 1.0.2.2.2 with Oracle Applications 11i" (document 146468.1). Apply these patches to your Target System technology stack. (Not Applicable)
Applied 5473858 (techstack RUP5).autoconfig failed with following error
autoconfig fails on adgendbc.sh with ORA-06512: at "APPS.FND_APP_SERVER_PKG", line 91
After applying 5473858 autoconfig fails on apps tier to resolve it apply patch 6496781. (Doc id 434494.1 on metalink)
Note: For information and instructions on applying the latest Developer 6i patchset, see Note 125767.1 on OracleMetaLink (Not Applicable)
Applied the following developer 6i patches
Developer 6i Developer 6i Patch Forms Reports Graphics Apps Interop Patch
Patch 18* 4948577
6.0.8.27.x 6.0.8.27.x 6.0.8.17.x 4888294
And the additional patches
5713544
4261542
5216496
5753922
6195758
2. Download and apply the techstack interop patch
Apply patch 4139957 to the Target Oracle Applications file system
3. Regenerate the file system objects
Source the APPL_TOP environment file and perform the following tasks to regenerate the platform dependent files on the Target System:
1. If migrating the Forms node, run the following script:
$AD_TOP/patch/115/bin/adgensgn.sh /
2. Run adadmin to generate messages, forms, reports, graphics and jar files.
3. Run AutoConfig to complete the Target System configuration
$AD_TOP/bin/adconfig.sh contextfile=
Note: The database will be updated to reflect the new Target System profile. Make sure all users are off the system and shut down the Source System application tier server processes. After this step, the Source System middle tier will no longer be available.
Section 3: Finishing Tasks
1. Update 3rd party extensions
ILOG Apply patch 2837811 and relink dependent executables.
ROGUEWAVE Apply patch 3006092 and relink dependent executables
After applying the above patches the adrelink should exit with status 0 i.e there should be no errors in relink.
2. Review and update your Target System application tier settings and customizations
a. Recompile any custom code (forms, C) in the Target System APPL_TOP.
b. If you were using UTF8 charset, Discoverer 4i, SSO or Portal 3i on the Source System, refer to the corresponding documentation to complete the migration:
Setup Documentation
UTF8 "Installing Oracle Applications 11i" Manual,
Chapter 5, "Set Up UTF8 Character Set".
Discoverer 4i Document 139516.1 on OracleMetaLink.
SSO or Portal 3i Document 146469.1 on OracleMetaLink.
3. Update printer settings
If the newly migrated System needs to utilize different printers, update the Target System with the new printer settings now.
4. Update Workflow configuration settings (would be done by autoconfig but please check)
Migrating an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance-specific data in the Workflow configuration on the Target System.
5.
Table Name Column Name Column Value Details
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE Value starts with http://: Update to new web host
WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE Value starts with "http://: Update to new web host
WF_SYSTEMS GUID Create a new System defined as the new global database name using the Workflow Administrator Web Applications responsibility.
WF_SYSTEMS NAME Value needs to be replaced with the database global name
WF_AGENTS ADDRESS Update database link with the new database global name.
FND_FORM_FUNCTIONS WEB_HOST_NAME Update with the new web host name
FND_FORM_FUNCTIONS WEB_AGENT_NAME Update to point at the new PLSQL listener name
FND_CONCURRENT_REQUESTS LOGFILE_NAME Update with the correct path to the logfile directory
FND_CONCURRENT_REQUESTS OUTFILE_NAME Update with the new directory path on the Target System
6. Review your CLASSPATH setting
Log in to the Target APPL_TOP environment (source the environment file) and perform the following tasks to consolidate your CLASSPATH:
a. Verify the AD classpath:
1. Run $ADJVAPRG -version
2. If the result shows a java version of 1.3.1 or higher, use Context Editor to update the variable s_adovar_classpath in the context file: replace appsborg.zip by appsborg2.zip in the classpath string.
b. Verify the AF classpath:
1. Run $AFJVAPRG -version
2. If the result shows a java version of 1.3.1 or higher, use Context Editor to update the variable s_adovar_afclasspath in the context file: replace appsborg.zip by appsborg2.zip in the classpath string.
The above would be done once you run autoconfig so no need to worry but do check this.
c. Run AutoConfig as described in document 165195.1 on OracleMetalink.
7. Start all services on the Target System
Start all services by running the script:
adstrtal.sh / located in /admin/scripts//
I will walk you with the steps required to convert the entire Oracle Applications environment from Solaris to AIX.
The Migration happens in 2 phases (any order can be followed)
1. Moving the source database to the target operating system
2. Moving the source application tier to the target operating system
Lets now discuss the first step in detail
1. Porting data for an Apps environment using expdp/impdp
The process consists of five discrete steps
1: Prepare the source system
Tasks that must be performed to prepare the source system for the database export
2: Prepare a target Applications Release 11i database instance
Tasks for creating an empty database instance in preparation for import
3: Export the source Applications Release 11i database instance
Tasks that must be performed to produce a valid export of an Applications Release 11i database instance
4: Import the Applications Release 11i database instance
Tasks for running the import utility
5: Update the imported Applications Release 11i database instance
Tasks that must be performed to restore the imported Applications Release 11i database instance to a fully functional state
Note: The source (export from) and target (import to) ORACLE_HOME directories must be Oracle Database 10g Release 2 (10.2.0). Environments using Oracle8i Enterprise Edition Release 8.1.7, Oracle9i Enterprise Edition Release 2 (9.2.0), or Oracle Database 10g Release 1 (10.1.0) have to be upgraded to Oracle Database 10g Release 2 (10.2.0) before you begin the export/import process.
Section 1: Prepare the source system
This section describes how to ensure that you have the required patches, create your export file, and capture important information that is required to import your database.
· Verify that you have at least 1.5 GB of free SYSTEM tablespace. · Apply the Applications consolidated export/import utility patchApply patch 4872830to the source administration server node. This patch provides several SQL scripts that facilitate exporting and importing an Applications database instance. The patch includes a template for the export and import parameter files and a perl script, which creates an AD patch driver.
· Apply latest Applications database preparation scripts patch Apply patch 5000152to every application tier server node in the source system (superseded by 5873146)
Generate target database instance creation script adcrdb.sql
The target database instance must be created with the same tablespace and file structure as the source database instance.
Patch 4872830 provides the adclondb.sql script which generates the following scripts:
adcrdb.sql, which you use to create the target database instance with the appropriate tablespace and file structure
adpostcrdb.sql, which you use to convert tablespaces to locally managed.
The adpostcrdb.sql script converts all tablespaces except for SYSTEM to locally managed tablespaces, if they are not already so.
On the source administration server node, use SQL*Plus to connect to the database as SYSTEM and run the
$AD_TOP/patch/115/sql/adclondb.sql script. It creates adcrdb.sql in the current directory. $ sqlplus system/\ @$AD_TOP/patch/115/sql/adclondb.sql 10
Record Advanced Queue settings Advanced Queue settings are not propagated in the target database instance during the export/import process. Therefore, you must record them beforehand and enable them in the target database instance afterwards.
Patch 4872830 contains auque1.sql, which generates a script called auque2.sql.
You can use auque2.sql to enable the settings in the target database instance.
Copy the auque1.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the source database server node. It does not matter which directory you use. Then, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the auque1.sql script.
It generates auque2.sql in the current directory.
$ sqlplus /nologSQL> connect / as sysdba;SQL> @auque1.sql
Section 2: Prepare a target Applications Release 11i database instance
This section describes how to create the empty target database and populate it with all of the required system objects prior to running import.
The Oracle home of the target database instance is on a different machine running a different operating system, for example), but it should use Oracle Database 10g Release 2 Enterprise Edition
· Install the Oracle Software 10.2.0.2
· Create the target initialization parameter file and CBO parameter file The initialization parameter file (init.ora) and cost-based optimizer (CBO) parameter file (ifilecbo.ora) are located in the $ORACLE_HOME/dbs directory on the source database server node.
Copy both files to the Oracle 10g $ORACLE_HOME/dbs directory on the target database server node.Refer to Database Initialization Parameters (init.ora settings) in Oracle Applications Release 11iand update both the init.ora and ifilecbo.ora files with any necessary changes. You may also need to update initialization parameters involving the db_name, control_files, and directory structures.
Comment out the parameters undo_tablespace and undo_management in the initialization parameter file of the target database instance. Add these parameters after the adcrdb.sql script has been run. Ignore the initialization parameters that pertain to the native compilation of PL/SQL code.
Create the target database instance Copy the adcrdb.sql script, generated in Section 1, from the source administration server node to the target database server node. Then update the script on the target database server node with any necessary changes to the directory structures for the log file(s), data file(s), or tablespaces, reflecting the layout of the target database server node.
If the target database server node is running Windows, update the directory structure from UNIX/Linux format to Windows format.
Make sure that the environment of your session on the target database server node is set up properly for the target database instance, especially the ORACLE_HOME, ORACLE_SID, and ORA_NLS10 environment settings. (ORACLE_SID must be set to the same value as the db_name parameter in the init.ora file.)
Then, use the following commands to run adcrdb.sql and create the target database instance:
$ sqlplus /nologSQL> connect / as sysdba;
SQL> spool adcrdb.log;
For UNIX or Linux:
SQL> startup nomount;
SQL> @adcrdb.sql
SQL> exit;
Add the parameters undo_tablespace and undo_management to the initialization parameter file
If PL/SQL of the source database was natively compiled, see the "Compiling PL/SQL Code for Native Execution" section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference 10g Release 2 (10.2)for instructions on how to natively compile PL/SQL in the target database. Add the parameters that pertain to the native compilation where specified. Do not use the natively compiled code generated by the source database. Oracle does not support switching the PL/SQL compilation mode from interpreted to native (and vice-versa) for an export/import. Exporting/importing using native mode takes significantly more time than interpreted mode.
When the target database instance has been created, restart the database instance.
Copy database preparation scripts to target Oracle home The database preparation scripts that you applied to the source administration server node in Section 1 contain four scripts that are needed on the target database server node.
Copy the following files from the $APPL_TOP/admin directory of the source administration server node to the Oracle 10g $ORACLE_HOME/appsutil/admin directory of the target database server node: addb1020.sql, adsy1020.sql, adjv1020.sql, and admsc1020.sql (UNIX or Linux) or addb1020_nt.sql, adsy1020_nt.sql, adjv1020_nt.sql, and admsc1020_nt.sql (Windows).
As you run each of the next four steps, note the following:
The remarks section at the beginning of each script contains additional information.
Each script creates a log file in the current directory
Set up the SYS schema
The addb1020.sql or addb1020_nt.sql script sets up the SYS schema for use with the Applications.
On the target database server node, use SQL*Plus to connect to the target database instance as SYSDBA and run $ORACLE_HOME/appsutil/admin/addb1020.sql (UNIX/Linux) or addb1020_nt.sql (Windows).
Here is an example on UNIX or Linux:
$ sqlplus "/ as sysdba" @$ORACLE_HOME/appsutil/admin/addb1020.sql
Set up the SYSTEM schema
The adsy1020.sql or adsy1020_nt.sql script sets up the SYSTEM schema for use with the Applications. On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/adsy1020.sql (UNIX/Linux) or adsy1020_nt.sql (Windows).
Here is an example on UNIX or Linux:
The adjv1020.sql or adjv1020_nt.sql script installs the Java Virtual Machine (JVM) in the database.
On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/adjv1020.sql (UNIX/Linux) or adjv1020_nt.sql (Windows).
Here is an example on UNIX or Linux:
$ sqlplus system/\ @$ORACLE_HOME/appsutil/admin/adjv1020.sql
Note: This script can be run only once in a given database instance, because the scripts that it calls are not rerunnable.
Install other required components
The admsc1020.sql or admsc1020_nt.sql script installs the following required components in the database: ORD, Spatial, XDB, OLAP, Data Mining, interMedia, and ConText.
On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/admsc1020.sql (UNIX/Linux) or admsc1020_nt.sql (Windows).
You must pass the following arguments to the script, in the order specified:
Argument
Value
remove context?
FALSE
SYSAUX tablespace
SYSAUX
temporary tablespace
TEMP
Here is an example on UNIX or Linux: ·
$ sqlplus system/\ @$ORACLE_HOME/appsutil/admin/admsc1020.sql FALSE SYSAUX TEMP
Note: All of the components are created in the SYSAUX tablespace regardless of where it was installed in the source database.
· Runs adpostcrdb.sql script Copy the adpostcrdb.sql script, generated in Section 1, from the source administration server node to the target database server node. On the target database server node, use SQL*Plus to connect to the database instance as SYSTEM and run the following command.
$ sqlplus system/@adpostcrdb.sql
· Disable automatic gathering of statistics Copy $APPL_TOP/admin/adstats.sql from the administration server node to the target database server node. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode and run adstats.sql:
$ sqlplus "/ as sysdba"
SQL> shutdown normal;
SQL> startup restrict;
SQL> @adstats.sql
SQL> exit;
· Back up the target database instance
The target database instance is now prepared for an import of the Applications data.
You should perform a backup before starting the import.
Section 3: Export the source Applications Release 11i database instance This section describes how to ensure that you have the required patches, create your export file, and capture important information that is required to import your database. · Create the export parameter file A template for the export parameter file has been included as part of the export/import patch 4872830. Copy $AU_TOP/patch/115/import/auexpdp.dat from the source administration server node to the directory on the database server node where the export dump files are to be created.
Use a text editor to modify the file to reflect the source environment and other customized parameters.
The customizable parameters are:
Parameter
Description
Template Value
directory
directory where the export dump files will be created
dmpdir
dumpfile
export dump file name(s)
aexp%U.dmp
filesize
export dump file size
1GB
log
log file name
expdpapps.log
Note : InterMedia, OLAP, and Data Mining schemas are not exported.
The admsc1020.sql script creates these schemas in the target database.
Ensure that the schema names in the exclude parameters reflect those in your database.
For Windows platforms, add the following line to the parameter file: exclude=table_statistics
Create a directory in the system schema that corresponds to the directory specified in the template.
Here is an example of how to create a directory named dmpdir:
$ sqlplus system/
SQL> create directory dmpdir as '/u01/expimp';
Comment out or remove the transform parameter. It is used only for the import process. Do not change the other parameters.
The export process uses as many of the listed file names as necessary to hold the exported data. You must ensure that the number of dump files specified, as well as the size of each dump file, is sufficient to contain all the data in your source database instance.
· Shut down Applications server processes
Shut down all Applications server processes except the database and the Net8 listener for the database. Users cannot use the Applications until the import is completed.
· Export the Applications database instance
Start an export session on the source database server node using the customized export parameter file.
Use the following command:
$ expdp system/parfile=
Typically, the export runs for several hours.
Section 4: Import the Applications Release 11i database instance This section describes how to use the import utility to load the Oracle Applications data into the target database.
1. Create the import parameter file
Copy the export parameter file you created in Section 1 from the source database server node to the target database server node, renaming it if necessary.
Updating the new file with the following changes converts it to an import parameter file:
o Remove the exclude parameters.
o Remove the filesize parameter.
o Change the name of the log file.
o Uncomment the transform parameter.
Create a directory in the system schema with the name set to the directory specified in the template and the path set to where the export dump files will reside. Here is an example of how to create a directory named dmpdir:
$ sqlplus system/ SQL> create directory dmpdir as '/u01/expimp';
Save the changed file.
· Copy the export dump files
Copy the export dump files from the source database server node to the target database server node.
Import the Applications database instance Start the import session on the target database server node using the customized import parameter file. Use the following command:
$ impdp system/parfile=
Typically, import runs for several hours. Once the import is complete, you can delete the export dump files, as well as the export and import parameter files, from the source and target database server nodes
Section 5: Update the imported Applications Release 11i database instance
This section describes how to recreate the database objects and relationships that are not handled by the export and import utilities.
Reset Advanced Queues
Copy the auque2.sql script that was generated in Section 1 from the $ORACLE_HOME/appsutil/admin directory of the source database server node to the same directory on the target database server node.
Then, on the target database server node, as the owner of the Oracle 10g file system and database instance, use SQL*Plus to connect to the target database as SYSDBA and run the $ORACLE_HOME/appsutil/admin/auque2.sql script to enable the Advanced Queue settings that were lost during the export/import process.
The script creates a log file in the current directory.
$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> @$ORACLE_HOME/appsutil/admin/auque2.sql
· Perform post-import steps outlined in the Interoperability documents
· Create OWA_MATCH package (conditional) (Not Applicable)
If you are using iAS 1.0.2, perform the steps in document 312165.1to create SYS.OWA_MATCH on the target database.
· Compile invalid objects
On the target database server node, as the owner of the Oracle 10g file system and database instance, use SQL*Plus to connect to the target database as SYS and run the $ORACLE_HOME/rdbms/admin/utlrp.sql script to compile invalid objects. ·
$ sqlplus sys/@$ORACLE_HOME/rdbms/admin/utlrp.sql
First, complete the applications porting so that DB can be made Autoconfig enabled.
Enable autoconfig on the target system database
Section 7: Migrating to AutoConfig on the Database Tier
Complete the steps in this section (in the order listed) to migrate to AutoConfig on the Database Tier. If you have already migrated to AutoConfig on the Database Tier omit this section.
1. Copy AutoConfig to the RDBMS ORACLE_HOME Update the RDBMS ORACLE_HOME file system with the AutoConfig files by performing the following steps:
o On the Application Tier (as the APPLMGR user):
1 Log in to the APPL_TOP environment (source the environment file)
2 Create appsutil.zip file perl /bin/admkappsutil.pl
3 This will create appsutil.zip in $APPL_TOP/admin/out .
o On the Database Tier (as the ORACLE user):
$ Copy or FTP the appsutil.zip file to the $ cd unzip -o appsutil.zip
2. Generate your Database Context FileIf your Applications system was created with the Release 11.5.9 Rapid Install or later, go to Task 3 in this section.
If your Applications system was created with the Release 11.5.8 Rapid Install or earlier, execute the following commands to create your Database Context File:
o On UNIX
$ cd $ . .env
$ cd /appsutil/bin
$ perl adbldxml.pl tier=db appsuser=appspasswd=
Prepare for AutoConfig Complete the following AutoConfig steps.
Review Prior Manual Configuration Changes
The Database Context File may not include manual post-install configuration changes made after the Rapid Install completed. Before running the AutoConfig portion of this patch, review any modifications to specific configuration files and reconcile them with the Database Context file
1. The AutoConfig check utility is located at:
Tier Command Application /bin
Database /appsutil/bin
2. Check the AutoConfig configuration files by executing the following command:
o On UNIX
adchkcfg.sh contextfile=appspass=
1. Generate and Apply AutoConfig Configuration files
Attention: This step performs the conversion to AutoConfig. Once completed, the previous configuration will not be available.
2. Attention: The database server and the database listener must remain available during the AutoConfig run. All the other database tier services should be shut down.
3. Execute the following commands:
On UNIX
$ cd /appsutil/bin/
$ adconfig.sh contextfile=appspass=
Noe the database is autoconfig enabled.
· Create ConText and Spatial objects ( to be followed after db is Auto config enabled)
Certain ConText and Spatial objects are not preserved by the import process. The consolidated export/import utility patch 4872830 that you applied to the source administration server node in Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch driver file. You use this driver file to call the scripts that create these objects.
Run the following command: ·
$ perl $AU_TOP/patch/115/driver/dpost_imp.pl
Once the driver file has been generated, use AutoPatch to apply it on the target administration server node.
· Maintain Applications database objects
Run AD Administration on the target administration server node.
From the Maintain Applications Database Objects menu, perform the following tasks:
o Compile flexfield data in AOL tables
o Recreate grants and synonyms for APPS schema
If you use Multiple Reporting Currencies:
o Maintain Multiple Reporting Currencies schemaEnter Yes for the following options:
§ Update MRC schema itself
§ Compile invalid objects after updating MRC schema objects
§ Recreate MRC triggers in the APPS schema
· Start Applications server processes
Start all the server processes on the target Applications system. You can allow users to access the system at this time.
· Create DQM indexes Create DQM indexes by following these steps:
o Log on to Oracle Applications with the "Trading Community Manager" responsibility
o Click Control > Request > Run
o Select "Single Request" option
o Enter "DQM Staging Program" name
o Enter the following parameters:
§ Number of Parallel Staging Workers: 4
§ Staging Command: CREATE_INDEXES
§ Continue Previous Execution: NO
§ Index Creation: SERIAL
o Click "Submit"
· Gather Applications statistics
If you encountered failures importing statistics or if your platform is Windows, gather the statistics by following these steps:
o Ensure that there are no concurrent programs running.
o Log on to Oracle Applications with the "System Administrator" responsibility.
o Click Navigation List > Request > Run.
o Enter appropriate parameters. Specify "ALL" in the schema name to gather statistics for all database objects. You may choose individual schemas to make the process run faster.
o Click "Submit".
Now the database should be on the target operating system.
In the next post I will write how to convert the source application tier to the target application tier.
Red Hat Certified Engineer (RHCE) is a performance-based test that measures actual competency on live systems. Called the "crown jewel of Linux certifications," RHCE proves an individual's ability to configure networking services and security on servers running a Red Hat OS. RHCE was recently named the hottest certification in all of IT by CertCities.com.
The RHCE Exam
Becoming a Red Hat Certified Engineer requires passing a 3.5 hour hands-on exam. There are four different approaches to preparing for the exam depending on your existing level of Linux expertise.
Q: How to delete files older than N number of days ? (Useful in delete log, trace, tmp file )
find . -name ‘*.*’ -mtime +[N in days] -exec rm {} \; ( This command will delete files older then N days in that directory, always good to use it when you are in applcsf/ tmp,out,log directory)
Q: How to list files modified in last N days
find . -mtime - -exec ls -lt {} \;
So to find files modified in last 3 days
find . -mtime -3 -exec ls -lt {} \;
Q: How to sort files based on Size of file ? ( useful to find large files in log directory to delete in case disk is full )
ls -l | sort -nrk 5 | more
Q: How to find files changed in last N days (Solaris)
find -mtime -N -print
Q: How to extract cpio file
cpio -idmv < file_name (Don’t forget to use sign < before file name)
Q: How to find CPU & Memory detail of linux
cat /proc/cpuinfo (CPU)
cat /proc/meminfo (Memory)
Q: How to find if Operating system in 32 bit or 64 bit ?
For solaris use command
isainfo -v
If you see out put like
32-bit sparc applications
That means your O.S. is only 32 bit
but if you see output like
64-bit sparcv9 applications
32-bit sparc applications
above means your o.s. is 64 bit & can support both 32 & 64 bit applications
Q: How to find if any service is listening on particular port or not ?
netstat -an | grep {port no}
For example if you know that OID is running on 389 port so to check if OID services is listening or not then use
netstat -an | grep 389
Q: How to find Process ID (PID) associated with any port ?
This command is useful if any service is running on a particular port (389, 1521..) and that is run away process which you wish to terminate using kill command
lsof | grep {port no.} (lsof should be installed and in path)
Q: How to change a particular pattern in a file ?
Open file using vi or any other editor, go in escape mode (by pressing escape) and use
:1,$s/old_pattern/new_parameter/gc ( g will change globally, c will ask for confirmation before changing )
Q: How to find a pattern in some file in a directory ?
grep pattern file_name ( to find pattern in particular file )
grep pattern * ( in all files in that directory )
If you know how to find a pattern in files in that directory recursively please answer that as comment
Q: How to create symbolic link to a file ?
ln -s pointing_to symbolic_name
e.g. If you want to create symbolic link from a -> b
ln -s b a
(Condition:you should have file b in that directory & there should not be any file with name a)
Q: How to setup cronjob (cronjob is used to schedule job in Unix at O.s. Level )
crontab -l( list current jobs in cron)
crontab -e ( edit current jobs in cron)
_1_ _2_ _3_ _4_ _5_ executable_or_job
Where
1 - Minutes (0-59)
2 - Hours ( 0-24)
3 - day of month ( 1- 31 )
4 - Month ( 1-12)
5 - A day of week ( 0- 6 ) 0 -> sunday 1-> monday
e.g. 0 3 * * 6 Means run job at 3AM every saturday
This is useful for scheduling ftp, rman backup or removed old log files regularly.
Oracle 11g New Features for Database Administrators (DBA)
1.Installation, Database Upgrades and Change Management
• Installation New Features Support
• Role and Privilege Changes
• Deprecated Components
• New Initialization Parameters Affecting Database Creation
• DBCA Enhancements
• Upgrading to Oracle Database 11g
• Database Replay
• The SQL Performance Analyzer
• Patching in Oracle Database Control
2.Database Diagnosis and Repair
• Introducing Automatic Diagnostic Repository (ADR)
• Configuring the ADR
• Using adrci Tool
• Using The Support Workbench in the OEM
• Database Health Monitor
• Data Recovery Advisor
• SQL Test Case Builder
• Data Block Corruption Parameters
3.Database Administration
• Automatic Memory Management
• Automatic Maintenance Tasks
• Oracle Flashback-Related New Features
• Flashback Data Archive
• Oracle Flashback Transaction Backout
• Virtual Columns
• New Data Partitioning Schemes
• DDL Lock Timeout
• Explicit Locking of Tables
• Invisible Indexes
• Read-Only Tables
• Shrinking Temporary Tablespaces and Tempfiles
• Creating an Initialization Parameter File from Memory
• Restore Point Enhancements
• Database Resident Connection Pooling
• Comparing and Synchronizing Database Objects
• SQL*Plus New Features
• Online Application Maintenance
• Oracle Advanced Compression Option
• Oracle Scheduler New Features
• Lightweight Jobs
• Remote External Jobs
• Finer-grained Dependency Management
• Enhancements in Oracle Database Resource Manager
4.Performance Tuning
• PL/SQL Native Compilation
• Server Result Cache
• Client Side Result Cache
• Enhanced Oracle Process Monitoring
• Subprogram Inlining
• SQL Tuning Automation
• SQL Access Advisor Enhancements
• Changing Statistics Preferences
• Enhanced Statistics Maintenance
• SQL Plan Management
• ADDM New Features
• AWR New Features
• Setting Metric Thresholds for Baselines
• Performance-Related Changes in Database Control
• Miscellaneous New Performance Tuning Features
• Real-Time SQL Monitoring
5.Database Security
• Stronger Password Hash Algorithm
• Security Out of the Box
• Anti Network Attacks Parameters
• Tablespace Encryption
• Fine-Grained Access Control for UTL* Packages
• Further Security New Features
6.Backup and Recovery New Features
• Enhanced Block Media Recovery
• RMAN Substitution Variables
• New RMAN Configuration Parameters
• The Multisection Backups
• Creating Archival Backups
• VALIDATE Command
• Configuring an Archived Redo Log Deletion Policy
• Active Database Duplication
• Importing and Moving Recovery Catalogs
• Virtual Private Catalogs
• Miscellaneous New Features in RMAN
7.Data Pump Utilities
• Compression Enhancement
• Encryption Enhancements
• Reusing a Dump File
• Remapping Data
• Renaming Tables During Export or Import
• Data Pump and Partitioned Tables
• Ignoring Nondeferred Constraints
• External Tables Based on Data Pump Driver
• Enhancement in the Transportable Parameter
8.Automatic Storage Management (ASM)
• SYSASM Privilege and OSASM Group
• Upgrading ASM using DBUA
• Upgrading ASM Manually
• ASM Restricted Mode
• Diskgroup Attributes
• Checking Diskgroup
• asmcmd Utility Commands
• Fast Rebalance
• Miscellaneous ASM New Features
9.PL/SQL New Features
• PL/SQL New Features
10.Data Warehousing
• SecureFiles
• Accessing a LOB Using SQL and PL/SQL
• Online Redefinition
• Partition Change Tracking (PCT)
• PIVOT Operator Enhancements
• Partitioning Improvements
“Oracle Applications DBA” BY Joyjeet
I am delighted to inform you all that my book “Oracle Applications DBA covering 11i and R12″ publisher Mc Graw Hills now got released worldwide and now is available at amazon.
The book “Oracle Applications DBA” covers all the pertinent aspects of administrating Oracle Applications—from installation to day-to-day maintenance. It covers upgrading, cloning, patching, maintenance and troubleshooting of the application system. Embellished with over 350 screenshots and illustrations, it helps in administrating complex Oracle Database in an easy-to-navigate format. To help readers manage Oracle Applications without much difficulty, a comprehensive discussion on upgrading Oracle Applications in Unix environment has been provided. Further the book includes a balanced coverage of Oracle 11i and R12 – making it a must-have for experienced Oracle Applications DBAs. Professionals who are keen to migrate from DBA to Apps DBA profile would also find the book useful. This is the only book available in the market which contains everything about R12.
Amazon Link
http://www.amazon.com/Oracle-Applications-DBA-Covers-11i/dp/0070077290/ref=sr_1_1?ie=UTF8&s=books&qid=1218777553&sr=8-1
For Oracle Apps DBA training; apart from basics look for at least Installation, Patching and Cloning.
**********************
Oracle University
**********************
http://education.oracle.com/ check for course "D17423GC51 11i Install, Patch, and Maintain Oracle Applications"
Institutes mentioned here are in alphabetical Order and I don't personally recommend any training Institute.
************
Bangalore
***********
Human Base India Inc.
Software Development Centre
Royal ArcadeNo.6, 4th Floor,
80 Ft RoadKoramangala, Industrial Layout
Bangalore – 560 095
Tel: 91- 80-25531221, 25532440, 25535429e-
MailFor sreeni@humanbaseindia.com
Q-Soft Systems & Solutions (P) Ltd.
#253/19, 1st & 2nd Floor,
Kanakapura Road,
Jayanagar 7th Block,
Bangalore-560082
Tel : +91 80 26639207, 26544135
Fax : +91 80 26637692
URL : http://www.qsoftindia.com/
E-Mail : shrivardhan@qsoftindia.com
************
Chennai
***********
Crest Of Technolgies
No. 64, A.R.R. Complex,
North Usman Road, T.Nagar,
Chennai - 600017.
Ph : +91 44 55634550, 55634551
URL http://www.crestsofttechnologies.com/
Ikon Infotech
II Avenue, II Floor,
Near Blue Star Signal Annanagar,
Chennai - 40
Ph : +91 44 26214127 , 42611909
Ora Solution
10th Main Road II Avenue,Annanagar,
Chennai - 600 040
Ph : +91 44 42612461 , 9841148256
