ORA-60471 Occurs When Changing The Value Of MAX_COLUMNS From EXTENDED To STANDARD (23ai And Later)
(Doc ID 3070058.1)
Last updated on FEBRUARY 03, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 23.4 and laterOracle Database - Standard Edition - Version 23.4 and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Information in this document applies to any platform.
Symptoms
In order to change the value of MAX_COLUMNS from EXTENDED to the default value of STANDARD, all tables with more than 1000 columns that had been created on the database were dropped.
However, even after dropping all of those tables, attempting to change the value of MAX_COLUMNS to STANDARD results in ORA-60471.
Changes
Dropped all tables with more than 1000 columns and then tried to change the value to MAX_COLUMNS=STANDARD.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |