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 : 26-09-2017
ORA-24907

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

  • ora-02210 : no options specified for ALTER TABLE
  • ora-31633 : unable to create master table "string.string"
  • ora-12054 : cannot set the ON COMMIT refresh attribute for the materialized view
  • ora-15001 : diskgroup "string" does not exist or is not mounted
  • ora-00313 : open failed for members of log group string of thread string
  • ora-26709 : Streams RFS restart
  • ora-12168 : TNS:Unable to contact LDAP Directory Server
  • ora-07602 : spgto: $GETJPIW failure
  • ora-02430 : cannot enable constraint (string) - no such constraint
  • ora-25448 : rule string.string has errors
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-28277 : LDAP search, while authenticating global user with passwords, failed.
  • ora-19025 : EXTRACTVALUE returns value of only one node
  • ora-09274 : szrfc: insufficient role name buffer space
  • ora-30068 : Internal Event to turn on nested
  • ora-28121 : driving context does not exist
  • ora-13345 : a compound polygon geometry has fewer than five coordinates
  • ora-25212 : invalid PRIORITY specified when using sequence deviation
  • ora-06548 : no more rows needed
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-32101 : cannot create OCI Environment
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-02716 : osnpgetdatmsg: message from host had incorrect message type
  • ora-12430 : invalid privilege number
  • ora-29665 : Java thread deadlock detected
  • ora-02261 : such unique or primary key already exists in the table
  • ora-07709 : sksaprs: archiving to a remote host is not allowed
  • ora-01576 : The instance string is not enabled
  • ora-14131 : enabled UNIQUE constraint exists on one of the tables
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • 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.