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-06-2017
ORA-33304

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-27303 : additional information: string
  • ora-31207 : DBMS_LDAP: PL/SQL - Invalid LDAP search time value.
  • ora-01698 : a clone database may only have SYSTEM rollback segment online
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-31643 : unable to close dump file "string"
  • ora-36871 : (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.
  • ora-12025 : materialized view log on "string"."string" already has primary keys
  • ora-09933 : Deletion of old password file failed.
  • ora-01260 : warning: END BACKUP succeeded but some files found not to be in backup mode
  • ora-06707 : TLI Driver: connection failed
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • ora-36200 : (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one.
  • ora-09929 : GLB of two labels is invalid
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-01861 : literal does not match format string
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-36722 : (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
  • ora-22150 : variable-length array has not been initialized
  • ora-38777 : database must not be started in any other instance.
  • ora-28605 : bitmap indexes cannot be reversed
  • ora-32005 : error while parsing size specification [string]
  • ora-01265 : Unable to delete string string
  • ora-00377 : Frequent backups of file string causing write operation to stall
  • ora-01518 : CREATE DATABASE must specify more than one log file
  • ora-19681 : block media recovery on control file not possible
  • ora-24240 : invalid database access descriptor (DAD) name
  • ora-36696 : (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
  • ora-14137 : Table in partially dropped state, submit DROP TABLE PURGE
  • ora-01126 : database must be mounted in this instance and not open in any instance
  • 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.