Blog Loud

Transaction Management with LogMiner and Flashback Data Archive

2011-10-19T14:47:00.001+05:00

LogMiner is an often dismissed yet very strong implement in the Oracle Database. It is employed to extract DML assertions from the redo log files—the primary SQL that produced the transaction and even the SQL that can change back the transactions. (For an introduction to LogMiner and how it works, cite to my Oracle Magazine portion "Mining for Clues.") Until now, this strong implement was ordinarily under-appreciated due to the deficiency of a more simple interface. In Oracle Database 11g, even so, Oracle Enterprise Manager has a graphical interface to extract transaction from the redo logs employing LogMiner,

which makes it greatly not hard to use the implement to appraise and rollback transactions. (Note: As in earlier versions, you can carry on to use the DBMS_LOGMNR parcel to put on lead line-driven log prospecting if you wish.)
Let's observe an instance how this is done. To empower log prospecting, you want only less noteworthy supplemental logging empowered for the database or a least the table. Flashback Transaction demands main key logging. To empower it for the every part of database, subject the subsequent commands:

SQL> alter database add supplemental log data;
 
Database altered.
 
SQL> alter database add supplemental log data (primary key) columns;
 
Database altered.

Now, consider the following statements issued by an application against your database:

SQL> insert into res values (100002,sysdate,12,1);
 
1 row created.
 
SQL> commit;
 
Commit complete.

SQL> update res set hotel_id = 13 where res_id = 100002;

1 row updated.
 
SQL> commit;
 
Commit complete.

SQL> delete res where res_id = 100002;
 
1 row deleted.
 
SQL> commit;
 
Commit complete.

Note the  assertions  carefully: each one is  was  winning   by a  entrust    assertion,  which  suggests  that each  assertion  is a transaction. Now 
let's  observe  how you can  appraise  the transactions in LogMiner in Oracle 
Database 11g Database Control.

In the Enterprise Manager video screen, from the Database homepage, depart to the tab tagged Availability.

Click View and Manage Transactions, listed under Manage. This brings up the main LogMiner interface, as shown below:

You can move into precise assortments in time or SCNs to explore for transactions. In the diagram atop, I have moved into a assortment of time to explore in the Query Time Range. In the Query Filter, I have employed only the SCOTT's transactions, because that was employed to put on all the DMLs. In the Advanced Query segment, you can move into any supplemental filter. After all paddocks are moved into, snap Continue.
This hits up the Log Mining method that explorations through the redologs (both online and archived, if needed) and finds the transactions distributed by the customer SCOTT. After the method is concluded, you will observe the effects screen.
The apex part of the effects video screen views like this:

The effects suggest that the explore encountered two transactions by SCOTT, which changed two records.
The foundation part of the video screen presentations the particulars of those transactions. Here is a partial scenery of the screen. You can observe the transactions present as 1 ins (meaning "1 penetrate statement"). The leftmost post presentations the transaction identifiers (XID), a number that solely acknowledges a transaction.

If you click on that transaction identifier, you can see the details of that transaction as shown in the screen below:

As you can perceive, you can exert Database Control to hunt and diagnose the transactions. Click the buttons Previous Transaction and Next Transaction to scroll through all the transactions found via the search.

Use Cases

How can you exert this feature? Well, a figure of ways. The majority significant exert may be to discover "who" did "what." If you don't have auditing enabled for performance purposes, or just haven't retained the audit listing, all you have to do is to hunt for the evidence in the LogMiner interface via mining the redo logs—online as well as archived ones. In the hunt screen, you can enter else filtering conditions in the Advanced Query field beneath Query Filter.
Suppose you want to locate a transaction where the record for the RES_ID = 100002 was inserted, deleted, or updated. You can hunt for a particular quality in the redo river via employing the operate column_present in the dbms_logmnr bundle as shown below:

This run will obtain all the transactions that fascinated 100002 in the RES_ID column in RES office desk below the SCOTT schema.
You can also exercise this attribute to unearth the DDL commands liberated against the database. To do that, decide the radio button View DDL Only in the Query Filter section.

Backout of Selected Transactions

When you check a transaction, what do you want do with it? One thought—perhaps the intent you are staring into the transaction in the first place—is that the transaction was organised in fault and you want to undo it. That's rightly simple; if the transaction is an usher in, you just have to delete it; or if it is an update, afterward the undo will be updating the row to the major value.
However, message the transactions adapted in the case carefully. The first transaction ushers in a row. The second one updates the row just inserted and the third one deletes that very row. The first one (the insert) is the transaction you want to backout. But, here is a problem; the row is already deleted by the afterwards transactions; so what is the undo transaction overseen to be, in this case?
This is where the Dependent Transaction seeing attribute in Oracle Database 11g comes handy. Click Flashback Transaction. After numerous tracks down, it will prevailing a screen interchangeable to below:

This video screen presentations you the reliant transactions and renew and deletes as well. Now when you back-out the transaction, you can back-out the dependents as well. To perform so, decide the Cascade broadcasting button from the table under and snap OK.

It will show you the different transactions you want backed out; click the Transaction IDs to see that what SQL statements Oracle will issue to undo the specific transaction.

For instance, to undo the insert, it has to issue a delete, as shown above. If you click on the next transaction (just below it), you will see the details of what needs to be done to back that one out:

You get the idea. Click Submit and all these transactions will be rolled back, in one sweep. This is the cleanest way to undo a transaction and its dependents.

Command Line Interface

What if you don't have get access to to the Enterprise Manager or possibly you desire this finished through a script? The bundle DBMS_FLASHBACK, which is furthermore present in Oracle Database 10g, has a new method called TRANSACTION_BACKOUT. This method is overloaded so you have to overtake the worth to the entitled parameters, as shown below.

declare

   trans_arr xid_array;

begin

   trans_arr := xid_array('030003000D040000','F30003000D04010');

   dbms_flashback.transaction_backout (

        numtxns         => 1,

        xids            => trans_arr,

        options         => dbms_flashback.cascade

);

end;

The kind xid_array is furthermore new in Oracle Database 11g. It is present to overtake a sequence of transaction identifiers to the procedure.

Other LogMiner Improvements

If you have been utilising XMLType as a facts and numbers kind and you have more causes to use it in Oracle Database 11g, you will be joyous to glimpse that the XML facts and numbers is mined as well in LogMiner. It displays up both in SQL_REDO and SQL_UNDO columns.
You can set an choice called SKIP_CORRUPTION while beginning LogMiner which will skip the corrupt blocks in redo logs. So, you can still salvage legitimate facts and numbers from the redo logs even if it is partially damaged. Here is how you can use the advanced syntax:

begin

   dbms_logmnr.start_logmnr(

        options => dbms_logmnr.skip_corruption

) ;

end;

Flashback Data Archive

Oracle9i Database Release 2 presented the proverbial time appliance in the pattern of the Flashback Query, which permits you to choose the pre-changed type of the data. For demonstration, had you altered a worth from 100 to 200 and pledged, you can still choose the worth as of two minutes before even if the change was committed. This expertise utilised the pre-change facts and numbers from the alter segments. In Oracle Database 10g, this facility was increased with the introduction of Flashback Versions Query, where you can even pathway the alterations made to a strip as long as the alterations are still present in the alter segments.
However, there was a little problem: When the database is recycled, the alter facts and numbers is cleansed out and the pre-change standards disappear. Even if the database is not recycled, the facts and numbers may be elderly out of the alter segments to make room for new changes.
Since pre-11g flashback procedures count on the alter facts and numbers, which is accessible only for a short length, you can't actually use it over an expanded time span of time or for more enduring notes for example for auditing. As a workaround, we resorted to composing initiates to make more enduring notes of the alterations to the database.
Well, don't despair. In Oracle Database 11g, Flashback Data Archive blends the best of both worlds: it boasts the ease and power of the flashback queries but does not depend on transient storage like the undo. Rather, it notes alterations in a more enduring position, the Flashback Recovery Area.
Let's gaze at an example. (Note: you require to cause Automatic Undo Management for Flashback Data Archive to work.) First, you conceive a Flashback Data Archive, as shown below:

SQL>  conceive  flashback archive near_term

  2  tablespace far_near_term

  3  retention 1 month

  4  /

Flashback archive created.

For the time being disregard the significance of the period "retention"; we will revisit it later. (This is a position where the alterations will be recorded.) The archive is conceived in the tablespace far_near_term.

Assume you have to record alterations to a table called TRANS. All you require to manage is endow the Flashback Data Archive rank of the table to start notes the alterations in that archive.

SQL>  adjust  table trans flashback archive near_term;

Table altered.

This places the table into the Flashback Data Archive mode. All the alterations to the lines of the table will be now followed permanently. Let's glimpse a demonstration.

First, choose a exact strip of the table.

SQL>  choose  txn_amt from trans where trans_id = 2;

   TXN_AMT

----------

  19325.67

SQL>  revise  trans set txn_amt = 2000 where trans_id = 2;

1  strip  updated.

SQL> commit;

Commit complete.

Now, if you choose the strip, it will habitually brandish 2000 in this column. To find out the older worth as of a certain time, you can use the Flashback query as shown below:

elect txn_amt

from trans

as of timestamp to_timestamp ('07/18/2007 12:39:00','mm/dd/yyyy hh24:mi:ss')

where trans_id = 2;

   TXN_AMT

----------

  19325.67

Now, after some time, when the alter facts and numbers has been purged out of the alter segments, query the flashback facts and numbers again:

