Abandoned Oracle multipart uploads keep billing you for the parts

TL;DR

Abort multipart uploads you no longer need, and add a lifecycle rule for uncommitted parts so crashed uploads do not turn into a line item. Deleting the not-quite-object does nothing because there is no object yet.

Steps

1. Abort multipart uploads you no longer need, and add a lifecycle rule for uncommitted parts so crashed uploads do not turn into a line item.
2. Deleting the not-quite-object does nothing because there is no object yet.

When to use

Use this skill when you run into "Abandoned Oracle multipart uploads keep billing you for the parts".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: If a multipart upload to Oracle Object Storage is started but never committed, the uploaded parts sit in inventory and you are charged for them anyway. Deleting the not-quite-object does nothing because there is no object yet. You have to list active uploads and abort them, or set an Object Lifecycle Management rule to clean up uncommitted uploads automatically.

Verified resolution: Abort multipart uploads you no longer need, and add a lifecycle rule for uncommitted parts so crashed uploads do not turn into a line item.

Source URL: https://www.oracle.com/it/cloud/storage/object-storage/faq/