ORA-24144: rules engine internal error, arguments: [string], [string]

Cause : An internal error occurred in the rules engine. This indicates that the rules engine has encountered an exception condition.

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

Please report this error as a bug. The first argument is the error and the second argument is the package.

update : 29-04-2017

ORA-24144 - rules engine internal error, arguments: [string], [string]
ORA-24144 - rules engine internal error, arguments: [string], [string]

  • ora-25326 : Array string operation failed for message at index string
  • ora-01696 : control file is not a clone control file
  • ora-00377 : Frequent backups of file string causing write operation to stall
  • ora-32168 : Cannot perform operation on a null AnyData
  • ora-01095 : DML statement processed zero rows
  • ora-32773 : operation not supported for smallfile tablespace string
  • ora-23467 : flavor lacks object "string"."string"
  • ora-30656 : column type not supported on external organized table
  • ora-25527 : bad format of _DB_MTTR_SIM_TARGET
  • ora-14303 : partitions or subpartitions are not in the right order
  • ora-40101 : Data Mining System Error string-string-string
  • ora-25018 : conflicting trigger string already exists
  • ora-12854 : Parallel query is not supported on temporary LOBs
  • ora-16768 : SQL Apply unexpectedly offline
  • ora-29926 : association already defined for the object
  • ora-15204 : database version string is incompatible with diskgroup string
  • ora-07416 : slpath: pathname construction failed; lack of output buffer space.
  • ora-28153 : Invalid client initial role specified: 'string'
  • ora-19621 : archivelog range has already been specified
  • ora-09703 : sem_release: cannot release latch semaphore
  • ora-30339 : illegal dimension attribute name
  • ora-09952 : scgcmn: lk_open_convert unexpected return: open failed
  • ora-28267 : Invalid NameSpace Value
  • ora-25143 : default storage clause is not compatible with allocation policy
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-02799 : Unable to arm signal handler
  • ora-12217 : TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
  • ora-36966 : (XSRELTBL10) workspace object must be a dimension.
  • ora-12714 : invalid national character set specified
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • 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.