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-04-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-30103 : 'string' contains an illegal integer radix for 'string'
  • ora-26027 : unique index string.string partition string initially in unusable state
  • ora-00129 : listener address validation failed 'string'
  • ora-13638 : The user interrupted the current operation.
  • ora-00741 : logfile size of (string) blocks exceeds maximum logfile size
  • ora-23540 : Redefinition not defined or initiated
  • ora-06112 : NETTCP: invalid buffer size
  • ora-36272 : (XSCGMDLAGG04) 'workspace object' is not a valid operator for the AGGREGATION function.
  • ora-27073 : Trying to close a file which has async I/Os pending to be dequeued
  • ora-07841 : sllfop: SYS$OPEN failure
  • ora-31655 : no data or metadata objects selected for job
  • ora-13639 : The current operation was interrupted because it timed out.
  • ora-01532 : cannot create database; instance being started elsewhere
  • ora-39112 : Dependent object type string skipped, base object type string creation failed
  • ora-00233 : copy control file is corrupt or unreadable
  • ora-29873 : warning in the execution of ODCIINDEXDROP routine
  • ora-12690 : Server Authentication failed, login cancelled
  • ora-01977 : Missing thread number
  • ora-33074 : (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object.
  • ora-01719 : outer join operator (+) not allowed in operand of OR or IN
  • ora-13187 : subdivision failed
  • ora-13386 : commit/rollback operation error: [string]
  • ora-15077 : could not locate ASM instance serving a required diskgroup
  • ora-27021 : sequential file handle must be specified
  • ora-12922 : concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
  • ora-29816 : object being disassociated is not present
  • ora-01638 : parameter string does not allow ORACLE version string to mount cluster database
  • ora-24009 : invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
  • ora-32612 : invalid use of FOR loop
  • ora-13640 : The current operation was cancelled because it timed out, and was not in interruptible mode.
  • 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.