On 11/30/15 9:27 AM, Alex wrote:
Hello developers,
I have a database that was recently upgraded from 10.11 to 10.12 via
"upgrade=true" connection attribute.
After dropping a trigger on a table I can't create any new triggers on
that table, getting this error:
Error: StoredPreparedStatement '19ba803c-014e-b216-6d98-00000650b418'
does not exist.
SQLState: 42X94
ErrorCode: 30000
It was working when DB was on 10.11 version. I found this ID in 2
system tables; attaching their exports. They were made before dropping
the trigger - the marked lines are not there anymore after the drop. I
never manipulated system tables or database files of course.
What I need help with is how to boil it down to a test case to create
a JIRA issue. I tried setting up 10.11 database with the exact same
DDL, upgrading it to 10.12 and then dropping/creating the trigger - it
works fine. A database backup and full DDL history are available.
Any hints?
--
/--Regards, Alex/
Hi Alex,
Does it help if you run SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS()
(see
http://db.apache.org/derby/docs/10.12/ref/rrefsyscsinvalidatestoredstmts.html)?
There were some trigger (re)compilation problems in older releases. In
scripting the problem, you might try creating the database with an old
Derby version like 10.8.3.0. Do you know how old the original database
is and what version of Derby was used to create it initially?
Thanks,
-Rick