Steps to import data from 11g to 9i database

Steps to import data from 11g to 9i database


In 11g database Change the definition of view EXU9DEFPSWITCHES from:

CREATE OR REPLACE VIEW exu9defpswitches (
compflgs, nlslensem ) AS
SELECT a.value, b.value
FROM sys.v$parameter a, sys.v$parameter b
WHERE a.name = 'plsql_compiler_flags' AND
b.name = 'nls_length_semantics'

to

CREATE OR REPLACE VIEW exu9defpswitches (
compflgs, nlslensem ) AS
SELECT a.value, b.value
FROM sys.v$parameter a, sys.v$parameter b
WHERE a.name = 'plsql_code_type' AND
b.name = 'nls_length_semantics'

(see new parameter PLSQL_CODE_TYPE)

This need to be change because of following issue.
Export From 11g using EXP Utility Version 9iR2 Produces Corrupt Export Dump [ID 550740.1]

1- Go to 9i database server

2- Add the tns entry fro 11g database

(Export from 11.1.0.7 using export utility of 9.2.0.6)

( To minimize the number of conversation set NLS_LANG during export to the same as character set of the exported database. In this case WE8ISO8859P1.This means no conversation takes place, all data is stored in export file as it was stored in the database)

3- export NLS_LANG=american_america.WE8ISO8859P1

4- Take the export of 11g database from this server

exp system/manager@11gDB owner=scott file=test.dmp log=a.log

(Run import in 9.2.0.6 database to import the export dump created from 11.1.0.7 with 9.2.0.6 export)

5- export ORACLE_SID of 9i database

6- export NLS_LANG=american_america.WE8ISO8859P1

7- Now import the export of 11g database data which is taken from 9i export utility

imp system/manage fromuser=scott touser=new file=test.dmp log=b.log

Business Continuity for EBS Using Oracle 11g Physical Standby DB

Our Applications Technology Group database architects have released two new documents covering the use of Oracle Data Guard to create physical standby databases for Oracle E-Business Suite environments:

• Business Continuity for Oracle E-Business Release 12 Using Oracle 11g Physical Standby Database (Note 1070033.1)
• Business Continuity for Oracle E-Business Release 11i Using Oracle 11g Physical Standby Database (Note 1068913.1)

What is a Standby Database?

A standby database is a transactionally-consistent copy of the primary database. Using a backup copy of the primary database, you can create up to thirty standby databases and incorporate them in Data Guard configuration.

There are three types of standby databases:

Physical Standby
Provides a physically identical copy of the primary database, with on-disk database structures that are identical to the primary database on a block-for-block basis. The database schema, including indexes, are the same. A physical standby database is kept synchronized with the primary database by recovering the redo data received from the primary database.

Logical Standby
Contains the same logical information as the primary database, although the physical organization and structure of the data can be different. It is kept synchronized with the primary database by transforming the data in the redo logs received from the primary database into SQL statements and then executing the SQL statements on the standby database.

Snapshot Standby
A fully updatable standby database. Like a physical or logical standby database, a snapshot standby database receives and archives redo data from a primary database. Unlike a physical or logical standby database, a snapshot standby database does not apply the redo data that it receives.

These new notes detail the steps for setting up the first of these types, a Physical Standby database using Oracle Data Guard.

New EBS Roadmap documentations, too

Our Applications Technology Group database architects have also released two new roadmap documents covering the latest options for High Availability, Real Application Clusters, and Maximum Availability Architectures:

• Oracle E-Business Suite Release 11i High Availability Documentation Roadmap (Note 1072807.1)
• Oracle E-Business Suite Release 12 High Availability Documentation Roadmap (Note 1072636.1)

Oracle Apps Database Administrator (Apps DBA)

Oracle Apps DBA has almost all duties of core DBA, in addition to this following are more responsibilities
- Application fundamentals such as concepts and architecture
- Application Installation and configuration
- Patching and Upgrades
- Patch Management and Version Control
- Customization Updates
- Cloning requirements. This can be frequent in an Apps environment
- Concurrent Managers
- Forms/Report Servers
- Web Servers
- all the "ad" utilities
- all the database restrictions for the applications. That is so that the installation is still supportable and conforms to all vendor (Oracle) requirements.
- All special application related regular and maintenance functions. Such as month end and period end functions.
- Understand any backup and recovery constraints. Such as for table imports (NOT) and partial recoveries.
- special requirements and restrictions for tuning. Example optimizer and index requirements.
- Printer Configuration
- User Access Administration

You can get much more findings on this , but above are the some basic things that must be know to each Apps DBA

Oracle Application EBS.

Oracle Corporation's E-Business Suite also know as Oracle Apps or EBS consists of a collection of enterprise resource planning (ERP), customer relationship management (CRM), and supply-chain management (SCM) computer applications either developed by or acquired by Oracle.
This software uses oracle's core RDBMS technology. The EBS contains following products,

• Oracle CRM
• Oracle Financials
• Oracle HRMS
• Oracle Mobile Supply Chain Applications
• Oracle Order Management
• Oracle Procurement
• Oracle Project Portfolio Management
• Oracle Quotes
• Oracle Transportation Management
• Oracle Warehouse Management Systems
• Oracle Inventory
• Oracle Enterprise Asset Management

Each product comprises several modules, each separately licensed.