Info icon
End of Life Notice: For Trend Cloud One™ - Conformity Customers, Conformity will reach its End of Sale on “July 31st, 2025” and End of Life “July 31st, 2026”. The same capabilities and much more is available in TrendAI Vision One™ Cloud Risk Management. For details, please refer to Upgrade to TrendAI Vision One™
Use the Knowledge Base AI to help improve your Cloud Posture

Define Contacts for Operational Notifications and Announcements

TrendAI Vision One™ provides continuous assurance that gives peace of mind for your cloud infrastructure, delivering over 1400 automated best practice checks.

Risk Level: Low (generally tolerable level of risk)
Rule ID: OCI-AutonomousAIDatabase-009

Ensure that your OCI Autonomous AI Databases are configured with customer contacts in order to receive critical operational notifications, announcements, and unplanned maintenance notices directly from Oracle, ensuring the appropriate administrator group is immediately aware of service-related issues and upcoming events, thus preventing missed communications that could impact business continuity.

Security
Operational
excellence

When customer contacts are configured, Oracle sends service-related notifications such as unplanned maintenance alerts, upgrade notices, and wallet-expiration warnings to the specified email addresses. This ensures that the right personnel are informed promptly about operational issues, enabling faster response, better continuity planning, and reduced risk of unexpected downtime.


Audit

To determine if your OCI Autonomous AI Databases are configured with customer contacts, perform the following operations:

Using OCI Console

  1. Sign in to your Oracle Cloud Infrastructure (OCI) account.

  2. Navigate to Autonomous AI Databases console available at https://cloud.oracle.com/db/adbs.

  3. For Applied filters, choose an OCI compartment from the Compartment dropdown menu, to list the Autonomous AI Databases provisioned in the selected compartment.

  4. Click on the name (link) of the Autonomous AI Database that you want to examine, listed in the Display Name column.

  5. Select the Autonomous AI Database information tab to access the maintenance configuration settings available for the selected database instance.

  6. In the Maintenance section, check the Customer contacts attribute value to determine whether operational notifications and announcements are sent for your database instance. If Customer contacts is set to None, the selected OCI Autonomous AI Database will not receive notifications for service-related operational issues and announcements.

Using OCI CLI

  1. Run iam compartment list command (Windows/macOS/Linux) with output query filters to list the ID of each compartment available in your Oracle Cloud Infrastructure (OCI) account:

    oci iam compartment list
    	--all
    	--include-root
    	--query 'data[]."id"'
    
  2. The command output should return the requested OCI compartment identifiers (OCIDs):

    [
    	"ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
    	"ocid1.compartment.oc1..abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd"
    ]
    
  3. Run db autonomous-database list command (Windows/macOS/Linux) with the ID of the OCI compartment that you want to examine as the identifier parameter, to list the ID of each Autonomous AI Database provisioned in the selected OCI compartment:

    oci db autonomous-database list
    	--compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
    	--all
    	--query 'data[]."id"'
    
  4. The command output should return the requested database instance IDs:

    [
    	"ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
    	"ocid1.autonomousdatabase.oc1.ap-sydney-1.abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd"
    ]
    
  5. Run db autonomous-database get command (Windows/macOS/Linux) with the name of the Autonomous AI Database that you want to examine as the identifier parameter and custom output filters to determine if customer contacts are configured for the selected database instance:

    oci db autonomous-database get
    	--autonomous-database-id 'ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
    	--query 'data."customer-contacts"'
    
  6. The command output should return the customer contacts (i.e., email address(es)) defined for the selected instance:

    Query returned empty result, no output to show.
    

    If the db autonomous-database get command output returns Query returned empty result, no output to show., as shown in the output example above, there are no customer contacts defined for the selected database instance. As a result, your OCI Autonomous AI Database will not receive notifications for service-related operational issues and announcements.

Remediation / Resolution

To ensure that Oracle Cloud Infrastructure (OCI) sends operational notifications and announcements for your Autonomous AI Databases, perform the following operations:

Using OCI Console

  1. Sign in to your Oracle Cloud Infrastructure (OCI) account.

  2. Navigate to Autonomous AI Databases console available at https://cloud.oracle.com/db/adbs.

  3. For Applied filters, choose an OCI compartment from the Compartment dropdown menu, to list the Autonomous AI Databases provisioned in the selected compartment.

  4. Click on the name (link) of the Autonomous AI Database that you want to configure, listed in the Display Name column.

  5. Select the Autonomous AI Database information tab to access the maintenance configuration settings available for the selected database instance.

  6. In the Maintenance section, choose Manage next to Customer contacts to manage customer contacts for the selected Autonomous AI Database.

  7. In the Contact email box, enter the email address where you want to receive notifications for your database instance, and then choose Save to apply the changes. Use the Add customer contact button to add as many contacts as needed. The customer contacts (i.e., email addresses) specified in this step will receive operational notices and announcements as well as unplanned database maintenance notifications.

