ORA-27470: failed to re-enable "string.string" after making requested change

Cause : A change was made to an enabled scheduler object that caused it to become disabled.

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

Alter the object so that it becomes valid and then enable it.

update : 28-06-2017
ORA-27470

ORA-27470 - failed to re-enable "string.string" after making requested change
ORA-27470 - failed to re-enable "string.string" after making requested change

  • ora-30131 : number of keys being set exceeds allocation
  • ora-36680 : (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
  • ora-12725 : unmatched parentheses in regular expression
  • ora-13498 : %s
  • ora-00273 : media recovery of direct load data that was not logged
  • ora-06524 : Unsupported option : string
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-32809 : foreign queue string is already registered
  • ora-01059 : parse expected before a bind or execute
  • ora-13362 : disjoint sub-element in a compound polygon
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-24017 : cannot enable enqueue on QUEUE, string is an exception queue
  • ora-30045 : No undo tablespace name specified
  • ora-30566 : Index maintainence clause not allowed for this command
  • ora-39167 : Tablespace string was not found.
  • ora-27472 : invalid metadata attribute string
  • ora-14013 : duplicate partition name
  • ora-32841 : invalid value for property string
  • ora-39301 : schema "string" does not exist or is in use
  • ora-16212 : number processes specified for APPLY is too great
  • ora-01637 : rollback segment 'string' is being used by another instance (#string)
  • ora-06010 : NETASY: dialogue file too long
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-01548 : active rollback segment 'string' found, terminate dropping tablespace
  • ora-09857 : smprset: vm_protect error while protecting pga.
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-33911 : (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
  • ora-32821 : subscriber queue and exception queue must have same payload type
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-12843 : pdml lock not held properly on the table
  • 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.