Let me start off by saying I’m somewhat of a grisly veteran when it comes to attending Oracle OpenWorld, having attended more than a handful of OpenWorld conferences over the years.
Let me start off by saying I’m somewhat of a grisly veteran when it comes to attending Oracle OpenWorld, having attended more than a handful of OpenWorld conferences over the years.
The Federal Information Processing Standard (FIPS) is a government standard (140-2) for identifying cryptographic security requirements to protect data at rest and transit over the network. FIPS has multiple levels ranging from 1 (lowest) to 4 (highest). The 140-2 represents level 2: this applies to the operational environment for a software module which is the highest level for software. For those that wonder how to get to Level 4 on the database, it only applies to hardware components.
There are many aspects of the patching process which have been automated by Oracle to assist and reduce the complexity, but these engineered systems contain intricate components requiring system and database administrators to account for the local changes prior to beginning the patch cycle.
Here’s what you need to know to begin a patch on Oracle Exadata.
Because I was an Oracle DBA by trade—and everything was command line driven—it was confusing at the time to understand the commands and purpose behind each process.
In addition, in choices like classic mode vs. integrated capture and data pump vs. no data pump, there was a learning curve that clearly required a good understanding of its capabilities and key decisions before even beginning setup.