Checking table corruption using export

Export utility can be used, to determine if there is a table level corruption.

exp system/manager TABLES='<table_name>' log=tbl_chk.log 

But we may have space constraint, when table is very large & we don’t have enough space to export that table. In this case, we can use ‘/dev/null’ as a output file.  It will not create a physical file, but will read through the table

exp system/manager TABLES='<table_name>' log=tbl_chk.log 
file=/dev/null  volsize=100g

NOTE: volsize defines the output file size. In this case it’s as good as unlimited.

Export logfile will have more details on corruption. Oracle support will be able to analyse the logfile & provide with the action plan.

This entry was posted in Oracle Database Corrpution and tagged . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s