DB Installation and Configuration best practices 3
DB Installation and Configuration best practices.
1.Separate oracle binaries owner
Description:
This can be considered if the databases are managed by different DBA groups
Benefits:
It provides more security.
Any Impact?
None
2.Multiple OracleHomes
Description:
When ever applying patch or patch set it is recommended to do on the new home.
Benefits:
The downtime is significantly reduced.
The risk is reduced significantly, as there is no rolling back a patch; you just go to the older version.
You can perform a “diff” on these two homes to see what changed. You can see the differences across multiple homes as well.
You can take several databases running on the same server to the new Oracle Home one by one.
You can see the various Oracle Homes and what patch level they are on using the inventory.
Any Impact:
Occupies more space
3.OracleDB/OEM AgentHome entry in oratab
Description:
Software home directory for DB / Agent
Benefits:
It avoids confusion when we are restarting databases/agents when we have multiple homes
Any Impact:
None
4. Set audit trail to DB
Description:
Set the audit trail to DB by placing the parameter AUDIT_TRAIL = DB in the initialization
parameter file during the database creation. Setting this parameter does not start the auditing, because an explicit AUDIT command must be given on the object. But the parameter must be set to a value other than FALSE (the default) for the command to take effect. Being a non-dynamic parameter, the database must be bounced to change the value of AUDIT_TRAIL.
Benefits:
To save the trouble and avoid an outage, always set the value to DB, even if you never intend to audit anything. It does not break anything and you will always be ready to audit when the time comes.
Any Impact:
No Bounce is required whenever we go for auditinf
5.Don’t use .log for redolog files
Description:
Don’t use .log as the extension of redo logs. Someone may run a script to remove all the log files assuming they are redundant and you will end up losing the online redo logs as well, forcing a database recovery. Instead, name them with extension “redo” or “rdo.”
Benefits:
Human errors can be minimized.
Any Impact:
None
6. Block change Tracking
Description:
Oracle tracks the physical location of all database changes for incremental backups
Benefits:
Incremental backup Time will be reduced.
Any Impact:
None
See Also: