Answer / guest

Cause: The precompiler expected to find a statement
terminator at the end of an EXEC statement but found
something else. This can happen if tabs were embedded in the
source code (because the precompiler has no way of knowing
how many spaces a tab represents).

Action: If tabs are embedded in the source ocde, replace
them with spaces. Check the statement syntax and check that
each EXEC statement has a terminator. For embedded CREATE
{FUNCTION | PROCEDURE | PACKAGE} statements and for embedded
PL/SQL blocks, check that the statement terminator is END-EXEC.

Please add more information about this Error

NNL-00891: Corrupted messages received: number

1 Answers  

---

ORA-06440: ssaio: the asynchronous read returned incorrect number of bytes

1 Answers  

---

ORA-22618: attribute is a BAD NULL in the image handle

1 Answers  

---

ORA-01688: unable to extend table string.string partition string by string in tablespace string

1 Answers  

---

ORA-12043: invalid CREATE MATERIALIZED VIEW option

1 Answers  

---

TNS-01301: TNS error structure:

1 Answers  

---

ORA-36666: (XSDPART04) workspace object is not a concat dimension.

1 Answers  

---

SQL-02129: Fetched number of bytes is odd.

1 Answers  

---

NNO-00107: line string: ignoring stale checkpoint data

1 Answers  

---

SQL*Loader-00820: cannot create where clause with range for table string

1 Answers  

---

NZE-29243: the toolkit does not recognize the type of key being used

1 Answers  

---

ORA-12985: tablespace 'string' is read only, cannot drop column

1 Answers  

---