Path: news.cambrium.nl!textnews.cambrium.nl!feeder3.cambriumusenet.nl!feed.tweaknews.nl!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: ddf Newsgroups: comp.databases.oracle.misc Subject: Re: Oracle Streams Archived log Downstream Capture: Source DB on RAC:A question @ RAC listeners Date: Wed, 8 Aug 2012 12:43:07 -0700 (PDT) Organization: http://groups.google.com Lines: 85 Message-ID: <63c8da19-fd9f-454e-bc35-9906a497de86@googlegroups.com> References: <85a1e047-f63e-4277-a215-ec8f24d6f610@googlegroups.com> NNTP-Posting-Host: 69.4.5.254 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1344455106 32416 127.0.0.1 (8 Aug 2012 19:45:06 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 8 Aug 2012 19:45:06 +0000 (UTC) In-Reply-To: <85a1e047-f63e-4277-a215-ec8f24d6f610@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.4.5.254; posting-account=KXUmygkAAABvBFmgDBe4RBLFwhTRAMZC User-Agent: G2/1.0 Xref: news.cambrium.nl On Wednesday, August 8, 2012 12:43:04 PM UTC-6, Ora_DBA wrote: > I don't have much experience in Oracle RAC. >=20 >=20 >=20 > We are implementing Oracle Streams using Archived-Log Downstream capture.= Source and Target DBs are 11gR2. >=20 >=20 >=20 > The source DB is in RAC (uses scan listeners). >=20 >=20 >=20 > During Deployment, to prevent the users from accessing the source DB, the= DBA of the source DB shutdown the listener on port 1521 (changed the port = number to 0000 in some file). There was one more listener on port 1523 that= was up and running. We used port 1523 to create DB link between the 2 data= bases. >=20 >=20 That 'some file' is the listener.ora file. >=20 > But, because the listener on Port 1521 was down, the archived logs from t= he source DB could not be shipped to the shared rive. As per the source DB = DBA, the two instances in RAC use this listener/port to communicate with ea= ch other. >=20 >=20 The two instances use the cluster interconnect to communicate with each oth= er, using a configured VIP, not a listener. The listener is for external c= lient connections and log transport. >=20 > As such, when we ran DBMS_CAPTURE_ADM.CREATE_CAPTURE procedure from the t= arget DB, the Logminer Data Dictionary that was extracted from the source D= B to the Redo Logs was not avaialble to the target DB and the streams imple= mentation failed. >=20 >=20 How is the local_listener parameter configured? If it's using port 1521 th= en that would explain why port 1523 wasn't used. You can change the local_= listener setting to point to the listener on port 1523. >=20 > It seems that for the archived logs to ship from the source DB to the sha= red drive, we need the listener on the port 1521 up and running. (Correct m= e if I am wrong ). >=20 >=20 See above; change local_listener to use the other listener and you should b= e fine. >=20 > My question is:=20 >=20 >=20 >=20 > Is there a way to shutdown a listener to prevent users from accessing the= DB and have another listsener up so that the archived logs can be shipped = to the shared drive ? If so, can you please give the details/example ? >=20 >=20 See above. >=20 > We asked the same question to the DBA of the source DB and we were told t= hat it could not be done.=20 >=20 >=20 No comment. >=20 > Thanks in advance. David Fitzjarrell