👀 Views: 16 💬 Answers: 1 📅 Created: 2025-08-06

OCI AutonomousDatabase JavaSDK Java

I'm relatively new to this, so bear with me. I'm working with a `QuotaExceeded` behavior when attempting to create a new Autonomous Database instance on Oracle Cloud Infrastructure using the Java SDK (v2.14.0). I have verified that I still have available quota for Autonomous Databases in my account, but the behavior continues. Here’s the code snippet I’m using to create the instance: ```java import com.oracle.bmc.database.DatabaseClient; import com.oracle.bmc.database.model.CreateAutonomousDatabaseDetails; import com.oracle.bmc.database.requests.CreateAutonomousDatabaseRequest; import com.oracle.bmc.database.responses.CreateAutonomousDatabaseResponse; DatabaseClient databaseClient = DatabaseClient.builder().build(); CreateAutonomousDatabaseDetails createDetails = CreateAutonomousDatabaseDetails.builder() .compartmentId("your_compartment_id") .dbName("testdb") .cpuCoreCount(1) .dataStorageSizeInTBs(1) .adminPassword("YourSecurePassword123!") .build(); CreateAutonomousDatabaseRequest request = CreateAutonomousDatabaseRequest.builder() .createAutonomousDatabaseDetails(createDetails) .build(); try { CreateAutonomousDatabaseResponse response = databaseClient.createAutonomousDatabase(request); System.out.println("Database created successfully with ID: " + response.getAutonomousDatabase().getId()); } catch (Exception e) { e.printStackTrace(); } ``` I've double-checked my quota limits in the OCI console, and I see that I still have capacity left in the same region. Additionally, I am using the correct compartment ID. I also verified that there are no existing databases that could be consuming this quota. Has anyone else faced a similar scenario? Could there be another underlying reason for this behavior? Are there any additional considerations I should check regarding the quota for Autonomous Databases? I'd really appreciate any guidance on this.