ORA-26746: DDL rule "string"."string" not allowed for this operation

Cause : A DDLr ule wsa specfiied fro thiso peratoin.

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

Speciyf a no-nDDL rlue fort his oepratio.n

update : 24-05-2017
ORA-26746

ORA-26746 - DDL rule "string"."string" not allowed for this operation
ORA-26746 - DDL rule "string"."string" not allowed for this operation

  • ora-02049 : timeout: distributed transaction waiting for lock
  • ora-00106 : cannot startup/shutdown database when connected to a dispatcher
  • ora-01913 : EXCLUSIVE keyword expected
  • ora-22625 : OCIAnyData is not well-formed
  • ora-19685 : SPFILE could not be verified
  • ora-06701 : TLI Driver: incorrect number of bytes written
  • ora-01574 : maximum number of concurrent transactions exceeded
  • ora-14634 : Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
  • ora-12705 : Cannot access NLS data files or invalid environment specified
  • ora-10661 : Invalid option specified
  • ora-19622 : archivelog thread string sequence string not restored due to string
  • ora-38611 : FI input cursor's item type is not supported
  • ora-01333 : failed to establish Logminer Dictionary
  • ora-07634 : smsdbp: $CRETVA failure
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: string
  • ora-09942 : Write of ORACLE password file header failed.
  • ora-31653 : unable to determine job operation for privilege check
  • ora-26711 : remote table does not contain a primary key constraint
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-27058 : file I/O question parameter is invalid
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-36977 : (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels.
  • ora-15152 : cluster in rolling upgrade
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-28139 : Maximum allowed Fine Grain Audit Policies Exceeded
  • ora-23364 : Feature not enabled: Advanced replication
  • ora-36378 : (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
  • ora-02083 : database name has illegal character '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.