update : 17-08-2017

DBA Script : dba_blocks_used_by_table.sql

-- | FILE : dba_blocks_used_by_table.sql |
-- +----------------------------------------------------------------------------+
-- | |
-- | |
-- | www.high-oracle.com |
-- |----------------------------------------------------------------------------|
-- | www.high-oracle.com |
-- |----------------------------------------------------------------------------|
-- | DATABASE : Oracle |
-- | FILE : dba_blocks_used_by_table.sql |
-- | CLASS : Database Administration |
-- | PURPOSE : This article describes how to find out how many blocks are |
-- | really being used within a table. (ie. Blocks that are not |
-- | empty) Scripts are included for both Oracle7 and Oracle8. |
-- | NOTE : As with any code, ensure to test this script in a development |
-- | environment before attempting to run it in production. |
-- +----------------------------------------------------------------------------+
--------------------------------------------
HOW MANY BLOCKS CONTAIN DATA (are not empty)
-----------------------------------------------------------------------
Each row in the table has pseudocolumn called ROWID.
This pseudo contains information about physical location
of the row in format:
block_number.row.file
If the table is stored in a tablespace which has one
datafile, all we have to do is to get DISTINCT
number of block_number from ROWID column of this table.
But if the table is stored in a tablespace with more than one
datafile then you can have the same block_number but in
different datafiles so we have to get DISTINCT number of
block_number+file from ROWID.
The SELECT statements which give us the number of "really used"
blocks is below. They are different for ORACLE 7 and ORACLE 8
because of different structure of ROWID column in these versions.
You could ask why the above information could not be determined
by using the ANALYZE TABLE command. The ANALYZE TABLE command only
identifies the number of 'ever' used blocks or the high water mark
for the table.
-----------------------------------------------------------------------
-------
ORACLE7
-----------------------------------------------------------------------
SELECT
COUNT(DISTINCT(SUBSTR(rowid,1,8)
||
SUBSTR(rowid,15,4)))
FROM &table_name
/
--------
ORACLE8+
-----------------------------------------------------------------------
SELECT COUNT ( DISTINCT
DBMS_ROWID.ROWID_BLOCK_NUMBER(rowid)
||
DBMS_ROWID.ROWID_RELATIVE_FNO(rowid)
) "Used"
FROM &table_name;
- or -
SELECT COUNT (DISTINCT SUBSTR(rowid,1,15)) "Used"
FROM &table_name;

End Script

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.