Those are connection messages. Normally those are they coming from data
guard broker? Were you able to set up the dataguard and get it working
before trying to enable broker? I have seen that a few times when deep
packet inspection and some other paranoid level firewall settings were
enabled. As I recall, it was deep packet inspection between the primary
and standby sites, and all port numbers including the high ports where
connections are typically handed off to, were blocked unless specifically
opened. So, while 1521 was open, when the listener tried to hand off the
connection to a random high port number, that connection was blocked.
On Mon, Dec 17, 2018 at 10:42 AM Seth Miller <sethmiller.sm@xxxxxxxxx>
wrote:
Scott,
There are lots of reasons you might be getting these errors so the error
numbers alone are not nearly enough information. If you would like help
from this list, you will need to provide very detailed information about
your environment and what you have done so far. Think of this community as
MOS, except more useful and literate.
Seth
On Mon, Dec 17, 2018 at 10:22 AM Scott Canaan <srcdco@xxxxxxx> wrote:
I am trying to do a data guard creation via Enterprise Manager. It
restores everything via RMAN correctly, but can’t create the data guard.
I am getting an ORA-16664 and ORA-16665, but I can’t figure out what is
causing them.
This is Oracle 12.1.0.2.
Unfortunately, I’m under the gun time-wise.
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
