OGG-01031 There is a problem in network communication

During starting up a new Pump Extract in Oracle GoldenGate 12c Release 2, I came through the following error that ABEND the pump extract at source database server.


ERROR   OGG-01031  There is a problem in network communication, a remote file problem, encryption keys f
or target and source do not match (if using ENCRYPT) or an unknown error. (Reply received is Output file /u01/ogg_12c/rmttrai
l/em000000 is not in any allowed output directories.).

GGSCI (prodsrv) 1> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING                                           
EXTRACT     RUNNING     EXEMP       00:00:00      00:00:01    
EXTRACT     ABENDED     PEMP        00:00:00      00:24:10    










Cause : In Oracle GoldenGate 12c Release 2, by default, Pump extract try to push the EXTRACT TRAIL logs from source Database server to target database server to the default directory(i.e. ./dirdat) but in our case we are using the custom directory(/u01/ogg_12c/rmttrail) to store the remote trail files on the target server.


From OGG Error log at target server.

2017-10-30 21:06:16  INFO    OGG-01226  Oracle GoldenGate Collector for Oracle:  Socket buffer size set to 187200 (flush size 27985).
2017-10-30 21:06:16  WARNING OGG-01223  Oracle GoldenGate Collector for Oracle:  Output file /u01/ogg_12c/rmttrail/em000000 is not in any allowed output directories.
2017-10-30 21:06:16  INFO    OGG-01971  Oracle GoldenGate Collector for Oracle:  The previous message, 'WARNING OGG-01223', repeated 1 times.
2017-10-30 21:06:16  INFO    OGG-01676  Oracle GoldenGate Collector for Oracle:  Terminating after client disconnect.

Pump Extract Parameter file at source:

GGSCI (prodsrv) 15> view param pemp

EXTRACT PEMP
RMTHOST drsrv, mgrport 7809, timeout 30
RMTTRAIL /u01/ogg_12c/rmttrail/em
PASSTHRU
TABLE scott.emp;







Solutions: Go to the target Oracle GoldenGate server and add the following parameter(ALLOWOUTPUTDIR )in the ./GLOBALS parameter file to solve this problem.

GGSCI (DRsrv) 8> view param ./GLOBALS

GGSCHEMA ogg
ALLOWOUTPUTDIR /u01/ogg_12c/rmttrail


GGSCI (DRsrv) 9> 




Subsequently start the pump extract at source and it would move forward.

GGSCI (prodsrv) 16> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING                                           
EXTRACT     RUNNING     EXEMP       00:00:00      00:00:04    
EXTRACT     RUNNING     PEMP        00:00:00      00:00:03    







Happy Learning....!!