Pod is Running, but SingleInstanceDatabase Object Status is Pending

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.