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

Cause : hTsii s aebinngm seaseg .hT eWAV LADITA Eocmmna dofnu dnaa anylit cowkrpsca eah sosemi anccseislb epsca.e

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

iEhtren toihgn ,roe pxro tna derrcaeett eha anylit cowkrpscae

update : 29-04-2017

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

  • ora-32629 : measure used for referencing cannot be updated
  • ora-01323 : Invalid state
  • ora-02204 : ALTER, INDEX and EXECUTE not allowed for views
  • ora-19852 : error creating services for auxiliary instance string (error string)
  • ora-07273 : sppst: invalid semaphore id.
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-08444 : syntax error in JUSTIFIED clause in mask options
  • ora-07257 : spdcr: translation error expanding program name.
  • ora-01568 : cannot set space quota on PUBLIC
  • ora-31090 : invalid database schema name "string"
  • ora-02373 : Error parsing insert statement for table string.
  • ora-38474 : attribute set may not have attributes of TABLE COLLECTION type.
  • ora-31108 : Action failed as resource string is locked
  • ora-12424 : length exceeds binary label size
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-09952 : scgcmn: lk_open_convert unexpected return: open failed
  • ora-24069 : cannot downgrade queue table string while it is being upgraded
  • ora-38742 : Flashback log file has incorrect log reset status.
  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-29741 : IMR active for some, but not all members of cluster
  • ora-29309 : export dump file was generated by different version of DBMS_PITR package
  • ora-02087 : object locked by another process in same transaction
  • ora-39025 : jobs of type string are not restartable
  • ora-31076 : required attribute "string" not specified
  • ora-19657 : cannot inspect current datafile string
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-19276 : XP0005 - XPath step specifies an invalid element/attribute name: (string)
  • ora-25189 : illegal ALTER TABLE option for an index-organized table
  • ora-34344 : (MXDSS03) Analytic workspace string is not attached.
  • ora-27421 : usage of string not supported in a calendar definition
  • 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.