ORA-19596: SPFILE already included

Cause : The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE.

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

No action required - the conversation is still active, and more files can be specified.

update : 29-06-2017

ORA-19596 - SPFILE already included
ORA-19596 - SPFILE already included

  • ora-22340 : cannot string type "string"."string". Dependent tables must be upgraded to latest version
  • ora-25242 : cannot change subscriber name from string to string without FIRST_MESSAGE option
  • ora-02189 : ON required
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-16060 : Log file is current
  • ora-01206 : file is not part of this database - wrong database id
  • ora-00029 : session is not a user session
  • ora-38704 : Checksum error in flashback database log file header.
  • ora-38778 : Restore point 'string' already exists.
  • ora-31069 : Cannot apply typed changes to non-schema-based XMLType nodes
  • ora-32161 : Cannot perform piecewise fetch
  • ora-19753 : error writing to change tracking file
  • ora-27503 : IPC error attempting to cancel request
  • ora-01157 : cannot identify/lock data file string - see DBWR trace file
  • ora-07218 : slkhst: could not perform host operation
  • ora-19110 : unsupported XQuery expression
  • ora-02306 : cannot create a type that already has valid dependent(s)
  • ora-08193 : Flashback Table operation is not allowed on temporary tables
  • ora-00452 : foreground process unexpectedly terminated with error string
  • ora-24069 : cannot downgrade queue table string while it is being upgraded
  • ora-29321 : too many datafiles added since the point-in-time
  • ora-21607 : memory cartridge service handle not initialized
  • ora-37008 : (AWLISTALL06) number writers
  • ora-12165 : TNS:Trying to write trace file into swap space.
  • ora-30060 : Internal event for RECO tracing
  • ora-14076 : submitted alter index partition/subpartition operation is not valid for local partitioned index
  • ora-10644 : SYSTEM tablespace cannot be default temporary tablespace
  • ora-31401 : change source string is not an existing change source
  • ora-13190 : recursive SQL fetch failed
  • ora-32102 : invalid OCI handle
  • 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.