PLS-00495: too many columns in SELECT...INTO statement after
bursting record targets
- 1 Answers
- 2144 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Type checking indicated the columns in a SELECT or
FETCH were being collected into a record in the INTO list.
The record was burst into its fields. There were not enough
fields in the record for each of the columns.
Action: Change the number of columns or the record
variable(s) in the INTO clause so that they match.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-19605: input filename must be specified
NID-00407: Reversion of database ID failed.
RMAN-06005: connected to target database: string (DBID=string)
TNS-01096: %s * string * string * string * string * number
ORA-30739: cannot drop a table that has subtables
LFI-00134: Unable to protect a file for an append operation.
QSM-01034: materialized view, string, needs a dimension level to join table, string
ORA-01108: file string is in backup or media recovery
ORA-01194: file string needs more recovery to be consistent
ORA-12516: TNS:listener could not find available handler with matching protocol stack
ORA-31662: metadata transform name can not be defaulted
ORA-14078: you may not drop the highest partition of a GLOBAL index
Oracle Errors 
