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 : 17-08-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-13000 : dimension number is out of range
  • ora-01591 : lock held by in-doubt distributed transaction string
  • ora-30934 : 'string' (string node) cannot be inserted in parent 'string' (string node)
  • ora-19025 : EXTRACTVALUE returns value of only one node
  • ora-27128 : unable to determine pagesize
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-22905 : cannot access rows from a non-nested table item
  • ora-07285 : sksaprd: volume size should not be specified for a disk file.
  • ora-34841 : (OPCREATE02) The string option must be declared with the READONLY attribute.
  • ora-24150 : evaluation context string.string does not exist
  • ora-19008 : Invalid version of the XMLType
  • ora-26730 : %s 'string' already exists
  • ora-16642 : db_unique_name mismatch
  • ora-31700 : Very long string supplied for AUDIT_SYSLOG_LEVEL parameter
  • ora-00092 : LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
  • ora-24909 : call in progress. Current operation cancelled
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-13191 : failed to read SDO_ORDCNT value
  • ora-22132 : hexadecimal string does not correspond to a valid REF
  • ora-22061 : invalid format text [string]
  • ora-21503 : program terminated by fatal error
  • ora-31425 : subscription does not exist
  • ora-13020 : coordinate is NULL
  • ora-01891 : Datetime/Interval internal error
  • ora-26523 : rpc termination error
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-30655 : cannot select FOR UPDATE from external organized table
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-06556 : the pipe is empty, cannot fulfill the unpack_message request
  • ora-09284 : sllfop: cannot allocate read buffer
  • 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.