Path: news.cambrium.nl!textnews.cambrium.nl!feeder2.cambriumusenet.nl!feed.tweaknews.nl!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Ora_DBA Newsgroups: comp.databases.oracle.misc Subject: Oracle Streams Archived log Downstream Capture: Source DB on RAC:A question @ RAC listeners Date: Wed, 8 Aug 2012 11:43:04 -0700 (PDT) Organization: http://groups.google.com Lines: 37 Message-ID: <85a1e047-f63e-4277-a215-ec8f24d6f610@googlegroups.com> NNTP-Posting-Host: 20.137.216.64 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1344451385 25206 127.0.0.1 (8 Aug 2012 18:43:05 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 8 Aug 2012 18:43:05 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=20.137.216.64; posting-account=ZVHXiAoAAAB9yKO-SOmGR5Z1quk0xmol User-Agent: G2/1.0 Xref: news.cambrium.nl I don't have much experience in Oracle RAC. We are implementing Oracle Streams using Archived-Log Downstream capture. S= ource and Target DBs are 11gR2. The source DB is in RAC (uses scan listeners). During Deployment, to prevent the users from accessing the source DB, the D= BA of the source DB shutdown the listener on port 1521 (changed the port nu= mber to 0000 in some file). There was one more listener on port 1523 that w= as up and running. We used port 1523 to create DB link between the 2 databa= ses. But, because the listener on Port 1521 was down, the archived logs from the= source DB could not be shipped to the shared rive. As per the source DB DB= A, the two instances in RAC use this listener/port to communicate with each= other. As such, when we ran DBMS_CAPTURE_ADM.CREATE_CAPTURE procedure from the tar= get DB, the Logminer Data Dictionary that was extracted from the source DB = to the Redo Logs was not avaialble to the target DB and the streams impleme= ntation failed. It seems that for the archived logs to ship from the source DB to the share= d drive, we need the listener on the port 1521 up and running. (Correct me = if I am wrong ). My question is:=20 Is there a way to shutdown a listener to prevent users from accessing the D= B 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 ? We asked the same question to the DBA of the source DB and we were told tha= t it could not be done.=20 Thanks in advance.