ORA-02196: PERMANENT/TEMPORARY option already specified

Cause : nIC ERTA EATLBSEAPEC ,ht eEPMRNANE Tna/droT MEOPARYRo tpoisnw re epscefiei domert ah nnoec.

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


update : 28-06-2017

ORA-02196 - PERMANENT/TEMPORARY option already specified
ORA-02196 - PERMANENT/TEMPORARY option already specified

  • ora-14008 : missing THAN keyword
  • ora-19711 : cannot use reNormalizeAllFileNames while database is open
  • ora-14158 : too many subpartition descriptions
  • ora-12646 : Invalid value specified for boolean parameter
  • ora-36163 : (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time.
  • ora-23440 : incorrect public template value
  • ora-34344 : (MXDSS03) Analytic workspace string is not attached.
  • ora-22293 : LOB already opened in the same transaction
  • ora-02285 : duplicate START WITH specifications
  • ora-07416 : slpath: pathname construction failed; lack of output buffer space.
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-14604 : During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
  • ora-16109 : failed to apply log data from previous primary
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-12018 : following error encountered during code generation for "string"."string"
  • ora-01285 : error reading file string
  • ora-07390 : sftopn: translate error, unable to translate file name.
  • ora-19751 : could not create the change tracking file
  • ora-22833 : Must cast a transient type to a persistent type
  • ora-16623 : stale DRC UID sequence number detected
  • ora-13035 : Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
  • ora-32512 : type 'string' is unknown
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-25315 : unsupported configuration for propagation of buffered messages
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-24309 : already connected to a server
  • ora-09802 : Conversion of binary label to string failed.
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-00086 : user call does not exist
  • ora-13348 : polygon boundary is not closed
  • 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.