Maintaining the Manageability of Exadata Cloud Service
The following best practices ensure that your Oracle Database Exadata Cloud Service instances stay manageable.
To keep your Exadata Cloud Service instances manageable, follow these guidelines:
-
Wherever possible, use Oracle-supplied cloud interfaces (Web consoles, cloud-specific tools, or REST APIs) to perform lifecycle management and administrative operations. For example, you should use the Oracle Database Cloud Service console to create databases instead of manually running the Oracle Database Configuration Assistant (DBCA), and you should use the Oracle Database Cloud Service console or the
exadbcpatchmulti
command to apply Oracle Database patches instead of manually runningopatch
. -
Do not change the compute node OS user accounts for the
opc
andoracle
users. -
Do not alter the SSH keys that are used to automate Exadata Cloud Service. There are three Exadata Cloud Service automation keys, which are stored in one or more of the following files:
/root/.ssh/authorized_keys
/home/opc/.ssh/authorized_keys
/home/oracle/.ssh/authorized_keys
You can identify the Exadata Cloud Service automation keys by using the following key comments:
PUBLIC_KEY
identifies a key that is associated with Database Cloud Services automation.OEDA_PUB
identifies a key that is associated with the Oracle Exadata Deployment Assistant.EXACLOUD_KEY
identifies a key that is associated with Exadata Cloud Service infrastructure automation.
-
Apply the quarterly Patch Set Updates (PSUs) regularly, every quarter if possible.
-
Do not change the ports for Oracle Net Listener, or Enterprise Manager.