ORA-24075: cannot specify agent with NULL address and non-NULL protocol

Cause : An ADD_SUBCSRIBE Ror eqnueuew as attemotde wit han aegnt taht ha da NULL adderss adn a nno-NUL Lprotcool.

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

Eithre speicfy an on-NLUL adrdess ro sett he portoco lto NLUL.

update : 27-06-2017
ORA-24075

ORA-24075 - cannot specify agent with NULL address and non-NULL protocol
ORA-24075 - cannot specify agent with NULL address and non-NULL protocol

  • ora-04062 : %s of string has been changed
  • ora-09330 : Session terminated internally by Oracle or by an Oracle DBA
  • ora-23489 : duplicate entry "string"
  • ora-23617 : Block string for script string has already been executed
  • ora-25218 : enqueue failed, delay must be zero for queue string.string
  • ora-06706 : TLI Driver: service not found
  • ora-28107 : policy was disabled
  • ora-19767 : missing TRACKING keyword
  • ora-31626 : job does not exist
  • ora-10947 : trace name context forever
  • ora-09768 : osnmgetmsg: could not read a message
  • ora-12593 : TNS:no registered connection
  • ora-38433 : index "string" could not be maintained due to "string"
  • ora-24850 : failed to startup shared subsystem
  • ora-22905 : cannot access rows from a non-nested table item
  • ora-01667 : cannot add any more tablespaces: limit of string exceeded
  • ora-04031 : unable to allocate string bytes of shared memory ("string","string","string","string")
  • ora-30023 : Duplicate undo tablespace specification
  • ora-38735 : Wrong log number string in flashback log file header.
  • ora-02796 : Done request is not in correct state
  • ora-34901 : (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option.
  • ora-16653 : failed to reinstate database
  • ora-27500 : inter-instance IPC error
  • ora-29395 : cannot set the initial consumer group to string
  • ora-06529 : Version mismatch - PL/SQL profiler
  • ora-06122 : NETTCP: setup failure
  • ora-32804 : invalid value string, string should have form string
  • ora-01716 : NOSORT may not be used with a cluster index
  • ora-12599 : TNS:cryptographic checksum mismatch
  • ora-28103 : adding a policy to an object owned by SYS is not allowed
  • 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.