Re: Backup Restore. 6.X -> 7.1
Yes I would recommend that you use with no log option whenever explicitly
createing a temp table be it in a create statement or in a select into temp
statement. What I was talking about are implicitly declared table. Examples
would be temp tables for order by causes, or complex joins etc...
these types of statements do not allow you to control how the table will be
built (with no log).
Russ...
} From ellis.oncontact.com!rmy.emory.edu!informix-list-owner Wed Jan 10 17:18:20 1996
} From: "Juan R. Guzman" <jguzman@transre.com>
} Message-Id: <30F42170.72E8@transre.com>
} Subject: Re: Backup Restore. 6.X -> 7.1
} Date: Wed, 10 Jan 1996 20:28:32 GMT
} Reply-To: "Juan R. Guzman" <jguzman@transre.com>
} Organization: Transatlantic Reinsurance Company
} Sender: informix-list-owner@rmy.emory.edu
} To: informix-list@rmy.emory.edu
} X-Informix-List-To: russell@oncontact.com
} X-Informix-List-Id: <news.20174>
}
} Russ Kahler wrote:
} >
} > We just went through a similar problem.
} > Our problem was that we didnot define the dbspace used for temp storage
} > as a temp dbspace. the problem we ran into is that complex queries (any
} > query using a temp table) would generate a temp table that would be logged.
} > since these tables are created by the engine itself you cannot control the
} > logging. the only way to prevent them from being logged is to use a temp
} > dbspace for temp storage. Informix told use this is a "feature" of
} > 7.11 and this is the only way around this problem.
} >
} > I hope this helps....
} > Good Luck...
} > Russ..
} >
} > >
} > > I have problems when I restore a 6.X database backup to informix version 7.1
} > > The backup works fine, but when I start to do work on the database (dbaccess)
} > > I start to get long transactions causing rollbacks of my work.
} > > This happens (obviously) beacuse the logical log are being filled and not
} > > cleared out when they are full. I can avoid the problem by forcing the logs
} > > to be cleared manually using onmode.
} > >
} > > I know that informix 7.1 manages the logs slightly differently but why does
} > > this cause the problem. Is this a bug (oversight) or can it be avoided. No
} > > one in Informix tech support knows or wants to tell me.
} > >
} > > any info would be appriacted
} > >
} > > Dave McCreery
} > > Technical Consultant
} > > Credo Electronic Banking
} > > .
} > >
} > >
} > Russell P. Kahler |||||/// ----------
} > Internet: russell@oncontact.com ======== / Uh...
} > on!contact Software . | O O | /Just reboot
} > W67 N250A Evergreen Blvd | v_' / --> that will /
} > Cedarburg, WI 53012 # _| |_ fix it /
} > (414) 375-6555 (#) ( ) ----------
} > # //|* *|
} > #//( * )/
} > # =====
} > # ( )
} > Blah, Blah, Blah. # || ||
} > .#---'| |----.
} > #----' -----
Just be sure to use the no log option when selecting into temp tables,
because if you don't, your users won't be able create any temp tables.
Russell P. Kahler |||||/// ----------
Internet: russell@oncontact.com ======== / Uh...
on!contact Software . | O O | /Just reboot
W67 N250A Evergreen Blvd | v_' / --> that will /
Cedarburg, WI 53012 # _| |_ fix it /
(414) 375-6555 (#) ( ) ----------
# //|* *|
#//( * )/
# =====
# ( )
Blah, Blah, Blah. # || ||
.#---'| |----.
#----' -----