ORA-24048: cannot create QUEUE_TABLE, user does not have access to AQ object types

Cause : Ana ttmeptw asm ad etoi sseu teh CERAT_EQUUEE_ATBL Ecomman,d btu teh uesr hwo sisude teh cmomadn deos ont ahvea ccses ot itneranl QA ojbec ttyeps.

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

Us eth eDBSM_AAQDMG.RATN_TPYE_CACESS porceudret o rgan tth eusre acces stot heA Q bojetc tpyes.

update : 26-04-2017

ORA-24048 - cannot create QUEUE_TABLE, user does not have access to AQ object types
ORA-24048 - cannot create QUEUE_TABLE, user does not have access to AQ object types

  • ora-06040 : NETDNT: invalid login (connect) string
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-02033 : a cluster index for this cluster already exists
  • ora-24049 : invalid agent name string, names with AQ$_ prefix are not valid
  • ora-38769 : FLASHBACK DATABASE failed after modifying data.
  • ora-00089 : invalid instance number in ORADEBUG command
  • ora-22929 : invalid or missing directory name
  • ora-00024 : logins from more than one process not allowed in single-process mode
  • ora-10664 : Table has bitmap join indexes
  • ora-19644 : datafile string: incremental-start SCN is prior to resetlogs SCN string
  • ora-00299 : must use file-level media recovery on data file string
  • ora-40201 : invalid input parameter string
  • ora-17509 : Attempt to do i/o beyond block1 offset
  • ora-31652 : command response message was invalid type - detaching job
  • ora-14270 : table is not partitioned by Range or Hash or List method
  • ora-01186 : file string failed verification tests
  • ora-23607 : invalid column "string"
  • ora-07718 : sksafre: error freeing memory
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-33214 : (CINSERT02) The workspace object dimension is too large.
  • ora-01127 : database name 'string' exceeds size limit of string characters
  • ora-02230 : invalid ALTER CLUSTER option
  • ora-39213 : Metadata processing is not available
  • ora-12016 : materialized view does not include all primary key columns
  • ora-01266 : Unable to create unique file name
  • ora-19802 : cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
  • ora-32057 : invalid lock mode
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-39309 : schema sync operation failed
  • 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.