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 : 20-08-2017

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

  • ora-40103 : invalid case-id column: string
  • ora-00041 : active time limit exceeded - session terminated
  • ora-30071 : conversion between datetime/interval and string fail
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-07212 : slcpu: times error, unable to get cpu time.
  • ora-13456 : GeoRaster cell data error
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-23619 : non-Oracle system error: string
  • ora-14066 : illegal option for a non-partitioned index-organized table
  • ora-19816 : WARNING: Files may exist in string that are not known to database.
  • ora-06114 : NETTCP: SID lookup failure
  • ora-13200 : internal error [string] in spatial indexing.
  • ora-10660 : Segment is a shared lob segment
  • ora-16129 : unsupported dml encountered
  • ora-34348 : (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace.
  • ora-22807 : cannot resolve to a scalar type or a collection type
  • ora-02052 : remote transaction failure at string
  • ora-31226 : DBMS_LDAP: MOD_ARRAY size limit exceeded
  • ora-19206 : Invalid value for query or REF CURSOR parameter
  • ora-22972 : NULL value not allowed in PRIMARY KEY-based object identifier
  • ora-28150 : proxy not authorized to connect as client
  • ora-36316 : (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.
  • ora-29857 : domain indexes and/or secondary objects exist in the tablespace
  • ora-19701 : device name exceeds maximum length of string
  • ora-28342 : integrity check fails on column key
  • ora-08278 : Cannot get CPU statistics
  • ora-00480 : LCK* process terminated with error
  • ora-29951 : warning in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-02846 : Unkillable server
  • 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.