Starting a Database in OracleDB for Azure is accomplished from the blade for the database you wish to stop. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to start.
2. Select the specific database you want to start from the list. This will open the details for that specific database.
3. Select the Start icon. If the Start icon is not active, the database is already started.
4. Confirm that you want to Start the database by selecting the Yes button. If you do not wish to start that database, select the No button.
5. The command to Start the database will be submitted. The database details will update when the database has been started. Use the Refresh icon to see this.
6. For Oracle HeatWave, the HeatWave Cluster is automatically started and stopped when you start and stop the database system, but it can also be started and stopped on its own while the database system is running. If you have stopped the HeatWave Cluster on its own, you can start it again by selecting the HeatWave tab on the left menu bar, then selecting the Start icon.

Stopping a Database in OracleDB for Azure is accomplished from the blade for the database you wish to stop. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to stop.
2. Select the specific database you want to stop from the list. This will open the details for that specific database.
3. Select the Stop icon. If the Stop icon is not active, the database is already stopped.
4. Confirm that you want to Stop the database by selecting the Yes button. If you do not wish to stop that database, select the No button.
5. The command to Stop the database will be submitted. The database details will update when the database has been stopped. Use the Refresh icon to see this.
6. For Oracle HeatWave, the HeatWave Cluster is automatically started and stopped when you start and stop the database system, but it can also be started and stopped on its own while the database system is running. You can stop the HeatWave Cluster on its own by selecting the HeatWave tab on the left menu bar, then selecting the Stop icon.

Deleting a Database in OracleDB for Azure is accomplished from the blade for the database you wish to delete. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to delete. The delete function is available on the blade for every database type.
2. You can also select the specific database you want to delete from the list. This will open the details for that specific database.
3. Select the Delete icon. If the Delete icon is not active, you have not selected a database, or you do not have permissions to delete that database.
   For Oracle HeatWave, if you have enabled delete protection for the database system, you must disable this first in the settings of the database. Find the settings in the Management tab.
4. Confirm that you want to Delete the database by selecting the Yes button. If you do not wish to delete that database, select the No button.
5. The command to Delete the database will be submitted. The database details will update when the database has been deleted. Use the Refresh icon to see this.
6. For Oracle HeatWave, the HeatWave Cluster is automatically deleted if you delete the database system, but it can also be deleted on its own while the database system is running. You can delete the HeatWave Cluster on its own by selecting the HeatWave tab on the left menu bar, then selecting the Delete icon.

Restarting a Database in OracleDB for Azure is accomplished from the blade for the database you wish to stop. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to restart.
2. Select the specific database you want to start from the list. This will open the details for that specific database.
3. Select the Restart icon. If the Restart icon is not active, the database is already started.
4. Confirm that you want to Restart the database by selecting the Yes button. If you do not wish to start that database, select the No button.
5. The command to Restart the database will be submitted. The database details will update when the database has been started. Use the Refresh icon to see this.
6. For Oracle HeatWave, the HeatWave Cluster is automatically restarted when you restart the database system, but it can also be restarted on its own while the database system is running. You can restart the HeatWave Cluster on its own by selecting the HeatWave tab on the left menu bar, then selecting the Restart icon.

Download a Wallet for a database in OracleDB for Azure is accomplished from the blade for the database you want to use. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to download the wallet.
2. Select the specific database you want to start from the list. This will open the details for that specific database.
3. Select the Download wallet icon. If the Download wallet icon is not present, the database does not support this function. The task both downloads the wallet, and gives it a new password. The password for the new wallet must comply with the same password requirements you used during database provisioning. See the specific database provisioning tasks for these requirements.
4. Confirm that you want to Download wallet for the database by selecting the OK button. If you do not wish to start that database, select the Discard button.
5. The command to Download wallet for the database will be submitted. The wallet file will be downloaded locally to your machine.

