Nanda's ORACLE Core & APPS Knowledge Base

How to Turn off / Disable User Account Expiration

2011-10-11T13:12:00.000-07:00

Oracle User Account Expired. How to disable or turn off EXPIRE
===========================================

Issue:

One of the critical User account got expired, expire to be turned off to avoid connection issue on application connectivity

Issue Details:

1. Found User account is about to expire and it is on GRACE Period

SQL> select username,account_status,LOCK_DATE,EXPIRY_DATE,CREATED,PROFILE from dba_users where username='TEST';

USERNAME ACCOUNT_STATUS LOCK_DATE EXPIRY_DATE CREATED PROFILE
------------------------------ -------------------------------- --------------- --------------- --------------- ------------------------------
TEST EXPIRED(GRACE) 18-OCT-11 09-APR-11 DEFAULT

2. Confirmed with profile settings that 180 expiration

SQL> select * from dba_profiles where profile='DEFAULT';

PROFILE RESOURCE_NAME RESOURCE LIMIT
------------------------------ -------------------------------- -------- ----------------------------------------
DEFAULT COMPOSITE_LIMIT KERNEL UNLIMITED
DEFAULT SESSIONS_PER_USER KERNEL UNLIMITED
DEFAULT CPU_PER_SESSION KERNEL UNLIMITED
DEFAULT CPU_PER_CALL KERNEL UNLIMITED
DEFAULT LOGICAL_READS_PER_SESSION KERNEL UNLIMITED
DEFAULT LOGICAL_READS_PER_CALL KERNEL UNLIMITED
DEFAULT IDLE_TIME KERNEL UNLIMITED
DEFAULT CONNECT_TIME KERNEL UNLIMITED
DEFAULT PRIVATE_SGA KERNEL UNLIMITED
DEFAULT FAILED_LOGIN_ATTEMPTS PASSWORD 10
DEFAULT PASSWORD_LIFE_TIME PASSWORD 180

PROFILE RESOURCE_NAME RESOURCE LIMIT
------------------------------ -------------------------------- -------- ----------------------------------------
DEFAULT PASSWORD_REUSE_TIME PASSWORD UNLIMITED
DEFAULT PASSWORD_REUSE_MAX PASSWORD UNLIMITED
DEFAULT PASSWORD_VERIFY_FUNCTION PASSWORD NULL
DEFAULT PASSWORD_LOCK_TIME PASSWORD 1
DEFAULT PASSWORD_GRACE_TIME PASSWORD 7

3. To disable/Turn off the expiration, we need to set profile to UNLIMITED:

SQL> alter profile default limit PASSWORD_LIFE_TIME unlimited;

Profile altered.

4. While Checking the status, it still shows Expiry date as shown earlier, so, what could be cause or reason???

SQL> select username,account_status,CREATED,LOCK_DATE,EXPIRY_DATE,PROFILE from dba_users where username='TEST';

USERNAME ACCOUNT_STATUS CREATED LOCK_DATE EXPIRY_DATE PROFILE
------------------------------ -------------------------------- --------------- --------------- --------------- ------------------------------
TEST EXPIRED(GRACE) 09-APR-11 18-OCT-11 DEFAULT

5. Profile shows UNLIMITED, but why user account did not get effect???

SQL> select resource_name,limit from dba_profiles where profile='DEFAULT';

RESOURCE_NAME LIMIT
-------------------------------- ----------------------------------------
COMPOSITE_LIMIT UNLIMITED
SESSIONS_PER_USER UNLIMITED
CPU_PER_SESSION UNLIMITED
CPU_PER_CALL UNLIMITED
LOGICAL_READS_PER_SESSION UNLIMITED
LOGICAL_READS_PER_CALL UNLIMITED
IDLE_TIME UNLIMITED
CONNECT_TIME UNLIMITED
PRIVATE_SGA UNLIMITED
FAILED_LOGIN_ATTEMPTS 10
PASSWORD_LIFE_TIME UNLIMITED

RESOURCE_NAME LIMIT
-------------------------------- ----------------------------------------
PASSWORD_REUSE_TIME UNLIMITED
PASSWORD_REUSE_MAX UNLIMITED
PASSWORD_VERIFY_FUNCTION NULL
PASSWORD_LOCK_TIME 1
PASSWORD_GRACE_TIME 7

16 rows selected.

6. Tried resetting the profile again to user, but no luck... :-(

SQL> alter user TEST profile default;

User altered.

SQL> select username,account_status,CREATED,LOCK_DATE,EXPIRY_DATE,PROFILE from dba_users where username='TEST';

USERNAME ACCOUNT_STATUS CREATED LOCK_DATE EXPIRY_DATE PROFILE
------------------------------ -------------------------------- --------------- --------------- --------------- ------------------------------
TEST EXPIRED(GRACE) 09-APR-11 18-OCT-11 DEFAULT

7. Tried setting account unlock...but still no luck....

SQL> alter user TEST account unlock;

User altered.

SQL> select username,account_status,CREATED,LOCK_DATE,EXPIRY_DATE,PROFILE from dba_users where username='TEST';

USERNAME ACCOUNT_STATUS CREATED LOCK_DATE EXPIRY_DATE PROFILE
------------------------------ -------------------------------- --------------- --------------- --------------- ------------------------------
TEST EXPIRED(GRACE) 09-APR-11 18-OCT-11 DEFAULT

SOLUTION:

8. Then found that, when user is already in GRACE Period, even altering profile, will NOT take effect until the password is changed

Setting the PASSWORD_LIFE_TIME Profile Parameter to a Low Value

Be careful if you plan to set the PASSWORD_LIFE_TIME parameter of CREATE PROFILE or ALTER PROFILE to a low value (for example, 1 day). If the user who is assigned this profile is concurrently logged in when you make this modification, then Oracle Database sets the user's account status from OPEN to EXPIRED(GRACE)with the warning error ORA-28002: the password will expire within n days. You may not be notified of this change because the user can still connect to the Oracle database. You can find the concurrently logged in users by querying the USERNAME column of the V$SESSION dynamic performance view.

Note the following:

If the user is not logged in when you set PASSWORD_LIFE_TIME to a low value, then the user's account status does not change when the user does log in.

You can set the PASSWORD_LIFE_TIME parameter to UNLIMITED, but this only affects accounts that have not entered their grace period. If the user has already entered the grace period, then he or she must change the password.

Ref: http://download.oracle.com/docs/cd/B28359_01/network.111/b28531/authentication.htm#i1007339

SQL> alter user TEST identified by test;

User altered.

SQL> select username,account_status,CREATED,LOCK_DATE,EXPIRY_DATE,PROFILE from dba_users where username='TEST'

USERNAME ACCOUNT_STATUS CREATED LOCK_DATE EXPIRY_DATE PROFILE
------------------------------ -------------------------------- --------------- --------------- --------------- ------------------------------
TEST OPEN 09-APR-11 DEFAULT

Alert Log : Diskgroup Mounted & Dismounted

2011-10-10T08:50:00.000-07:00

I could see the following messages in Alertlog , was curious to know the reason behind it…

Mon Oct 10 11:49:00 2011
SUCCESS: diskgroup ARCH_QA was mounted
SUCCESS: diskgroup ARCH_QA was dismounted
SUCCESS: diskgroup ARCH_QA was mounted
SUCCESS: diskgroup ARCH_QA was dismounted
Mon Oct 10 11:50:00 2011
SUCCESS: diskgroup ARCH_QA was mounted
SUCCESS: diskgroup ARCH_QA was dismounted
SUCCESS: diskgroup ARCH_QA was mounted
SUCCESS: diskgroup ARCH_QA was dismounted
Mon Oct 10 11:51:00 2011
SUCCESS: diskgroup ARCH_QA was mounted
SUCCESS: diskgroup ARCH_QA was dismounted
SUCCESS: diskgroup ARCH_QA was mounted
SUCCESS: diskgroup ARCH_QA was dismounted

This is expected behavior. The messages you see are not errors (that is why they are prefixed with "SUCCESS"). The database instance is creating and then closing archive logs one at a time in the ARCH_QA disk group. Whenever a database closes its last file in a disk group, it dismounts the disk group. Whenever a database accesses a disk group when it does not have any other files open in the disk group, it mounts the disk group.

If you do not want to see the log messages frequently, you can put a mirrored control-file, or mirrored online redo, or dummy online tablespace data file on the diskgroup. This message will not be output frequently in this case. Because CKPT keeps opening a control-file, LGWR keeps opening an online redo, DBW keeps opening an online tablespace data file. So, the diskgroup is not dismounted until the database shutdown.

TailPiece: we get this messages only for respective ASM disk groups for archive logs are written and in a high number

Ref: Why FRA Diskgroup Gets Mounted/Dismounted ? [ID 603204.1]

Cross Platform Database : Best Approach

2011-10-07T07:52:00.000-07:00

How to Move Huge Database from Sun to Linux : Best Approach

You wanna transfer your huge database cross platform sun to linux ??

Lets Look at the options:

1. Best Option : RMAN

RMAN Cross-Platform Transportable Databases and Tablespaces

2. Other Options:

Export/Import
Datapump : Expdp/Impdp
Transport tablespace

Please share your ideas,best methods/practice ....

All About ADI in Oracle Applications

2011-10-06T06:29:00.000-07:00

What is ADI? How this is used? Let's see the complete details about it...

Oracle ADI is a spreadsheet-based extension to Oracle Applications that offers full cycle accounting and asset management within the comfort and familiarity of a spreadsheet. Oracle ADI combines a spreadsheet’s ease of use with the power of Oracle Applications, to provide true desktop integration during every phase of your accounting cycle. You can create budgets, record transactions, add assets, reconcile inventory, and run financial statements and inventory reports all without leaving your spreadsheet.

You can run Oracle ADI as a stand-alone application, without installing the full client version of Oracle General Ledger (GL) or Oracle Assets on your PC. This gives you the ability to confirm and reconcile inventory, revise budgets, create journal entries, and define financial and asset reports from any location, without being connected to your server. You only need to connect when you want to transfer data to or from Oracle Applications.

Figure describes how ADI integrates with other applications.

Oracle ADI Key Features
Oracle ADI key features are as follows:
■ Budget Wizard, Journal Wizard, Report Wizard, and Analysis Wizard to
simplify your work with GL.
■ Account Hierarchy Editor to graphically create, maintain, and review account
structure hierarchies.
■ Spreadsheet-based interface to simplify asset creation and physical inventory
process.
■ Request Center for submitting, monitoring, and publishing your reports.

Oracle ADI Integrations
Oracle ADI integrates with the following modules:
Oracle General Ledger
GL is a comprehensive financial management solution that enhances financial
controls, data collection, information access, and financial reporting throughout the
enterprise. It is part of the Oracle E-Business Suite, an integrated set of applications
that are engineered to work together.
Oracle Assets
Oracle Assets is a comprehensive asset management solution that ensures
maintenance of accurate property and equipment inventory as well as optimal
accounting and tax strategies. It is part of the Oracle E-Business Suite, an integrated
set of applications that are engineered to work together.

Ref: http://download.oracle.com/docs/cd/B15436_01/current/acrobat/115csadiug.pdf

EBS 11i Application Desktop Integrator (ADI) Certified on 10gR2 Database

Client Applications Desktop Integrator (ADI) is now certified with Oracle E-Business Suite Release 11i running on the 10gR2 Database. Customers may continue using the client-installed ADI even after upgrading their E-Business Suite Release 11i environment to the 10gR2 Database.

This certification applies to all ADI functionality, including:

General Ledger Journal Wizard
Budget Wizard
Report Wizard
Analysis Wizard
Account Hierarchy Editor
Request Center
Assets Integrators

Note that this certification applies only to Client ADI with Applications 11i. Client ADI cannot be used with Oracle E-Business Suite Release 12; webADI is available for Release 12 users.

For more details (and a useful Frequently Asked Questions summary for ADI), see:

Client ADI for EBS 11i is Certified with 10g (Metalink Note 747386.1)

Ref: http://blogs.oracle.com/stevenChan/entry/ebs_11i_application_desktop_integrator_10gr2_certification

Unable to View Concurrent Requests Ouput Files

2011-10-05T05:18:00.000-07:00

ISSUE:

"Unable to view Concurrent Requests log/output files"..

We are running 11.5.10.2 and recently did a clone of production to test. However, in the test environment when I run a concurrent request I am no longer able to view the logs or outputs through Oracle.

ERROR

An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_TESTDB There may be a network configuration problem, or the TNS listener on node FNDFS_TESTDB may not be running. Please contact your system administrator.

CHECKING:

a) Check whether Concurrent Request log & Output files generated in $APPLCSF/log & $APPLCSF/out to confirm this is NOT Concurrent issue

RESEARCH:

• ADI: Unable To View Reports In ADI [ID 1018797.102]
• How To Set RRA:Service Prefix for Multiple Instances on One Server [ID 235785.1]
• Tracing the sqlnet connection in ADI [ID 223136.1]
• Troubleshooting the "Error Occurred While Attempting to Establish an Applications
File Server Connection" [ID 117012.1]

SOLUITION Path:

1. Perform the RRA Setup Diagnostic Test

This Step will identify all Profile Settings & TNSNames.ora,Hostname in
FND_CONCURRENT_QUEUES table in one go.

Ref: 11i : Oracle Application Object Library Report Review Agent Setup Test
[ID 200358.1]

Command-Line Usage Instructions

• If the latest Oracle Diagnostics patch has been installed, this diagnostic script
is already available on your system. Change directory to $IZU_TOP/bin and execute
the test from there.

• If the latest Oracle Diagnostics patch has not been installed, download and unzip
the latest Oracle Diagnostics patch (see Note 167000.1)
Once unzipped, the Oracle Diagnostics patch can be installed in the normal way
using adpatch (see Note 167000.1) or the test can be executed directly from the
patch directory. Change directory to /izu/bin and execute the test
from there.

• Run the test as follows:

UNIX
$ ./FNDValidateFNDFS115.sh

Windows NT/2000
> sh FNDValidateFNDFS115.sh

2. CrossCheck for multiple Node Name

Verify that the nodename specified in the FNDFS_ entry is the
same as the nodename in the above error message. This should also match the
node name returned from the following select statement:

SQL> select distinct LOGFILE_NODE_NAME
from FND_CONCURRENT_REQUESTS;

3. If this is Cloned Instance from PROD, then check whether any profile values still
pointing to PROD

SQL> select a.profile_option_value,b.profile_option_name from
fnd_profile_option_values a , fnd_profile_options b
where a.profile_option_id=b.profile_option_id
and upper(profile_option_value) like '%PROD%' ;

SQL> select * from fnd_profile_options where profile_option_id=&ID;
SQL> select * from fnd_profile_option_values where profile_option_id=&ID;

4. Mostly issue could be either RRA Profile setting issue or any other profile
setting pointing to PROD

Oracle APPS : Workflow Tables

2011-09-29T10:27:00.000-07:00

Oracle Applications - Workflow Tables (Quick Review)

Important WF Tables:

wf_user_role_assignments
wf_user_roles
wf_roles
wf_items
wf_item_attributes
wf_item_attribute_values
wf_item_attributes_tl
wf_activities
wf_activities_tl
wf_activity_attributes
wf_activity_attributes_tl
wf_activity_transitions
wf_deferred--wf_control

WF_NOTIFICATION_ATTRIBUTES
WF_MESSAGES
WF_MESSAGES_TL
WF_MESSAGE_ATTRIBUTES
WF_MESSAGE_ATTRIBUTES_TL
WF_ETS
WF_PROCESS_ACTIVITIES

WF_ACTIVITIES table stores the definition of an activity. Activities can be Processes, notifications, functions or folders. A process activity is a modelled workflow process, which can be included as an activity in other processes to represent a subprocess. A notification activity sends a message to a performer. A functions activity performs an automated function that is written as a PL/SQL stored procedure. A folder activity is not part of a process, it provides a means of grouping activities.

WF_ITEMS is the runtime table for workflow processes. Each row defines one work item within the system.

WF_ITEM_ATTRIBUTES table stores definitions of attributes associated with a process. Each row includes the sequence in which the attribute is used as well as the format of the attribute data.

WF_NOTIFICATIONS holds the runtime information about a specific
instance of a sent message. A new row is created in the table each time a message is sent.

DBA_Objects shows identical object on same schema?

2011-09-15T06:57:00.000-07:00

MATERIALIZED VIEW
=================

Whenever a Materialized view created, you should see 2 entries in dba_objects with same name. Because, it creates a table(segment) and a materialized view.
So, We should NOT get confused that why 2 objects has same name on same schema.

SQL> create materialized view mv1 as select * from i;
Materialized view created.

SQL>select object_name,object_id,data_object_id,object_type,status from dba_objects where object_name='MV1'

OBJECT_NAME OBJECT_ID DATA_OBJECT_ID OBJECT_TYPE STATUS
------------------------------ ---------- -------------- ------------------- -------
MV1 4838577 4838577 TABLE VALID
MV1 4838579 MATERIALIZED VIEW VALID

SQL> alter MATERIALIZED VIEW MV_MOVEMENT_PROCESSES compile;

SQL> execute dbms_mview.refresh('MINE1.MV_MOVEMENT_PROCESSES');
PL/SQL procedure successfully completed.

Im Back!!

2011-08-21T09:15:00.001-07:00

Hi All,

I m back to my Blog after a long gap.
You will see my intensive knowledge sharing all my experience in the recent past.

Your Suggestions & Contributions are most welcome!!!

Happy Knowledge Sharing.....

Why there is a diff btwen DBA_SEGMENTS & DATAPUMP of particular schema size

2009-01-08T03:27:00.001-08:00

Why there is a difference between DBA_SEGMENTS & DataPUMP of size of particular schema
======================================================================================

1. SELECT SUM(bytes)/1024/1024/1024 AS size_gig FROM DBA_SEGMENTS WHERE OWNER= 'XXX';

2. $ expdp estimate_only=y schemas=xxx

In Common, data pump export would show less value than the size computed from dba_segments/extents

ESTIMATE_ONLY - Use this parameter to estimate the required export file size without starting an actual export job.
ESTIMATE - The ESTIMATE parameter will tell you how much space your new export job is going to consume.
Estimate_only shows the export dump file size not a schema size.

Also, DBA_SEGMENTS contains INDEX segments too,

So, The following query may give you close result

select sum(bytes)/1024/1024/1024 as size_gig, segment_type
from dba_segments
where owner='ENDUR01'
group by segment_type;

How to get the Schema/User size

2009-01-07T23:08:00.000-08:00

In SQLPLUS run any of the following scripts to find the total size occupied by a particular schema.

1.

SQL> SELECT sum(bytes)/1024/1024 FROM user_segments;

The output above query would be similar as follows:

SUM(BYTES)/1024/1024
——————–
2552.75

-- OR --

2.

SQL> SELECT tablespace_name, Sum(bytes)/1024/1024 AS total_size_mb
FROM dba_segments
WHERE owner = Upper(&User_Name)
GROUP BY owner, rollup(tablespace_name)

-- OR --

3. To be more precise on particular table which excluding index,lob segments etc

SQL> SELECT sum(bytes)/1024/1024/1024 as size_gig, segment_type
FROM dba_segments
WHERE owner='XXX'
GROUP BY segment_type;

RAC for Beginners

2008-12-31T22:51:00.000-08:00

Real Application Clusters (RAC)

Oracle RAC, introduced with Oracle9i, is the successor to Oracle Parallel Server (OPS). Oracle RAC allows multiple instances to access the same database (storage) simultaneously. RAC provides fault tolerance, load balancing, and performance benefits by allowing the system to scale out, and at the same time since all nodes access the same database, the failure of one instance will not cause the loss of access to the database.

Oracle RAC 10g is a shared disk subsystem. All nodes in the cluster must be able to access all of the data, redo log files, control files and parameter files for all nodes in the cluster. The data disks must be globally available in order to allow all nodes to access the database. Each node has its own redo log file(s) and UNDO tablespace, but the other nodes must be able to access them (and the shared control file) in order to recover that node in the event of a system failure.

The difference between Oracle RAC and OPS is the addition of Cache Fusion. With OPS a request for data from one node to another required the data to be written to disk first, then the requesting node can read that data. With cache fusion, data is passed along a high-speed interconnect using a sophisticated locking algorithm.

With Oracle RAC 10g, the data files, redo log files, control files, and archived log files reside on shared storage on raw-disk devices, a NAS, ASM, or on a clustered file system

Oracle RAC is composed of two or more database instances.
They are composed of Memory structures and background processes same as the single instance database.

Oracle RAC instances use two processes

==> GES(Global Enqueue Service)
==> GCS(Global Cache Service) this enable cache fusion.

Oracle RAC instances are composed of following background processes:

ACMS—Atomic Controlfile to Memory Service (ACMS)
GTX0-j—Global Transaction Process
LMON—Global Enqueue Service Monitor
LMD—Global Enqueue Service Daemon
LMS—Global Cache Service Process
LCK0—Instance Enqueue Process
RMSn—Oracle RAC Management Processes (RMSn)
RSMN—Remote Slave Monitor

LMON

The background Global Enqueue Service Monitor (LMON) monitors the entire cluster to manage global resources. LMON manages instance and process failures and the associated recovery for the Global Cache Service (GCS) and Global Enqueue Service (GES). In particular, LMON handles the part of recovery associated with global resources. LMON-provided services are also known as cluster group services (CGS)

This process monitors global enques and resources across the cluster and performs global enqueue recovery operations.This is called as Global Enqueue Service Monitor.

LCKx

The LCK process manages instance global enqueue requests and cross-instance call operations. Workload is automatically shared and balanced when there are multiple Global Cache Service Processes (LMSx).

This process is called as Instance enqueue process.This process manages non-cache fusion resource requests such as libry and row cache requests.

LMSx

The Global Cache Service Processes (LMSx) are the processes that handle remote Global Cache Service (GCS) messages. Current Real Application Clusters software provides for up to 10 Global Cache Service Processes. The number of LMSx varies depending on the amount of messaging traffic among nodes in the cluster. The LMSx handles the acquisition interrupt and blocking interrupt requests from the remote instances for Global Cache Service resources. For cross-instance consistent read requests, the LMSx will create a consistent read version of the block and send it to the requesting instance. The LMSx also controls the flow of messages to remote instances.

This process is called as Global Cache service process.This process maintains statuses of datafiles and each cahed block by recording information in a Global Resource Dectory(GRD).This process also controls the flow of messages to remote instances and manages global data block access and transmits block images between the buffer caches of different instances.This processing is a part of cache fusion feature.

LMDx

The Global Enqueue Service Daemon (LMD) is the resource agent process that manages Global Enqueue Service (GES) resource requests. The LMD process also handles deadlock detection Global Enqueue Service (GES) requests. Remote resource requests are requests originating from another instance.

This process is called as global enqueue service daemon. This process manages incoming remote resource requests within each instance.

DIAG

The diagnose daemon is a Real Application Clusters background process that captures diagnostic data on instance process failures. No user control is required for this demo.

ACMS

ACMS stands for Atomic Controlfile Memory Service.In an Oracle RAC environment ACMS is an agent that ensures a distributed SGA memory update(ie)SGA updates are globally committed on success or globally aborted in event of a failure.

GTX0-j

The process provides transparent support for XA global transactions in a RAC environment.The database autotunes the number of these processes based on the workload of XA global transactions.

RMSn

This process is called as Oracle RAC management process.These pocesses perform managability tasks for Oracle RAC.Tasks include creation of resources related Oracle RAC when new instances are added to the cluster.

RSMN

This process is called as Remote Slave Monitor.This process manages background slave process creation andd communication on remote instances. This is a background slave process.This process performs tasks on behalf of a co-ordinating process running in another instance.

CRS

CRS (Cluster Ready Services) is a new feature for 10g Real Application Clusters that provides a standard cluster interface on all platforms and performs new high availability operations not available in previous versions. CRS manages cluster database functions including node membership, group services, global resource management, and high availability. CRS serves as the clusterware software for all platforms. It can be the only clusterware or run on top of vendor clusterware such as Sun Cluster, HP Serviceguard, etc.

CRS automatically starts the following resources:
· Nodeapps
o Virtual Internet Protocol(VIP) address for each node
o Global Services Daemon
o Oracle Net Listeners
o Oracle Network Services (ONS)
· Database Instance
· Services

Oracle Clusterware (Cluster Ready Services in 10g/ Cluster Manager in 9i) - provides infrastructure that binds multiple nodes that then operate as single server. Clusterware monitors all components like instances and listeners. There are two important components in Oracle clusterware, Voting Disk and OCR (Oracle Cluster Registry)

OCR & Voting Disk

Oracle, 10g RAC, provided its own cluster-ware stack called CRS. The main file components of CRS are the Oracle Cluster Repository (OCR) and the Voting Disk.
The OCR contains cluster and database configuration information for RAC and Cluster Ready Services (CRS). Some of this information includes the cluster node list, cluster database instance-to-node mapping information, and the CRS application resource profiles. The OCR contains configuration details for the cluster database and for high availability resources such as services, Virtual Inerconnect Protocoal (VIP) addresses.

The Voting Disk is used by the Oracle cluster manager in various layers. The Node Monitor (NM) uses the Voting Disk for the Disk Hearbeat, which is essential in the detection and resolution of cluster "split brain".

Cache Fusion:-

Oracle RAC is composed of two or more instances. When a block of data is read from datafile by an instance within the cluster and another instance is in need of the same block,it is easy to get the block image from the insatnce which has the block in its SGA rather than reading from the disk. To enable inter instance communication Oracle RAC makes use of interconnects. The Global Enqueue Service(GES) monitors and Instance enqueue process manages the cahce fusion

Cache Fusion and Global Cache Service (GCS)
Memory-to-memory copies between buffer caches over high-speed interconnects

· fast remote access times
· memory transfers for write or read access
· transfers for all types (e.g data, index, undo, headers )
· Cache coherency across the cluster
· globally managed access permissions to cached data
· GCS always knows whether and where a data block is cached
· a local cache miss may result in remote cache hit or disk read

@@@ Article is still under edit... will be adding more info @@@@

11g RAC

2008-12-29T21:57:00.000-08:00

Oracle Real Application Clusters

Learn More about 11g RAC and its New Features, Refer the following ORACLE official Site for 11g RAC

Oracle Real Application Clusters 11g

The Courseware,materials * Guides needed for OCA/OCP/OCE Exam Preparation

2008-12-26T21:08:00.000-08:00

Oracle Certifications are one of most recognized and value certification to acquire to add more weightage to your profile.

These Certifications not only provides you knowledge and also gives better scope to get good opportunities in the Industry

The experience and recognition i am getting on these certifications is immensive.
I am certified on Oracle 9i and 10g OCA/OCP/OCE and 10g OCM on Oracle Database Product.
So, The following information on these certification may useful to many people who aspire to build career in ORACLE Technology.

The following tips may be useful to attain these certifications:

1. First and Foremost thins is, You need to attend the Oracle University Course to
understand the technology and concepts of Oracle Database for particular Version.

2. It is suggested to use the Oracle official Material/Student Guide to get better
understanding of the concepts and features

3. The Course Material / Oracle ITL materials have set of Theory & Practical
questions which would help you understand & Test your knowledge on the product
before proceeding for OCP/OCE Certifications.

4. The Oracle course ware are made in simple english and very easy to understand,
and have very précised and handy information.

