Hi, all.
I'm trying to manually create a standby database on
Solaris 2.6 Oracle 8.0.5.2.1
The vendor for our application provided a script that
uses the command
alter index <idx> rebuild tablespace <tblspace>
NOLOGGING;
for all of their application indexes.
When I test the standby (copy datafiles, copy and
apply redo logs, bring up database) and execute a
query, I get the error message
ORA-01578: ORACLE data block corrupted (file # 17,
block # 150586)
ORA-01110: data file 17:
'/orastandby/u12/oradata/ent/adv_indexes01.dbf'
Metalink doc 164836.1 says that this can be fixed by
executing the command
alter index <idx> logging;
against all the indexes that were set nologging and
rebuilding the standby.
I tried this, and got the same corrupt block error
message on my query.
Here's the order of things:
(1) alter indexes rebuild with nologging;
(2) immediately after rebuild, alter index logging;
(3) shut down database, cold backup to disk, rcp files
to standby
(database comes up without errors; redo logs are
applied successfully. There are no errors in alert
log)
Analyzing the indexes without the "nolog" option
increases the time considerably, and we have a short
maintenance window.
Any ideas?
TIA!
Barb
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Barbara Baker
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).