Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect chained and migrated rows in Oracle – Part 1 | Tanel Poder Consulting #25

Open
utterances-bot opened this issue Mar 3, 2022 · 1 comment

Comments

@utterances-bot
Copy link

Detect chained and migrated rows in Oracle – Part 1 | Tanel Poder Consulting

I received a question about migrated rows recently.
It was about how to detect migrated rows in a 200TB data warehouse, with huge tables – as the ANALYZE TABLE xyz LIST CHAINED ROWS INTO command can not be automatically parallelized at table level (as DBMS_STATS can be, but oh, DBMS_STATS doesn’t gather the migrated/chained row info). Therefore the analyze command would pretty much run forever before returning (and committing) the chained row info in the output table. Also as there are regular maintenance jobs running on these tables (I suspect partition maintentance for example), then it wouldn’t be nice to keep running ANALYZE on the whole table constantly.
So, is there any faster or better way for fin

https://tanelpoder.com/2009/11/04/detect-chained-and-migrated-rows-in-oracle/

Copy link

nice~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants