Amund Tenstad

Any update on this @alyssajotice? Also see https://github.com/MicrosoftDocs/live-share/issues/4646

Thanks for looking into this. I mean an invalid PDB name, so that the DB server wont create the PDB inside the existing (and working) CDB. ```yaml --- apiVersion: database.oracle.com/v1alpha1...

> What is the sequence of event leading to the ORA-65197? can you please specify list of kubectl commands used? did you attempt to delete resource using "kubectl delete pdbs...

> Issue reproduced in house working on it Sweet! Would be nice to be able to just `action: Delete` it, without requiring it to be correct configured for deletion. But...

Any update on if deleting the PDB resource in Kubernetes can result in the PDB being deleted in the database server? (not having to update the Kubernetes PDB resource's action...

I'm sorry to say that doesn't work for us. It's not the common declerative way of managing infrastructure (and does not support cleaning up resouces by deleting the Kubernets objects)....

Thats nice, meaning it's not a technical issue! The thing we disagree about is then only declerative vs imperative management of the PDB resource. We would like it to behave...

`.op(Op::postfix(Rule::EOI))` and ```rust .map_postfix(|lhs, op| match op.as_rule() { Rule::EOI => lhs, ``` seems to work :smile:

Don't have the operator installed anymore, but can easily be reproduced. 1. Create CDB with a [`ordsImage`](https://github.com/oracle/oracle-database-operator/blob/bb344e4dee6ae72e5132f55e15ca4deb55557e71/config/crd/bases/database.oracle.com_cdbs.yaml#L151), then update the `ordsImage`. 2. Create CDB, then find the `ReplicaSet` just created....

Sorry, it's not a two step process, but two separate examples. And no, I do not really need to update the image, it's just an example field to illustrate the...