ORA-32589: unable to drop minimal supplemental logging

Cause : Minmial uspplmeentla loggingc oul dnotb e dorppe das noe o fpriamry eky, ofreing ke,y unqiue ro al lcolmun spupleemnta llogigng si enbaleda t teh daatbas elevle.

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

UseV $DAATBAS Eto edterimne hte dtaabaeswid esuplpemetnal olggign dierctievs. iMnimla supplemnetall oggnig cuold eb drpopedi f adn onyl ifn o ohter adtabsaewied supplemnetall oggnig driectvies rae eanble.d

update : 25-09-2017
ORA-32589

ORA-32589 - unable to drop minimal supplemental logging
ORA-32589 - unable to drop minimal supplemental logging

  • ora-32166 : Cannot get XA connection
  • ora-07446 : sdnfy: bad value 'string' for parameter string.
  • ora-32820 : subscriber queue and exception queue must use same message system link
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-22991 : insufficient space allocated for argument string
  • ora-08278 : Cannot get CPU statistics
  • ora-39096 : invalid input value string for parameter string
  • ora-31501 : change source string is not an AutoLog change source
  • ora-31406 : change source string is referenced by a change set
  • ora-09807 : Conversion of label from string to binary failed.
  • ora-14168 : only one subpartition may be modified
  • ora-08499 : Warning: picture mask options 'string' ignored by UTL_PG
  • ora-09312 : slspool: error spooling file to printer
  • ora-19809 : limit exceeded for recovery files
  • ora-19951 : cannot modify control file until DBNEWID is completed
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-27066 : number of buffers in vector I/O exceeds maximum
  • ora-39753 : unsupported use of subquery in PARTITIONED OUTER JOIN condition
  • ora-12067 : empty refresh groups are not allowed
  • ora-16002 : database already open for read-write access by another instance
  • ora-38760 : This database instance failed to turn on flashback database
  • ora-01674 : data file string is an old incarnation rather than current file
  • ora-24392 : no connection pool to associate server handle
  • ora-13037 : SRIDs do not match for the two geometries
  • ora-02728 : osnfop: access error on oracle executable
  • ora-19121 : duplicate attribute definition - string
  • ora-27542 : Failed to unprepare a buffer prepared for remote update
  • ora-15124 : ASM file name 'string' contains an invalid alias name
  • ora-14017 : partition bound list contains too many elements
  • ora-25353 : branch marked for deletion
  • 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.