When you upgrade your entire CDB with AutoUpgrade, there is a parameter which allows you some tuning or tweaking. And I often see some misunderstanding here. Therefore, for CDB upgrades – explaining catctl_options is my focus today.
Photo by Arthur Mazi on Unsplash
catctl_options – what it is meant for
This AutoUpgrade config file parameter allows you to set specific settings, mostly for tuning, but also to override some defaults. In the documentation you will find the whole list of options. You can set it in your AutoUpgrade config file, e.g.:
upg1.catctl_options=-T
catctl_options in CDB upgrades
Here, …
Continue reading...
The downsides of the “old” auditing facilities became obvious when too many users had activities or transactions at the same time leading to audit records being written into AUD$. Contention was a typical issue. The same thing happened when too many users tried to login at the same time. Furthermore protecting the auditing information required Database Vault as there was no default protection available.
Simple question – and more a reminder to myself as I’d assume that many people have their examples somewhere already. But in upgrade and migration projects it’s sometime useful to simply select SQL statements directly from between two AWR snapshots into a SQL Tuning Set (STS). This will give you the possibility to later put a failing plan directly into a SQL Plan Baseline, part of the free Enterprise Edition’s SQL Plan Management feature.
