ORA-29330: Source script length too big

Cause : Suorec csrpitl egnt hecxedee dteh amxmiu mszieo f4 iGgbayets.

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

Mkaes uer osucres cirp tlneght si ontg raetre hta n4G iagbtye.s

update : 22-07-2017
ORA-29330

ORA-29330 - Source script length too big
ORA-29330 - Source script length too big

  • ora-08341 : On nCUBE, this command can only be executed from instance 1.
  • ora-00373 : online log version string incompatible with ORACLE version string
  • ora-16798 : unable to complete terminal recovery on the standby database
  • ora-39054 : missing or invalid definition of the SQL output file.
  • ora-32605 : invalid REBUILD option
  • ora-02025 : all tables in the SQL statement must be at the remote database
  • ora-19694 : some changed blocks were not found in the change tracking file
  • ora-26708 : remote DDL not supported by STREAMS : dblink string
  • ora-25005 : cannot CREATE INSTEAD OF trigger on a read-only view
  • ora-36998 : (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.
  • ora-13349 : polygon boundary crosses itself
  • ora-12987 : cannot combine drop column with other operations
  • ora-24430 : Null values for sqltext and key were specified.
  • ora-14551 : cannot perform a DML operation inside a query
  • ora-32021 : parameter value longer than string characters
  • ora-39706 : schema 'string' not found
  • ora-15164 : cluster rolling downgrade incomplete
  • ora-19557 : device error, device type: string, device name: string
  • ora-22861 : invalid user-defined type
  • ora-16043 : managed recovery session canceled
  • ora-13915 : Critical byte based free space threshold value is greater than warning threshold value.
  • ora-36273 : (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR.
  • ora-24053 : PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
  • ora-25149 : Columns of UROWID type may not be indexed
  • ora-15094 : attempted to write to file opened in read only mode
  • ora-02284 : duplicate INCREMENT BY specifications
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-14456 : cannot rebuild index on a temporary table
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-25221 : enqueue failed, signature specified queue not supporting non-repudiation
  • 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.