Here’s a quick and dirty script to create a procedure (in the SYS schema – so be careful) to check the Hakan Factor for an object. If you’re not familiar with the Hakan Factor, it’s the value that gets set when you use the command “alter table minimize records_per_block;”.

I was prompted to publish this note by an item on the OTN SQL forum describing a problem with partition exchange with a table when there were bitmap indexes in place and the table had been changed to have some extra columns added. (Problem as yet unresolved as I publish).

Cloud computing has brought a host of advantages for businesses that have become impossible to ignore, from decreased capital spending to enhanced collaboration. However, the true benefits of these technologies come with time, and therefore, a more extensive and strategic cloud plan, with remote database support, can potentially offer enterprises a more significant competitive edge in the long run. By applying these initiatives more holistically to all aspects of the organization, firms stand to gain more flexibility and productivity than ever before.

Goal

Created an Unix user (e.g. tier1 ) in the Oracle database server that can perform some database administration tasks but cannot be used to view or modify any application data.

Current typical Unix/Liux Environment:

- OS user: "oracle" is the Oracle software owner and its primary group is "dba" (i.e. Oracle database files have ownership oracle:dba )

- Assuming OSDBA group is "dba" (i.e. every os user that belongs to "dba" group can login as sysdba and view any data)

It’s the only explanation!