Eldon, If you want to drop and recreate the table, you could always split the job into a couple of stages. The first could drop and recreate the table as a suitable user. The remainder of the job could then continue as it currently does.
Cheers, Jeremy Eldon B Tucker wrote: > I've been looking at the use of NOT LOGGED INITIALLY > under UDB EEE 7.1 on AIX. I have a question or two, and > would like comments on a particular idea. > > If I have a large table being rebuilt via SQL > (INSERT INTO SELECT) and am using ALTER TABLE ACTIVATE > NOT LOGGED INITIALLY to keep the command from being > logged, what database resources are getting locked? > > I've noticed that while a table is being populated > in this situation, another job fails when trying to > do an RUNSTATS on an unrelated table. Could the > NOT LOGGED INITIALLY be causing the system tables to > be locked, blocking the RUNSTATS in another job from > updating the system statistics on the other table? > > Also, regarding an idea that I have that I'd like an > opinion on. > > I'd like to rebuilt through SQL a large table using > NOT LOGGED INITIALLY. There might be occasional (but > unlikely) situations where the insert fails and the > table is left in a permanently bad state. In that case, > someone would have to drop and recreate the table before > the job could be restarted. > > In order to automate this, I'd like to see the job > always drop and recreate the table before using it > once a night. The only catch is > that the batch jobs don't run with a userid that permits > dropping and recreating tables in our production database. > > My idea is that the tables in question be changed to > aliases (having the proper ownership) pointing to the > tables that the batch program would drop and recreate each > time under its own userid. > > Is this idea workable? Has anyone tried this? What are the > other limitations and workarounds for use of NOT LOGGED > INITIALLY in UDB 7.1? > > -- Eldon Tucker > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** You are subscribed to [EMAIL PROTECTED] > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** You are subscribed to [EMAIL PROTECTED] *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
