ORA-33304: (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.

Cause : This is a benign message. The AW VALIDATE command found an analytic workspace has some inaccessible space.

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

Either nothing, or export and recreate the analytic workspace

update : 26-05-2017

ORA-33304 - (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
ORA-33304 - (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.

  • ora-36968 : (XSRELTBL11) workspace object must be a relation.
  • ora-02085 : database link string connects to string
  • ora-22307 : operation must be on a user-defined type
  • ora-22336 : table contained 8.0 image format, must specify INCLUDING DATA
  • ora-09801 : Unable to get user ID from connection
  • ora-16546 : missing or invalid piece
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-38401 : synonym string not allowed
  • ora-29284 : file read error
  • ora-12519 : TNS:no appropriate service handler found
  • ora-26713 : remote object does not exist or is inaccessible
  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-16053 : DB_UNIQUE_NAME string is not in the Data Guard Configuration
  • ora-30069 : Auto Undo-Management Error simulation - test site = string
  • ora-01878 : specified field not found in datetime or interval
  • ora-21612 : key is already being used
  • ora-09772 : osnpmetbrkmsg: message from host had incorrect message type
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-24049 : invalid agent name string, names with AQ$_ prefix are not valid
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-24152 : cannot drop evaluation context string.string with dependents
  • ora-09874 : TASDEF_READ: read error, unable to read tasdef@.dbf file.
  • ora-16735 : error executing dbms_logstdby.unskip_error procedure
  • ora-28515 : cannot get external object definitions from string
  • ora-28049 : the password has expired
  • ora-29892 : indextypes with array DML do not support the given data type
  • ora-19017 : Attributes can only be simple scalars
  • ora-39056 : invalid log file specification.
  • ora-09369 : Windows 3.1 Two-Task driver bad instance handle
  • 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.