Session ID:
Prepared by:
Remember to complete your evaluation for this session within the app!
10156Anatomy of an EBS
Platform Migration
26 April, 2018
James Morrow
Sr. E-Business Suite DBA
Viscosity NA
@kansasdba
James Morrow
• Oracle Applications DBA
• Viscosity NA
• 22+ years as an E-Business Suite DBA
• 24+ years as a Unix/Linux Administrator
• E-Business Suite versions 9.4.2 through R12.2.7
• Oracle RDBMS 7.0.16 through 12.1.0.1
PerformanceHealth ChecksHow’s it running?
CUSTOMApplication Development
DBA ServicesRemote and On-site
On-Call Support
ManagedServices
ZERO DOWNTIME
Migrations
ProfessionalServicesWhere you need it most
Staff Aug Workforce Capacity on Demand
Oracle License ManagementGet the most out of your Oracle investment
Collaborate 2017 Booth #1208
Release Information
and Support
Timelines
E-Business Suite Releases(April, 2017)
Support Timelines(April, 2017)
Database Patch Set Release Roadmap [MOS 742060.1] (April, 2017)
Database Support Changes (12.1)
Database 12.1
Premier Support through July 31, 2018
Extended Support through July 31, 2021
Extended Support Fee Waived through July 31, 2019
SOURCE: E-Business Suite Technology Blog, February 8, 2017
https://blogs.oracle.com/stevenChan/entry/db121_extfee
https://blogs.oracle.com/stevenChan/entry/db121_extfee
Database Support Changes (11.2)
Database 11.2
Premier Support expired July, 2015
Extended Support through December 31, 2020
Extended Support Fee Waived through December 31, 2018
SOURCE: E-Business Suite Technology Blog, February 7, 2017
https://blogs.oracle.com/stevenChan/entry/db112_extfee
Planning Your
Migration Project
Planning: Decisions
Will you be doing a database upgrade at the same time?
Will you be doing an E-Business Suite upgrade as well?
What method will you be using for database migration?
11
Planning: Master Note
• MOS 1377213.1 Oracle E-Business Suite Upgrades and Platform Migration
12
Database Migration
Decisions
Database Migration Decisions
Upgrade during separate outage window
PRO
• Smaller individual outages
• One less thing to do during EBS migration or upgrade
CON
• Target database version might not be available on current platform/OS version
• Requires separate testing effort
14
Database Migration Decisions
Upgrade during migration effort? (“Big Bang”)
PRO
• Only requires one testing effort
• Source system not impacted
CON
• Longer individual outage
15
Database Migration Decisions
What migration method should we use
• Copy datafiles
• Transportable Database
• Cross Platform Transportable Tablespaces
• DataPump Export/Import
• Traditional Export/Import
16
Database Migration Decisions
Copy Datafiles
PRO
• Simple
CON
• Not really a valid choice for any real platform migrations
17
Database Migration Decisions
Transportable Database
PRO
• Relatively Simple
• Fast
CON
• Only for 10.2.0 and newer
• Source and target must be same version
• Source and target must have same ENDIAN format (MOS 733205.1)
18
Database Migration Decisions
Cross Platform Transportable Tablespaces
PRO
• Relatively simple
• Fast
• Can convert ENDIAN formats
CON
• Source and target must be same version
• Source and target must have same character set
• TDE is not supported
19
Database Migration Decisions
DataPump Export/Import
PRO
• Faster than exp/imp
• Parallel
• Database Re-org
• Use as part of DB upgrade
• Works between all platforms
CON
• Not available for < 10g
• Slower than most other methods
20
Database Migration Decisions
Traditional Export/Import
PRO
Available for ALL DB versions
Database Re-org
Use as part of DB upgrade
Works between all platforms
CON
Slowest available method
Might not be supported
21
Perform Database
Platform Migration
dbTier Approach 1:
Transportable
Database
dbTier Approach 1: Transportable Database
MOS 2011169.1 EBS R12.2 with RDBMS 11gR2 or 12cR1
MOS 734763.1 EBS R12.0 and R12.1 with RDBMS 10gR2, 11g, or 12cR1
MOS 729309.1 EBS R11i with RDBMS 10gR2 or 11g
24
dbTier Approach 1: Transportable Database
• Prepare SOURCE
– Check prerequisites and external objects
• Verify TDB support:
– select platform_name from v$db_transportable_platform;
– Identify External Directories & Tables files
– Identify BFILE files
25
dbTier Approach 1: Transportable Database
• Prepare TARGET
– Prepare Target Operating System
– Install RDBMS Software & Patches
• must be same versions as on source
• Follow the appropriate “EBS Interoperability Notes” for your versions
– Pre-create any directories for external tables or BFILEs
26
dbTier Approach 1: Transportable Database
• On the SOURCE
– Upgrade AutoConfig
– Shutdown appsTier
– Convert datafiles to the new platform
• Export OLAP workspaces
• Database in READ ONLY mode
27
dbTier Approach 1: Transportable Database
• SOURCE SYSTEM CONVERSION
– RMAN CONVERT DATABASE TO PLATFORM
• Creates transport script, PFILE, and a copy of datafiles in target format
– Transfer files to target (or use NFS to avoid this step)
28
dbTier Approach 1: Transportable Database
• TARGET SYSTEM CONVERSION
– RMAN CONVERT DATABASE ON TARGET PLATFORM
– Creates a script to convert all datafiles.
– Also creates a transport script and a PFILE.
29
dbTier Approach 1: Transportable Database
• After Conversion
– Deploy PFILE, Transport SQL script, External Table files, BFILE files
– Review and edit PFILE
– If you did a SOURCE system conversion
• Also deploy STAGE files to their final location (If NFS was used, you could have converted them directly to their new home)
– If you did a TARGET system conversion
• Also deploy uncoverted data files into TARGET staging area
• Run RMAN Convert script
– Run Transport SQL script
– Import OLAP workspaces
– Cleanup FND_NODES
– Implement & run AutoConfig
30
dbTier Approach 2:
Cross Platform
Transportable
Tablespaces
dbTier Approach 2: Transportable
Tablespaces
MOS 2157661.1 E-Business Suite R12.2 with RDBMS 12cR1
MOS 1945814.1 EBS R12.0 or R12.1 with RDBMS 12cR1
MOS 1311487.1 EBS R12.0 or R12.1 with RDBMS 11gR2
MOS 1366265.1 EBS R11i with RDBMS 11gR2
MOS 454574.1 EBS R11i with RDBMS 10gR2
32
dbTier Approach 2: Transportable
Tablespaces
• Prepare SOURCE
– Upgrade AutoConfig to latest version
– Apply any required patches
– Create DataPump working directory
– Create TRANSPORT_SET_VIOLATIONS table
– Run auxttspre.sql
• Adjust tablespace/datafile count/sizes in aucrdb.sql
– Record AQ Settings
– Turn off Spatial Index Rebuild
– Synchronize Text Indexes
33
dbTier Approach 2: Transportable
Tablespaces
• Prepare TARGET
– Prepare OS
– Install RDBMS software (Check EBS Interop note for your platform/versions)
– Confirm Time Zone patches (source/target must be the same)
– Create init.ora
– Create DataPump working directory
– Create empty Target Database using generated scripts (adjust
tablespaces/datafiles)
– Run any patch post-install steps (12c)
– Disable autostats
34
dbTier Approach 2: Transportable
Tablespaces
• Export SOURCE database
– Perform cross platform incremental backup (MOS 1389592.1)
– Modify any export parameter files (directory, dumpfile, filesize, logfile, etc.)
– Shutdown appsTiers
– Disable Database Vault (conditional)
– Various purges/Backups/Minor exports
• Purge unused columns, recycle bin
• Backup AZ table data (conditional)
• Export OLAP workspaces (conditional)
• Drop XLA packages (conditional)
• Convert database callout to data
• Remove MGDSYS schema (conditional)
35
dbTier Approach 2: Transportable
Tablespaces
• Export SOURCE database (continued)
– Mark tablespaces READ-ONLY
– Export transportable tablespaces
– Export SYSTEM tablespace schemas
– Export global temporary tables
– Export miscellaneous data
– Export tables with XML type columns (conditional)
– Copy dump files/datafiles to TARGET
– Shutdown SOURCE
• There are additional steps that can be taken if you want to re-open source in the MOS
note.
36
dbTier Approach 2: Transportable
Tablespaces
• Import on TARGET
– Setup/Edit import parameter files
– Create DataPump working directory
– Convert endian format of datafiles (rman aurman.dat) (conditional)
– Import miscellaneous data (conditional)
– Import transportable tablespace set (impdp)
– Import OLAP workspaces
– Reset Advanced Queues
– Start listener
37
dbTier Approach 2: Transportable
Tablespaces
• Import on TARGET (continued)
– Run adgrants, adctxprv.sql,
– Gather SYS stats
– Cleanup FND_NODES
– Implement & Run AutoConfig
– Fix broken database links (conditional)
– Create ConText objects
– Populate CTXSYS.DR$SQE
– Create DQM indexes
38
dbTier Approach 3:
Export/Import
dbTier Approach 3: Export/Import
MOS 1926203.1 EBS R12.2 with RDBMS 12cR1
MOS 1613716.1 EBS R12.2 with RDBMS 11gR2
MOS 1585256.1 EBS R12.0 or R12.1 with RDBMS 12cR1
MOS 741818.1 EBS R12.0 or R12.1 with RDBMS 11gR2
MOS 454616.1 EBS R12 with RDBMS 11gR2
MOS 1585257.1 EBS 11i with RDBMS 12cR1
MOS 557738.1 EBS 11i with RDBMS 11gR1/11gR2
MOS 362205.1 EBS 11i with RDBMS 10gR2
dbTier Approach 3: Export/Import
• Prepare SOURCE Database
– Apply any prerequisite patches
– Apply any consolidated export/import patch
– Run auclondb.sql to generate database create script
– Run auque1.sql to record advanced queue settings
– Remove rebuild index parameter in special indexes
– Synchronize text indexes
– Details may vary slightly depending on versions involved
dbTier Approach 3: Export/Import
• Prepare TARGET
– Prepare Target Operating System
– Install Target Database Software (upgrade?)
• Pay attention to appropriate MOS interoperability notes for your target platform/versions
– Patch Target Software
– Apply latest CPU/PSU Patches
– E-Business Suite Recommended Patches
– Create target init.ora files
– Create empty database to receive your import (using aucrdb.sql created on source and other scripts provided)
• Be sure to address any space/sizing changes you want to make (number/size of datafiles, move to ASM or Oracle Managed Files)
– Details may vary slightly depending on versions involved
dbTier Approach 3: Export/Import
• Export the SOURCE Database
– Same basic approach for DataPump or for Traditional Export/Import
– Parrallelism only as good as the longest thread (usually APPS schema objects)
• Copy/Transport the *.dmp files to TARGET
– Export/Import may not like NFS
– Parallel SCP
– If doing traditional exp/imp, can start copy as soon as exp is done writing a file (but
not with expdp/impdp)
– Unmount volume from SOURCE, mount on TARGET
dbTier Approach 3: Export/Import
• Import into the TARGET database
– Same basic approach for DataPump or for Traditional Export/Import
– Parrallelism only as good as the longest thread (usually APPS schema objects)
dbTier Approach 3: Export/Import
• Implement AutoConfig
– Implement/Run AutoConfig on your dbTier
• Run AutoConfig on appsTier
– If you’re not migrating that as well
– Make appropriate changes to appsTier context files
– Both RUN & PATCH filesystems for R12.2
Migrate the
E-Business Suite
appsTier
Migrate EBS appsTier
MOS 2048954.1 E-Business Suite R12.2
MOS 438086.1 E-Business Suite R12.0 and R12.1
MOS 238276.1 E-Business Suite R11i
47
appsTier Migration
• The hard way (NOT SUPPORTED)
– Fresh install (including database) on target platform
– Re-apply copy driver of EVERY appsTier patch applied since last major upgrade
– Bring over customizations
– Delete fresh install database and replace with your own
– Apply any post-migration fixes
– Cross your fingers
48
E-Business Suite
R12.2
appsTier Migration (R12.2)
• The CORRECT way (SOURCE)
– ONLY for R12.2.3 or later
– Ensure that there are no active patching cycles
– As always, run ETCC
– Upgrade to FMW 11.1.1.7
– Apply latest AD patch to SOURCE
– Confirm appropriate patches are applied to SOURCE
– Run adpreclone.pl on SOURCE
– Maintain Snapshot Information
– Identify TechStack Patches/Versions
– Generate Manifest (adgenpsf.pl) and upload to:
• https://updates.oracle.com/PlatformMigration
50
https://updates.oracle.com/PlatformMigration
appsTier Migration (R12.2)
• The CORRECT way (TARGET)– Create TARGET applTop
• Copy from SOURCE (specific directories vary by version)
• Generate the TARGET Context File (for RUN & PATCH)
– Install appsTier Technology Stack• buildstage.sh/rapidwiz –techstack
– Run AutoConfig setup phase
– Run txkPlatformMigrationTasks.pl
– Download & Apply the Patch generated by your manifest• Contains platform specific files
– Regenerate filesystem objects
– Clean up nodes (afcpclean.sh)
– Run AutoConfig
– Regenerate filesystem objects (adgensgn.sh)
– Adadmin & Apply post-migration fixes
– AutoConfig on RUN filesystem
– Run AutoConfig on PATCH filesystem (-syncctx)
51
E-Business Suite 11i,
R12.0, R12.1
appsTier Migration (11i, R12.0, R12.1)
• The CORRECT way (SOURCE)
– Apply latest AD patch to SOURCE
– Implement AutoConfig (11i)
– Confirm appropriate patches are applied to SOURCE
– Run adpreclone.pl on SOURCE
– Maintain Snapshot Information
– Identify TechStack Patches/Versions
– Generate Manifest (adgenpsf.pl) and upload to:
• https://updates.oracle.com/PlatformMigration
53
https://updates.oracle.com/PlatformMigration
appsTier Migration (11i, R12.0, R12.1)
• The CORRECT way (TARGET)
– Create TARGET applTop
• Copy from SOURCE (specific directories vary by version)
• Clone the Context File from SOURCE to TARGET
– Install appsTier Technology Stack
• rapidwiz -techstack (11i, R12.0, R12.1)
– Run AutoConfig setup phase
– Download & Apply the Patch generated by your manifest
• Contains platform specific files
– Regenerate filesystem objects
– Run AutoConfig
– Adadmin & Apply post-migration fixes
54
Session ID:
Remember to complete your evaluation for this session within the app!
10156
