I agree with Ric that it should be possible. However, there is a possibility that apply process will go crazy as object_id and data_object_id will be changed in LSTBY database (as mentioned - test, test, test). In this case an alternative is to reinstantiate the table but it will need to pull all the data from primary via db link and might actually impact your primary db (at least you will need to make sure you don't hit ORA-1555).
Yes I believe you can do that. The SQL Apply used to maintain the logical standby doesn't require that all the tables be in the same tablespace as the primary like a physical standby. I'm not sure how the SQL Apply and the online reorg will play together however. It's very likely that all this activity on the logical standby will cause it to slow do to such a degree that the apply service will fall way behind. I think it would be best to suspend the apply service (ALTER DATABASE STOP LOGICAL STANDBY APPLY), do the reorg then restart the apply service (ALTER DATABASE START LOGICAL STANDBY APPLY). Have them both going at the same time could be interesting.
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of qihua wu Sent: Tuesday, June 27, 2006 9:50 PM To: oracle-l@xxxxxxxxxxxxx Subject: Is it possible to reorganize tables for logical standby while maintain the synchronization?
So is it possible to create a logical standy based on the production database, and then reorg the logical standby, after the reorg is done, then switch the role of the standby to primary database? As far as I know, the logical standy use sql appying instead of redo applying, so the transaction should be able to applied to logical standby while the reorg is under going.
-- Best regards, Alex Gorbachev
http://blog.oracloid.com -- //www.freelists.org/webpage/oracle-l