select txn_amt

from trans

as of timestamp to_timestamp ('07/18/2007 12:39:00','mm/dd/yyyy hh24:mi:ss')

where trans_id = 2;

It arrives back with the result: 19325.67. The alter is gone, so where did the facts and numbers arrive from?
Let's inquire Oracle. You can manage that utilising autotrace and glimpse the execution plan:

SQL> set autotrace traceonly explain

SQL>  choose  txn_amt

  2  from trans

  3  as of timestamp to_timestamp ('07/18/2007 12:39:00','mm/dd/yyyy hh24:mi:ss')

  4  where trans_id = 2;



Execution Plan

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

Plan hash value: 535458644



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



| Id  | Operation                 | Name               | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop

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

|   0 | SELECT STATEMENT          |                    |     2 |    52 |    10  (10)| 00:00:01 |       |

|   1 |  VIEW                     |                    |     2 |    52 |    10  (10)| 00:00:01 |       |

|   2 |   UNION-ALL               |                    |       |       |            |          |       |

|*  3 |    FILTER                 |                    |       |       |            |          |       |

|   4 |     PARTITION RANGE SINGLE|                    |     1 |    52 |     3   (0)| 00:00:01 |     1 |     1

|*  5 |      TABLE ACCESS FULL    | SYS_FBA_HIST_68909 |     1 |    52 |     3   (0)| 00:00:01 |     1 |     1

|*  6 |    FILTER                 |                    |       |       |            |          |       |

|*  7 |     HASH JOIN OUTER       |                    |     1 |  4053 |    10  (10)| 00:00:01 |       |

|*  8 |      TABLE ACCESS FULL    | TRANS              |     1 |    38 |     6   (0)| 00:00:01 |       |

|   9 |      VIEW                 |                    |     2 |  8030 |     3   (0)| 00:00:01 |       |

|* 10 |       TABLE ACCESS FULL   | SYS_FBA_TCRV_68909 |     2 |  8056 |     3   (0)| 00:00:01 |       |

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



Predicate Information (identified by  procedure  id):

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



   3 - filter(NULL IS NOT NULL)

   5 - filter("TRANS_ID"=2 AND "ENDSCN">161508784336056 AND "ENDSCN"<=1073451 AND ("STARTSCN" IS NULL

              OR "STARTSCN"<=161508784336056))

   6 - filter("F"."STARTSCN"<=161508784336056 OR "F"."STARTSCN" IS NULL)

   7 - access("T".ROWID=("F"."RID"(+)))

   8 - filter("T"."VERSIONS_STARTSCN" IS NULL AND "T"."TRANS_ID"=2)

  10 - filter(("ENDSCN" IS NULL OR "ENDSCN">1073451) AND ("STARTSCN" IS NULL OR "STARTSCN"<1073451))



Note

-----

   - dynamic  trying   utilised  for this statement

This yield responses the riddle "Where did the facts and numbers arrive from?"; it came from the table SYS_FBA_HIST_68909, which is a position in the Flashback Archive you characterised previous for that table. You can ascertain the table but it's not sustained by Oracle to exactly peek at that facts and numbers there. Anyway, I don't glimpse a cause you would desire to manage that.
The facts and numbers interior the archive is kept but until how long? This is where the keeping time span arrives into play. It's kept up to that period. After that, when new facts and numbers arrives in, the older facts and numbers will be purged. You can furthermore purge it yourself, e.g.

alter flashback archive near_term purge before scn 1234567;

Managing Flashback Archives

You can add more than one tablespace to an archive. Conversely you can get clear of a tablespace from one too. If you are arranging to use a tablespace that has other customer written knowledge as well, you run into the risk of choking with population the tablespace with the Flashback Data Archive written knowledge and moving out no space for the customer data. To lessen the risk, you can initiate a quota on how much space the archive can take indoors the tablespace. You can set the quota by:

alter flashback archive near_term modify tablespace far_near_term quota 10M;

You can review which desks have Flashback Data Archive turned on by querying the list of remarks view:

SQL> select * from user_flashback_archived_tables;

TABLE_NAME                     OWNER_NAME

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

FLASHBACK_ARCHIVE_NAME

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

TRANS                          ARUP

NEAR_TERM

You can find out about the archives by querying the dictionary view:

sql> select * from flashback_archives;

FLASHBACK_ARCHI FLASHBACK_ARCHIVE# RETENTION_IN_DAYS  PURGE_SCN STATUS

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

NEAR_TERM                        1                30    1042653

MED_TERM                         2               365    1042744

LONG_TERM                        3              1825    1042838

Using multiple archives lets you exercise them fruitfully in dissimilar situations. For instance, a hotel company's database may deficiency one year of reservation knowledge but three years of payments. So you can define multiple archives with dissimilar retention policies and distribute them to the tables. Or if you have a uniform retention policy, you can define simply one archive and generate it the default.

alter flashback archive near_term set default;

When you don't deficiency an archive for a office desk, you can turn it off with:

 alter table trans no flashback archive;

As you can suppose, you just enabled a forceful modification recording system without writing a single row of code.

Differences vs. Regular Auditing

How does Flashback Data Archive differ from regular auditing? First of all, the latter requires the audit_trail parameter be set to DB or DB_EXTENDED and the trails are written to the office desk summoned AUD$ in the SYSTEM tablespace. Flashback Data Archives can be defined on any tablespace (or more than one, even on parts of a tablespace where user knowledge exists) and thus can be defined on cheaper storage.
Second, auditing is grounded on autonomous transaction, which has numerous performance overhead. Flashback Data Archives are written by a committed background process summoned FBDA so there is smaller diagram impact on performance.
Finally, Flashback Data Archives can be purged at regular intervals automatically. Audit trails must be manually maintained.

Use Cases

Flashback Data Archive is handy for many purposes. Here are numerous ideas:

To audit for recording how knowledge changed
To enable an submission to undo modifications (correct mistakes)
To debug how knowledge has been changed
To heed with numerous justice that want knowledge must not be modified later numerous time. Flashback Data Archives are not regular office desks so they can't be modified by typical users.
Recording audit trails on cheaper storage thereby commending more retention at smaller diagram cost

How To- Ping Sitemap of Website Blogs

2011-10-19T10:30:00.001+05:00

XML sitemaps announce search engines about the sheets accessible to crawl on your website. Search motors find new sheets by navigating connections on websites. Sitemaps enhance seek motor crawling by supplying explicit data about the exact urls on your website. Sitemaps don’t double-check that your webpages will be indexed, but they normally boost both the possibility and pace of indexing.

If you have new content on your blog or website, it is careful to make certain the seek motors understand about this to get the content indexed as shortly as possible. One way this is finished is by pinging your xml sitemap. Although there are numerous seek motors and services you can ping your sitemap to, confirm you focus on the large-scale 3: Google, Bing, and Yahoo.

So, how manage you mechanically ping your revised sitemap each time your website updates? Read How to Ping Your Sitemap to Google, Yahoo, and Bing to find out:

If you’ve got an XML sitemap for your website, you can attentive the seek motors to revisions by typing a particularly formatted URL into your browser.

Bing is Microsoft’s freshly labelled and revamped seek motor that is profiting attractiveness and market share every day since its latest launch. It’s well renowned that Bing takes a long time to primarily catalogue a website, so ping their service when you launch a website and every time you revise content.

Their ping service is http://www.bing.com/webmaster/ping.aspx?siteMap=[your sitemap web address].

In my case this would be: http://www.bing.com/webmaster/ping.aspx?siteMap=http://www.bluefalconmarketing.com/sitemap.xml

You can manually ping Bing by going into the overhead url in a world broad web browser and pushing enter. I favour to automate this method, by going into the url into a ping register in WordPress. WordPress will then mechanically ping Bing each time I revise or submit a new post.

Google is the overriding explore motor, and you will like to report when a thing new or modifications becomes noticeable on your site.

The ping url is

http://www.google.com/webmasters/sitemaps/ping?sitemap=http://www.example.com/sitemap-file.xml,

in my case it would be http://www.google.com/webmasters/sitemaps/ping?sitemap=http://www.bluefalconmarketing.com/sitemap.xml

Again, you can manually visit this url to ping Google, or add the url to an automated pinging service if this is carried by your website development platform.

Yahoo’s ping service allows you notify them anytime your place modifications so their indicator can be renewed quicker. Their ping url is

http://search.yahooapis.com/SiteExplorerService/V1/updateNotification?appid=YahooDemo&url=http://www.domain.com/sitemap.xml, in my case this would be http://search.yahooapis.com/SiteExplorerService/V1/updateNotification?appid=YahooDemo&url=http://www.bluefalconmarketing/sitemap.xml

You can self-acting submit your renewed place depiction employing a pinging service or manually moving into the atop url.

If you don’t have an xml sitemap yet, you can use a free xml sitemap generator to get you started.

How To- Submit Your Blogs Website to Google

2011-10-19T10:17:00.001+05:00

Blogging is the newest passion for youth presently.
Many juvenile persons were rotating their vocations as bloggers.
Its likely because of the Globalization. Many new and juvenile bloggers
were developing every year. According to latest Technorati investigation over
1.8 million blogs were been listing every year. These statistics notify us the power of Blogging.

Blogging is not such a so straightforward task. You require to be persevering, require to compose proceed intelligent, require to be revised, require to present SEO, require to work on construction connection, and numerous more tasks.

