data pump fails

With the physical IP it is working

EXTRACT PXDWN

USERIDALIAS oraggext

--RMTHOST proddb-scan, MGRPORT 7809

RMTHOST 10.215.227.17, MGRPORT 7809

RMTTRAIL /ogg/ora12c/dirdat/cd

but with scan host name(proddb-scan) I am getting the above error:

proddb-scan

ERROR   OGG-01224  Oracle GoldenGate Capture for Oracle, pxdwn.prm:  TCP/IP error 146 (Connection refused), endpoint: proddb-scan:7809.

Hi Veera,

please find below the pump parameter file:

EXTRACT PXDWN

USERIDALIAS oraggext

--RMTHOST proddb-scan, MGRPORT 7809

RMTHOST 10.215.227.17, MGRPORT 7809

RMTTRAIL /ogg/ora12c/dirdat/cd

--RMTTRAIL /data1/oggdwn/dirdat/SOURCE/lt

PASSTHRU

TABLE CBS_CORE.CB_INSTALLMENT;

TABLE CBS_CORE.CB_INSTALLMENT_DTLS;

TABLE CBS_CORE.cb_serv_installment_dtls;

TABLE CBS_CORE.cb_subs_deposits;

TABLE CBS_CORE.cb_bill_cycle;

TABLE CBS_CORE.CB_SUBS_PROVISIONING;

TABLE CBS_CORE.cb_order_request_dtls;

TABLE CBS_CORE.CB_WORK_ORDER;

TABLE  CBS_CORE.CB_SUB_AR_AP;

TABLE CBS_CORE.WF_WRKFLWMGR;

TABLE CBS_CORE.cb_offers;

TABLE CBS_CORE.CB_SUBS_PAID_ADV_DTLS;

TABLE CBS_CORE.INV_ITEM_MASTER;

TABLE  CLM_TT.tt_ticketinfo;

TABLE CLM_TT.CB_FAULT_TYPES;

TABLE CLM_TT.TT_TICKET_ADDNL_INFO;

TABLE CLM_TT.wf_todoitem;

TABLE CLM_TT.WF_WORKASSIGNMENT_HISTORY;

TABLE CLM_TT.WF_WORKASSIGNMENT;

TABLE CBS_CORE.wf_usergroup;

TABLE CLM_TT.wf_todoitem_history;

TABLE CLM_TT.TT_TICKETINCIDENT;

TABLE CLM_TT.TT_CATEGORY_MASTER;

TABLE CLM_TT.WF_WORKFLOW;

TABLE CBS_CORE.CB_USER_GROUP;

TABLE CBS_CORE.CB_USERS;

TABLE CBS_CORE.CB_SUB_SERVICES;

TABLE CBS_CORE.CB_ADVANCE_RENTAL;

TABLE  CBS_CORE.CB_SUB_INVOICE;

TABLE  CBS_CORE.CB_BANK_MASTER;

TABLE  CBS_CORE.CB_CR_DB_NOTES;

TABLE  CBS_CORE.CB_SUBS_OFFER_DETAILS;

TABLE  CBS_CORE.CB_SUBSCRIBER_SUB_CATEGORY;

TABLE  CBS_CORE.CB_SUBSCRIBER_MASTER;

TABLE  CBS_CORE.CB_SUBS_POS_SERVICES;

TABLE  CBS_CORE.CB_SUBSCRIBER_CATEGORY;

TABLE  CBS_CORE.CB_ADDRESS_XML;

TABLE  CBS_CORE.CB_RETAIL_OUTLETS;

TABLE  CBS_CORE.CB_RECEIPTS;

TABLE  CBS_CUST.CB_POS_TRANS_DTLS;

TABLE CBS_CUST.CB_POS_TRANSACTIONS;

proddb-scan is the virtual host name for target.

Regards,

Joe

Hi Veera,

ping is fine

ora12c@cbsdb1:/u01/app/ora12c/product/12.1.0/dbhome_1/network/admin$ ping -s proddb-scan

PING proddb-scan: 56 data bytes

64 bytes from proddb-scan.telecom.mu (10.215.227.23): icmp_seq=0. time=0.127 ms

64 bytes from proddb-scan.telecom.mu (10.215.227.23): icmp_seq=1. time=0.108 ms

64 bytes from proddb-scan.telecom.mu (10.215.227.23): icmp_seq=2. time=0.111 ms

64 bytes from proddb-scan.telecom.mu (10.215.227.23): icmp_seq=3. time=0.085 m

Regards,

Joe

Hi,

the IP address is the physical IP address for that server.

proddb-scan is the virtual IP

ora12c@proddb1:/ogg/ora12c$ netstat -an | grep 7809

      *.7809               *.*                  0      0  256000      0 LISTEN

      *.7809                            *.*                               0      0  256000      0 LISTEN

Yes it is open.

Regards,

Joe

The 3 scan ip (21,22 and 23) can be distributed on any of the 2 rac nodes at any given time (17 and 18)

  Currently I note that 22 and 23 are on node 17 and scan ip 21 is on node 18

On node 17 port 7809 is up (netstat -a|grep 7809) and on node 18 port 7809 is not up.

Hence when the scan name proddb-scan hits 21 GG won't work.

How do I start GG services on node 2 (21)?

MGR param file:

PORT 7809

DYNAMICPORTLIST 20000-20099

PURGEOLDEXTRACTS ./dirdat/aa* , USECHECKPOINTS, MINKEEPHOURS 72

PURGEOLDEXTRACTS ./dirdat/cb*, USECHECKPOINTS, MINKEEPHOURS 72

AUTORESTART ER *, RETRIES 3, WAITMINUTES 10, RESETMINUTES 60

DOWNREPORTMINUTES 15

--DOWNCRITICAL

LAGCRITICALSECONDS 10

LAGINFOMINUTES 0

LAGREPORTMINUTES 15

pump PARAM:

EXTRACT PXDWN

USERIDALIAS oraggext

RMTHOST 10.215.227.17, MGRPORT 7809

RMTHOST 10.215.227.18, MGRPORT 7809

RMTHOST 10.215.227.21, MGRPORT 7809

RMTHOST 10.215.227.22, MGRPORT 7809

RMTHOST 10.215.227.23, MGRPORT 7809

RMTTRAIL /ogg/ora12c/dirdat/cd

--RMTTRAIL /data1/oggdwn/dirdat/SOURCE/lt

PASSTHRU

TABLE CBS_CORE.CB_INSTALLMENT;

TABLE CBS_CORE.test;

TABLE CBS_CORE.CB_INSTALLMENT_DTLS;

TABLE CBS_CORE.cb_serv_installment_dtls;

TABLE CBS_CORE.cb_subs_deposits;

TABLE CBS_CORE.cb_bill_cycle;

TABLE CBS_CORE.cb_order_request_dtls;

TABLE  CBS_CORE.CB_SCHEME_REFERENCE;

TABLE  CBS_CORE.CB_CANCEL_RECEIPTS;

TABLE  CBS_CORE.FXL_SERVICE_MAST;

Regards,

Joe