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 : 25-04-2017
ORA-24907

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

  • ora-32837 : invalid configuration state string
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-24102 : invalid prefix for generate_job_name
  • ora-30044 : 'Retention' can only specified for undo tablespace
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-29270 : too many open HTTP requests
  • ora-13769 : Snapshots string and string do not exist.
  • ora-01179 : file string does not exist
  • ora-39501 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-36378 : (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
  • ora-00272 : error writing archive log string
  • ora-00360 : not a logfile member: string
  • ora-13346 : the coordinates defining an arc are collinear
  • ora-07702 : unrecognized device type in archive text
  • ora-24792 : cannot mix services in a single global transaction
  • ora-09314 : sltln: error translating logical name
  • ora-06447 : ssvpstp: Incorrect parameter passed to function call
  • ora-37132 : (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-37127 : (XSCCOMP02) The COMPRESSED COMPOSITE workspace object must be last in the dimension list.
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-02057 : 2PC: string: bad two-phase recovery state number string from string
  • ora-31522 : could not find Streams object string for CDC change set string
  • ora-00037 : cannot switch to a session belonging to a different server group
  • ora-12061 : invalid ALTER MATERIALIZED VIEW option
  • ora-01227 : log string is inconsistent with other logs
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-09773 : osnmgetdatmsg: message from host had incorrect message type
  • ora-25288 : AQ HTTP propagation encountered error, status-code number, string
  • ora-09703 : sem_release: cannot release latch semaphore
  • 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.