您需要确保数据库应用程序按预期运行，变更能够顺利进行，并且，如果出现错误，可以找到问题的根源。
You need to ensure that your database applications work as intended, that changes roll out smoothly, and that if something goes wrong, you can investigate the problem.
这意味着随着负载的增加，数据库不会崩溃，即使出现错误，造成的损害对管理员和用户都是透明的。
What this means is that as our load increases, databases aren't corrupted, and in the event of an error, the "penalty" is transparent to the administrators and users.
当脚本终止并且确保没有出现关于数据库未显式分离的 DBI 错误消息时， END()子例程就会执行。
The END() subroutine executes when the script terminates and ensures that a DBI error message about not explicitly disconnecting from the database doesn't occur.
如果表不存在(当数据库刚创建时就会出现这种情况)，将显示一条错误消息；但前面的SQL注释指明，您可以安全地忽略这些消息。
If the tables don't exist (which is the case if the database was just created), an error message is displayed; but as the preceding SQL comments indicate, you can safely ignore those messages.
如果出现数据库连接故障，脚本将向电话报告错误。
In the case of failure to connect to the database, the script reports the error to the phone.
如果数据库出现了错误，您将得到DATABASE_ERROR的错误信息，如图7所示。
If there is something wrong with the database, you get the error message of DATABASE_ERROR, as shown in Figure 7.
如果出现数据库连接错误，文本输出不需要封装到任何标记中，因为简单输出无需任何标记即可在此电话上正确显示。
The text output in the case of an error making the connection to the database is not wrapped in any kind of markup because simple output displays correctly on the phone without the markup.
如果出现错误，您可以将其记录到错误日志或数据库中，或发送一封警告电子邮件。
If you get an error, you can write an entry in an error log or a database, or send a warning E-mail message.
如果在客户机和主机SVR1上的SALES数据库之间出现通信错误，客户机首先尝试重新连接主机SVR1上的SALES数据库。
If a communication error occurs between a client and the SALES database at host SVR1, the client will first attempt to reconnect to the SALES database on host SVR1.
但是，当尝试连接到数据库时，在 db2diag.log 中可能间歇地出现如下错误消息。
However, the following message occurs intermittently in the db2diag.log when trying to connect to the database.
初始化过程完成之后，查看以下日志文件，确认数据库初始化过程中没有出现错误。
When initialization is complete, view the following log files to make sure there were no errors in the database initialization process.
最后一个事件将会发生于每一个控件之上,然后,一直到结束.这时,所有的控件将会输出流并且不能够再被改变.在这个事件中,任何试图访问应答流的方法将都会出现错误.这个事件主要被用来清除善后工作,比如说数据库连接,打开的文件流,事件日志,或者其他的任务等等.
At this point, all controls have been rendered to the output stream and cannot be changed. During this event any attempt to access the response stream will result in an exception being thrown.
从配置文件读取信息时出现错误。无法恢复数据库。
Error in reading information from configuration files. Can not restore the database.
由于数据库快照不是冗余存储，因此，它们不会防止磁盘出现错误或其他类型的损坏。
Because database snapshots are not redundant storage, they do not protect against disk errors or other types of corruption.
但是当数据库中存储的信息本身存在一些拼写错误时，这些拼错的信息只能在用户查询并出现同样的错误时才能被查询出来，这很杯具。
But if there are some misspellings in the database, information that is misspelt will only be found by users doing the same mistake when they query; not a desirable situation.
将已存在的书本或表格中的数据用人工方法录入到数据库中是一项繁重的工作，且容易出现错误。
It is a hard work to input data of table or books copy to database by manual work.
恢复对本地用户数据库所作的改动时，出现了一个内部错误。
An internal error occured while attempting to rollback the changes you made to the local user database.
恢复对本地用户数据库所作的改动时，出现了一个内部错误。
An internal error occured while attempting to rollback the changes you made to the local user database.
应用推荐