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 : 25-06-2017

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-08270 : sksachk: Illegal archival control string
  • ora-37174 : source SQL must be a SELECT statement
  • ora-13435 : GeoRaster metadata dimension inconsistent
  • ora-24090 : at least one protocol must be enabled
  • ora-13601 : The specified Advisor string does not exist.
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-00600 : internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-30129 : invalid function argument received
  • ora-14295 : column type or size mismatch between partitioning columns and subpartitioning columns
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-00353 : log corruption near block string change string time string
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-00960 : ambiguous column naming in select list
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-24025 : invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an object type
  • ora-25463 : table alias not specified
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-07700 : sksarch: interrupt received
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-40207 : duplicate or multiple function settings
  • ora-02487 : Error in converting trace data
  • ora-22923 : amount of data specified in streaming LOB write is 0
  • ora-01799 : a column may not be outer-joined to a subquery
  • ora-32002 : cannot create SPFILE already being used by the instance
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-32141 : get method does not match the type of the parameter
  • ora-39778 : the parallel load option is not allowed when loading lob columns
  • ora-38412 : Expression set column string does not exist.
  • ora-30047 : Internal event for kti tracing
  • ora-02202 : no more tables permitted in this cluster
  • 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.