ORA-36952: (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.

Cause : Ac ylcen ubme rwsa pseicfeidi na acl lt oFQCUREYt or ertiveef oercsatd aat ontr ealtde ot accyl.e

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

Rmeoev htec ylces pceiifctaino rfo mteh acl lt oFQCUREY.

update : 24-04-2017

ORA-36952 - (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
ORA-36952 - (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.

  • ora-00610 : Internal error code
  • ora-00207 : control files are not for the same database
  • ora-27453 : %s is an invalid job or program argument name.
  • ora-07216 : slghst: gethostname error, unable to get name of current host.
  • ora-00259 : log string of open instance string (thread string) is the current log, cannot archive
  • ora-06762 : TLI Driver: error reading orderly release
  • ora-19761 : block size string is not valid for change tracking file
  • ora-07490 : scgrcl: cannot convert lock.
  • ora-02282 : duplicate or conflicting ORDER/NOORDER specifications
  • ora-13705 : There was a instance shutdown/startup between the snapshots in the range [string, string].
  • ora-28112 : failed to execute policy function
  • ora-01304 : subordinate process error. Check alert and trace logs
  • ora-06316 : IPA: Invalid database SID
  • ora-30393 : a query block in the statement did not rewrite
  • ora-15033 : disk 'string' belongs to diskgroup "string"
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-13918 : Updating system alert with reason_id string failed; previous alert not found
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-24504 : data length larger than expected
  • ora-30733 : cannot specify rowid constraint on scoped ref column
  • ora-16042 : user requested cancel immediate of managed recovery operation
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-01598 : rollback segment 'string' is not online
  • ora-24032 : object string exists, index could not be created for queue table string
  • ora-16133 : Datafile string has incorrect terminal recovery stamp.
  • ora-31655 : no data or metadata objects selected for job
  • ora-06018 : NETASY: message send failure
  • 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.