ORA-13798: Parameter string cannot be NULL.

Cause : A call to GET_THRESHOLD procedure was made without a required parameter.

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

Specify a valid value for this parameter.

update : 24-09-2017
ORA-13798

ORA-13798 - Parameter string cannot be NULL.
ORA-13798 - Parameter string cannot be NULL.

  • ora-37601 : (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-14059 : partition "string": INITRANS value must be less than MAXTRANS value
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-24308 : illegal define position
  • ora-28200 : IDENTIFIED USING already specified
  • ora-40207 : duplicate or multiple function settings
  • ora-23441 : object does not exist for refresh group template
  • ora-14624 : DEFAULT subpartition must be last subpartition specified
  • ora-12680 : Native services disabled but required
  • ora-28168 : attempted to grant password-protected role
  • ora-26673 : duplicate column name string
  • ora-19203 : Error occurred in DBMS_XMLGEN processingstring
  • ora-02195 : Attempt to create string object in a string tablespace
  • ora-13506 : operation failed due to invalid snapshot range (string, string)
  • ora-38101 : Invalid column in the INSERT VALUES Clause: string
  • ora-19163 : XP0004 - XQuery type mismatch: argument type mismatch: expected - 'string' got - 'string' for function 'string'
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-22858 : invalid alteration of datatype
  • ora-14609 : Tablespace was not specified for the previous lob segments of column string in template but is specified for string
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-29871 : invalid alter option for a domain index
  • ora-37084 : Output valueset string must match string's dimensionality
  • ora-10925 : trace name context forever
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-37116 : OLAP API table function error: (string)
  • ora-13332 : invalid LRS point
  • ora-37031 : (XSMLTMAINT02) You cannot DELETE values of dimension workspace object in MULTI mode.
  • ora-26099 : direct path context is already prepared
  • ora-29881 : failed to validate indextype
  • 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.