Rotating a Wallet in OracleDB for Azure is accomplished from the blade for the database you wish to stop. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database where you want to rotate the connection wallet.
2. Select the specific database you want to start from the list. This will open the details for that specific database.
3. Select the Rotate wallet icon. If the Rotate wallet icon is not present, the database does not support or require this activity.
4. Confirm that you want to Rotate wallet for the database by selecting the Yes button. If you do not wish to rotate the wallet for that database, select the No button.
5. The command to Rotate wallet the database will be submitted. The database details will update when the database has been started. Use the Refresh icon to see this.

Changing a Database Password in OracleDB for Azure is accomplished from the blade for the database you wish to change. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to change the owner password.
2. Select the specific database you want to change the owner password for from the list. This will open the details for that specific database.
3. Select the Change password icon. If the Change password icon is not present, the administrator password cannot be changed using the database blade.
   The new password must comply with the same password requirements you used during database provisioning. See the specific database provisioning tasks for these requirements.
4. Confirm that you want to Change password for the database by selecting the OK button. If you do not wish to start that database, select the Discard button.
5. The command to Change password for the database will be submitted.

Database Actions in OracleDB for Azure are only supported for Oracle Autonomous Databases.

1. Go to the database blade for the database you wish to use Database Actions.
2. Select the specific database you want to use Database Actions with from the list. This will open the details for that specific database.
3. Select the Database Actions icon. If the Database Actions icon is not present, you are attempting to do this on an unsupported database type. Database Actions is only supported for Oracle Autonomous Databases.
4. Login to Database Actions using the ADMIN user and password that you set during Oracle Autonomous Database provisioning.
5. When you login successfully, you will see the Database Actions Home page on the OCI portal. For more information, see the About Oracle Database Actions documentation.

Viewing the Metrics for a Database in OracleDB for Azure is accomplished from the blade for the database you wish to stop. Each blade is slightly different and so are the database details, but the process is similar.

The following steps define the primary process for viewing your database metrics. In addition to this process, there is a mechanism provided through Microsoft Azure to view metrics. That process is defined at the end of these steps to provide a secondary approach, in desired.

1. Go to the database blade for the database you wish to view its metrics.
2. Select the specific database you want to start from the list. This will open the details for that specific database.
3. Select the Metrics icon. If the Metrics icon is not active, the database does not yet have viewable metrics. See Resolving the Metrics Icon Not Showing for a Database for more information.
4. The Microsoft Azure Application Insights blade opens.
5. You can learn more about Microsoft Azure Application Insights at About Application Insights .
6. Select the Metrics link on the left-side menu.
7. This is the Metrics blade. You can select a variety of metrics to display. Before you can see any metrics, you must select the Metrics Namespace and the specific metric or metrics you wish to chart.
   By default, the starting Metrics Namespace is the Log-based Metrics namespace. For a Oracle Autonomous Database Serverless, an Oracle Exadata Database, a Oracle Base Database, or an Oracle HeatWave Database, you will need to select the namespace as follows:

   Table 1-1 Metrics Namespace

   Database Type	Metrics Namespace
   Oracle Autonomous Database Serverless	oci_autonomous_database
   Oracle Exadata Database	oracle_oci_database
   Oracle Base Database	oracle_oci_database
   Oracle HeatWave Database	oci_mysql_database

8. Select the Metric or Metrics you wish to chart.
9. By default, the timeframe for the metrics is the Last 24 hours. To change this, select the timeframe selector at the top-right of the Metrics blade.
10. For any other issues, see the Database Troubleshooting guide.

Using Microsoft Azure for Database Metrics can be accomplished as follows:

11. From anywhere in the Microsoft Azure portal, select the Azure menu (hamburger) on the top-left of the page.
12. From this menu, select the Dashboard entry.
13. The My Dashboard portal will open. Select the drop-down at the top.
14. From this drop-down, select the specific database you wish to view.
15. This is the top of the dashboard that is created, in Microsoft Azure, for your database. There are lots of useful information and functions on this dashboard. For example, you can copy the connection strings required to access the database from this part of the dashboard. For the metrics, scroll down in the dashboard.
16. These are the metrics presented for your database.

