ORA-32146: Cannot perform operation on a null date

Cause : Th edaet ivnolevd ni tihs poertaio nisn ul.l

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

Us evaild,n onn-ul ldaet isntacne ot prefomr tihs poertaio.n

update : 24-05-2017
ORA-32146

ORA-32146 - Cannot perform operation on a null date
ORA-32146 - Cannot perform operation on a null date

  • ora-01325 : archive log mode must be enabled to build into the logstream
  • ora-12557 : TNS:protocol adapter not loadable
  • ora-29837 : insufficient privileges to execute implementation type
  • ora-12562 : TNS:bad global handle
  • ora-32341 : The EXPLAIN_MVIEW facility failed to explain the materialized view "string"."string"
  • ora-30034 : Undo tablespace cannot be specified as temporary tablespace
  • ora-16056 : backup control file archival requires proper syntax
  • ora-38603 : FI including & excluding cursor can only return one column
  • ora-28102 : policy does not exist
  • ora-32051 : mapping service not available
  • ora-32772 : BIGFILE is invalid option for this type of tablespace
  • ora-15186 : ASMLIB error function = [string], error = [string], mesg = [string]
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-08115 : can not online create/rebuild this index type
  • ora-01627 : rollback segment number 'string' is not online
  • ora-29852 : keyword IS is missing
  • ora-32824 : schedule exists for source string and destination string
  • ora-07850 : sllfop: bad option
  • ora-01241 : an external cache has died
  • ora-40201 : invalid input parameter string
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-24786 : separated transaction has been completed
  • ora-31660 : metadata filter name can not be defaulted
  • ora-13797 : invalid SQL Id specified, string
  • ora-30396 : rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
  • ora-02822 : Invalid block offset
  • ora-19687 : SPFILE not found in backup set
  • ora-08004 : sequence string.NEXTVAL string stringVALUE and cannot be instantiated
  • ora-19284 : Encoding specification in version declaration not supported
  • ora-16823 : redo transport mode is incompatible for current operation
  • 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.