This is the item, that I'm composing for sake of grave bloggers who are rotating their vocation as full time dedicated bloggers.

Google the primary search engine and is deliberated as the greatest source to move ahead traffic to one’s website. The most condensed concurrently Search Engine by any of the SEO experts. Submitting a blog/website to Google is the greatest task for any website to get indexed. If your website is indexed in Google, your work is wrapped up more than 60%.

Yahoo retains the next location after Google, in periods of effectiveness and traffic. Yahoo is a best seek engine with yahoo in person sponsoring numerous tools. Yahoo lives at 21% of Search Engine Share after Google.

Here are the Steps that you should pursue for submitting your website to Yahoo.

Yahoo Sitemaps is usefed if you want your blog/website to get indexed completely in Yahoo Search Engine.
Submit your blog/website to Yahoo Sitemaps.
For Submitting, Click on submit you Website or Webpage option and enter your blog/website address.
And then submit your site feed, for submitting Click on Submit Site Feed and enter the sitemap of your blog.
Finally add the feed of your Blog.

Bing a seek motor from Microsoft which is actually buzzing allover the world. This is commenced by Microsoft in alignment to give Google the large affray, by proposing more characteristics that Google. Most of the websites/blogs were currently indexed into Bing, as the Bing.com is utilising the database of MSN, though you can still submit your website to get indexed.

Here are the Steps that you should pursue for submitting your website to Bing.

Submit your blog/website to Bing here.
After that, enter your website details (your website/blog’s address) and the fill the CAPTCHA correctly and then click on submit.
Then a notification will be given to you. If you are interested to Submit another website, click on submit another website else click on return to bing.

Installation Of Grid Structure For Linux

2011-10-18T17:35:00.001+05:00

Install the Grid Infrastructure

Make sure both virtual machines are started, then login to "ol6-112-rac1" as the oracle user and start the Oracle installer.

$ cd /host/software/oracle/11gR2/11.2.0.3.0/linux64_grid

$ ./runInstaller

Select the "Skip software updates" option, then click the "Next" button.

Click the "SSH Connectivity..." button and enter the password for the "oracle" user. Click the "Setup" button to to configure SSH connectivity, and the "Test" button to test it once it is complete.

Click the "Identify network interfaces..." button and check the public and private networks are specified correctly. Once you are happy with them, click the "OK" button and the "Next" button on the previous screen.

Set the redundancy to "External", click the "Change Discovery Path" button and set the path to "/dev/asm*". Return the main screen and select all 4 disks and click the "Next" button.

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.

Adding read,write permissions for group.

Removing read,write,execute permissions for world.

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. Example output can be seen here (Node1, Node2).
Once the scripts have completed, return to the "Execute Configuration Scripts" screen on "rac1" and click the "OK" button.

We expect the verification phase to fail with an error relating to the SCAN, assuming you are not using DNS.

INFO: Checking Single Client Access Name (SCAN)...

INFO: Checking name resolution setup for "rac-scan.localdomain"...

INFO: ERROR:

INFO: PRVF-4664 : Found inconsistent name resolution entries for SCAN name "rac-scan.localdomain"

INFO: ERROR:

INFO: PRVF-4657 : Name resolution setup check for "rac-scan.localdomain" (IP address: 192.168.2.201) failed

INFO: ERROR:

INFO: PRVF-4664 : Found inconsistent name resolution entries for SCAN name "rac-scan.localdomain"

INFO: Verification of SCAN VIP and Listener setup failed

Provided this is the only error, it is safe to ignore this and continue by clicking the "Next" button.
Click the "Close" button to exit the installer.

The grid infrastructure installation is now complete.

Install the Database

Make sure the "ol6-112-rac1" and "ol6-112-rac2" virtual machines are started, then login to "ol6-112-rac1" as the oracle user and start the Oracle installer.

$ cd /host/software/oracle/11gR2/11.2.0.3.0/linux64_database

$ ./runInstaller

Uncheck the security updates checkbox and click the "Next" button and "Yes" on the subsequent warning dialog.

Enter "/u01/app/oracle/product/11.2.0/db_1" for the software location. The storage type should be set to "Automatic Storage Manager". Enter the appropriate passwords and database name, in this case "RAC.localdomain".

The RAC database creation is now complete.

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

Database unique name: RAC

Database name: RAC

Oracle home: /u01/app/oracle/product/11.2.0/db_1

Oracle user: oracle

Spfile: +DATA/RAC/spfileRAC.ora

Domain: localdomain

Start options: open

Stop options: immediate

Database role: PRIMARY

Management policy: AUTOMATIC

Server pools: RAC

Database instances: RAC2,RAC1

Disk Groups: DATA

Mount point paths:

Services:

Type: RAC

Database is administrator managed

$ srvctl status database -d RAC

Instance RAC1 is running on node ol6-112-rac1

Instance RAC2 is running on node ol6-112-rac2

The V$ACTIVE_INSTANCES view can also display the current status of the instances.

$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Tue Sep 27 22:20:14 2011

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,

Data Mining and Real Application Testing options

SQL> SELECT inst_name FROM v$active_instances;

INST_NAME

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

ol6-112-rac1.localdomain:RAC1

ol6-112-rac2.localdomain:RAC2

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://ol6-112-rac1.localdomain:1158/em".

Installation Of Linux RAC.

2011-10-18T16:53:00.001+05:00

Oracle Linux 6 installation as you would for a basic server. A general pictorial guide to the installation can be found here. More specifically, it should be a server installation with a minimum of 4G+ swap, firewall and SELinux disabled and the following package groups installed:

Base System > Base
Base System > Client management tools
Base System > Compatibility libraries
Base System > Hardware monitoring utilities
Base System > Large Systems Performance
Base System > Network file system client
Base System > Performance Tools

Base System > Perl Support
Servers > Server Platform
Servers > System administration tools
Desktops > Desktop
Desktops > Desktop Platform
Desktops > Fonts
Desktops > General Purpose Desktop
Desktops > Graphical Administration Tools
Desktops > Input Methods
Desktops > X Window System
Applications > Internet Browser
Development > Additional Development
Development > Development Tools

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

