PLS-00495: too many columns in SELECT...INTO statement after
bursting record targets
- 1 Answers
- 2414 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 |
TNS-12683: encryption/crypto-checksumming: no Diffie-Hellman seed
ORA-19765: mount id string does not match mount id string in control file
UDI-00011: parameter string is incompatible with parameter string
NNL-00251: DEFAULT-FORWARDER-ONLY mode is now enabled
PLS-00516: Type mismatch between object table and value 'string' in INSERT statement.
ORA-26048: Scoped REF column has wrong table name.
CLSR-06502: Failed to connect to database
ORA-24090: at least one protocol must be enabled
NNL-00231: Controller NOCONFIRM mode is now string
DRG-11839: Internal Server Error
RMAN-06013: duplicate channel identifier found: string
ORA-04093: references to columns of type LONG are not allowed in triggers
Oracle Errors 
