Answer Posted / guest

Cause: An Oracle extension to the ANSI/ISO SQL standard was
used. Specifically, the parameter RELEASE was used in a
COMMIT or ROLLBACK statement. For example, the offending
code might look like: EXEC SQL ROLLBACK RELEASE; This
informational message is issued by the FIPS Flagger when
FIPS=YES.

Action: No action required. However, for ANSI/ISO
compliance, do not use the parameter RELEASE;

Please add more information about this Error

IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1605

---

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

3963

---

ORA-26029: index string.string partition string initially in unusable state

2140

---

RMAN-05017: no copy of datafile number found to recover

2399

---

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

1926

---

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

1732

---

ORA-26082: load of overlapping segments on table string.string is not allowed

1755

---

when i ran any workflow or session, getting below error: seesion task instance[s_xxx]: Execution terminated unexpecterdly

2217

---

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

8802

---

ORA-26094: stream format error: input column overflow

2785

---

ORA-26095: unprocessed stream data exists

3548

---

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

2720

---

ORA-26079: file "string" is not part of table string.string

1934

---

In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2862

---

[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

2707

---