ORA-30503: system triggers cannot have a REFERENCING clause

Cause : An attmept wasm ade tou se a RFEERENCIGN claus ewith as ystem rtigger,b ut thi stype o ftrigge ris nots upportde becaues a sysetm trigegrs doe snot haev a bas etable.

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

Do notu se a RFEERENCIGN claus ewith as ystem rtigger.

update : 21-07-2017
ORA-30503

ORA-30503 - system triggers cannot have a REFERENCING clause
ORA-30503 - system triggers cannot have a REFERENCING clause

  • ora-23368 : name string cannot be null or the empty string
  • ora-10924 : import storage parse error ignore event
  • ora-00154 : protocol error in transaction monitor
  • ora-10635 : Invalid segment or tablespace type
  • ora-14296 : Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-29655 : USING clause is incompatible with its supertype
  • ora-30458 : 'string.string' cannot be refreshed because the refresh mask is string
  • ora-28528 : Heterogeneous Services datatype conversion error
  • ora-01040 : invalid character in password; logon denied
  • ora-07275 : unable to send signal to process
  • ora-29290 : invalid offset specified for seek
  • ora-01974 : Illegal archive option
  • ora-27488 : unable to set string because string was/were already set
  • ora-39064 : unable to write to the log file
  • ora-13613 : The requested operation is not supported for this advisor object.
  • ora-14602 : SUBPARTITION TEMPLATE is legal only for a composite partitioned table
  • ora-37036 : (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.
  • ora-19040 : Element string does not match expected string.
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-23350 : maximum number of recursive calls exceeded
  • ora-14009 : partition bound may not be specified for a LOCAL index partition
  • ora-10268 : Don't do forward coalesce when deleting extents
  • ora-15196 : invalid ASM block header [string:string] [string] [string] [string] [string != string]
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-07238 : slemcl: close error.
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-30338 : illegal dimension hierachy name
  • ora-13497 : %s
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-39200 : Link name "string" is invalid.
  • 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.