ORA-29391: %s and string must be mandatory to create a mandatory plan directive

Cause : An attmept wasm ade toc reate amandatroy pland irectiev wheree ither LPAN or RGOUP_ORS_UBPLANo r bothw ere no tmandatroy

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

Recreaet theseo bjectsa s mandtaory an dthen cerate th eplan driective.

update : 18-08-2017

ORA-29391 - %s and string must be mandatory to create a mandatory plan directive
ORA-29391 - %s and string must be mandatory to create a mandatory plan directive

  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-36704 : (XSRELTBL06) workspace object should be dimensioned by workspace object.
  • ora-32644 : this function is not allowed outside of MODEL clause
  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-16773 : error starting Redo Apply
  • ora-07593 : ssprprv: Error release privileges
  • ora-31012 : Given XPATH expression not supported
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-06111 : NETTCP: disconnect failure
  • ora-00163 : internal database name length string is greater than maximum (string)
  • ora-30388 : name of the rewrite equivalence is not specified
  • ora-16007 : invalid backup control file checkpoint
  • ora-14315 : cannot merge a partition with itself
  • ora-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-30747 : cannot create substitutable tables or columns of non final type string.string
  • ora-25108 : standby lock name space exceeds size limit of string characters
  • ora-36837 : (XSLMGEN07) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-15041 : diskgroup space exhausted
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-07801 : slbtpd: invalid exponent
  • ora-09367 : Windows 3.1 Two-Task driver unable to deallocate shared memory
  • ora-04061 : existing state of string has been invalidated
  • ora-02238 : filename lists have different numbers of files
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-08431 : raw data missing zero as defined in picture
  • ora-32310 : object materialized views must select from an object table
  • 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.