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 : 17-08-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-12650 : No common encryption or data integrity algorithm
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-15001 : diskgroup "string" does not exist or is not mounted
  • ora-13422 : invalid model coordinate parameter
  • ora-15039 : diskgroup not dropped
  • ora-06914 : CMX: unexepected event during start of oracle
  • ora-01947 : TEMPORARY TABLESPACE already specified
  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-28368 : cannot auto-create wallet
  • ora-00481 : LMON process terminated with error
  • ora-12412 : policy package string is not installed
  • ora-06029 : NETASY: port assignment failure
  • ora-09715 : orasrv: cannot obtain puname
  • ora-01500 : failure in getting date/time
  • ora-19005 : Duplicate XMLType LOB storage option
  • ora-23392 : could not find materialized view to be associated with "string"."string"
  • ora-36222 : (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object
  • ora-08449 : invalid numeric symbol found in picture mask
  • ora-00290 : operating system archival error occurred. See error below
  • ora-25505 : the system is not in quiesced state
  • ora-24090 : at least one protocol must be enabled
  • ora-06737 : TLI Driver: connection failed
  • ora-01260 : warning: END BACKUP succeeded but some files found not to be in backup mode
  • ora-24759 : invalid transaction start flags
  • ora-32058 : operation restricted to SYSDBA users
  • ora-17622 : failed to deregister the memory with Oracle Disk Manager library
  • ora-04097 : DDL conflict while trying to drop or alter a trigger
  • ora-26095 : unprocessed stream data exists
  • ora-33265 : (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.
  • ora-15183 : ASMLIB initialization error [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.