Re: [Info-Ingres] persistent .d00 tables in data area -
08-24-2010
, 02:38 AM
Hi Graham,
Checked in iifile_info and there was no mention of them.
The files were removed when I did a ckpdb +j to backup the system before I started the verifydb -o purge. The latter removed a shit load of files fromthe work area as well.
It seems the ordinary checkpoint of this database ... which is schedulled weekly did not remove the files.
Marty
From: Newlands, Graham [mailto:Graham.Newlands (AT) au (DOT) fujitsu.com]
Sent: 24 August 2010 00:31
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] persistent .d00 tables in data area
Hi Marty,
Sounds like a good approach to start with...
You can also query the system catalogues as well to see if there is a tabledefined with a .d00 extension filename (ii_filesysteminfo or similar ?), that way after you do your backup and if the purge option doesn't work you can possibly just remove the files safely...
I would also perform your task during a scheduled maintenance time though with enough time to perform a rollback...
G
________________________________
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin Bowes
Sent: Monday, 23 August 2010 7:36 PM
To: Ingres and related product discussion forum
Subject: [Info-Ingres] persistent .d00 tables in data area
Hi All,
I have a 9.1.1 (a64.lnx/103)NPTL + p13001 installation.
On one database of the many we find a persistent set of files in the data area named with a '.d00' extension. These things have now accumulated to an extent that they make up about 50% of the data area.
I'd assumed that these were associated with an uncommitted drop table transaction. However, they have a mixture of create dates ranging from recent (Aug 20) to less so (Apr 20). The log file is empty.
It appears to me that these may be associated with transactions that have been aborted due to lack of space in the workfile area and that the subsequent rollback has failed to remove the file.
My temptation is to backup the database and then do a verifydb -mrun -o purge on the database and see if they go away.
Would anyone like to comment on that?
Marty
This is an email from Fujitsu Australia Limited, ABN 19 001 011 427. It is confidential to the ordinary user of the email address
to which it was addressed and may contain copyright and/or legally privileged information. No one else may read, print, store, copy
or forward all or any of it or its attachments. If you receive this email in error, please return to sender. Thank you.
If you do not wish to receive commercial email messages from Fujitsu Australia Limited, please email unsubscribe (AT) au (DOT) fujitsu.com |