ORA-14165: MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations

Cause : ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (e.g. ADD PARTITION or PCTFREE) which is illegal

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

Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will

update : 29-06-2017
ORA-14165

ORA-14165 - MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
ORA-14165 - MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations

  • ora-07565 : sldext: $SEARCH failure
  • ora-09880 : sstasfre/sstasdel: shmdt error, unable to detach tas write page
  • ora-19024 : Cursor expression must be named
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-26737 : version string already has an export dump file
  • ora-28279 : Error reading ldap_directory_access init parameter.
  • ora-00028 : your session has been killed
  • ora-16778 : redo transport error for one or more databases
  • ora-00361 : cannot remove last log member string for group string
  • ora-38795 : warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
  • ora-07823 : sspsqr: $QIO failure
  • ora-32585 : duplicate specification of a supplemental log attribute
  • ora-02238 : filename lists have different numbers of files
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-29963 : missing BINDING keyword
  • ora-23397 : global name "string" does not match database link name "string"
  • ora-29251 : Index1 is greater than Index2 in call to dbms_sql.bind_array
  • ora-00310 : archived log contains sequence string; sequence string required
  • ora-17509 : Attempt to do i/o beyond block1 offset
  • ora-29534 : referenced object string.string could not be resolved
  • ora-07705 : sksaprs: device name buffer too small
  • ora-22323 : error table "string"."string" does not exist
  • ora-32639 : Aggregate functions on reference MODELs are not allowed
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-19017 : Attributes can only be simple scalars
  • ora-13480 : the Source Type is not supported
  • ora-28366 : invalid database encryption operation
  • ora-07597 : spguns: $GETJPIW failure
  • ora-14083 : cannot drop the only partition of a partitioned table
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • 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.