ORA-25473: cannot store string in rule action context

Cause : The user attempted to put unsupported data types, such as LOBs and evolved ADTs, into the rule action context.

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

Use only supported data types in rule action context.

update : 27-06-2017

ORA-25473 - cannot store string in rule action context
ORA-25473 - cannot store string in rule action context

  • ora-24810 : attempting to write more data than indicated
  • ora-36666 : (XSDPART04) workspace object is not a concat dimension.
  • ora-06530 : Reference to uninitialized composite
  • ora-38858 : cannot mark redo thread string as enabled
  • ora-01947 : TEMPORARY TABLESPACE already specified
  • ora-07507 : scgcm: unexpected lock status condition
  • ora-15170 : cannot add entry 'string' in directory 'string'
  • ora-00475 : TRWR process terminated with error
  • ora-06778 : TLI Driver: error sending ccode
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-36402 : (XSSPROP03) The property '$string' requires a leading "$" because it is a system-reserved property name.
  • ora-14635 : only one resulting subpartition can be specified for MERGE SUBPARTITIONS
  • ora-02217 : duplicate storage option specification
  • ora-16772 : error switching over between primary and standby databases
  • ora-19725 : can not acquire plug-in enqueue
  • ora-16246 : User initiated abort apply successfully completed
  • ora-31606 : XML context number does not match any previously allocated context
  • ora-24435 : Invalid Service Context specified.
  • ora-16509 : the request timed out
  • ora-30113 : error when processing file 'string'
  • ora-33429 : (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT.
  • ora-22153 : source variable-length array is not initialized
  • ora-32505 : too many watchpoints
  • ora-01162 : block size string in file header does not match configured block sizes
  • ora-26516 : no push transaction acknowledgement
  • ora-23317 : a communication failure has occurred
  • ora-19117 : invalid redefinition of predefined namespace prefix 'string'
  • ora-32615 : incorrect use of MODEL IS ANY predicate
  • ora-07446 : sdnfy: bad value 'string' for parameter string.
  • ora-15109 : conflicting protection attributes specified
  • 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.