怎樣Import時候不記錄日志

wangkai8

需要向一個表中Import幾百萬條記錄，按照以前論壇上說得的方法，
alter table ab activate not logged initially
import from ..... insert into ....
但是依然報事務日志已滿的錯誤，好像依然記錄日志。請問各位如何解決？
不想在import時候用commitcount參數(shù)

huyuhui001

你對這個理解有誤，下面的內(nèi)容是從inforcenter里面節(jié)選出來的。
ACTIVATE NOT LOGGED INITIALLY

1. Any changes made to the table by an INSERT, DELETE, UPDATE, CREATE INDEX, DROP INDEX, or ALTER TABLE in the same unit of work after the table is altered by this statement are not logged. 特別注意，in the same unit of work。

2. Any changes made to the system catalog by the ALTER statement in which the NOT LOGGED INITIALLY attribute is activated are logged.

3. Any subsequent changes made in the same unit of work to the system catalog information are logged.

4. At the completion of the current unit of work, the NOT LOGGED INITIALLY attribute is deactivated and all operations that are done on the table in subsequent units of work are logged.  特別注意這一點，結(jié)合第一點，就是你依然碰到日志滿的原因了。

wangkai8

問一下： in the same unit of work 是啥意思？

huyuhui001

下面是官方準確的解釋。
http://publib.boulder.ibm.com/in ... oc/doc/c0005018.htm


Units of work

A transaction is commonly referred to in DB2 Database for Linux, UNIX, and Windows as a unit of work. A unit of work is a recoverable sequence of operations within an application process. It is used by the database manager to ensure that a database is in a consistent state. Any reading from or writing to the database is done within a unit of work.

For example, a bank transaction might involve the transfer of funds from a savings account to a checking account. After the application subtracts an amount from the savings account, the two accounts are inconsistent, and remain so until the amount is added to the checking account. When both steps are completed, a point of consistency is reached. The changes can be committed and made available to other applications.

A unit of work is started implicitly when the first SQL statement is issued against the database. All subsequent reads and writes by the same application are considered part of the same unit of work. The application must end the unit of work by issuing either a COMMIT or a ROLLBACK statement. The COMMIT statement makes permanent all changes made within a unit of work. The ROLLBACK statement removes these changes from the database. If the application ends normally without either of these statements being explicitly issued, the unit of work is automatically committed. If it ends abnormally in the middle of a unit of work, the unit of work is automatically rolled back. Once issued, a COMMIT or a ROLLBACK cannot be stopped. With some multi-threaded applications, or some operating systems (such as Windows(R)), if the application ends normally without either of these statements being explicitly issued, the unit of work is automatically rolled back. It is recommended that your applications always explicitly commit or roll back complete units of work. If part of a unit of work does not complete successfully, the updates are rolled back, leaving the participating tables as they were before the transaction began. This ensures that requests are neither lost nor duplicated.

There is no physical representation of a unit of work because it is a series of instructions (SQL statements).

[ 本帖最后由 huyuhui001 于 2007-12-2 12:19 編輯 ]

w3231717

LOAD 是不寫日志的

有瑕

把你的那兩條語句放一個腳本里面，執(zhí)行時用db2 +c -tvf a.db2

weizeyan

用load吧。