PLS-00496: too few columns in SELECT...INTO statement after
bursting record targets
- 1 Answers
- 2634 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
columns to fill all of the fields in the record.
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-32805: identifier for string too long, maximum length is string characters
ORA-33004: (XSAGDNGL01) workspace object is not a relationship array.
ORA-01204: file number is string rather than string - wrong file
ORA-31464: target table for the change table no longer exists
NNL-01000: SERVER FAILURE responses received: number
NCR-01009: NCRS: Record handling error.
RMAN-06142: DEVICE TYPE cannot be specified with this command
ORA-28591: agent control utility: unable to access parameter file
ORA-29324: SET COMPATIBILITY release string format is wrong
ORA-00375: unable to get default db_block_size
ORA-06517: PL/SQL: Probe error - string
ORA-13770: Baseline "string" does not exist.
Oracle Errors 
