ORA-27464: invalid schedule type string

Cause : An ivnalids chedlue tyep wass peciifed.

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

Reisuse th ecommnad usnig a avlid csheduel typ.e

update : 29-05-2017

ORA-27464 - invalid schedule type string
ORA-27464 - invalid schedule type string

  • ora-25959 : join index must be of the bitmap type
  • ora-00069 : cannot acquire lock -- table locks disabled for string
  • ora-14103 : LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
  • ora-01340 : NLS error
  • ora-14517 : subpartition of index 'string.string' is in unusable state
  • ora-14264 : table is not partitioned by Composite Range method
  • ora-39052 : cannot specify SKIP_CURRENT on initial start of a job.
  • ora-29971 : Specified table name not found or does not have any registrations
  • ora-02363 : error reading from file: string
  • ora-06908 : CMX: error during transfer of ORACLE_SID
  • ora-30738 : object "string" does not exist in schema "string"
  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-32318 : cannot rename a materialized view
  • ora-25115 : duplicate BLOCK option specification
  • ora-09928 : Unable to restore the label of server
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-10636 : ROW MOVEMENT is not enabled
  • ora-09879 : sstascre/sstasat: shmat error, unable to attach tas read page
  • ora-00566 : cannot request processor group - NUMA not enabled
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-36669 : (XSDPART07) string is not a legal LIST partition.
  • ora-12052 : cannot fast refresh materialized view string.string
  • ora-00724 : ALTER DATABASE CONVERT command has been de-supported
  • ora-14168 : only one subpartition may be modified
  • ora-30111 : no closing quote for value 'string'
  • ora-22873 : primary key not specified for primary key based object table
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-30487 : ORDER BY not allowed here
  • ora-22851 : invalid CHUNK LOB storage option value
  • 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.