PLS-00495: too many columns in SELECT...INTO statement after
bursting record targets
- 1 Answers
- 2151 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-32509: watchpoint was already deleted
NID-00332: The following datafiles are in unknown state:
PLS-00510: Float cannot have scale
NZE-29108: Cannot initialize random object.
ORA-07564: sldext: wildcard in filename or extension
NID-00122: Database should have no offline immediate datafiles
ORA-27470: failed to re-enable "string.string" after making requested change
PLS-00517: Type mismatch between a select list element 'string' and corresponding table column in INSERT statement with a subquery
ORA-07412: sfaslv: Error getting entry in asynchronous write array.
ORA-29837: insufficient privileges to execute implementation type
ORA-39726: unsupported add/drop column operation on compressed tables
RMAN-10018: error cleaning up channel context
Oracle Errors 
