1. ORA-00332: Archived log is to small - May be incompletely archivedora-00334: archived log: '/global/oradata/ctsdb/archive/arch1_1212.log'
The KeepAlive value of the setup operating system can be resolved, and after the RFS process is aware that the Primary end has been broken, there will be the following information in Alertlog:
RFS: Possible network disconnect with primary databaseFri Aug 13 19:17:06 2004RFS: Possible network disconnect with primary databaseClosing latent archivelog for thread 1 sequence 1723EOF located at block 15 low SCN 0: 2164886 next SCN 0: 2164902Latent archivelog '/ global / oradata /ctsdb/archive/arch1_1723.log'If you wish to failover to this standby database, you should use thefollowing command to manually register the archivelog for recovery: ALTER DATABASE REGISTER LOGFILE '/global/oradata/ctsdb/archive/arch1_1723.log' FRI AUG 13 19:17:12 2004RFS: Possible Network Disconnect with Primary Database
2. SQL> ALTER DATABASE ACTIVATE LOGICAL Standby Database;
Alter Database Activate Logical Standby Database
ORA-16209: Logical Standby Dictionary Build Faled to Complete.
Upgrade to the problem after 9205, delete the table space originally assigned to the logminer, then CATPROC recompores all stored procedures, then execute the above command, will not be wrong.
3. The StandBy end has always been one to two logs that will not be Apply because the mechanism of the Logical Standby Apply based on TraSction determines that it will not receive the Redo all Apply because the transaction may span several Redo. At this point in the main library DOWN, try to reduce the requirements of data loss. It is very unsatisfactory.
4. Alter Database Start Logical Standby Apply Initial
ORA-01332: Internal Logminer Dictionary Error
It is not solved, it is this error, let me completely lose confidence in logical standby.
BUG is much too much, the performance is low, although it can be apply readonly, but this advantage is really a decisive role in front of its instability.
The entire program is changed to: Remote Physical Standby, local plus one server provides Query services with MV Replication.
BTW: Metalink can check the problem, but I hope that Oracle's technicians will help you solve the problem in a timely manner. A group of people only know common sense, I want to have few practical experience.
