Answer / guest

Cause: The Data Guard NetSlave process detected a connection
failure to a remote database in the broker configuration.
This failure happened in the middle of a transmission
session. A transmission session usually requires more than
one send operation for sending a large amount of data (e.g.
the broker configuration file) to the remote database. This
error implies the transmission has to be re-started from the
beginning.

Action: In most cases, no user action is required. The Data
Guard broker always tries to re-send the data from the
beginning. If the problem persists, the user will eventually
see this error reported. This will indicate there are some
problems with the network connection between broker managed
databases. Further network troubleshooting should be done to
identify and address the actual problem.

Please add more information about this Error

ORA-31655: no data or metadata objects selected for job

1 Answers  

---

ORA-36342: (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]

1 Answers  

---

RMAN-06598: conversion between platforms 'string' and 'string' is not needed

1 Answers  

---

ORA-31202: DBMS_LDAP: LDAP client/server error: string

1 Answers  

---

ORA-24001: cannot create QUEUE_TABLE, string already exists

1 Answers  

---

ORA-16525: the Data Guard broker is not yet available

2 Answers  

---

PCC-00080: TYPE identifier already TYPEd

1 Answers  

---

ORA-23540: Redefinition not defined or initiated

1 Answers  

---

ORA-14109: partition-extended object names may only be used with tables

1 Answers  

---

NNL-00907: NOT ALLOWED responses sent: number

1 Answers  

---

PCC-02106: Userid only used when SQLCHECK = FULL, userid ignored.

1 Answers  

---

ORA-36608: (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow.

1 Answers  

---