Change in Execution Plan when huge number of rows loaded into the table
(Doc ID 1284117.1)
Last updated on AUGUST 17, 2023
Applies to:Oracle TimesTen In-Memory Database - Version 184.108.40.206.6 and later
Information in this document applies to any platform.
After ttbulkcp is executed on the table the execution plan generated for the below query was changed and query become very slow.
1) Inserted records into the table using ttbulkcp
Here the optimizer is using the TblLkTtreeScan along with <table02>.XXX_DATE_S >= <table01>.XXX_DATE_S condition in the execution plan. The exucution time was very high. It was taking 241 seconds.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document