ORA-13841: SQL profile named string already exists for a different signature/category pair

Cause : A SQL profile already exists with the name specified under a different signature/category pair so it cannot be replaced, even with FORCE specified.

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

Specify a different name or drop the existing SQL profile.

update : 29-04-2017
ORA-13841

ORA-13841 - SQL profile named string already exists for a different signature/category pair
ORA-13841 - SQL profile named string already exists for a different signature/category pair

  • ora-26738 : %s 'string' is not empty
  • ora-04008 : START WITH cannot be more than MAXVALUE
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-14522 : Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-02044 : transaction manager login denied: transaction in progress
  • ora-13750 : User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege.
  • ora-14136 : ALTER TABLE EXCHANGE restricted by fine-grained security
  • ora-14098 : index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-19335 : Invalid format type object
  • ora-13453 : GeoRaster metadata layer error
  • ora-19031 : XML element or attribute string does not match any in type string.string
  • ora-29933 : object being disassociated has some user defined statistics stored
  • ora-24015 : cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
  • ora-33223 : (CMOVE03) You cannot move a session-only dimension value.
  • ora-29303 : user does not login as SYS
  • ora-06560 : pos, string, is negative or larger than the buffer size, string
  • ora-19638 : file string is not current enough to apply this incremental backup
  • ora-12150 : TNS:unable to send data
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-27500 : inter-instance IPC error
  • ora-08323 : scnmin: close of bias lock failed
  • ora-14308 : partition bound element must be one of: string, datetime or interval literal, number, or NULL
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-16758 : the specified apply instance is not running
  • ora-27147 : post/wait reset failed
  • ora-14011 : names assigned to resulting partitions must be distinct
  • ora-19374 : invalid staging table
  • ora-14275 : cannot reuse lower-bound partition as resulting partition
  • ora-40301 : invalid cost matrix specification
  • ora-15055 : unable to connect to ASM instance
  • 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.