sybperl-l Archive

From: =?iso-8859-1?Q?Pochet_Fr=E9d=E9ric?= <Frederic dot Pochet at cockerill-sambre dot com>
Subject: RE: only one record in table
Date: Aug 2 1999 12:49PM

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' in
isql) and you don't put the 'trunc log on chkpoint' option on the db db2 and
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 new
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: frederic.pochet@cockerill-sambre.com


-----Original Message-----
From: Oliver Scheit [mailto:oscheit@quoka.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.

Regards,
Oliver Scheit