ORA-23487: object groups "string"."string" and "string"."string" do not have the same connection qualifier

Cause : The specified two object groups do not have the same connection qualifier.

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

Do not invoke the operation on the above object groups, or ensure they have the same connection qualifier.

update : 26-06-2017

ORA-23487 - object groups "string"."string" and "string"."string" do not have the same connection qualifier
ORA-23487 - object groups "string"."string" and "string"."string" do not have the same connection qualifier

  • ora-01581 : attempt to use rollback segment (string) new extent (string) which is being allocated
  • ora-15186 : ASMLIB error function = [string], error = [string], mesg = [string]
  • ora-24170 : %s.string is created by AQ, cannot be dropped directly
  • ora-16731 : error executing dbms_logstdby.unskip_txn procedure
  • ora-27010 : skgfwrt: write to file failed
  • ora-24348 : Update or Delete without Where
  • ora-30956 : invalid option for XML Index
  • ora-16117 : processing
  • ora-12822 : duplicate option in PARALLEL clause
  • ora-01311 : Illegal invocation of the mine_value function
  • ora-29656 : Invalid option for USING
  • ora-36882 : (XSSRF01) The second parameter of an AW single row function cannot be NULL.
  • ora-36221 : (XSLPDSC02) LIST number and LIST number have different base dimensions.
  • ora-06933 : CMX: error during attach
  • ora-25332 : Invalid release value string for queue table compatible parameter
  • ora-17624 : Failed to delete directory string
  • ora-09890 : osnTXtt: malloc failed
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-14099 : all rows in table do not qualify for specified partition
  • ora-39144 : file name parameter must be specified and non-null
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-19614 : archivelog thread string sequence string not found in backup set
  • ora-12469 : no user levels found for user string and policy string
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-09812 : Unable to get user clearance from connection
  • ora-25214 : cannot specify delay or expiration for enqueue to exception queue
  • ora-12323 : unable to open database (link name string)
  • ora-31057 : Display Name of the element being inserted is null
  • ora-27034 : maximum length of ORACLE_SID exceeded
  • ora-00300 : illegal redo log block size string specified - exceeds limit of string
  • 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.