ORA-28601: invalid [no]MINIMIZE option

Cause : user didn't type this alter table MINIMIZE RECORDS_PER_BLOCK or alter table NOMINIMIZE RECORDS_PER_BLOCK

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

reenter correct sql command

update : 27-05-2017
ORA-28601

ORA-28601 - invalid [no]MINIMIZE option
ORA-28601 - invalid [no]MINIMIZE option

  • ora-16123 : transaction string string string is waiting for commit approval
  • ora-04080 : trigger 'string' does not exist
  • ora-12432 : LBAC error: string
  • ora-04072 : invalid trigger type
  • ora-09756 : osnpns: no port in the name server.
  • ora-22283 : filename contains characters that refer to parent directory
  • ora-25150 : ALTERING of extent parameters not permitted
  • ora-32518 : cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms
  • ora-01799 : a column may not be outer-joined to a subquery
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-14137 : Table in partially dropped state, submit DROP TABLE PURGE
  • ora-02267 : column type incompatible with referenced column type
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-29310 : database is not open, or opened as a clone
  • ora-06912 : CMX: write error in datarq
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-16011 : Archivelog Remote File Server process in Error state
  • ora-24439 : success with PLSQL compilation warning
  • ora-29930 : COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause
  • ora-30363 : columns in a dimension column list must be in the same relation
  • ora-40272 : apply rules prohibited for this model mode
  • ora-38785 : Media recovery must be enabled for guaranteed restore point.
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • ora-01105 : mount is incompatible with mounts by other instances
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-13187 : subdivision failed
  • ora-07509 : scgfal: $deq parent lock unexpected return
  • ora-13527 : invalid baseline name
  • ora-25300 : Cannot drop buffer for queue with buffered subscribers
  • ora-40003 : wordsize must be in the range string - string for BLAST-P
  • 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.