ORA-02084: database name is missing a component

Cause : supplide databsae namec annot ocntain aleadin g'.', tariling .'' or ''@, or tow '.' o r'@' ina row.

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

none

update : 29-04-2017
ORA-02084

ORA-02084 - database name is missing a component
ORA-02084 - database name is missing a component

  • ora-26698 : %s did not have a string rule set
  • ora-32773 : operation not supported for smallfile tablespace string
  • ora-01157 : cannot identify/lock data file string - see DBWR trace file
  • ora-00025 : failed to allocate string
  • ora-09778 : snynfyport: failure allocating the notify port.
  • ora-26696 : no streams data dictionary for object with number string and version number string from source database string
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-36994 : (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric.
  • ora-01913 : EXCLUSIVE keyword expected
  • ora-01531 : a database already open by the instance
  • ora-09880 : sstasfre/sstasdel: shmdt error, unable to detach tas write page
  • ora-39143 : dump file "string" may be an original export dump file
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-27509 : IPC error receiving a message
  • ora-16724 : the intended state for the database has been set to OFFLINE
  • ora-02269 : key column cannot be of LONG datatype
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
  • ora-06264 : NETNTT: data protocol error
  • ora-38958 : Source platform string is in different byte order than target platform string
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-02778 : Name given for the log directory is invalid
  • ora-24011 : cannot drop QUEUE, string should be stopped first
  • ora-01612 : instance string (thread string) is already enabled
  • ora-25335 : AQ array operations not allowed for buffered messages
  • ora-30077 : illegal casting between specified datetime types
  • ora-10668 : Inject Evil Identifiers
  • ora-23420 : interval must evaluate to a time in the future
  • 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.