ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition

Cause : Specfiyinga STOER-IN lcaused urin gCREAET/ALTRE of aRang,e ComopsiteR angeL ist aprtitoined atble hwich si nota llowde"

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

Re-issue teh staemnt atfer rmeovin gthe TSORE-NI clasue

update : 26-09-2017
ORA-14641

ORA-14641 - STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
ORA-14641 - STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition

  • ora-06766 : TLI Driver: close failed during release
  • ora-26748 : The one-to-one transformation function string encountered the following error: string
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-12722 : regular expression internal error
  • ora-01232 : cannot start online backup - file string is being made read-only
  • ora-22308 : operation not allowed on evolved type
  • ora-13016 : specified topology [string] is invalid
  • ora-27121 : unable to determine size of shared memory segment
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-25104 : UNRECOVERABLE option can only be used with ALTER INDEX REBUILD
  • ora-19704 : file name exceeds maximum length of string
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • ora-40283 : missing cost matrix
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-23493 : "string" is not a new site for extension request "string"
  • ora-24092 : invalid value string specified
  • ora-24757 : duplicate transaction identifier
  • ora-12569 : TNS:packet checksum failure
  • ora-30370 : set operators are not supported in this context
  • ora-23317 : a communication failure has occurred
  • ora-08340 : This command not allowed on nCUBE, only one thread is ever used.
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-00091 : LARGE_POOL_SIZE must be at least string
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-12632 : Role fetch failed
  • ora-08106 : cannot create journal table string.string
  • ora-01920 : user name 'string' conflicts with another user or role name
  • ora-12431 : invalid audit action
  • 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.