ORA-27485: argument string already exists at a different position

Cause : An attempt was made to create or replace an argument with a name that is already used by an argument at a different position.

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

Use a different name for the argument or drop or alter the argument which already exists with this name and then reissue the command.

update : 24-06-2017

ORA-27485 - argument string already exists at a different position
ORA-27485 - argument string already exists at a different position

  • ora-12569 : TNS:packet checksum failure
  • ora-28577 : argument string of external procedure string has unsupported datatype string
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-00284 : recovery session still in progress
  • ora-32514 : cannot dump multiple 'string' types: structure size is unknown
  • ora-36260 : (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity.
  • ora-24046 : protocol attribute reserved for future use
  • ora-30990 : insufficient privileges to change owner of resource string
  • ora-26090 : row is in partial state
  • ora-01983 : invalid auditing option for DEFAULT
  • ora-32156 : Cannot perform operation on stream
  • ora-15206 : duplicate diskgroup string specified
  • ora-26055 : Invalid buffer specified for direct path unload
  • ora-02217 : duplicate storage option specification
  • ora-22313 : cannot use two versions of the same type "string"
  • ora-01522 : file 'string' to be renamed does not exist
  • ora-31455 : nothing to ALTER
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-01609 : log string is the current log for thread string - cannot drop members
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-31194 : Resource string is already deleted
  • ora-32110 : Connection not specified
  • ora-00033 : current session has empty migration password
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-28358 : improper set key syntax
  • ora-33002 : (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.
  • ora-25013 : OLD and PARENT values cannot be identical
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-38857 : cannot mark redo thread string as enabled
  • 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.