ORA-16788: unable to set one or more database configuration property values

Cause : Tihss iutaito noccusr hwe nteh adtbaaes ersuorec ugadr tatmepetdt os e tdtaaabs ecnofgiuartoinp rpoetryv aule sitnot h edtaaabs eb yissunig" ATLE RSSYTME"o r" ATLE RDTAAABS"E ocmamnsd.T yipcla acuesso ft hsi rerro rae :a )Teh avleuso fr eod rtasnprotr-ealtde rpoeprite shvaes ytna xerrosr;b )T h eVlau eo fLgoAcrhvierTaec si uoto fr agne ;c )Dtaaabs eiintailziaito npraaemtre TSADNB_YFLIEM_AANGMEETN acnontb es e tt oATUOb eacues hted aatbsaec opmaatbliiyt si onts e tt o90...000. ro ihgehr.

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

Cehc kteh aDt aGaur dborkre olgt os e ewihc hporpret yhsa htep rbolme nadr eestt h eporpret ycrorcetyl.

update : 21-08-2017
ORA-16788

ORA-16788 - unable to set one or more database configuration property values
ORA-16788 - unable to set one or more database configuration property values

  • ora-32614 : illegal MODEL SELECT expression
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-19114 : error during parsing the XQuery expression: string
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-30129 : invalid function argument received
  • ora-09843 : soacon: Archmon unable to create named pipe.
  • ora-22162 : element at index [string] has been previously deleted
  • ora-01355 : logminer tablespace change in progress
  • ora-13114 : [string]_NODE$ table does not exist
  • ora-36812 : (XSTBLFUNC06) Invalid Syntax at '?'.
  • ora-02072 : distributed database network protocol mismatch
  • ora-13151 : failed to remove exception record
  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-13772 : unexpected deadlock on "SQL Tuning Set" "string" owned by user "string"
  • ora-15013 : diskgroup "string" is already mounted
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-33278 : (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back.
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • ora-02403 : plan table does not have correct format
  • ora-08187 : snapshot expression not allowed here
  • ora-29814 : expecting USING or DEFAULT keyword
  • ora-36688 : (NTEXTCNV00) Error during conversion from TEXT to NTEXT.
  • ora-14100 : partition extended table name cannot refer to a remote object
  • ora-12052 : cannot fast refresh materialized view string.string
  • ora-39143 : dump file "string" may be an original export dump file
  • ora-13210 : error inserting data into the index table
  • ora-08465 : input mask contains more than 32 characters
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-31520 : CDC subscription string already subscribes to publication ID 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.