Обсуждение: Error in MS Access

Hi,

My database users are getting following error:

ODBC-call failed
Error while executing query
Error: ItsWriteBlock: failed to write block 1 of temporary file
Perhaps out of disk space (#1)

This happens in front-end Access. Could anyone shed some light on this? Thank you.

Rocky

On Mon, May 15, 2006 at 10:38:47AM -0500, Xu, Xiaoyi (Rocky) FSM wrote:
> Hi,
>
> My database users are getting following error:
>
> ODBC-call failed
> Error while executing query
> Error: ItsWriteBlock: failed to write block 1 of temporary file
> Perhaps out of disk space (#1)

Does the command work when you try it from psql?

Someone on the ODBC or interfaces list might be better able to help,
btw.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

On Mon, May 15, 2006 at 12:56:16PM -0500, Xu, Xiaoyi (Rocky) FSM wrote:
> Thank you Andy.
>
> The server is SunOS 5.8 Generic_117350-29 ultra-250. The db is version 7.

7.what?

> I checked disk (df -k) telling me /home0 is full 100% that has DB on. Former DBA has notes to delete large log files
(server.log).But this time I didn't find same file. I saw pg_log file 4.6 MB timestamped May 9. 

Be *VERY* careful about deleting anything in $PGDATA. A file called
pg_log is probably safe, but you never know...

4.6MB certainly isn't going to get you very far. How large is /home0?
How large is the database? How often have you been vacuuming?
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

Jim,

I will find out the detailed version. Meanwhile /home0 is around 8.6 GB.
I don't know how large the DB is. Which file or which command I should
look for? About vacuuming, I don't know either. Can I do vacuuming while
making DB online? I am helping an internal department whose IT person
left and for 5 months no one ever managed this Solaris box. All of
sudden database users began to experience problems with an in-house
application.

Thank you again and I really appreciate all your help and other's help
from this community.

Rocky

-----Original Message-----
From: Jim C. Nasby [mailto:jnasby@pervasive.com]
Sent: Monday, May 15, 2006 2:42 PM
To: Xu, Xiaoyi (Rocky) FSM
Cc: andy.shellam@mailnetwork.co.uk; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error in MS Access

On Mon, May 15, 2006 at 12:56:16PM -0500, Xu, Xiaoyi (Rocky) FSM wrote:
> Thank you Andy.
>
> The server is SunOS 5.8 Generic_117350-29 ultra-250. The db is version
7.

7.what?

> I checked disk (df -k) telling me /home0 is full 100% that has DB on.
Former DBA has notes to delete large log files (server.log). But this
time I didn't find same file. I saw pg_log file 4.6 MB timestamped May
9.

Be *VERY* careful about deleting anything in $PGDATA. A file called
pg_log is probably safe, but you never know...

4.6MB certainly isn't going to get you very far. How large is /home0?
How large is the database? How often have you been vacuuming?
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

On Mon, May 15, 2006 at 02:55:04PM -0500, Xu, Xiaoyi (Rocky) FSM wrote:
> Jim,
>
> I will find out the detailed version. Meanwhile /home0 is around 8.6 GB.
> I don't know how large the DB is. Which file or which command I should
> look for? About vacuuming, I don't know either. Can I do vacuuming while
> making DB online? I am helping an internal department whose IT person
> left and for 5 months no one ever managed this Solaris box. All of
> sudden database users began to experience problems with an in-house
> application.

If it's anything newer than 7.2 (and I really hope it's a *lot* newer
than that), then yes, you can vacuum without locking users out. I know
that at some point you couldn't do that, but I don't know how long ago
that was since I started using PostgreSQL at version 7.2.

I suspect that no one has been vacuuming the database and that it now
has scads of dead rows. It's surprising users haven't been screaming
about it being slow before now if that's the case.

If you search for 'vacuum' at
http://www.pervasivepostgres.com/instantkb13/search.aspx you'll find
some articles that might help you.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

Jim C. Nasby wrote:
> On Mon, May 15, 2006 at 12:56:16PM -0500, Xu, Xiaoyi (Rocky) FSM wrote:
>> Thank you Andy.
>>
>> The server is SunOS 5.8 Generic_117350-29 ultra-250. The db is version 7.
>
> 7.what?
>
>> I checked disk (df -k) telling me /home0 is full 100% that has DB on. Former DBA has notes to delete large log files
(server.log).But this time I didn't find same file. I saw pg_log file 4.6 MB timestamped May 9. 
>
> Be *VERY* careful about deleting anything in $PGDATA. A file called
> pg_log is probably safe, but you never know...

Well pg_log is the default logging location of PostgreSQL as of 8.1 (if
it is not logging to syslog), thus anything within there *should* be safe.

However, Jim is correct... be very, very careful in that directory.

>
> 4.6MB certainly isn't going to get you very far. How large is /home0?
> How large is the database? How often have you been vacuuming?


Joshua D. drake


--

            === The PostgreSQL Company: Command Prompt, Inc. ===
      Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
      Providing the most comprehensive  PostgreSQL solutions since 1997
                     http://www.commandprompt.com/