ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified

Cause : More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.

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

Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.

update : 26-06-2017
ORA-00118

ORA-00118 - Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified
ORA-00118 - Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified

  • ora-06712 : TLI Driver: error on accept
  • ora-12525 : TNS:listener has not received client's request in time allowed
  • ora-35066 : (QFGET03) Extension number number is missing for EIF file string.
  • ora-38733 : Physical size string less than needed string.
  • ora-06261 : NETNTT: nrange() failed
  • ora-27473 : argument string does not exist
  • ora-26536 : refresh was aborted because of conflicts caused by deferred transactions
  • ora-16572 : Data Guard configuration file not found
  • ora-12023 : missing index on materialized view "string"."string"
  • ora-01260 : warning: END BACKUP succeeded but some files found not to be in backup mode
  • ora-25206 : enqueue failed, enqueue to exception queue string.string not permitted
  • ora-29280 : invalid directory path
  • ora-02763 : Unable to cancel at least one request
  • ora-28151 : more than one user name specified for command
  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-32143 : Environment not specified
  • ora-07742 : slemop: $CONNECT failure
  • ora-19625 : error identifying file string
  • ora-12150 : TNS:unable to send data
  • ora-31077 : invalid attribute "string" specified
  • ora-28576 : lost RPC connection to external procedure agent
  • ora-24328 : illegal attribute value
  • ora-09350 : Windows 32-bit Two-Task driver unable to allocate context area
  • ora-16751 : resource guard encountered errors in switchover to primary database
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • ora-15199 : Internal ASM tracing event number 15199
  • ora-24100 : error in ktz testing layer
  • ora-26504 : operation not implemented
  • ora-02442 : Cannot drop nonexistent unique key
  • 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.