Answer Posted / guest

Cause: The destination defined in the INIT.ORA file has the
wrong syntax, and the Data Guard broker failed to update the
destination when the log transport is turned on.

Action: Fix the syntax error in the INIT.ORA file or remove
the entry from the INIT.ORA file. Check for correct syntax
for the log transport related properties.

Please add more information about this Error

IMP-00070: Lob definitions in dump file are inconsistent with database.

1796

---

IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2782

---

NZE-28890: Entrust Login Failed

1918

---

ORA-26030: index string.string had string partitions made unusable due to:

1986

---

ORA-26095: unprocessed stream data exists

3636

---

ORA-26084: direct path context already finished

1994

---

ORA-16626: failed to enable specified object

2272

---

[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table

2772

---

ORA-16516: The current state is invalid for the attempted operation.

8873

---

ORA-26027: unique index string.string partition string initially in unusable state

6789

---

IMP-00064: Definition of LOB was truncated by export

6465

---

if the lengths of two wires are same and the area of cross sections is 4:7 then what will be the ratio of current passing through these wires

2751

---

ORA-16627: No standby databases support the overall protection mode.

4036

---

ORA-26032: index string.string loading aborted after string keys

2176

---

ORA-26028: index string.string initially in unusable state

3910

---