Oracle Consulting Oracle Training Oracle Support Development
Home
Catalog
Oracle Books
SQL Server Books
IT Books
Job Interview Books
eBooks
Rampant Horse Books
911 Series
Pedagogue Books

Oracle Software
image
Write for Rampant
Publish with Rampant
Rampant News
Rampant Authors
Rampant Staff
 Phone
 800-766-1884
Oracle News
Oracle Forum
Oracle Tips
Articles by our Authors
Press Releases
SQL Server Books
image
image

Oracle 11g Books

Oracle tuning

Oracle training

Oracle support

Remote Oracle

STATSPACK Viewer

Privacy Policy

 

 
 

table fetch continued row

Article by Rampant Author Brian Carr

This indicates that rows are spanning across multiple blocks. While this may simply be indicative of long rows, it can also be indicative of data fragmentation.

Recommendation: Consider reorganizing data via export/import to pack rows more tightly and alleviate chained row issues. Another option is using larger block sizes on tables with long rows.

It has been seen (anecdotal evidence) that dropping and recreating Global Temporary Tables on a periodic basis can have positive performance improvements.

Additionally it has been proven that issuing REBUILDs on indexes to compact it and minimize fragmented space can help performance.

Recommendation: Perform REBUILDs on indexes. After issuing a REBUILD on your indexes be sure to gather stats via the DBMS_STATS package. Also consider reorganizing data via export/import to pack rows more tightly and alleviate chained row issues.

(FRAGMENTATION = POOR PERFORMANCE)

 

 

 

 

   

 Copyright © 1996 -2016 by Burleson. All rights reserved.


Oracle® is the registered trademark of Oracle Corporation. SQL Server® is the registered trademark of Microsoft Corporation. 
Many of the designations used by computer vendors to distinguish their products are claimed as Trademarks