Scaling a Database in OracleDB for Azure is accomplished from the blade for the database you wish to stop. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to scale.
2. Select the specific database you want to scale from the list. This will open the details for that specific database.
3. Select the Scale icon. If the Scale icon is not active, the database cannot be scaled. If the Scale icon is not present, this task is not available for this database type.
4. Enter the scaling options. You might be able to scale down your storage if the storage used is less than the scaled down storage selected. You cannot scale down below the storage currently in use.
5. Confirm that you want to Scale the database by selecting the Scale button. If you do not wish to start that database, select the Discard button.
6. The command to Scale the database will be submitted. The database details will update when the database has been started. Use the Refresh icon to see this.

Restoring a Database in OracleDB for Azure is accomplished from the blade for the database you wish to stop. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to start.
2. Select the specific database you want to start from the list. This will open the details for that specific database.
3. Select the Backups tab on the left menu bar.
4. Select the backup from which to restore.
5. Select the Restore icon. If the Restore icon is not active, you have not selected a backup, or there are no backups from which to restore.
   For Oracle HeatWave, you restore the backup to a new database system and HeatWave Cluster rather than reusing the old one, so the icon is labeled Restore to new DB system.
6. Confirm that you want to Restore the database by selecting the Yes button. If you do not wish to start that database, select the No button.
7. The command to restore the database will be submitted. The database details will update when the database has been started. Use the Refresh icon to see this.

Cloning a Database in OracleDB for Azure is accomplished from the blade for the database you wish to clone. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to clone.
2. Select the specific database you want to clone from the list. This will open the details for that specific database.
3. Select the Clone icon. If the Clone icon is not present, the database type does not support cloning.
4. Confirm that you want to Clone the database by selecting the Yes button. If you do not wish to start that database, select the No button.
5. The command to Clone the database will be submitted. The database details will update when the database has been cloned. Use the Refresh icon to see this.

Some of the settings for your database in OracleDB for Azure are edittable. The most common example is adding, changing, or deleting tags. Editing is accomplished from the blade for the database you wish to edit. Each blade is slightly different and so are the database details, but the process is similar.

1. Go to the database blade for the database you wish to edit.
2. Select the specific database you want to start from the list. This will open the details for that specific database.
3. Select the Edit link. If there is not an Edit link, there may be edittable settings on other blades. If there is not an Edit link for those settings, it is not something that can be changing.
4. Edit the settings as required.

Oracle Database Service for Azure (OracleDB for Azure) Portal allows you to set account-specific settings for a number of UI items, including default language, default Microsoft Azure region, and the selection of the default OracleDB for Azure Portal layout.

1. To access your Settings, select the Settings icon at the top of the OracleDB for Azure Portal.
2. To set the default subscription and location, click Subscriptions + locations from the left navigation menu.
   1. Default subscription: Choose a subscription that has been linked to your OCI tenancy through OracleDB for Azure as the default subscription. The value set here shows up as the default subscription value on the various Create Resource pages.
   2. Default location: For the selected subscription, choose a listed locations as the default provisioning location. The value set here shows up as a default location value on the various Create Resource pages.
3. There are two options for Menu behavior under Appearance:
   • Flyout: This is the default portal appearance.
   • Docked: This option docks the menu on the left side of the portal.
4. To change the Appearance, select the desire Appearance layout, and then select the Apply button. Exit the Settings when done.
5. To select a default language, click Language in the left navigation menu. Choose a language from the drop down list as the default Language. The value set here is used across the OracleDB for Azure Portal.
6. To select the signing out behavior, click Signing out in the left navigation menu. Choose a default signing out time for an inactive login. The value set here is used across the OracleDB for Azure Portal for this account.
7. You can exit the Settings at any time by selecting Home from the menu or the X icon at the top of the Settings blade. Unapplied changes are discarded.