5. You may also practice exams of Self Test Software and Transcender are
recommended for preparing the OCA/OCP/OCE Exams.

6. The OCA/OCP/OCE Exams are Objective Type, so it is easy to choose the right
answer for each question

7. Except OCM, remaining all Oracle Certifications are objective type which are
binded with some practical related questions but there is no practical involved

8. The OCP/OCE questions are very tricky and confusing one each answers, so it is
advised to understand the concepts better to choose the right answer

9. DO NOT mug up or Copy the practice exam questions and answers, instead try
understanding the question and the answer.

Here is link for Oracle Student Guides/ILT (Instructor Led Training) Materials

# Where to get Student Guides/ILT (Instructor Led Training) Materials

# To know more about ORACLE Database OCA/OCP/OCE on all Database versions

# ORACLE Suggests ==> Self Test Software and Transcended Test engines

# For any suggestions, tips, experience of Others on OCA/OCP/OCE
Refer OCP Blog ==> ORACLE CERTIFIED PROFESSIONALS

# OTN Forum for Oracle Certifications

# Oracle Magazine Inside OCP Columns

# Oracle Certification Preparation (OCP)/Hidden Treasures

All the Best !! for better career through ORACLE!
Blog me anytime for any tips/suggestions :)

Oracle Database OCA OCP OCE OCM

2008-12-26T21:00:00.000-08:00

Oracle Certification Program - Oracle Database

Oracle Database 11g
Oracle Database 10g
Oracle9i Database
News and Information

Database and Grids

2008-12-26T20:55:00.000-08:00

The Courses and Certifications Offered for Database and Grids

Select a topic to view a course listing and its related categories.

* Oracle Database 11g
* Oracle Database 10g
* 9i Database
* 8i Database
* Oracle Enterprise Manager 10g

* Oracle Enterprise Manager 9i
* Oracle Application Testing Suite
* 9i Lite
* Oracle Berkeley
* Oracle TimesTen

For More Details, Refer the Official ORACLE Education Link ==> Database and Grids

Oracle Certification

2008-12-26T20:48:00.000-08:00

The following Link is official Oracle Site for all ORACLE Product Certification and courses offered by Oracle University

ORACLE UNIVERISTY - Courses & Certifications on all ORACLE Products

How to change the database listener port with EBS system

2008-12-26T02:54:00.000-08:00

How to change the database listener port with EBS system

1. In dbtier xml file under /appsutil change the below line to reflect
the right port

1541

2. In /network/admin/

change the prot values manually in listener.ira and tnsnames.ora

3. Run autoconfg in db tier. if it completes perform the following

4. In apps tier xml file under /admin change the below line to reflect the
right port

1541

5. Run autoconfig in apps tier

How to enable the multi-lingual option for some modules in R12

2008-12-26T02:40:00.000-08:00

How to enable the multi-lingual option in R12
=============================================

Refer the following Metalink notes:

Note 252422.1:Requesting Translation Synchronization Patches
Note 550206.1:Oracle Applications NLS Release Notes, Release 12.0.4

Implementing Dataguard on 11g RAC

2008-12-25T21:27:00.000-08:00

Creating RAC Standby Database

Configuration Details:

• Primary Host Names are RAC_PRIM01 and RAC_PRIM02

• Standby Host Names are RAC_STDBY01 and RAC_STDBY02

• The primary database is RAC_PRIM

• Virtual Names are RAC_PRIM01-vip, RAC_PRIM02-vip, RAC_STDBY01-vip and RAC_STDBY02-vip

• Both the primary and standby databases use ASM for storage

• The following ASM disk groups are being used +DATA (for data) and +FRA for Recovery/Flashback

• The standby database will be referred to as RAC_STDBY

• Oracle Managed Files will be used.

• ORACLE_BASE is set to /u01/app/oracle

1. Configure Primary and Standby sites

For Better and Simpler configuration of Data Guard, it is recommended that the Primary and Standby machines have exactly the same structure, i.e.

• ORACLE_HOME points to the same mount point on both sites.
• ORACLE_BASE/admin points to the same mount point on both sites.
• ASM Disk Groups are the same on both sites

2. Install Oracle Software on each site.

• Oracle Clusterware

• Oracle database executables for use by ASM

• Oracle database executables for use by the RDBMS

3. Server Names / VIPs

The Oracle Real Application Clusters 11g virtual server names and IP addresses are used and maintained by Oracle Cluster Ready Services (CRS).

Note: Both short and fully qualified names will exist.

Server Name/Alias/Host Entry Purpose
RAC_PRIM01.local Public Host Name (PRIMARY Node 1)
RAC_PRIM02.local Public Host Name (PRIMARY Node 2)
RAC_STDBY01.local Public Host Name (STANDBY Node 1)
RAC_STDBY02.local Public Host Name (STANDBY Node 2)
RAC_PRIM01-vip.local Public Virtual Name (PRIMARY Node 1)
RAC_PRIM02-vip.local Public Virtual Name (PRIMARY Node 2)
RAC_STDBY01-vip.local Public Virtual Name (STANDBY Node 1)
RAC_STDBY02-vip.local Public Virtual Name (STANDBY Node 2)

4. Configure Oracle Networking

4.1 Configure Listener on Each Site

Each site will have a listener defined which will be running from the ASM Oracle Home. The following listeners have been defined in this example configuration.

Primary Role
Listener_RAC_PRIM01
Listener_RAC_PRIM02
Listener_RAC_STDBY01
Listener_RAC_STDBY02

4.2 Static Registration

Oracle must be able to access all instances of both databases whether they are in an open, mounted or closed state. This means that these must be statically registered with the listener.

These entries will have a special name which will be used to facilitate the use of the Data Guard Broker, discussed later.

4.3 Sample Listener.ora

LISTENER_RAC_STDBY01 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY01-vip)(PORT = 1521)
(IP = FIRST))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY01)(PORT = 1521)
(IP = FIRST))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
)
)
)
SID_LIST_LISTENER_RAC_STDBY01 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME=RAC_STDBY_dgmgrl.local)
(SID_NAME = RAC_STDBY1)
(ORACLE_HOME = $ORACLE_HOME)
)
)

4.4 Configure TNS entries on each site.

In order to make things simpler the same network service names will be generated on each site. These service names will be called:

Alias Comments
RAC_PRIM1_DGMGRL.local Points to the RAC_PRIM instance on RAC_PRIM01 using the service name RAC_PRIM_DGMGRL.local. This can be used for creating the standby database.
RAC_PRIM1.local Points to the RAC_PRIM instance on RAC_PRIM01. using the service name RAC_PRIM.local
RAC_PRIM2.local Points to the RAC_PRIM instance on RAC_PRIM02 using the service name RAC_PRIM.local
RAC_PRIM.local Points to the RAC_PRIM database i.e. Contains all database instances.
RAC_STDBY1_DGMGRL.local Points to the RAC_STDBY instance on RAC_STDBY01 using the service name RAC_STDBY1_DGMGRL ** This will be used for the database duplication.
RAC_STDBY1.local Points to the RAC_STDBY instance on RAC_STDBY01 using the service name RAC_STDBY.local
RAC_STDBY2.local Points to the RAC_STDBY instance on RAC_STDBY02 using the service name RAC_STDBY.local
RAC_STDBY.local Points to the RAC_STDBY database i.e. Contains all the database instances
listener_DB_UNIQUE_NAME.local This will be a tns alias entry consisting of two address lines. The first address line will be the address of the listener on Node1 and the second will be the address of the listener on Node 2. Placing both of the above listeners in the address list will ensure that the database automatically registers with both nodes. There must be two sets of entries. One for the standby nodes call listener_RAC_STDBY and one for the primary nodes called listener_RAC_PRIM

Sample tnsnames.ora (RAC_PRIM01)

RAC_PRIM1_DGMGRL.local =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_PRIM01-vip)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_PRIM_DGMGRL.local)
)
)

RAC_PRIM1.local =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_PRIM01-vip)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_PRIM.local)
(INSTANCE_NAME = RAC_PRIM1)
)
)

RAC_PRIM2.local =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_PRIM02-vip)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_PRIM.local)
(INSTANCE_NAME = RAC_PRIM2)
)
)

RAC_PRIM.local =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_PRIM01-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_PRIM02-vip)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_PRIM.local)
)
)

RAC_STDBY1_DGMGRL.local =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY01-vip)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_STDBY_DGMGRL.local)
)
)

RAC_STDBY2.local=
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY02-vip)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_STDBY.local)
(INSTANCE_NAME=RAC_STDBY2)
)
)

RAC_STDBY1.local=
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY01-vip)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_STDBY.local)
(INSTANCE_NAME=RAC_STDBY1)
)
)

RAC_STDBY.local=
(DESCRIPTION =
(ADDRESS_LIST=
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY01-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY02-vip)(PORT = 1521)))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC_STDBY.local)
)
)

LISTENERS_RAC_PRIM.local=
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_PRIM01-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_PRIM02-vip)(PORT = 1521))
)

4.5 Configure ASM on each Site

Certain initialisation parameters are only applicable when a database is running in either a standby or primary database role. Defining ALL of the parameters on BOTH sites will ensure that, if the roles are switched (Primary becomes Standby and Standby becomes the new Primary), then no further configuration will be necessary.

Some of the parameters will however be node-specific; therefore there will be one set of parameters for the Primary site nodes and one for the Standby site nodes.

4.6 Primary Site Preparation

The following initialisation parameters should be set on the primary site prior to duplication. Whilst they are only applicable to the primary site, they will be equally configured on the standby site.
Dg_broker_config_file1 Point this to a file within the ASM disk group – Note File need not exist.
Dg_broker_config_file2 Point this to a file within the ASM disk group – Note File need not exist.
db_block_checksum To enable datablock integrity checking (OPTIONAL)
db_block_checking To enable datablock consistency checking (OPTIONAL)

As long as performance implications allow and do not violate existing SLAs it should be mandatory to have db_block_checksum and db_block_checking enabled.

Additionally, the following must also be configured:

Archive Log Mode

The primary database must be placed into archive log mode.

Forced Logging

The standby database is kept up to date by applying transactions on the standby site, which have been recorded in the online redo logs. In some environments that have not previously utilized Data Guard, the NOLOGGING option may have been utilized to enhance database performance. Usage of this feature in a Data Guard protected environment is strongly undesirable.
From Oracle version 9.2, Oracle introduced a method to prevent NOLOGGING transactions from occurring. This is known as forced logging mode of the database. To enable forced logging, issue the following command on the primary database:

alter database force logging;

Password File
The primary database must be configured to use an external password file. This is generally done at the time of installation. If not, then a password file can be created using the following command:

orapwd file=$ORACLE_HOME/dbs/orapwRAC_PRIM1 password=mypasswd

Before issuing the command ensure that the ORACLE_SID is set to the appropriate instance – in this case RAC_PRIM1.

Repeat this for each node of the cluster.

Also ensure that the initialisation parameter remote_login_passwordfile is set to ‘exclusive’.

As with Oracle11.1 the Orale Net sessions for Redo Transport can alternatively be auhenticated through SSL (see also section 6.2.1 in the Data Guard Concepts manual).

Standby Site Preparation

Initialization Parameter File :

As part of the duplication process a temporary initialisation file will be used. For the purposes of this document this file will be called /tmp/initRAC_PRIM.ora have one line:

db_name=RAC_PRIM

Password File

The standby database must be configured to use a password file. This must be created by copying the password file from the primary site to the standby site and renaming it to reflect the standby instances.

Repeat this for each node of the cluster.

Additionally ensure that the initialisation parameter remote_login_passwordfile is set to xclusive.

Create Audit File Destination

Create a directory on each node of the standby system to hold audit files.
mkdir /u01/app/oracle/admin/RAC_STDBY/adump

Start Standby Instance

Now that everything is in place the standby instance needs to be started ready for duplication to commence:

export ORACLE_SID=RAC_STDBY1
sqlplus / as sysdba
startup nomount pfile=’/tmp/initRAC_PRIM.ora’

Test Connection

From the primary database test the connection to the standby database using the command:

sqlplus sys/mypasswd@RAC_STDBY_dgmgrl as sysdba

This should successfully connect.

Duplicate the Primary database

The standby database is created from the primary database. In order to achieve this, up to Oracle10g a backup of the primary database needs to be made and transferred to the standby and restored. Oracle RMAN 11g simplifies this process by providing a new method which allows an ‘on the fly’-duplicate to take place. This will be the method used here (the pre-11g method is described in the Appendicies).

From the primary database invoke RMAN using the following command:

export ORACLE_SID=RAC_PRIM1
rman target / auxiliary sys/mypasswd@RAC_STDBY1_dgmgrl

NOTE: If RMAN returns the error “rman: can’t open target” then ensure that ‘ORACLE_HOME/bin’ appears first in the PATH because there exists a Linux utility also named RMAN.

Next, issue the following duplicate command:

duplicate target database for standby from active database
spfile
set db_unique_name=’RAC_STDBY’
set control_files=’+DATA/RAC_STDBY/controlfile/control01.dbf’
set instance_number=’1’
set audit_file_dest=’/u01/app/oracle/admin/RAC_STDBY/adump’
set remote_listener=’LISTENERS_RAC_STDBY’
nofilenamecheck;

Create an SPFILE for the Standby Database

By default the RMAN duplicate command will have created an spfile for the instance located in $ORACLE_HOME/dbs.

This file will contain entries that refer to the instance names on the primary database. As part of this creation process the database name is being changed to reflect the DB_UNIQUE_NAME for the standby database, and as such the spfile created is essentially worthless. A new spfile will now be created using the contents of the primary database’s spfile.

Get location of the Control File

Before starting this process, note down the value of the control_files parameter from the currently running standby database

Create a text initialization pfile

The first stage in the process requires that the primary databases initialisation parameters be dumped to a text file:

set ORACLE_SID=RAC_PRIM1
sqlplus “/ as sysdba”
create pfile=’/tmp/initRAC_STDBY.ora’ from spfile;

Copy the created file ‘/tmp/initRAC_STDBY.ora’ to the standby server.

Edit the init.ora

On the standby server, edit the /tmp/initRAC_STDBY.ora file:

NOTE: Change every occurrence of RAC_PRIM with RAC_STDBY with the exception of the parameter DB_NAME which must NOT change.

Set the control_files parameter to reflect the value obtained in 4.3.8.1 above. This will most likely be +DATA/RAC_STDBY/controlfile/control01.dbf.

Save the changes.

Create SPFILE

Having created the textual initialisation file it now needs to be converted to a spfile and stored within ASM by issuing:

export ORACLE_SID=RAC_STDBY1
sqlplus “/ as sysdba”
create spfile=’+DATA/RAC_STDBY/spfileRAC_STDBY.ora’ from pfile= ’/tmp/initRAC_STDBY.ora’

Create Pointer File

With the spfile now being in ASM, the RDBMS instances need to be told where to find it.

Create a file in the $ORACLE_HOME/dbs directory of standby node 1 (RAC_STDBY01 ) called initRAC_STDBY1.ora . This file will contain one line:

spfile=’+DATA/RAC_STDBY/spfileRAC_STDBY.ora’

Create a file in the $ORACLE_HOME/dbs directory of standby node 2 (RAC_STDBY02) called initRAC_STDBY2.ora . This file will also contain one line:

spfile=’ +DATA/RAC_STDBY/spfileRAC_STDBY.ora’

Additionally remove the RMAN created spfile from $ORACLE_HOME/dbs located on standby node 1 (RAC_STDBY01 )

Create secondary control files

When the RMAN duplicate completed, it created a standby database with only one control file. This is not good practice, so the next step in the process is to create extra control files.
This is a two-stage process:

1. Shutdown and startup the database using nomount :

shutdown immediate;
startup nomount;

2. Change the value of the control_files parameter to ‘+DATA’,’ +FRA’

alter system set control_files=‘+DATA’,’ +FRA’ scope=spfile;

3. Shutdown and startup the database again :

shutdown immediate;
startup nomount;

3. Use RMAN to duplicate the control file already present:

export ORACLE_SID=RAC_STDBY1
rman target /
restore controlfile from ‘+DATA/RAC_STDBY/controlfile/control01.dbf’

This will create a control file in both the ASM Disk group’s +DATA and +FRA. It will also update the control file parameter in the spfile.

If you wish 3 to have control files simply update the control_files parameter to include the original controlfile as well as the ones just created.

Cluster-enable the Standby Database

The standby database now needs to be brought under clusterware control, i.e. registered with Cluster Ready Services.

Before commencing, check that it is possible to start the instance on the second standby node (RAC_STDBY02):

export ORACLE_SID=RAC_STDBY2
sqlplus “/ as sysdba”
startup mount;

Ensure Server Side Load Balancing is configured

Check whether the init.ora parameter remote_listener is defined in the standby instances.

If the parameter is not present then create an entry in the tnsnames.ora files (of all standby nodes) which has the following format:

LISTENERS_RAC_STDBY.local =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY01 -vip.local)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = RAC_STDBY02-vip.local)(PORT = 1521))
)
)

Then set the value of the parameter remote_listener to LISTENERS_ RAC_STDBY.local.

Register the Database with CRS

Issue the following commands to register the database with Oracle Cluster Ready Services:

srvctl add database –d RAC_STDBY –o $ORACLE_HOME –m local –p “+DATA/RAC_STDBY/spfileRAC_STDBY.ora” –n RAC_PRIM –r physical_standby –s mount
srvctl add instance –d RAC_STDBY –i RAC_STDBY1 –n RAC_STDBY01
srvctl add instance –d RAC_STDBY –i RAC_STDBY2 –n RAC_STDBY02

Test

Test that the above has worked by stopping any running standby instances and then starting the database (all instances) using the command:

srvctl start database –d RAC_STDBY

Once started check that the associated instances are running by using the command:

srvctl status database –d RAC_STDBY

Temporary Files

Temporary files associated with a temporary tablespace are automatically created with a standby database.

Create Standby Redo Logs

Standby Redo Logs (SRL) are used to store redo data from the primary databases when the transport is configured using the Logwriter (LGWR), which is the default.

Each standby redo log file must be at least as large as the largest redo log file in the primary database. It is recommended that all redo log files in the primary database and the standby redo logs in the respective standby database(s) be of the same size.

The recommended number of SRLs is :

(# of online redo logs per primary instance + 1) * # of instances .

Whilst standby redo logs are only used by the standby site, they should be defined on both the primary as well as the standby sites. This will ensure that if the two databases change their roles (primary-> standby and standby -> primary) then no extra configuration will be required.

The standby database must be mounted (mount as ‘standby’ is the default) before SRLs can be created.

SRLs are created as follows (the size given below is just an example and has to be adjusted to the current environment):

1. sqlplus ‘ / a sysdba’

2. startup mount

3. alter database add standby logfile SIZE 100M;

NOTE: Standby Redo Logs are also created in logfile groups. But be aware of the fact that group numbers then must be greater than the group numbers which are associated with the ORLs in the primary database. Wrt group numbering Oracle makes no difference between ORLs and SRLs.

NOTE: Standby Redo Logs need to be created on both databases.

The standby database is now created. The next stage in the process concerns enabling transaction synchronisation. There are two ways of doing this:

1. Using SQL Plus

2. Using the Data Guard Broker

Configuring Data Guard using SQL Plus

Configure the Standby Database

The following initialisation parameters need to be set on the standby database:

Parameter Value (RAC_STDBY01 ) Value (RAC_STDBY02)
db_unique_name RAC_STDBY
db_block_checking TRUE (OPTIONAL)
db_block_checksum TRUE (OPTIONAL)
log_archive_config dg_config=(RAC_PRIM, RAC_STDBY)
log_archive_max_processes 5
fal_client RAC_STDBY1.local RAC_STDBY2.local
fal_server ‘RAC_PRIM1.local’, ‘RAC_PRIM2.local’
Standby_file_management Auto
log_archive_dest_2 service=RAC_PRIM LGWR SYNC AFFIRM db_unique_name=PRIMARY_RAC_PRIM VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE)
log_archive_dest_2 (Max. Performance Mode) service=RAC_PRIM ARCH db_unique_name=PRIMARY_RAC_PRIM VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE)

Configure the Primary Database

The following initialisation parameters need to be set on the primary database:

Parameter Value (RAC_PRIM01 ) Value (RAC_PRIM02)
db_unique_name RAC_PRIM
db_block_checking TRUE (OPTIONAL)
db_block_checksum TRUE (OPTIONAL)
log_archive_config dg_config=(RAC_PRIM, RAC_STDBY)
log_archive_max_processes 5
fal_client RAC_PRIM1.local RAC_PRIM2.local
fal_server ‘RAC_STDBY1.local’, ‘RAC_STDBY2.local’
standby_file_management Auto
Log_archive_dest_2 service=RAC_STDBY LGWR SYNC AFFIRM db_unique_name=RAC_STDBY VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE)
Log_archive_dest_2 (Max. Performance Mode) service=RAC_STDBY ARCH db_unique_name=RAC_STDBY VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE

Set the Protection Mode

In order to specify the protection mode, the primary database must be mounted but not opened.

NOTE: The database must be mounted in exclusive mode which effectively means that all RAC instances but one be shutdown and the remaining instance be started with a parameter setting of cluster_database=false.

Once this is the case then the following statement must be issued on the primary site:

If using Maximum Protection mode then use the command:

Alter database set standby database to maximize protection;

If using Maximum Availability mode then use the command:

Alter database set standby database to maximize availability;

If using Maximum Performance mode then use the command:

Alter database set standby database to maximize performance;

Enable Redo Transport & Redo Apply

Enabling the transport and application of redo to the standby database is achieved by the following:

Standby Site

The standby database needs to be placed into Managed Recovery mode. This is achieved by issuing the statement:

Alter database recover managed standby database disconnect;

Oracle 10gR2 introduced Real Time redo apply (SRLs required). Enabling real time apply is achieved by issuing the statement:

alter database recover managed standby database using current logfile disconnect;

Primary Site:

Set:

log_archive_dest_state_2=enable

in the init.ora file or issue via SQLPlus :

alter system set log_archive_dest_state_2=enable

For Complete and More details, Please refer the following ORACLE HA Best Practices Article:

Data Guard 11g Installation and Configuration Best Practices on Oracle RAC

====================================================================================

Implementing Data Vault 10204 on Oracle Applications E-Business suite

2008-12-24T02:56:00.000-08:00

Oracle E-Business Suite Release 12 with Oracle Database Vault 10.2.0.4

Please refer the following Metalink Note for complete steps

Note:566841.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 10.2.0.4

Note 428503.1 Integrating Oracle E-Business Suite Release 11i with Oracle Database Vault 10.2.0.4

To Understand More about Datavault , Please refer the following Oracle Link

Oracle Database 10g Release 2 Vault Administrator's Guide

Business Continuity - Implement Dataguard on R12

2008-12-15T04:47:00.000-08:00

IMPLEMENTING Dataguard Physical Standby on R12 on 11g Database Using RMAN Hot Backup
=====================================================================

==> Machine 01 has an E-Business Suite Release 12.0.4 (PROD) DB_NAME=PROD01

==> Machine 02 is clean and will be used as the Standby machine DB_NAME=PROD02

==> Machine 03 will be clean and used as the Observer

1. Prepare the Existing Database as PRIMARY ==> Machine 01

1.Enable Archivelog mode in PRIMARY

SQL>archive log list

>> The output for above command will show whether archive is enabled or Not <<
>> If output shows as follows,then proceed for next step in this section to ENABLE ARCHIVE LOG Mode

SQL> archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /oracle/PROD/11.1.0/db_1/RDBMS/
Oldest online log sequence 386
Current log sequence 387

SQL> shutdown immediate
SQL> startup mount

SQL> alter database force logging;
SQL> alter database archivelog;

>>
>>

2. Create Database Password Files

cd $ORACLE_HOME/dbs
orapwd file=orapw password= ignorecase="Y"

3. Create IFILE and add ifile entry in the pfile

Add the following Entry at end of pfile

IFILE=/oracle/PROD/db/tech_st/11.1.0/dbs/PROD__ifile.ora

Create IFILE as follows:

[oracle@emeaicm01 dbs]$ vi PROD_emeaicm01_ifile.ora

4. Create directory called " PROD_emeaicm01" and place all network files under this folder

[oracle@emeaicm01 PROD_emeaicm01]$ mkdir PROD_emeaicm01

Add IFILE entry on both TNSNAMES.ORA and LISTENER.ORA to use IFILE at the end of file

In Listener.ora
IFILE=/oracle/PROD/db/tech_st/11.1.0/network/admin/PROD_emeaicm01/listener_ifile.ora

In Tnsnames.ora

IFILE=/oracle/PROD/db/tech_st/11.1.0/network/admin/PROD_emeaicm01/PROD_emeaicm01_ifile.ora

Now, Create common IFILE for both Listener and Tnsnames entry

[oracle@emeaicm01 PROD_emeaicm01]$ vi PROD_emeaicm01_ifile.ora

3. Add the following Entries in for standby configuration

PROD01=
(DESCRIPTION=
(ADDRESS_LIST=
(LOAD_BALANCE=YES)
(FAILOVER=YES)
(ADDRESS=(PROTOCOL=tcp)(HOST=emeaicm01.uk.oracle.com)(PORT=1533))
)
(CONNECT_DATA=
(SID=PROD)
)
)

PROD02=
(DESCRIPTION=
(ADDRESS_LIST=
(LOAD_BALANCE=YES)
(FAILOVER=YES)
(ADDRESS=(PROTOCOL=tcp)(HOST=emeaicm02.uk.oracle.com)(PORT=1533))
)
(CONNECT_DATA=
(SID=PROD)
)
)

4. At PRIMARY , Set following parameters in IFILE

LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST MANDATORY'
LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf'
DB_RECOVERY_FILE_DEST_SIZE = 107374182400
DB_RECOVERY_FILE_DEST= '/oracle/archive'
DB_UNIQUE_NAME=PROD01
LOG_ARCHIVE_CONFIG='dg_config=(PROD01,PROD02)'
LOG_ARCHIVE_DEST_2='service=PROD02 valid_for=(online_logfiles,primary_role) db_unique_name=PROD02 LGWR ASYNC=20480 OPTIONAL REOPEN=15 NET_TIMEOUT=30'
LOG_ARCHIVE_DEST_STATE_2=enable
FAL_SERVER='PROD02'
FAL_CLIENT='PROD01'
#standby_archive_dest='LOCATION=USE_DB_RECOVERY_FILE_DEST'
standby_file_management=AUTO
parallel_execution_message_size=8192

5. Create standby redolog

>>>Create standby redo logs on the primary database to support the standby role. The standby redo logs must be the same size as the primary database online redo logs.
It is recommended that the number of standby redo logs is one more than the number of online redo logs. <<<<

Assume, We have 2 Online logs in PRIMARY, then we need to add 3 standby log files

SQL> alter database add standby logfile thread 1 group 3 ( '/oracle/PROD/db/apps_st/data/stdbylog03a.dbf', '/oracle/PROD/db/apps_st/data/stdbylog03b.dbf') size 1G;
SQL> alter database add standby logfile thread 1 group 4 ( '/oracle/PROD/db/apps_st/data/stdbylog04a.dbf', '/oracle/PROD/db/apps_st/data/stdbylog04b.dbf') size 1G;
SQL> alter database add standby logfile thread 1 group 5 ( '/oracle/PROD/db/apps_st/data/stdbylog05a.dbf', '/oracle/PROD/db/apps_st/data/stdbylog05b.dbf') size 1G;

