DB2 high availability disaster recovery (HADR) in the limit

Environmental Product: DB2 UDB

Platform: Cross Platform

Version: 8.2 (8.1 patch 7)

Question DB2 UDB High Availability Disaster Recovery (HADR) is a database replication feature that is part of the fault and the site provides a high availability solution. HADR changes through the data from the source database (known as the master database) to the target database (known as the standby database) to prevent data loss, the data replication operation is achieved through the database log. Here the configuration to use HADR attention should be considered and the restrictions on the HADR.

Answers on the high availability disaster recovery (HADR) restrictions are summarized as follows:

1. Only in the DB2 UDB Enterprise Server Edition (ESE) on the support of HADR. However, when there are multiple ESE database partition, do not support the HADR.

2. The primary database and standby database must have the same operating system version and the same version of DB2 UDB, alternating scroll shorter than the upgrade process.

3. The primary database and standby database on the DB2 UDB release must have the same bit size (32-bit or 64-bit).

4. Do not support the standby database read operations. Standby database client can not connect.

5. Only by the current implementation of the master database log file.

6. Standby database does not support backup operations.

7. Can not be non-(log) records to replicate to the standby database.

HADR is to use the library because the log to copy the data to the standby database, so the master database to allow non-logged operations, but does not allow copying of such operations to the standby database. These non-copy operation, including the following (but not limited to the following):

1) Use the specified NOT LOGGED INITIALLY option to create the table.

2) BLOB and CLOB fields. Although these fields are not copied, but the standby database is assigned space.

3) the use of UPDATE DATABASE CONFIGURATION and UPDATE DATABASE MANAGER CONFIGURATION command executed on the database configuration update.

4) restoration of historical documents and changes to this historical document.

8. Does not support the COPY NO option specified the mount operation.

9. Do not support the use of DataLink.

10. Do not support the original log.

HADR does not support the database log files using the original I / O (direct disk access). If you use the START HADR command start HADR, or if configured restart HADR database will detect the original logs, resulting in failure of the associated command and generates SQL1768N reason code "9" of error, namely:

Database configured to use the original log. However, HADR does not support the database log files using the original I / O (direct disk access).






Recommended links:



Jia Peng Lei: "diversity" denatured



Simple FTP Clients



M2TS Converter



3DS Max 7 Mental Ray renderer whole strategy: global illumination



MPG to 3GP



Make use of DHTML scrolling bulletin board with links



Vice Minister of Ministry of Industry and women throughout the year Ou died 59 years



HP means to MAINTAIN the integrity of former coach



For You Cartoons - Screen Savers



Blackberry bold 9000 or iphone



Next-generation console out of stock, 2007 to continue



09 'happy to steal Food' in 2010 what we steal?



ASF to MOV



OPEN-SOURCE framework for thinking about [3]