Hello. I keep getting these errors from eventviewer and I am not sure what is happening. I can't find these tables in the database because it looks like it is a temp table. Here is the event viewer error verbatim.
Event Type: Error
Event Source: RISKMSTR
Event Category: None
Event ID: 4
Date: 5/18/2004
Time: 8:47:04 PM
User: N/A
Computer: ICMRESOURCE01
Description:
2004-05-18-20.47.04.749000 Instance:RISKMSTR Node:000
PID:1568(db2syscs.exe) TID:400 Appid:C0A8A815.DA0C.025D09014634
data management sqldEndNoLogList Probe:1 Database:RISKMAST
ADM5530E The COMMIT processing of table "RISK .CLAIM_TEMP_IT" that used NOT
LOGGED INITIALLY has been initiated. It is recommended that you take a backup
of this table's table space(s).
I found this explanation on another forum but it doesn't give the solution. Please help!
Because changes to the table are not logged, you should consider the
following when deciding to use the NOT LOGGED INITIALLY table attribute:
a.. All changes to the table will be flushed out to disk at commit
time. This means that the commit may take longer.
b.. If the NOT LOGGED INITIALLY attribute is activated and an activity
occurs that is not logged, the entire unit of work will be rolled back if a
statement fails or a ROLLBACK TO SAVEPOINT is executed (SQL1476N).
c.. You cannot recover these tables when rolling forward. If the
rollforward operation encounters a table that was created or altered with
the NOT LOGGED INITIALLY option, the table is marked as unavailable. After
the database is recovered, any attempt to access the table returns SQL1477N.
Note:
When a table is created, row locks are held on the catalog tables
until a COMMIT is done. To take advantage of the no logging behavior, you
must populate the table in the same unit of work in which it is created.
This has implications for concurrency
Thanks.
Event Type: Error
Event Source: RISKMSTR
Event Category: None
Event ID: 4
Date: 5/18/2004
Time: 8:47:04 PM
User: N/A
Computer: ICMRESOURCE01
Description:
2004-05-18-20.47.04.749000 Instance:RISKMSTR Node:000
PID:1568(db2syscs.exe) TID:400 Appid:C0A8A815.DA0C.025D09014634
data management sqldEndNoLogList Probe:1 Database:RISKMAST
ADM5530E The COMMIT processing of table "RISK .CLAIM_TEMP_IT" that used NOT
LOGGED INITIALLY has been initiated. It is recommended that you take a backup
of this table's table space(s).
I found this explanation on another forum but it doesn't give the solution. Please help!
Because changes to the table are not logged, you should consider the
following when deciding to use the NOT LOGGED INITIALLY table attribute:
a.. All changes to the table will be flushed out to disk at commit
time. This means that the commit may take longer.
b.. If the NOT LOGGED INITIALLY attribute is activated and an activity
occurs that is not logged, the entire unit of work will be rolled back if a
statement fails or a ROLLBACK TO SAVEPOINT is executed (SQL1476N).
c.. You cannot recover these tables when rolling forward. If the
rollforward operation encounters a table that was created or altered with
the NOT LOGGED INITIALLY option, the table is marked as unavailable. After
the database is recovered, any attempt to access the table returns SQL1477N.
Note:
When a table is created, row locks are held on the catalog tables
until a COMMIT is done. To take advantage of the no logging behavior, you
must populate the table in the same unit of work in which it is created.
This has implications for concurrency
Thanks.