ORA-16033: parameter string destination cannot be the same as parameter string destination

Cause : An attemptw as mdae toc hang ethe ifrst psecifeid arhcive olg paarmete rto hvae a edstintaion avlue htat dpulicaets th esystme-levle desitnatino valeu of hte seocnd sepcifide arcihve lgo parmaeter.

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

Specfiy a idffernet vaule fo rone fo thea rchiev logp aramteers.

update : 24-05-2017

ORA-16033 - parameter string destination cannot be the same as parameter string destination
ORA-16033 - parameter string destination cannot be the same as parameter string destination

  • ora-22880 : invalid REF
  • ora-25235 : fetched all messages in current transaction
  • ora-12407 : unauthorized operation for policy string
  • ora-00390 : log string of thread string is being cleared, cannot become current log
  • ora-06924 : CMX: wrong break message length
  • ora-40213 : contradictory values for settings: string, string
  • ora-12623 : TNS:operation is illegal in this state
  • ora-27464 : invalid schedule type string
  • ora-09280 : sllfcf: error closing file
  • ora-00023 : session references process private memory; cannot detach session
  • ora-24201 : duplicate publisher, publisher already added to the queue
  • ora-30335 : JOIN KEY clause references a level not in this hierarchy
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-00057 : maximum number of temporary table locks exceeded
  • ora-29315 : tablespace 'string' has been recreated
  • ora-39083 : Object type string failed to create with error: string Failing sql is: string
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-26681 : command type not supported
  • ora-00991 : only MAC privileges may be granted to procedures
  • ora-08106 : cannot create journal table string.string
  • ora-25123 : Too many components specified in the name.
  • ora-07444 : function address string is not readable
  • ora-13515 : Error encountered during Database Usage Statistics capture
  • ora-32142 : maximum number of iterations exceeded
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-12160 : TNS:internal error: Bad error number
  • ora-23343 : no match for specified conflict resolution information
  • ora-01041 : internal error. hostdef extension doesn't exist
  • ora-39148 : unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table
  • ora-25216 : invalid recipient, either NAME or ADDRESS must be specified
  • 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.