Hi Tamil,

Yes, I also nopticed that one workaround would be not to use the partition name. Another workaround would be to drop the index. Without index, even if it's no using it, Oracle will generate another explain plan and so not make this error.

Because most of our scripts uses the partiton name to limit the data to the data of the current month it would be a lot of work to use this workaround. Also even then I think that Oracle may, as soon as it's using the same execution plan again, return the wrong result.

I'm wondernig what kind of solution Oracle Support will recommand.