ORA-27454: argument name and position cannot be NULL

Cause : The name or position of a program or job argument was defined as NULL.

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

Reissue the command providing either a valid argument name or valid argument position.

update : 20-08-2017
ORA-27454

ORA-27454 - argument name and position cannot be NULL
ORA-27454 - argument name and position cannot be NULL

  • ora-12088 : cannot online redefine table "string"."string" with unsupported datatype
  • ora-16068 : redo log file activation identifier mismatch
  • ora-16713 : the resource guard timed out while servicing the request
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-24091 : Destination queue string is the same as the source queue
  • ora-33002 : (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.
  • ora-30044 : 'Retention' can only specified for undo tablespace
  • ora-19679 : RMAN configuration number string is outside valid range of 1 through string
  • ora-13021 : element not continuous
  • ora-28115 : policy with check option violation
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-28363 : buffer provided not large enough for output
  • ora-31464 : target table for the change table no longer exists
  • ora-24811 : less data provided for writing than indicated
  • ora-29278 : SMTP transient error: string
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • ora-07471 : snclrd: name translation error of sgadef.dbf file name.
  • ora-30087 : Adding two datetime values is not allowed
  • ora-31631 : privileges are required
  • ora-25502 : concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
  • ora-12426 : invalid audit option
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-36861 : (XSTFRC01) SQL Cache ID parameter is invalid or missing.
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • ora-19620 : %s is not of string type
  • ora-07636 : smsdbp: $MGBLSC failure
  • ora-16812 : log apply service not running on apply instance recorded by the broker
  • ora-18001 : no options specified for ALTER OUTLINE
  • ora-13835 : invalid attribute name specified
  • ora-23497 : repgroup name cannot be null
  • 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.