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 : 25-04-2017
ORA-28601

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

  • ora-31231 : DBMS_LDAP: invalid PROPERTY_SET
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-23340 : incorrect resolution method string
  • ora-10852 : Enable tracing for Enqueue Dequeue Operations
  • ora-30085 : syntax error was found in overlaps predicate
  • ora-31085 : schema "string" already registered
  • ora-00273 : media recovery of direct load data that was not logged
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-02750 : osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf
  • ora-26679 : operation not allowed on LOB or LONG columns in LCR
  • ora-24750 : incorrect size of attribute
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-30078 : partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
  • ora-12222 : TNS:no support is available for the protocol indicated
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-16519 : the resource handle is invalid
  • ora-27022 : skgfqsbi: could not allocate memory for media manager
  • ora-19260 : XQ0040 - invalid namespace node in element constructor
  • ora-08274 : Out of memory for environment variable
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-06541 : PL/SQL: compilation error - compilation aborted
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-25142 : default storage clause specified twice
  • ora-25260 : AQ latch cleanup testing event
  • ora-28237 : seed length too short
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-26669 : parameter string inconsistent with parameter string
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-25253 : listen failed, queue string.string is not enabled for dequeue
  • ora-24774 : cannot switch to specified transaction
  • 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.