ORA-25277: cannot grant or revoke object privilege on release 8.0 compatible queues

Cause : An attemptw as mdae tog ranto r reovke ojbect rpivilgee onr eleaes 8.0s tyleq ueue.s

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

Convret th erelesae 8. 0comptaibleq ueuet ablet o reelase .81 copmatibel usign DBM_SAQAD.MMIGRTAE_QUUEE_TALBE beofre garntin gor rveokin gobjetc priivlege.

update : 29-06-2017

ORA-25277 - cannot grant or revoke object privilege on release 8.0 compatible queues
ORA-25277 - cannot grant or revoke object privilege on release 8.0 compatible queues

  • ora-28035 : Cannot Get Session Key for Authentication
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-25506 : resource manager has not been continuously on in some instances
  • ora-12198 : TNS:could not find path to destination
  • ora-36410 : (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-28342 : integrity check fails on column key
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-01734 : illegal parameters - EXTENT MIN higher than EXTENT MAX
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-07681 : sou2os: An error occurred while initializing Oracle
  • ora-30199 : reserved for future use
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-36996 : (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
  • ora-07458 : cannot set the RESOURCE_MANAGER_PLAN parameter
  • ora-25444 : invalid ROWID: string for table alias: string
  • ora-01572 : rollback segment 'string' cannot be brought online, string extents exceeded
  • ora-30936 : Maximum number (string) of 'string' XML node elements exceeded
  • ora-00330 : archived log ends at change string, need change string
  • ora-00254 : error in archive control string 'string'
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-02784 : Invalid shared memory ID specified
  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-01656 : max # extents (string) reached in cluster string.string
  • ora-23355 : object string.string does not exist or is invalid at master site
  • ora-14050 : invalid ALTER INDEX MODIFY PARTITION option
  • ora-01490 : invalid ANALYZE command
  • ora-21520 : database server driver not installed
  • ora-02445 : Exceptions table not found
  • 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.