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 : 23-06-2017

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

  • ora-01044 : size string of buffer bound to variable exceeds maximum string
  • ora-19718 : length for command id longer than string
  • ora-25463 : table alias not specified
  • ora-29826 : keyword FOR is missing
  • ora-22310 : ALTER TYPE error. Refer to table "string"."string" for errors
  • ora-22996 : NEXT extent size is smaller than LOB chunksize
  • ora-23602 : Invalid streams process type string
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-24195 : attemp to retrieve the name list of a map message with size exceeding 1024
  • ora-16172 : archive logs detected beyond Terminal End-Of-Redo
  • ora-13372 : failure in modifying metadata for a table with spatial index
  • ora-29663 : Unable to find a method that matches one or more of the functions
  • ora-01699 : tablespace 'string' is being imported for point in time recovery
  • ora-12066 : invalid CREATE MATERIALIZED VIEW command
  • ora-01987 : client os username is too long
  • ora-31475 : redo log catalog contains no metadata for the source table
  • ora-38762 : thread string redo log with scn string could not be found
  • ora-31497 : invalid value specified for first_scn
  • ora-01219 : database not open: queries allowed on fixed tables/views only
  • ora-30960 : The entity is neither an XPATH nor a NAMESPACE.
  • ora-30051 : VERSIONS clause not allowed here
  • ora-03291 : Invalid truncate option - missing STORAGE keyword
  • ora-03254 : unable to execute the sql in read only database
  • ora-02221 : invalid MAXEXTENTS storage option value
  • ora-22975 : cannot create a PRIMARY KEY-based REF to this object view
  • ora-33313 : (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.
  • ora-06533 : Subscript beyond count
  • ora-02207 : invalid INITRANS option value
  • ora-38768 : resizing datafile string failed
  • 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.