I get this message all the time when running a CREATE TABLE without
commitment control - I'd say it's a normal thing. SQL makes an
assumption that you usually want to run with commitment control, hence,
you need to journal. But this may be a time that it is not needed.
So if you don't need to recover data, and if is not a transactional
situation, this is of no importance, in all likelihood.
On 3/6/2014 5:14 PM, 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
Message ID . . . . . . :
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
should not be started, the default journal did not exist, or the
journal did exist but the journaling could not be started. The
journal may be damaged, unable to accept journal entries, or may not
The SQL name for the table is DTAWHSO and the system name for the table
DTAWHSO. For a distributed table, journaling could not be started on all
the systems. The default journal must exist, and be able to accept
entries, on each of the systems in the node
Recovery . . . : The table was created, but until the table is
COMMIT(*CHG), COMMIT(*CS), COMMIT(*RS), COMMIT(*RR), COMMIT(*UR),
and COMMIT(*ALL) will not be allowed for table DTAWHSO.