tablespace level restore in HADR stand by works only for bad table spaces?

Harishkumar .Pathangay

tablespace level restore in HADR stand by works only for bad table spaces?

Hi,

table space level restore in HADR stand by works only for bad table spaces?   let me explain.

I have a primary and stand by all working well.

I do a create and drop index on primary with log index build off and also do a reorg of indexes for the table.

so obviously, the indexes are marked invalid in stand by. I need to clean it up. I can re-initialize the entire database.

but then I am thinking that table space level restore is supported in stand by as I am in 11.1

so I take a backup of entire database, and deactivate stand by, stop hadr, restore only affected table spaces [data table and data index] and then start hadr on stand by again.

expectation was that stand by will catchup with primary and all table spaces will come back to normal.

but it did not. the affected table spaces were in 0X000080 - Roll Forward Pending State.

It is not synching things up or coming back to normal.

Does that mean table space level restore in HADR stand by works only for bad table spaces?  why it will not work for good table spaces? 

thanks,

harish pathangay

Harishkumar .Pathangay

RE: tablespace level restore in HADR stand by works only for bad table spaces?
(in response to Harishkumar .Pathangay)

i did another scenario too.

i just did reorg of indexes alone in primary, then took backup on-line of database.

deactivate stand by, stop hadr on stand by and restore data and index table space lone. start hadr on stand by.

it is still in roll forward pending state and not able to catchup with primary.

table space level restore works on stand by only if table space is removed from the roll forward set on some error condition. if it is not in error condition, it does not work. 

please let me know your inputs.

 

thanks, harish p