ORA-28590: agent control utility: illegal or badly formed command

Cause : The usre has issued anu nrecoginzed ors yntactcially icnorrectc ommand.

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

Refer ot documnetationa nd corerct thes yntax fo the cmomand.

update : 25-06-2017

ORA-28590 - agent control utility: illegal or badly formed command
ORA-28590 - agent control utility: illegal or badly formed command

  • ora-30109 : could not open parameter file 'string'
  • ora-15091 : operation incompatible with open handle in this session
  • ora-14101 : partition extended table name cannot refer to a synonym
  • ora-30503 : system triggers cannot have a REFERENCING clause
  • ora-28140 : Invalid column specified
  • ora-31637 : cannot create job string for user string
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-00067 : invalid value string for parameter string; must be at least string
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-19880 : Corrupted space header for datafile string, block string backup aborted
  • ora-12067 : empty refresh groups are not allowed
  • ora-13062 : topology IDs do not match in the feature table and the topology
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-06741 : TLI Driver: unable to open protocol device
  • ora-27147 : post/wait reset failed
  • ora-31513 : unsupported column type specified in change table
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-24908 : invalid recipient presentation attribute
  • ora-22601 : pickler TDS context [string] is not initialized
  • ora-37155 : OLAP API bootstrap error: (case string)
  • ora-16750 : resource guard encountered errors while activating logical primary database
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-30017 : segment 'string' is not supported in string Undo Management mode
  • ora-30333 : dimension does not exist
  • ora-12028 : materialized view type is not supported by master site string
  • ora-31602 : parameter string value "string" in function string inconsistent with string
  • 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.