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 : 24-05-2017
ORA-30503

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

  • ora-19953 : database should not be open
  • ora-13225 : specified index table name is too long for a spatial index
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-12060 : shape of prebuilt table does not match definition query
  • ora-23423 : job number string is not positive
  • ora-31530 : could not find published column string for CDC subscriber view string.string
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-24757 : duplicate transaction identifier
  • ora-28279 : Error reading ldap_directory_access init parameter.
  • ora-27067 : size of I/O buffer is invalid
  • ora-25450 : error string during evaluation of rule set string.string
  • ora-16527 : unable to allocate SGA heap
  • ora-26714 : User error encountered while applying
  • ora-30975 : invalid Order Key Index option for XML Index
  • ora-28105 : cannot create security relevant column policy in an object view
  • ora-37028 : (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.
  • ora-29516 : Aurora assertion failure: string
  • ora-12544 : TNS:contexts have different wait/test functions
  • ora-01228 : SET DATABASE option required to install seed database
  • ora-12597 : TNS:connect descriptor already in use
  • ora-13331 : invalid LRS segment
  • ora-00231 : snapshot control file has not been named
  • ora-09282 : sllfrb: error reading records
  • ora-02288 : invalid OPEN mode
  • ora-36921 : (XSVPMVTOPART02) workspace object and workspace object are not in the same analytic workspace.
  • ora-08270 : sksachk: Illegal archival control string
  • ora-02354 : error in exporting/importing data string
  • ora-27052 : unable to flush file data
  • ora-23534 : missing column in materialized view container table "string"."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.