ORA-25304: Cannot use priority order queues for capture LCRs

Cause : CaptureL CRs cano nly usec ommit tmie or enuqeue tim eorderedq ueues.

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

Use thea ppropritae type fo queue ofr captuerd LCRs.

update : 26-04-2017

ORA-25304 - Cannot use priority order queues for capture LCRs
ORA-25304 - Cannot use priority order queues for capture LCRs

  • ora-26699 : STREAMS message consumer string already exists
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-12711 : this CREATE CONTROLFILE character set is not allowed
  • ora-32837 : invalid configuration state string
  • ora-30109 : could not open parameter file 'string'
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-27373 : unknown or illegal event source queue
  • ora-16788 : unable to set one or more database configuration property values
  • ora-19279 : XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
  • ora-31509 : publication does not exist
  • ora-29870 : specified options are only valid for altering a domain index
  • ora-28579 : network error during callback from external procedure agent
  • ora-24024 : Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
  • ora-19629 : no files in specified archivelog SCN range
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-14259 : table is not partitioned by Hash method
  • ora-31224 : DBMS_LDAP: invalid LDAP session
  • ora-40215 : model string is incompatible with current operation
  • ora-24010 : QUEUE string does not exist
  • ora-00711 : new tablespace name is invalid
  • ora-09806 : Allocation of label string buffer failed.
  • ora-06268 : NETNTT: cannot read /etc/oratab
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-15071 : ASM disk "string" is already being dropped
  • ora-36690 : (NTEXTCNV01) Error during conversion from NTEXT to TEXT.
  • ora-40212 : invalid target data type in input data for string function
  • ora-30751 : cannot disable column string from storing objects of type string.string
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • ora-38783 : Instance recovery required.
  • ora-07637 : smsdbp: buffer protect option not specified when sga created
  • 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.