No, AFAIK you will not get any rows of this table from this export. Export performs full table scan on this table and like normal select it fails without returning any rows when hitting the first corrupted block.

You have sveral options of how to pull out the table data (other than rows in the corrupted blocks).

*** If you are on 8i you can simply isue the following:

execute DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('','');

and then export the table. This will enable exp to skip over the corrupted blocks. After you are done you can reset the skip flag back to normal with:

execute DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('', '', flags=>dbms_repair.noskip_flag);

*** If you are on pre-8i or if you can't use DBMS_REPAIR, you can set special event in your init.ora:

event="10231 trace name context forever, level 10"

This event like the procedure above enable the database to skip over the corrupted blocks when performing full table scan. Start the database with this modified init.ora, export the table, shutdown the database, delete the above event from your init.ora and start the database again.

***
If you can't or wouldn't use any of the above options (for example you don't have the appropriate privileges on the database), you could find out the ROWID "boundaries" of the corrupted block and use that in your WHERE clause of the export. You should find the LAST rowid that resides in the block prior the offended block and the FIRST one that resides in the block following the corrupted one. Then you can simply use something like QUERY="where ROWID <= rid_LAST or ROWID >= rid_FIRST" in your exp, replacing rid_LAST and rid_FIRST with your actual ROWIDs found in the previous step. Note that QUERY parameter of exp is available only in 8i.