hostname: ol6-112-rac1.localdomain
IP Address eth0: 192.168.0.111 (public address)
Default Gateway eth0: 192.168.0.1 (public address)
IP Address eth1: 192.168.1.111 (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. This includes the 64-bit and 32-bit versions of some packages. The commented out packages are those already installed if you have followed the suggested package selection. There is no suitable "oracle-validated" package available at this time, so the packages need to be installed manually.

# From Oracle Linux 6 DVD
cd /media/cdrom/Server/Packages
#rpm -Uvh binutils-2.*
#rpm -Uvh compat-libstdc++-33*
#rpm -Uvh elfutils-libelf-0.*
#rpm -Uvh libaio-0.*
rpm -Uvh libaio-devel-0.*
#rpm -Uvh sysstat-9.*
#rpm -Uvh glibc-2.*
#rpm -Uvh glibc-common-2.*
#rpm -Uvh glibc-devel-2.* glibc-headers-2.*
rpm -Uvh ksh-2*
#rpm -Uvh make-3.*
#rpm -Uvh libgcc-4.*
#rpm -Uvh libstdc++-4.*
rpm -Uvh libstdc++-4.*.i686*
#rpm -Uvh libstdc++-devel-4.*
#rpm -Uvh gcc-4.*x86_64*
#rpm -Uvh gcc-c++-4.*x86_64*
#rpm -Uvh --allfiles elfutils-libelf-0*x86_64* elfutils-libelf-devel-0*x86_64*
rpm -Uvh elfutils-libelf-0*i686* elfutils-libelf-devel-0*i686*
rpm -Uvh libtool-ltdl*i686*
rpm -Uvh ncurses*i686*
rpm -Uvh readline*i686*
rpm -Uvh unixODBC*
cd /
eject


# Install the following package from the Oracle grid media after you've defined groups.
cd /your/path/to/grid/rpm
rpm -Uvh cvuqdisk*

Oracle Installation Prerequisites

Perform the following steps whilst logged into the "rac1" virtual machine as the root user.
If you are not using DNS, the "/etc/hosts" file must contain the following information.

127.0.0.1       localhost.localdomain   localhost
# Public
192.168.0.111   ol6-112-rac1.localdomain        ol6-112-rac1
192.168.0.112   ol6-112-rac2.localdomain        ol6-112-rac2
# Private
192.168.1.111   ol6-112-rac1-priv.localdomain   ol6-112-rac1-priv
192.168.1.112   ol6-112-rac2-priv.localdomain   ol6-112-rac2-priv
# Virtual
192.168.0.113   ol6-112-rac1-vip.localdomain    ol6-112-rac1-vip
192.168.0.114   ol6-112-rac2-vip.localdomain    ol6-112-rac2-vip
# SCAN
192.168.0.115   ol6-112-scan.localdomain ol6-112-scan
192.168.0.116   ol6-112-scan.localdomain ol6-112-scan
192.168.0.117   ol6-112-scan.localdomain ol6-112-scan

Note. The SCAN address should not really be defined in the hosts file. Instead is should be defined on the DNS to round-robin between 3 addresses on the same subnet as the public IPs. For this installation, we will compromise and use the hosts file.
If you are using DNS, then only the first line must be present in the "/etc/hosts" file. The other entries are defined in the DNS, as described here. Having said that, I normally include everything except the SCAN entries when using DNS.
Add or amend the following lines to the "/etc/sysctl.conf" file.

fs.aio-max-nr = 1048576
fs.file-max = 6815744
#kernel.shmall = 2097152 
#kernel.shmmax = 1054504960
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default=262144
net.core.rmem_max=4194304
net.core.wmem_default=262144
net.core.wmem_max=1048586

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  4096
oracle              hard    nofile  65536
oracle              soft    stack   10240

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

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

Either configure NTP, or make sure it is not configured so the Oracle Cluster Time Synchronization Service (ctssd) can synchronize the times of the RAC nodes. In this case we will deconfigure NTP.

# service ntpd stop
Shutting down ntpd:                                        [  OK  ]
# chkconfig ntpd off
# mv /etc/ntp.conf /etc/ntp.conf.orig
# rm /var/run/ntpd.pid

If you are using NTP, you must add the "-x" option into the following line in the "/etc/sysconfig/ntpd" file.

OPTIONS="-x -u ntp:ntp -p /var/run/ntpd.pid"

Then restart NTP.

# service ntpd restart

Create the new groups and users.

groupadd -g 1000 oinstall
groupadd -g 1200 dba
useradd -u 1100 -g oinstall -G dba oracle
passwd oracle

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

mkdir -p  /u01/app/11.2.0/grid
mkdir -p /u01/app/oracle/product/11.2.0/db_1
chown -R oracle:oinstall /u01
chmod -R 775 /u01/

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

ORACLE_HOSTNAME=ol6-112-rac1.localdomain; export ORACLE_HOSTNAME
ORACLE_UNQNAME=RAC; export ORACLE_UNQNAME
ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
GRID_HOME=/u01/app/11.2.0/grid; export GRID_HOME
DB_HOME=$ORACLE_BASE/product/11.2.0/db_1; export DB_HOME
ORACLE_HOME=$DB_HOME; export ORACLE_HOME
ORACLE_SID=RAC1; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
BASE_PATH=/usr/sbin:$PATH; export BASE_PATH
PATH=$ORACLE_HOME/bin:$BASE_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

alias grid_env='. /home/oracle/grid_env'
alias db_env='. /home/oracle/db_env'

Create a file called "/home/oracle/grid_env" with the following contents.

ORACLE_SID=+ASM1; export ORACLE_SID
ORACLE_HOME=$GRID_HOME; export ORACLE_HOME
PATH=$ORACLE_HOME/bin:$BASE_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

Create a file called "/home/oracle/db_env" with the following contents.

ORACLE_SID=RAC1; export ORACLE_SID
ORACLE_HOME=$DB_HOME; export ORACLE_HOME
PATH=$ORACLE_HOME/bin:$BASE_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

Once the "/home/oracle/grid_env" has been run, you will be able to switch between environments as follows.

$ grid_env
$ echo $ORACLE_HOME
/u01/app/11.2.0/grid
$ db_env
$ echo $ORACLE_HOME
/u01/app/oracle/product/11.2.0/db_1
$

Install Guest Additions

Log into the VM as the root user and add the "divider=10" option to the kernel boot options in "/etc/grub.conf" file to reduce the idle CPU load. The entry should look something like this.

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/mapper/vg_ol6112rac1-lv_root
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Oracle Linux Server-uek (2.6.32-100.34.1.el6uek.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.32-100.34.1.el6uek.x86_64 ro root=/dev/mapper/vg_ol6112rac1-lv_root rd_LVM_LV=vg_ol6112rac1/lv_root rd_LVM_LV=vg_ol6112rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk  rhgb quiet divider=10
        initrd /initramfs-2.6.32-100.34.1.el6uek.x86_64.img
title Oracle Linux Server (2.6.32-131.0.15.el6.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.32-131.0.15.el6.x86_64 ro root=/dev/mapper/vg_ol6112rac1-lv_root rd_LVM_LV=vg_ol6112rac1/lv_root rd_LVM_LV=vg_ol6112rac1/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk crashkernel=auto rhgb quiet divider=10
        initrd /initramfs-2.6.32-131.0.15.el6.x86_64.img

Click on the "Devices > Install Guest Additions" menu option at the top of the VM screen, then run the following commands.

cd cd /media/VBOXADDITIONS_4.1.4_74291
export MAKE='/usr/bin/gmake –i'
sh ./VBoxLinuxAdditions.run

The VM will need to be restarted for the additions to be used properly. The next section requires a shutdown so no additional restart is needed at this time.

Create Shared Disks

Shut down the "rac1" virtual machine using the following command.

# shutdown -h now

Create 4 sharable virtual disks and associate them as virtual media using one of the following sets of commands on the host server.

$ mkdir -p /u04/VirtualBox/ol6-112-rac
$ cd /u04/VirtualBox/ol6-112-rac
$
$ # Create the disks and associate them with VirtualBox as virtual media.
$ VBoxManage createhd --filename asm1.vdi --size 5120 --format VDI --variant Fixed
$ VBoxManage createhd --filename asm2.vdi --size 5120 --format VDI --variant Fixed
$ VBoxManage createhd --filename asm3.vdi --size 5120 --format VDI --variant Fixed
$ VBoxManage createhd --filename asm4.vdi --size 5120 --format VDI --variant Fixed
$
$ # Connect them to the VM.
$ VBoxManage storageattach ol6-112-rac1 --storagectl "SATA Controller" --port 1 --device 0 --type hdd --medium asm1.vdi --mtype shareable
$ VBoxManage storageattach ol6-112-rac1 --storagectl "SATA Controller" --port 2 --device 0 --type hdd --medium asm2.vdi --mtype shareable
$ VBoxManage storageattach ol6-112-rac1 --storagectl "SATA Controller" --port 3 --device 0 --type hdd --medium asm3.vdi --mtype shareable
$ VBoxManage storageattach ol6-112-rac1 --storagectl "SATA Controller" --port 4 --device 0 --type hdd --medium asm4.vdi --mtype shareable
$
$ # Make shareable.
$ VBoxManage modifyhd asm1.vdi --type shareable
$ VBoxManage modifyhd asm2.vdi --type shareable
$ VBoxManage modifyhd asm3.vdi --type shareable
$ VBoxManage modifyhd asm4.vdi --type shareable

Start the "ol6-112-rac1" virtual machine by clicking the "Start" button on the toolbar. When the server has started, log in as the root user so you can configure the shared disks. The current disks can be seen by issuing the following commands.

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

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 with disk identifier 0x62be91cf.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
         switch off the mode (command 'c') and change display units to
         sectors (command 'u').

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-652, default 1): 
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-652, default 652): 
Using default value 652

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" 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
#

Configure your UDEV rules, as shown here.
The SCSI ID of my disks are displayed below.

# /sbin/scsi_id -g -u /dev/sdb1
1ATA_VBOX_HARDDISK_VBbfd37c1c-9b7c9336
# /sbin/scsi_id -g -u /dev/sdc1
1ATA_VBOX_HARDDISK_VB46bd30ca-ef5d5d6d
# /sbin/scsi_id -g -u /dev/sdd1
1ATA_VBOX_HARDDISK_VB5d431382-68a070ad
# /sbin/scsi_id -g -u /dev/sde1
1ATA_VBOX_HARDDISK_VB2ceafd7d-e56ad1d8
#

Using these, the "/etc/udev/rules.d/99-oracle-asmdevices.rules" file contained the following entries.

KERNEL=="sd?1", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u /dev/$name", RESULT=="1ATA_VBOX_HARDDISK_VBbfd37c1c-9b7c9336", NAME="asm-disk1", OWNER="oracle", GROUP="dba", MODE="0660"
KERNEL=="sd?1", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u /dev/$name", RESULT=="1ATA_VBOX_HARDDISK_VB46bd30ca-ef5d5d6d", NAME="asm-disk2", OWNER="oracle", GROUP="dba", MODE="0660"
KERNEL=="sd?1", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u /dev/$name", RESULT=="1ATA_VBOX_HARDDISK_VB5d431382-68a070ad", NAME="asm-disk3", OWNER="oracle", GROUP="dba", MODE="0660"
KERNEL=="sd?1", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u /dev/$name", RESULT=="1ATA_VBOX_HARDDISK_VB2ceafd7d-e56ad1d8", NAME="asm-disk4", OWNER="oracle", GROUP="dba", MODE="0660"

Load updated block device partition tables.

# /sbin/partprobe /dev/sdb1
# /sbin/partprobe /dev/sdc1
# /sbin/partprobe /dev/sdd1
# /sbin/partprobe /dev/sde1

Test the rules are working as expected.

# /sbin/udevadm test /block/sdb/sdb1

Reload the UDEV rules and start UDEV.

# /sbin/udevadm control --reload-rules
# /sbin/start_udev

The disks should now be visible and have the correct ownership using the following command. If they are not visible, your UDEV configuration is incorrect and must be fixed before you proceed.

# ls -al /dev/asm*
brw-rw---- 1 oracle dba 8, 17 Oct 12 14:39 /dev/asm-disk1
brw-rw---- 1 oracle dba 8, 33 Oct 12 14:38 /dev/asm-disk2
brw-rw---- 1 oracle dba 8, 49 Oct 12 14:39 /dev/asm-disk3
brw-rw---- 1 oracle dba 8, 65 Oct 12 14:39 /dev/asm-disk4
#

The shared disks are now configured for the grid infrastructure.

Clone the Virtual Machine

Later versions of VirtualBox allow you to clone VMs, but these also attempt to clone the shared disks, which is not what we want. Instead we must manually clone the VM.
Shut down the "ol6-112-rac1" virtual machine using the following command.

# shutdown -h now

Manually clone the "ol6-112-rac1.vdi" disk using the following commands on the host server.

```
mkdir -p /u03/VirtualBox/ol6-112-rac2
```

VBoxManage clonehd /u01/VirtualBox/ol6-112-rac1/ol6-112-rac1.vdi /u03/VirtualBox/ol6-112-rac2/ol6-112-rac2.vdi

Now create the hardisk in the same way as you did in "ol6-112-rac1", with the exception of using an existing rac2.vdi virtual hard drive.

Remember to add the second network adaptor as you did on the "ol6-112-rac1" VM. When the VM is created, attach the shared disks to this VM.

Next Blog I ll tell you the steps about Installing the Grid Infrastructure

Oracle Database 11g Release 2 (11.2.0.3.0) RAC On Oracle Linux 6.1 Using VirtualBox

2011-10-18T16:46:00.001+05:00

Introduction

One of the large-scale obstacles stopping persons from setting up check RAC environments is the obligation for distributed storage. In a output natural environment, distributed storage is often supplied by a SAN or high-end NAS apparatus, but both of these choices are very costly when all you desire to manage is get some know-how establishing and utilising RAC. A lower alternate is to use a FireWire computer disk enclosure to permit two appliances to get access to the identical disk(s), but that still charges cash and needs two servers. A third choice is to use virtualization to phony the distributed storage.
Using VirtualBox you can run multiple Virtual Machines (VMs) on a lone server, permitting you to run both RAC nodes on a lone machine. In additon, it permits you to set up distributed virtual computer disks, overwhelming the obstacle of costly distributed storage.
Before you launch into this setting up, here are a couple of things to consider.

The completed scheme encompasses the owner functioning scheme, two visitor functioning schemes, two groups of Oracle Grid Infrastructure (Clusterware + ASM) and two Database examples all on a lone server. As you can envisage, this needs a important allowance of computer disk space, CPU and memory. I accomplished this setting up on a Quad-Core processor with 8G of recollection, so don't anticipate to work on a reduced spec machine.
Following on from the last issue, the VMs will each require not less than 2G of RAM (3G for 11.2.0.3), preferably 3-4G if you don't desire the VMs to swap like crazy. As you can glimpse, 11gR2 RAC needs much more recollection than 11gR1 RAC. Don't suppose you will be adept to run this on a little PC or laptop. You won't.
This method presents a bare skeletal components setting up to get the RAC working. There is no redundancy in the Grid Infrastructure setting up or the ASM installation. To add this, easily conceive twice the allowance of distributed computer disks and choose the "Normal" redundancy choice when it is offered. Of course, this will take more computer disk space.
During the virtual computer disk creation, I habitually select not to preallocate the computer disk space. This makes virtual computer disk get access to slower throughout the setting up, but keeps on trashed computer disk space. The distributed computer disks should have their space preallocated.
This is not, and should not be advised, a production-ready system. It's easily to permit you to get utilised to establishing and utilising RAC.
The Single Client Access Name (SCAN) should actually be characterised in the DNS or GNS and round-robin between one of 3 locations, which are on the identical subnet as the public and virtual IPs. In this item I've characterised it as a lone IP address in the "/etc/hosts" document, which is incorrect and will origin the cluster verification to go incorrect, but it permits me to entire the establish without the occurrence of a DNS.
The virtual appliances can be restricted to 2Gig of swap, which determinants a prerequisite ascertain malfunction, but doesn't avert the setting up working. If you desire to bypass this, characterise 3+Gig of swap.
This article uses the 64-bit versions of Oracle Linux and Oracle 11g Release 2.
When doing this installation on my server, I split the virtual disks on to different physical disks ("/u02", "/u03", "/u04"). This is not necessary, but makes things run a bit faster.

VirtualBox Installation

First, install the VirtualBox software. On RHEL and its clones you do this with the following command as the root user.

# rpm -Uvh VirtualBox-4.1-4.1.2_73507_fedora15-1.x86_64

Once complete, VirtualBox is started from the "Applications > System Tools > Oracle VM VirtualBox" menu option.

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.
Start VirtualBox and click the "New" button on the toolbar. Click the "Next" button on the first page of the Virtual Machine Wizard.

Enter the name "ol6-112-rac1", OS "Linux" and Version "Oracle (64 bit)", then click the "Next" button.

Enter "4096" as the base memory size, then click the "Next" button.

Accept the default option to create a new virtual hard disk by clicking the "Next" button.

Click the "Next" button on the Create Virtual Disk Wizard welcome screen.

Acccept the default option by clicking the "Next" button.

Accept the default location and set the size to "30G" and click the "Next" button.

Click the "Create" button on the Virtual Machine Wizard Summary screen.

The "ol6-112-rac1" VM will appear on the left hand pane. Scroll down the "Details" tab on the right and click on the "Network" link.

Make sure "Adapter 1" is enabled, set to "Bridged Adapter", then click on the "Adapter 2" tab.

Make sure "Adapter 2" is enabled, set to "Bridged Adapter", then click on the "OK" button.

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

Now Place the linux DVD in the drive and press start button , this will lead you to the linux guest installation boot screen ..

Steps to Install this linux will be in my next blog named Installation Of Linux RAC.

Steps To Add New TimeLine In the Facebook

2011-10-18T13:27:00.001+05:00

FaceBook Timelines Steps:

open the link FaceBook TimeLine Or you can find facebook developers from search bar in your profile.

After the highlighted link open you have to clicp APP on the top centre and give the permission as facebook ask for some application. then it will lead you the below page.

Click Create New App

Give Display Name and application name Application name may get failed if someone has use it before so you have to chose a unique application name here and then press continue

You will see captcha image here you have to write both captcha with space in between.

Write both captcha and press submit .

You will redirected to new page as showing above you dont have to do any thing here jst scroll down

after scrolling down you will see the button save changes press it .

Then see on left panel you will see open graph there press it . it will open sub menu and the page you can see above. there is a tricky part you have to complete the sentence as i did Read a book. and press get started.

This new page open you just have to scroll it down you see the button as you can see in the next screen.

Yes here is the button click it .

Once again scroll it down and click the blue color button its all over you have done with timelines :)

