ORA-13829: SQL profile named string already exists

Cause : A SQL profile already exists with the name specified.

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

Specify a different name or drop the existing SQL profile.

update : 28-06-2017
ORA-13829

ORA-13829 - SQL profile named string already exists
ORA-13829 - SQL profile named string already exists

  • ora-01684 : max # extents (string) reached in table string.string partition string
  • ora-30107 : parameter name abbreviation 'string' is not unique
  • ora-12056 : invalid REFRESH method
  • ora-26734 : different datafiles_directory_object parameter must be specified
  • ora-27250 : OS system call failure
  • ora-10944 : trace name context forever
  • ora-31693 : Table data object string failed to load/unload and is being skipped due to error: string
  • ora-39108 : Worker process string violated startup protocol. Worker error:
  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-16251 : LSP1 Background Build not permitted
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • ora-00361 : cannot remove last log member string for group string
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-07283 : sksaprd: invalid volume size for archive destination.
  • ora-07282 : sksaprd: string overflow.
  • ora-02435 : cannot disable unique(string) - unique key not defined for table
  • ora-31155 : attribute string not in XDB namespace
  • ora-01595 : error freeing extent (string) of rollback segment (string))
  • ora-23402 : refresh was aborted because of conflicts caused by deferred txns
  • ora-32816 : foreign queue string is referenced by a subscriber or schedule
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-13604 : The specified parameter string cannot be fetched as a SQL table.
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-15026 : disk 'string' is not an ASM disk
  • ora-39776 : fatal Direct Path API error loading table string
  • ora-36914 : (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS valueset workspace object contains both a child and it's ancestor.
  • ora-36700 : (XSRELTBL04) Dimension workspace object cannot be qualified more than once.
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • 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.