Tuesday, November 23, 2010
Wednesday, November 17, 2010
Thread 1 cannot allocate new log, sequence...
I sometimes expecting this message in alert.log file:
Thread 1 cannot allocate new log, sequence nnnnn
It can be skipped because it is not harmful but I decided to explore.
let's get some outcome at first.
Thread 1 cannot allocate new log, sequence nnnnn
It can be skipped because it is not harmful but I decided to explore.
SQL> alter system set log_checkpoints_to_alert=true;
SQL> alter system checkpoint;
let's get some outcome at first.
Wednesday, November 3, 2010
"Error: ORA-16541: site is not enabled" after ENABLE CONFIGURATION command in Data Guard Brocker
If you see something like that:
DGMGRL> connect /
Connected.
DGMGRL> DISABLE CONFIGURATION;
Disabled.
DGMGRL> edit database "dbXX" set property 'LocalListenerAddress'='(ADDRESS=(PROTOCOL=tcp)(HOST=XXX.XX.au)(PORT=1521))';
Error: ORA-16541: site is not enabled
Configuration details cannot be determined by DGMGRL
DGMGRL> ENABLE CONFIGURATION;
Error: ORA-16541: site is not enabled
Configuration details cannot be determined by DGMGRL
DGMGRL> exit
It may well happen after switchover operation.
DGMGRL> connect /
Connected.
DGMGRL> DISABLE CONFIGURATION;
Disabled.
DGMGRL> edit database "dbXX" set property 'LocalListenerAddress'='(ADDRESS=(PROTOCOL=tcp)(HOST=XXX.XX.au)(PORT=1521))';
Error: ORA-16541: site is not enabled
Configuration details cannot be determined by DGMGRL
DGMGRL> ENABLE CONFIGURATION;
Error: ORA-16541: site is not enabled
Configuration details cannot be determined by DGMGRL
DGMGRL> exit
It may well happen after switchover operation.
Labels:
CONFIGURATION,
data guard,
DGMGRL,
ORA-16541,
Physical Standby Databases
Subscribe to:
Posts (Atom)