Oracle DBaaS 1z0-160 part 3:-Best Practise to be followed for cloud deployment

  1. Do not create additional installations of Oracle Database software.Each deployment comes with Oracle Database software already installed.
  2. Do not create additional Oracle databases.
  3. Do not change fundamental characteristics of the database, such as the DB name (SID).
  4. Use only cloud tooling to update the password of the SYS and SYSTEM database users.
  5. Apply only patches that are available through Database Cloud Service.Do not apply patches from any other source unless directed to by Oracle Support.This best practice applies to both database and OS patches.
  6. Apply database and OS patches when they become available through Database Cloud Service.
  7. Update the cloud tooling regularly.
  8. Do not disable or close access to the SSH port (port 22).You can open other ports and protocols.
  9. Do not directly modify a compute node’s user or SSH settings
  10. Do not modify the default administration ports.Do not change the ports for Oracle Cloud DBaaS Monitor, Oracle Application Express, Oracle Net Listener, Enterprise Manager Database Express 12c, or Enterprise Manager 11g Database Control after the deployment is created.
  11. When specifying backups to cloud storage, use a different cloud storage container or bucket for each deployment.
  12. Do not manually remove files from a cloud storage container or bucket that is being used for backups.
  13. Do not detach, change file access permissions for, or change the mount point of any storage volume that was attached to a compute node during the creation of your deployment. In particular, do not unmount or change the file access permissions of /u01 through /u05.
  14. When adding storage to a deployment configured for local backups, be sure add both FRA storage and Data storage to maintain a 1.7-to-1 ratio of FRA storage to Data storage. That is, the FRA storage size should be 1.7 times the Data storage size.
  15. When adding storage to a deployment, especially on Oracle Cloud Infrastructure Classic, avoid adding small amounts (under 10GB) of storage.Oracle Cloud Infrastructure Classic supports a very limited number of storage volumes attached to a compute node.
  16. When adding storage to a deployment on Oracle Cloud Infrastructure Classic, use the Oracle Database Cloud Service cloud tooling. Do not use the Oracle Cloud Infrastructure Compute Classic cloud tooling unless you are adding temporary storage to use for a specific short-term period and then remove.

Tags :

About the Author

debasis maity

12+ years of rich experience on Database Administrations and on Infrastructure Solution Architect. AWS Certified Solution Architect and Senior Oracle DBA

Leave a Reply

Your email address will not be published. Required fields are marked *