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 : 17-08-2017

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-39027 : wrong version of master table
  • ora-25210 : invalid value for RELATIVE_MSGID, no message in queue with that msgid
  • ora-09967 : unable to create or open lock file
  • ora-00220 : control file not mounted by first instance, check alert log for more info
  • ora-08468 : mask option string is not supported
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-22904 : invalid reference to a nested table column
  • ora-30400 : identical JOIN KEY clauses
  • ora-30348 : ADD and DROP cannot both be specified
  • ora-02366 : The following index(es) on table string were processed:
  • ora-06449 : The list IO or the sysvendor is not installed.
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-22338 : must specify CASCADE INCLUDING DATA when altering the final property
  • ora-19661 : datafile string could not be verified
  • ora-39065 : unexpected master process exception in string
  • ora-00291 : numeric value required for PARALLEL option
  • ora-13446 : GeoRaster metadata TRS error
  • ora-30107 : parameter name abbreviation 'string' is not unique
  • ora-09709 : soacon: failed to accept a connection.
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-12069 : invalid object for offline instantiation
  • ora-09774 : osnmui: cannot send break message
  • ora-01268 : invalid TEMPFILE clause for alter of permanent TABLESPACE
  • ora-09833 : addCallback: bad message format.
  • ora-03203 : concurrent update activity makes space analysis impossible
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-30736 : objects in a table or view hierarchy have to be in the same schema
  • ora-25224 : sender name must be specified for enqueue into secure queues
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-16565 : duplicate property, syntax error at "string"
  • 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.