ORA-08261: ora_addr: cannot find name in nameserver

Cause : The listener nameserver entry for an instance could not be found.

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

Make sure the nameserver is up and running. Additional information gives nameserver's returned status.

update : 28-07-2017

ORA-08261 - ora_addr: cannot find name in nameserver
ORA-08261 - ora_addr: cannot find name in nameserver

  • ora-01981 : CASCADE CONSTRAINTS must be specified to perform this revoke
  • ora-26077 : direct path column array is not initialized
  • ora-01538 : failed to acquire any rollback segment
  • ora-19241 : XP0021 - cast to type string failed
  • ora-00291 : numeric value required for PARALLEL option
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-38464 : expression set is not empty.
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-23304 : malformed deferred rpc at arg string of string in call string, in tid string
  • ora-00399 : corrupt change description in redo log
  • ora-27123 : unable to attach to shared memory segment
  • ora-16206 : database already configured as Logical Standby database
  • ora-00438 : %s Option not installed
  • ora-26688 : missing key in LCR
  • ora-37126 : (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as a base of a single variable.
  • ora-16060 : Log file is current
  • ora-00292 : parallel recovery feature not installed
  • ora-03231 : the INITIAL extent may not be deallocated
  • ora-12401 : invalid label string: string
  • ora-14076 : submitted alter index partition/subpartition operation is not valid for local partitioned index
  • ora-27007 : failed to open file
  • ora-32308 : object materialized views must use SELECT *
  • ora-12993 : tablespace 'string' is offline, cannot drop column
  • ora-09985 : SGA definition file could not be read
  • ora-38851 : cannot mark the current instance (redo thread) as disabled
  • ora-39955 : invalid PL/SQL warning message number
  • ora-00085 : current call does not exist
  • ora-01469 : PRIOR can only be followed by a column name
  • ora-30087 : Adding two datetime values is not allowed
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • 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.