Clone the Database Software to Standby
-----------------------------------------

6. Prepare the Database Tier for Cloning

As ORACLE user on one of the production database servers, run the adpreclone.pl script.
For Example:

cd $ORACLE_HOME/appsutil/scripts/
perl adpreclone.pl dbTier

In our case

cd $ORACLE_HOME/appsutil/scripts/PROD_emeaicm01
perl adpreclone.pl dbTier

Supply the APPS password when requested
Use the same port pool as Source

7. Copy Database Tier to Standby

Use following command to tar the source file , copy and untar in target ==> The following command will automatically tar,copy and untar in the target system

$ tar czvf - . |ssh -l oracle emeaicm02.uk.oracle.com "cd /oracle/PROD/db/tech_st; tar xvzf -"

>>>> It is recommended to use the same directory names on the standby site. <<<<<<

8. Configure the Standby Database Tier using Rapid Clone

At Standby Site, Execute the following adcfgclone.pl script for new database Oracle home:

$ cd $ORACLE_HOME/appsutil/clone/bin
perl adcfgclone.pl dbTechStack

Respond to the prompts appropriately:

Target instance is a Real Application Cluster (RAC) instance (y/n):
"n" in the single instance case
Target System database name:
Note, db_name, not db_unique_name
Number of DATA_TOP's on the target system [4]:
Usually only one for ASM.
Target system DATA_TOP 1:
For example, /oracle/PROD

Source The New Environment

$ cd /oracle/PROD/db/tech_st/11.1.0/
$ . . PROD_emeaicm02.env

9. Configure New Database for Communication between Primary and Standby

When adjusting parameters on the production site for Data Guard setup, you created an include file
holding TNS service definitions. Copy the file to the $TNS_ADMIN directory at your standby site and
name it _ifile.ora.

$ cd $TNS_ADMIN
$ mv PROD_emeaicm01_ifile.ora PROD_emeaicm02_ifile.ora

10. Configure Standby Database Data Guard Parameters

$ vi PROD_emeaicm02_ifile.ora
>> Add/change the following parameters <<

LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST MANDATORY'
LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf'
DB_RECOVERY_FILE_DEST_SIZE = 107374182400
DB_RECOVERY_FILE_DEST= '/oracle/archive'
log_archive_config='dg_config=(PROD_IN01,PROD_IN02)'
LOG_ARCHIVE_DEST_STATE_2=enable
#standby_archive_dest='LOCATION=USE_DB_RECOVERY_FILE_DEST'
standby_file_management=AUTO
parallel_execution_message_size=8192
db_unique_name=PROD_IN02
log_archive_dest_2='service=PROD_IN01 valid_for=(online_logfiles,primary_role) db_unique_name=PROD_IN01 LGWR ASYNC=20480 OPTIONAL REOPEN=15 NET_TIMEOUT=30'
fal_server='PROD_IN01'
fal_client='PROD_IN02'
log_file_name_convert='xx','xx'

Clone Application Tier to Standby
----------------------------------

# Use the same ORACLE_BASE as Source i.e /oracle/PROD
# Use the same port pool as Source, i.e port pool 12
# Setup SSH on both Primary and Standby nodes - Follow - How to setup SSH.doc
# Setup cron to periodically synchronise concurrent manager log and out files - Follow - How to use crontab to rsync CCM log and out files.doc

11. Prepare the Application Tier for Cloning

Log in to the APPLMGR user and run the following commands to prepare the application tier for
cloning:

$ cd /admin/scripts
$ perl adpreclone.pl appsTier

12. Copy the Application Tier to Standby

SR czvf - . |ssh -l oracle emeaicm02.uk.oracle.com "cd /oracle/PROD/apps; tar xzvf -"

13. Configure Standby Application Tier using Rapid Clone
Run adcfgclone.pl first to start configuring the new application tier file systems. These steps must be run
on each application tier node:

$ cd /clone/bin
$ perl adcfgclone.pl atTechStack

Answer prompts appropriately:

SRget system database SID:
Note: db_name, not db_unique_name
SRget system database server node:
Database server hostname, could be any node for RAC node if RAC used

To complete the configuration of environment run AutoConfig using the following commands:

$ cd /ad/12.0.0/bin
$ adconfig.sh contextfile=/appl/admin/.xml run=INSTE8

>>>AutoConfig will report errors regarding to database connection, these errors can be ignored as the
database is unavailable. <<<<

14. Setup cron to periodically synchronise concurrent manager log and out files

emeaicm01.uk.oracle.com is machine A (Primary machine)
emeaicm02.uk.oracle.com is machine B (Standby machine)

On the Standby machine:
mkdir -p /log
mkdir -p /out

mkdir -p /oracle/PROD/inst/apps/PROD_emeaicm01/logs/appl/conc/log
mkdir -p /oracle/PROD/inst/apps/PROD_emeaicm01/logs/appl/conc/out

On the Primary Machine
mkdir -p /log
mkdir -p /out

mkdir -p /oracle/PROD/inst/apps/PROD_emeaicm02/logs/appl/conc/log
mkdir -p /oracle/PROD/inst/apps/PROD_emeaicm02/logs/appl/conc/out

You can set the timings to push files according to your requirement.
In our case, we have set the timing for 30 mintues as follows:

From machine A
===============

The files will be pushing from machine A every 30 minutes, on the hour and half hour, so our entries will be:

$ crontab -e

#
## Push log and out files from this machine to emeaicm02 every 30 minutes, on the hour and half hour
#
00,30 * * * * rsync -av /oracle/PROD/inst/apps/PROD_emeaicm01/logs/appl/conc oracle@emeaicm02: /oracle/PROD/inst/apps/PROD_emeaicm01/logs/appl --rsync-path=/usr/bin/rsync >> /tmp/rsync_01_00-30.log
#

As crontab uses “vi” syntax, save changes using :wq!

From machine B
==============

We will also be pushing files from machine B every 30 minutes, on the quarter hour and three quarter hour, so our entries will be:

#
## Push log and out from this machine to emeaicm01 every 30 minutes at quarter past, and quarter to.
#
15,45 * * * * rsync -av /oracle/PROD/inst/apps/PROD_emeaicm02/logs/appl/conc oracle@emeaicm01:/oracle/PROD/inst/apps/PROD_emeaicm02/logs/appl --rsync-path=/usr/bin/rsync >> /tmp/rsync_01_15-45.log
#

15. Setup SSH on both Primary and Standby nodes

On Primary Node: (Machine 1)
----------------------------

· Log in as oracle
· Generate the ssh key by issuing the following command:
ssh-keygen -t rsa (then press enter 3 times)

$ ssh-keygen -t rsa
Generating public/private rsa key pair.

· Press the Enter key three times.
Enter file in which to save the key (/home/oracle/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/oracle/.ssh/id_rsa.
Your public key has been saved in /home/oracle/.ssh/id_rsa.pub.
The key fingerprint is:
5a:58:7e:65:ae:71:1a:82:2c:95:98:5b:48:b3:52:ac oracle@emeaicm15.uk.oracle.com
· CD into the .ssh directory, which is located under the home directory. Note that a file called id_rsa.pub is created.

$ ls -lrt $HOME/.ssh/
total 24
-rw-r--r-- 1 oracle dba 948 Mar 3 10:57 known_hosts
-rw-r--r-- 1 oracle dba 240 Mar 4 10:15 id_rsa.pub
-rw------- 1 oracle dba 887 Mar 4 10:15 id_rsa

· Update authorized_keys file to enable ssh ‘loopback’

$ cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys

· Use SCP to copy id_rsa.pub to the /tmp directory of the Remote Nodes.
$ scp $HOME/.ssh/id_rsa.pub oracle@emeaicm16.uk.oracle.com:/tmp
oracle@emeaicm16.uk.oracle.com's password:
id_rsa.pub 100% 240 0.2KB/s 00:00

On the Remote Node(s):

· Login as the oracle user
· Remove specialized .login, .profile or similar files which cause extra verbiage to be displayed to the screen.
· Create a directory called .ssh in the home directory
$ mkdir $HOME/.ssh
mkdir: cannot create directory `/home/oracle/.ssh': File exists

· Copy the content of /tmp/id_rsa.pub (copied from the Primary Node) into a new file named authorized_keys. (If you already have a file called authorized_keys in this directory, open it in vi, go to the bottom of the file, add one blank line and then copy and paste the contents of the file /tmp/id_rsa.pub into the existing file and save it.)

$ cat /tmp/id_rsa.pub >> $HOME/.ssh/authorized_keys

· Verify that the .ssh directory permission is set to 700
$ chmod 700 $HOME/.ssh
· Verify that the authorized_keys file permission is set to 600
$ chmod 600 $HOME/.ssh/authorized_keys
· Verify that the $HOME directory does not have write permissions for group and others.
$ chmod go-w $HOME
· Ensure that the ssh daemon is running
$ ps -ef |grep -i ssh

root 2418 22004 0 10:25 ? 00:00:00 sshd: oracle [priv]
oracle 2420 2418 0 10:25 ? 00:00:00 sshd: oracle@pts/1
oracle 2690 2421 0 10:37 pts/1 00:00:00 grep -i ssh
root 22004 1 0 Feb29 ? 00:00:00 /usr/sbin/sshd

Test the installation:
~~~~~~~~~~~~~~~~~~~~~

· Login to the PrimaryNode as oracle user.

Execute the following command, replacing [user] with the username on the Remote Node, and [SERVER] with the host name of the Remote Node:
ssh -l [user] [SERVER]
$ uname -n
emeaicm15.uk.oracle.com

$ ssh -l oracle emeaicm15 (connect to same machine)
Last login: Tue Mar 4 10:41:52 2008 from emeaicm15.uk.oracle.com

$ uname -n
emeaicm15.uk.oracle.com
· When prompted to confirm the identity, respond "Yes".
· Disconnect from the server.

$ exit
Connection to emeaicm16 closed

$ ssh -l oracle emeaicm16 (connect to machine 2)
Last login: Tue Mar 4 10:41:52 2008 from emeaicm15.uk.oracle.com

$ uname -n
emeaicm16.uk.oracle.com
· When prompted to confirm the identity, respond "Yes".
· Disconnect from the server.

$ exit
Connection to emeaicm16 closed
· Execute the following commands:

$ uname -n
emeaicm15.uk.oracle.com

$ ssh oracle@emeaicm16 uname -n
emeaicm16.uk.oracle.com

The remote hostname should appear, followed by the prompt, and you should not be asked to enter and ID or password. If you are prompted for a password, verify the following:
§ The content of the authorized_keys file contains the content of id_rsa.pub of the client
§ The permissions of the authorized_keys file are set to 600.
§ The permissions of the .ssh directory are set to 700.
The permissions of the $HOME directory do not include execute for group and other.

Now repeat the steps again as follows (to enable SSH in the opposite direction)

On Standby Node: (machine 2)

· Log in as oracle
· Generate the ssh key by issuing the following command:
ssh-keygen -t rsa (then press enter 3 times)

$ ssh-keygen -t rsa
Generating public/private rsa key pair.

· Press the Enter key three times.
Enter file in which to save the key (/home/oracle/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/oracle/.ssh/id_rsa.
Your public key has been saved in /home/oracle/.ssh/id_rsa.pub.
The key fingerprint is:
6c:7d:4c:5c:21:9d:d6:8e:1f:6d:9c:52:2f:88:1c:3d oracle@emeaicm16.uk.oracle.com
· CD into the .ssh directory, which is located under the home directory. Note that a file called id_rsa.pub is created.

$ ls -lrt $HOME/.ssh/
-rw-r--r-- 1 oracle dba 703 Feb 18 09:54 known_hosts
-rw-r--r-- 1 oracle dba 240 Mar 4 10:32 authorized_keys
-rw-r--r-- 1 oracle dba 240 Mar 4 10:49 id_rsa.pub
-rw------- 1 oracle dba 887 Mar 4 10:49 id_rsa

· Update authorized_keys file to enable ssh ‘loopback’

$ cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys
· Use SCP to copy id_rsa.pub to the /tmp directory of the Remote Nodes.

$ scp $HOME/.ssh/id_rsa.pub oracle@emeaicm15.uk.oracle.com:/tmp
oracle@emeaicm15.uk.oracle.com's password:
id_rsa.pub 100% 240 0.2KB/s 00:00

On the Primary Node: (Machine 1)

· Login as the oracle user
· Copy the content of /tmp/id_rsa.pub (copied from the Primary Node) into file named authorized_keys
$ cat /tmp/id_rsa.pub >> $HOME/.ssh/authorized_keys
· Verify that the .ssh directory permission is set to 700
$ chmod 700 $HOME/.ssh
· Verify that the authorized_keys file permission is set to 600
$ chmod 600 $HOME/.ssh/authorized_keys
· Verify that the $HOME directory does not have write permissions for group and others.
$ chmod go-w $HOME
· Ensure that the ssh daemon is running
$ ps -ef |grep -i ssh

root 2418 22004 0 10:25 ? 00:00:00 sshd: oracle [priv]
oracle 2420 2418 0 10:25 ? 00:00:00 sshd: oracle@pts/1
oracle 2690 2421 0 10:37 pts/1 00:00:00 grep -i ssh
root 22004 1 0 Feb29 ? 00:00:00 /usr/sbin/sshd

Test the installation at both Node(s):
--------------------------------------

· Login to the Remote Node as oracle user (Machine 2).
· Execute the following command, replacing [user] with the username on the Remote Node, and [SERVER] with the host name of the Remote Node:
ssh -l [user] [SERVER]

$ uname -n
emeaicm16.uk.oracle.com

$ ssh -l oracle emeaicm16 (connect to same machine)
Last login: Tue Mar 4 10:41:52 2008 from emeaicm16.uk.oracle.com

$ uname -n
emeaicm16.uk.oracle.com

$ exit
Connection to emeaicm16 closed

$ ssh -l oracle emeaicm15 (connect to machine 1)
Last login: Tue Mar 4 10:41:52 2008 from emeaicm16.uk.oracle.com

$ uname -n
emeaicm15.uk.oracle.com
· When prompted to confirm the identity, respond "Yes".
· Disconnect from the server.

$ exit
Connection to emeaicm15 closed
· Execute the following commands:

$ uname -n
emeaicm16.uk.oracle.com

$ ssh oracle@emeaicm15 uname -n
emeaicm15.uk.oracle.com

The remote hostname should appear, followed by the prompt, and you should not be asked to enter and ID or password. If you are prompted for a password, verify the following:
§ The content of the authorized_keys file contains the content of id_rsa.pub of the client
§ The permissions of the authorized_keys file are set to 600.
§ The permissions of the .ssh directory are set to 700.
§ The permissions of the $HOME directory do not include execute for group and other.

16. Establish the Standby Database

Create a hot backup using Recovery Manager (RMAN)

Take Backup of Primary Database and Copy the backup to Standby(Machine02) using RMAN HOT BACKUP

a)set RDBMS_ORACLE_HOME env file
b) $ rman target /

RMAN> run
{
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
backup database plus archivelog;
}

>>>>For RMAN: Monitoring Recovery Manager Jobs ==> Ref Note 144640.1

To monitor the Rman Backup job, Please execute the following in SQLPLUS as sysdba

SQL> SELECT sid, spid, client_info FROM v$process p, v$session s
WHERE p.addr = s.paddr
AND client_info LIKE '%id=rman%';

SQL> SELECT sid, serial#, context, sofar, totalwork,round(sofar/totalwork*100,2) "% Complete"
FROM v$session_longops
WHERE opname LIKE 'RMAN%'
AND opname NOT LIKE '%aggregate%'
AND totalwork != 0
AND sofar <> totalwork
/

SQL> SELECT sid, seconds_in_wait AS sec_wait, event FROM v$session_wait
WHERE wait_time = 0
ORDER BY sid;

Take backup of current controlfile at primary for standby site in RMAN

For Backup as Backupset:

RMAN> run
{
allocate channel c1 type disk;
backup current controlfile for standby;
}

For Backup as COPY :

RMAN> run
{
allocate channel c1 type disk;
backup as copy current controlfile for standby;
}

Once backup is done, copy the backup with archivelogs & Standby controlfile to remote location(standby)

rsync -av /oracle/archive oracle@machine02.oracle.com:/oracle/archive

17. At Standby (Machine02), Startup mount the Standby database

The following command will automatically duplicate the database using backup taken at primary and
mount the database

$ rman target sys/oracle@prod_in01 auxiliary sys/oracle@prod_in02

RMAN> DUPLICATE TARGET DATABASE FOR STANDBY
DORECOVER NOFILENAMECHECK;

Run the following command to check the standby database details

SQL> select database_role,switchover_status,checkpoint_change#,switchover#,dataguard_broker,guard_status,current_scn,flashback_on from v$database

The output should be similar to the following:

DATABASE_ROLE SWITCHOVER_STATUS CHECKPOINT_CHANGE# SWITCHOVER# DATAGUAR GUARD_S CURRENT_SCN FLASHBACK_ON
--------------- ------------------ ---------------------- ----------- --------------- ------------------- ------------------
PHYSICAL STANDBY NOT ALLOWED 5965111847227 83208404 ENABLED NONE 5965112465873 YES

18. On the primary database enable the previously deferred remote destination by executing this command
from SQL*Plus connected as sysdba:

SQL> alter system set log_archive_dest_state_2=enable SID='*';

19. Place the standby database in managed recovery by executing this command from SQL*Plus
connected as sysdba:

SQL> recover managed standby database using current logfile disconnect;

20. Verify whether the standby is correctly applying redo from the primary.
On the primary database, archive the current log using the following SQL statement:

>>Find the current Sequence and last archived log sequence:

SQL> archive log list;

>>Archive the current redolog sequence:

SQL> alter system archive log current;

On the standby database, query the v$archived_log view to verify that the logs are received and applied:

SQL> select thread#, sequence#, applied,
to_char(first_time, 'mm/dd/yy hh24:mi:ss') first,
to_char(next_time, 'mm/dd/yy hh24:mi:ss') next,
to_char(completion_time, 'mm/dd/yy hh24:mi:ss') completion
from v$archived_log order by first_time;

You can also execute the following query to find the shipping details on both primary and standby

SQL> select process,status,sequence# from v$managed_standby;

21. If incase the logs are not shipping, Please check the following

a) Check alertlog file on Primary and see whether log_archive_dest_2 is reachable and check any TNS
error, if the standby destination not reachable, fix the TNS issue

b) Check the status of the log_archive_dest_2

SQL> select status,error from v$archive_dest;

>> If any error from above statement, you shall defer it temporarily

SQL> alter system set log_archive_dest_state_2=defer;

c) Once the error is rectified on log_archive_dest_2, you can execute the following query to enable it

SQL> alter system set log_archive_dest_state_2=enable;

d) If logs are not shipping and if you want to apply manually, you shall move/copy the missing archivelog
from primary to standby manually using OS scp command and run the following command to apply
the changes

SQL> alter database register logfile '/oracle/archive/PROD_IN02/archivelog/2008_11_18/o1_mf_1_34_4l5bb7b4_.arc';

SWITCHOVER
============

1. Switchover Primary Database to Remote Standby Database

a) Shutdown Production E-Business Suite -
Shut down E-Business Suite application tier. Ensure the application is completely shutdown.

b) On the NoteIMARY database , Issue the following command to commit to switchover to
standby:

SQL> alter database commit to switchover to standby with session shutdown;

c) Shutdown the NoteIMARY database
SQL> shutdown immediate

d) Stop the NoteIMARY database listener: on all database nodes:

lsnrctl stop

e) On the STANDBY database, verify that it is ready to be converted to the new primary:

SQL> select switchover_status from v$database;

You should see the following value:
SWITCHOVER_STATUS
-----------------
TO PRIMARY

f) On the STANDBY database, execute the following command to convert it to be the new primary:

SQL> alter database commit to switchover to primary;

g) Enable Flashback on the STANDBY database (Optional)

SQL> alter database flashback on;

h) Open the STANDBY Database (New Primary database)

SQL> alter database open;

i) Remove the Old Application Topology
Connect to the new primary database using SQL*Plus as user APPS and execute the following
commands:

SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
SQL> commit;

j) Configure the Standby Database Tier
Run AutoConfig on STANDBY database(New Primary) node to configure the Oracle home for use
by the E-Business Suite.

$ cd $ORACLE_HOME/appsutil/scripts/
$ ./adautocfg.sh

k) Start Original PRIMARY as Standby
Start the database listener on database node at the original primary site:

$ lsnrctl start

Start and mount database instance and then start managed recovery:

SQL> startup mount;
SQL> recover managed standby database using current logfile disconnect;

On the New PRIMARY database at the standby site enable remote archiving by executing this
command from SQL*Plus connected as sysdba:

SQL> alter system set log_archive_dest_state_2=enable SID='*';

Verify whether logs are switching from New PRIMARY to this Standby database as described in
Step 20.

l) Perform the Cloning Finishing Tasks as per Note 406982.1

How to change the characterset of Oracle 10g DB

2008-12-10T23:21:00.000-08:00

Decide the character set you want to change and check whether new character is superset of old character set

1.SQL> shutdown immediate
2.SQL> startup open restrict
3.SQL> alter database character set internal_use UTF8;
4.SQL> shutdown immediate
5.SQL> startup

Refer the following Metalink Note for more details:

Note 225912.1 Changing the Database Character Set - a short overview
Note 227330.1 Character Sets & Conversion - Frequently Asked Questions

How to kill all ORACLE Process in one command

2008-12-09T05:22:00.001-08:00

At OS prompt, Execute the following command to kill all ORACLE process

$ kill -9 `ps -ef |grep PROD |awk '{print $2}'`

RMAN Backup Validation Check

2008-12-03T00:07:00.000-08:00

To Test and Check the Integrity for Backups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The database prevents operations that result in unusable backup files or corrupt restored datafiles. The database server automatically does the following:

* Blocks access to datafiles while they are being restored or recovered
* Allows only one restore operation for each datafile at a time
* Ensures that incremental backups are applied in the correct order
* Stores information in backup files to allow detection of corruption

To Detect of Logical Block Corruption
--------------------------------------

This tests data and index blocks for logical corruption, such as corruption of a row piece or index entry. If RMAN finds logical corruption, then it logs the block in the alert.log

1. Start RMAN in nocatalog mode and connect to your database:

From the operating system prompt issue at database host :

$ rman target / nocatalog

2. From the RMAN> prompt issue the validate command with the "check logical"
clause:

The following example shows how to validate a single datafile:

run {
allocate channel d1 type disk;
backup check logical validate datafile 77;
release channel d1;
}

If you wish to monitor the progress of RMAN backup validate, you may issue this
query:

SQL> select sid, serial#, context, sofar, totalwork,
round(sofar/totalwork*100,2) "%_complete"
from v$session_longops
where opname like 'RMAN%'
and opname not like '%aggregate%'
and totalwork != 0
and sofar <> totalwork
/

3. Once the validate process is complete, you either check the alert log or a
view depending on the version of Oracle being used.

In Oracle9i and beyond you can query the view name V$DATABASE_BLOCK_CORRUPTION
to determine what corruption, if any, was found by RMAN.

Query to find All Background_processes in the Database

2008-12-02T04:30:00.000-08:00

Background Processes

Background processes support various types of Oracle processing

Each version of Oracle has a set of associated background processes. Each background process has a descriptor in the fixed area of the SGA. Background process descriptors are of type ksbdp. The descriptors can be seen in the level 2 GLOBAL_AREA dump for example:

ALTER SESSION SET EVENTS 'immediate trace name global_area level 2';

Every background process descriptor has an internal (structure) name e.g. ktmprc_ and an external (display) name e.g. SMON. A list of background process descriptors together with the external and internal names can be obtained using the following query:

SELECT ksbdd.ksbddidn, ksmfsv.ksmfsnam, ksbdd.ksbdddsc
FROM x$ksbdd ksbdd, x$ksbdp ksbdp, x$ksmfsv ksmfsv
WHERE ksbdd.indx = ksbdp.indx
AND ksbdp.addr = ksmfsv.ksmfsadr
ORDER BY ksbdd.ksbddidn;

how to change expired status of user accounts.txt

2008-12-02T04:25:00.001-08:00

SQL> select username,account_status from dba_users where username='DIP';

USERNAME ACCOUNT_STATUS
----------------------- ---------------
SCOTT EXPIRED & LOCKED

SQL> alter user SCOTT account unlock;

User altered.

SQL> select username,account_status from dba_users where username='SCOTT';

USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
SCOTT EXPIRED

SQL> select password from dba_users where username='SCOTT';

PASSWORD
------------------------------
CE4A36B8E06CA59C

SQL> alter user scott identified by values 'CE4A36B8E06CA59C';

User altered.

SQL> select username,account_status from dba_users where username='SCOTT';

USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
SCOTT OPEN

Difference Between AFN & RFN

2008-12-02T04:21:00.000-08:00

RELATIVE FILE NO.

Relative file no is the file no. generated which belongs to only one tablespace.
Every tablespace has its own datafiles will be referred by Relative file no.
So the relative file no. can be repeated in each tablespaces.
Eg; TAblespace users(TS#1) has 2 datafiles then Relative file no. REL file no. 1 and 2 for tablespace #1.
Tablespace userdata(TS#2) has 2 datafiles then Relative file no. will be 1 and 2 for tablespace # 2.

A tablespace can have only 1022 max datafiles .. so Relative file no will be 1022 for each tablespace max.

ABSOLUTE FILE NO.

Whereas Absolute file no is Datafile No. generated uniquely at database level.

How to use crontab to rsync CCM log and out files

2008-11-24T04:00:00.000-08:00

About CRON
cron is a unix utility that allows tasks to be automatically run in the background at regular intervals by the cron daemon. These tasks are often termed as cron jobs in unix.

Crontab Restrictions

You can execute crontab if your name appears in the file /usr/lib/cron/cron.allow. If that file does not exist, you can use
crontab if your name does not appear in the file /usr/lib/cron/cron.deny.
If only cron.deny exists and is empty, all users can use crontab. If neither file exists, only the root user can use crontab. The allow/deny files consist of one user name per line.
Crontab Commands
export EDITOR=vi specify a editor to open crontab file
crontab -e edit/create crontab file
crontab -l display your crontab file.
crontab -r remove your crontab file.
crontab -v * display the last time crontab file was edited
* This option is only available on a few systems.
Crontab syntax
A crontab file has five fields for specifying day, date and time followed by the command to be run at that interval.
* * * * * command to be executed- - - - -| | | | || | | | +----- day of week (0 - 6) (Sunday=0)| | | +------- month (1 - 12)| | +--------- day of month (1 - 31)| +----------- hour (0 - 23)+------------- min (0 - 59)
* in the value field above means all legal values as in braces for that column.
The value column can have a * or a list of elements separated by commas.
An element is either a number in the ranges shown above or two numbers in the range separated by a hyphen (meaning an inclusive range).

Note: The specification of days can be made in two fields: month day and weekday. If both are specified in an entry, they are cumulative meaning both of the entries will get executed .

Crontab Example
A line in crontab file like below removes the tmp files from /home/someuser/tmp each day at 6:30 PM.
30 18 * * * rm /home/someuser/tmp/*
Changing the parameter values as below will cause this command to run at different time schedule below :
min hour day/month month day/week Execution time
30 0 1 1,6,12 * At 00:30 Hrs on 1st of Jan, June & Dec.
:
0 20 * 10 1-5 At 8.00 PM every weekday (Mon-Fri) only in Oct.
:
0 0 1,10,15 * * At midnight on 1st ,10th & 15th of month
:
5,10 0 10 * 1 At 12.05,12.10 every Monday & on 10th of every month
:
Note : If you inadvertently enter the crontab command with no argument(s), do not attempt to get out with Control-d. This removes all entries in your crontab file. Instead, exit with Control-c.

Workshop Task - Establish log and out File Synchronization
In the workshop, the requirement is to synchronise the concurrent manager “log” and “out” files from the Primary to the Standby machine, every 15 minutes.

In this example, we are using the following machines:-
machine01.uk.oracle.com is machine A (Primary machine)

machine02.uk.oracle.com is machine B (Standby machine)

On the Standby machine:
mkdir -p /log
mkdir -p /out

mkdir -p /oracle/PROD/inst/apps/PROD_machine01/logs/appl/conc/log
mkdir -p /oracle/PROD/inst/apps/PROD_machine01/logs/appl/conc/out

On the Primary Machine
mkdir -p /log
mkdir -p /out

mkdir -p /oracle/PROD/inst/apps/PROD_machine02/logs/appl/conc/log
mkdir -p /oracle/PROD/inst/apps/PROD_machine02/logs/appl/conc/out

From machine A
We will be pushing files from machine A every 30 minutes, on the hour and half hour, so our entries will be:
$ crontab -e

#
## Push log and out files from this machine to machine02 every 30 minutes, on the hour and half hour
#
00,30 * * * * rsync -av /oracle/PROD/inst/apps/PROD_machine01/logs/appl/conc oracle@machine02: /oracle/PROD/inst/apps/PROD_machine01/logs/appl --rsync-path=/usr/bin/rsync >> /tmp/rsync_01_00-30.log
#

As crontab uses “vi” syntax, save changes using :wq!

From machine B
We will also be pushing files from machine B every 30 minutes, on the quarter hour and three quarter hour, so our entries will be:
#
## Push log and out from this machine to machine01 every 30 minutes at quarter past, and quarter to.
#
15,45 * * * * rsync -av /oracle/PROD/inst/apps/PROD_machine02/logs/appl/conc oracle@machine01:/oracle/PROD/inst/apps/PROD_machine02/logs/appl --rsync-path=/usr/bin/rsync >> /tmp/rsync_01_15-45.log
#

How to Setup SSH

2008-11-24T03:51:00.000-08:00

On Primary Node: (Machine 1) Example: primary.oracle.com

Log in as oracle
Generate the ssh key by issuing the following command:

ssh-keygen -t rsa (then press enter 3 times)

$ ssh-keygen -t rsa

Generating public/private rsa key pair.

Press the Enter key three times.

Enter file in which to save the key (/home/oracle/.ssh/id_rsa):

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /home/oracle/.ssh/id_rsa.

Your public key has been saved in /home/oracle/.ssh/id_rsa.pub.

The key fingerprint is:

5a:58:7e:65:ae:71:1a:82:2c:95:98:5b:48:b3:52:ac oracle@primary.oracle.com

CD into the .ssh directory, which is located under the home directory. Note that a file called id_rsa.pub is created.

$ ls -lrt $HOME/.ssh/

total 24

-rw-r--r-- 1 oracle dba 948 Mar 3 10:57 known_hosts

-rw-r--r-- 1 oracle dba 240 Mar 4 10:15 id_rsa.pub

-rw------- 1 oracle dba 887 Mar 4 10:15 id_rsa

Update authorized_keys file to enable ssh ‘loopback’

$ cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys

Use SCP to copy id_rsa.pub to the /tmp directory of the Remote Nodes.

$ scp $HOME/.ssh/id_rsa.pub oracle@stdby.oracle.com:/tmp

oracle@stdby.oracle.com's password:

id_rsa.pub 100% 240 0.2KB/s 00:00

On the Remote Node(s): Example: stdby.oracle.com

Login as the oracle user
Remove specialized .login, .profile or similar files which cause extra verbiage to be displayed to the screen.
Create a directory called .ssh in the home directory

$ mkdir $HOME/.ssh

mkdir: cannot create directory `/home/oracle/.ssh': File exists

Copy the content of /tmp/id_rsa.pub (copied from the Primary Node) into a new file named authorized_keys. (If you already have a file called authorized_keys in this directory, open it in vi, go to the bottom of the file, add one blank line and then copy and paste the contents of the file /tmp/id_rsa.pub into the existing file and save it.)

$ cat /tmp/id_rsa.pub >> $HOME/.ssh/authorized_keys

Verify that the .ssh directory permission is set to 700

$ chmod 700 $HOME/.ssh

Verify that the authorized_keys file permission is set to 600

$ chmod 600 $HOME/.ssh/authorized_keys

Verify that the $HOME directory does not have write permissions for group and others.

$ chmod go-w $HOME

Ensure that the ssh daemon is running

$ ps -ef |grep -i ssh

root 2418 22004 0 10:25 ? 00:00:00 sshd: oracle [priv]

oracle 2420 2418 0 10:25 ? 00:00:00 sshd: oracle@pts/1

oracle 2690 2421 0 10:37 pts/1 00:00:00 grep -i ssh

root 22004 1 0 Feb29 ? 00:00:00 /usr/sbin/sshd

Test the installation:

Login to the PrimaryNode as oracle user.
Execute the following command, replacing [user] with the username on the Remote Node, and [SERVER] with the host name of the Remote Node:

ssh -l [user] [SERVER]

$ uname -n

primary.oracle.com

$ ssh -l oracle primary (connect to same machine)

Last login: Tue Mar 4 10:41:52 2008 from primary.oracle.com

$ uname -n

primary.oracle.com

When prompted to confirm the identity, respond "Yes".
Disconnect from the server.

$ exit

Connection to stdby closed

$ ssh -l oracle stdby (connect to machine 2)

Last login: Tue Mar 4 10:41:52 2008 from primary.oracle.com

$ uname -n

stdby.oracle.com

When prompted to confirm the identity, respond "Yes".
Disconnect from the server.

$ exit

Connection to stdby closed

Execute the following commands:

$ uname -n

primary.oracle.com

$ ssh oracle@stdby uname -n

stdby.oracle.com

The remote hostname should appear, followed by the prompt, and you should not be asked to enter and ID or password. If you are prompted for a password, verify the following:

The content of the authorized_keys file contains the content of id_rsa.pub of the client
The permissions of the authorized_keys file are set to 600.
The permissions of the .ssh directory are set to 700.

The permissions of the $HOME directory do not include execute for group and other.

Now repeat the steps again as follows (to enable SSH in the opposite direction)

On Remote Node: (machine 2)

Log in as oracle
Generate the ssh key by issuing the following command:

ssh-keygen -t rsa (then press enter 3 times)

$ ssh-keygen -t rsa

Generating public/private rsa key pair.

Press the Enter key three times.

Enter file in which to save the key (/home/oracle/.ssh/id_rsa):

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

Your identification has been saved in /home/oracle/.ssh/id_rsa.

Your public key has been saved in /home/oracle/.ssh/id_rsa.pub.

The key fingerprint is:

6c:7d:4c:5c:21:9d:d6:8e:1f:6d:9c:52:2f:88:1c:3d oracle@stdby.oracle.com

CD into the .ssh directory, which is located under the home directory. Note that a file called id_rsa.pub is created.

$ ls -lrt $HOME/.ssh/

-rw-r--r-- 1 oracle dba 703 Feb 18 09:54 known_hosts

-rw-r--r-- 1 oracle dba 240 Mar 4 10:32 authorized_keys

-rw-r--r-- 1 oracle dba 240 Mar 4 10:49 id_rsa.pub

-rw------- 1 oracle dba 887 Mar 4 10:49 id_rsa

Update authorized_keys file to enable ssh ‘loopback’

$ cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys

Use SCP to copy id_rsa.pub to the /tmp directory of the Remote Nodes.

$ scp $HOME/.ssh/id_rsa.pub oracle@primary.oracle.com:/tmp

oracle@primary.oracle.com's password:

id_rsa.pub 100% 240 0.2KB/s 00:00

On the Primary Node: (Machine 1)

Login as the oracle user
Copy the content of /tmp/id_rsa.pub (copied from the Primary Node) into file named authorized_keys

$ cat /tmp/id_rsa.pub >> $HOME/.ssh/authorized_keys

Verify that the .ssh directory permission is set to 700

$ chmod 700 $HOME/.ssh

Verify that the authorized_keys file permission is set to 600

$ chmod 600 $HOME/.ssh/authorized_keys

Verify that the $HOME directory does not have write permissions for group and others.

$ chmod go-w $HOME

Ensure that the ssh daemon is running

$ ps -ef |grep -i ssh

root 2418 22004 0 10:25 ? 00:00:00 sshd: oracle [priv]

oracle 2420 2418 0 10:25 ? 00:00:00 sshd: oracle@pts/1

oracle 2690 2421 0 10:37 pts/1 00:00:00 grep -i ssh

root 22004 1 0 Feb29 ? 00:00:00 /usr/sbin/sshd

Test the installation:

Login to the Remote Node as oracle user (Machine 2).
Execute the following command, replacing [user] with the username on the Remote Node, and [SERVER] with the host name of the Remote Node:

ssh -l [user] [SERVER]

$ uname -n

stdby.oracle.com

$ ssh -l oracle stdby (connect to same machine)

Last login: Tue Mar 4 10:41:52 2008 from stdby.oracle.com

$ uname -n

stdby.oracle.com

$ exit

Connection to stdby closed

$ ssh -l oracle primary (connect to machine 1)

Last login: Tue Mar 4 10:41:52 2008 from stdby.oracle.com

$ uname -n

primary.oracle.com

When prompted to confirm the identity, respond "Yes".
Disconnect from the server.

$ exit

Connection to primary closed

Execute the following commands:

$ uname -n

stdby.oracle.com

$ ssh oracle@primary uname -n

primary.oracle.com

The remote hostname should appear, followed by the prompt, and you should not be asked to enter and ID or password. If you are prompted for a password, verify the following:

The content of the authorized_keys file contains the content of id_rsa.pub of the client
The permissions of the authorized_keys file are set to 600.
The permissions of the .ssh directory are set to 700.
The permissions of the $HOME directory do not include execute for group and other.

11g ASM New Features

2008-11-06T20:58:00.000-08:00

The new features in Automatic Storage Management (ASM) extend the storage management automation, improve scalability, and further simplify management for Oracle Database files.

■ ASM Fast Mirror Resync

A new SQL statement, ALTER DISKGROUP ... DISK ONLINE, can be executed
after a failed disk has been repaired. The command first brings the disk online for
writes so that no new writes are missed. Subsequently, it initiates a copy of all extents
marked as stale on a disk from their redundant copies.
This feature significantly reduces the time it takes to repair a failed diskgroup,
potentially from hours to minutes. The repair time is proportional to the number of
extents that have been written to or modified since the failure.

■ ASM Manageability Enhancements

The new storage administration features for ASM manageability include the following:

■ New attributes for disk group compatibility
To enable some of the new ASM features, you can use two new disk group
compatibility attributes, compatible.rdbms and compatible.asm. These
attributes specify the minimum software version that is required to use disk
groups for the database and for ASM, respectively. This feature enables
heterogeneous environments with disk groups from both Oracle Database 10g and
Oracle Database 11g. By default, both attributes are set to 10.1. You must advance
these attributes to take advantage of the new features.

■ New ASM command-line utility (ASMCMD) commands and options

ASMCMD allows ASM disk identification, disk bad block repair, and backup and
restore operations in your ASM environment for faster recovery.

■ ASM fast rebalance

Rebalance operations that occur while a disk group is in RESTRICTED mode
eliminate the lock and unlock extent map messaging between ASM instances in
Oracle RAC environments, thus improving overall rebalance throughput.
This collection of ASM management features simplifies and automates storage
management for Oracle databases.

■ ASM Preferred Mirror Read

When ASM failure groups are defined, ASM can now read from the extent that is
closest to it, rather than always reading the primary copy. A new initialization
parameter, ASM_PREFERRED_READ_FAILURE_GROUPS, lets the ASM administrator
specify a list of failure group names that contain the preferred read disks for each node
in a cluster.

In an extended cluster configuration, reading from a local copy provides a great
performance advantage. Every node can read from its local diskgroup (failure group),
resulting in higher efficiency and performance and reduced network traffic.

■ ASM Rolling Upgrade

Rolling upgrade is the ability of clustered software to function when one or more of
the nodes in the cluster are at different software versions. The various versions of the
software can still communicate with each other and provide a single system image.
The rolling upgrade capability will be available when upgrading from Oracle
Database 11g Release 1 (11.1).

This feature allows independent nodes of an ASM cluster to be migrated or patched
without affecting the availability of the database. Rolling upgrade provides higher
uptime and graceful migration to new releases.

■ ASM Scalability and Performance Enhancements

This feature increases the maximum data file size that Oracle can support to 128 TB.
ASM supports file sizes greater than 128 TB in any redundancy mode. This provides
near unlimited capacity for future growth. The ASM file size limits are:

■ External redundancy - 140 PB
■ Normal redundancy - 42 PB
■ High redundancy - 15 PB

Customers can also increase the allocation unit size for a disk group in powers of 2 up
to 64 MB.

■ Convert Single-Instance ASM to Clustered ASM

This feature provides support within Enterprise Manager to convert a non-clustered
ASM database to a clustered ASM database by implicitly configuring ASM on all
nodes. It also extends the single-instance to Oracle RAC conversion utility to support
standby databases.

Simplifying the conversion makes it easier for customers to migrate their databases
and achieve the benefits of scalability and high availability provided by Oracle RAC.

■ New SYSASM Privilege for ASM Administration

This feature introduces the new SYSASM privilege to allow for separation of database
management and storage management responsibilities.
The SYSASM privilege allows an administrator to manage the disk groups that can be
shared by multiple databases. The SYSASM privilege provides a clear separation of
duties from the SYSDBA privilege.

For complete list of 11g ASM New Feature, You can refer the following

Note 551205.1 11g ASM New Features Technical White Paper
http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-asm.html

11g New Features - Good sites

2008-11-04T23:00:00.000-08:00

Good Links for 11g New Features

How to Start the CSS Process ,ASM & DB Instances Services On Windows using Command Prompt.

2008-11-04T22:41:00.000-08:00

1. To start the services for CSS, ASM & DB Instances:

C:\> net start oraclecsservice
C:\> net start OracleASMService+ASM
C:\> net start OracleServiceDBAASMW


2.

Check whether above services are running using following command :

C:\> net start


Example as shows:
C:\> net start

These Windows services are started:

   OracleASMService+ASM
   OracleCSService
   OracleServiceDBAASMW

3. To stop the above services

C:\> net stop OracleServiceDBAASMW
C:\> net stop OracleASMService+ASM
C:\> net stop oraclecsservice

Oracle Database 11g Top New Features : Summary

2008-11-04T22:25:00.000-08:00

Oracle Database 11g Top New Features : Summary

1) Automatic Diagnostic Repository [ADR]

