Stopping the Database Server with stop

Run stop_iq from the command line.

Issue a command in this format:

stop_iq [ -cleanup ] [  -stop [ one  | all ] ]  [  -user <user_name> ] [  -version [ 12 | 15 | all ]> ] [  -wait <seconds> ]

When prompted to stop your server, respond Y (yes).
If the server is connected to one or more clients, respond to the warning that uncommitted transactions will be lost.

The following example illustrates how to use stop_iq interactively to list all the servers that are running, and then shut down one server.

% stop_iq

Checking system ...
The following 1 server(s) are owned by 'TEST'

##     Owner    PID   Started  CPU_Time   Additional Information
 -- ---------  -----  --------  --------  -----------------------
1:   TEST     22399  08:56:39      1:43  SVR:QA_sun7qa DB:iqdemo PORT:8888
/sun7qa1/users/QA/090513/IQ-16_0/bin64/iqsrv16 @iqdemo.cfg iqdemo.db -ti 4400
--
	Please note that ’stop_iq’ will shutdown a server completely 
	without regard for users connections or load processes status. 
	For a finer level of detail the utility ’dbstop’ has the options 
	to control whether a server is stopped based on active connections.

Do you want to stop the server displayed above <Y/N>? Y

Shutting down server (22399) ...
Checkpointing server (22399) ...
Server shutdown.

stop_iq Options
This table lists the options available for the stop_iq utility.
Stopping Servers in a cron or at Job
If using stop_iq in a cron or at job, use the appropriate -stop option:
Servers with Long Paths
Depending on the operating system, the stop_iq utility may fail to report running servers when the path to the server exceeds 74 characters.

Parent topic: stop_iq Database Shutdown Utility

Stopping the Database Server with stop_iq