× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



If you don't want the table journaled, don't worry about it.

Usually, you would have created a SCHEMA and this processed would have
setup the appropriate journalling objects. Then, any tables created in
this schema would be journalled.




"Brian Piotrowski" <bpiotrowski@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/03/2007 11:00 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
CREATE TABLE not Journaled






Hi Group,



Instead of creating physical files and compiling to our data library,
I'm thinking of going directly into the SQL interpreter and performing a
"CREATE TABLE" command. I did a small test using SQL, but when I
completed it, I received a message that said:



Message . . . . : Table WD_CONTROL in SPSL created but could not be


journaled.


Cause . . . . . : The table WD_CONTROL was created in SPSL, but the
table

could not be journaled. The journal QSQJRN in SPSL may be damaged,
removed,

unable to accept journal entries, or may not be created. The SQL name
for

the table is WD_CONTROL and the system name for the table is
WD_CONTROL. For

a distributed table, journaling could not be started on all of the
systems.

The journal QSQJRN in SPSL 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), and COMMIT(*ALL) will not be allowed for
table

WD_CONTROL.



I'm a bit concerned with this message, as we are moving to a HA solution
in the near future that will use remote journaling as it's method of
detecting changes. Of course, this may be a message that I don't have
to worry about, so I thought I'd throw it out to the group for opinions.



The table's data will be added/modified/deleted through an ASP (windows
web) program (no AS400 programs will be accessing this table). The
remainder of this message goes on to tell me to either create the
journal or fix the journal.



I'm a bit foggy on how this "Create journal" process works when you
compile a PF from a source file vs. creating a table from a CREATE TABLE
command. I don't recall seeing a similar message when I compile a PF
from a source file.



Based on this information, what would the group suggest that I need to
do to ensure that this data will be moved from our production i5 to the
backup i5 within the HA system?



Thanks in advance!



Brian.

-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.