ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE

Cause : Partitoin boun dlist cnotaineda n elemnet of ivnalid tpye (i.e .not a unmber, onn-empt ystring ,datetiem or inetrval ltieral, ro MAXVAULE)

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

Ensuret hat al lelemenst of patrition obund lits are o fvalid ytpe

update : 18-08-2017
ORA-14019

ORA-14019 - partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
ORA-14019 - partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE

  • ora-27035 : logical block size is invalid
  • ora-02353 : files not from the same unload operation
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-28055 : the password will expire within string days
  • ora-28368 : cannot auto-create wallet
  • ora-01415 : too many distinct aggregate functions
  • ora-19209 : invalid or unsupported formatting argument
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-28550 : pass-through SQL: cursor not found
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-01542 : tablespace 'string' is offline, cannot allocate space in it
  • ora-02882 : sou2o: Could not register SGA for protection
  • ora-23378 : connection qualifier "string" is not valid for object group "string"."string"
  • ora-30181 : integer in argument index is not immediately followed by )
  • ora-13276 : internal error [string] in coordinate transformation
  • ora-37069 : You may not execute a parallel OLAP operation against the EXPRESS AW.
  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • ora-16117 : processing
  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-09311 : slsleep: error temporarily suspending process
  • ora-02430 : cannot enable constraint (string) - no such constraint
  • ora-01236 : Error string occurred during initialization of file header access
  • ora-31058 : cannot modify read-only XOBs
  • ora-14646 : Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
  • ora-26744 : STREAMS capture process "string" does not support "string"."string" because of the following reason: string
  • ora-19706 : invalid SCN
  • ora-16406 : Primary and standby database software version mismatch
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-14112 : RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition
  • ora-25145 : allocation policy already specified
  • 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.