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 : 25-06-2017

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

  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • ora-07278 : splon: ops$username exceeds buffer length.
  • ora-00019 : maximum number of session licenses exceeded
  • ora-07563 : sldext: $PARSE failure
  • ora-21503 : program terminated by fatal error
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-31436 : duplicate change source string
  • ora-27452 : %s is an invalid name for a database object.
  • ora-24506 : invalid attempt to change character set id on env handle
  • ora-13049 : unable to determine tolerance value from table _SDODIM
  • ora-15021 : parameter "string" is not valid in string instance
  • ora-06102 : NETTCP: cannot allocate context area
  • ora-25246 : listen failed, the address string is an 8.0 style exception queue
  • ora-12722 : regular expression internal error
  • ora-25145 : allocation policy already specified
  • ora-13037 : SRIDs do not match for the two geometries
  • ora-32124 : Illegal attribute passed
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-38500 : %s
  • ora-07701 : sksatln: internal exception: output buffer too small
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-27165 : tried to join thread that does not exist
  • ora-10979 : trace flags for join index implementation
  • ora-30752 : column or table string is not substitutable
  • ora-07218 : slkhst: could not perform host operation
  • ora-24401 : cannot open further connections
  • ora-28540 : internal result set error
  • ora-02202 : no more tables permitted in this cluster
  • 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.