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 : 28-05-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-25315 : unsupported configuration for propagation of buffered messages
  • ora-24850 : failed to startup shared subsystem
  • ora-22608 : cannot add an attribute to the already generated image handle
  • ora-14173 : illegal subpartition-extended table name syntax
  • ora-01332 : internal Logminer Dictionary error
  • ora-17509 : Attempt to do i/o beyond block1 offset
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-32306 : updatable materialized views with user-defined types must use SELECT *
  • ora-29822 : selectivity cannot be specified for the type of object
  • ora-14258 : invalid partition description
  • ora-27480 : window "string" is currently open
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-25966 : join index cannot be based on an index organized table
  • ora-02163 : invalid value for FREELIST GROUPS
  • ora-39219 : directory object name is too long
  • ora-01185 : logfile group number string is invalid
  • ora-00363 : log is not the archived version
  • ora-19670 : file string already being restored
  • ora-01096 : program version (string) incompatible with instance (string)
  • ora-29876 : failed in the execution of the ODCIINDEXDELETE routine
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-09846 : soacon: ARCH unable to open named pipe.
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-02063 : preceding stringstring from stringstring
  • ora-02143 : invalid STORAGE option
  • ora-30089 : missing or invalid
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-09879 : sstascre/sstasat: shmat error, unable to attach tas read page
  • ora-30686 : no dispatcher accepted TCP/IP connection request
  • ora-19284 : Encoding specification in version declaration not supported
  • 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.