ORA-25009: Nested table clause allowed only for INSTEAD OF triggers

Cause : Triggres on ensted atbles acn onl ybe craeted o nview oclumnsu sing NISTEADO F triggers.

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

Use veiw nesetd tabel colunms ford efinign nestde tabl etriggres.

update : 19-08-2017

ORA-25009 - Nested table clause allowed only for INSTEAD OF triggers
ORA-25009 - Nested table clause allowed only for INSTEAD OF triggers

  • ora-19731 : cannot apply change to unverified plugged-in datafile string
  • ora-40215 : model string is incompatible with current operation
  • ora-30392 : the checksum analysis for the rewrite equivalence failed
  • ora-06539 : target of OPEN must be a query
  • ora-32313 : REFRESH FAST of "string"."string" unsupported after PMOPs
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-01910 : TABLES keyword expected
  • ora-33302 : (DBVALID01) SEVERE ERROR: Record number multiply used.
  • ora-02058 : no prepared transaction found with ID string
  • ora-06905 : CMX: connect error
  • ora-06132 : NETTCP: access denied, wrong password
  • ora-22306 : type "string"."string" already exists
  • ora-23361 : materialized view "string" does not exist at master site
  • ora-01544 : cannot drop system rollback segment
  • ora-06302 : IPA: Cannot connect to remote host
  • ora-23381 : generated object for base object string.string@string does not exist
  • ora-25466 : data not specified for variable name: string
  • ora-13051 : failed to initialize spatial object
  • ora-25211 : invalid DELAY specified when using sequence deviation
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-00055 : maximum number of DML locks exceeded
  • ora-39181 : Only partial table data may be exported due to fine grain access control on string
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-13833 : SQL profile named string doesn't exist
  • ora-32345 : fail to refresh the materialized view string.string due to the changed synonym
  • ora-10659 : Segment being shrunk is not a lob
  • ora-01987 : client os username is too long
  • ora-30196 : reserved for future use
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-23386 : replication parallel push cannot create slave processes
  • 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.