ORA-10662: Segment has long columns

Cause : Shirnkw asi sseud no as egemntw it hlogn cloumsn. hTisi s ont uspprote.d

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts


update : 26-06-2017

ORA-10662 - Segment has long columns
ORA-10662 - Segment has long columns

  • ora-15198 : operation string is not yet available
  • ora-01874 : time zone hour must be between -12 and 14
  • ora-13264 : geometry identifier column string does not exist in table string
  • ora-02292 : integrity constraint (string.string) violated - child record found
  • ora-13497 : %s
  • ora-36696 : (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
  • ora-31420 : unable to submit the purge job
  • ora-01036 : illegal variable name/number
  • ora-24350 : OCI call not allowed
  • ora-00264 : no recovery required
  • ora-01875 : time zone minute must be between -59 and 59
  • ora-19661 : datafile string could not be verified
  • ora-14137 : Table in partially dropped state, submit DROP TABLE PURGE
  • ora-08113 : composite partition index may not be compressed
  • ora-32051 : mapping service not available
  • ora-16804 : one or more configuration properties in metadata have invalid values
  • ora-29360 : retry operation. Too much concurrent activity
  • ora-00333 : redo log read error block string count string
  • ora-13221 : unknown geometry type in the geometry object
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-26521 : rpc initialization error
  • ora-23364 : Feature not enabled: Advanced replication
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-12481 : effective label not within program unit clearance range
  • ora-25107 : duplicate TABLESPACE option specification
  • ora-31193 : This versioning feature isn't supported for resource string
  • ora-25109 : standby lock name space has illegal character 'string'
  • ora-38792 : encountered unknown flashback record from release string
  • ora-16134 : invalid MANAGED recovery FINISH option
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.