Skip to content

Pod is Running, but SingleInstanceDatabase Object Status is Pending #175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ca2510fl opened this issue Apr 30, 2025 · 0 comments
Open

Comments

@ca2510fl
Copy link

Hi,

I am encountering an issue where the Pod related to the Oracle Database Operator is running, but the associated SingleInstanceDatabase object (named sidb-ords) has the status Pending. This seems to indicate that the operator is unable to proceed with the creation or initialization of the database, despite the pod being active.

Steps Taken:

  • I have verified the ClusterRoleBinding and ServiceAccount configurations, which seem to be correct.
  • I tried patching the SingleInstanceDatabase object to trigger a re-evaluation, but the status remains Pending.
  • I also deleted and re-applied the object, but the status stays in the same state.

The same Oracle Database Operator is also being used successfully for a Multitenant Database (CDB), and everything works as expected in that case. However, I am unsure if the current operator setup supports SingleInstanceDatabase (SIDB) properly or if a separate Oracle operator is required for SIDB.

Additionally, there are no errors related to this issue in either the Pod logs or the Oracle Operator Pod logs, which makes the problem harder to diagnose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant