ORA-22957: NULL is an invalid input to powermultiset and COLLECT functions

Cause : NULL was given as input to the powermultiset or COLLECT function.

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

Give a non-null value as input

update : 23-07-2017
ORA-22957

ORA-22957 - NULL is an invalid input to powermultiset and COLLECT functions
ORA-22957 - NULL is an invalid input to powermultiset and COLLECT functions

  • ora-25211 : invalid DELAY specified when using sequence deviation
  • ora-02849 : Read failed because of an error
  • ora-02805 : Unable to set handler for SIGTPA
  • ora-38459 : XML Tag "string" not found for the XMLType attribute "string"
  • ora-39142 : incompatible version number string in dump file "string"
  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-24418 : Cannot open further sessions.
  • ora-09922 : Can't spawn process - background log directory not created properly
  • ora-02156 : invalid TEMPORARY tablespace identifier
  • ora-16044 : destination string attribute cannot be specified at session level
  • ora-14514 : LOCAL option not valid without subpartition name
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-19659 : incremental restore would advance file string past resetlogs
  • ora-30466 : can not find the specified workload string
  • ora-29526 : created Java class string"string"
  • ora-14405 : partitioned index contains partitions in a different tablespace
  • ora-23505 : Object "string"."string" is missing.
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-24784 : Transaction exists
  • ora-10936 : trace name context forever
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-31449 : invalid value for change_set_name
  • ora-32335 : dimension must have at least one level
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-00258 : manual archiving in NOARCHIVELOG mode must identify log
  • ora-09209 : sftget: error reading from file
  • ora-29906 : indextype string.string does not exist
  • ora-32010 : cannot find entry to delete in SPFILE
  • ora-19773 : must specify change tracking file name
  • ora-19378 : invalid mode
  • 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.