Grid Control 10g Release 5 is out since Wednesday morning, a lot of people were eagerly awaiting this release. I attended the Global launch Webcast on Tues., March 3, 9am PT which was 1 AM Singapore time. Richard Sarwal, Oracle SVP of Product Development, conducted the talk and slideshow. Towards the end of the demo, it was mentioned that Release 5 was now available for download from OTN. Both Windows and Linux versions are available. I downloaded it overnight and will install it soon. Files more than 2 GB for full download.
Main plus points of Release 5, from what I could gather, are:
1. Most stable release of Grid Control 10g and with the best performance
2. Manages Oracle VM for the first time
3. Manages Oracle Weblogic Server, apps and Service Bus
4. Real User Experience Insight (RUEI) with E-Biz, Peoplesoft and Siebel Accelerators
5. Oracle Communications Billing and Revenue Management
6. Oracle Beehive Management
7. Oracle Coherence Management
8. Supports ADDM for RAC for the first time
9. Real Time SQL monitoring, Automatic Sql tuning
10. Now supports 11g's new advisors such as Partition Advisor, Data Recovery Advisor
11. Now supports Database Vault
12. Secure Cloning and Masking = Automate masking of sensitive production data while cloning. Masking has been enhanced with deterministic masks, compound masks etc.
13. Application Diagnostics for Java = always-on, real-time, deploy on any Java server, JVM, or JRockit
14. Configuration Management detects unauthorized changes in real time. Continuous change capture for os, database, middleware and applications
15. Configuration Management now integrates Enterprise Manager with My Oracle Support so you can upload configurations directly to My Oracle Support
16. Database Replay automation now can capture workloads from 9.2.0.8 onwards.
Enjoy!!!
Subscribe to:
Post Comments (Atom)
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
Labels
- Advantages and Power
- Interesting
- General Discussion
- technical
- 11g
- grid control
- New in 11g
- Grid Architecture
- article
- News
- Patching
- free
- new in 12c
- em12c cloud control
- workshop
- Packs and Plug-Ins
- book
- 11g book
- issue resolution
- webinar
- white paper
- RMAN and Grid
- charity
- cloud control
- webcast
- Greetings
- em11g
- GoldenGate
- event
- exadata
- ops center
- security grid control
- 12c book
- Launch
- OTN
- POC
- published
- seminar
- Linux and Grid Control
- PeopleSoft
- answers
- artcile
- automation
- em jobs
- list
- live chat
- migration
- overview
- presentation
- questions
- testing
- video
Other Interesting Oracle Blogs
-
-
-
-
Upcoming Events...10 years ago
-
-
2 comments:
Porus,
Is there any feature/solution within Grid to retain historical data from the repository which is helpful for capacity planning ex. database growth over the last x years etc?
As per the Enterprise Manager Advanced Configuration guide,
"Enterprise Manager aggregates your management data by hour and by day to minimize the size of the Management Repository. Before the data is aggregated, each data point is stored in a raw data table. Raw data is rolled up, or aggregated, into a one-hour aggregated metric table. One-hour records are then rolled up into a one-day table.
After Enterprise Manager aggregates the data, the data is then considered eligible for purging. A certain period of time has to pass for data to actually be purged. This period of time is called the retention time.
The raw data, with the highest insert volume, has the shortest default retention time, which is set to 7 days. As a result, 7 days after it is aggregated into a one-hour record, a raw data point is eligible for purging.
One-hour aggregate data records are purged 31 days after they are rolled up to the one-day data table. The highest level of aggregation, one day, is kept for 365 days."
Section 9.2.3 explains how to increase the retention times for the raw or aggregated data.
To modify the default retention time for each level of management data in the Management Repository, you must insert additional rows into the MGMT_PARAMETERS table.
Connect as sysman and issue the command:
INSERT INTO MGMT_PARAMETERS (PARAMETER_NAME, PARAMETER_VALUE) VALUES ('mgmt_day_keep_window','number of days');
Note the default is 365.
Post a Comment