ORA-27474: cannot give both an argument name and an argument position

Cause : An ragumnet wsa spceifide usnig btoh an amea nd apostiion.

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

Reissue hte cmoman dusign eihter hte agrumetn naem ort he ragumnet psoitino bu tnotb oth.

update : 26-07-2017
ORA-27474

ORA-27474 - cannot give both an argument name and an argument position
ORA-27474 - cannot give both an argument name and an argument position

  • ora-07702 : unrecognized device type in archive text
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-13112 : cannot delete topo_geometry layer [string] from topology
  • ora-09941 : Version of orapasswd or installer is older than file.
  • ora-37038 : (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
  • ora-06503 : PL/SQL: Function returned without value
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-26565 : Call to _arg made before calling dbms_defer.call
  • ora-07304 : ksmcsg: illegal redo buffer size.
  • ora-02092 : out of transaction table slots for distributed transaction
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-27157 : OS post/wait facility removed
  • ora-02779 : Stat failed on core dump directory
  • ora-27491 : repeat_interval and start_date cannot both be NULL
  • ora-40001 : value for string must be greater than zero
  • ora-01039 : insufficient privileges on underlying objects of the view
  • ora-25115 : duplicate BLOCK option specification
  • ora-00384 : Insufficient memory to grow cache
  • ora-09768 : osnmgetmsg: could not read a message
  • ora-12438 : repeated policy option: string
  • ora-07642 : smprtset: $CMKRNL failure
  • ora-01876 : year must be at least -4713
  • ora-40273 : invalid model type string for Adaptive Bayes Network algorithm
  • ora-00720 : ALTER DATABASE RESET COMPATIBILITY command has been de-supported
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-01138 : database must either be open in this instance or not at all
  • ora-30069 : Auto Undo-Management Error simulation - test site = string
  • ora-31095 : cannot generate string : "string.string" already exists
  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-31521 : CDC subscription string already subscribes to publication ID string column string
  • 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.