MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

table not journaled



fixed

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.
here is the message:
was not journaled. Either a QDFTJRN data area indicated that
journaling
should not be started, the default journal did not exist, or the
default
journal did exist but the journaling could not be started. The
default
journal may be damaged, unable to accept journal entries, or may not
exist.
The SQL name for the table is DTAWHSO and the system name for the table
is
DTAWHSO. For a distributed table, journaling could not be started on all
of
the systems. The default journal must exist, and be able to accept
journal
entries, on each of the systems in the node
group.
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.





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