Think of why you run the DB2 for z/OS REORG utility, and a number of reasons are likely to come quickly to mind: to restore row order per a table’s clustering key; to reestablish free space (for inserts and/or for updates ); to remove the AREO* status set for a table space following (for example) an ALTER TABLE ADD COLUMN operation; or to materialize a pending DDL change such as an enlargement of a table space’s DSSIZE. How about disk space reclamation? If that REORG motivation has not previously …read more
Related Articles
GDPR: A roadmap for the Oracle DBA
Probably one of the biggest challenges that company IT departments have is the security of their infrastructure, processes and data. Security is an issue that increasingly demands time and effort from...
Background Processes in Oracle ASM
Once the ASM instance is started, all the basic background processes, as well as some that are specific to the operation of ASM, are started. Notice that all the ASM processes begin with asm, whereas ...
Overview of developer features in Toad for DB2 – Part V
This video on the SQL editor is part five of an overview of developer features in Toad for DB2....