Using OCI CLI

  1. Run iam compartment list command (Windows/macOS/Linux) with output query filters to list the ID of each compartment available in your Oracle Cloud Infrastructure (OCI) account:

    oci iam compartment list
    	--all
    	--include-root
    	--query 'data[]."id"'
    
  2. The command output should return the requested OCI compartment identifiers (OCIDs):

    [
    	"ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
    	"ocid1.compartment.oc1..abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd"
    ]
    
  3. Run db autonomous-database list command (Windows/macOS/Linux) with the ID of the OCI compartment that you want to examine as the identifier parameter, to list the ID of each Autonomous AI Database provisioned in the selected OCI compartment:

    oci db autonomous-database list
    	--compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
    	--all
    	--query 'data[]."id"'
    
  4. The command output should return the requested database instance IDs:

    [
    	"ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
    	"ocid1.autonomousdatabase.oc1.ap-sydney-1.abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd"
    ]
    
  5. Run db autonomous-database update command (Windows/macOS/Linux) with the name of the Autonomous AI Database that you want to configure as the identifier parameter, to enable operational notifications and announcements for the selected database instance. The customer contacts (i.e., email addresses) specified for the --customer-contacts parameter will receive operational notices and announcements as well as unplanned database maintenance notifications:

    oci db autonomous-database update
    	--autonomous-database-id 'ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
    	--customer-contacts '[{"email": "user@domain.com"}]'
    
  6. Type Y and press Enter for confirmation:

    WARNING: Updates to long-term-backup-schedule and freeform-tags and defined-tags and security-attributes and whitelisted-ips and standby-whitelisted-ips and nsg-ids and customer-contacts and resource-pool-summary and scheduled-operations and db-tools-details and vanity-url-details and encryption-key will replace any existing values. Are you sure you want to continue? [y/N]: Y
    
  7. The command output should return the configuration information available for the modified database instance:

    {
    	"data": {
    		"allocated-storage-size-in-tbs": 0.0078125,
    		"are-primary-whitelisted-ips-used": null,
    		"auto-refresh-frequency-in-seconds": null,
    		"auto-refresh-point-lag-in-seconds": null,
    		"autonomous-container-database-id": null,
    		"autonomous-maintenance-schedule-type": "REGULAR",
    		"availability-domain": "ABCD:AP-SYDNEY-1-AD-1",
    		"failed-data-recovery-in-seconds": null,
    		"freeform-tags": {},
    		"id": "ocid1.autonomousdatabase.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
    		"in-memory-area-in-gbs": null,
    		"in-memory-percentage": null,
    		"infrastructure-type": null,
    		"is-access-control-enabled": null,
    		"is-auto-scaling-enabled": true,
    		"is-auto-scaling-for-storage-enabled": true,
    		"is-backup-retention-locked": true,
    		"is-data-guard-enabled": true,
    		"is-dedicated": false,
    		"is-dev-tier": null,
    		"is-free-tier": false,
    		"is-local-data-guard-enabled": false,
    		"is-mtls-connection-required": true,
    		"is-preview": false,
    		"is-reconnect-clone-enabled": false,
    		"is-refreshable-clone": null,
    		"is-remote-data-guard-enabled": false,
    		"key-store-wallet-name": null,
    		"kms-key-id": "ORACLE_MANAGED_KEY",
    
    		...
    
    		"license-model": "LICENSE_INCLUDED",
    		"lifecycle-details": null,
    		"lifecycle-state": "UPDATING",
    		"local-adg-auto-failover-max-data-loss-limit": null,
    		"local-disaster-recovery-type": "BACKUP_BASED",
    		"time-data-guard-role-changed": null,
    		"time-deletion-of-free-autonomous-database": null,
    		"time-disaster-recovery-role-changed": null,
    		"time-earliest-available-db-version-upgrade": "2025-12-13T14:10:00+00:00",
    		"time-latest-available-db-version-upgrade": "2025-12-13T13:40:00+00:00",
    		"time-local-data-guard-enabled": "2025-12-13T09:27:58.721000+00:00",
    		"time-maintenance-begin": "2025-12-15T06:00:00+00:00",
    		"time-maintenance-end": "2025-12-15T08:00:00+00:00",
    		"time-of-auto-refresh-start": null,
    		"time-of-joining-resource-pool": null,
    		"time-of-last-failover": null,
    		"time-of-last-refresh": null,
    		"time-of-last-refresh-point": null,
    		"time-of-last-switchover": null,
    		"time-of-next-refresh": null,
    		"time-reclamation-of-free-autonomous-database": null,
    		"time-scheduled-db-version-upgrade": null,
    		"time-undeleted": null,
    		"time-until-reconnect-clone-enabled": null,
    		"total-backup-storage-size-in-gbs": 0.0,
    		"used-data-storage-size-in-gbs": null,
    		"used-data-storage-size-in-tbs": null,
    		"vanity-connection-urls": null,
    	},
    	"etag": "abcd1234",
    	"opc-work-request-id": "ocid1.coreservicesworkrequest.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd"
    }
    

References

Publication date Dec 3, 2025