Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Oracle Enterprise Manager Cloud Control 12c: Managing Data Center Chaos

You're reading from  Oracle Enterprise Manager Cloud Control 12c: Managing Data Center Chaos

Product type Book
Published in Dec 2012
Publisher Packt
ISBN-13 9781849684781
Pages 394 pages
Edition 1st Edition
Languages
Author (1):
PORUS HOMI HAVEWALA PORUS HOMI HAVEWALA
Profile icon PORUS HOMI HAVEWALA

Table of Contents (19) Chapters

Oracle Enterprise Manager Cloud Control 12: Managing Data Center Chaos
Credits
About the Author
Acknowledgements
About the Reviewers
www.PacktPub.com
Preface
1. Chaos at Data Centers 2. Enter Oracle Cloud Control 3. Ease the Chaos with Performance Management 4. Ease the Chaos with Configuration Management and Security Compliance 5. Ease the Chaos with Automated Provisioning 6. Ease the Chaos with Automated Patching 7. Ease the Chaos with Change Management 8. Ease the Chaos with Test Data Management 9. Ease the Chaos with Data Masking 10. Ease the Chaos with Exadata Management 11. Real-life Examples and Case Studies, and It's a Wrap: The Future is the Cloud Index

The Grid – where the cloud came from


In 2003, Oracle Database 10g was released—where the "g" stood for Grid.

Oracle had previously released Real Application Clusters (RAC) in Oracle 9i, which was the first active/active database system (multiple nodes and instances accessing the same database).

This technology made it possible to cluster large numbers of smaller servers and place the application's database on the cluster as a whole. So, instead of placing the database on a larger and dedicated expensive server that had been sized suitably to accommodate the changes for the next two years of application life, it could be placed on a cluster of smaller servers, sized appropriately.

As the application's demand increased, it would be easy to just add an extra node to the database cluster and expand horizontally instead of vertically. The database services (applications) could also share any of the nodes in the cluster instead of having a dedicated server installed for each application. This intention...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}