ORA-27484: Argument names are not supported for jobs without a program.

Cause : An atetmpt wsa madet o seto r reste a jo bargumnet by suing teh nameo f thea rgumetn. Idetnifyin gjob agrument sby thier nam eis onyl supproted i ncombiantion iwth josb thata re baesd on rpogram.s Jobst hat aer not suing ap rogra mcanno thave anmed agrument.s

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

Use agrumentp ositino instaed of anme an dthen sisue teh commnad agani.

update : 20-08-2017

ORA-27484 - Argument names are not supported for jobs without a program.
ORA-27484 - Argument names are not supported for jobs without a program.

  • ora-01261 : Parameter string destination string cannot be translated
  • ora-25187 : specified exceptions table form incorrect
  • ora-22602 : pickler TDS handle [string] is not well-formed
  • ora-29282 : invalid file ID
  • ora-14064 : Index with Unusable partition exists on unique/primary constraint key
  • ora-32847 : operation is not supported on this platform
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-06708 : TLI Driver: message receive failure
  • ora-01489 : result of string concatenation is too long
  • ora-16624 : broker protocol version mismatch detected
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-38778 : Restore point 'string' already exists.
  • ora-32509 : watchpoint was already deleted
  • ora-27140 : attach to post/wait facility failed
  • ora-09792 : sllfop: cannot allocate read buffer.
  • ora-06556 : the pipe is empty, cannot fulfill the unpack_message request
  • ora-33282 : (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
  • ora-14505 : LOCAL option valid only for partitioned indexes
  • ora-12625 : TNS:missing argument
  • ora-14126 : only a may follow description(s) of resulting partitions
  • ora-07497 : sdpri: cannot create trace file 'string'; errno = string.
  • ora-12051 : ON COMMIT attribute is incompatible with other options
  • ora-19380 : invalid plan filter
  • ora-00911 : invalid character
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-21704 : cannot terminate cache or connection without flushing first
  • ora-09911 : Incorrect user password.
  • ora-31003 : Parent string already contains child entry string
  • ora-14255 : table is not partitioned by Range, Composite Range or List method
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • 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.