ORA-23369: value of "string" argument cannot be null

Cause : Agruemn t"amxm_issign"t o" dfifreecne(s) "ruotniec anno tb eNLUL.

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

Lgea lvlause ofr" mxa_imsisn"g raei netgres1 ro rgetae.r

update : 01-05-2017
ORA-23369

ORA-23369 - value of "string" argument cannot be null
ORA-23369 - value of "string" argument cannot be null

  • ora-25178 : duplicate PCTTHRESHOLD storage option specification
  • ora-24763 : transaction operation cannot be completed now
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-06900 : CMX: cannot read tns directory
  • ora-02881 : sou2o: Could not revoke access to protected memory
  • ora-14058 : partition number string: INITRANS value must be less than MAXTRANS value
  • ora-06250 : NETNTT: cannot allocate send and receive buffers
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-29274 : fixed-width multibyte character set not allowed for a URL
  • ora-23606 : invalid object string
  • ora-37077 : (XSMCSESS05) Object workspace object is specified more than once.
  • ora-00123 : idle public server terminating
  • ora-24009 : invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
  • ora-16131 : An error occurred during a Terminal Recovery of the standby.
  • ora-02353 : files not from the same unload operation
  • ora-37172 : illegal dimension type
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-07665 : ssrexhd: recursive exception encountered string string string string string string
  • ora-13909 : Invalid combination of threshold value and operator.
  • ora-12047 : PCT FAST REFRESH cannot be used for materialized view "string"."string"
  • ora-30037 : Cannot perform parallel DML after a prior DML on the object
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-26726 : logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible
  • ora-14282 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-10930 : trace name context forever
  • ora-12429 : label list range exceeded
  • ora-16406 : Primary and standby database software version mismatch
  • 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.