Cannot add a logical log
A user rebuilt/reinitialized his instance and then couldn't add 10MB logical logs, getting "Cannot add a logical log / ISAM error: DBSpace is full" even though the log dbspace chunk appeared to have free pages. Suggestions were to add logs from another dbspace, add chunks, or create a new log dbspace, plus checks on log size and target dbspace; Art also noted a long-transaction rollback can consume as much log space as the original transaction. The poster resolved it himself: after reinitializing, the reused chunk was reported as empty but was actually still full of the old instance's 100 logical logs, so no real space existed.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi,
I have a recent issue the the logical logs. After rebuilding the whole
database from scratch, no I can't add logical logs. Had no problem before.
I receive error:
Cannot add a logical log.
ISAM error: DBSpace is full.
There is enough space in the log file
4afa6028 2 2 0 524288 514235 PO-B-D /opt/informix/storage/chunks/ts_logdbs
The obvious response is to either add the logical logs from a different
existing dbspace, add more chunks to this dbspace, or create a new dbspace
for the additional logs and add them from there.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Fri, Jan 6, 2017 at 11:16 AM, R MICHAEL <mboncalo@gmail.com> wrote:
> Hi,
> I have a recent issue the the logical logs. After rebuilding the whole
> database from scratch, no I can't add logical logs. Had no problem before.
>
> I receive error:
> Cannot add a logical log.
> ISAM error: DBSpace is full.>
> There is enough space in the log file
>
> 4afa6028 2 2 0 524288 514235 PO-B-D /opt/informix/storage/chunks/ts_logdbs
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--f403045f1c6a544a7405456f66b5
This is a long transaction rollback. It needs almost at much logical log
space to record the rollback as it took to create the original transaction
(unless it was actually a small transaction that went dormant for along
time - like someone started the transaction and went on vacation without
committing it - but in that case the four logs you have already added would
have been enough). So, since you have a transaction that wrote data to most
of the 100 logical logs you already had, it will take nearly that many more
logs to complete the rollback.
That this never happened before is kind of irrelevant since it may be that
no one has ever executed so large a transaction before.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Fri, Jan 6, 2017 at 11:16 AM, R MICHAEL <mboncalo@gmail.com> wrote:
> Hi,
> I have a recent issue the the logical logs. After rebuilding the whole
> database from scratch, no I can't add logical logs. Had no problem before.
>
> I receive error:
> Cannot add a logical log.
> ISAM error: DBSpace is full.>
> There is enough space in the log file
>
> 4afa6028 2 2 0 524288 514235 PO-B-D /opt/informix/storage/chunks/ts_logdbs
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--94eb2c12cad04dd59905456f7383
1 - how big is the log you are trying to add
2 - are you adding it to the right dbspace.
I know, stupid questions, but I would check those first.
j.
On 1/6/17 11:16 AM, R MICHAEL wrote:
> Hi,
> I have a recent issue the the logical logs. After rebuilding the whole
> database from scratch, no I can't add logical logs. Had no problem before.
>
> I receive error:
> Cannot add a logical log.
> ISAM error: DBSpace is full.>
> There is enough space in the log file
>
> 4afa6028 2 2 0 524288 514235 PO-B-D /opt/informix/storage/chunks/ts_logdbs
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
I reinitialized ids and used the same chunk for logical logs, didn't create another one..I added 100 Llogs in the old instance using the same chung. Should I create new dbspace for logical log and delete the old one ?
yes to both
sorry, 1. 10 MB 2 yes
As I suspected, after i reinitialized the instance, rootdbs started new and after added the log space as empty when it was almose full from adding Llogs in other instance. So there was no space in the log dbspace even if it showed like it's enough. thank you for your support!