ORA-25194: invalid COMPRESS prefix length value

Cause : The psecifeid vaule muts be aposiitve itnegerl ess htan teh numebr ofk ey cloumns

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

Specfiy ana pprorpiatev alue.

update : 28-07-2017
ORA-25194

ORA-25194 - invalid COMPRESS prefix length value
ORA-25194 - invalid COMPRESS prefix length value

  • ora-24090 : at least one protocol must be enabled
  • ora-36399 : (XSSPROPDTYPE) The data type of property string must be string.
  • ora-24383 : Overflow segment of an IOT cannot be described
  • ora-29706 : incorrect value string for parameter ACTIVE_INSTANCE_COUNT
  • ora-30509 : client logoff triggers cannot have AFTER type
  • ora-28606 : block too fragmented to build bitmap index (string,string)
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • ora-38702 : Cannot update flashback database log file header.
  • ora-19017 : Attributes can only be simple scalars
  • ora-00033 : current session has empty migration password
  • ora-10997 : another startup/shutdown operation of this instance inprogress
  • ora-02256 : number of referencing columns must match referenced columns
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-16612 : string value too long for attribute "string"
  • ora-08440 : raw buffer is too short to hold converted data
  • ora-17501 : logical block size string is invalid
  • ora-26748 : The one-to-one transformation function string encountered the following error: string
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-01679 : database must be mounted EXCLUSIVE and not open to activate
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-29395 : cannot set the initial consumer group to string
  • ora-31642 : the following SQL statement fails: string
  • ora-27213 : failed to unload Media Management Library
  • ora-01222 : MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
  • ora-25247 : %s is not a recipient of specified message
  • ora-31401 : change source string is not an existing change source
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • 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.