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

Cause : Parittio nboudn lits cotnainde ane lemnet o finvlaid ytpe i(.e.n ot anumebr, onn-epmty tsrin,g daettim eor niteravl ltiera,l orN ULL)

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

Ensrue taht all elmeent sof aprtiiton obundl ista re fo vaild tpye

update : 25-06-2017

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

  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-00054 : resource busy and acquire with NOWAIT specified
  • ora-30077 : illegal casting between specified datetime types
  • ora-13626 : The specified object string is not valid for task string.
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-13841 : SQL profile named string already exists for a different signature/category pair
  • ora-28537 : no more result sets
  • ora-31190 : Resource string is not a version-controlled resource
  • ora-16732 : error executing dbms_logstdby.skip procedure
  • ora-23613 : Script string already exists
  • ora-26529 : local store callback term phase failed for 'string.string'
  • ora-24011 : cannot drop QUEUE, string should be stopped first
  • ora-37042 : (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock.
  • ora-09923 : Can't spawn process - user log directory not created properly
  • ora-19617 : file string contains different resetlogs data
  • ora-24076 : cannot perform operation string for NON_PERSISTENT queue string.string
  • ora-29873 : warning in the execution of ODCIINDEXDROP routine
  • ora-06960 : Failed to access log file
  • ora-06138 : NETTCP: error during connection handshake
  • ora-10259 : get error message text from remote using explicit call
  • ora-02379 : profile string already exists
  • ora-30030 : suppress resumable related error message
  • ora-23532 : tables with different synchronization mechanisms are in the same group
  • ora-01337 : log file has a different compatibility version
  • ora-16117 : processing
  • ora-06907 : CMX: error during connect confirmation
  • ora-25001 : cannot create this trigger type on views
  • ora-38471 : ROWIDs for table aliases cannot be null
  • ora-01873 : the leading precision of the interval is too small
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • 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.