2) Database Replay

3) Automatic Memory Tuning

4) Case sensitive password

5) Virtual columns and indexes

6) Interval Partition and System Partition

7) The Result Cache

8) ADDM RAC Enhancements

9) SQL Plan Management and SQL Plan Baselines

10) SQL Access Advisor & Partition Advisor

11) SQL Query Repair Advisor

12) SQL Performance Analyzer (SPA) New

13) DBMS_STATS Enhancements

14) The Result Cache

15) Total Recall (Flashback Data Archive)

Note: The above are only top new features, there are other features as well introduced in 11g which will be included subsequently

Oracle 11g Database DBA New Features with brief explanation
==========================================

# Database Capture/replay database workloads :
This allows the total database workload to be captured, transferred to a test database
create from a backup or standby database, then replayed to test the affects of an upgrade or
system change. Currently, these are working to a capture performance overhead of 5%,
so this will capture real production workloads

# Automatic Memory Tuning:

Automatic PGA tuning was introduced in Oracle 9i. Automatic SGA tuning was already
introduced in Oracle 10g. But In 11g, all memory can be tuned automatically by setting one
parameter. We can literally tell Oracle how much memory it has and it determines how
much to use for PGA, SGA and OS Processes. Maximum and minimum thresholds can be set

# Interval partitioning for tables :

Interval partitions are extensions to range partitioning. These provide automation for
equi-sized range partitions. Partitions are created as metadata and only the start partition is
made persistent. The additional segments are allocated as the data arrives. The additional
partitions and local indexes are automatically created.

# Feature Based Patching:

All one-off patches will be classified as to which feature they affect. This allows you to easily
identify which patches are necessary for the features you are using. EM will allow you to
subscribe to a feature based patching service, so EM automatically scans for available
patches for the features you are using

# RMAN UNDO bypass :

Rman backup can bypass undo. Undo tablespaces are getting huge, but contain lots of
useless information. Now rman can bypass those types of tablespace. Great for exporting a
tablespace from backup.

# Virtual columns/indexes :

User can create Virtual index on table. This Virtual index is not visible to optimizer, so it will
not affect performance, Developer can user HINT and see is Index is useful or not.Invisible
Indexesprevent premature use of newly created indexes

# New default audit settings :

Oracle database where general database auditing was "off" by default, logging is intended
to be enabled by default with the Oracle Database 11g beta secure configuration. Notable
performance improvements are planned to be introduced to reduce the performance
degradation typically associated with auditing.

# Case sensitive password :

Passwords are expected to also become case sensitive This and other changes should result
in better protection against password guessing scenarios. For
example, in addition to limiting the number of failed login attempts to 10 (default
configuration in 10gR2), Oracle 11g beta’s planned default settings should expire
passwords every 180 days, and limit to seven the number of times a user can login with an
expired password before disabling access.

# Faster DML triggers : Create a disabled trigger; specify trigger firing order

# Fine grained access control for Utl_TCP:

in 10g all port are available, now it is controlled.

# Data Guard supports "Flashback Standby"

# New Trigger features

# Partitioning by logical object and automated partition creation.

# LOB's - New high-performance LOB features.

# New Oracle11g Advisors

# Enhanced Read only tables

# Table trigger firing order

# Enhanced Index rebuild online : - Online index build with NO pause to DML.

# No recompilation of dependent objects:- When

A) Columns added to tables
B) Procedures added to packages

# Improved optimizer statistics collection speed

# Online index build with NO pause to DML

# Read only table :-

alter table t read only

alter table t read write

Oracle 11g Database SQL/PL-SQL New Features
----------------------------------------------

> Fine Grained Dependency Tracking:

In 11g we track dependencies at the level of element within unit. so that these changes have
no consequence

• Transparent performance improvement
•Unnecessary recompilation certainly consumes CPU

create table t(a number)

create view v as select a from t

alter table t add(Unheard_Of number)

select status from User_Objectswhere Object_Name = 'V'
- -----
VALID

No recompilation of dependent objects when Columns added to tables OR Procedures
added to packages

> Named and Mixed Notation from SQL:

select fun(P4=>10) from DUAL

In 10g not possible to call function in select statment by passing 4th parameter,
but in 11g it is possible

> PL/SQL "continue" keyword - It is same as we read in c/c++ loop

> Support for “super”: It is same "super" in Java.

> Powerfull Regular Expression:

Now we can access data between TAGS like data between tags .........

The new built-in REGEXP_COUNT returns the number of times the pattern is matched in the
input string.

> New table Data Type "simple_integer"

> SQL Performance Analyzer(SPA) :

It is same as Database replay except it not capture all transaction.The SQL Performance
Analyzer (SPA) leverages existing Oracle Database 10g SQL tuning components. The SPA
provides the ability to capture a specific SQL workload in a SQL Tuning Set, take a
performance baseline before a major database or system change, make the desired change
to the system, and then replay the SQL workload against the modified database or
configuration. The before and after performance of the SQL workload can then be compared
with just a few clicks of the mouse. The DBA only needs to isolate any SQL statements that
are now performing poorly and tune them via the SQL Tuning Advisor

> Caching The Results with /*+ result_cache */ :

select /*+ result_cache */ * from my_table, New for Oracle 11g, the result_cache hint caches
the result set of a select statement. This is similar to alter table table_name cache,but as you
can adding predicates makes /*+ result_cache */ considerably more powerful by caching a
subset of larger tables and common queries.

select /*+ result_cache */ col1, col2, col3 from my_table where colA = :B1

> The compound trigger :

A compound trigger lets you implement actions for each of the table DML timing points in a
single trigger

> PL/SQL unit source can exceeds 32k characters

> Easier to execute table DDL operations online:

Option to wait for active DML operations instead of aborting

> Fast add column with default value:

Does not need to updateall rows to default value.

Oracle 11g Database Backup & Recovery New Features
------------------------------------------------

* Enhanced configuration of archive deletion policies Archive can be deleted , if it is not
need DG , Streams Flashback etc When you CONFIGURE an archived log deletion policy
applies to all archiving destinations, including the flash recovery area. BACKUP ... DELETE
INPUT and DELETE... ARCHIVELOG use this configuration, as does the flash recovery area.
When we back up the recovery area, RMAN can fail over to other archived redo log
destinations if the flash recovery area is inaccessible.

* Configuring backup compression:

In 11g can use CONFIGURE command to choose between the BZIP2 and ZLIB compression
algorithms for RMAN backups.

* Active Database Duplication:

Now DUPLICATE command is network aware i.e.we can create a duplicate or standby
database over the network without taking backup or using old backup.

* Parallel backup and restore for very large files:

RMAN Backups of large data files now use multiple parallel server processes to efficiently
distribute theworkload for each file. This features improves the performance of backups.

* Improved block media recovery performance:

RECOVER command can recover individual data blocks.
RMAN take older, uncorrupted blocks from flashback and the RMAN can use these blocks,
thereby speeding up block media recovery.

* Fast incremental backups on physical standby database:

11g has included new feature of enable block change tracking on a physical standby
database (ALTER DATABASE ENABLE/DISABLE BLOCK CHANGE TRACKING SQL statement).
This new 11g feature enables faster incremental backups on a physical standby database
than in previous releases.because RMAN identifywe the changed blocks sincethe last
incremental backup.

11g ASM New Features
-----------------------

The new features in Automatic Storage Management (ASM) extend the storage
management automation, improve scalability, and further simplify management for
Oracle Database files.

■ ASM Fast Mirror Resync

A new SQL statement, ALTER DISKGROUP ... DISK ONLINE, can be executed
after a failed disk has been repaired. The command first brings the disk online for
writes so that no new writes are missed. Subsequently, it initiates a copy of all extents
marked as stale on a disk from their redundant copies.
This feature significantly reduces the time it takes to repair a failed diskgroup,
potentially from hours to minutes. The repair time is proportional to the number of
extents that have been written to or modified since the failure.

■ ASM Manageability Enhancements

The new storage administration features for ASM manageability include the following:

■ New attributes for disk group compatibility
To enable some of the new ASM features, you can use two new disk group
compatibility attributes, compatible.rdbms and compatible.asm. These
attributes specify the minimum software version that is required to use disk
groups for the database and for ASM, respectively. This feature enables
heterogeneous environments with disk groups from both Oracle Database 10g and
Oracle Database 11g. By default, both attributes are set to 10.1. You must advance
these attributes to take advantage of the new features.

■ New ASM command-line utility (ASMCMD) commands and options

ASMCMD allows ASM disk identification, disk bad block repair, and backup and
restore operations in your ASM environment for faster recovery.

■ ASM fast rebalance

Rebalance operations that occur while a disk group is in RESTRICTED mode
eliminate the lock and unlock extent map messaging between ASM instances in
Oracle RAC environments, thus improving overall rebalance throughput.
This collection of ASM management features simplifies and automates storage
management for Oracle databases.

■ ASM Preferred Mirror Read

When ASM failure groups are defined, ASM can now read from the extent that is
closest to it, rather than always reading the primary copy. A new initialization
parameter, ASM_PREFERRED_READ_FAILURE_GROUPS, lets the ASM administrator
specify a list of failure group names that contain the preferred read disks for each node
in a cluster.

In an extended cluster configuration, reading from a local copy provides a great
performance advantage. Every node can read from its local diskgroup (failure group),
resulting in higher efficiency and performance and reduced network traffic.

■ ASM Rolling Upgrade

Rolling upgrade is the ability of clustered software to function when one or more of
the nodes in the cluster are at different software versions. The various versions of the
software can still communicate with each other and provide a single system image.
The rolling upgrade capability will be available when upgrading from Oracle
Database 11g Release 1 (11.1).

This feature allows independent nodes of an ASM cluster to be migrated or patched
without affecting the availability of the database. Rolling upgrade provides higher
uptime and graceful migration to new releases.

■ ASM Scalability and Performance Enhancements

This feature increases the maximum data file size that Oracle can support to 128 TB.
ASM supports file sizes greater than 128 TB in any redundancy mode. This provides
near unlimited capacity for future growth. The ASM file size limits are:

■ External redundancy - 140 PB
■ Normal redundancy - 42 PB
■ High redundancy - 15 PB

Customers can also increase the allocation unit size for a disk group in powers of 2 up
to 64 MB.

■ Convert Single-Instance ASM to Clustered ASM

This feature provides support within Enterprise Manager to convert a non-clustered
ASM database to a clustered ASM database by implicitly configuring ASM on all
nodes. It also extends the single-instance to Oracle RAC conversion utility to support
standby databases.

Simplifying the conversion makes it easier for customers to migrate their databases
and achieve the benefits of scalability and high availability provided by Oracle RAC.

■ New SYSASM Privilege for ASM Administration

This feature introduces the new SYSASM privilege to allow for separation of database
management and storage management responsibilities.
The SYSASM privilege allows an administrator to manage the disk groups that can be
shared by multiple databases. The SYSASM privilege provides a clear separation of
duties from the SYSDBA privilege.

For complete list of 11g ASM New Feature, You can refer the following

Note 551205.1 11g ASM New Features Technical White Paper
http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/11g-asm.html

For Complete list of 11g New Features, You can refer to the following link

http://www.oracle.com/technology/pub/articles/oracle-database-11g-top-features/index.html

Exporting and restoring Statistics

2008-10-29T21:58:00.000-07:00

I.Export Statistics

1) DBMS_STATS.CREATE_STAT_TABLE

This will create a statistics table in the schema specified.
· ownname – Schema where the table can be created.
· stattab - statistics table name.
· tblspace - tablespace to be used.
exec dbms_stats.create_stat_table (
ownname=>'OWNER',
stattab=>'STAT_TAB',
tblspace=>'USER');

2) DBMS_STATS.EXPORT_TABLE_STATS

This method exports the statistics of the table specified.

ownname - schema name
tabname - table name
stattab - stat table name
cascade - TRUE = indexes too
statown - stat table schema

exec dbms_stats.export_table_stats (
ownname =>'OWNER',
tabname =>'TABLE_NAME',
stattab =>'STAT_TAB',
cascade =>true);

3) DBMS_STATS.EXPORT_SCHEMA_STATS

This method exports the statistics of the SCHEMA specified.

ownname - schema name
stattab - stat table name
statown - stat table schema

exec dbms_stats.export_schema_stats(
ownname=>’OWNER’,
stattab=>'STAT_TAB');

4) DBMS_STATS.EXPORT_DATABASE_STATS

