How to update records without invalidating cursor oracle Free sexy video chat in mobile
When you gather statistics on a table, the goal is to get new plan if statistics have changed, so you can expect cursor invalidation.
However, invalidating immediately all cursors that have a dependency with the table may cause a hard parse storm and this is why by default rolling invalidation occurs: invalidation of cursor will be planned randomly in a time window that follows next execution.
When you have the same statement that has several versions (children), the view v$sql_shared_cursor shows the reason why the statement cannot be shared.
You may be able to find that for each child cursor except the first one, why it was not possible to share a previously created child cursor.
Lets create the objects so we can make some changes and see what happens.12c comes with a new feature, global temporary table private stats where execution plans are not shared between sessions.