富国银行如何用OEM+Cloud+Control监控1万多个实例？.pdfVIP

How We Do It: Monitoring Databases at Scale Using Oracle Enterprise Manager (CAS6176) Tim Albrecht and Vijay Sambandam Wells Fargo Bank September 2019 © 2019 Wells Fargo Bank, N.A. All rights reserved. Agenda • Enterprise Manager Evolution at Wells Fargo • EM 13c Environment • Operational Basics Allowing Scalability • Maintaining a highly available, secure EM Infrastructure • Summary There is an appendix that contains sample “working” info that can help when your OEM environment scales up. Included are SQL, EMCLI commands, and python examples, that could be used to manage your OMS environment. 1 OEM’s Evolution at Wells Fargo Secondary Monitoring Tool Critical to worldwide financial offerings 2009(10g) 2019 (13.3) 200+ agents, 100 Clusters, 100’s RAC DBs. 2000+ agents, 330 Clusters, 5,000+ RAC DBs, 12K+ Instances, 90 Exadata, 350 ZFS/ZBA DBA scripts used extensively. DBAs consider OEM secondary No DBA scripts allowed on shared infrastructure. OEM monitors ALL DBs (Required) OEM monitoring not required, some important apps monitored OEM monitors DBs supporting the critical applications including Stores, trading, ATM. OEM monitors DBs across the country OEM monitors DBs across the world HA implemented, rarely tested. Long outages with no impact. OEM considered