ORA-16642: db_unique_name mismatch
- 1 Answers
- 6812 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The expected db_unique_name value did not match the
actual db_unique_name value for the database that the broker
contacted using the connect identifier that was associated
with that database.
Action: Verify that the connect identifier correctly
connects to the intended database. Verify that the name of
the database that the broker expects to find via that
connect identifier matches the actual db_unique_name for
that database.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-00319: log string of thread string has incorrect log reset status
ORA-13237: internal error during R-tree concurrent updates: [string]
PROT-00303: Dump file already exists
ORA-08434: raw data has invalid trailing sign
ORA-39959: invalid warning number (string)
TNS-12228: TNS:protocol adapter not loadable
SQL*Loader-00501: Unable to read file (string)
ORA-07645: sszfsl: $CHANGE_CLASS failure
NZE-28780: invalid data access method specified by the parameter
ORA-16107: all log data from primary has been processed
ORA-16629: Database reports a different protection level from the protection mode.
ORA-16792: Some configurable property value is inconsistent with the database setting.
Oracle Errors 
