ORA-24907: invalid pair of callback and recepient protocol attributes

Cause : The subscription handle passed into the OCI call can't have both the callback defined and a recepient protocol other than OCI_SUBSCR_PROTO_OCI at the same time.

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

Please set the appropriate callback and recepient protocol attributes using the OCIAttrSet() call.

update : 27-05-2017

ORA-24907 - invalid pair of callback and recepient protocol attributes
ORA-24907 - invalid pair of callback and recepient protocol attributes

  • ora-30973 : invalid Path Table option for XML Index
  • ora-36766 : (XSAGGCNTMOVE04) workspace object cannot be used as an AGGCOUNT because it has an AGGCOUNT.
  • ora-12900 : must specify a default temporary tablespace for a locally managed database
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-39218 : type check on object type "string"."string" failed
  • ora-16765 : Redo Apply is unexpectedly online
  • ora-02425 : create table failed
  • ora-39033 : Data cannot be filtered under the direct path access method.
  • ora-37108 : (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.
  • ora-03204 : the segment type specification should indicate partitioning
  • ora-32579 : password for SYSTEM already specified
  • ora-40222 : data mining model export failed, job name=string, error=string
  • ora-06774 : TLI Driver: error sending break mode
  • ora-24002 : QUEUE_TABLE string does not exist
  • ora-13150 : failed to insert exception record
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-31463 : logfile location string is an empty directory
  • ora-26762 : Cannot autogenerate name for parameter string because of the following reason: string
  • ora-31443 : deadlock detected while acquiring lock on string
  • ora-09208 : sftcls: error closing file
  • ora-26721 : enqueue of the LCR not allowed
  • ora-26083 : unsupported direct path stream version string
  • ora-27547 : Unable to query IPC OSD attribute string
  • ora-24143 : invalid evaluation context name
  • ora-07454 : queue timeout, string second(s), exceeded
  • ora-36674 : (XSDPART12) Invalid dimension value starting at string.
  • ora-06951 : Operating system call error
  • ora-25199 : partitioning key of a index-organized table must be a subset of the primary key
  • ora-15117 : command only operates on one diskgroup
  • ora-13850 : Tracing for client identifier string is not enabled
  • 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.