[askdba] Re: Strange LGWR problem in alert log
- From: "Ankur Shah" <ankur_ora@xxxxxxxxxxx>
- To: <askdba@xxxxxxxxxxxxx>
- Date: Fri, 1 Oct 2004 15:41:41 -0400
Vijay...well I do have STANDBY instances but don't run LGWR but run th'h
ARCH instead for performance
standb point.My assumption was from the error it depicted that U might have
had the paremeter set mistakenly
without redos created.
> As u had mentioned this might be something to do with 9.2.0.5 patch...let
see what Oracle says
=================
Keep Posted
Ankur
----- Original Message -----
From: "Vijay, Sekhar" <sekhar.vijay@xxxxxxxxxxx>
To: <askdba@xxxxxxxxxxxxx>
Sent: Friday, October 01, 2004 3:31 PM
Subject: [askdba] Re: Strange LGWR problem in alert log
> Hi Ankur
>
> Thanks for your response. I do have log_archive_dest_2 set to use LGWR
> (without standby redo) but I am not sure how this would create the error I
> mentioned. I have had this setup for the past 4 years without once
> encountering this error. If possible, can you explain in some more detail
> your theory so I can further examine the causes ?
>
> Thanks in advance
>
>
> -----Original Message-----
> From: askdba-bounce@xxxxxxxxxxxxx [mailto:askdba-bounce@xxxxxxxxxxxxx]On
> Behalf Of Ankur Shah
> Sent: Friday, October 01, 2004 3:28 PM
> To: askdba@xxxxxxxxxxxxx
> Subject: [askdba] Re: Strange LGWR problem in alert log
>
>
> I believe U are using LGWR SYNC/ASYNC mode.If not then parameter for
STANDBY
> services is set
> to use LGWR for writing to STANDBY redo while there are no redo logs on
> STANDBY created.
>
> ========================
>
> HTHU
>
> Ankur Shah
> Oracle DBA
> DHR-GA
>
>
>
> ----- Original Message -----
> From: "Vijay, Sekhar" <sekhar.vijay@xxxxxxxxxxx>
> To: <askdba@xxxxxxxxxxxxx>
> Sent: Friday, October 01, 2004 2:46 PM
> Subject: [askdba] Strange LGWR problem in alert log
>
>
> > Hi All
> >
> > Can anyone shed some light on this weird entry I have in my alert log ?
> > This is a QA database on Sun Solaris 5.8 (db version is 9.2.0.5.0
recently
> > patched):
> >
> > Fri Oct 1 00:00:00 2004
> > LGWR received timedout error from KSR
> > LGWR: Destination LOG_ARCHIVE_DEST_2 not using standby redo logfiles;
> cannot
> > reconnect
> > Network asynch I/O wait error 2 log 2 service 'trp4.digitrade.com'
> > Fri Oct 1 00:00:00 2004
> > Errors in file /export/home/oracle/admin/trp3/bdump/trp3_lgwr_4317.trc:
> > ORA-00002: Message 2 not found; product=RDBMS; facility=ORA
> > Fri Oct 1 00:14:38 2004
> > LGWR: Completed archiving log 2 thread 1 sequence 18656
> > LGWR: Error 16164 disconnecting from destination LOG_ARCHIVE_DEST_2
> standby
> > host 'trp4.digitrade.com'
> > LGWR: Destination LOG_ARCHIVE_DEST_2 not using standby redo logfiles;
> cannot
> > reconnect
> > LGWR: Error 16169 closing archivelog file 'trp4.digitrade.com'
> > Fri Oct 1 00:14:38 2004
> > Errors in file /export/home/oracle/admin/trp3/bdump/trp3_lgwr_4317.trc:
> > ORA-16169: LGWR network server invalid parameters
> > Thread 1 advanced to log sequence 18657
> > Current log# 4 seq# 18657 mem# 0:
> > /export/home/oracle/oradata/trp3/redoa04A.log
> > Current log# 4 seq# 18657 mem# 1:
> > /export/home1/oracle/oradata/trp3/redoa04B.log
> > Fri Oct 1 00:14:39 2004
> > ARC1: Evaluating archive log 2 thread 1 sequence 18656
> > ARC1: Beginning to archive log 2 thread 1 sequence 18656
> > Creating archive destination LOG_ARCHIVE_DEST_1:
> > '/export/home/oracle/admin/trp3/arch/1_18656.dbf'
> > ARC1: Completed archiving log 2 thread 1 sequence 18656
> >
> > I tried to do some research on this but came up with a blank. Metalink
> only
> > points to a single note which is basically the OERR output. Has anyone
> seen
> > anything similar in their database ?
> >
> > I have put in a TAR with Oracle support to find out if this is related
to
> > the 9.2.0.5.0 patchset I recently installed.
> >
> > Thanks for your time.
> >
> >
> > -----Original Message-----
> > From: askdba-bounce@xxxxxxxxxxxxx [mailto:askdba-bounce@xxxxxxxxxxxxx]On
> > Behalf Of Rajesh Puneyani
> > Sent: Friday, October 01, 2004 1:28 PM
> > To: askdba@xxxxxxxxxxxxx
> > Subject: [askdba] Strange Problem with TNSPING
> >
> >
> > Hi guys,
> >
> > I have this very strange problem with TNSPING.
> >
> > My tnsnames.ora file had IP Address (rather than server names)
> > hardcoded for databases and now those IP Address are changed (but
> > server names remain the same) and I have changed those old IP
> > Addresses to SERVER NAMES.
> >
> > But now when I TNSPING those databases then it is still trying to
> > resolve the database alias from old IP Address and it is not picking
> > up the SERVER name.
> >
>
> --------------------------------------------------------------------------
> --
> > ----------------------------
> > Used TNSNAMES adapter to resolve the alias
> > Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS =
> > (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.xxx)(PORT = 1521))) (CONNECT_DATA
> > = (SERVER = DEDICATED) (SERVICE_NAME = GLIDEV)))
> >
> > Here xxx.xxx.xxx.xxx is the old IP address
>
> --------------------------------------------------------------------------
> --
> > -----------------------------
> >
> > Am I missing something here ? Is there anything cached that I needed to
> > clear ?
> >
> > Thanks and Regards
> >
> >
>
>
Other related posts:
