- 17.9K All Categories
- 3.3K Industry Applications
- 3.2K Intelligent Advisor
- 59 Insurance
- 533.9K On-Premises Infrastructure
- 137.5K Analytics Software
- 38.5K Application Development Software
- 5.2K Cloud Platform
- 109.1K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 70.8K Infrastructure Software
- 105K Integration
- 41.5K Security Software
Fleet maintenance vs fleet patching and provisioning
I’ve been reading up in automated methods to patch my environments (a mix of RAC, EE, 12.1, 12.2, 19c on RHEL 7). I’ve found some good stuff on Fleet Maintenance and Fleet Patching and Provisioning.
I understand that Fleet Maintenance is primarily done through emcli commands using OEM (I use 13.3). But Fleet Patching and Provisioning requires a separate server to run.
Can anyone help me understand the advantages / disadvantages of using the one or the other? They seem pretty similar to each other.
Also, if I run either one of these, how many people does it take to run? For example, let’s say I have 400 production databases and my gold image already created, could I do this all myself (deploying, upgrading, etc) if I wanted to regularly install RUs or would it take multiple DBAs working with me?