When making a record insert with SQL (Insert into values) from the JDBC Toolbox driver, Visual Explain and Optimizer messages shows a table scan with reason T1(no index) for the access plan. The table has a primary key index (dspdbr), 50 active records 180.000 deleted. System version is V5R3. Why does DB2 make table scans and shows this reason code?
If you're worried about the performance of this SQL Insert, I'd suggest analyzing if the Insert is being done as a Full Open or Reusable Open.
MORE INFORMATION ON THIS TOPIC
Visit the ITKnowledge Exchange and get answers to your DB2 questions fast.
Check out this Search400.com Featured Topic: Expert advice on DB2
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: Tips, tutorials and more.
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.