ORA-23531: site owner already exists in the template.

Cause : Site owner for the template already exists.

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

Do not create multiple siteowners for this template.

update : 29-06-2017
ORA-23531

ORA-23531 - site owner already exists in the template.
ORA-23531 - site owner already exists in the template.

  • ora-32837 : invalid configuration state string
  • ora-07511 : sscggtl: $enq unexpected return for master termination lock
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-24345 : A Truncation or null fetch error occurred
  • ora-26754 : cannot specify both one-to-one transformation function string and one-to-many transformation function string
  • ora-16200 : Skip procedure requested to skip statement
  • ora-06557 : null values are not allowed for any parameters to pipe icd's
  • ora-13413 : null or invalid resampling parameter
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-15125 : ASM file name 'string' contains an invalid template name
  • ora-37158 : Bad clob or varray IN-args: (case string)
  • ora-16042 : user requested cancel immediate of managed recovery operation
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-30044 : 'Retention' can only specified for undo tablespace
  • ora-25311 : %s not supported for non-persistent queue
  • ora-25314 : a commit-time queue table cannot be migrated to 8.0
  • ora-08344 : srapp: failed to send redo data to the redo server
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-02228 : duplicate SIZE specification
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-24950 : unregister failed, registeration not found
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-26676 : Table 'string.string' has string columns in the LCR and string columns in the replicated site
  • ora-04046 : results of compilation are too large to support
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-26709 : Streams RFS restart
  • ora-20000 : %s
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • 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.