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 : 24-04-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-04028 : cannot generate diana for object stringstringstringstringstring
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • ora-30163 : The thread safety initialization failed
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-36843 : (XSLMGEN13) Dimension string.string!string hierarchy string is missing a PHYSICALNAME property value
  • ora-32152 : Cannot perform operation on a null number
  • ora-16802 : downgrading redo transport mode from SYNC disallowed
  • ora-01311 : Illegal invocation of the mine_value function
  • ora-32762 : Turn on Temp LOB Ref Count Tracing
  • ora-31443 : deadlock detected while acquiring lock on string
  • ora-29878 : warning in the execution of ODCIINDEXTRUNCATE routine
  • ora-02468 : Constant or system variable wrongly specified in expression
  • ora-12157 : TNS:internal network communication error
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-01926 : cannot GRANT to a role WITH GRANT OPTION
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-00569 : Failed to acquire global enqueue.
  • ora-14059 : partition "string": INITRANS value must be less than MAXTRANS value
  • ora-10636 : ROW MOVEMENT is not enabled
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-24412 : Cannot reinitialize non-existent pool
  • ora-22613 : buflen does not match the size of the scalar
  • ora-13062 : topology IDs do not match in the feature table and the topology
  • ora-06517 : PL/SQL: Probe error - string
  • ora-00445 : background process "string" did not start after string seconds
  • ora-29821 : specified primary operator does not exist
  • ora-29706 : incorrect value string for parameter ACTIVE_INSTANCE_COUNT
  • ora-26504 : operation not implemented
  • ora-24795 : Illegal string attempt made
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • 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.