DB2 备份 以及 各个参数（国外英文资料）.docVIP

DB2 备份 以及 各个参数（国外英文资料） DB2 backup and various parameters (1) The DB2 log is stored in the file system as a file and is divided into two modes: circular logging and archival logging. When a new database is created, the default mode for the log is circular logging. In this mode, only the offline backup and recovery of the database can be implemented. If you want to implement online backup and restore, you must set up the archive logging pattern. Offline backup is also the simplest backup in DB2 UDB. Offline backup requires full database backup, and obviously the database is offline during the backup process. In other words, when the offline backup is performed, the user cannot access the database. If you are using circular logging, offline backup is the only supported type. This is the default logging method when you first create a database. For circular logging, log retain for recovery status and user exit for logging status are set to NO. Both LOGRETAIN and USEREXIT are set to OFF. Log retain for recovery status = NO User exit for logging status = YES Log retain for recovery enabled (LOGRETAIN) = OFF User exit for logging enabled (USEREXIT) = OFF Currently in the integrated business system, the archive logging pattern is set; Other systems (such as later supervision, business decision, intermediate business, etc.) are generally set to circular logging mode. As to what mode, you can change the database configuration parameter (LOGRETAIN) to implement: archive log mode: for db2 update db CFG using LOGRETAIN on note: instead of on, to check the database configuration parameter LOGRETAIN value, actual shows the recovery. Once this parameter is changed, the database will display the database in a BACKUP PENDING state. At this point, you need to do an offline backup of the database (db2 backup db) to make the database state normal. Circular logging pattern: db2 update db CFG for using logretain on Modify the logging pattern Objective: to make the log changes to archive lo