Answer / guest

Cause: Poorly formed network configuration data. For
example, a PREFERRED_CMANAGERS entry may have an incorrect
CMANAGER_NAME in the client's TNSNAV.ORA file. Or an
Interchange downtime parameter (TIMEOUT_INTERVAL) on the
Navigator may be set to zero in INTCHG.ORA.

Action: Check the entries in TNSNAV.ORA and the Interchange
configuration files and correct them. If necessary, talk
with your network administrator to determine if the
specified Interchanges (Connection Managers) are available
and properly configured. Use the Oracle Network Manager to
generate the configuration files if necessary.

Please add more information about this Error

ORA-28605: bitmap indexes cannot be reversed

1 Answers  

---

PCC-02391: Runtime context variable not of correct type

1 Answers  

---

ORA-27060: could not set close-on-exec bit on file

1 Answers  

---

NZE-28797: invalid key data type

1 Answers  

---

ORA-36958: (XSFCAST26) The OFFSET value for cycle number cannot be greater than the cycle's PERIODICITY, which is number. You specified number.

1 Answers  

---

ORA-16746: Resource guard encountered error during database mount

1 Answers  

---

ORA-12502: TNS:listener received no CONNECT_DATA from client

1 Answers  

---

ORA-07704: error in archive text: need ':' after device name

1 Answers  

---

DRG-11840: Not Implemented

1 Answers  

---

PLS-00601: partition extended object names may only be used with tables

1 Answers  

---

DRG-11212: procedure filter procedure name contains a semicolon

1 Answers  

---

ORA-26091: requested direct path operation not supported

1 Answers  

---