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 : 26-06-2017
ORA-25009

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

  • ora-13625 : %s is an invalid advisor object type.
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-14188 : sub-partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-10915 : TABLESPACE GROUP cannot be specified for this type of tablespace
  • ora-09762 : sNeXT_instanceName: translation error.
  • ora-22909 : exceeded maximum VARRAY limit
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-12351 : cannot create view using a remote object which has a remote object reference
  • ora-14616 : table is not subpartitioned by List method
  • ora-33425 : (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file.
  • ora-02761 : File number to be canceled is negative.
  • ora-14069 : invalid TABLESPACE_NUMBER value
  • ora-19729 : File string is not the initial version of the plugged in datafile
  • ora-12669 : Shared server: outbound protocol does not support proxies
  • ora-12663 : Services required by client not available on the server
  • ora-07620 : smscre: illegal database block size
  • ora-16132 : An error occurred during activation of the standby.
  • ora-30695 : JDWP message format problem
  • ora-13607 : The specified task or object string already exists
  • ora-09948 : Process information label retrieval failed.
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-19161 : XP0004 - XQuery type mismatch: invalid argument type 'string' for function 'string'
  • ora-02780 : Name given for the core dump directory is invalid
  • ora-23376 : node string is not compatible with replication version "string"
  • ora-39113 : Unable to determine database version
  • ora-00832 : no streams pool created and cannot automatically create one
  • 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.