Answer / guest

Cause: SQLCHECK=NONE was specified on the command line but
is no longer a supported option. SQLCHECK=SYNTAX was used
instead.

Action: This is a warning message only. To avoid this
warning, specify SQLCHECK=SYNTAX or SQLCHECK=SEMANTICS.

Please add more information about this Error

NNF-04003: Entry in inputfile is too long

1 Answers  

---

NZE-28804: Data source cannot close.

1 Answers  

---

ORA-13856: Service name must be specified

1 Answers  

---

ORA-14624: DEFAULT subpartition must be last subpartition specified

1 Answers  

---

LPX-00664: VM Node-Stack overflow.

1 Answers  

---

ORA-38715: Invalid log number specified in the DUMP FLASHBACK command.

1 Answers  

---

[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

0 Answers   HCL,

---

ORA-22605: FDO handle [string] is not initialized

1 Answers  

---

ORA-01628: max # extents (string) reached for rollback segment string

1 Answers  

---

ORA-00405: compatibility type "string"

1 Answers  

---

ORA-02396: exceeded maximum idle time, please connect again

1 Answers  

---

TNS-12620: TNS:requested characteristic not available

1 Answers  

---