Sybase IQ DBCC ?
If you’re coming from Microsoft SQL Server or Sybase ASE, SAP’s IQ doesn’t have the
slew of dbcc commands you might expect. It rolls up all the pertinent dbccs
into a single stored procedure. sp_iqcheckdb has four operational modes
with a granularity at the database, table or index level:
In check mode, sp_iqcheckdb performs an internal
consistency check on all IQ indexes and checks that each database block has been
allocated correctly. All available database statistics are reported. This mode
reads all data pages and can detect all types of allocation problems and most
types of index inconsistencies. Check mode should run considerably faster than
verify mode for most databases.
In verify mode, sp_iqcheckdb performs an intra-index
consistency check, in addition to internal index consistency and allocation
checking. All available database statistics are reported. The contents of each
non-FP index is verified against its corresponding FP index(es). Verify mode
reads all data pages and can detect all types of allocation problems and all
types of index inconsistencies.
In allocation mode, sp_iqcheckdb checks that each database
block is allocated correctly according to the internal physical page mapping
structures (blockmaps). Database statistics pertaining to allocation are also
reported. This mode executes very quickly. Allocation mode, however, does not
check index consistency and cannot detect all types of allocation problems.
When the Sybase IQ server runs in single-node mode, you can use
dropleaks mode with either a database or dbspace target to
reset the allocation map for the entire database or specified dbspace targets.
If the target is a dbspace, then the dropleaks operation must also prevent
read-write operations on the named dbspace. All dbspaces in the database or
dbspace list must be online.
No changes are actually performed with the exception of the dropleaks mode.
If check or verify detects an issue with allocation, you will need to run
sp_iqcheckdb in the dropleaks mode while the database is in single user mode.
For any issues with indexes, use sp_rebuildindex on both the index and possibly
the affected column of the table.
By default output of sp_iqcheckdb will go to the (instance_name).iqmsg log
file but you can redirect it to its own file for easier reading:
set temporary option dbcc_log_progress='on';