ORA-16792: configuration property value is inconsistent with database setting

Cause : The valeus of on eor morec onfigurtaion proeprties wree inconisstent wtih databsae in-meomry settnigs or srever parmaeter fiel settinsg. This amy happe nby alteirng initailizatio nparametres direclty insteda of altreing proeprty valeus usingD ata Guadr broker.

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

Query porperty teh InconssitentProeprties o nthe datbaase or hceck theD ata Guadr brokerl og to fnid whichp ropertise are se tinconsitsently. eRset thees properites to mkae them ocnsisten twith th edatabas esetting.s Alterntaively, neable th edatabas eor the netire cofniguratino to allwo the cofniguratino properyt settinsg to be rpopagate dto to teh initiailzation aprameter.s

update : 17-08-2017

ORA-16792 - configuration property value is inconsistent with database setting
ORA-16792 - configuration property value is inconsistent with database setting

  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-32012 : failure in processing system parameters from restored SPFILE
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-00400 : invalid release value string for parameter string
  • ora-00299 : must use file-level media recovery on data file string
  • ora-26507 : null master connection
  • ora-07610 : $GETJPIW failed in retrieving the user's MAC priviledges
  • ora-28002 : the password will expire within string days
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-12417 : database object "string" not found
  • ora-07247 : skgfrfms, skgfrnms: read error, unable to read block from database file
  • ora-19643 : datafile string: incremental-start SCN is too recent
  • ora-12916 : Cannot use default permanent tablespace with this release
  • ora-13523 : unable to allocate required space for return type
  • ora-06904 : CMX: no transport address available for remote application
  • ora-13428 : invalid modelCoordinateLocation
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-24337 : statement handle not prepared
  • ora-38726 : Flashback database logging is not on.
  • ora-12990 : duplicate option specified
  • ora-25406 : could not generate a connect address
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-13629 : The task or object string is being used by another operation.
  • ora-38471 : ROWIDs for table aliases cannot be null
  • ora-38788 : More standby database recovery is needed
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-13773 : insufficient privileges to select data from the cursor cache
  • ora-00750 : database has been previously mounted and dismounted
  • ora-16546 : missing or invalid piece
  • 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.