ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers

Cause : WHEN clause is specified in an INSTEAD OF trigger.

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

Remove the WHEN clause when creating an INSTEAD OF trigger.

update : 23-07-2017
ORA-25004

ORA-25004 - WHEN clause is not allowed in INSTEAD OF triggers
ORA-25004 - WHEN clause is not allowed in INSTEAD OF triggers

  • ora-07274 : spdcr: access error, access to oracle denied.
  • ora-13436 : GeoRaster metadata dimensionSize error
  • ora-26035 : Error attempting to encrypt or decrypt column
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-01233 : file string is read only - cannot recover using backup control file
  • ora-02750 : osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf
  • ora-00051 : timeout occurred while waiting for a resource
  • ora-32108 : max column or parameter size not specified
  • ora-31617 : unable to open dump file "string" for write
  • ora-00355 : change numbers out of order
  • ora-22336 : table contained 8.0 image format, must specify INCLUDING DATA
  • ora-16544 : modifying DG_BROKER_START requires SID='*' qualifier
  • ora-29830 : operator does not exist
  • ora-28112 : failed to execute policy function
  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-01925 : maximum of string enabled roles exceeded
  • ora-32550 : Replacement occured despite hint to the contrary
  • ora-02760 : Client close of file failed.
  • ora-25269 : cant specify sognature with get signature option
  • ora-22279 : cannot perform operation with LOB buffering enabled
  • ora-24231 : database access descriptor (DAD) string not found
  • ora-14275 : cannot reuse lower-bound partition as resulting partition
  • ora-22913 : must specify table name for nested table column or attribute
  • ora-01900 : LOGFILE keyword expected
  • ora-01742 : comment not terminated properly
  • ora-10920 : Cannot offline tablespace belonging to default temporary tablespace group
  • ora-23487 : object groups "string"."string" and "string"."string" do not have the same connection qualifier
  • ora-19016 : attributes cannot occur after element specifications
  • ora-28154 : Proxy user may not act as client 'string'
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • 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.