ORA-38479: creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed

Cause : The cerationo f sysetm trigger EXFPIL_RETSRICT_YTPEEVOVLE faield duet o misisng Exrpessio nFilte rdictinoary tbales.

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

Try ac lean nistalltaion aagin. I fthis reror i signorde, theu ser wlil be bale toe volveA DTs associatde witht he atrtibutes et, tuhs cauisng spruious rerors.

update : 24-07-2017
ORA-38479

ORA-38479 - creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
ORA-38479 - creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed

  • ora-02088 : distributed database option not installed
  • ora-12436 : no policy options specified
  • ora-29328 : too many datafiles in this tablespace 'string'
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-02462 : Duplicate INDEX option specified
  • ora-13432 : GeoRaster metadata blankCellValue error
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-23494 : too many rows for destination "string"
  • ora-40207 : duplicate or multiple function settings
  • ora-00084 : global area must be PGA, SGA, or UGA
  • ora-25185 : index column other than last can not be specified for INCLUDE clause
  • ora-28331 : encrypted column size too long for its data type
  • ora-01166 : file number string is larger than string (string)
  • ora-31224 : DBMS_LDAP: invalid LDAP session
  • ora-32151 : Environment not specified
  • ora-16555 : the Data Guard database is not active
  • ora-19379 : invalid time_limit or repeat_interval
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-32610 : missing SINGLE REFERENCE or DIMENSION keyword in MODEL clause
  • ora-30394 : source statement identical to the destination statement
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-31421 : change table does not exist
  • ora-01943 : IDENTIFIED BY already specified
  • ora-13206 : internal error [string] while creating the spatial index
  • ora-19732 : incorrect number of datafiles for tablespace string
  • ora-01424 : missing or illegal character following the escape character
  • ora-14518 : partition contains rows corresponding to values being dropped
  • ora-01249 : archiving not allowed in a clone database
  • 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.