Nonstop Database, HiRDB Version 9 System Operation Guide
HiRDB employs the startup modes listed in the table below. The pdstart command's options depend on the startup mode.
Table 1-1 HiRDB startup modes
Startup mode | Execution command | Description of the startup mode | Previous termination mode |
---|---|---|---|
Normal startup | pdstart | This is the usual startup mode. In this mode, information that was in effect during the previous session is not inherited. However, the following types of information are inherited:
|
Normal termination |
Restart#1 | This is the mode that is used (automatically) when the previous termination mode was one of those listed to the right. In this mode, the information that was in effect during the previous session is inherited. For details about the information that is inherited during a HiRDB restart, see 20.1.5 Information inherited during a HiRDB restart. |
|
|
Forced startup#2 | pdstart dbdestroy | Do not use this mode unless it is absolutely necessary. When HiRDB cannot be restarted, this mode is used to start HiRDB forcibly. | -- |
--#3 | pdstart -i | Do not use this mode unless it is absolutely necessary; it is used when a database is being reinitialized. | |
pdstart -r [-t] | Do not use this mode unless it is absolutely necessary; it is used in the event of an error in the master directory RDAREA. | ||
pdstart -R [-t]#4 | This is the mode that is used when the unit in which the system manager is located is abnormally terminated by an error after a server in a HiRDB parallel server configuration is started using the pdstart -r command. Executing this command forcibly starts the unit in which the abnormally terminated system manager is located, and then forcibly terminates the server in the HiRDB parallel server configuration. | ||
pdstart -a | Do not use this mode unless it is absolutely necessary; it is used when the front-end server is in SUSPEND status. |
All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.