ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.

Cause : User attemptedt o defien a RANEG or LITS partiiton temlpate wiht more htan onep artitino dimenison.

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

Removea ll buto ne of hte dimesnions form the APRTITIO NBY RANEG(...) ro PARTIITON BY ILST(... )clauseo f the aprtitio ntemplaet defintiion.

update : 24-08-2017
ORA-36672

ORA-36672 - (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
ORA-36672 - (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.

  • ora-31158 : schema "string" currently being referenced
  • ora-28115 : policy with check option violation
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-00324 : log file 'string' translated name 'string' too long, string characters exceeds string limit
  • ora-29393 : user string does not exist or is not logged on
  • ora-33094 : (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.
  • ora-38403 : attribute set name may not be longer than 22 characters
  • ora-07215 : slsget: getrusage error.
  • ora-30041 : Cannot grant quota on the tablespace
  • ora-01156 : recovery in progress may need access to files
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-01952 : system privileges not granted to 'string'
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-30188 : reserved for future use
  • ora-30340 : illegal dimension name
  • ora-00721 : changes by release string cannot be used by release string
  • ora-13842 : no SELECT privilege on DBA_SQL_PROFILES
  • ora-01704 : string literal too long
  • ora-16115 : %s\% of LogMiner dictionary loading is done
  • ora-28273 : No mapping for user nickname to LDAP distinguished name exists.
  • ora-28022 : cannot grant external roles to global user or role
  • ora-16717 : clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
  • ora-28109 : the number of related policies has exceeded the limit of 16
  • ora-01613 : instance string (thread string) only has string logs - at least 2 logs required to enable.
  • ora-19693 : backup piece string already included
  • ora-19809 : limit exceeded for recovery files
  • ora-39068 : invalid master table data in row with PROCESS_ORDER=string
  • ora-08186 : invalid timestamp specified
  • ora-31412 : change set string is disabled and cannot be advanced
  • ora-00316 : log string of thread string, type string in header is not log file
  • 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.