Oracle Exadata X7

Oracle Exadata X7

Oracle announced the next-generation Oracle Exadata X7 with significant hardware and software enhancements in overall performance, storage capacity, network bandwidth, and automation. The Oracle Exadata is an Engineered System designed to be the ideal platform for all database workloads.

Key Important features:

-New Exadata Smart Software : Exadata 18c
-Up to 912 CPU core and 28.5TB memory per rack
-2 to 19 DB servers per rack
-3 to 18 Storage servers per rack
-Maximum of 920TB flash capacity
-2.1PB of disk capacity
-Delivers 20% faster throughput from earlier models
-50% more memory capacity from earlier models
-10TB size disk. (10TB x 12 = 120TB RAW per storage server). The only system in the market today with 10TB disk capacity
-Increased OLTP performance : about 4.8 million reads and about 4.3 million writes per second
-Featuring an Intel Skylake processor with 24 cores
-Ethernet network bandwidth has increased by 150 percent from 10 to 25 Gigabits per second
-Delivers in-memory performance from Shared Storage
-OEDA commandline interface
-Overall, Exadata X7 database applications can realize 20 to 40 percent improvement in performance for OLTP, analytics and mixed workloads.

Exadata Configuration Files

Exadata Configuration Files

Exadata Compute node:
/opt/oracle - contains dbserver software
/opt/oracle.cellos - Contains all cell OS configuration files, image executables, and so forth
/opt/oracle.exacli - Contains exacli and exadcli executables
/opt/oracle.ExaWatcher - Contains ExaWatcher utilities and output/archive files/directories
/opt/oracle.oswatcher - Contains OSWatcher utilities and output/archive files/directories
/opt/oracle.SupportTools - Contains support and configuration files
/opt/oracle.SupportTools/onecommand - Contains OneCommand files used for Exadata install/config
/etc/oracle/cell/network-config - Contains files that enable compute servers to communicate with storage servers
/etc/oracle/cell/network-config/cellinit.ora - Contains IB IP subnet for storage cells
/etc/oracle/cell/network-config/cellip.ora - Contains IB IP addresses for each storage cell
/u01/app/oracle - Oracle Base
/u01/app/12.1.0.x/grid - Grid Infrastructure Home
/u01/app/oracle/product/12.1.0.x/db - Oracle Database Home

Storage Cells:
/opt/oracle - Contains cell software
/opt/oracle.cellos - Contains Exadata cell software and utilities
/opt/oracle.cellos/cell.conf - Contains cell configuration file
/opt/oracle.exacli - Contains exacli and exadcli executables
/opt/oracle.ExaWatcher - Contains ExaWatcher utilities and output/archive files/directories
/opt/oracle.oswatcher - Contains OSWatcher utilities and output/archive files/directories
/opt/oracle.SupportTools - Contains OneCommand files used for Exadata install/config
/var/log/oracle - Contains cell server log files, alerts, and trace files
/var/log/oracle/cellos - Contains log and trace files for Cell Services utilities and cell server startup/shutdown events
/var/log/oracle/diag/asm - Contains log and trace files for cell storage-related

What is iDB Protocol

What is iDB Protocol

iDB protocol is an intelligent DataBase protocol which is the heart of the Exadata. It is used to do communication between Database node and cell storage. It transfers data between cell storage  and Database Node. Also it's provides interconnection bandwidth aggregation and failover.

Oracle GoldenGate Processes & Status

Oracle GoldenGate Processes & Status

Manager Process
-Manager process is common for source and target datatabase.
-It is required for Stop and Start GoldenGate Extract, Pump and Replicat processes
-It will monitor the livileness of other processes within the system.
-Default port is 7809
-It is the actual process which control other sub-components.
-It makes the communication using GG user.

Status of manager process:
-Stopped
-Running

Extract Process
-This is the actual process on source side which reads the actual data.
-It reads database from online redo log files and optionally from archive log files and write data to local or remote trail files.

Status of extract process:
-Stopped
-Starting
-Running
-Abended

Pump Process
-It is optional process avaliable on source side.
-To reduce the load of extract process.
-It reads data from local trail file and writes data to remote trail over the TCP/IP network. It is an optional process but highly recommended.

Status of pump process:
-Stopped
-Starting
-Running
-Abended

Replicat Process
-This is the actual process which available on target and it is actually apply the data to the database.
-It reads data from remote trail files and write to the database one transaction at a time.

Status of replicat process:
-Stopped
-Starting
-Running
-Abended

Collector Process
-This process is only available on target side.
-It receives data from Pump Extract and writes data to remote trail files.

Trails and Files
- Trail files ar the files which actually contains the data in the source and target side.
-Trails files are required for continuous data replication. These files are canonical structured files which only GoldenGate process can read.

Checkpoint Table
-CKPT is to maintain the integrity of data on the soure and target system.
-Incase of failure it doesn't read from the scratch, it reads from the point-of-failure.
-It provides the transaction recovery in case GoldenGate processes stopped abnormally.

Wallet
-It is a secure common storage for User IDs and Passwords. It is highly recommended to use wallet for secure credentials

Oralce Goldengate Topologies

Oralce Goldengate Topologies

• Uni-directional: Data is replicated in one direction from source to target.
• Bi-Directional: The data flows in both direction and stays synced up between site A and site B.
• Peer to Peer: Similar to Bi-directional but involves more that 2 databases which stay synced up.
• Broadcast: Data from source is sent to multiple destinations.
• Consolidation: Data from multiple sources is delivered to one destination DB.
• Cascading: Data from one source is sent to multiple destinations.

Oracle GoldenGate Key Features and Benefits

Oracle GoldenGate Key Features and Benefits

Oracle GoldenGate provides the following features and benefits that enable you to rapidly move transactional data between enterprise systems, Maintain Continuous Availability to Critical Systems and Oracle GoldenGate helps organizations eliminate the downtime caused by both unplanned and planned outages, and improve system performance and scalability.

The software can be configured to support the following scenarios:

-Disaster recovery and data protection. Create and maintain an immediate failover with up-to-the-minute data to minimize recovery time for missioncritical systems—deploy with Oracle Database or in non-Oracle environments.

-Zero-downtime operations. Enable uninterrupted business operations during system upgrade, migration, and maintenance activities.

-Data distribution. Synchronize data for distributed applications in real time for improved availability and scalability.

-Query offloading. Ensure high performance for production systems while still supporting necessary read-only activities by replicating data between heterogeneous sources and targets.

-Real-time data: Immediately capture, transform, and deliver transactional data to other systems with subsecond latency. Improve organizational decision-making through enterprise-wide visibility into accurate, up-to-date information.

-Heterogeneous support: Utilize heterogeneous databases and platforms to increase IT department flexibility. Extract data from existing IT investments and lower your total cost of ownership while unifying data from all enterprise systems

-Reliability: Deliver all committed records to the target, even in the event of network outages. Move data without requiring system interruption or outage windows.

-High performance with low impact: Move thousands of transactions per second with negligible impact on source and target systems. Access critical information in real time without bogging down production systems.

-Flexible topology support: Manage data in one-source-to-one-target, one-to-many, many-to-one, many-to-many, cascading, and bidirectional configurations.

Oracle Memory Structure

Oracle Memory Structure

Oracle’s memory structure consists of two memory areas known as:

• System Global Area (SGA): Allocated at instance startup, and is a fundamental component of an Oracle Instance
• Program Global Area (PGA): Allocated when the server process is started

System Global Area

The SGA is also called the shared global area. It is used to store database information that is shared by database processes. It contains data and control information for the Oracle server and is allocated in the virtual memory of the computer where Oracle resides.

The SGA consists of several memory structures:
– Shared pool
– Database buffer cache
– Redo log buffer
– Other structures (e.g. lock and latch management,
statistical data)
• There are two optional memory structures that can be configured within the SGA:
– Large pool
– Java pool

Shared Pool

The shared pool is used to store the most recently executed SQL statements and the most recently used data definitions.
• It consists of two key performance-related memory
structures:
– Library cache
– Data dictionary cache
• Sized by the parameter
SHARED_POOL_SIZE.

Database Buffer Cache

The database buffer cache stores copies of data blocks that have been retrieved from the data files.
• It enables great performance gains when you obtain and update data.
• It is managed through a least recently used (LRU) algorithm.
• DB_BLOCK_SIZE determines the primary block size.
Consists of independent sub-caches:
– DB_CACHE_SIZE
– DB_KEEP_CACHE_SIZE
– DB_RECYCLE_CACHE_SIZE
• Database buffer cache can be dynamically resized to grow or shrink using ALTER SYSTEM.
• DB_CACHE_ADVICE can be set to gather statistics for predicting different cache size behavior.

Redo Log Buffer Cache

The redo log buffer cache records all changes made to the database data blocks.
• Its primary purpose is recovery.
• Changes recorded within are called redo entries.
• Redo entries contain information to reconstruct or redo changes.
• Size is defined by LOG_BUFFER.

Large Pool

The large pool is an optional area of memory in the SGA configured only in a shared server environment.
• It relieves the burden placed on the shared pool.
• This configured memory area is used for session memory (UGA), I/O slaves, and backup and restore operations.
• Unlike the shared pool, the large pool does not use an LRU list.
• Sized by LARGE_POOL_SIZE.
ALTER SYSTEM SET LARGE_POOL_SIZE = 64M;

Java Pool

The Java pool services the parsing requirements for Java commands.
• Required if installing and using Java.
• It is stored much the same way as PL/SQL in database tables.
• It is sized by the JAVA_POOL_SIZE parameter.

Library Cache

