Thank you for the quick response.
My logon schema does have the table SQLN_EXPLAIN_PLAN table and it does have the TIMESTAMP column in it.
Even though it had the TIMESTAMP field I decided to drop it and recreate it using the explain plan tool to see if it would fix the problem. The problem is still persist.
However while it created the SQLN_EXPLAIN_PLAN it asked me if I wanted to create a synonym for it and I answered yes. It then failed to create the synonym because it already existed. So I dropped the existing synonym (it was pointing at a different schema/user). I then dropped the table again and recreated the Explain Plan table and the synonym and all works great now.
The SQLN_EXPLAIN_PLAN table that it was pointing to did have the TIMESTAMP field in it as well. So I’m not sure why it was failing.
After this little experiment I realize that it would probably be best that we don’t have a synonym for the explain plan table. At least not until we find out why it couldn’t use the Explain Plan table from another schema.
Thank you for your help again!