This method exports the statistics of the entire database.

stattab - stat table name
statid - optional identifier
statown - stat table schema

exec dbms_stats.export_database_stats(
stattab=>'STAT_TAB');

Ø dbms_stats.export_dictionary_stats – Retrieves statistics for all dictionary schemas (SYS and SYSTEM)

Ø dbms_stats.export_fixed_object_stats- Retrieves statistics for fixed tables
Ø dbms_stats.export_system_stats - Retrieves and stores system statistics

The STAT_TAB created will hold the database/schema/table statistics in the form of an oracle table. If we wish to keep it safe outside of the database, use the traditional export(exp utility) to export the contents of the same.

exp user/****** tables=STAT_TAB file=stat_tab.dmp

Now, we will see the methods and options available on how to import the statistics.

Before importing any statistics from a table or restoring them back from database, it is recommended to delete the existing statistics using DBMS_STATS.DELETE_TABLE_STATS package.

II. Deleting Statistics

This method deletes particular statistics from the user statistics table identified by stattab and stores them in the dictionary.
ownname - schema name
tabname - table name

exec dbms_stats.delete_table_stats(
ownname =>'OWNER',
tabname =>'TABLE_NAME');

Following methods are available for deleting statistics on schema/dictionary/database level.

exec dbms_stats.delete_schema_stats(OWNER);
exec dbms_stats.delete_dictionary_stats;
exec dbms_stats.delete_fixed_object_stats;
exec dbms_stats.delete_database_stats;

III. Import Statistics

1) DBMS_STATS.IMPORT_TABLE_STATS

This method imports particular table statistics from the user statistics table identified by stattab and stores them in the dictionary.

ownname - schema name
tabname - table name
partname - partition name
stattab - stat table name
statid - optional identifier
cascade - TRUE = indexes too
statown - stat table schema

exec dbms_stats.import_table_stats(
ownname =>'OWNER',
tabname =>'TABLE_NAME',
stattab =>'STAT_TAB',
cascade =>true);

2) DBMS_STATS.IMPORT_SCHEMA_STATS

This method imports the statistics of the SCHEMA specified.

ownname - schema name
stattab - stat table name
statown - stat table schema

exec dbms_stats.import_schema_stats(
ownname=>’OWNER’,
stattab=>’STAT_TAB’);

3) DBMS_STATS.IMPORT_DATABASE_STATS

This method imports the statistics of the entire database.

stattab - stat table name
statid - optional identifier
statown - stat table schema

exec dbms_stats.import_database_stats(
stattab=>'STAT_TAB');

Ø dbms_stats.import_dictionary_stats – Retrieves statistics for all dictionary schemas (SYS and SYSTEM)

Ø dbms_stats.import_fixed_object_stats- Retrieves statistics for fixed tables
Ø dbms_stats.import_system_stats - Retrieves and stores system statistics

Now, we will see the options available on how to restore statistics from the database, within the stats retention period.

V. Restoring Database Statistics

The old statistics are retained at the database level and if there’s any problem with performance of queries, the same can be restored. By default, the statistics are retained at the database level for 31 days.

To see the retention period, the below SQL will return the current retention period(in days) for the stats.

select DBMS_STATS.GET_STATS_HISTORY_RETENTION from dual;

GET_STATS_HISTORY_RETENTION
---------------------------
31

The below SQL will return the oldest possible stats date availability and can be restored.

select DBMS_STATS.GET_STATS_HISTORY_AVAILABILITY from dual;

GET_STATS_HISTORY_AVAILABILITY
--------------------------------------
08-SEP-08 12.47.26.580621000 AM -04:00

To find the history of statistics availability for a table,

select TABLE_NAME, STATS_UPDATE_TIME from dba_tab_stats_history
where table_name=';

TABLE_NAME STATS_UPDATE_TIME
------------------------------ ----------------------------------------
TABLE_NAME 21-SEP-08 06.00.55.159788 AM -04:00
TABLE_NAME 23-SEP-08 07.15.47.596361 AM -04:00

Once we decide on whether to restore statistics at table level/schema level/database level, the following command lines can be used to restore them accordingly.

VI. Restoring Table level Statistics

Ownname - schema name
tabname - Table name
as_of_timestamp – with time zone

execute DBMS_STATS.RESTORE_TABLE_STATS ('owner', 'table', date)

e.g. exec dbms_stats.restore_table_stats (
'OWNER',
'TABLE_NAME',
'23-SEP-08 07.15.47.596361 AM -04:00');

Same way, we can use the following methods based on our requirement to restore the statistics.

Ø execute DBMS_STATS.RESTORE_DATABASE_STATS(date);

Ø execute DBMS_STATS.RESTORE_DICTIONARY_STATS(date);

Ø execute DBMS_STATS.RESTORE_FIXED_OBJECTS_STATS(date);

Ø execute DBMS_STATS.RESTORE_SCHEMA_STATS('owner',date);
Ø execute DBMS_STATS.RESTORE_SYSTEM_STATS(date);

How to disable/enable schedule job and keep run_count?

2008-10-29T05:59:00.000-07:00

You enable one or more jobs by using the ENABLE procedure or Enterprise Manager.

The effect of using this procedure is that the job will now be picked up by the
job coordinator for processing.
Jobs are created disabled by default, so you need to enable them before they
can run.
When a job is enabled, a validity check is performed. If the check fails, the
job is not enabled.

For more information refer to the link

http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/scheduse.
htm#sthref3569 ==> ( see Enabling Jobs and Disabling Jobs)

Regarding run_count please refer to the following metalink article:

Article-ID: Note 602729.1
Title: Mismatch in RUN_COUNT of DBA_SCHEDULER_JOBS

Dropping a Database in 10G

2008-10-29T05:56:00.000-07:00

Dropping a Database in 10G Consists of the following steps.

echo $ORACLE_SID
sqlplus "/as sysdba"
SQL> startup nomount;
ORACLE instance started.

Total System Global Area 1077936128 bytes
Fixed Size 2034344 bytes
Variable Size 427824472 bytes
Database Buffers 633339904 bytes
Redo Buffers 14737408 bytes
SQL> alter database mount exclusive;

Database altered.

SQL> alter system enable restricted session;

System altered.

SQL> select name from v$database;

NAME
---------
TEST
SQL> drop database;

Database dropped.

Database is dropped & all related files are deleted automatically.

Please be very cautious while using this syntax in multidatabase environment.

Oracle 11g Release 1 RAC On Linux Using VMware Server

2008-10-28T02:38:00.000-07:00

Oracle 11g Release 1 RAC On Linux Using VMware Server

This article describes the installation of Oracle 11g release 1 (11.1) RAC on Linux (Oracle Enterprise Linux 5) using VMware Server with no additional shared disk devices.

Introduction

One of the biggest obstacles preventing people from setting up test RAC environments is the requirement for shared storage. In a production environment, shared storage is often provided by a SAN or high-end NAS device, but both of these options are very expensive when all you want to do is get some experience installing and using RAC. A cheaper alternative is to use a FireWire disk enclosure to allow two machines to access the same disk(s), but that still costs money and requires two servers. A third option is to use VMware Server to fake the shared storage.

Using VMware Server you can run multiple Virtual Machines (VMs) on a single server, allowing you to run both RAC nodes on a single machine. In additon, it allows you to set up shared virtual disks, overcoming the obstacle of expensive shared storage.

Before you launch into this installation, here are a few things to consider.

The finished system includes the host operating system, two guest operating systems, two sets of Oracle Clusterware, two ASM instances and two Database instances all on a single server. As you can imagine, this requires a significant amount of disk space, CPU and memory. I was able to complete this installation on a 3.4G Pentium 4 with 3G of memory, but it was extremely slow.
This procedure provides a bare bones installation to get the RAC working. There is no redundancy in the Clusterware installation or the ASM installation. To add this, simply create double the amount of shared disks and select the "Normal" redundancy option when it is offered. Of course, this will take more disk space.
During the virtual disk creation, I always choose not to preallocate the disk space. This makes virtual disk access slower during the installation, but saves on wasted disk space.
This is not, and should not be considered, a production-ready system. It's simply to allow you to get used to installing and using RAC.

Download Software

Download the following software.

VMware Server Installation

Regardless of the host OS, the setup of the virtual machines should be similar.

First, install the VMware Server software. On Linux you do this with the following command as the root user.

# rpm -Uvh VMware-server-*.rpm
Preparing...                ########################################### [100%]
1:VMware-server          ########################################### [100%]
#

Then finish the configuration by running the vmware-config.pl script as the root user. Most of the questions can be answered with the default response by pressing the return key. The output below shows my responses to the questions.

# vmware-config.pl
Making sure services for VMware Server are stopped.

Stopping VMware services:
Virtual machine monitor                                 [  OK  ]

You must read and accept the End User License Agreement to continue.
Press enter to display it.

VMWARE, INC.
SOFTWARE BETA TEST AGREEMENT

*** Editied out license agreement ***

Do you accept? (yes/no) yes

Thank you.

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the mime type icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application's icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

The module bld-2.6.9-5.EL-i686smp-RHEL4 loads perfectly in the running kernel.

Do you want networking for your virtual machines? (yes/no/help) [yes]

Configuring a bridged network for vmnet0.

The following bridged networks have been defined:

. vmnet0 is bridged to eth0

All your ethernet interfaces are already bridged.

Do you want to be able to use NAT networking in your virtual machines? (yes/no)
[yes]

Configuring a NAT network for vmnet8.

Do you want this program to probe for an unused private subnet? (yes/no/help)
[yes]

Probing for an unused private subnet (this can take some time)...

The subnet 172.16.210.0/255.255.255.0 appears to be unused.

The following NAT networks have been defined:

. vmnet8 is a NAT network on private subnet 172.16.210.0.

Do you wish to configure another NAT network? (yes/no) [no]

Do you want to be able to use host-only networking in your virtual machines?
[yes] no

Trying to find a suitable vmnet module for your running kernel.

The module bld-2.6.9-5.EL-i686smp-RHEL4 loads perfectly in the running kernel.

Please specify a port for remote console connections to use [902]

Stopping xinetd:                                           [  OK  ]
Starting xinetd:                                           [  OK  ]
Configuring the VMware VmPerl Scripting API.

Building the VMware VmPerl Scripting API.

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

The installation of the VMware VmPerl Scripting API succeeded.

Do you want this program to set up permissions for your registered virtual
machines?  This will be done by setting new permissions on all files found in
the "/etc/vmware/vm-list" file. [no] yes

Generating SSL Server Certificate

In which directory do you want to keep your virtual machine files?
[/var/lib/vmware/Virtual Machines] /u01/VM

Do you want to enter a serial number now? (yes/no/help) [no] yes

Please enter your 20-character serial number.

Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel:  ENTER-YOUR-SERIAL-NUMBER

Starting VMware services:
Virtual machine monitor                                 [  OK  ]
Virtual ethernet                                        [  OK  ]
Bridged networking on /dev/vmnet0                       [  OK  ]
Host-only networking on /dev/vmnet8 (background)        [  OK  ]
NAT service on /dev/vmnet8                              [  OK  ]
Starting VMware virtual machines...                     [  OK  ]

The configuration of VMware Server e.x.p build-22874 for Linux for this running
kernel completed successfully.

#

The VMware Server Console is started by issuing the command "vmware" at the command prompt, or by selecting it from the "System Tools" menu.

On the "Connect to Host" dialog, accept the "Local host" option by clicking the "Connect" button.

You are then presented with the main VMware Server Console screen.

The VMware Server is now installed and ready to use.

Virtual Machine Setup

Now we must define the two virtual RAC nodes. We can save time by defining one VM, then cloning it when it is installed.

Click the "Create a new virtual machine" button to start the "New Virtual Machine Wizard". Click the "Next" button onthe welcome page.

Select the "Custom" virtual machine configuration and click the "Next" button.

Select the "Linux" guest operating system option, and set the version to "Red Hat Enterprise Linux 4", then click the "Next" button. The RHEL4 option is used because at the time of writing, the current version of VMware server doesn't explicitly support RHEL5, but this setting works fine.

Enter the name "RAC1" and the location should default to "/u01/VM/RAC1", then click the "Next" button.

Select the required number of processors and click the "Next" button.

Uncheck the "Make this virtual machine private" checkbox and click the "Next" button.

Select the amount of memory to associate with the virtual machine. Remember, you are going to need two instances, so don't associate too much, but you are going to need approximately 1 Gig (1024 Meg) to compete the installation successfully.

Accept the "Use bridged networking" option by clicking the "Next" button.

Accept the "LSI Logic" option by clicking the "Next" button.

Select the "Create a new virtual disk" option and click the "Next" button.

Accept the "SCSI" option by clicking the "Next" button. It's a virtual disk, so you can still use this option even if your physical disk is IDE or SATA.

Set the disk size to "10.0" GB and uncheck the "Allocate all disk space now" option. The latter will make disk access slower, but will save you wasting disk space.

Accept "RAC1.vmdk" as the disk file name and complete the VM creation by clicking the "Finish" button.

On the "VMware Server Console" screen, click the "Edit virtual machine settings" button.

On the "Virtual Machine Settings" screen, highlight the "Floppy 1" drive and click the "- Remove" button.

Click the "+ Add" button, select a hardware type of "Ethernet Adapter", then click the "Next" button.

Accept the "Bridged" option by clicking the "Finish" button.

Finish by clicking the "OK" button on the Virtual Machine Settings dialog.

The virtual machine is now configured so we can start the guest operating system installation.

Guest Operating System Installation

Place the first OEL 5 disk in the CD drive and start the virtual machine by clicking the "Power on this virtual machine" button. The right pane of the VMware Server Console should display a boot loader, then the OEL installation screen.

Continue through the OEL 5 installation as you would for a normal server. A general pictorial guide to the installation can be found here. More specifically, it should be a server installation with a minimum of 2G swap, firewall and SELinux disabled and the following package groups installed:

GNOME Desktop Environment
Editors
Graphical Internet
Text-based Internet
Development Libraries
Development Tools
Server Configuration Tools
Administration Tools
Base
System Tools
X Window System

To be consistent with the rest of the article, the following information should be set during the installation:

hostname: rac1.localdomain
IP Address eth0: 192.168.2.101 (public address)
Default Gateway eth0: 192.168.2.1 (public address)
IP Address eth1: 192.168.0.101 (private address)
Default Gateway eth1: none

You are free to change the IP addresses to suit your network, but remember to stay consistent with those adjustments throughout the rest of the article.

Once the basic installation is complete, install the following packages whilst logged in as the root user.

# From Enterprise Linux 5 Disk 1
cd /media/cdrom/Server
rpm -Uvh binutils-2.*
rpm -Uvh elfutils-libelf-0.*
rpm -Uvh glibc-2.*
rpm -Uvh glibc-common-2.*
rpm -Uvh libaio-0.*
rpm -Uvh libgcc-4.*
rpm -Uvh libstdc++-4.*
rpm -Uvh make-3.*
cd /
eject

# From Enterprise Linux 5 Disk 2
cd /media/cdrom/Server
rpm -Uvh compat-libstdc++-33*
rpm -Uvh elfutils-libelf-devel-*
rpm -Uvh glibc-headers*
rpm -Uvh glibc-devel-2.*
rpm -Uvh libgomp*
rpm -Uvh gcc-4.*
rpm -Uvh gcc-c++-4.*
rpm -Uvh libaio-devel-0.*
rpm -Uvh libstdc++-devel-4.*
rpm -Uvh unixODBC-2.*
rpm -Uvh unixODBC-devel-2.*
cd /
eject

# From Enterprise Linux 5 Disk 3
cd /media/cdrom/Server
rpm -Uvh sysstat-7.*
cd /
eject

Oracle Installation Prerequisites

Perform the following steps whilst logged into the RAC1 virtual machine as the root user.

The /etc/hosts file must contain the following information.

127.0.0.1       localhost.localdomain   localhost
# Public
192.168.2.101   rac1.localdomain        rac1
192.168.2.102   rac2.localdomain        rac2
#Private
192.168.0.101   rac1-priv.localdomain   rac1-priv
192.168.0.102   rac2-priv.localdomain   rac2-priv
#Virtual
192.168.2.111   rac1-vip.localdomain    rac1-vip
192.168.2.112   rac2-vip.localdomain    rac2-vip

Add the following lines to the /etc/sysctl.conf file.

kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=4194304
net.core.rmem_max=4194304
net.core.wmem_default=262144
net.core.wmem_max=262144

Run the following command to change the current kernel parameters.

/sbin/sysctl -p

Add the following lines to the /etc/security/limits.conf file.

oracle               soft    nproc   2047
oracle               hard    nproc   16384
oracle               soft    nofile  1024
oracle               hard    nofile  65536

Add the following lines to the /etc/pam.d/login file, if it does not already exist.

session    required     /lib/security/pam_limits.so
session    required     pam_limits.so

Disable secure linux by editing the /etc/selinux/config file, making sure the SELINUX flag is set as follows.

SELINUX=disabled

Alternatively, this alteration can be done using the GUI tool (System > Administration > Security Level and Firewall). Click on the SELinux tab and disable the feature.

Create the new groups and users.

groupadd oinstall
groupadd dba
groupadd oper
groupadd asmadmin

useradd -u 500 -g oinstall -G dba,oper,asmadmin oracle
passwd oracle

Create the directories in which the Oracle software will be installed.

mkdir -p /u01/crs/oracle/product/11.1.0/crs
mkdir -p /u01/app/oracle/product/11.1.0/db_1
chown -R oracle:oinstall /u01

# Oracle Settings
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR

ORACLE_HOSTNAME=rac1.localdomain; export ORACLE_HOSTNAME
ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/11.1.0/db_1; export ORACLE_HOME
ORACLE_SID=RAC1; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=/usr/sbin:$PATH; export PATH
PATH=$ORACLE_HOME/bin:$PATH; export PATH

LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH

if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi

Install VMware Client Tools

Login as the root user on the RAC1 virtual machine, then select the "VM > Install VMware Tools..." option from the main VMware Server Console menu.

This should mount a virtual CD containing the VMware Tools software. Double-click on the CD icon labelled "VMware Tools" to open the CD. Right-click on the ".rpm" package and select the "Open with 'Install Packages'" menu option.

Click the "Continue" button on the "Completed System Preparation" screen and wait for the installation to complete.

Once the package is loaded, the CD should unmount automatically. You must then run the "vmware-config-tools.pl" script as the root user.

# vmware-config-tools.pl

Accept all the default settings and pick the screen resolution of your choice. Ignore any warnings or errors. The VMware client tools are now installed. Reboot the server before proceeding. After the reboot, it is possible the monitor will not be recognised. If this is the case don't panic. Follow th instructions provided on the screen and reconfigure the monitor setting, which will allow the XServer to function correctly.

Create Shared Disks

Shut down the RAC1 virtual machine using the following command.

# shutdown -h now

Create a directory on the host system to hold the shared virtual disks.

# mkdir -p /u01/VM/shared

On the VMware Server Console, click the "Edit virtual machine settings" button. On the "Virtual Machine Settings" screen, click the "+ Add" button.

Click the "Next" button on the welcome screen, then select the hardware type of "Hard Disk" and click the "Next" button.

Accept the "Create a new virtual disk" option by clicking the "Next" button.

Accept the "SCSI" option by clicking the "Next" button.

Set the disk size to "10.0" GB and uncheck the "Allocate all disk space now" option, then click the "Next" button.

Set the disk name to "/u01/VM/shared/ocr.vmdk" and click the "Advanced" button.

Set the virtual device node to "SCSI 1:1" and the mode to "Independent" and "Persistent", then click the "Finish" button.

Repeat the previous hard disk creation steps 4 more times, using the following values:

File Name: /u01/VM/shared/votingdisk.vmdk
Virtual Device Node: SCSI 1:2
Mode: Independent and Persistent
File Name: /u01/VM/shared/asm1.vmdk
Virtual Device Node: SCSI 1:3
Mode: Independent and Persistent
File Name: /u01/VM/shared/asm2.vmdk
Virtual Device Node: SCSI 1:4
Mode: Independent and Persistent
File Name: /u01/VM/shared/asm3.vmdk
Virtual Device Node: SCSI 1:5
Mode: Independent and Persistent

At the end of this process, the virtual machine should look something like the picture below.

Edit the contents of the "/u01/VM/RAC1/RAC1.vmx" file using a text editor, making sure the following entries are present. Some of the tries will already be present, some will not.

disk.locking = "FALSE"
diskLib.dataCacheMaxSize = "0"
diskLib.dataCacheMaxReadAheadSize = "0"
diskLib.dataCacheMinReadAheadSize = "0"
diskLib.dataCachePageSize = "4096"
diskLib.maxUnsyncedWrites = "0"

scsi1.present = "TRUE"
scsi1.virtualDev = "lsilogic"
scsi1.sharedBus = "VIRTUAL"

scsi1:1.present = "TRUE"
scsi1:1.mode = "independent-persistent"
scsi1:1.fileName = "/u01/VM/shared/ocr.vmdk"
scsi1:1.deviceType = "plainDisk"
scsi1:1.redo = ""

scsi1:2.present = "TRUE"
scsi1:2.mode = "independent-persistent"
scsi1:2.fileName = "/u01/VM/shared/votingdisk.vmdk"
scsi1:2.deviceType = "plainDisk"
scsi1:2.redo = ""

scsi1:3.present = "TRUE"
scsi1:3.mode = "independent-persistent"
scsi1:3.fileName = "/u01/VM/shared/asm1.vmdk"
scsi1:3.deviceType = "plainDisk"
scsi1:3.redo = ""

scsi1:4.present = "TRUE"
scsi1:4.mode = "independent-persistent"
scsi1:4.fileName = "/u01/VM/shared/asm2.vmdk"
scsi1:4.deviceType = "plainDisk"
scsi1:4.redo = ""

scsi1:5.present = "TRUE"
scsi1:5.mode = "independent-persistent"
scsi1:5.fileName = "/u01/VM/shared/asm3.vmdk"
scsi1:5.deviceType = "plainDisk"
scsi1:5.redo = ""

Start the RAC1 virtual machine by clicking the "Power on this virtual machine" button on the VMware Server Console. When the server has started, log in as the root user so you can partition the disks. The current disks can be seen by issueing the following commands.

# cd /dev
# ls sd*
sda  sda1  sda2  sdb  sdc  sdd  sde  sdf
#

Use the "fdisk" command to partition the disks sdb to sdf. The following output shows the expected fdisk output for the sdb disk.

# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.


The number of cylinders for this disk is set to 1305.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n
Command action
e   extended
p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1305, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1305, default 1305):
Using default value 1305

Command (m for help): p

Disk /dev/sdb: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        1305    10482381   83  Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
#

In each case, the sequence of answers is "n", "p", "1", "Return", "Return", "p" and "w".

Once all the disks are partitioned, the results can be seen by repeating the previous "ls" command.

# cd /dev
# ls sd*
sda  sda1  sda2  sdb  sdb1  sdc  sdc1  sdd  sdd1  sde  sde1  sdf  sdf1
#

Add the following commands to the /etc/rc.local file.

chown oracle:oinstall /dev/sdb1
chown oracle:oinstall /dev/sdc1
chown oracle:oinstall /dev/sdd1
chown oracle:oinstall /dev/sde1
chown oracle:oinstall /dev/sdf1
chmod 600 /dev/sdb1
chmod 600 /dev/sdc1
chmod 600 /dev/sdd1
chmod 600 /dev/sde1
chmod 600 /dev/sdf1

The shared disks are now configured. We don't have to worry about defining raw devices, which are deprecated in Enterprise Linux 5.

Clone the Virtual Machine

The current version of VMware Server does not include an option to clone a virtual machine, but the following steps illustrate how this can be achieved manually.

Shut down the RAC1 virtual machine using the following command.

# shutdown -h now

Copy the RAC1 virtual machine using the following command.

# cp -R /u01/VM/RAC1 /u01/VM/RAC2

Edit the contents of the "/u01/VM/RAC2/RAC1.vmx" file, making the following change.

displayName = "RAC2"

Ignore discrepancies with the file names in the "/u01/VM/RAC2" directory. This does not affect the action of the virtual machine.

In the VMware Server Console, select the File > Open menu options and browse for the "/u01/VM/RAC2/RAC1.vmx" file. Once opened, the RAC2 virtual machine is visible on the console. Start the RAC2 virtual machine by clicking the "Power on this virtual machine" button and click the "Create" button on the subsequent "Question" screen.

Ignore any errors during the server startup. We are expecting the networking components to fail at this point.

Log in to the RAC2 virtual machine as the root user and start the "Network Configuration" tool (System > Administration > Network).

Remove the devices with the "%.bak" nicknames. To do this, highlight a device, deactivate, then delete it. This will leave just the regular "eth0" and "eth1" devices. Highlight the "eth0" interface and click the "Edit" button on the toolbar and alter the IP address to "192.168.2.102" in the resulting screen.

Click on the "Hardware Device" tab and click the "Probe" button. Then accept the changes by clicking the "OK" button.

Repeat the process for the "eth1" interface, this time setting the IP Address to "192.168.0.102", and making sure the default gateway is not net for the "eth1" interface.

Click on the "DNS" tab and change the host name to "rac2.localdomain", then click on the "Devices" tab.

Once you are finished, save the changes (File > Save) and activate the network interfaces by highlighting them and clicking the "Activate" button. Once activated, the screen should look like the following image.

Edit the /home/oracle/.bash_profile file on the RAC2 node to correct the ORACLE_SID and ORACLE_HOSTNAME values.

ORACLE_SID=RAC2; export ORACLE_SID
ORACLE_HOSTNAME=rac1.localdomain; export ORACLE_HOSTNAME

Start the RAC1 virtual machine and restart the RAC2 virtual machine. When both nodes have started, check they can both ping all the public and private IP addresses using the following commands.

ping -c 3 rac1
ping -c 3 rac1-priv
ping -c 3 rac2
ping -c 3 rac2-priv

At this point the virtual IP addresses defined in the /etc/hosts file will not work, so don't bother testing them.

Configure SSH on each node in the cluster. Log in as the "oracle" user and perform the following tasks on each node.

su - oracle
mkdir ~/.ssh
chmod 700 ~/.ssh
/usr/bin/ssh-keygen -t rsa # Accept the default settings.

The RSA public key is written to the ~/.ssh/id_rsa.pub file and the private key to the ~/.ssh/id_rsa file.

Log in as the "oracle" user on RAC1, generate an "authorized_keys" file on RAC1 and copy it to RAC2 using the following commands.

su - oracle
cd ~/.ssh
cat id_rsa.pub >> authorized_keys
scp authorized_keys rac2:/home/oracle/.ssh/

Next, log in as the "oracle" user on RAC2 and perform the following commands.

su - oracle
cd ~/.ssh
cat id_rsa.pub >> authorized_keys
scp authorized_keys rac1:/home/oracle/.ssh/

The "authorized_keys" file on both servers now contains the public keys generated on all RAC nodes.

To enable SSH user equivalency on the cluster member nodes issue the following commands on each node.

ssh rac1 date
ssh rac2 date
ssh rac1.localdomain date
ssh rac2.localdomain date
exec /usr/bin/ssh-agent $SHELL
/usr/bin/ssh-add

You should now be able to SSH and SCP between servers without entering passwords.

Before installing the clusterware, check the prerequisites have been met using the "runcluvfy.sh" utility in the clusterware root directory.

/mountpoint/clusterware/runcluvfy.sh stage -pre crsinst -n rac1,rac2 -verbose

If you get any failures be sure to correct them before proceeding.

It's a good idea to take a snapshot of the virtual machines, so you can repeat the following stages if you run into any problems. To do this, shutdown both virtual machines and issue the following commands.

# cd /u01/VM
# tar -cvf RAC-PreClusterware.tar RAC1 RAC2 shared
# gzip RAC-PreClusterware.tar

The virtual machine setup is now complete.

Install the Clusterware Software

Start the RAC1 and RAC2 virtual machines, login to RAC1 as the oracle user and start the Oracle installer.

./runInstaller

On the "Welcome" screen, click the "Next" button.

Accept the default inventory location by clicking the "Next" button.

Enter the appropriate name and path for the Oracle Home and click the "Next" button.

Wait while the prerequisite checks are done. If you have any failures correct them and retry the tests before clicking the "Next" button.

The "Specify Cluster Configuration" screen shows only the RAC1 node in the cluster. Click the "Add" button to continue.

Enter the details for the RAC2 node and click the "OK" button.

Click the "Next" button to continue.

The "Specific Network Interface Usage" screen defines how each network interface will be used. Highlight the "eth0" interface and click the "Edit" button.

Set the "eht0" interface type to "Public" and click the "OK" button.

Leave the "eth1" interface as private and click the "Next" button.

Click the "External Redundancy" option, enter "/dev/raw/raw1" as the OCR Location and click the "Next" button. To have greater redundancy we would need to define another shared disk for an alternate location.

Click the "External Redundancy" option, enter "/dev/raw/raw2" as the Voting Disk Location and click the "Next" button. To have greater redundancy we would need to define another shared disk for an alternate location.

On the "Summary" screen, click the "Install" button to continue.

Wait while the installation takes place.

Once the install is complete, run the orainstRoot.sh and root.sh scripts on both nodes as directed on the following screen.

The output from the orainstRoot.sh file should look something like that listed below.

# cd /u01/app/oraInventory
# ./orainstRoot.sh
Changing permissions of /u01/app/oraInventory to 770.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete
#

The output of the root.sh will vary a little depending on the node it is run on. The following text is the output from the RAC1 node.

# cd /u01/crs/oracle/product/11.1.0/crs
# ./root.sh
WARNING: directory '/u01/crs/oracle/product/11.1.0' is not owned by root
WARNING: directory '/u01/crs/oracle/product' is not owned by root
WARNING: directory '/u01/crs/oracle' is not owned by root
WARNING: directory '/u01/crs' is not owned by root
WARNING: directory '/u01' is not owned by root
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.

Setting the permissions on OCR backup directory
Setting up Network socket directories
Oracle Cluster Registry configuration upgraded successfully
The directory '/u01/crs/oracle/product/11.1.0' is not owned by root. Changing owner to root
The directory '/u01/crs/oracle/product' is not owned by root. Changing owner to root
The directory '/u01/crs/oracle' is not owned by root. Changing owner to root
The directory '/u01/crs' is not owned by root. Changing owner to root
The directory '/u01' is not owned by root. Changing owner to root
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node :
node 1: rac1 rac1-priv rac1
node 2: rac2 rac2-priv rac2
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Now formatting voting device: /dev/sdc1
Format of 1 voting devices complete.
Startup will be queued to init within 30 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
rac1
Cluster Synchronization Services is inactive on these nodes.
rac2
Local node checking complete. Run root.sh on remaining nodes to start CRS daemons.
#

Ignore the directory ownership warnings. We should really use a separate directory structure for the clusterware so it can be owned by the root user, but it has little effect on the finished results.

The output from the RAC2 node is listed below.

NO KEYS WERE WRITTEN. Supply -force parameter to override.
-force is destructive and will destroy any previous cluster
configuration.
Oracle Cluster Registry for cluster has already been initialized
Startup will be queued to init within 30 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
rac1
rac2
Cluster Synchronization Services is active on all the nodes.
Waiting for the Oracle CRSD and EVMD to start
Waiting for the Oracle CRSD and EVMD to start
Waiting for the Oracle CRSD and EVMD to start
Oracle CRS stack installed and running under init(1M)
Running vipca(silent) for configuring nodeapps

Creating VIP application resource on (2) nodes...
Creating GSD application resource on (2) nodes...
Creating ONS application resource on (2) nodes...
Starting VIP application resource on (2) nodes...
Starting GSD application resource on (2) nodes...
Starting ONS application resource on (2) nodes...

Done.
#

Here you can see that some of the configuration steps are omitted as they were done by the first node. In addition, the final part of the script ran the Virtual IP Configuration Assistant (VIPCA) in silent mode.

You should now return to the "Execute Configuration Scripts" screen on RAC1 and click the "OK" button.

Wait for the configuration assistants to complete.

When the installation is complete, click the "Exit" button to leave the installer.

It's a good idea to take a snapshot of the virtual machines, so you can repeat the following stages if you run into any problems. To do this, shutdown both virtual machines and issue the following commands.

# cd /u01/VM
# tar -cvf RAC-PostClusterware.tar RAC1 RAC2 shared
# gzip RAC-PostClusterware.tar

The clusterware installation is now complete.

Install the Database Software and Create an ASM Instance

Start the RAC1 and RAC2 virtual machines, login to RAC1 as the oracle user and start the Oracle installer.

./runInstaller

On the "Welcome" screen, click the "Next" button.

Select the "Enterprise Edition" option and click the "Next" button.

Enter the name and path for the Oracle Home and click the "Next" button.

Select the "Cluster Install" option and make sure both RAC nodes are selected, the click the "Next" button.

Wait while the prerequisite checks are done. If you have any failures correct them and retry the tests before clicking the "Next" button.

Select the "Configure Automatic Storage Management (ASM)" option, enter the SYS password for the ASM instance, then click the "Next" button.

Select the "External" redundancy option (no mirroring), select all three raw disks (/dev/sdd1, /dev/sde1 and /dev/sdf1), then click the "Next" button.

The candidate disks may not be listed at first. If this is the case, click the "Change Disk Discovery Path..." button, enter the value "/dev/sd*", then click the "OK" button. After a short pause, the candidate disks should be listed as above.

Click the "next" button to avoid the Oracle Configuration Manager Registration.

On the "Summary" screen, click the "Install" button to continue.

Wait while the database software installs.

Once the installation is complete, wait while the configuration assistants run.

Execute the "root.sh" scripts on both nodes, as instructed on the "Execute Configuration scripts" screen, then click the "OK" button.

When the installation is complete, click the "Exit" button to leave the installer.

It's a good idea to take a snapshot of the virtual machines, so you can repeat the following stages if you run into any problems. To do this, shutdown both virtual machines and issue the following commands.

# cd /u01/VM
# tar -cvf RAC-PostASM.tar RAC1 RAC2 shared
# gzip RAC-PostASM.tar

The database software installation and ASM creation step is now complete.

Create a Database using the DBCA

Start the RAC1 and RAC2 virtual machines, login to RAC1 as the oracle user and start the Database Configuration Assistant.

dbca

On the "Welcome" screen, select the "Oracle Real Application Clusters database" option and click the "Next" button.

Select the "Create a Database" option and click the "Next" button.

Highlight both RAC nodes and click the "Next" button.

Select the "Custom Database" option and click the "Next" button.

Enter the values "RAC.WORLD" and "RAC" for the Global Database Name and SID Prefix respectively, then click the "Next" button.

Accept the management options by clicking the "Next" button. If you are attempting the installation on a server with limited memory, you may prefer not to configure Enterprise Manager at this time.

Enter database passwords then click the "Next" button.

Select the "Automatic Storage Management (ASM)" option, then click the "Next" button.

Select the "DATA" disk group, then click the "Next" button.

Accept the "Use Oracle-Managed Files" database location by the "Next" button.

Check both the "Specify Flash Recovery Area" and "Enable Archiving" options. Enter "+DATA" as the Flash Recovery Area, then click the "Next" button.

Uncheck all but the "Enterprise Manager Repository" option, then click the "Standard Database Components..." button.

Uncheck all but the "Oracle JVM" and "Oracle XML DB" options, then click the "OK" button, followed by the "Next" button on the previous screen. If you are attempting the installation on a server with limited memory, you may prefer not to install the JVM at this time.

Accept the default memory settings by clicking the "Next" button.

Accept the default security settings by clicking the "Next" button.

Accept the default automatic maintenence task settings by clicking the "Next" button.

Accept the database storage settings by clicking the "Next" button.

Accept the database creation options by clicking the "Finish" button.

Accept the summary information by clicking the "OK" button.

Wait while the database is created.

Once the database creation is complete you are presented with the following screen. Make a note of the information on the screen and click the "Exit" button.

The RAC database creation is now complete.

TNS Configuration

Once the installation is complete, the "$ORACLE_HOME/network/admin/listener.ora" file on each RAC node will contain entries similar to the following.

LISTENER_RAC1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
 (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
 (ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip)(PORT = 1521)(IP = FIRST))
 (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.2.101)(PORT = 1521)(IP = FIRST))
)
)

The "$ORACLE_HOME/network/admin/tnsnames.ora" file on each RAC node will contain entries similar to the following.

RAC =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
 (SERVER = DEDICATED)
 (SERVICE_NAME = RAC.WORLD)
)
)

LISTENERS_RAC =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip)(PORT = 1521))
)

RAC2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip)(PORT = 1521))
(CONNECT_DATA =
 (SERVER = DEDICATED)
 (SERVICE_NAME = RAC.WORLD)
 (INSTANCE_NAME = RAC2)
)
)

RAC1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip)(PORT = 1521))
(CONNECT_DATA =
 (SERVER = DEDICATED)
 (SERVICE_NAME = RAC.WORLD)
 (INSTANCE_NAME = RAC1)
)
)

This configuration allows direct connections to specific instance, or using a load balanced connection to the main service.

$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Mon Oct 22 09:09:01 2007

Copyright (c) 1982, 2007, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options

SQL> CONN sys/password@rac1 AS SYSDBA
Connected.
SQL> SELECT instance_name, host_name FROM v$instance;

INSTANCE_NAME    HOST_NAME
---------------- ----------------------------------------------------------------
RAC1             rac1.localdomain

SQL> CONN sys/password@rac2 AS SYSDBA
Connected.
SQL> SELECT instance_name, host_name FROM v$instance;

INSTANCE_NAME    HOST_NAME
---------------- ----------------------------------------------------------------
RAC2             rac2.localdomain

SQL> CONN sys/password@rac AS SYSDBA
Connected.
SQL> SELECT instance_name, host_name FROM v$instance;

INSTANCE_NAME    HOST_NAME
---------------- ----------------------------------------------------------------
RAC1             rac1.localdomain

SQL>

Check the Status of the RAC

There are several ways to check the status of the RAC. The srvctl utility shows the current configuration and status of the RAC database.

$ srvctl config database -d RAC
rac1 RAC1 /u01/app/oracle/product/11.1.0/db_1
rac2 RAC2 /u01/app/oracle/product/11.1.0/db_1
$

$ srvctl status database -d RAC
Instance RAC1 is running on node rac1
Instance RAC2 is running on node rac2
$

The V$ACTIVE_INSTANCES view can also display the current status of the instances.

$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Mon Oct 22 09:09:01 2007

Copyright (c) 1982, 2007, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options

SQL> SELECT * FROM v$active_instances;

INST_NUMBER INST_NAME
----------- ------------------------------------------------------------
     1 rac1.localdomain:RAC1
     2 rac2.localdomain:RAC2

SQL>

Finally, the GV$ allow you to display global information for the whole RAC.

SQL> SELECT inst_id, program, sid, serial# FROM gv$session;
SQL> /

INST_ID PROGRAM                                                 SID    SERIAL#
---------- ------------------------------------------------ ---------- ----------
    1 oracle@rac1.localdomain (q002)                          121         46
.
.
    1 racgimon@rac1.localdomain (TNS V1-V3)                   170         11
    2 sqlplus@rac2.localdomain (TNS V1-V3)                    120         51
.
.
    2 oracle@rac2.localdomain (RSMN)                          170          3

77 rows selected.

SQL>

If you have configured Enterprise Manager, it can be used to view the configuration and current status of the database using a URL like "https://rac1.localdomain:1158/em".

For more information see:

courtesy: http:oracle-base.com

You may refer the following link for above
http://www.oracle-base.com/articles/11g/OracleDB11gR1RACInstallationOnOEL5UsingVMware.php

Oracle Metalink Notes for Oracle Apps DBAs.

2008-10-28T02:14:00.000-07:00

Oracle Metalink Notes for Oracle Apps DBAs.

Dear Friends,

The following are the list of Oracle Metalink Notes, which ORACLE Support suggests
for various issues on different versions

Note: You need to have an account in Oracle Metalink to access notes.

NOTE.166650.1 :Working Effectively With Oracle Support Services

Autoconfig
**********
NOTE.218089.1 : Autoconfig FAQ
NOTE.165195.1 : Using AutoConfig to Manage System Configurations with
NOTE.270519.1 :Customizing an AutoConfig Environment

Patching
********
NOTE.181665.1 : Release 11i Adpatch Basics
NOTE.174436.1 : Oracle Applications Patching FAQ
NOTE.175485.1 : How to Apply an 11i Patch When adpatch is Already Running

Cloning
*******
NOTE.230672.1 : Cloning Oracle Applications Release 11i with Rapid Clone
NOTE.216664.1 : FAQ: Cloning Oracle Applications Release 11i
NOTE.135792.1 : Cloning Oracle Applications Release 11i
NOTE.362473.1 : Cloning E-Business Suite Using Hot Backup for Minimal
NOTE.216212.1 : Business Continuity for Oracle Applications Release 11i
NOTE.452056.1 : Business Continuity for Oracle Applications Release 12 on Database
Release 10gR2
NOTE.233428.1 : Sharing the Application Tier File System in Oracle
Note 243880.1 : Shared APPL_TOP FAQ

IOBJ
****
NOTE.74660.1 : Resolving Invalid Objects in Oracle Applications

NOTE.338879.1 : Landscape1309 - Linux Landscape Quick Reference
NOTE.341782.1 : Linux Quick Reference

NOTE.312572.1 : About Oracle Applications Technology Updates for Release 11.
NOTE.316806.1 : Oracle Applications Installation Update Notes, Release 11i
NOTE.370274.1 : New Features in Oracle Application 11i

NOTE.275734.1 : India Localization
NOTE.47837.1 : Applications Utilities FAQ
NOTE.189487.1 : System Administration FAQ's
NOTE.289786.1 : Installing Oracle Applications: A Guide to Using Rapid
NOTE.245079.1 : Steps to clone a 11i RAC environment to a non-RAC
NOTE.243693.1 : Rapid Clone Coredumps when Running Adcfgclone.pl
NOTE.231701.1 : How to Find Patching History (10.7, 11.0, 11i)
NOTE.139684.1 : Oracle Applications Current Patchset Comparison Utility -
NOTE.331746.1 : Oracle Accelerator FAQ for Global Product Support (Internal
NOTE.144751.1 : Applications Patching - Time Saving Techniques
NOTE.232833.1 : Oracle Applications Release Notes, Release 11i (11.5.9)
NOTE.110372.1 : 11i: How to Clean up the UNIX Environment After Install
NOTE.156219.1 : Net8i/9i Basic configuration of LISTENER.ORA and TNSNAMES.
NOTE.69725.1 : Configuring TNSNAMES.ORA, SQLNET.ORA,and LISTENER.ORA in
NOTE.356878.1 : How to relink the whole Applications 11i Installation
NOTE.233428.1 : Sharing the Application Tier File System in Oracle
NOTE.130686.1 : How to Generate Form, Library and Menu for Oracle
NOTE.246105.1 : Upgrading to J2SE 1.4.2 with Oracle Applications 11i
NOTE.139949.1 : NEED TO CLEAR APACHE, BROWSER OR JINITIATOR CACHE FOR
NOTE.133972.1 : How to Reset the APPS and APPLSYS Passwords in Release 11.5
NOTE.216980.1 : FNDLOAD Fails with PLS-306 in call to LOAD_ROW

NOTE.333785.1 : Oracle Applications Internationalization Guide
NOTE.222663.1 : Internationalization Update Notes for the Oracle E-Business Suite 11i
NOTE.372952.1 : Customer Translations

NOTE.168330.1 : Reload Applications Related Java Objects
NOTE.287176.1 : DMZ Configuration with Oracle E-Business Suite 11i

NOTE.233436.1 : Installing Oracle Application Server 10g with Oracle E-
NOTE.231701.1 : How to Find Patching History (10.7, 11.0, 11i)

NOTE.139684.1 : Oracle Applications Current Patchset Comparison Utility -
NOTE.238276.1 : Migrating to Linux with Oracle Applications Release 11i
NOTE.242480.1 : Using a Staged Applications 11i System to Reduce Patching
NOTE.1076329.6 : SQL*Plus Errors - SP1.MSB Not Found
NOTE.248857.1 : Oracle Applications Tablespace Model Release 11i -

NOTE.269293.1 : Oracle Applications Tablespace Model FAQs
NOTE.258330.1 : About Oracle Applications Manager Minipack 11i.OAM.H
NOTE.268837.1 : Gathering Debug Weboam Log

NOTE.342332.1 : Troubleshooting Login Problems in Oracle Applications 11i
NOTE.112577.1 : How to customize reports at runtime using XML - simple
NOTE.144689.1 : How to Generate a Report (.rdf) File from the UNIX Command
NOTE.211424.1 : How to Enable a Large SGA(over 1.7GB) on RedHat Advanced
NOTE.345145.1 : Is There A Way To Automate The Prompts For Adcfgclone.Pl?
NOTE.1812.1 : TECH : Getting a Stack Trace from a CORE file
NOTE.144599.1 : How to Generate a .pll Library File for Applications 11i
NOTE.282038.1 : Oracle Applications Release 11i with Oracle Database 10g
NOTE.208375.1 : How To Convert A Single Instance Database To RAC In A
NOTE.279956.1 : Oracle E-Business Suite Release 11i with 9i RAC :

NOTE.312731.1 : Configuring Oracle Applications Release 11i with 10g RAC
NOTE.362135.1 : Configuring Oracle Applications Release 11i with 10g R2 RAC

NOTE.1067473.6 : Custom Forms do not Show up in FNDSCMON Form
NOTE.232834.1 : Oracle Applications Release 11.5.9 Maintenance Pack

NOTE.216550.1 : Oracle Applications Release 11i with Oracle9i Release 2 (9.
NOTE.362203.1 : Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)

NOTE.233038.1 : AD Command Line Options

NOTE.186125.1 : Applications 11i and Standby Databases
NOTE.260887.1 : Steps to Clean Nonexistent Nodes or IP Addresses from
NOTE.342459.1 : Diagnostics Overview

NOTE.394615.1 : Adaddnode.Pl failed with : ORA-00001 : unique constraint

NOTE.338003.1 : How to change the hostname and/or port of the Database Tier
NOTE.341322.1 : How to change the hostname of an Applications Tier using AutoConfig

NOTE.333785.1 : Oracle Applications Internationalization Guide
NOTE.211708.1 : Detailed Explanations of How NLS/MLS is Being Handled in 11i
NOTE.73352.1 : NLS/MLS Frequently Asked Questions
NOTE.72324.1 : Guidelines on Resolving NLS/MLS issues

NOTE.316365.1 : Oracle Applications Release 11.5.10.2 Maintenance Pack
NOTE.230627.1 : 9i Export/Import Process for Oracle Applications Release 11i
NOTE.331221.1 : 10g Export/Import Process for Oracle Applications Release 11i
NOTE.362205.1 : 10g Release 2 Export/Import Process for Oracle Applications Release 11i
NOTE.259552.1 : 11.5.9 Category 3 Preupgrade Instructions for 9.2.0.4

NOTE.341281.1 : How to disable the language selection option available in AppsLocalLogin.jsp

NOTE.389472.1 : OATM Migration fails with ORA-22853 for LOB objects

NOTE.174605.1 : bde_chk_cbo.sql - Reports Database Initialization

NOTE.333785.1 : Oracle Applications Internationalization Guide
NOTE.124721.1 : Migrating an Applications Installation to a New Character
NOTE.66320.1 : Changing the Database Character Set or the Database
NOTE.119164.1 : Changing Database Character Set - Valid Superset Definitions
NOTE.123670.1 : Use Scanner Utility before Altering the Database Character
NOTE.213015.1 : SYS.METASTYLESHEET marked as having convertible data (ORA-
NOTE.258895.1 : SYS.RULE$ marked as having convertible data (ORA-12716 when
NOTE.258902.1 : SYS.JOB$ marked as having convertible data

NOTE.43208.1 : Certified Compilers
NOTE.270806.1 : 11.5.9 : Invalid Objects - IES Java Classes
NOTE.165114.1 : Resolving Invalid Java Classes in Oracle Applications
NOTE.343253.1 : Tns-12555, Tns-12560, Tns-00525, Linux Error : 1 Starting

NOTE.150168.1 : Obtaining Forms Runtime Diagnostics (FRD) In Oracle
NOTE.210193.1 : Use of Multiple Organizations In Oracle Applications
NOTE.165035.1 : Current Issues - Multiple Organizations Architecture
NOTE.208267.1 : Improved Convert to Multi-Org Process In Oracle
NOTE.226456.1 : Multiple Organizations in Oracle Applications R11i, March
NOTE.259546.1 : Setting Up Multiple Organizations in Oracle HRMS
NOTE.131081.1 : How can I find which version of Portal I am running ?

NOTE.262125.1 : Sun.io.MalformedInputException For OraSCV.asc,emreadme.txt,
NOTE.216205.1 : Database Initialization Parameters for Oracle Applications

NOTE.213015.1 : SYS.METASTYLESHEET marked as having convertible data (ORA-

NOTE.283225.1 : How to Recreate the Listener for Event and Listener for

NOTE.153960.1 : FAQ : X Server testing and troubleshooting

NOTE.146468.1 : Installing and Upgrading Oracle9i Application Server with
NOTE.233428.1 : Sharing the Application Tier File System in Oracle
NOTE.351283.1 : Interoperability Notes : Oracle Applications Release 11i
NOTE.287453.1 : Oracle Applications 11.5.10 - Installation Update Notes for
NOTE.317226.1 : Concurrent Managers Do Not Start With GSM Profile Option
NOTE.311015.1 : Adgendbc.sh Errors Running AutoConfig

NOTE.337937.1 : Step By Step - 10gR2 RAC with ASM install on Linux(x86) -

NOTE.266043.1 : Support of Linux and Oracle Products on Linux
NOTE.224302.1 : Raw Devices on Linux

NOTE.134395.1 : Cannot Connect to Personal Home Page : Your Session is no
NOTE.351646.1 : Configuring Oracle E-Business Suite Release 11i with 10g

NOTE.230688.1 : Basic ApacheJServ Troubleshooting with IsItWorking.class

NOTE.70276.1 : HOW TO INTEGRATE APPLICATIONS RELEASE 11 WITH CUSTOM
NOTE.273449.1 : Diagnosing Login Problems with Apps 11.5.9 (FND.G)
NOTE.139863.1 : Configuring and Troubleshooting the Self Service Framework

NOTE.342332.1 : Troubleshooting Login Problems in Oracle Applications 11i

NOTE.233428.1 : Sharing the Application Tier File System in Oracle
NOTE.252422.1 : Requesting Translation Synchronization Patches
NOTE.287176.1 : DMZ Configuration with Oracle E-Business Suite 11i

NOTE.68713.1 : Troubleshooting Self-Service Web Applications Login
NOTE.304489.1 : Using Oracle Applications with a Split Configuration

NOTE.225074.1 : 11i AOL : Cannot login to PHP after DB upgrade to 9.2.0.2
NOTE.358140.1 : Troubleshooting Unix coredumps and obtaining stack traces

NOTE.1007808.6 : HOW TO HANDLE CORE DUMPS ON UNIX

NOTE.1812.1 :
NOTE.169706.1 : Oracle Database on AIX,HP-UX,Linux,MacOSX,Solaris,Tru64

NOTE.197031.1 : 32-bit/64-bit Certification/Conversion Issues on Oracle
NOTE.300172.1 : Obsolescence of KOREAN_LEXER Lexer Type
NOTE.225456.1 : Troubleshooting Guide for Cloning Issues
NOTE.161474.1 : Oracle Applications Remote Diagnostics Agent (APPS_RDA)
NOTE.111383.1 : The Basics About Report Review Agent (FNDFS) on 11i

NOTE.210062.1 : Generic Service Management (GSM) in Oracle Applications 11i
NOTE.316447.1 : About Oracle XML Publisher Release 5.5
NOTE.295036.1 : About XML Publisher Release 5.0
NOTE.130091.1 : Upgrading Oracle Applications 11i to use JDK 1.3

NOTE.292424.1 : Cleaning your Windows System After a Failed Oracle
NOTE.124606.1 : Upgrading JInitiator with Oracle Applications 11i

NOTE.316806.1 : Oracle Applications Installation Update Notes, Release 11i
NOTE.177183.1 : Succesfully Installing NLS/MLS in 11i
NOTE.134007.1 : CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
NOTE.1010501.7 : FAQ : Licensing and de-licensing a product, country-specific

NOTE.217368.1 : Advanced Configurations and Topologies for Enterprise

NOTE.287176.1 : DMZ Configuration with Oracle E-Business Suite 11i

NOTE.302738.1 : Using Virtual Hostnames with Oracle Applications Release 11i
NOTE.403311.1 : United States Time Zone Changes 2007 : E-Business Suite

NOTE.333785.1 : Oracle Applications Internationalization Guide
NOTE.232313.1 : Information on Previous Versions of Developer 6i Patchsets
NOTE.240862.1 : Install Oracle Unicode Fonts for Dynamic Image Generation
NOTE.60966.1 : Getting Rid Of Those Pesky Invalid Objects In Oracle
NOTE.400830.1 : How to Render Non ASCII Characters in Personalized
NOTE.285218.1 : Recommended Browsers for Oracle Applications 11i
NOTE.403311.1 : United States & Canada 2007 Daylight Saving Time (DST)
NOTE.289788.1 : Upgrading Oracle Applications
NOTE.316804.1 : Oracle Applications NLS Release Notes, Release 11i (11.5.10.
NOTE.189867.1 : Troubleshooting FRM-92050, FRM-92100, FRM-92101, FRM-92102

NOTE.253763.1 : After Cloning on Target instance FRM-92050 Failed to

NOTE.274783.1 :

Amol's Bookmark
*********************************************************************
NOTE.167000.1 : eBusiness Suite Support - Oracle Diagnostics Support Pack
NOTE.235307.1 : OSS Application Diagnostics Tools : FAQ and Troubleshooting
NOTE.231142.1 : About Oracle Diagnostics version 2.1
NOTE.262006.1 : About Oracle Diagnostics 2.2
NOTE.300976.1 : Support Diagnostics Newsletter for Applications Core
NOTE.357223.1 : "This test can be executed only after logging into
NOTE.363759.1 : How To Add Diagnostic Tools To Responsibility Menu

Installation
*********

NOTE.215868.1 : 11i Release Notes
NOTE.77219.1 : Applications Release 11.0.3 One-Hour Install for Unix
NOTE.287453.1 : Oracle Applications 11.5.10 - Installation Update Notes for
NOTE.292424.1 : Cleaning your Windows System After a Failed Oracle
NOTE.110372.1 : 11i : How to Clean up the UNIX Environment After Install
NOTE.169402.1 : How To Cleanup After A Failed Applications Installation On
NOTE.48602.1 : How do I determine which products are fully installed, and
NOTE.124353.1 : WIN : Manually Removing all Oracle Components on Microsoft
NOTE.275493.1 : Removing 10g Database and Software from AIX, HP-UX, Linux,
NOTE.279519.1 : How to completely remove 8i / 9i Database and Software from
NOTE.232831.1. : Oracle Applications NLS Release Notes 11.5.9 - B10846-01
NOTE.287453.1 : Oracle Applications 11.5.10 - Installation Update Notes for
NOTE.187240.1 : Applications AOL Scenarios : Is It Supported ?
NOTE.287453.1 : Oracle Applications 11.5.10 - Installation Update Notes for
NOTE.316806.1 : Oracle Applications Installation Update Notes, Rel 11.5.10.2
NOTE.360079.1 : Global and Local Inventory explained
NOTE.295185.1 : How to Recreate the Global oraInventory
NOTE.197028.1 : Software Requirements and Tools for Oracle Applications
NOTE.201392.1 : Visual C++ Requirement for Release 11i on Windows
NOTE.268776.1 : GNU Make Requirement for Release 11i For Windows
NOTE.181244.1 : Configuring VNC Or XVFB As The X Server For Applications 11i
NOTE.153960.1 : FAQ : X Server testing and troubleshooting

Patching
*******

NOTE.174436.1 : Oracle Applications Patching FAQ
NOTE.175485.1 : How to Apply an 11i Patch When adpatch is Already Running
NOTE.231701.1 : How to Find Patching History (10.7, 11.0, 11i)
NOTE.252422.1 : Requesting Translation Synchronization Patches in Release
NOTE.316366.1 : 11.5.10 Oracle E-Business Suite Consolidated Update 2 (CU2)
NOTE.259484.1 : Release 11.5.10 Maintenance Pack Installation Instructions
NOTE.316365.1 : Oracle Applications Release 11.5.10.2 Maintenance Pack
NOTE.139684.1 : Oracle Applications Current Patchset Comparison Utility -
NOTE.181665.1 : Release 11i Adpatch Basics
NOTE.358247.1 : ORA-00001 : unique constraint violated error while applying
NOTE.358417.1 : Unable to Start Concurrent Managers After Applying 11i.
NOTE.353414.1 : Application Technology Group (ATG) Patching Policy
NOTE.359198.1 : XDF files fail to load on HP-UX, Memory Fault(Coredump)
NOTE.232834.1 : Oracle Applications Release 11.5.9 Maintenance Pack
NOTE.337274.1 : About Oracle Applications Technology 11i.ATG_PF.H Rollup 3
NOTE.244040.1 : Oracle E-Business Suite Recommended Performance Patches
NOTE.367756.1 : Uploading Java Objects To Patch History Tables Fails While
NOTE.76708.1 : Using ADSPLICE To Add Products To The APPL_TOP In

Cloning
******

NOTE.230672.1 : Cloning Oracle Applications Release 11i with Rapid Clone
NOTE.216664.1 : FAQ : Cloning Oracle Applications Release 11i
NOTE.242123.1 : Create new middle tier node in existing Apps 11i
NOTE.238276.1 : Migrating to Linux with Oracle Applications Release 11i
NOTE.364565.1 : Troubleshoot RapidClone or OAM Clone issues

Upgrade
*******
NOTE.200963.1 : R11.5.3/R11.5.4/R11.5.5 Upgrade And Install Issues
NOTE.289765.1 : Oracle Applications Release 11i (11.5.10) Upgrade Assistant
NOTE.289788.1 : Upgrading Oracle Applications

Autoconfig
**********
NOTE.165195.1 : Using AutoConfig to Manage System Configurations with
NOTE.218089.1 : Autoconfig FAQ
NOTE.270519.1 : Customizing an AutoConfig Environment
NOTE.260887.1 : Steps to Clean Nonexistent Nodes or IP Addresses from
NOTE.341322.1 : How to change the hostname of an Applications Tier using
NOTE.338003.1 : How to change the hostname and/or port of the Database Tier
NOTE.108865.1 : How To Create a Database Connection(DBC) File and

AD Utilities
**********
NOTE.233038.1 : AD Command Line Options

Relinking
********

NOTE.69798.1 : Basics of Relinking an Executable or Binary in an Oracle
NOTE.1009722.6 : How to relink Oracle Concurrent Program Executables on Unix

OAM
****

NOTE.210062.1 : Generic Service Management (GSM) in Oracle Applications 11i
NOTE.117264.1 : FAQ (Oracle Applications Manager)
NOTE.177089.1 : OAM11i Standalone Mode Setup and Configuration
NOTE.214962.1 : How To Determine The Version Of OAM (Oracle Application
NOTE.258330.1 : About Oracle Applications Manager Minipack 11i.OAM.H
NOTE.166115.1 : Oracle Applications Manager 11i integrated with Oracle
NOTE.185431.1 : Troubleshooting Oracle Applications Manager OAM 2.0 for 11i
NOTE.73959.1 : Installation and Configuration of Oracle Application Manager
NOTE.225024.1 : Oracle Applications Manager 11i Documentation Roadmap
NOTE.338317.1 : Basic Information on Cloning An 11.5.10 System Using OAM

NLS/MLS
*******

NOTE.15389.1 : NLS DEBUGGING SUCCESS GUIDE ** INTERNAL ONLY **
NOTE.227332.1 : NLS considerations in Import/Export - Frequently Asked
NOTE.15095.1 : Export/Import and NLS Considerations
NOTE.175300.1 : A Guide to Debugging Globalization (NLS) Support Issues
NOTE.124721.1 : Migrating an Applications Installation to a New Character

Forms
*****

NOTE.130686.1 : How to Generate Form, Library and Menu for Oracle
NOTE.177610.1 : Oracle Forms in Applications FAQ
NOTE.141012.1 : How to Manually Generate an 11.5 Form on Unix

Apps Database
*************

NOTE.174605.1 : bde_chk_cbo.sql - Reports Database Initialization
NOTE.186125.1 : Applications 11i and Standby Databases
NOTE.248857.1 : Oracle Applications Tablespace Model Release 11i -
NOTE.216205.1 : Database Initialization Parameters for Oracle Applications
NOTE.285267.1 : Oracle E-Business Suite 11i and Database FAQ
NOTE.230627.1 : 9i Export/Import Process for Oracle Applications Release 11i
NOTE.183078.1 : Recreating Applications 11i JAVA objects in the database
NOTE.216212.1 : Business Continuity for Oracle Applications Release 11i,
NOTE.282038.1 : Oracle Applications Release 11i with Oracle Database 10g
NOTE.340859.1 : Upgrading Oracle Applications 11i Database to 10g with
NOTE.174605.1 : bde_chk_cbo.sql - Reports Database Initialization
NOTE.216211.1. : Nologging in the E-Business Suite

NOTE.282038.1 : Oracle Applications Release 11i with Oracle Database 10g

RAC / Apps RAC
**************

NOTE.220970.1 : RAC : Frequently Asked Questions
NOTE.312731.1 : Configuring Oracle Applications Release 11i with 10g RAC
NOTE.270901.1 : How to Dynamically Add a New Node to an Existing 9.2.0 RAC
NOTE.294652.1 : E-Business Suite 11i on RAC : Configuring Database Load balancing & Failover
NOTE.312731.1 : Configuring Oracle Applications Release 11i with 10g RAC
NOTE.279956.1 : Oracle E-Business Suite Release 11i with 9i RAC :
NOTE.277825.1 : How to setup Tnsnames.ora (806) for 11i and RAC

Database
********

NOTE.1012933.6 : General Information : Alert Logs and Trace Files
NOTE.209870.1 : How to Reload the JVM in 9.2.0.X
NOTE.175472.1 : How to Reload the JVM in 8.1.7.X
NOTE.159143.1 : Separating Multiple 8i or 9i Oracle Versions to Avoid
NOTE.307349.1 : OUI tips for Oracle RDBMS 10.1.X on OpenVMS
NOTE.130814.1 : How to move LOB Data to Another Tablespace

System Administration
*******************

NOTE.189457.1 : Oracle Applications Systems Administration Setup and Usage
NOTE.290525.1 : Oracle User Management FAQ
NOTE.316277.1 : Unable To Change Guest User Password In Oracle Applications
NOTE.311552.1 : How to optimize the purge process in a high transaction
NOTE.154850.1 : How to Run the Purge Concurrent Request and/or Manager Data

Jserver
******

NOTE.295484.1 : Clear Server Cache and Bounce Apache (Web Server)
NOTE.220188.1 : Oracle Applications Release 11i apps.zip Re-architect
NOTE.230688.1 : Basic ApacheJServ Troubleshooting with IsItWorking.class

Invalid Objects
*************

NOTE.60558.1 : Troubleshooting the Source of Invalid Objects
NOTE.266910.1 : How To Resolve IES Invalid Java Classes After Loading JAR
NOTE.113947.1 : Step by Step Troubleshooting Guide to Solve APPS Invalid

UNIX / LINUX / WINDOWS
NOTE.1007808.6 : HOW TO HANDLE CORE DUMPS ON UNIX
NOTE.1812.1 : TECH : Getting a Stack Trace from a CORE file
NOTE.28588.1 : TECH : Using Truss / Trace on Unix

Advanced Configuration
NOTE.217368.1 : Advanced Configurations and Topologies for Enterprise
NOTE.226880.1 : Configuration of Load Balancing and Transparent Application
NOTE.97926.1 : Failover Issues and Limitations [Connect-time failover and
NOTE.123718.1 : 11i : A Guide to Understanding and Implementing SSL for

Techstack
NOTE.162488.1 : Complete Guide to JInitiator 1.1.8 Setup & Troubleshooting
NOTE.312572.1 : About Oracle Applications Technology Updates for Release 11.
NOTE.246105.1 : Upgrading to J2SE 1.4.2 with Oracle Applications 11i
NOTE.94091.1 : Example : Identifying Connection String Problems in JDBC

Workflow
NOTE.298550.1 : Troubleshooting Workflow Data Growth Issues

General
NOTE.184977.1 : Certify FAQ, Product Navigation & User's Guide
NOTE.224882.1 : Common Commands asked by Oracle Support for Troubleshooting
NOTE.110415.1 : Payables MRC Frequently Asked Questions
NOTE.285218.1 : Recommended Browsers for Oracle Applications 11i
NOTE.257650.1 : Resolving Problems with Connection Idle Timeout
NOTE.270523.1 : How To Find the Oracle Applications Framework and Rollup
NOTE.301504.1 : "Cannot Complete Applications Logon" Error After Selecting
NOTE.315094.1 : JTF Login Page - an operational assessment for CRM

NOTE.242490.1 :
NOTE.282038.1 :
NOTE.342861.1 :
NOTE.209999.1 :
REMARK.56942.1 :
NOTE.198160.1 :
NOTE.159244.1 :

NOTE.186981.1 : Oracle Application Server with Oracle E-Business Suite
NOTE.333436.1 : Oracle E-Business Suite 11i on Windows Server 2003 Service
NOTE.356878.1 : How to relink the whole Applications 11i Installation
NOTE.197031.1 : 32-bit/64-bit Certification/Conversion Issues on Oracle
NOTE.158577.1 : NLS_LANG Explained (How does Client-Server Character
NOTE.227331.1 : Setting NLS Parameters - Frequently Asked Questions
NOTE.124721.1 : Migrating an Applications Installation to a New Character
NOTE.43208.1 : Certified Compilers

NOTE.66320.1 : Changing the Database Character Set or the Database
NOTE.279956.1 : Oracle E-Business Suite Release 11i with 9i RAC :

NOTE.260393.1 : Java Mailer and Other 11.5.9/OWF G Current Issues in

NOTE.232313.1 : Information on Previous Versions of Developer 6i Patchsets

NOTE.125767.1 : Upgrading Developer 6i with Oracle Applications 11i

NOTE.371438.1 : adpreclone.pl dbTier fails with RC-50409 : Topology
NOTE.342332.1 :
NOTE.135949.1 : Troubleshooting the Personal Home Page Login Problems in 11.
NOTE.164317.1 : Upgrading JDBC drivers with Oracle Applications 11i
NOTE.302035.1 : How to Test a JDBC Thin Driver Connection From the SSO
NOTE.365735.1 : How to use Digital Certificates for 11i Applications
NOTE.357922.1 : Autoconfig Reverts to old Context File Values.

NOTE.206511.1 : How to Find a JAR File Which Contains a Particular JAVA

NOTE.68839.1 : 8i Using loadjava and dropjava to Load and Unload Java

NOTE.165123.1 : JAVA CLASS - ORA-29534 : referenced object
NOTE.165114.1 : Resolving Invalid Java Classes in Oracle Applications

NOTE.271218.1 : Yellow bar's and Java security error , The daddy of all

NOTE.294932.1 : Recommendations to Install Oracle Applications 11i
NOTE.169706.1 : Oracle Database on AIX,HP-UX,Linux,MacOSX,Solaris,Tru64
NOTE.342442.1 : Cloning Multi-Node to Single-Node Oracle Applications

NOTE.233428.1 :
NOTE.302738.1 : Using Virtual Hostnames with Oracle Applications Release 11i

NOTE.356433.1 : Using Oracle Applications Release 11i with Virtual

NOTE.362135.1 : Configuring Oracle Applications Release 11i with 10g R2 RAC

NOTE.159270.1 : How To Use FNDCPASS to Change The Oracle Users, APPS,

NOTE.303237.1 : Migrating Red Hat Linux 2.1 or 3.0 to Red Hat Linux 4.0
NOTE.91985.1 :
NOTE.200963.1 : R11.5.3/R11.5.4/R11.5.5 Upgrade And Install Issues
NOTE.272789.1 : Post Clone Problem : Login/Portal Server Installation May
NOTE.339664.1 : Analyst Crib Sheet for NLS/MLS issues in Oracle

NOTE.211708.1 : Detailed Explanations of How NLS/MLS is Being Handled in 11i
NOTE.245079.1 : Steps to clone a 11i RAC environment to a non-RAC
NOTE.362135.1 : Configuring Oracle Applications Release 11i with 10g R2 RAC

NOTE.362135.1 : Configuring Oracle Applications Release 11i with 10g R2 RAC

NOTE.312731.1 : Configuring Oracle Applications Release 11i with 10g RAC
NOTE.131321.1 : How to Relink Oracle Database Software on UNIX
NOTE.231876.1 : Windows OS Upgrade for 11i E-Business Suite

NOTE.184977.1 : Certify FAQ, Product Navigation & User's Guide

NOTE.209810.1 : How to Relink Oracle Applications 11i Programs After

NOTE.361428.1 : Using Linux Desktop Clients with Oracle Applications 11i

NOTE.296559.1 :
NOTE.275734.1 : India Localization
NOTE.364439.1 : Tips and Queries for Troubleshooting Advanced Topologies

NOTE.372928.1 : Oracle Critical Patch Update July 2006 Documentation Map
NOTE.372931.1 : E-Business Suite Critical Patch Update Note
NOTE.268837.1 : Gathering Debug Weboam Log
NOTE.292996.1 : How to Re-Install Intermedia on an 11i Environment

NOTE.160121.1 : Introduction to Sun Cluster v3
NOTE.188135.1 : Documentation Index for Real Application Clusters

NOTE.251351.1 : How to Change the Characterset in a Standby Database in 9i
NOTE.362203.1 : Oracle Applications Release 11i with Oracle 10g Release 2
NOTE.362205.1 : 10g Release 2 Export/Import Process for Oracle Applications

NOTE.1009718.6 : HOW TO SOLVE UNDEFINED SYMBOL ERRORS ON UNIX AND VMS

NOTE.316889.1 : Complete checklist for manual upgrades to 10gR2

NOTE.223721.1 : How to Install XVFB on Linux for dynamic image generartion
NOTE.130091.1 : Upgrading Oracle Applications 11i to use JDK 1.3
NOTE : 163400.1 : Release Content Documents and Features Summary Matrices

NOTE.253918.1 : Autopatch Fails with "Unable to call adppdepRunFndLoad

NOTE.166650.1 : Working Effectively With Oracle Support Services
NOTE.333785.1 : Oracle Applications Internationalization Guide

NOTE.119164.1 : Changing Database Character Set - Valid Superset Definitions

NOTE.17210.1 : Supported NLS Character Sets

NOTE.179133.1 : The correct NLS_LANG in a Windows Environment

NOTE.226565.1 : 9iRAC Useful Views and Statistics (INTERNAL ONLY)

NOTE.387046.1 : RCONFIG : Frequently Asked Questions

NOTE.200340.1 : RAC : Cache Fusion

NOTE.265253.1 : 10g Recyclebin Features And How To Disable it( _recyclebin )
NOTE.312594.1 : Get Warning Messages Trying To Generate Jar Files From
NOTE.242480.1 : Using a Staged Applications 11i System to Reduce Patching
NOTE.134007.1 : CMCLEAN.SQL - Non Destructive Script to Clean Concurrent
NOTE.365228.1 : About Oracle Applications Technology 11i.ATG_PF.H Rollup 4
NOTE.371016.1 : How To License A New Product.

NOTE.151654.1 : How To Start the License Manager After Installing Oracle

NOTE.279430.1 : How To Change Project Installation From Shared To Full

NOTE.123891.1 :
NOTE.123891.1 : How to deactivate a language in e-Business Suite
NOTE.216550.1 : Oracle Applications Release 11i with Oracle9i Release 2 (9.
NOTE.341437.1 : Business Continuity for Oracle Applications Release 11i

NOTE.246105.1 : Upgrading to J2SE 1.4.2 with Oracle Applications 11i
NOTE.304748.1 : Internal : E-Business Suite 11i with Database FAQ
NOTE.308320.1 : How to install the 10.1.0 Enterprise Manager Grid Control

NOTE.291901.1 : Maintenance Mode - A New Feature in 11.5.10
NOTE.134527.1 : TNS-00516 Starting TNS Listener

NOTE.300482.1 : Overview of Using Java with Oracle E-Business Suite Release
NOTE.208256.1 : WIN : How to Remove a Single ORACLE_HOME and Its Traces on
NOTE.363827.1 : Rebaselined Oracle Applications Technology Components for
NOTE.373611.1 : How to move Concurrent Processing Server from one node to

NOTE.240818.1. :
NOTE.69660.1 : Understanding Data Auditing in Oracle Application Tables

NOTE.60828.1 : Overview of Oracle Applications AuditTrails
NOTE.134949.1 : Release 11.0.3 and Oracle 8i Release 8.1.6 Interoperability
NOTE.342332.1 : Troubleshooting Login Problems in Oracle Applications 11i

NOTE.189256.1 : UNIX : Script to Verify Installation Requirements for Oracle
NOTE.296559.1 : FAQ : Common Tracing Techniques within the Oracle
NOTE.177183.1 : Succesfully Installing NLS/MLS in 11i
NOTE.73352.1 : NLS/MLS Frequently Asked Questions

NOTE.399789.1 : NLS Frequently Asked Questions

NOTE.339664.1 : Analyst Crib Sheet for NLS/MLS issues in Oracle
NOTE.227331.1 : Setting NLS Parameters - Frequently Asked Questions

NOTE.110849.1 : Installing and Relinking Oracle Developer on UNIX Platforms

NOTE.76535.1 :
NOTE.316804.1 : Oracle Applications NLS Release Notes, Release 11i (11.5.10.
NOTE.287176.1 : DMZ Configuration with Oracle E-Business Suite 11i

NOTE.310840.1 : AFPCAL Received Failure Code While Parsing or Running
NOTE.371434.1 : Using Openfiler iSCSI with an Oracle database

NOTE.233040.1 : When Oracle Applications Automatic Patch Prerequisite
NOTE.236469.1 : Using Distributed AD in Applications Release 11.5.
NOTE.233043.1 : 11.5.9 Oracle E-Business Suite Consolidated Update 2
NOTE.108185.1 : Oracle Applications Object Library SQL scripts
NOTE.201662.1 : How To Manually Relink on Windows NT or Windows 2000

NOTE.306906.1 : How to create missing DB objects from xdf files

NOTE.396708.1 : Guidelines to Determine whether a Bug or SR is a LinuxOS

NOTE.166762.1 : Oracle Applications Manager 11i Availability
NOTE.60966.1 : Getting Rid Of Those Pesky Invalid Objects In Oracle
NOTE.216589.1 : Step By Step Guide to Creating a Custom Application in
NOTE.105127.1 : FAQ (Customization)
NOTE.243880.1 : Shared APPL_TOP FAQ
NOTE.409045.1 : How to clone from Rac to Non-rac in Oracle Applications 11i.

NOTE.373611.1 : How to move Concurrent Processing Server from one node to

NOTE.342442.1 : Cloning Multi-Node to Single-Node Oracle Applications

NOTE.261428.1 : Setting up 11i E-Business suite using a hardware load

NOTE.224875.1 : Installation, Patching & Upgrade Frequently Asked Questions

NOTE.278816.1 : How to Setup Parallel Concurrent Processing using Shared

NOTE.286506.1 : Sharing Middle-tier Oracle Home in E-Business Suite 11i

NOTE.105133.1 : Concurrent Manager Questions and Answers Relating to
NOTE.69336.1 : Basic information about Concurrent Managers
NOTE.169706.1 : Oracle Database on AIX,HP-UX,Linux,MacOSX,Solaris,Tru64
NOTE.345145.1 : Is There A Way To Automate The Prompts For Adcfgclone.Pl?
*********************************************************************

NOTE.416338.1 : How To Upgrade JDK / J2SE 1.4 Sub-Versions
NOTE.225165.1 : Patching Best Practices and Reducing Downtime
NOTE.368628.1 : Is The 'Personal Home Page' Mode Supported In Oracle 11i Applications?

NOTE.387859.1 : Using AutoConfig to Manage System Configurations in Oracle
NOTE.402306.1 : Oracle Applications Installation and Upgrade Notes Release
NOTE.160214.1 : How to change the oracle users, APPS, APPLSYS and

NOTE.159244.1 : How To Use FNDCPASS to Change The Oracle Users, APPS,
NOTE.335515.1 : Relink fails for Oracle 9.2.0.7.0 on LINUX x86 server on

NOTE.372800.1 : How to Implement an SSL CA Root Certificate in JInitiator

NOTE.402312.1 : Oracle Applications Installation and Upgrade Notes Release

NOTE.394692.1 : Oracle Applications Documentation Resources, Release 12

NOTE.603104.1 : Troubleshooting RapidClone issues with Oracle Applications R12
NOTE.384248.1 : Sharing The Application Tier File System in Oracle E-Business Suite Release 12

NOTE.388577.1 : Configuring Oracle Applications Release 12 with 10g R2 RAC
NOTE.559518.1 : Cloning Oracle Applications Release 12 with Rapid Clone on RAC Enabled Systems

NOTE.393861.1 : Globalization Guide for Oracle Applications Release 12
NOTE.372800.1 : How to Implement an SSL CA Root Certificate in JInitiator
NOTE.184876.1 : Oracle Application Object Library Middle (Web) Tier Setup
NOTE.403385.1 : Duplicate Responsibilities Created On Sysadmin Login And

NOTE.380483.1 : Oracle E-Business Suite Release 12 Additional Configuration
NOTE.148903.1 : Interoperability Notes Oracle Applications Release 11i with
NOTE.364704.1 : A Guide to Configure, Maintain & Troubleshoot JDBC Buffers

NOTE.148902.1 : Interoperability Notes Oracle Applications Release 11.0
NOTE.337762.1 : How to Remove an Oracle Applications 11i node

NOTE.399362.1 : Oracle Applications Release 12 Upgrade Sizing and Best
NOTE.104457.1 : Invalid Objects In Oracle Applications FAQs
NOTE.132604.1 : Upgrading OJSP with Oracle Applications 11i
NOTE.215268.1 : Implementing and Using the JSP Precompiler

NOTE.316900.1 : ALERT : Oracle 10g Release 2 (10.2) Support Status and Alerts

NOTE.189908.1 : ALERT : Oracle9i Release 2 (9.2) Support Status and Alerts
NOTE.380490.1 : Oracle E-Business Suite R12 Configuration in a DMZ

NOTE.269291.1 : Oracle Applications Tablespace Migration Utility User
NOTE.206511.1 : How to Find a JAR File Which Contains a Particular JAVA
NOTE.406982.1 : Cloning Oracle Applications Release 12 with Rapid Clone
NOTE.262125.1 : Sun.io.MalformedInputException For OraSCV.asc,emreadme.txt,
NOTE.419839.1 : How to enable Apache, OC4J and OPMN logging in Oracle
NOTE.422419.1 : How To Enable and Collect Debug for HTTP, OC4J and OPMN in

NOTE.15390.1 : How to Determine and Change DB_NAME or ORACLE_SID
NOTE.375682.1 : About Oracle Applications Technology ATG_PF.H Rollup 5

NOTE.135715.1. : Diagnostic Steps for Intermittent FRM-99999 & FRM-92100
NOTE.185489.1 : Setting Up Parallel Concurrent Processing On Unix Server
NOTE.431496.1 : Java In The Database For Oracle Applications : Introduction
NOTE.183408.1 : Raw Devices and Cluster Filesystems With Real Application
NOTE.277366.1 : Technology Validation Utility for Oracle Applications
NOTE.394448.1 : Getting Started with the Application Management Pack for
NOTE.412044.1 : Application Management Pack for Oracle E-Business Suite
NOTE.375113.1 : Oracle Diagnostics 2.4
NOTE.405425.1 : Oracle Diagnostics 2.5

NOTE.201340.1 : Using Forms Listener Servlet with Oracle Applications 11i
NOTE.160337.1 : How To Manually Change The APPS, APPLSYS and APPLSYSPUB
NOTE.372322.1 : HP Tru64 UNIX Migration Strategy for Oracle E-Business

NOTE.303709.1 : Reclaiming unused space in APPLSYSD tablespace

NOTE.130183.1 : How to Get Log Files from Various Programs for Oracle
NOTE.269129.1 : How to Implement Printing for Oracle Applications : Getting

NOTE.297522.1 :
NOTE.215527.1 : Maintenance Wizard Overview
NOTE.452120.1 : How to locate the log files and troubleshoot RapidWiz for
NOTE.312640.1 : Oracle Text : Re-installation of Applications 11i (11.5.10)

**************
*** iSetup ***
**************
NOTE.402785.1 : iSetup dependency with Deinstall and Reinstall of XMLDB
NOTE.368670.1 : About Oracle iSetup Minipack 11i.AZ.H
NOTE.243554.1 : How to Deinstall and Reinstall XML Database (XDB)

NOTE.244523.1 : Security Alert #57 : Buffer Overflows in EXTPROC of Oracle
NOTE.433435.1 : Japanese characters are displayed like square boxes in
NOTE.455366.1 : Investigating NoClassDefFoundError in eBusiness 11i when
NOTE.197409.1 : Error Opening Oracle*Terminal File fmrweb.res
NOTE.312553.1 : How To Use the Original Forms for Reprint Instead of the
NOTE.438086.1 : Platform Migration with Oracle Applications Release 12

NOTE.458452.1 : Complying with Daylight Saving Time (DST) and Time Zone
NOTE.189367.1 : Best Practices for Securing the E-Business Suite
NOTE.300969.1 : Troubleshooting SSL with Oracle Applications 11i
NOTE.444524.1 : About Oracle Applications Technology ATG_PF.H Rollup 6
NOTE.265253.1 : 10g Recyclebin Features And How To Disable it( _recyclebin )
NOTE.428262.1 : How to identify the form name attached to an f60webmx

NOTE.68839.1 : 8i Using loadjava and dropjava to Load and Unload Java
NOTE.405521.1 : Oracle Enterprise Manager Grid Control Release Notes for
NOTE.187905.1 : bde_imt_index_status.sql - List all interMedia Text indexes
NOTE.388577.1 : Configuring Oracle Applications Release 12 with 10g R2 RAC

NOTE.345106.1 : Login Links On New Rapid Install Homepage Do Not Function
NOTE.443521.1 : Enterprise Manager Grid Control Plug-in for Oracle Applications, Version 1.0/1.2

NOTE.398412.1 : Workflow Queues Creation Scripts
NOTE.77483.1 : External Support FTP site : Information Sheet

NOTE.122452.1 : Global Customer Services Policy Regarding Customizations
NOTE.257911.1 : How To Use Rotatelogs In 9iAS Release 1 (1.0.2.x)
NOTE.276845.1 : Apache Web Server Hangs Every Other Time Running Adapcctl.
NOTE.218893.1 : How to Create The Service Manager 'FNDSM' on Oracle
NOTE.437878.1 : Upgrading Forms and Reports 10g in Oracle Applications
NOTE.290807.1 : Upgrading Sun JRE with Oracle Applications 11i

NOTE.280167.1 : AS10g with Apps 11i - Summary of Login process

NOTE.357218.1 : Troubleshooting JDeveloper setup for Oracle Applications
NOTE.403339.1 : Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite Release 12 Upgrade

NOTE.463249.1 : After Clone Forms Is Trying To Connect To Target Instance
NOTE.386374.1 : How to enable/disable/change password of the listeners for Oracle Applications 11i

NOTE.454750.1 : Oracle Apps Release 12 with Oracle Database 10.2.0 interoperability notes

NOTE.428503.1 : Integrating Oracle E-Business Suite Release 11i with Oracle Database Vault 10.2.0.3

NOTE.443761.1 : How to check if a certain Patch was applied to Oracle Applications instance using 'adpatch'?

NOTE.291783.1 : Getting Started with the Oracle Grid Control Plug-in for Oracle Applications in Release 11i (AMP v1)

NOTE.468980.1 : How to Remove the Language Icons in the AppsLocalLogin.jsp

NOTE.398619.1 : Clone Oracle Applications 11i using Oracle Application Manager (OAM Clone)

NOTE.295606.1 : Oracle Application Server 10g with Oracle E-Business Suite Release 11i Troubleshooting

NOTE.169706.1 : Oracle® Database on AIX®,HP-UX®,Linux®,Mac OS® X,
Solaris®,Tru64 Unix® Operating Systems Installation and
Configuration Requirements Quick Reference (8.0.5 to 11.1)

NOTE.109665.1 : Organization Setup Frequently Asked Questions - FAQ
NOTE.434395.1 : ATG Service Request Creation
NOTE.438086.1 : Platform Migration with Oracle Applications Release 12
NOTE.469213.1 : How To Encrypt The Apps Password In Wdbsvr.App
NOTE.293369.1 : OPatch documentation list
NOTE.275379.1 : Script To Check What Workflow Related Patches Are Installed
NOTE.388577.1 : Configuring Oracle Applications Release 12 with 10g R2 RAC

NOTE.264157.1 : The correct NLS_LANG setting in Unix Environments
NOTE.91985.1 : Step by Step on Cloning the ORACLE_HOME (Including DB) and
NOTE.74838.1 : Migrating Apps Release 11.0 from UNIX Host To A Second

NOTE.396009.1 : Database Initialization Parameters for Oracle Applications Release 12

NOTE.391406.1 : How to get a clean Autoconfig Environment
NOTE.560719.1 : How to troubleshoot iSetup issues
NOTE.406376.1 : Oracle E-Business Tax Release 12 Known Issues
NOTE.577713.1 : On Windows, After 10g Upgrade, Running Autoconfig on Apps
NOTE.343917.1 : Frequently Asked Questions : Oracle E-Business Suite Support
NOTE.553831.1 : java.lang.ArrayIndexOutOfBoundsException Error when

NOTE.119319.1 : How to Replace Oracle Logo with Company Logo on Applications 11i Sign-On Screen

NOTE.554336.1 : How Do You Manually Generate A Form In Release 12 (frmcmp)

NOTE.444286.1 : How to manually generate a R12 report on Unix
NOTE.356433.1 : Using Oracle Applications Release 11i with Virtual Hostnames and Business Continuity

NOTE.555081.1 : Concurrent Manager Does Not Start if the Profile Option "Concurrent : GSM Enabled" is Set "Y" at Site Level

NOTE.149124.1 : Creating a StatsPack performance report
NOTE.471566.1 : Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit

NOTE.397757.1 : How to Speed Up Index Creation on FND_LOBS by indexing Only FND_HELP Data

NOTE.375127.1 : How to restart the adworker having status fixed,restart,wait
NOTE.353150.1 : OPatch Failing Validation Phase When Archiving Really Did Not Fail

NOTE.215527.1 : Maintenance Wizard Overview
NOTE.564465.1 : Sysadmin And User Responsibility Not Available
NOTE.219968.1 : SQL*Net, Net8, Oracle Net Services - Tracing and Logging at a Glance

NOTE.417122.1 : Resolving the Library Cache Locks
NOTE.419475.1 : Removing Credentials from a Cloned EBS Production Database

Oracle Applications 11i/12 Online Documentation

http://www.oracle.com/technology/documentation/applications.html

Note: There are many other notes on various issues available in Oracle Metalink
For any specific issue, you shall always contact ORACLE SUPPORT for complete assistance.

Archiver Tracing

2008-10-28T00:22:00.001-07:00

The init.ora parameter LOG_ARCHIVE_TRACE can be used to find problems with the archiver process. I recently used this to sort out some archiving issues with a standby database. The parameter is dynamically changable using ALTER SYSTEM.

The following values can be used. To get a combination of the required states add the numbers.
* 0 : Disables Tracing
* 1 : Records archiving of redo log files
* 2 : Records status of archiving for each destination
* 4 : Traces archival operation
* 8 : Tracks activity at the archive log destination
* 16 : Tracks in detail activity at archive log destination
* 32 : Records archive log destination parameter changes
* 64 : Tracks ARCn process state
* 128: Traces FAL server activity
* 512: Traces asynchronous log writer activity
*1024: Traces RFS client
*2048: Traces RFS/ARCn heartbeats

Oracle All Command Sheet

2008-10-26T00:11:00.000-07:00

http://www.oracle.com/technology/books/pdfs/portable_ch1.pdf

OCM

2008-10-25T09:56:00.000-07:00

Oracle Certified Master Profiles

The Oracle OCM credential is the most advanced Database Administrator certification. This credential is for senior database professionals with both classroom and on-the-job experience. Candidates must first obtain the OCA and OCP credentials. In addition, they must complete two advanced hands-on courses and pass the two-day practicum exam.

Solaris 10 (x86-32) Installation

2008-10-25T05:11:00.000-07:00

Refer following link for step by step installation

http://www.oracle-base.com/articles/misc/Solaris10X86-32Installation.php

RMAN Backup and Recovery Scenarios

2008-10-25T04:37:00.000-07:00

RMAN Backup and Recovery Scenarios

=> Complete Closed Database Recovery. System tablespace is missing
If the system tablespace is missing or corrupted the database cannot be started up so a complete closed database recovery must be performed.
Pre requisites: A closed or open database backup and archived logs.
1. Use OS commands to restore the missing or corrupted system datafile to its original location, ie:
cp -p /user/backup/uman/system01.dbf /user/oradata/u01/dbtst/system01.dbf
2. startup mount;
3. recover datafile 1;
4. alter database open;

=> Complete Open Database Recovery. Non system tablespace is missing
If a non system tablespace is missing or corrupted while the database is open, recovery can be performed while the database remain open.
Pre requisites: A closed or open database backup and archived logs.
1. Use OS commands to restore the missing or corrupted datafile to its original location, ie:
cp -p /user/backup/uman/user01.dbf /user/oradata/u01/dbtst/user01.dbf
2. alter tablespace offline immediate;
3. recover tablespace ;
4. alter tablespace online;

=> Complete Open Database Recovery (when the database is initially closed).Non system tablespace is missing
If a non system tablespace is missing or corrupted and the database crashed,recovery can be performed after the database is open.
Pre requisites: A closed or open database backup and archived logs.
1. startup; (you will get ora-1157 ora-1110 and the name of the missing datafile, the database will remain mounted)
2. Use OS commands to restore the missing or corrupted datafile to its original location, ie:
cp -p /user/backup/uman/user01.dbf /user/oradata/u01/dbtst/user01.dbf
3. alter database datafile3 offline; (tablespace cannot be used because the database is not open)
4. alter database open;
5. recover datafile 3;
6. alter tablespace online;

=> Recovery of a Missing Datafile that has no backups (database is open).
If a non system datafile that was not backed up since the last backup is missing,recovery can be performed if all archived logs since the creation of the missing datafile exist.
Pre requisites: All relevant archived logs.
1. alter tablespace offline immediate;
2. alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf’;
3. recover tablespace ;
4. alter tablespace online;
If the create datafile command needs to be executed to place the datafile on a location different than the original use:
alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf’ as ‘/user/oradata/u02/dbtst/newdata01.dbf’

=> Restore and Recovery of a Datafile to a different location.
If a non system datafile is missing and its original location not available, restore can be made to a different location and recovery performed.
Pre requisites: All relevant archived logs.

1.Use OS commands to restore the missing or corrupted datafile to the new
location, ie:
cp -p /user/backup/uman/user01.dbf /user/oradata/u02/dbtst/user01.dbf
2. alter tablespace offline immediate;
3. alter tablespace rename datafile ‘/user/oradata/u01/dbtst/user01.dbf’ to ‘/user/oradata/u02/dbtst/user01.dbf’;
4. recover tablespace ;
5. alter tablespace online;

=>Control File Recovery
Always multiplex your controlfiles. Controlfiles are missing, database crash.
Pre requisites: A backup of your controlfile and all relevant archived logs.
1. startup; (you get ora-205, missing controlfile, instance start but database is not mounted)
2. Use OS commands to restore the missing controlfile to its original location:
cp -p /user/backup/uman/control01.dbf /user/oradata/u01/dbtst/control01.dbf
cp -p /user/backup/uman/control02.dbf /user/oradata/u01/dbtst/control02.dbf
3. alter database mount;
4. recover automatic database using backup controlfile;
5. alter database open resetlogs;
6. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.

=>Incomplete Recovery, Until Time/Sequence/Cancel
Incomplete recovery may be necessaire when an archived log is missing, so recovery can only be made until the previous sequence, or when an important object was dropped, and recovery needs to be made until before the object was dropped.
Pre requisites: A closed or open database backup and archived logs, the time or sequence that the ‘until’ recovery needs to be performed.
1. If the database is open, shutdown abort
2. Use OS commands to restore all datafiles to its original locations:
cp -p /user/backup/uman/u01/*.dbf /user/oradata/u01/dbtst/
cp -p /user/backup/uman/u02/*.dbf /user/oradata/u01/dbtst/
cp -p /user/backup/uman/u03/*.dbf /user/oradata/u01/dbtst/
cp -p /user/backup/uman/u04/*.dbf /user/oradata/u01/dbtst/
etc…
3. startup mount;
4. recover automatic database until time ‘2004-03-31:14:40:45′;
5. alter database open resetlogs;
6. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.Alternatively you may use instead of until time, until sequence or until cancel:
recover automatic database until sequence 120 thread 1; OR
recover database until cancel;

=>Rman Recovery Scenarios
Rman recovery scenarios require that the database is in archive log mode, and that backups of datafiles, control files and archived redolog files are made using Rman. Incremental Rman backups may be used also.
Rman can be used with the repository installed on the archivelog, or with a recovery catalog that may be installed in the same or other database.
Configuration and operation recommendations:
Set the parameter controlfile autobackup to ON to have with each backup a
controlfile backup also:
configure controlfile autobackup on;
set the parameter retention policy to the recovery window you want to have,
ie redundancy 2 will keep the last two backups available, after executing delete obsolete commands:
configure retention policy to redundancy 2;
Execute your full backups with the option ‘plus archivelogs’ to include your archivelogs with every backup:
backup database plus archivelog;
Perform daily maintenance routines to maintain on your backup directory the number of backups you need only:
crosscheck backup;
crosscheck archivelog all;
delete noprompt obsolete backup;
To work with Rman and a database based catalog follow these steps:
1. sqlplus /
2. create tablespace repcat;
3. create user rcuser identified by rcuser default tablespace repcat temporary tablespace temp;
4. grant connect, resource, recovery_catalog_owner to rcuser
5. exit
6. rman catalog rcuser/rcuser # connect to rman catalog as the rcuser
7. create catalog # create the catalog
8. connect target / #

=>Complete Closed Database Recovery. System tablespace is missing
In this case complete recovery is performed, only the system tablespace is missing,so the database can be opened without reseting the redologs.
1. rman target /
2. startup mount;
3. restore database;
4. recover database;
5. alter database open;

=>Complete Open Database Recovery. Non system tablespace is
missing,database is up
1. rman target /
2. sql ‘alter tablespace offline immediate’;
3. restore datafile 3;
4. recover datafile 3;
5. sql ‘alter tablespace online’;

=> Complete Open Database Recovery (when the database is initially
closed).Non system tablespace is missing
A user datafile is reported missing when tryin to startup the database. The datafile can be turned offline and the database started up. Restore and recovery are performed using Rman. After recovery is performed the datafile can be turned online again.
1. sqlplus /nolog
2. connect / as sysdba
3. startup mount
4. alter database datafile ‘’ offline;
5. alter database open;
6. exit;
7. rman target /
8. restore datafile ‘’;
9. recover datafile ‘’;
10. sql ‘alter tablespace online’;

=> Recovery of a Datafile that has no backups (database is up).
If a non system datafile that was not backed up since the last backup is missing,recovery can be performed if all archived logs since the creation of the missing datafile exist. Since the database is up you can check the tablespace name and put it offline. The option offline immediate is used to avoid that the update of the datafile header.
Pre requisites: All relevant archived logs.
1. sqlplus ‘/ as sysdba’
2. alter tablespace offline immediate;
3. alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf;
4. exit
5. rman target /
6. recover tablespace ;
7. sql ‘alter tablespace online’;
If the create datafile command needs to be executed to place the datafile on a location different than the original use:
alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf’ as ‘/user/oradata/u02/dbtst/newdata01.dbf’

=> Restore and Recovery of a Datafile to a different location. Database is up.
If a non system datafile is missing and its original location not available, restore can be made to a different location and recovery performed.
Pre requisites: All relevant archived logs, complete cold or hot backup.
1. Use OS commands to restore the missing or corrupted datafile to the new location, ie:
cp -p /user/backup/uman/user01.dbf /user/oradata/u02/dbtst/user01.dbf
2. alter tablespace offline immediate;
3. alter tablespace rename datafile ‘/user/oradata/u01/dbtst/user01.dbf’ to ‘/user/oradata/u02/dbtst/user01.dbf’;
4. rman target /
5. recover tablespace ;
6. sql ‘alter tablespace online’;

=> Control File Recovery
Always multiplex your controlfiles. If you loose only one controlfile you can replace it with the one you have in place, and startup the Database. If both controlfiles are missing, the database will crash.
Pre requisites: A backup of your controlfile and all relevant archived logs. When using Rman alway set configuration parameter autobackup of controlfile to ON. You will need the dbid to restore the controlfile, get it from the name of the backed up controlfile.It is the number following the ‘c-’ at the start of the name.
1. rman target /
2. set dbid
3. startup nomount;
4. restore controlfile from autobackup;
5. alter database mount;
6. recover database;
7. alter database open resetlogs;
8. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.
Incomplete Recovery, Until Time/Sequence/Cancel
Incomplete recovery may be necessaire when the database crash and needs to be recovered, and in the recovery process you find that an archived log is missing. In this case recovery can only be made until the sequence before the one that is missing.
Another scenario for incomplete recovery occurs when an important object was dropped or incorrect data was committed on it.
In this case recovery needs to be performed until before the object was dropped.
Pre requisites: A full closed or open database backup and archived logs, the time or sequence that the ‘until’ recovery needs to be performed.
1. If the database is open, shutdown it to perform full restore.
2. rman target \
3. startup mount;
4. restore database;
5. recover database until sequence 8 thread 1; # you must pass the thread, if a single instance will always be 1.
6. alter database open resetlogs;
7. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.Alternatively you may use instead of until sequence, until time, ie: ‘2004-12-28:01:01:10′.

How do I find the overall database size?

2008-10-25T03:19:00.000-07:00

how many megabytes are allocated to ALL datafiles:

select sum(bytes)/1024/1024 "Meg" from dba_data_files;

To get the size of all TEMP files:
select nvl(sum(bytes),0)/1024/1024 "Meg" from dba_temp_files;

To get the size of the on-line redo-logs:
select sum(bytes)/1024/1024 "Meg" from sys.v_$log;

Putting it all together into a single query:

select a.data_size+b.temp_size+c.redo_size "total_size"
from ( select sum(bytes) data_size
from dba_data_files ) a,
( select nvl(sum(bytes),0) temp_size
from dba_temp_files ) b,
( select sum(bytes) redo_size
from sys.v_$log ) c
/

Core DBA

2008-10-25T03:14:00.000-07:00

Install Oracle 11g on Linux (Red Hat Enterprise Linux – 4)

2008-10-22T21:38:00.000-07:00

Operating System Details:
Linux – (Red Had Enterprise Linux – 4.0)

Database Version Details:
Oracle 11g Release 1 (11.1.0)

Download Software: (linux_11gR1_database.zip)
http://www.oracle.com/technology/software/products/database/index.html

Pre-Installation Tasks:

* Prepare the stage area for Oracle Software on the Serve
----- Choose the mount point where software needs to be staged.
/u01

----- Create the stage directories and change the ownership and permissions.
Su – root
Password: xxxxx ( Enter your root password Here)
# mkdir –p /u01/11gStage
# chown –R oracle:dba /u01/11gStage
# chmod –R 755 /u01/11gStage

----- Copy the software in the stage area
ftp the downloaded Oracle 11g software in this stage area and change the ownership and permissions.
$ cd /u01/11gStage
$ chown oracle:dba linux_11gR1_database.zip
$ chmod 755 linux_11gR1_database.zip

* Performing the pre-installation tasks
----- Check the size of physical RAM
$ grep MemTotal /proc/meminfo
Note: During the installation it will say failed when it checks the available physical RAM is less than 900 MB , no problem even if you have less than 900MB (if it’s for testing purpose), you can continue with the installation.

----- Check the size of SWAP space
$ grep SwapTotal /proc/meminfo

----- Check the free disk space in “/tmp” directory
$ df -k /tmp

----- Check the free space available on the system
$ df –k

* Checking the Software Requirements
----- The version of Linux is installed
$ uname –a

----- Check the following required packages are installed.
binutils-2.15.92.0.2-18
compat-libstdc++-33.2.3-47.3
elfutils-libelf-0.97-5
elfutils-libelf-devel-0.97-5
glibc-2.3.9.4-2.19
glibc-common-2.3.9.4-2.19
glibc-devel-2.3.9.4-2.19
gcc-3.4.5-2
gcc-c++-3.4.5-2
libaio-devel-0.3.105-2
libaio-0.3.105-2
libgcc-3.4.5
libstdc++-3.4.5-2
libstdc++-devel-3.4.5-2
make-3.80-5
sysstat-5.0.5
unixODBC-2.2.11
unixODBC-devel-2.2.11

----- To check RPMS are installed or not.
Login as ROOT user
# rpm –q libaio-devel-0.3.105-2
# rpm –q unixODBC-devel-2.2.11
……………………………
……………………………
Like this check for all the above RPMS.

----- Install the missing packages or rpms.
First download the missing RPMS from the relavent Linux websites, or if you have the CDs with you, used during the Linux Installation, you can use them to find the missing rpms from that.

----- To install or upgrade RPMS are installed or not.
Login as the ROOT user
# rpm –ivh unixODBC-devel-2.2.11.3-1.i386.rpm
Or
# rpm –Uvh unixODBC-devel-2.2.11.3-1.i386.rpm

* Creating Required Operating System Groups and Users
----- Check and create DBA group
Su – root
Password: xxxxx ( Enter your root password Here)
# cat /etc/group|grep dba
# /usr/sbin/groupadd dba

----- Check and create ORACLE user and assign dba group.
# cat /etc/passwd|grep oracle
# /usr/sbin/useradd –d “/home/oracle” –m –g dba –c “Oracle 11g Owner” oracle

----- Set the password of the ORACLE user
# passwd oracle

* Create Required Directories
----- The Oracle Base Directory and Oracle Home Directories
Su – root
Password: xxxxxx (Enter the password for root here)
# mkdir –p /u01/app/oracle/product/11.0.1
# mkdir –p /u02/oradata

----- Chang the owner and group of the directories
# chown –R oracle:dba /u01/app/oracle/product/11.0.1
# chown –R oracle:dba /u02/oradata

----- Change the permissions of the directories
# chmod –R 755 /u01/app/oracle/product/11.0.1
# chmod –R 755 /u02/oradata

* Configuring Kernel Parameters
----- Check the current parameters and values in /etc/sysctl.conf
# cat /etc/sysctl.conf
Note: Take a back up of this file before changing the values and parameters.
# cp –p /etc/sysctl.conf /etc/sysctl.conf.old

----- Check and add the below parameters in /etc/sysctl.conf
fs.file-max = 76800
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144

----- To change the current values of the kernel parameters
# /sbin/sysctl -p

----- Make sure that the parameters and values in /etc/system file are set properly
# cat /etc/sysctl.conf

----- Check and set the following lines in the /etc/security/limits.conf file.
Note: Take a back up of this file before changing the values and parameters.
# cp –p /etc/security/limits.conf /etc/security/limits.conf.old

oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536

----- Add or edit the following line in the /etc/pam.d/login file, if it does not already exist
Note: Take a back up of this file before changing the values and parameters.
# cp –p /etc/pam.d/login /etc/pam.d/login .old

session required /lib/security/pam_limits.so
session required pam_limits.so

* Configuring the Oracle User’s Environment
----- Check and change the contents of .profile or .lgoin files.
$ vi .bash_profile

----- Remove the oracle environment variables set already.

----- Check the DISPLAY variable is set, if not, then set the variable.
$ echo $DISPLAY
$ DISPLAY=:0.0
$ export DISPLAY
Su – root
Password: xxxx ( Enter the root password here)
# xhost +

----- Make sure that xclock command is running
$ xlcok

Installation of Oracle Software:

* Login as oracle on the server
Su – oracle
Password: xxxxx (Oracle user password)

* Go the directory where Oracle software is staged.
$ cd /u01/11gStage

* Unzip the software file
$ unzip linux_11gR1_database.zip

* Run/Launch the runinstaller
$ cd /u02/11gStage/database
$./.runInstaller

* Answer to the subsequent wizards or screens options with the proper information

Note: Fore more instructions one creating the database using DBCA tool or Manual method, please refer my blog link for the same.

http://sabdarsyed.blogspot.com/2007/08/dear-friends-following-are-general.html
Conclusion: I have followed the above series of steps for installing on one of Linux boxes. I would request and suggest them to go through the referenced links below, who are willing to do this with other options during the installation and as per their requirement.

References:

Oracle Database Installation Guide 11g Release 1 (11.1) for Linux

http://download.oracle.com/docs/cd/B28359_01/install.111/b32002/pre_install.htm#CHDHFGBJ

Installing Oracle Database 11g on Linux

http://www.oracle.com/technology/obe/11gr1_db/install/dbinst/dbinst.htm

Oracle 11g Documentations

http://www.oracle.com/pls/db111/homepage

Others:

http://www.datasoftech.com/library.html

Your suggestions would be appreciated !!!

ASM on Windows

2008-10-03T08:18:00.000-07:00

ASM Creation (Windows)

You can follow this steps and create a ASM diskgroup on your local machine and play with it ( Windows)

1) Creating a dummy disks

F:\>mkdir asmdisks
F:\>cd asmdisks
F:\asmdisks>asmtool -create F:\asmdisks\ disk1 512
F:\asmdisks>asmtool -create F:\asmdisks\ disk2 512
F:\asmdisks>asmtool -create F:\asmdisks\ disk3 512

Now you have 3 disks(dummy) of 512mb each which can be used to create a ASM disk group.

2) Create ASM instance

a) Configure Cluster Synchronization Servie

C:\>c:\oracle\product\ 10.2.0\db_ 1\BIN\localconfi g add

Step 1: stopping local CSS stack
Step 2: deleting OCR repository
Step 3: creating new OCR repository
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'ap\arogyaa' , privgrp ''..
Operation successful.
Step 4: creating new CSS service
successfully created local CSS service
successfully reset location of CSS setup
b) Create Init pfile
Open notepad edit the following parameters and save file as "C:\oracle\product\ 10.2.0\db_ 1\database\ init+ASM. ora"
INSTANCE_TYPE= ASM
DB_UNIQUE_NAME= +ASM
LARGE_POOL_SIZE= 8M
ASM_DISKSTRING= 'F:\asmdisks\ *'
_ASM_ALLOW_ONLY_ RAW_DISKS= FALSE

c) Create service and password file
oradim will create an ASM instance and start it automatically.
c:\> orapwd file=C:\oracle\ product\10. 2.0\db_1\ database\ PWD+ASM.ora password=asm
c:\> oradim -NEW -ASMSID +ASM -STARTMODE auto

3) Create ASM disk group
a) Create asm disk group
SQL> select path, mount_status from v$asm_disk;
PATH MOUNT_S
------------ --------- --------- --
F:\ASMDISKS\ DISK1 CLOSED
F:\ASMDISKS\ DISK3 CLOSED
F:\ASMDISKS\ DISK2 CLOSED

SQL> create diskgroup data external redundancy disk
2 'F:\ASMDISKS\ DISK1',
3 'F:\ASMDISKS\ DISK2',
4* 'F:\ASMDISKS\ DISK3';
Diskgroup created.
b) Change PFILE to SPFILE, Add ASM Diskgroup parameter and your all set to go and use ASM.
SQL> create spfile from pfile;
SQL> startup force;
SQL> alter system set asm_diskgroups= data scope=spfile;
SQL> startup force;
SQL> startup force
ASM instance started
Total System Global Area 83886080 bytes
Fixed Size 1247420 bytes
Variable Size 57472836 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL>
Now you can go ahead and use your DBCA and create a database and on step 6 of 13, you can use Automatic Storage management as your Filesystem.

2008-06-09T07:25:00.000-07:00

I am Nandakumar recently completed my 10g OCM . I treat this as great achievement as i have prepared extensively and passed with higher grade.
I am currently working as ORACLE DBA in ORACLE India Pvt Ltd for 3 years.
Please feel free to post any doubts/assistance needed on 10g OCM Exam