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-04-2017
ORA-13829

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

  • ora-14002 : only one GLOBAL clause may be specified
  • ora-24132 : table name string is too long
  • ora-25353 : branch marked for deletion
  • ora-01692 : unable to extend lob segment string.string partition string by string in tablespace string
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-31642 : the following SQL statement fails: string
  • ora-22310 : ALTER TYPE error. Refer to table "string"."string" for errors
  • ora-02069 : global_names parameter must be set to TRUE for this operation
  • ora-09986 : wrong number of bytes read from SGA definition file
  • ora-27470 : failed to re-enable "string.string" after making requested change
  • ora-12666 : Dedicated server: outbound transport protocol different from inbound
  • ora-16246 : User initiated abort apply successfully completed
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-00294 : invalid archivelog format specifier 'string'
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-39076 : cannot delete job string for user string
  • ora-06979 : X.25 Driver: server cannot start oracle
  • ora-19590 : conversation already active
  • ora-31901 : the current operation was cancelled by the user
  • ora-28658 : This operation is supported only for Index-Organized tables
  • ora-40217 : priors table mismatched with training data
  • ora-16748 : resource guard encountered errors during database open
  • ora-02034 : speed bind not permitted
  • ora-26045 : REF column string expects string arguments; found string.
  • ora-16009 : remote archive log destination must be a STANDBY database
  • ora-10932 : trace name context forever
  • ora-32059 : deadlock detected on mapping structures
  • ora-12055 : materialized view definition contains cyclic dependencies with existing materialized views
  • ora-36692 : (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [levelorder lovs] [inhierarchy {variable | valueset}].
  • 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.