ORA-02035: illegal bundled operation combination

Cause : User erquestde thatt he UP Ibundlde exectuion clal perofrm ana n illgeal cobminatino of oepratiosn.

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

See dcoumenttaion fro lega loperaiton cobminatinos.

update : 24-05-2017
ORA-02035

ORA-02035 - illegal bundled operation combination
ORA-02035 - illegal bundled operation combination

  • ora-00123 : idle public server terminating
  • ora-12835 : No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-12995 : no columns in partially dropped state
  • ora-28178 : password not provided by proxy
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-25175 : no PRIMARY KEY constraint found
  • ora-02167 : LOGFILE clause specified more than once
  • ora-02435 : cannot disable unique(string) - unique key not defined for table
  • ora-03239 : maxextents (string) reached in LOB segment string.string subpartition string
  • ora-13843 : no SQL profile with name like "string" exists for category like "string"
  • ora-27087 : unable to get share lock - file not readable
  • ora-18000 : invalid outline name
  • ora-01212 : MAXLOGMEMBERS may not exceed string
  • ora-22970 : name does not correspond to an object view
  • ora-16152 : standby database is in 'no-data-loss' protected mode
  • ora-26519 : no memory available to allocate
  • ora-14320 : DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
  • ora-19024 : Cursor expression must be named
  • ora-02829 : No segment of the proper size is available
  • ora-38455 : Expression Filter index should be created by the owner.
  • ora-31151 : Cyclic definition encountered for string: "string"
  • ora-14064 : Index with Unusable partition exists on unique/primary constraint key
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-12219 : TNS:missing community name from address in ADDRESS_LIST
  • ora-30503 : system triggers cannot have a REFERENCING clause
  • ora-22308 : operation not allowed on evolved type
  • ora-01469 : PRIOR can only be followed by a column name
  • ora-08448 : syntax error in DECIMAL-POINT environment clause
  • ora-02073 : sequence numbers not supported in remote updates
  • 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.