What's new in Customer Journeys?

Connect and learn more! ×
Subnet / Private IP not released after terminating a DBSystem — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Subnet / Private IP not released after terminating a DBSystem

Received Response
edited Jul 16, 2018 12:48PM in Database 7 comments


DBSystem created in a subnet with 2 private IP addresses. After terminating the DBSystem 2 times, we can't launch a DBSystem again.



our configuration (Proof-of-Concept for a customer) using OCI command line interface:

Compute instance VM on Subnet1, DBSystem (VM) on Subnet2 only to run the DBs (test/development environment on request). 

Our Subnet2 does have a  network (in total 4 IP addresses, of which 2 are usable). When we launch a DBSystem and terminate that twice, we can't create a new one, after 3.5hours of deployment and restoring from backup we get an error, that all private IP addresses are in use. In reality, there is no system running/launched/available at the Subnet2, so all private IP addresses should be available. 


Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!