now open your facebook you see timeline on the above click it and you will facebook new look on the left side there are timelines and the big picture is profile cover you can add or edit by mouse over on it :)

These were the step to get the timeline

Hope it will help you .

Auditing In Oracle Of Sys and Other Users

2011-10-17T11:41:00.002+05:00

SQL> SHOW PARAMETER AUDIT

NAME                 TYPE        VALUE
----------------------------------------------------
audit_file_dest      string      C:\ORACLE\PRODUCT\10.2.0\
                                 ADMIN\DB10G\ADUMP
audit_sys_operations boolean     FALSE
audit_trail          string      NONE
SQL>

Audit is disable by default, but can be enabled by audit_trail

static parameter which can have following possible values.

Audit_Trail = 'Following_Option'

```
None
```
```
OS
```
```
DB
```
```
DB, Extended
```
```
XML
```
```
XML, Extended
```

Description Of the Above Options:

None Or False

Auditing is disabled.

OS

Audit is enables with all records directed to the Operating

Systems.

DB or True

Audit is enables for all records stored in the database audit

trail ie.SYS.AUD$

DB, Extended

Same as DB , but two more columns will be populated by this

options which are SQL_BINDS and SQL_TEXT.

XML (New In 10gR2)

Audit is enable for all OS records and written in the file

format xml OS Files.

XML, Extended (New In 10gR2)

Same as XML , but SQL_BIND and SQL_Text Column Values will

also be shown in the file format XML OS files.

Now Start Auditing follow the steps below:

SQL> conn sys/password@connection_string AS SYSDBA

SQL> ALTER SYSTEM SET audit_trail=db SCOPE=SPFILE;

System altered.

SQL> SHUTDOWN
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP
ORACLE instance started.

Total System Global Area  289406976 bytes
Fixed Size                  1248600 bytes
Variable Size              71303848 bytes
Database Buffers          213909504 bytes
Redo Buffers                2945024 bytes
Database mounted.
Database opened.

SQL>

First we create a simple user name audit_test to verify

the auditing with different options.

CONNECT sys/password AS SYSDBA

CREATE USER audit_test IDENTIFIED BY password
  DEFAULT TABLESPACE users_test
  TEMPORARY TABLESPACE temp_text
  QUOTA UNLIMITED ON users_test;

GRANT connect TO audit_test;
GRANT create table, create procedure TO audit_test;

USER CREATED AND GRANTED.

Our next step is to start auditing for the created user

AUDIT_TEST.

```
AUDIT ALL BY audit_test BY ACCESS;
```

AUDIT SELECT TABLE, UPDATE TABLE, INSERT TABLE,

DELETE TABLE BY audit_test BY ACCESS;

AUDIT EXECUTE PROCEDURE BY audit_test BY ACCESS;

Now we performs some actions which can be use to test

our auditing is working fine or not.

CONN audit_test/password

CREATE TABLE test_audit (
  test_id  NUMBER
);

INSERT INTO test_audit (test_id) VALUES (1);
UPDATE test_audit SET test_id = test_id;
SELECT * FROM test_audit;
DELETE FROM test_audit;
DROP TABLE test_audit;

Now Time to check out audit tables.

There are some audit views which are populated when

auditing is set to be true.

SELECT view_name
FROM   dba_views
WHERE  view_name LIKE 'DBA%AUDIT%'
ORDER BY view_name;

VIEW_NAME
------------------------------
DBA_AUDIT_EXISTS
DBA_AUDIT_OBJECT
DBA_AUDIT_POLICIES
DBA_AUDIT_POLICY_COLUMNS
DBA_AUDIT_SESSION
DBA_AUDIT_STATEMENT
DBA_AUDIT_TRAIL
DBA_COMMON_AUDIT_TRAIL
DBA_FGA_AUDIT_TRAIL
DBA_OBJ_AUDIT_OPTS
DBA_PRIV_AUDIT_OPTS
DBA_REPAUDIT_ATTRIBUTE
DBA_REPAUDIT_COLUMN
DBA_STMT_AUDIT_OPTS

14 rows selected.

COLUMN username FORMAT A10
COLUMN owner    FORMAT A10
COLUMN obj_name FORMAT A10
COLUMN extended_timestamp FORMAT A20

SELECT username,
       extended_timestamp,
       action_name
FROM   dba_audit_trail
WHERE  owner = 'AUDIT_TEST'
ORDER BY timestamp;

USERNAME   EXTENDED_TIMESTAMP                 ACTION_NAME
---------- -------------------------------------------------
AUDIT_TEST 17-OCT-2011 14:16:55.435000 +00:00 CREATE TABLE
AUDIT_TEST 17-OCT-2011 14:16:55.514000 +00:00 INSERT
AUDIT_TEST 17-OCT-2011 14:16:55.545000 +00:00 UPDATE
AUDIT_TEST 17-OCT-2011 14:16:55.592000 +00:00 SELECT
AUDIT_TEST 17-OCT-2011 14:16:55.670000 +00:00 DELETE
AUDIT_TEST 17-OCT-2011 14:17:00.045000 +00:00 DROP TABLE

6 rows selected.

SQL>

Or auditing can be set on in Init.ora file by adding

the following parameters.

audit_sys_operation <------ It will start auditing

for sys user.

audit_file_dest='Location\xml_audit'

audit_trail='XML','EXTENDED'

and then you can create a batch file of the following

query to get the logs of user sys on daily basis.

set linesize 500
set pagesize 200
column db_user format a10
column os_user format a24
column os_host format a28
column extended_timestamp format a34
column sql_text format a300

column tm new_value file_time noprint

select to_char(sysdate, 'fmDD-MON-YYYY') tm from dual;

prompt&file_time

spool location\audit_log_sys__&file_time.log(desired Location)

select db_user, os_user, os_host, TO_CHAR(EXTENDED_TIMESTAMP,

'fmDd-MM-YYYY HH:MI:SS AM'), sql_text
from v$xml_audit_trail
where db_user in ('sys', 'SYS', '/')
and to_char(extended_timestamp, 'fmDd-MM-YYYY')

= to_char(SYSDATE, 'fmDd-MM-YYYY')
order by 4;

spool off;

EXIT;

just copy the above code and paste in the notepad file and

create a batch file in schedule task. it will populate the

spool file.

Modifications can be done by the following command.Or you

can just start auditing for the specific table by the

following command.

AUDIT INSERT, UPDATE, DELETE ON sys.aud$ BY ACCESS;

The OS and XML audit trail are managed through OS, These files should be
secure at the OS level and correct permission should be given to the users by
System administrator.
It is hardly recommended that the above procedure should be done
by only Oracle database administrator.

Hope This will Help.

Oracle Installation Guide Step by Step

2011-10-14T17:17:00.000+05:00


Installation Process

It is same for Oracle 10g and 11g , but you must have your system eligible for 11g .

A Welcome window will appear: when you start the Oracle Universal Installer :

§ It is assumed that this is a fresh install so no other Oracle products should be installed at this time.

§ The "Installation Types" screen will appear next. For this installation, we chose the Enterprise Edition.

§ The next step is to identify the Product specific prerequisite checks

§ Select Configuration Option

§ Select from creating full database, configuring ASM or installing software only.

§ For our database we create the database.

§ Select the database configuration

§ For our purpose we use ‘General Purpose ‘

§ Specify a name for the database e.g. orcl

§ Character set is the default one

§ Uncheck ‘Create database with sample schemas’

§ Select the management option for the database. It could be either Grid Control for centralized management or Database Control for locally managing the database.

§ For our purpose we will specify Database Control

§ Specify the storage option

§ For our purpose we use ‘File System ‘

§ Specify the backup and recovery options for the database

§ The Automated Backup option allows one to schedule the backups and let oracle manage them on it’s own.

§ We will not use this option and select ‘Do not enable Automated backups’

§ Specify the passwords SEPERATELY for each schema.

§ The Summary screen shows you all the options that you have selected for a final review..

§ The installer will now run showing you the progress and steps that are being configured during installation.

§ At the end of installation it will show u a message about config files.

§ Press ‘Exit’ to leave the installer.

IBM Calls Out Oracle On Server And Systems Claims

2011-10-12T17:11:00.004+05:00

Oracle's evaluations of its T4 Servers and SuperCluster wares to IBM Power 7 yield are off foundation, and its allegations about hardware and programs toiling concurrently are confusing because programs isn't truly embraced in so-called engineered systems. That's the gist of a apex IBM executive's response to Oracle smashes over the last two week.

IBM seldom observations on competent allegations, but Bernard Spang, chief director of approach and selling for database programs and procedures, advised InformationWeek Oracle's evaluations with IBM Power 7 procedures "don't line up" with reality.

IBM Calls Out Oracle On Server And Systems Claims

2011-10-12T17:11:00.003+05:00

Data Guard/Broker Configuration Oracle 10g

2011-10-07T20:43:00.005+05:00

PRIMARY SITE: (Information)

Machine IP: 192.168.1.10
Database name (db_name): ORCL
Database Unique Name (db_unique_name): primary
TNS Service Name: to_standby (Through this service, the primary machine will be connected to STANDBY machine)

STANDBY SITE: (Information)

Machine IP: 192.168.1.20
Database name (db_name): ORCL
Database Unique Name (db_unique_name): standby
TNS Service Name: to_primary (Through this service, the standby machine will be connected to PRIMARY machine)

CONFIGURATION ON PRIMARY

Create pfile from spfile on the primary database:

SQL> Create pfile=’C:\oracle\product\10.2.0\db_1\dbs\spfilePrimary.ora’ from spfile;

initPrimary.ora file setting on the PRIMARY Machine.

db_unique_name=’PRIMARY’

FAL_Client=’to_primary’

FAL_Server=’to_standby’

Log_archive_config=’DG_CONFIG=(primary,standby)’

Log_archive_dest_1=’Location=c:\oracle\backup

VALID_FOR=(ALL_LOGFILES,ALL_ROLES)

db_unique_name=primary’

Log_archive_dest_2=’Service=to_standby lgwr async

VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)

db_unique_name=standby’

Log_archive_dest_state_1=ENABLE

Log_archive_dest_state_2=DEFER

Service_names=’primary’

Standby_File_Management=’AUTO’

Create password file using ‘cmd’.

C:\> orapwd file=C:\oracle\product\10.2.0\db_1\database\PWDOrcl.ora password=oracle entries=5 [force=y].

Force option is used to replace an existing password file. Now startup the PRIMARY database to MOUNT stage.

• SQL> startup mount;

Make the following changes: Take the database to Archive Mode.

• SQL> Alter database ArchiveLog;

§ Enable Force Logging.

• SQL> Alter database Force Logging;

On the PRIMARY site, create standby log file for data guard and data broker setting

• SQL>Alter database add standby logfile

(‘C:\oracle\product\10.2.0\oradata\ORCL\StandbyRedo.log’) size 150m;

Now shutdown the primary database.

• SQL> shutdown immediate;

Copy all the Datafiles and standby redo logfile from PRIMARY site to the same location on the STANDBY site. Then again startup the PRIMARY database to mount stage.

• SQL> startup mount;

Now create a standby controlfile on the PRIMARY site.

• SQL> Alter database create standby controlfile as ‘c:\oracle\backup\standcontrol.ctl’;

Now copy the created standby control file to the standby datafile location.

Create spFile from pfile.

• SQL> Create spfile from pfile;

Restart the primary database.

on PRIMARY machine create an entry in TNSnames.ora file through which the PRIMARY site will be connected to the Standby.

TO_STANDBY =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.20)(PORT = 1521))

)

(CONNECT_DATA =

(SERVICE_NAME = standby)

)

Also check the connectivity from the SQL Prompt.

• SQL> connect sys/oracle@to_standby as sysdba

Connected.

> Lsnrctl stop

> Lsnrctl start

Query the DATABASE_ROLE column from V$DATABASE to view the role of primary database. It should return ‘PRIMARY’.

CONFIGURATION ON STANDBY

Check the mode of Archiving by following command:

• SQL> Archive Log List

Then create pfile from spfile on the standby database:

SQL> Create pfile from spfile=’C:\oracle\product\10.2.0\db_1\dbs\spfileStandby.ora’;

initStandby.ora file on the STANDBY Machine.

db_unique_name=’STANDBY’

FAL_Client=’to_standby’

FAL_Server=’to_primary’

Log_archive_config=’DG_CONFIG=(primary,standby)’

Log_archive_dest_1=’Location=c:\oracle\backup

