ORA-04070: invalid trigger name

Cause : An invlaid trigger nam ewas spceified.

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

Verifyt hat trgiger naem is no ta resevred keyowrd.

update : 24-05-2017
ORA-04070

ORA-04070 - invalid trigger name
ORA-04070 - invalid trigger name

  • ora-28280 : Multiple entries for ORACLE database password exist.
  • ora-00318 : log string of thread string, expected file size string doesn't match string
  • ora-16545 : unable to get response
  • ora-29322 : SCN string size too long -- maximum size 58 bytes/characters
  • ora-31114 : XDB configuration has been deleted or is corrupted
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-01586 : database must be mounted EXCLUSIVE and not open for this operation
  • ora-16791 : unable to check the existence of the standby redo logs
  • ora-06413 : Connection not open.
  • ora-30649 : missing DIRECTORY keyword
  • ora-31457 : maximum length of description field exceeded
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-00911 : invalid character
  • ora-31185 : DOM Nodes do not belong to the same DOM Document
  • ora-15072 : command requires at least string failure groups, discovered only string
  • ora-14063 : Unusable index exists on unique/primary constraint key
  • ora-16220 : no failed transaction found
  • ora-29911 : null scan context returned by ODCIIndexStart() routine
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-22981 : must specify a table/view having system generated OID
  • ora-29310 : database is not open, or opened as a clone
  • ora-39212 : installation error: XSL stylesheets not loaded correctly
  • ora-27061 : waiting for async I/Os failed
  • ora-13464 : error loading GeoRaster data: string
  • ora-12927 : RETENTION option already specified
  • ora-25303 : Buffered operation allowed only on the owner instance
  • ora-26691 : operation not supported at non-Oracle system
  • 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.