MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

Re: table not journaled



fixed

On 06-Mar-2014 15:14 -0800, Hoteltravelfundotcom wrote:
I created a table to be used as a Data Warehouse table to our
reporting tool or even on the i. This is going to be refreshed
nightly. It will be used strictly in a reporting mode.
Do we need to be concerned about the Not Journal status?

Message ID : SQL7905
Message. . : Table DTAWHSO in PROJ_T1 created but was not journaled.
<<SNIP>>
Recovery . : The table was created, but until the table is
journaled, COMMIT(*CHG), COMMIT(*CS), COMMIT(*RS), COMMIT(*RR),
COMMIT(*UR), and COMMIT(*ALL) will not be allowed for table DTAWHSO.

The "Recovery" explains whether a concern is warranted; i.e. if an isolation level other than NC [no-commit] is required, for any reason when accessing the file [data; i.e. effectively just for DML, including SELECT], then the data access will fail [with SQL7008]. To ensure a SELECT does not operate with a commitment-control\isolation level other than *NC, then use\append the WITH NC clause to the request.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact