Friday, July 29, 2011

Publisher says Outstanding Orders to be filled soon

Friends,

I have heard back from the publisher today. They have printed enough copies to fill the demand. All outstanding orders should be filled within the next two weeks. The demand was higher than expected and caught them off guard. That is actually good news that the book is selling better than expected. Moving forward there will be sufficient copies available to satisfy everyone.

Thanks for the great support from all my readers.

You can place an order for the book by clicking on the title below. An out of stock warning may appear right now, but you can safely ignore that. A description of the book is as follows.

Oracle Enterprise Manager Grid Control: Advanced OEM Techniques for the Real World

Oracle’s Enterprise Manager Grid Control is recognized as the IT Industry’s leading Oracle stack (application to disk) administration and management tool. It is unrivalled in its ability to monitor, manage, maintain and report on entire enterprise grids that comprise hundreds (if not thousands) of Oracle databases, middle-ware and servers following an approach that is consistent and repeatable, as well as the Oracle Applications such as Oracle E-Business Suite, PeopleSoft, Siebel, and so on.

However, Enterprise Manager Grid Control may seem daunting even to the most advanced Oracle Administrator. The problem is you know about the power of Enterprise Manager but how do you unleash that power amongst what initially appears to be a maze of GUI-based screens that feature a myriad of links to reports and management tasks that in turn lead you to even more reports and management tasks?

This book shows you how to unleash that power.

Based on the Author’s considerable and practical Oracle database and Enterprise Manager Grid Control experience you will learn through illustrated examples how to create and schedule RMAN backups, generate Data Guard Standbys, clone databases and Oracle Homes and patch databases across hundreds and thousands of databases. You will learn how you can unlock the power of the Enterprise Manager Grid Control Packs, PlugIns and Connectors to simplify your database administration across your company’s database network, as also the management and monitoring of important Service Level Agreements (SLAs), and the nuances of all important real-time change control using Enterprise Manager.

There are other books on the market that describe how to install and configure Enterprise Manager but until now they haven’t explained using a simple and illustrated approach how to get the most out of your Enterprise Manager. This book does just that.

Regards,

Porus.

Thursday, July 21, 2011

Using Enterprise Manager Database Control for a RAC cluster

A friend wrote:
We are using 11GR2 RAC with 5 nodes on Redhat Linux;

We have configured the DB coonsole (not grid control) to run in Node 1 as repository and active node and the agents to run in nodes 2, node 3, node 4 and node 5.

We have used this command to configure that;

emca -config dbcontrol db -repos create -cluster -EM_NODE db01 -EM_NODE_LIST db02,db03,db04,db05

Now, in order to be prepared in the case of failure of our node 1, I have to prepare the procedure in order to maybe move the repository (the same node 1 repository) to run in node 2 actively and the agents to run in node 3, node 4 and node 5.

I would like to keep the node 1 repository but moving it to node 2, and run node 2 as the active node, in case of failure just to guarantee the HA.


Please let me know if it's clear now. I wonder if you could give a help and help guide me in order to have the procedure prepared,
My reply to him:

Oracle really recommends using a separate installation of Enterprise Manager Grid Control for RAC databases, and then putting agents on all RAC nodes. That way you are covered for any node failure, Enterprise Manager will keep on working.

For what you want, ie. using EM Database control and then failing over Database Control from 1 RAC node to the other, it is not recommnended but it is possible, please use these commands:

Drop the DB Control on all RAC nodes, but keeping the repository. Run this command on the first node: (in the second iteration, try it on a different node)

$ emca -deconfig dbcontrol db -cluster
Enter the following information:
- Database unique name

This emca command does the following:
- stop the DB Control (dbconsole, agent) on all nodes of the cluster
- remove all DB Control related directories on all nodes of the cluster

The repository is in the RAC database and has not been dropped. You can then recreate the DBControl without recreating the repository. Do this by:

emca -reconfig dbcontrol -cluster -EM_NODE db02 -EM_NODE_LIST db01,db03,db04,db05

Test out the above and let me know if ok.

For added info please see the My Oracle Support (MOS) note "How to manage DB Control 11.x for RAC Database with emca" [ID 578011.1]

Regards,

Porus.

Disclaimer

Opinions expressed in this blog are entirely the opinions of the writers of this blog, and do not reflect the position of Oracle corporation. No responsiblity will be taken for any resulting effects if any of the instructions or notes in the blog are followed. It is at the reader's own risk and liability.

Blog Archive