Filter
Top Products
41
Example
Assume that the DBA cannot successfully open and connect to database foo,
because of reported IQ errors during database open and recovery. To force
recovery and correct leaked space, follow the steps below.
Note Do not confuse an inability to connect to a database with an IQ server-
level error while IQ is trying to open a database.
1 Start the database server with the
-iqfrec switch:
asiqsrv12 -iqfrec foo ... -gd dba ... foo.db
or on UNIX
start_asiq -iqfrec foo ... -gd dba ... foo.db
2 Connect to the database (foo).
The .iqmsg file reports that the database was opened in forced recovery
mode.
3 Bring down the server as you would normally. (If you use
dbstop to bring
down the server, be sure to include
-iqfrec in the dbstop command.)
4 Start up the server again with the
-iqdroplks switch:
asiqsrv12 -iqdroplks foo ... -gd dba ... foo.db
5 Connect to the database. It will be fully allocated.
6 To correct the leaks created by the forced recovery open, run
sp_iqcheckdb on foo.
9.5.5 Improved output in stored procedures
Several stored procedures now display output in units that are easier to
understand. The following table describes the new column names. The stored
procedure
sp_iqindexsize displays all of these columns except Nblocks. The
stored procedures
sp_iqdbsize, sp_iqtablesize, and sp_iqjoinindexsize
display all of these columns except Info.
Table 3: New Stored Procedure Columns
Column name Description
Kbytes Physical object size in KB
Pages Number of IQ pages needed to hold the object in
memory
Compressed Pages Number of IQ pages when the object is compressed (on
disk)