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 : 23-09-2017
ORA-04070

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

  • ora-25230 : invalid value string, WAIT should be non-negative
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-39769 : finish is not allowed with an incompletely loaded last row
  • ora-24237 : object id argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-24021 : queue table definition not imported for string.string
  • ora-10267 : Inhibit KSEDMP for testing
  • ora-16575 : request terminated at broker discretion
  • ora-39109 : Unprivileged users may not operate upon other users' schemas
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-12719 : operation requires database is in RESTRICTED mode
  • ora-31420 : unable to submit the purge job
  • ora-01186 : file string failed verification tests
  • ora-29302 : database is not open clone
  • ora-24143 : invalid evaluation context name
  • ora-24318 : call not allowed for scalar data types
  • ora-13158 : Oracle object string does not exist
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-07477 : scgcmn: lock manager not initialized.
  • ora-30368 : ATTRIBUTE cannot determine column in a different relation
  • ora-14608 : Tablespace was specified for the previous lob segments of column string in template but is not specified for string
  • ora-01910 : TABLES keyword expected
  • ora-00128 : this command requires a dispatcher name
  • ora-18001 : no options specified for ALTER OUTLINE
  • ora-36410 : (VCACHE03) 'number' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'.
  • ora-02220 : invalid MINEXTENTS storage option value
  • ora-32506 : expecting one of string, string, or string but found string
  • 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.