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 : 29-04-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-24433 : This statement has already been prepared using OCIStmtPrepare2.
  • ora-16625 : cannot reach the database
  • ora-32633 : MODEL subquery FOR cell index returns too many rows
  • ora-19707 : invalid record block number - string
  • ora-23605 : invalid value "string" for STREAMS parameter string
  • ora-24307 : invalid length for piece
  • ora-31605 : the following was returned from string in routine string: LPX-number: string
  • ora-07742 : slemop: $CONNECT failure
  • ora-07650 : sigunc: $GETJPIW failure
  • ora-10647 : Tablespace other than SYSTEM, string, string not found in read only mode
  • ora-06766 : TLI Driver: close failed during release
  • ora-19006 : XMLType TYPE storage option not appropriate for storage type
  • ora-27144 : attempt to kill process failed
  • ora-26718 : transaction limit reached
  • ora-25141 : invalid EXTENT MANAGEMENT clause
  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-12400 : invalid argument to facility error handling
  • ora-08183 : Flashback cannot be enabled in the middle of a transaction
  • ora-16567 : Data Guard broker internal parser error at "string"
  • ora-14060 : data type or length of a table partitioning column may not be changed
  • ora-12480 : specified clearance labels not within the effective clearance
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-16409 : Archive log switchover reference number mismatch
  • ora-13510 : invalid RETENTION string, must be in the range (string, string)
  • ora-29345 : cannot plug a tablespace into a database using an incompatible character set
  • ora-29533 : attempt to overwrite class or resource string while defining or compiling string.string
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-27214 : skgfrsfe: file search failed
  • ora-38758 : cannot flashback data file string; restored since last recovery
  • ora-24337 : statement handle not prepared
  • 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.