ORA-24415: Missing or null username.

Cause : Username and password must be specified when pool is created in this mode.

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

Specify a valid username and password.

update : 23-06-2017

ORA-24415 - Missing or null username.
ORA-24415 - Missing or null username.

  • ora-25180 : PCTTHRESHOLD only valid for certain table organizations
  • ora-21605 : property [string] is not a property of value instances
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-01300 : writable database required for specified LogMiner options
  • ora-00352 : all logs for thread string need to be archived - cannot enable
  • ora-33313 : (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.
  • ora-19960 : Internal use only
  • ora-24793 : Test DTP service start and stop
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-38620 : DT expressions in input cursor do not have an alias name
  • ora-08196 : Flashback Table operation is not allowed on AQ tables
  • ora-24368 : OCI mutex counter non-zero when freeing a handle
  • ora-03241 : Invalid unit size
  • ora-24166 : evaluation context string.string has errors
  • ora-37184 : illegal value string for ADVMODE
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-26521 : rpc initialization error
  • ora-14503 : only one partition name can be specified
  • ora-19512 : file search failed
  • ora-29810 : inadequate operator privileges
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-29394 : session id string and serial# string do not exist
  • ora-01074 : cannot shut down ORACLE; inside a login session - log off first
  • ora-38601 : FI Not enough memory for frequent itemset counting: string
  • ora-25951 : join index where clause cannot contain OR condition
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-36665 : (XSDPART03) workspace object is not in the dimension list of the PARTITION TEMPLATE.
  • ora-37115 : New OLAP API history is not allowed
  • ora-01201 : file string header failed to write correctly
  • ora-13368 : simple polygon type has more than one exterior ring
  • 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.