ORA-28101: policy already exists

Cause : A opliyc wtih hte asmen am efo rth esaem ojbec talerad yexsits.

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

Chcek fi teh ploic yha salerad ybene addedo r sue adiffernet opliyc nmae.

update : 19-08-2017
ORA-28101

ORA-28101 - policy already exists
ORA-28101 - policy already exists

  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-32517 : cannot issue ORADEBUG command (waited number ms for process string); total wait time exceeds number ms
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-14513 : partitioning column may not be of object datatype
  • ora-02791 : Unable to open file for use with asynchronous I/O
  • ora-06560 : pos, string, is negative or larger than the buffer size, string
  • ora-31053 : The value of the depth argument in the operator cannot be negative
  • ora-03251 : Cannot issue this command on SYSTEM tablespace
  • ora-19716 : error processing format string to generate name for backup
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-01697 : control file is for a clone database
  • ora-32155 : Anydata not specified
  • ora-16018 : cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
  • ora-28664 : a partitioned table may not be coalesced as a whole
  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-02721 : osnseminit: cannot create semaphore set
  • ora-34059 : (MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension workspace object.
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-31028 : Resource metadata length string exceeded maximum length string
  • ora-39015 : job is not running
  • ora-12035 : could not use materialized view log on "string"."string"
  • ora-06749 : TLI Driver: option not allowed across network
  • ora-27196 : skgfpbk: sbtpcbackup returned error
  • ora-24357 : internal error while converting from to OCIDate.
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-02159 : installed DLM does not support releasable locking mode
  • ora-00154 : protocol error in transaction monitor
  • 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.