ORA-36341: (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)

Cause : Bad syntax

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

Correct syntax

update : 30-04-2017
ORA-36341

ORA-36341 - (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
ORA-36341 - (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)

  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-36921 : (XSVPMVTOPART02) workspace object and workspace object are not in the same analytic workspace.
  • ora-14276 : EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
  • ora-29349 : tablespace 'string' already exists
  • ora-31017 : Error generating unique OID for XML document
  • ora-30750 : cannot enable column string to store objects of type string.string
  • ora-34359 : (MXDSS11) string appears twice in the alias list.
  • ora-15047 : ASM file name 'string' is not in multiple-file creation form
  • ora-32165 : Cannot get XA environment
  • ora-30079 : cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
  • ora-19261 : XQ0041 - non empty URI in QName
  • ora-25306 : Cannot connect to buffered queue's owner instance
  • ora-32144 : Cannot perform operation on a null interval
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-24195 : attemp to retrieve the name list of a map message with size exceeding 1024
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-14084 : you may specify TABLESPACE DEFAULT only for a LOCAL index
  • ora-32637 : Self cyclic rule in sequential order MODEL
  • ora-10920 : Cannot offline tablespace belonging to default temporary tablespace group
  • ora-39090 : Cannot add devices to file oriented job.
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-13622 : invalid recommendation annotation
  • ora-31457 : maximum length of description field exceeded
  • ora-25310 : Subscriber is Notification only; dequeue not supported
  • ora-29308 : view TS_PITR_CHECK failure
  • ora-07845 : sllfcl: LIB$FREE_VM failue
  • ora-36702 : (XSRELTBL05) The format of the HIERHEIGHT function is: HIERHEIGHT(relation [,] level) level >= 1.
  • ora-25439 : duplicate variable value for variable: string
  • ora-12062 : transaction string received out of sequence from site string
  • ora-15034 : disk 'string' does not require the FORCE option
  • 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.