Errors and Troubleshooting

Object Storage in Oracle Backend with Firebase APIs allows developers to upload, download, list, and manage files securely. While the APIs and Console make these operations straightforward, errors can occur due to invalid paths, permission issues, or misconfigured security rules. This chapter provides guidance on common errors, their causes, and troubleshooting steps to resolve them.

Upload Errors

Uploading files may fail if the file path, size, or authentication context is invalid.

Common Errors

Invalid Path: Occurs when the object path is malformed or points to a non‐existent directory.
```
{ "error": "Invalid object path" }
```
File Too Large: Uploads exceeding the configured size limit fail.
```
{ "error": "File size exceeds maximum allowed limit" }
```
Unauthorized Access: Happens when the user is not authenticated or lacks permission.
```
{ "error": "Permission denied: upload not allowed" }
```

Troubleshooting

Verify the object path matches the expected structure.
Use chunked uploads for large files.
Ensure the client is authenticated and has the correct role.

Download Errors

Downloading files may fail due to invalid paths, missing files, or insufficient permissions.

Common Errors

File not Found

{ "error": "Requested file does not exist" }

Invalid Path
```
{ "error": "Invalid object path" }
```

Unauthorized Access

{ "error": "Permission denied: download not allowed" }

Troubleshooting

Confirm the file exists in the specified bucket/path.
Ensure the path matches the expected folder structure.
Verify authentication token and user role permissions.

List Operation Errors

Listing files in Object Storage may fail if parameters are invalid or authentication is missing.

Common Errors

Invalid Bucket or Path
```
{ "error": "<details>" }
```

Unauthorized Access

{ "error": "Permission denied: list not allowed" }

Troubleshooting

Verify bucket and path values.
Ensure the token is valid and not expired.
Confirm user privileges on the bucket.

Delete Errors

Deleting files or projects may fail due to role restrictions or invalid identifiers.

Common Errors

Permission Error
```
{ "error": "PERMISSION ERROR" }
```

Invalid Project Metadata

{ "code": -20013, "error": "ORA-20013: Invalid project name/type/id" }

Troubleshooting

Only project owner role can perform delete operations.
Ensure project identifiers and tags are valid.

Key Notes

Confirm token validity and expiration.
Verify role assignment before restricted operations.
Ensure JSON payloads are correctly structured.
Use uppercase for usernames and schema identifiers.
Double-check Object Storage bucket names and paths.
Review ORDS and SDK logs for detailed error traces.