ORA-13828: generated SQL profile name string already exists

Cause : A SQL profile already exists with the name generated by the system.

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

Retry the operation as the generated name is time sensitive.

update : 25-06-2017

ORA-13828 - generated SQL profile name string already exists
ORA-13828 - generated SQL profile name string already exists

  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-01541 : system tablespace cannot be brought offline; shut down if necessary
  • ora-33008 : (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.
  • ora-16742 : the standby database "string" has exhausted its quota
  • ora-15194 : Internal ASM-DB interaction testing event number 15194
  • ora-12350 : database link being dropped is still mounted
  • ora-12482 : internal MLS error: string Error: string
  • ora-30960 : The entity is neither an XPATH nor a NAMESPACE.
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-19861 : additional backup pieces cannot be validated in this conversation
  • ora-08453 : more than one V symbol specified in picture mask
  • ora-31218 : DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn.
  • ora-02728 : osnfop: access error on oracle executable
  • ora-01108 : file string is in backup or media recovery
  • ora-13008 : the specified date format has an invalid component
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-01293 : mounted database required for specified LogMiner options
  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-16706 : no resource guard is available
  • ora-32592 : all columns in log group can not be no log columns
  • ora-14514 : LOCAL option not valid without subpartition name
  • ora-12625 : TNS:missing argument
  • ora-07704 : error in archive text: need ':' after device name
  • ora-32302 : object materialized views must be object ID based
  • ora-19560 : %s is not a valid device limit
  • ora-07640 : smsget: SGA not yet valid. Initialization in progress
  • ora-22312 : must specify either CASCADE or INVALIDATE option
  • ora-24203 : operation failed, queue table string.string has errors
  • ora-00485 : DIAG process terminated with error string
  • ora-39706 : schema 'string' not found
  • 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.