ORA-16809: multiple warnings detected for the database

Cause : The broker has detected multiple warnings for the database.

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

Check the StatusReport monitorable property of the database specified.

update : 27-04-2017
ORA-16809

ORA-16809 - multiple warnings detected for the database
ORA-16809 - multiple warnings detected for the database

  • ora-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • ora-13762 : The string ranking measure is invalid.
  • ora-22890 : cannot specify name for REF column constraint
  • ora-01088 : cannot shut down ORACLE while active processes exist
  • ora-19954 : control file is not current
  • ora-12450 : LOB datatype disabled in LBAC initialization file
  • ora-31463 : logfile location string is an empty directory
  • ora-22604 : TDS handle already generated
  • ora-39959 : invalid warning number (string)
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-09834 : snyGetPortSet: failed to collect info on a port.
  • ora-29305 : cannot point-in-time recover tablespace 'string'
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-15132 : block string of file string in diskgroup string could not be written
  • ora-32343 : let MVIEW engine know that it is IMPORT from 9i or earlier
  • ora-31197 : Error in processing file string
  • ora-13198 : Spatial error: string
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • ora-01525 : error in renaming data files
  • ora-14617 : cannot add/drop values to DEFAULT subpartition
  • ora-24231 : database access descriptor (DAD) string not found
  • ora-01219 : database not open: queries allowed on fixed tables/views only
  • ora-25000 : invalid use of bind variable in trigger WHEN clause
  • ora-03205 : partition name is required when partitioned type is specified
  • ora-09344 : spsig: error signalling thread
  • ora-07227 : rtneco: unable to set noecho mode.
  • ora-32136 : Cannot perform operation on an invalid stream
  • ora-16731 : error executing dbms_logstdby.unskip_txn procedure
  • ora-19663 : cannot apply current offline range to datafile 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.