Up Prev Next
<Frederic dot Pochet at cockerill-sambre dot com>
Subject: RE: only one record in table
Date: Aug 2 1999 1:55PM
Perhaps, thr row size of your table net_hw is much bigger than the other
try the following command for each table:
PS: sp_estspace stand for est(imate)space...
DBA DB Distribuées
Tel: +32 4 236 20 71
Fax: +32 4 236 21 00
Sent: lundi 2 août 1999 15:31
To: SybPerl Discussion List
Subject: Re: only one record in table
First, let me say thank you.
I did have exactly 0 kb available, so
I altered the database. (changed it to 10 MB)
It works now.
Here's one thing, that I still don't understand:
I kept a sharp eye on the output of "sp_helpdb db2"
The free space never changes whenever I insert a row into other tables
located in db2.
It's just when I insert a row into the table "net_hw", the free space gets
What could make this table so different to other tables?
Pochet Frédéric schrieb:
> You don't have any space available.
> - One reason may be that your log is on the same device as your data (you
> have the message data and log when you issue the command 'sp_helpdb db2'
> isql) and you don't put the 'trunc log on chkpoint' option on the db db2
> you never truncate the log. If so, your space my be reclaim with the
> following command: dump tran db2 with truncate_only.
> - a secon reason: your data fills your data device. You have to define a
> one (disk init ...) and alter your database 'alter database db2 on
> new_dev=' to add more space.
> best regards
> Frédéric POCHET
> DBA DB Distribuées
> Cockerill Sambre/Usinor
> Tel: +32 4 236 20 71
> Fax: +32 4 236 21 00
> e-mail: firstname.lastname@example.org
> -----Original Message-----
> From: Oliver Scheit [mailto:email@example.com]
> Sent: lundi 2 août 1999 14:14
> To: SybPerl Discussion List
> Subject: only one record in table
> Please excuse my bad knowledge about this.
> I have a table where I can insert one record.
> If I try to insert a second record, I get:
> Message String: Can't allocate space for object 'net_hw' in database
> 'db2' because the 'default' segment is full. If you ran out of space in
> syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or
> sp_extendsegment to increase the size of the segment.
> Server message:
> Message number: 7101, Severity 17, State 1, Line 1
> Message String: Unable to allocate new text value, dbid 5.
> I don't really understand, what is wrong.
> Also, I don't really understand what I'm supposed to do.
> How can I find out whether I ran out of space in syslogs or not?
> How to dump the transaction log?
> If anyone could find the time to give me a hint,
> I'd be grateful.
> Oliver Scheit