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 : 23-09-2017

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

  • ora-09976 : skxfqdini: Error Creating Port
  • ora-07275 : unable to send signal to process
  • ora-01489 : result of string concatenation is too long
  • ora-09943 : Allocation of memory for password list component failed.
  • ora-12656 : Cryptographic checksum mismatch
  • ora-17502 : ksfdcre:string Failed to create file string
  • ora-28501 : communication error on heterogeneous database link
  • ora-27059 : could not reduce file size
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-28029 : could not authorize remote server for user string
  • ora-01686 : max # files (string) reached for the tablespace string
  • ora-25218 : enqueue failed, delay must be zero for queue string.string
  • ora-01179 : file string does not exist
  • ora-16110 : user procedure processing of logical standby apply DDL
  • ora-16037 : user requested cancel of managed recovery operation
  • ora-00360 : not a logfile member: string
  • ora-22813 : operand value exceeds system limits
  • ora-32810 : foreign queue string is not registered
  • ora-10973 : backout evet for 2619509
  • ora-16002 : database already open for read-write access by another instance
  • ora-24388 : Unsupported functionality in fast path mode
  • ora-33072 : (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension.
  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-25503 : cannot open database because the database is being quiesced
  • ora-12209 : TNS:encountered uninitialized global
  • ora-01352 : tablespace given for Logminer spill does not exist
  • ora-12022 : materialized view log on "string"."string" already has rowid
  • 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.