# Non-Production OCI Autonomous Databases Left Running 24/7 Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/non-production-oci-autonomous-databases-left-running-24-7 Development, test, training and demo Autonomous AI Databases are often used only during working hours but left running around the clock. By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Development, test, training and demo Autonomous AI Databases are often used only during working hours but left running around the clock. PointFive Research Cloud cost research at PointFive OCI service [OCI Autonomous Database](https://www.pointfive.co/efficiency-hub/cloud-services/oci-autonomous-database) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0553 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. A running Autonomous AI Database bills its base ECPU count every hour whether or not any session is connected, so nights and weekends can account for most of a non-production database's compute cost. Oracle provides a built-in Auto Start/Stop Schedule specifically so that shutdown periods can be scheduled for times when a system is not in use. A stopped Autonomous AI Database has zero ECPU usage and keeps its data, so stopping idle databases removes compute cost without rebuilding anything. Stopping is manual unless a schedule is set, and because related resources are easy to miss: refreshable clones start and stop independently of their source database. ## Billing model The pricing dimensions that drive this cost. ECPU usage is measured each second and averaged across the hour for as long as the database is running. Running database Billed for base ECPUs every hour, plus any auto-scaled ECPUs, regardless of activity Stopped database Zero ECPU usage and CPU billing halted; storage and backup storage, billed per GB-month, continue to accrue Local Data Guard peer Not billed for ECPU while the primary is stopped Refreshable clone Has its own ECPU count and is started and stopped independently of its source database ## How to detect 4 checks to find it in your estate. - Identify non-production Autonomous databases by compartment, tags or display name, and check whether the Auto start/stop schedule field under General Information on the database details page is set - Chart Sessions, CurrentLogons and CpuUtilization in the oci\_autonomous\_database metric namespace by hour of day and day of week to find databases with no activity outside business hours - Find databases with no logons and near-zero CPU for many days, which are candidates for termination rather than scheduling - List refreshable clones whose source database is stopped on a schedule but that remain running themselves ## How to fix 4 ways to remove the waste. - Enable Auto Start/Stop Schedule from More actions on the database details page, selecting start and stop times per day of the week (hourly, in UTC); only a stop time or only a start time can also be set - Apply the same schedule to refreshable clones that are only used together with their source, since stopping the source does not stop them - For databases that are no longer used, take a final backup or export and terminate them; note that undeleting a terminated database bills base ECPUs and storage for the whole period it was deleted - Preconditions: a scheduled stop ends running sessions and in-flight transactions like a manual stop, Always Free databases do not support schedules, and Oracle recommends starting a database at least once every 7 days because a longer stop can make the next start take significantly longer ## Documentation Vendor references for pricing and configuration. - [Schedule Start and Stop Times for an Autonomous AI Database Instance docs.oracle.com](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/autonomous-auto-stop-start.html) - [Stop Autonomous AI Database docs.oracle.com](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/autonomous-stop.html) - [Oracle Autonomous AI Database Serverless Features Billing docs.oracle.com](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/autonomous-features-billing.html) - [Autonomous AI Database Pricing oracle.com](https://www.oracle.com/autonomous-database/pricing/) - [Available Metrics: oci\_autonomous\_database docs.oracle.com](https://docs.oracle.com/en-us/iaas/autonomous-database-serverless/doc/autonomous-monitor-metrics-list.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - OCI Autonomous Database CER-0552 ### [Underutilized OCI Autonomous Database ECPUs](https://www.pointfive.co/efficiency-hub/inefficiencies/underutilized-oci-autonomous-database-ecpus) OCI Autonomous AI Database (Serverless) bills every running hour for the base ECPU count set on the database, whatever the workload actually uses. Base ECPUs are often sized for a peak, a load test or a migration and left there, so... Databases - OCI Base Database CER-0554 ### [Overprovisioned CPU on OCI Base Database Systems](https://www.pointfive.co/efficiency-hub/inefficiencies/overprovisioned-cpu-on-oci-base-database-systems) OCI Base Database Service virtual machine DB systems are billed for every enabled OCPU or ECPU on each node, whether the database uses them or not. DB systems sized for an expected peak, a migration or a vendor sizing guide and then left... Databases - AWS RDS CER-0299 ### [Orphaned RDS Backup Storage After Database Deletion](https://www.pointfive.co/efficiency-hub/inefficiencies/orphaned-rds-backup-storage-after-database-deletion) An RDS database instance is deleted but its manual snapshots or retained backups remain. Unlike automated backups tied to a live instance, these backups persist independently and continue generating storage costs despite no longer... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.