The library cache stores information about the most recently used SQL and PL/SQL statements.
The library cache:
• Enables the sharing of commonly used statements
• Is managed by a least recently used (LRU) algorithm
• Consists of two structures:
– Shared SQL area
– Shared PL/SQL area
• Has its size determined by the shared pool sizing.

Data Dictionary Cache

The data dictionary cache is a collection of the most recently used definitions in the database.
• It includes information about database files, tables, indexes, columns, users, privileges, and other database objects.
• During the parse phase, the server process looks at the data dictionary for information to resolve object names and validate access.
• Caching the data dictionary information into memory improves response time on queries.
• Size is determined by the shared pool sizing.

Program Global Area Components

The Program Global Area or Process Global Area (PGA) is a memory region that contains data and control information for a single server process or a single background process. The PGA is allocated when a process is created and deallocated when the process is terminated. In contrast to the SGA, which is shared by several processes, the PGA is an area that is used by only one process. In a dedicated server configuration, the PGA includes these components:
• Sort area: Used for any sorts that may be required to process the SQL statement
• Session information: Includes user privileges and performance statistics for the session
• Cursor state: Indicates the stage in the processing of the SQL statements that are currently used by the session
• Stack space: Contains other session variables

Process Structure

An Oracle process is a program that depending on its type can request information, execute a series of steps, or perform a specific task. Oracle takes advantage of various types of processes:
• User process: Started at the time a database user requests connection to the Oracle server.
• Server process: Connects to the Oracle Instance and is started when a user establishes a session.
• Background process: Available when an Oracle instance is started.

User Process

A user process is a program that requests interaction with the Oracle server.
• It must first establish a connection.
• It does not interact directly with the Oracle server.

Server Process

A server process is a program that directly interacts with the Oracle server.
• It fulfills calls generated and returns results.
• Can be dedicated or shared server.

Background Processes

The relationship between the physical and memory structures is maintained by Oracle’s background processes.
• Mandatory background processes
DBWn  PMON CKPT LGWR SMON RECO
• Optional background processes
ARCn LMON Snnn QMNn LMDn CJQ0 Pnnn LCKn Dnnn

Database Writer

The server process records changes to rollback and data blocks in the buffer cache. Database Writer (DBWn) writes the dirty buffers from the database buffer cache to the data files. It ensures that a sufficient number of free buffers—buffers that can be overwritten when server processes need to read in blocks from the data files—are available in the database buffer
cache. Database performance is improved because server processes make changes only in the buffer cache.

DBWn defers writing to the data files until one of the following events occurs:
• Incremental or normal checkpoint
• The number of dirty buffers reaches a threshold value
• A process scans a specified number of blocks when scanning for free buffers and cannot
fine any.
• Timeout occurs.
• A ping request in Real Application Clusters environment.
• Placing a normal or temporary tablespace offline.
• Placing a tablespace in read only mode.
• Dropping or Truncating a table.
• ALTER TABLESPACE tablespace name BEGIN BACKUP

LOG Writer

LGWR performs sequential writes from the redo log buffer cache to the redo log file under
the following situations:
• When a transaction commits
• When the redo log buffer cache is one-third full
• When there is more than a megabyte of changes records in the redo log buffer cache
• Before DBWn writes modified blocks in the database buffer cache to the data files
• Every 3 seconds.
Because the redo is needed for recovery, LGWR confirms the commit only after the redo is written to disk.
LGWR can also call on DBWn to write to the data files.
Note: DBWn does not write to the online redo logs.

System Monitor

If the Oracle instance fails, any information in the SGA that has not been written to disk is lost. For example, the failure of the operating system causes an instance failure. After the loss of the instance, the background process SMON automatically performs instance recovery when the database is reopened. Instance recovery consists of the following steps:
1. Rolling forward to recover data that has not been recorded in the data files but that has been recorded in the online redo log. This data has not been written to disk because of the loss of the SGA during instance failure. During this process, SMON reads the redo log files and applies the changes recorded in the redo log to the data blocks. Because all committed transactions have been written to the redo logs, this process completely recovers these transactions.
2. Opening the database so that users can log on. Any data that is not locked by unrecovered transactions is immediately available.
3. Rolling back uncommitted transactions. They are rolled back by SMON or by the individual server processes as they access locked data.
SMON also performs some space maintenance functions:
• It combines, or coalesces, adjacent areas of free space in the data files.
• It deallocates temporary segments to return them as free space in data files. Temporary segments are used to store data during SQL statement processing.

Process Monitor

The background process PMON cleans up after failed processes by:
• Rolling back the user’s current transaction
• Releasing all currently held table or row locks
• Freeing other resources currently reserved by the user
• Restarts dead dispatchers.

Checkpoint

An event called a checkpoint occurs when the Oracle background process DBWn writes all the modified database buffers in the SGA, including both committed and uncommitted data, to the data files.

Checkpoints Responsible for:
• Signalling DBWn at checkpoints.
• Updating datafile headers with checkpoint information.
• Updating control files with checkpoint information.

Archiver (ARCn)

• Optional background process
• Automatically archives online redo logs when ARCHIVELOG mode is set
• Preserves the record of all changes made to the database.

Logical Structure

A logical structure hierarchy exists as follows:
• An Oracle database is a group of tablespaces.
• A tablespace may consist of one or more segments.
• A segment is made up of extents.
• An extent is made up of logical blocks.
• A block is the smallest unit for read and write operations.

Control File Contents

The information in the control file includes:
• Database name is taken from either the name specified by the initialization parameter
DB_NAME or the name used in the CREATE DATABASE statement.
• Database identifier is recorded when the database is created.
• Time stamp of database creation is also recorded at database creation.
• Names and locations of associated data files and online redo log files are updated when
a data file or redo log is added to, renamed in, or dropped from the database.
• Tablespace information is updated as tablespaces are added or dropped.
• Redo log history is recorded during log switches.
• Location and status of archived logs are recorded when archiving occurs.
• Location and status of backups are recorded by the Recovery Manager utility.
• Current log sequence number is recorded when log switches occur.
• Checkpoint information is recorded as checkpoints are made.

Redo Log Files

Redo log files record all changes made to data and provide a recovery mechanism from a system or
media failure.
• Redo log files are organized into groups.
• An Oracle database requires
at least two groups.
• Each redo log within a group is called a member.

Structure of the Redo Log Files

The database administrator can set up the Oracle database to maintain copies of online redo log files to avoid losing database information due to a single point of failure.
Online Redo Log Groups
• A set of identical copies of online redo log files is called an online redo log group.
• The LGWR background process concurrently writes the same information to all online redo log files in a group.
• The Oracle server needs a minimum of two online redo log file groups for the normal operation of a database.
Online Redo Log Members
• Each online redo log file in a group is called a member.
• Each member in a group has identical log sequence numbers and the same size. The log sequence number is assigned each time the Oracle server starts writing to a log group to identify each redo log file uniquely. The current log sequence number is stored in the control file and in the header of all data files.

Archived Redo Log Files

• Archiving redo log files is accomplished by ARCn (Archiver) or manually through SQL statements.
• An entry in the control file recording the archive log name, log sequence number, and high and low SCN number is made whenever a redo log is successfully archived.
• A filled redo log file cannot be reused until a checkpoint has taken place and the redo log file has been backed up the ARCn process.
• Archived redo log files can be multiplexed.
• Archived redo log files must be maintained by theDBA.

ARCHIVELOG mode or in NOARCHIVELOG mode.

NOARCHIVELOG

In NOARCHIVELOG mode, the online redo log files are overwritten each time an online redo log file is filled, and log switches occur. LGWR does not overwrite a redo log group until the checkpoint for that group is completed.

ARCHIVELOG

If the database is configured to run in ARCHIVELOG mode, inactive groups of filled online redo log files must be archived. Because all changes made to the database are recorded in the online redo log files, the database administrator can use the physical backup and the archived online redo log files to recover the database without losing any committed data.
There are two ways in which online redo log files can be archived:
• Manually
• Automatically: Recommend method

How to Unlock OIM Schema

How to Unlock OIM Schema.

To view schema name and status:

SELECT username, account_status FROM dba_users;

Unlock Schema:
ALTER USER <Schema_Name>_OIM ACCOUNT UNLOCK;
ALTER USER <Schema_Name>_MDS ACCOUNT UNLOCK;
ALTER USER <Schema_Name>_OPSS ACCOUNT UNLOCK;
ALTER USER <Schema_Name>_ORASDPM ACCOUNT UNLOCK;
ALTER USER <Schema_Name>_SOAINFRA ACCOUNT UNLOCK;
ALTER USER <Schema_Name>_BIPLATFORM ACCOUNT UNLOCK;

Basics of IDAM

Basics of IDAM

Oracle Identity and Access Management (IDAM) components are Java applications deployed on WebLogic Server with database as repository. Consider the following components when starting and stopping an Oracle Identity and Access management server:

-One and only one Admin server
-One or more SOA Suite Managed servers
-One or more OIM Managed servers
-One or more OAM Managed servers
-Database server used as repository for Oracle Identity and Access Management
-Node Manager per machine (optional component)
-External LDAP server as User store (optional component)

Note
Oracle Access Manager's default identity store is an embedded LDAP server (shipped as part of WebLogic server). It is recommended to configure Oracle Access Manager's Identity Store to external LDAP server, such as Oracle Internet directory or Microsoft Active directory.

Top-level directories and HOMES used in Identity and Access Management:

