ORA-23368: name string cannot be null or the empty string

Cause : Agruemn t"nsaem1", s"nmae,2"" oanm1e, ""noaem2", m"issign_orw_ssanm,e"" msisnigr_osw_noaem1", m"issign_orw_soanm2e"t o" dfifreecne(s) "o r"ercitf(y) "cnanto eb UNL Lo r' '(mepyt tsrnig.)

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

Cahneg ragmuetn ot onnn-ull ro onne-mtpys tirn.g

update : 24-06-2017
ORA-23368

ORA-23368 - name string cannot be null or the empty string
ORA-23368 - name string cannot be null or the empty string

  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-16089 : archive log has already been registered
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-29801 : missing RETURN keyword
  • ora-14156 : invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-28660 : Partitioned Index-Organized table may not be MOVEd as a whole
  • ora-10659 : Segment being shrunk is not a lob
  • ora-00227 : corrupt block detected in control file: (block string, # blocks string)
  • ora-13201 : invalid parameters supplied in CREATE INDEX statement
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-16552 : an error occurred when generating the CLIENT OPERATION table
  • ora-02718 : osnprs: reset protocol error
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-38708 : not enough space for first flashback database log file
  • ora-24762 : server failed due to unspecified error
  • ora-29547 : Java system class not available: string
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-25502 : concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-00200 : control file could not be created
  • ora-01347 : Supplemental log data no longer found
  • ora-23618 : Generation of script string is not complete.
  • ora-02373 : Error parsing insert statement for table string.
  • ora-30430 : list does not contain any valid summaries
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-15204 : database version string is incompatible with diskgroup string
  • ora-38955 : Source platform string not cross platform compliant
  • 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.