db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (DERBY-5793) Document new SYSCS_INVALIDATE_STORED_STATEMENTS procedure
Date Wed, 24 Oct 2012 20:22:11 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase reopened DERBY-5793:
------------------------------


Reopening to add more content based on this information from Kathey Marsden:

Run SYSCS_INVALIDATE_STORED_STATEMENTS whenever you think that your metadata queries or triggers
are mis-behaving, for example if they  throw a NoSuchMethod error on execution. Derby stores
plans for triggers and metadata queries in the database.  These should be invalidated automatically
on upgrade and at other necessary times.  Should you encounter an instance where they are
not,  you have found a bug that you should report, but one that you can likely  work around
by running SYSCS_INVALIDATE_STORED_STATEMENTS. 

                
> Document new SYSCS_INVALIDATE_STORED_STATEMENTS procedure
> ---------------------------------------------------------
>
>                 Key: DERBY-5793
>                 URL: https://issues.apache.org/jira/browse/DERBY-5793
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Documentation
>            Reporter: Mamta A. Satoor
>            Assignee: Kim Haase
>             Fix For: 10.10.0.0
>
>         Attachments: DERBY-5793.diff, DERBY-5793.stat, rrefsyscsinvalidatestoredstmts.html
>
>
> We should document the procedure that will get added as part of DERBY-5578. The new procedure
will invalidate all the stored prepared statements. When such an invalid stored prepared statement
is executed next time, it will get recompiled at that point thus generating a new plan for
it. This can be a very useful tool from support point of view, especially after upgrades.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message