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 : 30-04-2017

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

  • ora-22868 : table with LOBs contains segments in different tablespaces
  • ora-01334 : invalid or missing logminer dictionary processes context
  • ora-29284 : file read error
  • ora-36958 : (XSFCAST26) The OFFSET value for cycle number cannot be greater than the cycle's PERIODICITY, which is number. You specified number.
  • ora-25222 : enqueue failed, complete sender info. not provided for a queue supporting non-repudiation
  • ora-27015 : skgfcls: failed to close the file
  • ora-07633 : smsdbp: illegal protection value
  • ora-19924 : there are no row with id string
  • ora-19242 : XQ0022 - namespace declaration attribute must be a literal
  • ora-24321 : inconsistent parameters passed
  • ora-23301 : mixed use of deferred rpc destination modes
  • ora-24317 : define handle used in a different position
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-01497 : illegal option for ANALYZE CLUSTER
  • ora-26738 : %s 'string' is not empty
  • ora-30005 : missing or invalid WAIT interval
  • ora-33012 : (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
  • ora-22317 : typecode number is not legal as a number type
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-30177 : invalid flag used in a format specification
  • ora-28264 : Client identifier is too long
  • ora-16793 : logical standby database guard is unexpectedly off
  • ora-31155 : attribute string not in XDB namespace
  • ora-10930 : trace name context forever
  • ora-25408 : can not safely replay call
  • ora-00912 : input parameter too long
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-40204 : model string already exists
  • ora-13772 : unexpected deadlock on "SQL Tuning Set" "string" owned by user "string"
  • ora-32590 : log group specification not allowed here
  • 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.