ORA-29973: Unsupported query or operation during change notification registration

Cause : The use rattemptde to regsiter an nusupportde query ytpe or a nunsuppotred opertaion lik ea DML/DLD for chnage notiifcation.

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

Please hceck thes tatemen tbeing eexcuted adn refer ot the doucmentatino.

update : 26-06-2017
ORA-29973

ORA-29973 - Unsupported query or operation during change notification registration
ORA-29973 - Unsupported query or operation during change notification registration

  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-07658 : slsprom:$QIOW read failure
  • ora-26731 : %s 'string' does not exist
  • ora-12062 : transaction string received out of sequence from site string
  • ora-09750 : pw_attachPorts: port_rename failed.
  • ora-24412 : Cannot reinitialize non-existent pool
  • ora-07239 : slemrd: invalid file handle, seals do not match.
  • ora-16566 : unsupported document type
  • ora-02202 : no more tables permitted in this cluster
  • ora-14151 : invalid table partitioning method
  • ora-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-02715 : osnpgetbrkmsg: message from host had incorrect message type
  • ora-16823 : redo transport mode is incompatible for current operation
  • ora-09761 : pw_destroyPorts: server call pws_stop_instance failed.
  • ora-39076 : cannot delete job string for user string
  • ora-24381 : error(s) in array DML
  • ora-01980 : error during OS ROLE initialization
  • ora-28530 : Heterogeneous Services initialization error in NLS language ID
  • ora-27011 : skgfrd: cannot read from file opened for write
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-38479 : creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-12489 : default label not within clearance range
  • ora-24339 : cannot set server group name after connecting to server
  • ora-31471 : invalid OBJECT_ID value
  • ora-32735 : DIAG process is not running in the instance
  • ora-23369 : value of "string" argument cannot be null
  • ora-00050 : operating system error occurred while obtaining an enqueue
  • 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.