Database Events
You can affect a server by using database events. Database events override the flag settings in the configuration file. An Ingres application must connect to the server’s database to issue the event. You can affect a server in any mode: stopped, started and active, or started and quiet.
You can send events from the following sources:
• Visual DBA, Visual Performance Monitor, or SQL Scratchpad window
For more information, see the online help topic Raising Events at the Server Level.
• Terminal Monitor
• Ingres 4GL, embedded SQL, or OpenAPI application
The database events you can use to affect server behavior are:
dd_stop_server[n]
Stops the server, where n is the number of the server. If n is not specified, all started servers on that database are requested to shut down.
For example:
dd_stop_server7
Note: Servers shut down only after they finish current processing activities.
dd_go_server[n]
Directs a quiet server to process pending replication transactions, where n is the number of the server. If n is not specified, all started servers on that database processes pending transactions.
For example:
dd_go_server7
You can use the dd_go_server[
n] event to schedule replication at specific times with a quiet server. For more information, see
Scheduling Servers.
dd_ping
Sends a ping event to all servers.
dd_set_server[n] '-flag'
Overrides the server parameters set in the configuration file, where
n is the number of the server and flag is a server parameter that can be set dynamically. For more information about server flags, see
Server Parameters.
For example:
dd_set_server7 '-NQT'
If n is not specified, all started servers connected to that database are altered.