Middleware Home: MW_HOME
WebLogic Home: WL_HOME
Coherence Home: COHERENCE_HOME
Oracle Home for IDAM: IDAM ORACLE_HOME
Oracle Home for common: COMMON ORACLE_HOME
Oracle Home for SOA: SOA ORACLE_HOME
Domain Home: DOMAIN_HOME

why SOA is required in IDAM?
SOA Suite is required only if you are using Oracle Identity Manager. OIM uses Service Oriented Architecture (SOA) to process workflows related to approvals of various OIM requests


Why does EBS require OID with OAM?
Oracle Access Manager itself doesn't require Oracle Internet Directory.  However, Oracle Internet Directory is a mandatory requirement when Oracle Access Manager is integrated with the E-Business Suite.
Why?  The short answer is that the E-Business Suite has hardcoded dependencies on Oracle Internet Directory for this configuration. These dependencies mean that you cannot replace Oracle Internet Directory with any third-party LDAP directory for this particular configuration.


Weblogic

WebLogic Server is a J2EE application server on which both Oracle Identity Manager (OIM) and Oracle Access Manager (OAM) are deployed.

-WebLogic Server Domain: WebLogic server domain is logical grouping of resources and services. It contains Admin Server, Managed server, JDBC data Sources, Java Messaging Server, and coherence.

-WebLogic Administration (Admin) Server: Administration server is a WebLogic server that maintains configuration data for a domain. There is always one and only one administration server in a Weblogic domain.

-WebLogic Managed Server: Any WebLogic server other than the Admin server is called a Managed server. When you configure both OAM and OIM in same domain, domain creation creates three Managed servers one for OAM (oam_server1); the second for OIM (oim_server1); and the third for SOA (soa_server1).

Note:

These are default names used by the doamin configuration.

-7001 is WebLogic's default Admin server port which the installer will assign during domain configuration. If 7001 is in use by another process during domain configuration then the installer will use the next available port, that is 7002.

-If you are not sure about the port used by Weblogic server's (Admin and Managed servers) (OAM, OIM and SOA), you can verify it from the configuration file $DOMAIN_HOME/config/config.xml.

-It is recommended that you create the file boot.properties under $DOMAIN_HOME/servers/<server_name>/security/ so that you don't have to provide username and password manually. This file should contain two lines:

USERNAME=<weblogic_user_name>
PASSWORD=<weblogic_user_password>

-WebLogic server will automatically encrypt the boot.properties file during next start-up.

-WebLogic configuration is stored in the XML file $DOMAIN_HOME/config/config.xml and contains information such as Admin/Managed server hostname, port, and name of managed server. Check this file to find the information required to start/stop IDAM components.

-Boot identity file (boot.properties) is a text file that contains user credentials for starting and stopping an instance of WebLogic server. For more information on Boot Identity File: http://download.oracle.com/docs/cd/E12839_01/web.1111/e13708/overview.htm#START128.

-Each WebLogic server instance runs in its own JVM. If you are unable to shut down a server instance using the methods described in the previous sections, you can use an operating system command to kill the JVM.

Note:
Killing a java process will do a forceful shutdown of WebLogic server instance.

-There is no script to stop the node manager. If you want to stop the node manager use kill -9 <PID>

- Start/Stop Overview
- OAM/OIM Start
- OAM/OIM Stop
- Start/StopLogs

OIM/OAM: Start

-Start OID/OIM/OAM Database & Listener
lsnrctl start
sqlplus “/as sysdba”
startup;

-Start OID(System) Component
:*Only if Integrated with OIM/OAM
opmnctl startall

-Start Java Component

==>Start Admin Server:
$DOMAIN_HOME/bin/startWebLogic.sh
==>Start OAM Managed Server:
$DOMAIN_HOME/bin/startManagedWebLogic.sh oam_server1
==>Start SOA Managed Server:
$DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1
==>Start OIM Managed Server:
$DOMAIN_HOME/bin/startManagedWebLogic.sh oim_server1


OIM/OAM: Stop

Stop Java Component

==>Stop SOA Managed Server:
$DOMAIN_HOME/bin/stopManagedWebLogic.sh soa_server1
==>Stop OIM Managed Server:
$DOMAIN_HOME/bin/stopManagedWebLogic.sh oim_server1
==>Stop OAM Managed Server:
$DOMAIN_HOME/bin/stopManagedWebLogic.sh oam_server1
==>Stop Admin Server:
$DOMAIN_HOME/bin/stopWebLogic.sh

Stop System Component:*Only if Integrated with OIM/OAM
opmnctl stopall

Stop OIM/OAM Database & Listener

sqlplus “/as sysdba”
shutdown immediate;
lsnrctl stop


OIM/OAM: Start/Stop Logs

Admin Server
$DOMAIN_HOME/servers/<server_name>/logs/
OIM/OAM/SOA Server
$DOMAIN_HOME/servers/<server_name>/logs/
OID:OPMN
$ORACLE_INSTANCE/diagnosVcs/logs/OPMN/opmn/
OID:LDAP
$ORACLE_INSTANCE/diagnosVcs/logs/OID/[oid1]/
OID:ODSM/DIP
$DOMAIN_HOME/servers/<server_name>/logs/

Installation:

-Oracle Linux 5.7 Virtual Machine
-Java Development Kit 1.7
-Oracle Database 11.2.0.4
-Oracle Weblogic Server 10.3.6
-Oracle SOA Suite 11.1.1.9
-Oracle Identity & Access Management 11.1.2.3
-Repository Creation Utility 11.1.1.9
-Oracle Unified Directory (This is optional and required only if you want to integrate OAM & OIM with LDAP. You can use any LDAP of your choice)

Reposity Creation Utility (11.1.1.9):
Note: 11.1.1.9 RCU is used to create schema in 11.1.2.3 IDAM) by running
pre-requisite:
-Database and listener should be up and running while configuring RCU.
-We need to set two parameters:
alter system set open_cursors=800 scope=spfile;
alter system set processes=800 scope=spfile;

During the installtion RCU will ask database connection details like:
-Database type
-Hostname
-Port number
-Service name/SID
-Username
-Password

which components you have selecte while installing RCU?
After creating a new prefix (bydefault DEV), we have to choose below components.
-Oracle Identity Manager
-Oracle Access Manager
-Oracle Mobile Security Manager
Below schema will be selected automatically
-Metadata Services
-Audit Services
-Oracle Platform Security Services
-Business Intelligence Platform
-SOA Infrastructure
-User Messaging Service

Note:
The default and temporary tablespaces are created for all the compoenents.

OIM - Frequently used schedulers

OIM - Frequently used schedulers

To trigger user policy :
Evaluate User Policy

To refresh catalog table : 
Catalog sync job

To delete AI permanently :
Application instance Post Delete Processing job

To sync entitlements :  
Entitlement List

Important Port Numbers In IDAM

Important Port Numbers In IDAM

Weblogic admin server 7001
Obiee server                  9704
Oam_server                   14100
Oam_policy_mgr 14150
Oim_server                   14000
Omsm_server                14180
Soa_server                     8001

Testing URLs
------------------
WebLogic Admin Server
http://prodidm:7001/console

Fusion Middleware Control
http://prodidm:7001/em

Oracle Access Manager Console
http://prodidm:7001/oamconsole

Oracle Access Manager Server
http://prodidm:141000/oam

