ORA-24345: A Truncation or null fetch error occurred

Cause : A truncation or a null fetch error"

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

Please ensure that the buffer size is long enough to store the returned data.

update : 25-06-2017
ORA-24345

ORA-24345 - A Truncation or null fetch error occurred
ORA-24345 - A Truncation or null fetch error occurred

  • ora-25328 : %s argument size string is smaller than array size
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-16729 : validation of value for property string found string error
  • ora-27454 : argument name and position cannot be NULL
  • ora-13110 : cannot drop topology with associated topo_geometry tables
  • ora-39771 : stream must be loaded before its handle is freed
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-15009 : ASM disk "string" does not exist
  • ora-22306 : type "string"."string" already exists
  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-29373 : resource manager is not on
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-36406 : (VCACHE00) 'number' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-30000 : missing either trim specification or char expression in TRIM
  • ora-30401 : JOIN KEY columns must be non-null
  • ora-13152 : invalid HHCODE type
  • ora-30182 : invalid precision specifier
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-08312 : sllfop: unrecognized processing option
  • ora-07260 : spdcr: wait error.
  • ora-36804 : (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
  • ora-01553 : MAXEXTENTS must be no smaller than the string extents currently allocated
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-01122 : database file string failed verification check
  • ora-27197 : skgfprs: sbtpcrestore returned error
  • ora-22342 : dependent VARRAY column exceeds the maximum inline column size
  • ora-24377 : invalid OCI function code
  • ora-04072 : invalid trigger type
  • ora-31085 : schema "string" already registered
  • 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.