VALID_FOR=(ALL_LOGFILES,ALL_ROLES)

db_unique_name=standby’

Log_archive_dest_2=’Service=to_primary

VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)

db_unique_name=primary’

Log_archive_dest_state_1=ENABLE

Log_archive_dest_state_2=ENABLE

Service_names=’STANDBY’

Standby_File_Management=’AUTO’

db_file_name_convert='/home/sanath/primary/','/home/sanath/standby/'

log_file_name_convert='/home/sanath/primary/','/home/sanath/standby/'

lock_name_space=standby

Create password file using ‘cmd’.

C:\> orapwd file=C:\oracle\product\10.2.0\db_1\database\PWDOrcl.ora password=oracle entries=5 [force=y].

Force option is used to replace an existing password file.

Now on STANDBY site create an entry in TNSnames.ora file through which the STANDBY machine will be connected to the PRIMARY machine.

TO_PRIMARY =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.10)(PORT = 1521))

)

(CONNECT_DATA =

(SERVICE_NAME = primary)

)

Check the connectivity from the SQL Prompt.

• SQL> connect sys/oracle@to_primary as sysdba

Connected.

> Lsnrctl stop

> Lsnrctl start

Create spfile from pfile.

• SQL> Create spfile from pfile;

Restart the database. Now startup the STANDBY database to mount stage.

• SQL> startup mount

Enable Force Logging.

• SQL> Alter database Force Logging;

Query the column DATABASE_ROLE from V$DATABASE to view the role of standby database. It should return ‘PHYSICAL STANDBY’.

LOG SHIPPING

On PRIMARY site enable Log_archive_dest_state_2 to start shipping archived redo logs.

• SQL> Alter system set Log_archive_dest_state_2=ENABLE scope=both;

System Altered.

Check the sequence # and the archiving mode by executing following command.

• SQL> Archive Log List

Then switch the logfile.

• SQL> Alter system switch logfile;

System Altered.

Now on the PRIMARY site check the status of Standby Archiving destination.

• SQL> Select Status, Error

from v$Archive_dest

where dest_id=2;

The STATUS should return – VALID. If it returns Error, then check the connectivity between the Primary and Standby machines.

START PHYSICAL LOG APPLY SERVICE.

On the STANDBY database execute the following command to start Managed Recovery Process (MRP). This command is executed on Mount stage.

• SQL> Alter Database Recover Managed Standby Database;

Database Altered.

By executing the above command your session will be taken by oracle and become in hang state . To avoid this hanging, you can execute the following command with DISCONNECT option.

• SQL> Alter Database Recover Managed Standby Database Disconnect;

Database Altered.

Now the session will be available to you and MRP (media recovery process )will work as a background process and apply the redo logs.

You can check whether the log is applied or not by querying V$ARCHIVED_LOG.

• SQL> Select Name, Applied, Archived

from v$Archived_log;

This query will return the name of archived files and their status of being archived and applied.

Manual Switchover:

On the PRIMARY Database: (Open stage)

Query V$DATABASE to check the role of Primary Database.

• SQL> Select Database_role

from v$Database;

It will return “PRIMARY”,

Now check the Switchover Status of the Primary Database.

• SQL> Select switchover_status

from v$Database;

It will return “SESSIONS ACTIVE”.

Now you are ready to perform a manual switchover. Execute the following command using “WITH SESSION SHUTDOWN” option.

• SQL> Alter Database Commit to Switchover to Physical Standby with session Shutdown;

Database Altered.

Now your PRIMARY Database has become Physical Standby. Before To verify this change, You must Shutdown the database and again Start it to mount stage. Again query the Database_role column of V$DATABASE. Now it will return “PHYSICAL STANDBY”.

On the PHYSICAL STANDBY Database: (Mount stage) Query V$DATABASE to check the role of Standby Database.

• SQL> Select Database_role

from v$Database;

It will return “PHYSICAL STANDBY”,

Now check the Switchover Status of the Standby Database.

• SQL> Select switchover_status

from v$Database;

It will return “NOT ALLOWED”

Now check the Switchover Status of the Standby Database.

• SQL> Alter database commit to switch over to primary;

It will change the role of standby then shutdown immediate the standby and start it again as you start your primary and start the log apply services as mentioned above.

Revert back the standby database to Primary and vice versa

Now cancel the MRP which is running in the background of the Standby Database. Execute the following command:

• SQL> Alter database Recover Managed Standby Database Cancel;

Database Altered.

Now you are ready to perform a manual switchover from Physical Standby to Primary. Execute the following command using “WITH SESSION SHUTDOWN” option.

• SQL> Alter Database Commit to Switchover to PRIMARY with session Shutdown;

Database Altered.

Now your PHYSICAL STANDBY Database has become PRIMARY. To verify this change, again query the Database_role column of V$DATABASE. Now it will return “PRIMARY”.

Shutdown the database and again Start it to Open stage.

DATAGUARD BROKER :

• Creating and enabling Data Guard configurations, including setting up log transport services and log apply services.

• Managing an entire Data Guard configuration from any system in the configuration.

• Managing and monitoring Data Guard configurations that contain Real Application Clusters primary or standby databases.

BROKER CONFIGURATION:

On both Primary and Standby sites, change the initialization parameter in the spfile to enable the Data guard broker.

•SQL> Alter system set dg_broker_start=True scope=both;

System Altered.

On the PRIMARY site, open the ‘cmd’ and start Command Line Interface (CLI) of the Dataguard Broker (DGMGRL).

C:\> dgmgrl

DGMGRL for 32-bit Windows: Version 10.2.0.1.0 - Production

Welcome to DGMGRL, type "help" for information.

DGMGRL>_

Now connect to the database through the service you made previously.

DGMGRL> connect sys/oracle@to_primary

Connected.

Create broker configuration.

DGMGRL> create configuration ‘broker1’ as

> primary database is ‘primary’

> connect identifier is to_primary;

(‘to_primary’ in Connect identifier is the service name through which the broker is connected to the PRIMARY database)

Add Standby Database to the above configuration.

DGMGRL> Add database ‘standby’ as

> connect identifier is to_standby

> maintained as physical;

(‘to_standby’ in Connect identifier is the service name through which the broker is connected to the STANDBY database)

Now the configuration has been set up but it is still disabled. You can view the configuration by executing:

DGMGRL> show configuration

Configuration

Name: broker1

Enabled: NO

Protection Mode: MaxPerformance

Fast-Start Failover: DISABLE

Databases:

primary - Physical standby database

standby - Primary database

Current status for "broker1":

DISABLE

The next step is to ENABLE the configuration ‘broker1’.

DGMGRL> enable configuration;

Enabled

Again view the configuration.

DGMGRL> show configuration

Configuration

Name: broker1

Enabled: YES

Protection Mode: MaxPerformance

Fast-Start Failover: DISABLE

Databases:

primary - Physical standby database

standby - Primary database

Current status for "broker1":

SUCCESS

Now we are ready to switch over the PRIMARY database Role to STANDBY database Role.

DGMGRL> switchover to ‘Standby’;

…..

Primary Database Successfully converted to Physical Standby. You can again switch over the Standby Database to Primary by executing following command.

DGMGRL> switchover to ‘Primary’;

…..

Standby Database is successfully converted to Primary Database.

Failover:

Failover can be done through the same configuration without any alteration. You simply need to execute following command:

DGMGRL> failover to ‘Standby’;

….

Failover to standby succeeded.

And also…

DGMGRL> failover to ‘Primary’;

….

Failover to primary succeeded.

with the same configuration and pc names and IP you can perfectly implement data guard / broker to your oracle database.

This post confirms my ownership of the site and that this site adheres to Google AdSense program policies and Terms and Conditions: ca-pub-6093313765784300

Data Guard/Broker Configuration Oracle 10g

2011-10-07T20:43:00.004+05:00

PRIMARY SITE: (Information)

Machine IP: 192.168.1.10
Database name (db_name): ORCL
Database Unique Name (db_unique_name): primary
TNS Service Name: to_standby (Through this service, the primary machine will be connected to STANDBY machine)

STANDBY SITE: (Information)

Machine IP: 192.168.1.20
Database name (db_name): ORCL
Database Unique Name (db_unique_name): standby
TNS Service Name: to_primary (Through this service, the standby machine will be connected to PRIMARY machine)

CONFIGURATION ON PRIMARY

Create pfile from spfile on the primary database:

SQL> Create pfile=’C:\oracle\product\10.2.0\db_1\dbs\spfilePrimary.ora’ from spfile;

initPrimary.ora file setting on the PRIMARY Machine.

db_unique_name=’PRIMARY’

FAL_Client=’to_primary’

FAL_Server=’to_standby’

Log_archive_config=’DG_CONFIG=(primary,standby)’

Log_archive_dest_1=’Location=c:\oracle\backup

VALID_FOR=(ALL_LOGFILES,ALL_ROLES)

db_unique_name=primary’

Log_archive_dest_2=’Service=to_standby lgwr async

VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)

db_unique_name=standby’

Log_archive_dest_state_1=ENABLE

Log_archive_dest_state_2=DEFER

Service_names=’primary’

Standby_File_Management=’AUTO’

Create password file using ‘cmd’.

C:\> orapwd file=C:\oracle\product\10.2.0\db_1\database\PWDOrcl.ora password=oracle entries=5 [force=y].

Force option is used to replace an existing password file. Now startup the PRIMARY database to MOUNT stage.

