Tuesday, July 27, 2010

ASM (Automatic storage Management)

ASM (Automatic storage Management)
ASM is storagement for Oracle Data.ASM is an extension to the OMF(Oracle Managed Files) it not only manages the storage automatically(reducing DBA job and time) it does the mirroring as well.

ASM is controlled by ASM instance found on each node.

Benefits of ASM:
• You don’t need to assign a layout for the Data, you just assign DISKS and that’s all.
• ASM will manage thousands of files automatically.
• It assigns the DISK groups to the DISKS.
• It is almost a Logical Volume Manager.
• It has built in mirring and stripping techniques.
• It creates and manages files automatically
• It automatically balances the IO balance between DISK groups.
• Manages Oracle files without specifying file and directory names.

What is ASM Database:
• When ASM is enabled, ORACLE will automatically create a small database where it will keep the metadata about ASM.
• The default Table Space created in ASM database is +ASM
• The default RAC nodes will appear as +ASMn
• ASM can be managed with srvctl commands

What are ASM Disks:
Disks assigned to ASM DISK groups are called ASM DISKS.
Files which are written to ASM DISKS are called ASM Files.

There are three types of ASM Redundancies.
1.Normal Redundancy
2.High Redundancy
3.External Redundancy

1.Normal Redundancy:
Oracle will create a mirror DISK for each DISK.

Oracle will create two mirror DISKS for each DISK.

3.External Redundancy
External Redundancy means that you will use some external hardware or tool for DISK mirroring. ORACLE wont do it for you.

Types of Files stored in ASM:
Data Files, Control Files, DataPump Dumpsets, table spaces, data guard files, spfiles.
Oracle Binaries, trace files and OS files cannot be stored in ASM.

ASM Instance and its Creation:
To create ASM instance you need to create a pramater file in /tmp directory.
Contents of SPfile would be


Creating SPFILE using ASM parameter file:
Sqlplus “/ as sysdba”
Create SPFile from – ASM ParameterFile—

Start the ASM instance with nomount mode:
Startup nomount

Now you can add DISK Groups and files.

You can use the Create DISKGroup command to create diskgroups.in this command you have to define the type of redundancy as well.
Note: you can alter,resize,drop,undrop DISGROUPS and files through SQL files.

Tuesday, July 20, 2010

Installing Oracle GoldenGate on Windows (Normal and Clustered)

Installing Oracle GoldenGate on Windows (Normal and Clustered)
Step 1.
To specify Oracle variables on Windows systems
On the desktop or Start menu (depending on the Windows version), right-click My
Computer, and then select Properties.
In Properties, click the Advanced tab.
Click Environment Variables.
Under System Variables, click New.
For Variable Name, type ORACLE_HOME.
For Variable Value, type the path to the Oracle binaries.
Click OK.
Click New again.
For Variable Name, type ORACLE_SID.
For Variable Value, type the instance name.
Click OK.

Step 2.
Unzip the GoldenGate software into a folder on your drive.

Step 3:
Download the Visual C++ Redistributable Packege from below link:

Step 4:
Go the GoldenGate directory through command prompt and type:
It will bring the GoldenGate prompt, In the GoldenGate prompt type:
Again type GGSCI and in there type:
It should open a text editor, in the text editor type
PORT 7809
And save the file.
Note: you can gave any available port.
Step 5.
Type exit from the GGSCI prompt and type following command to register manager as a window service:
In the GGSCI prompt type START MANAGER to start manager and STOP MANAGER to stop manager.
After that type
Install addevents Adds Oracle GoldenGate events to the Windows Event Manager. By default, Oracle GoldenGate errors are generic. To produce more specific error content, copy the following files from the Oracle GoldenGate installation directory to the SYSTEM32 directory.

Adding Oracle GoldenGate as a Windows cluster resource

* In the Cluster Administrator, select File>New>Resource.
* In the New Resource dialog box, provide a descriptive name for the Oracle GoldenGate
Manager (need not be its actual name). For Resource Type, select Generic Service. For Group,
select the group that contains the database instance to which Oracle GoldenGate will connect
* Click Next.
* In the Possible Owners dialog box, select the nodes on which Oracle GoldenGate will run.
* Click Next.
* In the GGS Manager Service Properties dialog box, click the Dependencies tab, and add the
following to the Resource dependencies list:
The database resource group
The disk resource containing the Oracle GoldenGate directory
The disk resource containing the database transaction log files
The disk resource containing the database transaction log backup files
*Click Apply, then OK.
In the Generic Service Parameters dialog box, type either the default Manager service name
of GGSMGR or, if applicable, the custom name specified in the GLOBALS file.
*Click Next.
*Click Finish to exit the wizard.
In the Cluster Administrator tree, right-click the Manager resource and select Properties.
* Click the Advanced tab, and deselect Affect the Group. This is a recommendation, but you
can configure it as needed for your environment.
* Click Apply.
* Bring the cluster resource online to verify that it was installed correctly.
* Take the resource offline again.
* Move the group to the next node in the cluster. When the group has been successfully
moved to the second node, the Manager resource should still be offline.
* Log onto the second node.
* Install Oracle GoldenGate Manager as a service on this node by running the install
program as you did on the previous node. If you created a custom name for Manager in
the GLOBALS file, that name will be used.
* Bring the resource online to verify that it is running correctly on this node.
* Repeat from step 16 for each additional node in the cluster.




  • You must have Perl 5.00503 (or later) installed under the ORACLE_HOME, or elsewhere within the host environment.

·                     If the Oracle inventory is not setup correctly this utility will fail. To check accessibility to the inventory you can use the command:

     % ORACLE_HOME/OPatch/opatch lsinventory

·                     OPatch scripts should be copied to $ORACLE_HOME/OPatch directory.

  • Prior to the Install Phase, following checks are performed:
- Conflicts with other patches

- Conflicts with subset patches (existing patch is a subset of the patch being installed)

-       If a conflict is found, please abort the install and contact Oracle Support Services.

-       If a subset is found, please continue the install, as all fixes for the subset patch are included in the patch being installed.  The subset patch(s) will be automatically rolled back prior to the installation of the new patch.

-       Shutdown all instances that are running under ORACLE_HOME being patched.

Installation Steps:
1- Set your current directory to the directory where the patch is located:

cd 7019661

·                     Ensure that the directory containing the opatch script appears in your $PATH; then enter the following command:
            % opatch apply
    % ORACLE_HOME/OPatch/opatch apply

Patch Deinstallation Instructions:
  Use the following command:

    % cd 7019661
    % ORACLE_HOME/OPatch/opatch rollback -id 7019661

Wednesday, July 14, 2010

Installation of Oracle WebLogic Server 11gR1 (10.3.2) on RHEL 5.5

In this article I will take you through step by step installation of Oracle Weblogic Server.
Installation of Oracle WebLogic Server 11gR1 (10.3.2).
Before installing, create OS users and group.

groupadd dba
useradd -g dba -G oinstall oraoem
mkdir /u01/app/oraoem/Middleware
chown -R oraoem:dba /u01/app/oraoem/Middleware