OIM Server
http://prodidm:14000/oim
xelsysadm/*******

SOA Suite
http://prodidm:8001/soa-infra
weblogic/*******

OIM Sysconsole
http://HOSTNAME:PORT/sysadmin/
Example:
http://localhost:14000/sysadmin/
or
http://iam.myhostname.com:14000/sysadmin/
Username for system administrator is : xelsysadm

OIM user console
http://HOSTNAME:PORT/oim/
Example:
http://localhost:14000/oim/
or
http://iam.myhostname.com:14000/oim/

OAM console
http://WLS_HOSTNAME:PORT/oamconsole
Example:
http://localhost:7001/oamconsole
or
http://iam.myhostname.com:7001/oamconsole

WLS console
http://WLS_HOSTNAME:PORT/console
Example:
http://localhost:7001/console
or
http://iam.myhostname.com:7001/console

What is Oracle IDAM ?

What is Oracle IDAM ?

Identity management is a collection of processes that a company uses to manage the security life cycle of resources for its users, organizations and entities.

Importance:
A company needs an identity management solution to:
-Manage its users, organizations and resources.
-Regulate access rights to its resources.
-Provide security for its resources.
-Audit, monitor and log its resouces
-Pass correspondence between resources

Day to Day Activities & Brief About Yourself

Day to Day Activities & Brief About Yourself

I am XYZ.

Currently i'm working with XYZ company, I have around 4.2 years of experience as Oracle Apps DBA,  I have worked on different projects like supporting, up-gradation, implementation & migration projects.

Though my involvement was not end-end on these projects, but my roles are major like:
-collecting information of servers.
-collecting information of databases
-collecting OS and mounpoint information
-database versions
-checking the required rpms on the servers and specially documenting and presenting to lead.

My current project is on support and I support 2 production instances, & that related we have UAT, TEST and DEVELOPMENT instances, all instances are running non-rac with single instance.

Third party applications are integrated with production servers like, SOA, OBIEE, Informatica and DOCSAVI.

Day to day Responsibilities:

- checking the critical alerts (maybe some services, mount-point full, datafiles resize, listener issues)
- checking the handover emails (maybe some scheduled activities like patching, clone, code deployments etc)
- checking the scheduled backup status.
- Perform cloning activity on users request, on few instances we clone every week.
- Sometimes getting a request to apply patch.
- code migrations
-creating SR's and follow-up with pending SR's
- doing Sanity checks on production servers. Depending on the priority basis I will start the work. If there is any pending in the work I will handover to next shift people.
- checking the calendar notes for any scheduled activities assigned in the shift
- Monthly performance Report
- Troubleshooting activities:
*users unable to connect to database
*listeners went down
*concurrent managers not coming up after clone.
* immediately after clone users are complaining that permissions and grants are missing.
*creating users and assigning roles in the new clone.

Home, Instance, Directories & Domain In Oracle Weblogic (10.3.6) 11g

Home, Instance, Directories & Domain In Oracle Weblogic (10.3.6) 11g

a) MW_HOME – Fusion Middleware Home : This is top level directory for Fusion Middleware products and is created at the time of webLogic Server installation.

b) WLS_HOME – Oracle WebLogic Server Home : This is directory under Fusion Middleware Home and is created at the time of webLogic Server installation. This directory contains binaries (software) for Oracle WebLogic Server.

c) ORACLE_HOME – Oracle Home : contains binaries (software) related to specific oracle middleware product (soa, webcenter,OID, HTTP).
– ORACLE_HOME does NOT contain any logs or configuration files (logs or configuration file will either be in domain orInstance Directory).
– Each Oracle Middleware Product (SOA, WebCenter, OID, HTTP Server) should be installed in its own ORACLE_HOME inside Fusion Middleware Home.
– Oracle HOME resides within directory structure of Fusion Middleware Home
– Each Oracle ORACLE_HOME can be associated with multiple Oracle Instances or WebLogic Domain.

d) ORACLE_INSTANCE – Oracle Instance : contains runtime (configuration, log..) files for one or more System Components (HTTP Server, WebCache, OID)
– System Components (HTTP Server, WebCache, OID) are configured in Oracle Instance
– Oracle Instance can reside anywhere (inside or outside fusion middleware home) on server.

e) WebLogic Domain – Domain is logical grouping of one (and only one) Administration Server and zero or more Managed Server in WebLogic Server.
– Java Components (SOA , WebCenter..) are configured in WebLogic Domain
– You can configure multiple domain for multiple Oracle Fusion Middleware component (one domain for SOA , another for Webcenter third for OID) or can cnfigure all Fusion middleware components in to single domain (webcenter, SOA, OID in same domain)

Homes in Weblogic:
There are 4 homes in weblogic.
1)JAVA_HOME
2)WL_HOME
3)MW_HOME
4)DOMAIN_HOME

Directories in Weblogic:

1.Java_Home
Bin---------important binaries related to java, like jps and jstack.     
Lib --------.jar files
Db
a)bin-------.bat files
b)lib-------some .jar files
Man-----------UTF-8 and man related directory     
Include-------linux dir and .h files
Jre
a)bin------some important binaries of java, like jcontrol, servertool etc.
b)lib------some libraries.
c)plugin and .txt files-----desktop dir.


2.Wl_home
cd $WL_HOME
common  inventory  L10N  server  sip  uninstall

$WL_HOME/common
bin  deployable-libraries  derby  eval  lib  nodemanager  quickstart  templates  wlst

$WL_HOME/common/bin
commEnv.sh  config.sh  setPatchEnv.sh  startManagedWebLogic.sh  unpack.sh   wlscontrol.sh   wlst.sh
config_builder.sh  pack.sh  startDerby.sh  stopDerby.sh  upgrade.sh  wlsifconfig.sh

$WL_HOME/common/nodemanager
nm_data.properties  nodemanager.domains  nodemanager.log  nodemanager.log.lck  nodemanager.properties

$WL_HOME/common/quickstart
images  quickstart.sh  resources  wls_qsConfig.xml

$WL_HOME/common/templates
applications  domains  scripts  silent_scripts
Inventory
L10N
Server
Sip
Uninstall   

$WL_HOME/server/bin
international  nohup.out  setWLSEnv.sh  startNodeManager.sh

3.MW_HOME

cd $MW_HOME
domain-registry.xml  modules  patch_wls1036  registry.xml   utils
logs  ocm.rsp  registry.dat   user_projects  wlserver_10.3

cd $MW_HOME/utils
bsu  ccr  clone  config  quickstart  uninstall  utils.jar

cd $MW_HOME/utils/bsu
bsu.jar  bsu.sh  cache_dir  patch-client.jar  smartupdate.ico

cd $MW_HOME/utils/quickstart
images  libjni.so  qs.html  quickstart.jar  quickstart.sh

cd $MW_HOME/utils/uninstall
extftr  libjni.so  uninstall.jar  uninstall.sh  WebLogic_Platform_10.3.6.0

cd $MW_HOME/logs
wlsconfig_20151211131015.log  wlst_20151214124918.log  wlst_20151217155251.log  wlst_20151218121910.log
wlsconfig_20151219172057.log  wlst_20151214124918.out  wlst_20151217155251.out  wlst_20151218121910.out
wlst_20151211134604.log       wlst_20151217091248.log  wlst_20151217161205.log  wlst_20151218122907.log

4.Domain_home

cd $DOMAIN_HOME
autodeploy  config    edit.lok  init-info  pending   servers   startWebLogic.sh
bin  console-ext  fileRealm.properties  lib  security  shutdown.py  tmp

cd $DOMAIN_HOME/config
configCache  config.lok  config.xml  deployments  diagnostics  jdbc  jms  nodemanager  security  startup

cd $DOMAIN_HOME/init-info
domain-info.xml  security.xml  startscript-unsub.xml  startscript.xml  tokenValue.properties

cd $DOMAIN_HOME/servers
AdminServer  domain_bak  ms-01  ms-02  ms-03  ms-04

cd $DOMAIN_HOME/bin
nodemanager  server_migration   setDomainEnv.sh          startWebLogic.sh        stopWebLogic.sh
nohup.out    service_migration  startManagedWebLogic.sh  stopManagedWebLogic.sh

Note:
1)Pending directory in DOMAIN_HOME
2)domain_bak under DOMAIN_HOME/servers
3)cache_dir under MW_HOME/utils/bsu

4)Autodeploy under DOMAIN_HOME
Pending directory: This directory contains the domain configuration files that represent the configuration changes that have

been requested, but not yet been activated. After the configuration changes are activated, the configuration files are deleted

from this directory. Configurations can be changed at runtime in the console of the Administration Server. Before they are

implemented within the domain, they are temporarily stored in this directory.

1.start/stop of Admin and Managed servers and contains configuration files.
setDomainEnv.sh
startWebLogic.sh
stopWeblogic.sh
$DomainHome/$serverName/bin

2. All important components e.g.  Domain configurtaion,  JMS, JDBC etc
config.xml
jdbc config files
jms config files
fmwconfig files etc
$DomainHome/$serverName/config

4. Encrypted wls username and password, used while starting the server.
boot.properties
$DomainHome/$serverName/servers/AdminServer/security

5. nodemanager script and other environment scripts are located:
startNodeManager.sh
setWLSEnv.sh
$WL_HOME\server\bin

6. All troubleshooting logfiles are stored:
access.log,
AdminServer.log
ManagedServer.log
gc.log
domain.log
AdminServer.out
ManagedServer.out files
$DomainHome/$serverName/servers/$serverName/logs

6.Contains Management Service logs and trace file for troubleshooting purpose.
emoms.log
emoms.trc
$DomainHome/$serverName/sysman/log

7. weblogic related important files are located:
commEnv.sh       
config.sh
setPatchEnv.sh
startManagedWebLogic.sh
unpack.sh 
wlscontrol.sh 
wlst.sh
config_builder.sh
pack.sh 
startDerby.sh 
stopDerby.sh           
upgrade.sh
wlsifconfig.sh
$WL_HOME/common/bin

8. Node manager related important files are located:
nm_data.properties
nodemanager.domains
nodemanager.log
nodemanager.log.lck
nodemanager.properties
$WL_HOME/common/nodemanager

9. weblogic upgrading related scripts loacted:
quickstart.sh
$WL_HOME/common/quickstart

1) where is the location of config.sh in wl (for domain creation) ?
ans) cd $WL_HOME/common/bin

2) where is the location of Nodemanager startup script ?
ans) cd $WL_HOME/server/bin

3) Where is Nodemanager configuration files ?
ans) cd $WL_HOME/common/nodemanager

4) Weblogic uninstall utility ?
ans) cd $WL_HOME/uninstall

5) Weblogic quickstart location ?
ans) cd $WL_HOME/common/quickstart

6) Logfiles location in Middleware ?
ans) cd $MW_HOME/logs

7) Where is the location of bsu.sh script ?
ans) cd $MW_HOME/utils/bsu

8) Domain directories location ?
ans) cd $MW_HOME/user_projects

9) Where is the location of Autodeploy directory ?
ans) cd $DOMAIN_HOME

10) Where is the location of startup & shutdown scripts for weblogic and managed server ?
ans) cd $DOMAIN_HOME/bin

11) Where is the location of nm_password.properties ?
ans) cd $DOMAIN_HOME/config/nodemanager

12) Where is the location of Admin server and Managed server logfiles (tmp/cache/logs)?
ans) cd $DOMAIN_HOME/servers

Oracle E-Business Suite High Level Upgrade From 12.1.1 to 12.2.7

Oracle E-Business Suite High Level Upgrade From 12.1.1 to 12.2.7

Pre-requites steps for upgrade

1)  Pre-install  packages on both database & application server.
-make sure all the rpms's are installed.
2) Take backup of whole application file system and database.
3) Take Backup of oracle software binaries.
4) Check the mount point, make sure its sufficient during upgrade process
5) Gather schema statistics
6) Add following parameter to initialize parameter file
-service_names=SID, ebs_patch
-local_listener='SID_LOCAL'
-recyclebin=off

7) Stage Creation (Root user)
-Go to startCD51
-Run buildStage.sh (Make sure run this script as root user)

8) Start installation of Application of R12.2.0 as a root user.
-cd /u02/apdba/ebs_upgrade_12_2/R12.2_Source/startCD/Disk1/rapidwiz
./ rapidwiz
-choose Upgrade to Oracle E-Business suite Release R12.2.0 and press Next button to continue.
-deselect check box to avoid any updates from My Oracle support.  Click next.
-First select "Create Upgrade File System" to configuring and creating an upgrade file system or upgraded database.
-Specify the port pool values for port pooling and press on Edit ports for specify DB port.
-Database node configuration wizard.
Fill all details about database host, SID, Port, Domain Name, DB OS User, Base Directory and RDBMS ORACLE_HOME.
Dont forget to select "User Existing Oracle Home (No New Database Home Install).
-Provide APPS user password details and review APPLSYSPUB and GUEST user details.
-Select your database character set and press Next.
-Fill all details in below wizard for application node and verify the apps base directory ,
instance home directory and click on Edit Services, enabled all services as Application and db are running on single server.
-Enter weblogic handy password and application OS user password.
-It will display all node information. Press Next to continue.
-This is pre-install validation steps. all must be completed with green yes mark.
-If its failed any of area of the prerequisites checks, then we have to fix the issue first and press retry button.
-list of component will be installed after rapiz wizard is completed successfully.
Press Next to continue.
-list of component will be installed after rapiz wizard is completed successfully.

9) Run the 12.2.0 Upgrade driver
-run adgrants.sql from patch directory to $ORACLE_HOME

10) Apply all Consolidated Upgrade Patches (CUPs)
-Downloaded the preinstall patches as per metalink note R12.1 and 12.2 Oracle E-Business Suite Preinstall Patches Report (Doc ID 1448102.2)
Note: Merged and apply the 12.2.0 upgrade with CUP patches.
It will take almost 18 hours and successfully completed.

11) Back up Oracle E-Business Suite (recommended) Perform a full Oracle E-Business Suite backup of the application and database.
-Run EBSSecConfigChecks.zip and EBSAuditScripts.zip

12) Update the RDBMS ORACLE_HOME file system with AutoConfig and Clone files.
-Run environment file of application file system.
-$perl <AD_TOP>/bin/admkappsutil.pl
-Copy to RDMBS_HOME (DATABASE HOME)
-unzip -o appsutil.zip
• Generate a new database context file
-$cd <RDBMS ORACLE_HOME>/appsutil/bin
-$perl adbldxml.pl
• Run AutoConfig on the database tier nodes
-$Cd <RDBMS ORACLE_HOME>
-$cd appsutil/bin/
-$adconfig.sh contextfile
• Run AutoConfig on the Apps Tier.
-Run environment file on apps Tier.
-Login to as apps/apps user
-Prior to running AutoConfig check if table - ADX_PRE_AUTOCONFIG is existing in APPS schema:
Select object_name, object_type, owner, status from dba_objects where    upper(object_name) = 'ADX_PRE_AUTOCONFIG' and object_type='TABLE' and upper(owner)='APPS';
-cd $AD_TOP/patch/115/sql
Sqlplus apps/appson
-Sql> @txkDropAdxPreAutoConfig.sql
-Run Autoconfig: go to $ADMIN_SCRIPT_HOME/
-$sh adautocfg.sh

13) Run the Rapid Install to configure Release 12.2 E-Business Suite instance.
-You must run the Rapid Install a second time to complete the configuration using the Run File System context file.
-Select Upgrade to Oracle E-Business Suite Release 12.2.0
-Select the option of Configure Upgraded Release 12.2.0 Instance.
-Select an existing application context file from newly installed file system.
-Review Application user information.

14) Enabling Online Patching Cycle.
-Online Patching requires the database to be upgraded to version 11.2.0.4 or higher. Ensure that the database upgrade was completed properly and without errors.
-Ensure that the required Database patches for Release 12.2 have been applied Review the Database Preparation Guidelines for Release 12.2 and ensure that all patches listed are installed in your database. Do not proceed with the enabling online patching process if all patches have not been installed.
-Create the online patching log file location and set it as the current directory:
mkdir $LOG_HOME/appl/op
-Run the following Readiness reports: • ADZDPSUM.sql and ADZDPMAN.sql and ADZDPCUST.sql
-both should be run system/manager.
-Run the Online Patching Diagnostic Reports ADZDEXRPT.sql

15) Download and apply the Online Patching Enablement patch Download and apply the Online Patching Enablement patch.
-Use Autopatch in hotpatch mode to apply the patch (adpatch options=hotpatch,forceapply)
-Important: While applying the Online Enablement patch, you may receive the following error: 'Attention: Adpatch should no longer be used to apply patches. Please use ADOP tool for applying patches.' If you receive this error, then you must use adop in hotpatch mode to apply the enablement patch.
-The Online patching enablement patch ran for almost 12-14 hours.
-Re-run the Online Patching Enablement Status Report after the Online Patching Enablement patch has been applied

Oracle E-Business Suite Upgrade High Level Steps From 12.2.0 to 12.2.5

Oracle E-Business Suite Upgrade High Level Steps From 12.2.0 to 12.2.5

All Oracle EBS Fresh installations will configure base release 12.2.0, which has to be upgraded separately after the successful completion of the installation.

Source version: 12.2.0
Target version: 12.2.5

1) Run the EBS Technology Codelevel Checker (ETCC), which will provide output of all the latest available patches that are missing on the current instance.
-available via patch 17537119.

2) Run the two scripts on database as well as application tier.
-source the ENV run checkDBpatch.sh
-it will show below homes patches.
*Oracle Forms and Reports 10.1.2.3.0
*Oracle Fusion Middleware (FMW) - Web Tier 11.1.1.9.0
*Oracle Fusion Middleware (FMW) - oracle_common 11.1.1.9.0
*Oracle WebLogic Server (WLS) 10.3.6.0.7
-source the ENV run sh checkDBpatch.sh
*Oracle Database Release 12.1.0.2  (No PSU applied)

3) Apply Oracle Database Release 12.1.0.2 Patches:
-Bring down Application, Database and listener.
-Apply all Database patches recommended by ETCC
-set path.
-opatch apply.

4) Apply Oracle Application Home 10.1.2.3.0 Patches:
-set path
-opatch apply

5) Apply Oracle Fusion Middleware (FMW) - Web Tier 11.1.1.9.0 Patches:
-set path.
-opatch apply.

6) Apply Oracle Fusion Middleware (FMW) - oracle_common 11.1.1.9.0 Patches.
-set path.
-opatch apply.

7) Apply Oracle WebLogic Server (WLS) 10.3.6.0.7 Patches.
-patch must be installed on WebLogic Server before proceeding with the upgrade.

8) Applying AD and TKX Patches.
e.g:
p20745242_R12.AD.C_R12_LINUX.zip
p20784380_R12.TXK.C_R12_GENERIC.zip
p22123818_R12.AD.C_R12_LINUX.zip
p22363475_R12.TXK.C_R12_GENERIC.zip
p22495069_R12.TXK.C_R12_GENERIC.zip
-make sure we have taken before applying these patches.
-mtart the WebLogic admin server from the RUN file system.
-run adgrants.sql from the respective patch directories before applying the patch.
-The patch 20745242 (R12.AD.C.Delta.7) contains a newer version of the adgrants.sql script, so it’s mandatory to execute this script from the database tier.
-adop phase=apply patches=20745242 hotpatch=yes
-Similarly, the patch 22123818:R12.AD.C also contains the adgrants.sql script. Execute the script before applying this patch.
-adop phase=apply patches=22123818 hotpatch=yes
-After installing these patches, you can merge patches 20784380, 22363475, and 22495069 and install it.
-adop phase=apply patches=20784380,22363475,22495069 hotpatch=yes merge=yes

9) Execute AutoConfig on the database tier.

10) Migrate the latest code on the database tier using $AD_TOP/bin /admkappsutil.pl.

11) Restart the database and application tiers.
-Once after applying all the patches, run again ETCC (EBS Technology Codelevel Checker) and get the confirmation that all the required pathces has been applied on all the technology stacks.
-sh checkDBpatch.sh
-sh checkMTpatch.sh

12) Installation of 12.2.5 Upgrade Patch.
-The preparation of the EBS 12.2.5 patch upgrade is complete. Now the system is almost ready for installing an upgrade patch. Follow these steps
-Set optimizer_adaptive_features to FALSE. It’s recommended that you set this to FALSE because of performance issues during upgrade.
-Source the RUN file system and stop all the application services.
- Ensure there is no active patching cycle using "adop -status"
- Install 12.2.5 Upgrade patch 19676458 in downtime mode.
-adop phase=apply apply_mode=downtime patches=19676458

13) Verify the logs and execute the cleanup phase.
- adop phase=cleanup
- After cleanup, run the fs_clone to sync the another file system with first one.
- adop phase=fs_clone
- Revert the DB parameter changes: optimizer_adaptive_features to TRUE.

The upgrade of Oracle EBS 12.2.0 to 12.2.5 has completed successfully.

12.2 ADOP Prepare Phase Fails with message " [ERROR]: Domain might be locked by some other WLS user process"

12.2 ADOP Prepare Phase Fails with message " [ERROR]: Domain might be locked by some other WLS user process"

Error:
On EBS 12.2 When running adop, prepare phase fails with the below error:

Validating configuration on node: [MYSERV]...
    Log: /u01/app/EBSR12/fs_ne/EBSapps/log/adop/14/prepare_20/<Context_Name>
    [WARNING]: There could be issues while validating the ports used for E-Business Suite instance against ports used in /etc/services. Refer the log file for more details.
    [WARNING]: Either some of the required entries in /etc/hosts file might be missing (e.g. localhost or hostname) OR the file /etc/hosts could not be read.
    [ERROR]: Domain might be locked by some other WLS user process
    [UNEXPECTED]Error occurred while executing "perl /u01/app/EBSR12/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/u01/app/EBSR12/fs2/inst/apps/<Context_Name>/appl/admin/<Context_Name>.xml -patchctxfile=/u01/app/EBSR12/fs1/inst/apps/<Context_Name>/appl/admin/<Context_Name>.xml -phase=prepare -logloc=/u01/app/EBSR12/fs_ne/EBSapps/log/adop/14/prepare_20150811_185137/<Context_Name> -promptmsg=hide"
    [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on MYSERV
Reviewing the file $INST_TOP/apps/<Context_Name>/logs/appl/rgf/TXK/txkValidateDomainInRCOut.txt, the below error message is recorded:
cmd : java weblogic.WLST /u01/app/EBSR12/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkValidateDomainInRC.py --adminuser=weblogic --verify=domainEditModeEnabled --adminurl=t1://hostname.domain:adminport> /u01/app/EBSR12/fs2/inst/apps/<Context_Name>/logs/appl/rgf/TXK/txkValidateDomainInRCOut.txt
ERROR: Domain is in edit mode.

Cause:
Someone with administrator privileges on WLS Admin Console may have locked the Weblogic domain for making changes, and has not released the checkout.
This leaves the domain in edit mode, resulting in the issue.

Solution:
To resolve the issue test the following steps in a development instance and then migrate accordingly:

1. Start the admin server on the run file system (if not started already).
2. Login in to WLS Admin Console (http(s)://hostname.domain:<adminport>/console)
3. Click on the "Activate Changes" or the "Release Configuration" button (depending on the version) in the "Change Center" region on the top left corner.
4. Logout of the WLS console.
5. Rerun the adop phase=prepare command and confirm adop completes successfully.

EBS Technology Codelevel Checker (ETCC)

EBS Technology Codelevel Checker (ETCC)

This patch provides two scripts, together referred to as ETCC, that help ensure you have the required database and middle tier bugfixes installed for your Oracle E-Business Suite Release 12.2 system.

The scripts are:
- checkDBpatch.sh (checkDBpatch.cmd on Windows). This is the Database EBS Technology Codelevel Checker (DB-ETCC), which determines if all the needed bugfixes exist in the specified database ORACLE_HOME.

- checkMTpatch.sh (checkMTpatch.cmd on Windows). This is the Middle Tier EBS Technology Codelevel Checker (MT-ETCC), which determines if all the needed bugfixes exist in the middle tier file system. 

High Level Steps For Database Migration From Windows to Linux Using RMAN

High Level Steps For Database Migration From Windows to Linux Using RMAN

Source database: Windows Server 2008 (11.2.0.1)
Target database: Oracle Linux 5.7  (11.2.0.1)

1) Before starting the migration make sure 11g database binary already installed on the linux server.

2) Perform the pre-checks on windows server.
-check the database version on source and target both should be same.
-check platform compatibility between source and target.
NOTE: ENDIAN_FORMAT for both OS should be same
-check the location and status of datafiles, controlfiles and redolog files.
-check the invalid objects.
-create the pfile.
-create the necessary directories for storing the migration files.

3) Backup the database

4) Shutdown the database.

5) Startup the database in read only.
-startup mount.
-alter database open read only;

6) Check database readiness for transport from Windows to Linux.

7) Check if there are any external objects.

8) Connect rman and prepare the convert script.
-convert database new database 'ORCL' transport script 'C:\mig\transport.sql' db_file_name_convert 'C:\app\admin\oradata\DELL' 'C:\mig' to platform 'Linux IA (64-bit)';
-At the end of the script it will give a message:
Run SQL script C:\MIG\TRANSPORT.SQL on the target platform to create database
To recompile all PL/SQL modules, run utlirp.sql and utlrp.sql on the target platform
To change the internal database identifier, use DBNEWID Utility
Finished conversion at source.

9) Prepare the target server.

10) Copy the migrated files from source to target.
-create the necessary directories and place the CRD files onto the folder.
-set the ENV of 11g linux home.
-prepare the pfile of 11ghome.

11) Modify the highlighted in Transport Script as per your Requiremt.
-Read the script, as it has all instruction for Migrating Database.

12) Run TRANSPORT.SQL Script.
-sqlplus / as sysdba
-Connected to an idle instance.
-SQL> @TRANSPORT.SQL
-Database Migration Has Completed

13) Perform post steps.

Changes In Oracle EBS R12.2.x from R12.1.x

Changes In Oracle EBS R12.2.x from R12.1.x

There are many changes in Oracle EBS R12.2.x when compared to Oracle EBS R12.1.x version.
Few of the major architectural changes and new features are mentioned below:

1. Oracle E-Business Suite R12 (12.2) uses Oracle Fusion Middleware 11g R1 PS3 (11.1.1.4) including WebLogic 10.3.4 as its application server (Note: In previous version of R12 i.e. 12.0.X and 12.1.X this is 10g R3 i.e. 10.1.3.X). Oracle HTTP server in R12.2 is 11.1.1.4 .

2. Oracle E-Business Suite R12.2 uses Oracle Application Server 10g R3 (10.1.2.3) for Forms & Reports (Note: In previous version of R12 i.e. 12.0.X and 12.1.X, forms are reports are of same version i.e. 10.1.2.3)

3. Default Database for Oracle E-Business Suite R12.2 is 11g R2 (11.2.X) . (Note: In previous version of R12 i.e. 12.0.X, default database is 11.1 and 12.1.X, default database is 11.2.0.3)

4. 12.0.X and 12.1.X Oracle JSP Compiler (OJSP) 10.1.3.5  is replaced by WebLogic JSP Compiler 11.1.1.4 in R12 version 12.2.x

5. In 12.2.x version, a new file "EBSapps.env" is introduced to source the Environment variables that will help to navigate the system.

To support online patching, 12.2 introduces a new database service

To support online patching, 12.2 introduces a new database service.

-service_names

The service_names parameter specifies one or more names by which clients can connect to an instance. The instance registers its service names with the listener. When a client requests a service, the listener determines which instances offer the requested service and then routes the client to the most appropriate instance.

On codelevels lower than AD-TXK Delta 9, the service name is always 'ebs_patch'. From the AD-TXK Delta 9 codelevel, the service name is defined by the the value of the context variable 's_patch_service_name'.

-local_listener

The local_listener setting is part of the AutoConfig templates, and required for listener registration of any non-default (1521) ports.

Database Upgrade High Level Steps From 11g to 12c

Database Upgrade High Level Steps From 11g to 12c.

Manual upgrade process are divided in 3 steps.

Step.1 pre-upgrade
Step.2 actual database upgrade
Step.3 post-upgrade

To perform pre-upgrade steps that you do not require downtime, you must be finished before downtime starts. Before starting upgrade process finish 12c installation on preffered mount point.

Source version: 11.2.0.3
Target version:12.1.0.2

1) Before starting the upgrade make sure Oracle 12c database binary already installed on the database server.
-Choose software only while installing 12chome

2) Check the integrity of the database by running (dbupgdiag.sql script)
-download the Oracle Database Upgrade Diagnostic Utility from support.oracle.com
-Check the invalid objects.
- Run utlrp.sql to validate invalid objects before upgrading process
-Check the duplicate objects owned by sys and system.
-purge recyclebin
-verify installed components status and version.
-check any corruption in data dictionary.

3) Run preupgrade information tool.
-Copy the Pre-Upgrade Information Tool script preupgrd.sql along with utluppkg.sql from the Oracle Database 12chome.
-Run preupgrd.sql
-It will generate below files
*preupgrade.log
*preupgrade_fixups.sql
*postupgrade_fixups.sql

4)  Review preupgrade.log script output.

5) Fix the warnings reported by preupgrade.log file.

6) Execute the preupgrade_fixup.sql
-preupgrade_fixups.sql script will attempt to resolve issues reported by the preupgrade process.
-Issues that cannot be resolved automatically by a fixup script are flagged with ** USER ACTION REQUIRED **.
-Disable cronjob
-check any files in media recovery/backup mode
-Check the timezone version
-Gather dictionary statistics
-Purge the Database RecycleBin Before Upgrading
-Remove EM repository

7) Stopping the 11g database components.

8) Backup the 11g home (preffered cold backup)

9)Set the 12c ENV variables and startup the database with upgrade.
-start with startup upgrade option.
-Run catupgrade script from os level with paralle=6 as below
cd $ORACLE_HOME/rdbms/admin
$ORACLE_HOME/perl/bin/perl catctl.pl -n  6 -l $ORACLE_HOME/diagnostics catupgrd.sql

10)  Run the Post-Upgrade Status Tool
-Execute post upgrade script- utlu121s.sql which provides a summary of the upgrade
-Execute catuppst.sql script
-Download the dst upgrade script from oracle
-Once dst upgrade is successful , validate the time_zone(It should be 18)
-Run postupgrade_fixup.sql, The postupgrade_fixups.sql script is created to address issues that can be fixed after the database has been upgraded.
-Change the ORACLE_HOME to 12c in listener.ora file.
-Run utlrp.sql
-Update the compatible parameter and restart database.

Re-organization Activity

Re-organization Activity

Reorganization is very useful in order to reduce space used by blocks and it also helps in improving the performance of the Oracle Database. It also helps to reduce the fragmentation.

There are 3 ways to do re-organization activity:

1.Export/Import.
2.Alter table Move.
3.CTAS method.

Schema Refresh

Schema Refresh

Schema refresh are of two types, they are:

1. Refresh the database schema with production database.
2. Refresh the database schema from production to some other databsae like DEV/TEST.

Steps:
-Find the roles & privileges that are assigned to the schema.
-Capture source database schema objects count.
-Export database schema using EXP/EXPDP utililty.
-Recreate the schema with default tablespaces and allocate quota.
-Make required roles & privileges for the schema.
-Import the dump file using IMP/IMPDP into the target database.
-Recompile invalid objects.
-Gather schema statistics after the refresh.

Oracle Enterprise Manager Comes In 3 Flavors

Oracle Enterprise Manager Comes In 3 Flavors

-Database control
-Grid control
-Cloud control

Database Control: Using database control you can manage only one database. If you want to administer more than one database, then you must configure a seperate database control (OEM) for each database, otherwise you can go for grid/cloud control configuration.

Grid control: Using grid control you can monitor you whole infrastructure; i.e. you can manage more that one databases. Grid control is responsible for monitoring all targets and collects information on the Oracle databases, application servers, listeners  hardware, operation system and third party softwares. Grid control is now obsolete.

Cloud control: cloud control is the latest release to manage and monitor multiple hosts, it provides much better management features for entire oracle and non-oracle databases.

Major Differences Between DBCA & EMCA

Major Differences Between DBCA & EMCA

DBCA does not provide any options to re-configure the DBcontorl.
But EMCA can perform all possible customizations for existing DBcontrol.
E.g. drop dbconsole, recreate dbconsole, upgrade, etc...

Automated Maintenance Task

Automated Maintenance Task

In 11g, There are 3 main automated maintenance tasks in every database enabled by default:

-Automatic Optimizer Statistics Collection – Gathers stale or missing statistics for all schema objects. The task name is ‘auto optimizer stats collection’.
-Automatic Segment Advisor – Identifies segments that could be reorganized to save space. The task name is ‘auto space advisor’.
-Automatic SQL Tuning Advisor – Identifies high load SQL The task name is ‘sql tuning advisor’

These tasks can run up to 20 hours on Saturdays & Sundays utilizing a good portion of your hardware.

Oracle E-Business 12.2 Installation

Oracle E-Business 12.2 Installation

Disk space

Fresh- PROD 180gb
Vision 350gb

Software Required:

Oracle Enterprise Linux 5.7 (64-bit)
Oracle E-Business suite R12.2 for LinuxX86-64-bit

Hardware Requirement:

Databases Node:
Operating System : Oracle Enterprise Linux 5.7 64bit
Memory               : 16 GB
Hostname : delta001db.oracle.com
IP Address           : 192.168.1.110

Applications Node:
Operating System : Oracle Enterprise Linux 5.2 64bit
Memory : 16 GB
Hostname : delta001app.oracle.com
IP Address : 192.168.1.111

Prerequisite Steps:

1.create OS group, user and directories:

groupadd dbaerp
useradd -g dbaerp oracle
useradd -g dbaerp applmgr

Changing password for user oracle and applmgr.
passwd oracle
passwd applmgr

2.create directories and change permissions:

mkdir -p /u01/ora_prod
mkdir -p /u01/appl_prod
chmod -R 775 /u01/*_prod
chown -R oracle:dbaerp /u01/ora_prod
chown -R applmgr:dbaerp /u01/appl_prod

3.configure kernel parameters (Edit /etc/sysctl.conf file):

#All below kernel parameters are related to oracle EBS - R12.2#################kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmall = 268435456
kernel.shmmax = 429496729
kernel.shmmni = 4096
kernel.sem = 256 32000 100 142
fs.file-max = 327679
net.ipv4.ip_local_port_range = 10000 65000
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_max = 4194304
:wq

[root@delta001 Server]# sysctl -p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmall = 268435456
kernel.shmmax = 429496729
kernel.shmmni = 4096
kernel.sem = 256 32000 100 142
fs.file-max = 327679
net.ipv4.ip_local_port_range = 10000 65000
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_max = 4194304

5.Verify and change Domain Name System (DNS) Resolver Parameters

Two Domain Name System (DNS) resolver parameters (timeout and attempts) are set by default to low values when the operating system is installed. These low values may cause attempted network connections to an Oracle database to fail. If this happens, add or update the following entries to these minimum settings in the /etc/resolv.conf file on each server node:

options attempts:5
options timeout:15

6.Modifying the Number of Open File Descriptors open the /etc/security/limits.conf file and change the existing values for "hard" and "soft" parameters as follows. Restart the system after making changes.

Note: If the current value for any parameter is higher than the value listed in this document, then do not change the value of that parameter.

* hardnofile 65535
* softnofile 4096
* hardnproc 16384
* softnproc 2047

7.Make sure all OS packages exists on the system.

To Check the Package is installed
Use:  rpm –q <pkgname>

To Install the required package
Use: rpm –i<pkg file name>

To Erase the package
Use: rpm –e <pkg name>

The following packages should exists on system for a successful Installation.

openmotif21-2.1.30-11.EL5.i3861
xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386

8.checking swap memory should be 16GB or more (20GB is configured)

[root@delta001 ~]# grep SwapTotal /proc/meminfo
SwapTotal:      20482864 kB
[root@delta001 ~]#

9.Verify /etc/hosts file. It should be configured with fully qualified domain name

[root@delta001 ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
192.168.1.100           detlta001.oracle.com delta001

10.create Inventory and grant 775 permission to Inventory directory

[root@delta001 ~]# cat /etc/oraInst.loc
inventory_loc=/u01/ora_prod/oraInventory/
[root@delta001 ~]# mkdir -p /u01/ora_prod/oraInventory/

11.Verify that the /etc/sysconfig/network file is formatted as follows:

[root@delta001 Server]# more /etc/sysconfig/network
NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=detlta001.oracle.com

12.Create soft link for library as below for 10.1.2 Server:

[root@delta001 Server]# ls -lrt /usr/lib/libXtst.so.6
lrwxrwxrwx 1 root root 16 Sep 29 21:48 /usr/lib/libXtst.so.6 -> libXtst.so.6.1.0
[root@delta001 Server]# unlink /usr/lib/libXtst.so.6
[root@delta001 Server]# ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6
[root@delta001 Server]# ls -lrt /usr/lib/libXtst.so.6
lrwxrwxrwx 1 root root 29 Sep 29 23:34 /usr/lib/libXtst.so.6 -> /usr/X11R6/lib/libXtst.so.6.1
[root@delta001 Server]#
[root@delta001 etc]# ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
[root@delta001 etc]#

13.Threading model in Linux should be NPTL

[root@delta001 Server]# getconf GNU_LIBPTHREAD_VERSION
NPTL 2.5
[root@delta001 Server]#

14.Prepare Staging Area:

a) Download all required Parts
b) Unzip startHere CD for getting buildStage.sh
c) Execute bulildStage.sh script for creating Stage

15.Unzip startHere CD for getting buildStage.sh

- Create directory for R12 Stage
- unzip parts of StartHere CD in R12 Staging directory

[root@erpnode2 Oracle E-Business Suite 12.2.2]# ls -lrt V35215-*
-rwxrwx--- 1 root vboxsf   85594608 Sep 24 10:13 V35215-01_2of3.zip
-rwxrwx--- 1 root vboxsf  101976210 Sep 24 10:17 V35215-01_3of3.zip
-rwxrwx--- 1 root vboxsf 1409220447 Sep 24 12:55 V35215-01_1of3.zip
[root@erpnode1 Oracle E-Business Suite 12.2.2]# unzip V35215-01_1of3.zip

- After unzipping all three parts it will create directory startCD

c) Execute bulildStage.sh script for creating Stage:

- This script will be located under "startCD > rapidwiz > bin

[root@erpnode2 Disk1]# cd rapidwiz/
[root@erpnode2 rapidwiz]# ls
bin            driver  File    jlib  oui       RapidWiz.cmd  RapidWizVersion      TechInstallers  unzip
ClientWiz.cmd  etc     images  jre   rapidwiz  RapidWiz.ini  RapidWizVersion.cmd  template        Xpatches
[root@erpnode2 rapidwiz]# cd bin
[root@erpnode2 bin]# ls
adaixchk.sh   adgetreg.exe    buildStage.sh  JNLSLib3.dll  orpass.sql         riwipu.sh     riwTDBup.sql  WizOSD.dll
adchkutl.cmd  AFSCJAV8.pls    checkOS.cmd    JNLSTool.dll  perl510.dll        riwperl.pl    riwTXdis.sh   WTPrereqs.cmd
adchkutl.sh   AFSCJAVS.pls    checkOS.sh     launch.exe    perl.exe           riwTDBup.cmd  runWizard.sh  WTPrereqs.sh
addbptchk.sh  buildStage.cmd  filespace.exe  NMAKE.EXE     racvalidations.sh  riwTDBup.sh   syspass.sql
[root@erpnode2 bin]# sh buildStage.sh


                Build Stage Menu

------------------------------------------------------
1.     Create new stage area
2.     Copy new patches to current stage area.
3.     Display existing files in stage TechPatches.
4.     Exit menu
Enter your choice [4]: 1

         Rapid Install Platform Menu

------------------------------------------------------
1.    Oracle Solaris SPARC (64-bit)
2.    Linux x86-64
3.    IBM AIX on Power Systems (64-bit)
4.    HP-UX Itanium
5.    Exit Menu
Enter your choice [5]: 2

/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java -classpath /media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/emocmutl.jar:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/ewt-3_4_22.jar:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/share-1_1_18.jar:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/jnls.jar:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/ACC.JAR:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/netcfg.jar:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/ojdbc14.jar:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/OraInstaller.jar:/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../jlib/java oracle.apps.ad.rapidwiz.util.StageBuilder /media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin

Please enter the directory containing the zipped installation media:
/media/sf_Oracle_EBS_12.2.2
Unzipping V29764-01.zip
Unzipping V29856-01.zip
Unzipping V35215-01_1of3.zip
Unzipping V35215-01_2of3.zip
Unzipping V35215-01_3of3.zip
Unzipping V35230-01_1of2.zip
Unzipping V35230-01_2of2.zip
Unzipping V35231-01_1of5.zip
Unzipping V35231-01_2of5.zip
Unzipping V35231-01_3of5.zip
Unzipping V35231-01_4of5.zip
Unzipping V35231-01_5of5.zip
Unzipping V35802-01.zip
Unzipping V35803-01_1of3.zip
Unzipping V35803-01_2of3.zip
Unzipping V35803-01_3of3.zip
Unzipping V35804-01_1of2.zip
Unzipping V35804-01_2of2.zip
Unzipping V35805-01_1of2.zip
Unzipping V35805-01_2of2.zip
Unzipping V35806-01_1of3.zip
Unzipping V35806-01_2of3.zip
Unzipping V35806-01_3of3.zip
Unzipping V35807-01.zip
Unzipping V35808-01.zip
unzipping file V35808-01.zip
Unzipping V35809-01.zip
Unzipping V35810-01.zip
Unzipping V35811-01.zip
Unzipping V35812-01.zip
Unzipping V35813-01.zip
Unzipping V36798-01.zip
Unzipping V37515-01_1of6.zip
Unzipping V37515-01_2of6.zip
Unzipping V37515-01_3of6.zip
Unzipping V37515-01_4of6.zip
Unzipping V37515-01_5of6.zip
Unzipping V37515-01_6of6.zip
Unzipping V39211-01.zip
Unzipping V39571-01.zip
Unzipping V39615-01.zip
Unzipping V39664-01.zip
Applying one-off patches
All files have been unzipped.
Stage area is complete.

Done Unzipping shiphome ...
StageBuilder will now stage the tech patches for Linux_x64...
Copying one-off patches to shiphome
/media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../unzip/Linux_x64/unzip -o /media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../Xpatches/Linux_x64.zip -d /media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../../../../TechPatches

Archive:  /media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../Xpatches/Linux_x64.zip
creating: /media/sf_Oracle_EBS_12.2.2/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16303726/

Done Copying additional patches
Verifying stage area...

Directory /media/sf_Oracle_EBS_12.2.2/TechInstallMedia is valid
Directory /media/sf_Oracle_EBS_12.2.2/TechPatches/DB is valid
Directory /media/sf_Oracle_EBS_12.2.2/TechPatches/MiddleTier is valid
Directory /media/sf_Oracle_EBS_12.2.2/EBSInstallMedia/AppDB is valid
Directory /media/sf_Oracle_EBS_12.2.2/EBSInstallMedia/Apps is valid
Directory /media/sf_Oracle_EBS_12.2.2/EBSInstallMedia/AS10.1.2 is valid
Directory /media/sf_Oracle_EBS_12.2.2/TechInstallMedia/database is valid
Directory /media/sf_Oracle_EBS_12.2.2/TechInstallMedia/ohs11116 is valid
Directory /media/sf_Oracle_EBS_12.2.2/TechInstallMedia/wls1036_generic is valid

Stage area verified.

Press enter to continue...

                Build Stage Menu

------------------------------------------------------

1.     Create new stage area
2.     Copy new patches to current stage area.
3.     Display existing files in stage TechPatches.
4.     Exit menu
Enter your choice [4]:     

16.Make sure proper privileges are give to stage directory (755 or 775)

17.Install Oracle E-Business suite R12.2:

- Make sure proper display is configured

18.start the Installation through root user

[root@delta001 rapidwiz]pwd
/u01/Stage/startCD/Disk1/rapidwiz
[root@delta001 rapidwiz]# ./rapidwiz

Default Port Numbers:
node manager         5556
wls admin server 7001
wls oacore port 7201
wls forms 7401
wls oafm         7601
ohs admin 9999
database         1521

Verify Installation:

- Login to Oracle EBS and  verify application access

username=sysadmin
password=sysadmin

Note: after installing the 12.2.2 the default password of sysadmin is sysadmin.

weblogic services:
admin server(admin)

1.forms-c4ws_server1
2.forms_server1
3.oacore_server1
4.oafm_server1

Clone From Production To Development.

Clone From Production To Development

-Make sure preclone scripts already run, if it is not first run preclone on dbTier and appsTier.
-Take the backup of application binaries as well as database backup.
-Mount the backups to the target side, if it is not mounted then do the scp.
-Create blackouts on target side, and send an outage email to business users that this instance is going to clone.
-Shutdown the application services, shutdown the database and startup restrict-mode drop the database, and take backup if required (export-import, pfile, context_file and other config files) sometimes it depends on your project to project)
-On target side untar the binaries of database and prepare the pfile, in pfile keep all the parameters which is there, just add two parameters (db_file_name_convert and log_file_name_convert) which actually convert the filesystem from source to target, and then we do startup nomount (which starts the instance and background processes)
-Now we will run rman duplicate.
-Rman connect auxiliary and run command allocate channels.
-"DUPLICATE" target database to name of the database along with the backup location and then release channels.

what internally rman duplicate will do is?

*it will restore the controlfile from the backup.
*it will mount the database internally (alter database mount).
*it will restore the database.
*it will recover the database.
*and then it will open the database with resetlogs option.

when you open the database with resetlogs, incarnation of the database will be happen, it means

*new logfile sequence number will be assigned and it will be set to 1
*redologfile will be given a new timestamp
*new scn number will be assigned and then your datafile and controlfile will be sync.

-Untar binaries for application side, and then go to common_top/clone/bin and fire perl adcfgclone.pl appsTier.
-Fire perl adcfgclone.pl appsTier context_file=<give cloned instance contextfile>

Post Clone Steps:
* Change the APPS password.
*Cancel the scheduled requests.
*Change the java color and banner.
*Updating workflow mailer status.
*Cleanup the nodes table by running.
EXEC FND_CONC_CLONE.SETUP_CLEAN;.
*Run autoconfig on both the tiers.
*Drop softlinks which are pointing to production
*Do sanity check and release instance for user access.

*Etc.

Why Database Upgrade

Why Database Upgrade

Several Bugs that are causing outages and /or business impacts.

-Upgrade your database because numerous bugs fixed.
-Several new features deployed with higher versions.
-Improved performance and scale-ability for latest versions rather that previous versions.
-Already thousands of customers upgraded their database from lower versions to recent versions.
-Extended support fee can avoided, no bug fixes unless you pay extra fee to get extended support.

Upgrading means the process of changing the data dictionary contents of a database to reflect particular release.

Upgrading from 10.2.x to 11.2.x is a major release upgrade
Ex: 10.2.0.5.0 to 11.2.0.1.0

Upgrading from 10.2.0.x to 10.2.0.x is a patch set upgrade
Ex: 10.2.0.1 to 10.2.0.5

Database Upgrade High Level Steps From 10g to 11g.

Database Upgrade High Level Steps From 10g to 11g.

DBUA - Database Upgrade Assistant - Recommended
MANUAL - Using SQL Scripts & Utilities

Manual upgrade process are divided in 3 steps.
Step.1 pre-upgrade
Step.2 actual database upgrade
Step.3 post-upgrade

To perform pre-upgrade steps that you do not require downtime, you must be finished before downtime starts. Before starting upgrade process finish 11g installation on preffered mount point.

Source version:10.2.0.5
Target version: 11.2.01

1) Before starting the upgrade make sure 11g database binary already installed on the database server.
-install only 11g software in separate location.

2) Check integrity of the source database and sanity operations.
-find duplicate objects in sys and system
-purge recyclebin
-verify installed components status and version.
-fix invalid objects before upgrading process
-check any files in media recovery/backup mode
-Gather dictionary statistics
-check any corruption in data dictionary.

3) Run pre-upgrade information tool
-copy pre-upgrade script utlu112i.sql from 11g home and ran on 10g home

4) Review pre-upgrade script output.

5) Fix the warnings reported by pre-upgraded tool

6) create pfile from spfile and prepare the pfile from 11g home database.
-removing deprecated parameters.
-change compatibility parameter
-set 11g $ORACLE_BASE.
-copy newly created pfile from 10ghome to 11ghome dbs directory.
-Configure ENV file for 11g database.
-Network configuration for 11g
*add new listener with different port number in tnsnames.ora and listener.ora files

7) Stopping 10g database components

8) Backup 10g home (preffered cold backup, because we have downtime)

9) Set 11g ENV variables and startup the database.
-start with startup upgrade option.
-run catupgrd.sql script
-database shutdown automatically after completing the catupgrd.sql script.

10) startup the database and check version.

11) Execute post upgrade script- utlu112s.sql
-Verify upgraded components status and their versions.

12) Perform upgrade actions that changes the database from upgrade mode to normal mode
-run catuppst.sql
-find invalid objects count
-run utlrp.sql script
-verify any invalid objects is fixed or not

13) Upgrade timezone file version

14) Perform post upgrade tasks