• SQL> startup mount;

Make the following changes: Take the database to Archive Mode.

• SQL> Alter database ArchiveLog;

§ Enable Force Logging.

• SQL> Alter database Force Logging;

On the PRIMARY site, create standby log file for data guard and data broker setting

• SQL>Alter database add standby logfile

(‘C:\oracle\product\10.2.0\oradata\ORCL\StandbyRedo.log’) size 150m;

Now shutdown the primary database.

• SQL> shutdown immediate;

Copy all the Datafiles and standby redo logfile from PRIMARY site to the same location on the STANDBY site. Then again startup the PRIMARY database to mount stage.

• SQL> startup mount;

Now create a standby controlfile on the PRIMARY site.

• SQL> Alter database create standby controlfile as ‘c:\oracle\backup\standcontrol.ctl’;

Now copy the created standby control file to the standby datafile location.

Create spFile from pfile.

• SQL> Create spfile from pfile;

Restart the primary database.

on PRIMARY machine create an entry in TNSnames.ora file through which the PRIMARY site will be connected to the Standby.

TO_STANDBY =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.20)(PORT = 1521))

)

(CONNECT_DATA =

(SERVICE_NAME = standby)

)

Also check the connectivity from the SQL Prompt.

• SQL> connect sys/oracle@to_standby as sysdba

Connected.

> Lsnrctl stop

> Lsnrctl start

Query the DATABASE_ROLE column from V$DATABASE to view the role of primary database. It should return ‘PRIMARY’.

CONFIGURATION ON STANDBY

Check the mode of Archiving by following command:

• SQL> Archive Log List

Then create pfile from spfile on the standby database:

SQL> Create pfile from spfile=’C:\oracle\product\10.2.0\db_1\dbs\spfileStandby.ora’;

initStandby.ora file on the STANDBY Machine.

db_unique_name=’STANDBY’

FAL_Client=’to_standby’

FAL_Server=’to_primary’

Log_archive_config=’DG_CONFIG=(primary,standby)’

Log_archive_dest_1=’Location=c:\oracle\backup

VALID_FOR=(ALL_LOGFILES,ALL_ROLES)

db_unique_name=standby’

Log_archive_dest_2=’Service=to_primary

VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)

db_unique_name=primary’

Log_archive_dest_state_1=ENABLE

Log_archive_dest_state_2=ENABLE

Service_names=’STANDBY’

Standby_File_Management=’AUTO’

db_file_name_convert='/home/sanath/primary/','/home/sanath/standby/'

log_file_name_convert='/home/sanath/primary/','/home/sanath/standby/'

lock_name_space=standby

Create password file using ‘cmd’.

C:\> orapwd file=C:\oracle\product\10.2.0\db_1\database\PWDOrcl.ora password=oracle entries=5 [force=y].

Force option is used to replace an existing password file.

Now on STANDBY site create an entry in TNSnames.ora file through which the STANDBY machine will be connected to the PRIMARY machine.

TO_PRIMARY =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.10)(PORT = 1521))

)

(CONNECT_DATA =

(SERVICE_NAME = primary)

)

Check the connectivity from the SQL Prompt.

• SQL> connect sys/oracle@to_primary as sysdba

Connected.

> Lsnrctl stop

> Lsnrctl start

Create spfile from pfile.

• SQL> Create spfile from pfile;

Restart the database. Now startup the STANDBY database to mount stage.

• SQL> startup mount

Enable Force Logging.

• SQL> Alter database Force Logging;

Query the column DATABASE_ROLE from V$DATABASE to view the role of standby database. It should return ‘PHYSICAL STANDBY’.

LOG SHIPPING

On PRIMARY site enable Log_archive_dest_state_2 to start shipping archived redo logs.

• SQL> Alter system set Log_archive_dest_state_2=ENABLE scope=both;

System Altered.

Check the sequence # and the archiving mode by executing following command.

• SQL> Archive Log List

Then switch the logfile.

• SQL> Alter system switch logfile;

System Altered.

Now on the PRIMARY site check the status of Standby Archiving destination.

• SQL> Select Status, Error

from v$Archive_dest

where dest_id=2;

The STATUS should return – VALID. If it returns Error, then check the connectivity between the Primary and Standby machines.

START PHYSICAL LOG APPLY SERVICE.

On the STANDBY database execute the following command to start Managed Recovery Process (MRP). This command is executed on Mount stage.

• SQL> Alter Database Recover Managed Standby Database;

Database Altered.

By executing the above command your session will be taken by oracle and become in hang state . To avoid this hanging, you can execute the following command with DISCONNECT option.

• SQL> Alter Database Recover Managed Standby Database Disconnect;

Database Altered.

Now the session will be available to you and MRP (media recovery process )will work as a background process and apply the redo logs.

You can check whether the log is applied or not by querying V$ARCHIVED_LOG.

• SQL> Select Name, Applied, Archived

from v$Archived_log;

This query will return the name of archived files and their status of being archived and applied.

Manual Switchover:

On the PRIMARY Database: (Open stage)

Query V$DATABASE to check the role of Primary Database.

• SQL> Select Database_role

from v$Database;

It will return “PRIMARY”,

Now check the Switchover Status of the Primary Database.

• SQL> Select switchover_status

from v$Database;

It will return “SESSIONS ACTIVE”.

Now you are ready to perform a manual switchover. Execute the following command using “WITH SESSION SHUTDOWN” option.

• SQL> Alter Database Commit to Switchover to Physical Standby with session Shutdown;

Database Altered.

On the PHYSICAL STANDBY Database: (Mount stage) Query V$DATABASE to check the role of Standby Database.

• SQL> Select Database_role

from v$Database;

It will return “PHYSICAL STANDBY”,

Now check the Switchover Status of the Standby Database.

• SQL> Select switchover_status

from v$Database;

It will return “NOT ALLOWED”

Now check the Switchover Status of the Standby Database.

• SQL> Alter database commit to switch over to primary;

It will change the role of standby then shutdown immediate the standby and start it again as you start your primary and start the log apply services as mentioned above.

Revert back the standby database to Primary and vice versa

Now cancel the MRP which is running in the background of the Standby Database. Execute the following command:

• SQL> Alter database Recover Managed Standby Database Cancel;

Database Altered.

Now you are ready to perform a manual switchover from Physical Standby to Primary. Execute the following command using “WITH SESSION SHUTDOWN” option.

• SQL> Alter Database Commit to Switchover to PRIMARY with session Shutdown;

Database Altered.

Now your PHYSICAL STANDBY Database has become PRIMARY. To verify this change, again query the Database_role column of V$DATABASE. Now it will return “PRIMARY”.

Shutdown the database and again Start it to Open stage.

DATAGUARD BROKER :

• Creating and enabling Data Guard configurations, including setting up log transport services and log apply services.

• Managing an entire Data Guard configuration from any system in the configuration.

• Managing and monitoring Data Guard configurations that contain Real Application Clusters primary or standby databases.

BROKER CONFIGURATION:

On both Primary and Standby sites, change the initialization parameter in the spfile to enable the Data guard broker.

•SQL> Alter system set dg_broker_start=True scope=both;

System Altered.

On the PRIMARY site, open the ‘cmd’ and start Command Line Interface (CLI) of the Dataguard Broker (DGMGRL).

C:\> dgmgrl

DGMGRL for 32-bit Windows: Version 10.2.0.1.0 - Production

Welcome to DGMGRL, type "help" for information.

DGMGRL>_

Now connect to the database through the service you made previously.

DGMGRL> connect sys/oracle@to_primary

Connected.

Create broker configuration.

DGMGRL> create configuration ‘broker1’ as

> primary database is ‘primary’

> connect identifier is to_primary;

(‘to_primary’ in Connect identifier is the service name through which the broker is connected to the PRIMARY database)

Add Standby Database to the above configuration.

DGMGRL> Add database ‘standby’ as

> connect identifier is to_standby

> maintained as physical;

(‘to_standby’ in Connect identifier is the service name through which the broker is connected to the STANDBY database)

Now the configuration has been set up but it is still disabled. You can view the configuration by executing:

DGMGRL> show configuration

Configuration

Name: broker1

Enabled: NO

Protection Mode: MaxPerformance

Fast-Start Failover: DISABLE

Databases:

primary - Physical standby database

standby - Primary database

Current status for "broker1":

DISABLE

The next step is to ENABLE the configuration ‘broker1’.

DGMGRL> enable configuration;

Enabled

Again view the configuration.

DGMGRL> show configuration

Configuration

Name: broker1

Enabled: YES

Protection Mode: MaxPerformance

Fast-Start Failover: DISABLE

Databases:

primary - Physical standby database

standby - Primary database

Current status for "broker1":

SUCCESS

Now we are ready to switch over the PRIMARY database Role to STANDBY database Role.

DGMGRL> switchover to ‘Standby’;

…..

Primary Database Successfully converted to Physical Standby. You can again switch over the Standby Database to Primary by executing following command.

DGMGRL> switchover to ‘Primary’;

…..

Standby Database is successfully converted to Primary Database.

Failover:

Failover can be done through the same configuration without any alteration. You simply need to execute following command:

DGMGRL> failover to ‘Standby’;

….

Failover to standby succeeded.

And also…

DGMGRL> failover to ‘Primary’;

….

Failover to primary succeeded.

with the same configuration and pc names and IP you can perfectly implement data guard / broker to your oracle database.