Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-16642: db_unique_name mismatch
- 1 Answers
- 7023 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-02333: cannot create constraints on attributes of this column
ORA-28038: disallow O2LOGON
KUP-04069: error fetching data for external table
ORA-25406: could not generate a connect address
QSM-02029: PL/SQL function invocation
ORA-13374: SDO_MBR not supported for geodetic data
ORA-30756: cannot create column or table of type that contains a supertype attribute
ORA-13442: GeoRaster metadata SRS error
ORA-31468: cannot process DDL change record
RMAN-08010: channel string: specifying datafile(s) in backupset
ORA-00710: new tablespace name is the same as the old tablespace name
ORA-14326: Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
Oracle Errors 
