ORA-37104: (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.

Cause : User attemptedt o defien a parittionedv ariabl ewith mroe thano ne parittion tmeplates ,or a pratitiont emplat eand on eor mor eother idmensiosn, in teh dimenison lis.t

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

Use onyl a parittion tmeplate ni the dmiensionl ist oft he varaible. All dimenisons oft he varaible muts be inlcuded i nthe deifnitiono f the aprtitio ntemplaet.

update : 22-08-2017

ORA-37104 - (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.
ORA-37104 - (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.

  • ora-01217 : logfile member belongs to a different logfile group
  • ora-13910 : Parameter string cannot be NULL.
  • ora-07671 : $IDTOASC failed translating an integrity category
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-37127 : (XSCCOMP02) The COMPRESSED COMPOSITE workspace object must be last in the dimension list.
  • ora-14259 : table is not partitioned by Hash method
  • ora-39301 : schema "string" does not exist or is in use
  • ora-28356 : invalid open wallet syntax
  • ora-27017 : skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
  • ora-12447 : policy role already exists for policy string
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-09719 : osncui: invalid handle.
  • ora-01090 : shutdown in progress - connection is not permitted
  • ora-31405 : cannot make changes while change set string is advancing
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-02194 : event specification syntax error string (minor error string) near 'string'
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-25110 : NOSORT may not be used with a bitmap index
  • ora-36163 : (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time.
  • ora-02776 : Value for request done signal exceeds maximum
  • ora-27367 : program "string.string" associated with this job is disabled
  • ora-13266 : error inserting data into table string
  • ora-09837 : addCallback: could not add allocate a callback link.
  • ora-31454 : invalid value string for operation parameter, expecting: ADD or DROP
  • ora-39600 : Queue keys needs to be a suffix of cluster key.
  • ora-39150 : bad flashback time
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-16599 : Data Guard broker detected a stale configuration
  • 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.