Skip to Main Content
Forums

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Unassigned Status Of Standby Redo Log Files

437185Jul 26 2005 — edited Nov 12 2007
I created 2 standby redo log groups, and use LGWR in primary site to
transfer redo data, all are good. But when I query the V$STANDBY_LOG
view, I found that the status column of my both standby redo logs is UNASSIGNED".
also sequence#
THREAD# and all others are 0 and 0.
Any explains.

Comments

AlokKumar
Hi,
dear let me explain what you really want?I go through to your question buy unable to get your point.if you really suffering from something let the doctor know what the problem is? otherwise you end up with nothing your hand.


thanks..
399843
Hi,
It basically means that neither of the two groups has been utilized yet. Here's what will tickle the situation: Invoke a log switch on the primary database, and then watch the status on standby; one of the logs should be in use, w/ status ACTIVE. The second one will remain UNASSIGNED - probably the equivalent of INACTIVE from the v$log view.
437185
Thanks for the reply Sophie. I did perform log switch at my primary site but the status of standby redo log files remained unassinged. I am pasting here the message in my Alert Log file may be that can help you to diagonose the problem.



ALTER DATABASE SET STANDBY DATABASE PROTECTED
Tue Jul 26 15:35:18 2005
Completed: ALTER DATABASE SET STANDBY DATABASE PROTECTED
Tue Jul 26 15:35:22 2005
ALTER DATABASE OPEN
Tue Jul 26 15:35:23 2005
LGWR: Primary database is in CLUSTER CONSISTENT mode
LGWR: Primary database is in MAXIMUM PROTECTION mode
LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
LNS0 started with pid=18
Tue Jul 26 15:35:28 2005
LGWR: Error 16086 verifying archivelog destination LOG_ARCHIVE_DEST_2
LGWR: Continuing...
Tue Jul 26 15:35:28 2005
Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
ORA-16086: standby database does not contain available standby log files

LGWR: Error 16086 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host 'TESTstdb'
LGWR: Minimum of 1 applicable standby database required
Tue Jul 26 15:35:28 2005
Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
ORA-16072: a minimum of one standby database destination is required

LGWR: terminating instance due to error 16072
Instance terminated by LGWR, pid = 1864
399843
Ok, looks like a couple of initialization params may be misconfigured in your primary and/or standby sites. Particulary, log_archive_dest_1, log_archive_dest_2, log_archive_dest_state_2, and maybe a couple others, b/c your errors indicate that the primary database (I assume that was the alert log file from) doesn't know of your standby's archive log destination.
608015
hi

please try to run this Command and then open the primary database.

alter database set standby database to maximize performance;

alter database open;
1 - 5
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Dec 10 2007
Added on Jul 26 2005
#general-database-discussions
5 comments
8,143 views