支持崩溃、时间点和事务恢复。
该过程也称为事务恢复处理。
This activity is referred to as transaction recovery processing.
事务恢复由控制区域处理。
支持在线和离线完全备份以及崩溃和事务恢复。
Supports full online and offline backups and crash and transaction recovery.
支持在线和离线完全备份以及崩溃、时间点和事务恢复。
Supports full online and offline backups and crash, point-in-time and transaction recovery.
如果没有使用事务的高可用性，无需指定事务恢复日志目录。
If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory.
还有一次，有个客户向我询问关于产品如何在重负载下处理事务恢复的问题。
Another time, I had a customer question regarding how the product handles transaction recovery under heavy load.
事务恢复处理在数据库应用和网络分布计算环境中具有重要作用。
Transactional recovery plays an important role in database applications and in distributed network environment.
手动干预不是事务恢复的首选方法；有些用户会选择自动而透明的事务恢复策略。
Manual intervention might not be your preferred method of transaction recovery; some users will opt for automatic and transparent transaction recovery strategies.
如果在事务进行期间应用程序崩溃，则在重启时，事务恢复将回滚该事务。
If an application crashes in the middle of a transaction, when it restarts, transaction recovery will roll back the open transaction.
这可防止任何2pc分布式事务跨多个RAC节点分布，因而可避免出现事务恢复问题。
This prevents any 2pc distributed transaction to span across more than one RAC node, thereby avoiding the transaction recovery problem.
如果一个全局2pc事务中的所有连接都源自同一oraclerac节点，就不会出现事务恢复问题。
If all connections in a global 2pc transaction originate from the same Oracle rac node, transaction recovery problems should not arise.
如果应用服务器在调用prepare和commit、rollback之间失败，那么在服务器重启时需要进行事务恢复。
If the application server should fail between calling prepare and commit or rollback, then transaction recovery needs to take place when the server restarts.
我们会对每个存储层重复执行该测试套件，并且会重新运行这些测试用例2次：一次是测试事务日志恢复，然后测试常规的关闭。
We repeat the test suite for each of our storage layers. Again we rerun those test cases 2 times: once to test Transaction Log recovery and then to test Regular Shutdown.
它把记录写入恢复日志，增加事务状态信息。
It writes records to a recovery log, plus transaction state information.
所以正在建立的连接的类型无关紧要，因为数据库的启动将恢复事务日志中所有未完成的事务，以便保持数据完整性。
So the type of connection being established does not matter because the act of booting the database will recover any incomplete transactions in the transaction log in order to preserve data integrity.
对您来说，更快的恢复与更快的事务哪个优先？
Has faster recovery a higher priority for you versus faster transaction?
本文也展示了一些从失败的事务中完好地恢复的例子。
It also shows examples of recovering from a failed transaction gracefully.
该引擎提供了事务和崩溃恢复，支持多个连接，而且支持使用一个连接的多个线程。
The engine provides transactions and crash recovery, and allows multiple connections and multiple threads to use a connection.
如果事务内的值发生更改，则将更改的值传播回本地环境和所有后续(新的和恢复的)事务。
If the value is changed within a transaction, the changed value is propagated back to the local environment and to all subsequent (new and resume) transactions.
为了执行从故障场景中恢复，事务管理器和资源管理器必须能够在事务流程的任何点从故障中恢复。
In order to implement recovery from failure scenarios, the transaction manager and the resource manager must be able to recover from a failure at any point in the transactional flow.
要恢复完整的备份，重播备份之后的所有事务的日志，该过程结束之后恢复就完成了。
Restore a full backup, replay the logs of all transactions since the backup, and your recovery is complete.
如果故障发生时的，事务的状态指示恢复处理。
The state of the transaction dictates recovery processing in the event of a failure.
高度可用的事务日志恢复。
在检查点之间的事务被写入到一个事务日志中，并且，如果系统发生崩溃，事务将从事务日志中恢复。
Between checkpoints, transactions are written to a transaction log and, if the system crashes, transactions are recovered from the transaction log.
在重启之后，DB2和IDS都将尝试恢复打开的事务分支。
DB2 as well as IDS will try to recovery the open transaction branch after reboot.
TCS的最后一个需求是在事务失败时实现重试及恢复。
A last requirement for the TCS is to implement retry and recovery for when transactions fail.
顾名思义，完全恢复能够完全地恢复所有提交的事务，而不完全恢复在恢复事务时会丢失一些数据。
Complete recovery, as the name implied, recovers all committed transactions, whereas incomplete recovery brings back transactions with some lost of data.
该变更的引入可以使得寄存事务日志的机器崩溃时，能够利用事务日志的同等恢复来完善不确定的事务。
This change was introduced to enable peer recovery of transaction log to complete in-doubt transactions when the machine hosting the transaction log crashes.
如果仅进行对CICS的单个调用，并且在事务中没有对可恢复资源的其他更新，就没必要使用全局事务。
If only a single call to CICS is made and there are no other updates to recoverable resources within the transaction, then it is not necessary to use a global transaction.
应用推荐