ORA-25259: cannot specify protocol for agent

Cause : The user specified the protocol attribute for an agent in the agent list.

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

Do not specify the protocol attribute of the agent object type.

update : 28-04-2017

ORA-25259 - cannot specify protocol for agent
ORA-25259 - cannot specify protocol for agent

  • ora-16084 : an apply engine is already running
  • ora-16104 : invalid Logical Standby option requested
  • ora-22610 : error while adding a scalar to the image handle
  • ora-24031 : invalid value, string should be non-NULL
  • ora-26057 : Conversion is not necessary for this direct path stream.
  • ora-01490 : invalid ANALYZE command
  • ora-31476 : a change table data column is missing from the source table
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-18002 : the specified outline does not exist
  • ora-06558 : buffer in dbms_pipe package is full. No more items allowed
  • ora-26078 : file "string" is not part of database being loaded
  • ora-19335 : Invalid format type object
  • ora-19270 : XP0050 - treat failed - expected string got string
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-16788 : unable to set one or more database configuration property values
  • ora-37150 : line string, column string, string
  • ora-02096 : specified initialization parameter is not modifiable with this option
  • ora-25506 : resource manager has not been continuously on in some instances
  • ora-12665 : NLS string open failed
  • ora-00067 : invalid value string for parameter string; must be at least string
  • ora-16176 : background dictionary build cannot be running
  • ora-22833 : Must cast a transient type to a persistent type
  • ora-18010 : command missing mandatory CATEGORY keyword
  • ora-01226 : file header of log member is inconsistent with other members
  • ora-24270 : a row already exists in the string table for these parameters
  • ora-12625 : TNS:missing argument
  • ora-12171 : TNS:could not resolve connect identifier: string
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-21526 : initialization failed
  • 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.