Answer / guest

Cause: The size of a table variable in an INTO/USING clause
of a dynamic EXECUTE statement has been ARRAYLEN...EXECUTE'd
while the other host variable has not and is not a table of
dimension 1 or a plain non-table host variable. Example: 01
X PIC X(10) OCCURS 10. 01 Y PIC S9(4) COMP OCCURS 10. 01 Z
PIC S9(4) COMP. ... EXEC SQL ARRAYLEN X (DIM) EXECUTE
END-EXEC. ... EXEC SQL EXECUTE S1 USING :X, :Y END-EXEC. <--
error EXEC SQL EXECUTE S1 USING :X, :Z END-EXEC. <-- ok
Please note that this error differs from 233 in that it is
an ERROR not a WARNING.

Action: ARRAYLEN...EXECUTE all of the table variables in the
INTO/USING clause or those host variables not
ARRAYLEN...EXECUTEd need to be of dimension 1.

Please add more information about this Error

ORA-16811: apply instance not recorded by the Data Guard broker

1 Answers  

---

ORA-16953: Type of SQL statement not supported.

1 Answers  

---

SQL*Loader-00458: Comparison text ('string') of CONTINUEIF LAST must be non-whitespace

1 Answers  

---

ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string

1 Answers  

---

ORA-33058: (XSAGDNGL28) In AGGMAP workspace object, error code string is greater than the maximum error code of number.

1 Answers  

---

RMAN-06717: number of source files (string) and destination files (string) does not match

1 Answers  

---

ORA-31020: The operation is not allowed, Reason: string

1 Answers  

---

ORA-16023: system string destination cannot be the same as session string destination

1 Answers  

---

ORA-16038: log string sequence# string cannot be archived

4 Answers  

---

QSM-00775: the specified SQL statement cannot be stored in the workload due to invalid table references

1 Answers  

---

ORA-16083: LogMiner session has not been created

1 Answers  

---

ORA-30337: multiple JOIN KEY clauses specified for the same parent level

1 Answers  

---