All 6 messages in topic - view as tree
From: Darren_Jac...@carmax.com - view profile
Date: Fri, Dec 1 2006 4:38 am
Email: Darren_Jac...@carmax.com
IDS 9.40 FC2XA
HPUX 11.11
Greetings,
I have a very interesting situation that started about a week ago. My
onbar logical log backups are being "Aborted by client" (online.log). The
bar_act.log file indicates "SQL 4294967025 Could not insert new row into
table." followed by "ISAM 4294967165 ISAM error: no free disk space".
The interesting thing is that after a onbar whole system backup completes
all logical log files backup without issue. Another interesting thing is
that TSM is indicating a 102 meg log file is being backed up.
Any help or insight would be greatly appreciated.
TIA
The logical log files backup via ALARMPROGRAM
/usr/informix/etc/log_full.sh.
log_full.sh
BACKUP_CMD="onbar -b -l"
onbar archive cmd:
onbar -b -w -L 0
sm_versions linked to sm_versions.tdp
1|5.2.1|adsm|5|
114 logfiles @ 100 meg
online.log
21:04:04 Maximum server connections 92
21:04:10 Logical Log 75915 Complete, timestamp:900189386.
21:04:11 Logical Log 75861 - Backup Started
21:08:27 Logical Log 75861 - Backup Aborted
Aborted by client.
21:08:32 Logical Log 75861 - Backup Started
21:08:45 Logical Log 75861 - Backup Aborted
Aborted by client.
21:08:51 Process exited with return code 139: /bin/sh /bin/sh -c
/usr/informix/
etc/log_full.sh 2 23 "Logical Log 75915 Complete, timestamp:900189386."
"Logical
Log 759
bar_act.log
2006-11-30 21:08:32 13638 13636 Begin backup logical log 75861.
2006-11-30 21:08:32 13638 13636 Successfully connected to Storage Manager.
2006-11-30 21:08:45 13638 13636 SQL 4294967025 Could not insert new
row
into the table.
2006-11-30 21:08:45 13638 13636 ISAM 4294967165 ISAM error: no free
disk
space
2006-11-30 21:08:50 13638 13636 SQL 4294967025 Could not insert new
row
into the table.
2006-11-30 21:08:50 13638 13636 ISAM 4294967165 ISAM error: no free
disk
space
2006-11-30 21:08:50 13638 13636 /usr/informix/bin/onbar_d complete,
returning
48 (0x94)
Reply » Rate this post: Text for clearing space
From: Ogiwara Tsutomu - view profile
Date: Fri, Dec 1 2006 5:26 am
Email: "Ogiwara Tsutomu"
Hi Darren.
Sounds like you do not have enouch space in ROOTDBS.
Probably, onbar attempted insert to bar_xxx of sysutils database.
[tsutoo@urraco ~]tsutoo100fc5% oncheck -pe | grep bar
sysutils:'informix'.bar_server 10498
8
sysutils:'informix'.bar_object 10506
8
sysutils:'informix'.bar_obj_idx 10514
7
sysutils:'informix'.bar_action 10521
8
sysutils:'informix'.bar_act_idx 10533
4
sysutils:'informix'.bar_instance 10545
8
Just my $0.02.
--
Tsutomu Ogiwara from Tokyo Japan.
- Hide quoted text -
- Show quoted text -
>From: Darren_Jac...@carmax.com
>To: informix-l...@iiug.org
>Subject: onbar log backups aborting w/TSM
>Date: Thu, 30 Nov 2006 21:38:49 -0500
>IDS 9.40 FC2XA
>HPUX 11.11
>Greetings,
>I have a very interesting situation that started about a week ago. My
>onbar logical log backups are being "Aborted by client" (online.log). The
>bar_act.log file indicates "SQL 4294967025 Could not insert new row into
>table." followed by "ISAM 4294967165 ISAM error: no free disk
space".
>The interesting thing is that after a onbar whole system backup completes
>all logical log files backup without issue. Another interesting thing is
>that TSM is indicating a 102 meg log file is being backed up.
>Any help or insight would be greatly appreciated.
>TIA
>The logical log files backup via ALARMPROGRAM
>/usr/informix/etc/log_full.sh.
>log_full.sh
>BACKUP_CMD="onbar -b -l"
>onbar archive cmd:
>onbar -b -w -L 0
>sm_versions linked to sm_versions.tdp
>1|5.2.1|adsm|5|
>114 logfiles @ 100 meg
>online.log
>21:04:04 Maximum server connections 92
>21:04:10 Logical Log 75915 Complete, timestamp:900189386.
>21:04:11 Logical Log 75861 - Backup Started
>21:08:27 Logical Log 75861 - Backup Aborted
> Aborted by client.
>21:08:32 Logical Log 75861 - Backup Started
>21:08:45 Logical Log 75861 - Backup Aborted
> Aborted by client.
>21:08:51 Process exited with return code 139: /bin/sh /bin/sh -c
>/usr/informix/
>etc/log_full.sh 2 23 "Logical Log 75915 Complete, timestamp:900189386."
>"Logical
> Log 759
>bar_act.log
>2006-11-30 21:08:32 13638 13636 Begin backup logical log 75861.
>2006-11-30 21:08:32 13638 13636 Successfully connected to Storage
Manager.
>2006-11-30 21:08:45 13638 13636 SQL 4294967025 Could not insert
new
>row
>into the table.
>2006-11-30 21:08:45 13638 13636 ISAM 4294967165 ISAM error: no free
>disk
>space
>2006-11-30 21:08:50 13638 13636 SQL 4294967025 Could not insert
new
>row
>into the table.
>2006-11-30 21:08:50 13638 13636 ISAM 4294967165 ISAM error: no free
>disk
>space
>2006-11-30 21:08:50 13638 13636 /usr/informix/bin/onbar_d complete,
>returning
>48 (0x94)
>_______________________________________________
>Informix-list mailing list
>Informix-l...@iiug.org
>http://www.iiug.org/mailman/listinfo/informix-list
_________________________________________________________________
「セキュリティ＋PCメンテナンス」を提供するWindows Live OneCare ベータ版（無
料）を今すぐトライ！ http://ideas.live.com/
Reply » Rate this post: Text for clearing space
From: John Carlson - view profile
Date: Fri, Dec 1 2006 6:07 am
Email: John Carlson
On Thu, 30 Nov 2006 21:38:49 -0500, Darren_Jac...@carmax.com wrote:
>IDS 9.40 FC2XA
>HPUX 11.11
>Greetings,
>I have a very interesting situation that started about a week ago. My
>onbar logical log backups are being "Aborted by client" (online.log). The
>bar_act.log file indicates "SQL 4294967025 Could not insert new row into
>table." followed by "ISAM 4294967165 ISAM error: no free disk space".
>The interesting thing is that after a onbar whole system backup completes
>all logical log files backup without issue. Another interesting thing is
>that TSM is indicating a 102 meg log file is being backed up.
Sysutils database is usually in the rootdbs, along with any temp
tables that may be created there as well.
How much space is free in rootdbs?
How busy is rootdbs?
Can you purge any data from the bar_?????? tables?
JWC
Reply » Rate this post: Text for clearing space
From: Floyd Wellershaus - view profile
Date: Fri, Dec 1 2006 2:08 pm
Email: Floyd Wellershaus
Darren,
If your sysutils is getting too big and filling up rootdbs, you should run onsmsync regularly.
I run it once a month in cron. It gets rid of all info about backups that Tivoli doesn't know about anymore, from your sysutils and from your $INFORMIXDIR/etc/ixbar files.
========================
-<
Database Administrator
Unix Administrator
email: fwell...@yahoo.com
Home: 703-430-0805
Cell: 703-477-6045
========================
http://www.one.org/
- Hide quoted text -
- Show quoted text -
----- Original Message ----
From: "Darren_Jac...@carmax.com"
To: informix-l...@iiug.org
Sent: Thursday, November 30, 2006 9:38:49 PM
Subject: onbar log backups aborting w/TSM
IDS 9.40 FC2XA
HPUX 11.11
Greetings,
I have a very interesting situation that started about a week ago. My
onbar logical log backups are being "Aborted by client" (online.log). The
bar_act.log file indicates "SQL 4294967025 Could not insert new row into
table." followed by "ISAM 4294967165 ISAM error: no free disk space".
The interesting thing is that after a onbar whole system backup completes
all logical log files backup without issue. Another interesting thing is
that TSM is indicating a 102 meg log file is being backed up.
Any help or insight would be greatly appreciated.
TIA
The logical log files backup via ALARMPROGRAM
/usr/informix/etc/log_full.sh.
log_full.sh
BACKUP_CMD="onbar -b -l"
onbar archive cmd:
onbar -b -w -L 0
sm_versions linked to sm_versions.tdp
1|5.2.1|adsm|5|
114 logfiles @ 100 meg
online.log
21:04:04 Maximum server connections 92
21:04:10 Logical Log 75915 Complete, timestamp:900189386.
21:04:11 Logical Log 75861 - Backup Started
21:08:27 Logical Log 75861 - Backup Aborted
Aborted by client.
21:08:32 Logical Log 75861 - Backup Started
21:08:45 Logical Log 75861 - Backup Aborted
Aborted by client.
21:08:51 Process exited with return code 139: /bin/sh /bin/sh -c
/usr/informix/
etc/log_full.sh 2 23 "Logical Log 75915 Complete, timestamp:900189386."
"Logical
Log 759
bar_act.log
2006-11-30 21:08:32 13638 13636 Begin backup logical log 75861.
2006-11-30 21:08:32 13638 13636 Successfully connected to Storage Manager.
2006-11-30 21:08:45 13638 13636 SQL 4294967025 Could not insert new
row
into the table.
2006-11-30 21:08:45 13638 13636 ISAM 4294967165 ISAM error: no free
disk
space
2006-11-30 21:08:50 13638 13636 SQL 4294967025 Could not insert new
row
into the table.
2006-11-30 21:08:50 13638 13636 ISAM 4294967165 ISAM error: no free
disk
space
2006-11-30 21:08:50 13638 13636 /usr/informix/bin/onbar_d complete,
returning
48 (0x94)
_______________________________________________
Informix-list mailing list
Informix-l...@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
Reply » Rate this post: Text for clearing space
From: Martin Fuerderer - view profile
Date: Fri, Dec 1 2006 5:53 pm
Email: Martin Fuerderer
Hi,
right. sysutils in rootdbs, probably some temp table (also
in rootdbs) during dbspace backup uses additional space,
so that you hit the ceiling ...
You should not "purge" things from the sysutils database, at least
not by manually connecting to the database and issuing "DELETE"
statements. This can easily cause you a lot of trouble in case of
a restore.
What you can (and should) do (more or less regularly) is to use
"onsmsync" utility to expire old backups (dbspaces and log files).
This will also delete entries from the systutils database. Please see
the manual "Backup and Restore Guide" for more info on "onsmsync".
That will avoid this situation in the future.
"oncheck -pe" shows which table has allocated how many pages,
as already noted.
In the short run you will probably have to add a chunk to the root
dbspace to make it work again. If you don't have temp dbspaces
yet, you can create some (and list them in onconfig file). It may help.
It is also possible that setting PSORT_DBTEMP environment variable
helps. This would cause the use of file system disk space rather than
temp dbspaces (or root dbspace) for sort tasks.
The backup of a log file does not only contain the log records from
the log file itself, but also any BLOBSpace BLOBs that have been
manipulated in corresponding transactions (log records). This is
necessary because BLOBSpace BLOBs themselves are not in the
logical log files. With that the backup of a log file can be much larger
than the log file itself.
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
Informix URLs list: http://home.arcor.de/mfu1/informix/urls.html
informix-list-boun...@iiug.org wrote on 01.12.2006 05:07:43:
- Hide quoted text -
- Show quoted text -
> On Thu, 30 Nov 2006 21:38:49 -0500, Darren_Jac...@carmax.com wrote:
> >IDS 9.40 FC2XA
> >HPUX 11.11
> >Greetings,
> >I have a very interesting situation that started about a week ago. My
> >onbar logical log backups are being "Aborted by client" (online.log).
The
> >bar_act.log file indicates "SQL 4294967025 Could not insert new row
into
> >table." followed by "ISAM 4294967165 ISAM error: no free disk
space".
> >The interesting thing is that after a onbar whole system backup
completes
> >all logical log files backup without issue. Another interesting thing
is
> >that TSM is indicating a 102 meg log file is being backed up.
> Sysutils database is usually in the rootdbs, along with any temp
> tables that may be created there as well.
> How much space is free in rootdbs?
> How busy is rootdbs?
> Can you purge any data from the bar_?????? tables?
> JWC
> _______________________________________________
> Informix-list mailing list
> Informix-l...@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
Reply » Rate this post: Text for clearing space
From: Sebastian, Norma J. - view profile
Date: Fri, Dec 1 2006 6:06 pm
Email: "Sebastian, Norma J."
Martin is the onbar king! :)
I would just like to add a comment about the onsmsync utility.
It is good and it works, but if you have not used it regularly, please
be cautious about using it.... run it first in a test copy of your prod
system because if you run it in prod when you have not done so in a long
time.... well, it can create a performance issue....
Speaking from experience of course.....
Norma Jean Sebastian
ERP Support Administration
GIS- Enterprise Technical Services
- Hide quoted text -
- Show quoted text -
-----Original Message-----
From: informix-list-boun...@iiug.org
[mailto:informix-list-boun...@iiug.org] On Behalf Of Martin Fuerderer
Sent: Friday, December 01, 2006 9:54 AM
To: Darren_Jac...@carmax.com
Cc: informix-list-boun...@iiug.org; informix-l...@iiug.org
Subject: Re: onbar log backups aborting w/TSM
Hi,
right. sysutils in rootdbs, probably some temp table (also
in rootdbs) during dbspace backup uses additional space,
so that you hit the ceiling ...
You should not "purge" things from the sysutils database, at least
not by manually connecting to the database and issuing "DELETE"
statements. This can easily cause you a lot of trouble in case of
a restore.
What you can (and should) do (more or less regularly) is to use
"onsmsync" utility to expire old backups (dbspaces and log files).
This will also delete entries from the systutils database. Please see
the manual "Backup and Restore Guide" for more info on "onsmsync".
That will avoid this situation in the future.
"oncheck -pe" shows which table has allocated how many pages,
as already noted.
In the short run you will probably have to add a chunk to the root
dbspace to make it work again. If you don't have temp dbspaces
yet, you can create some (and list them in onconfig file). It may help.
It is also possible that setting PSORT_DBTEMP environment variable
helps. This would cause the use of file system disk space rather than
temp dbspaces (or root dbspace) for sort tasks.
The backup of a log file does not only contain the log records from
the log file itself, but also any BLOBSpace BLOBs that have been
manipulated in corresponding transactions (log records). This is
necessary because BLOBSpace BLOBs themselves are not in the
logical log files. With that the backup of a log file can be much larger
than the log file itself.
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
Informix URLs list: http://home.arcor.de/mfu1/informix/urls.html
informix-list-boun...@iiug.org wrote on 01.12.2006 05:07:43:
> On Thu, 30 Nov 2006 21:38:49 -0500, Darren_Jac...@carmax.com wrote:
> >IDS 9.40 FC2XA
> >HPUX 11.11
> >Greetings,
> >I have a very interesting situation that started about a week ago.
My
> >onbar logical log backups are being "Aborted by client" (online.log).
The
> >bar_act.log file indicates "SQL 4294967025 Could not insert new row
into
> >table." followed by "ISAM 4294967165 ISAM error: no free disk
space".
> >The interesting thing is that after a onbar whole system backup
completes
> >all logical log files backup without issue. Another interesting
thing
is
> >that TSM is indicating a 102 meg log file is being backed up.
> Sysutils database is usually in the rootdbs, along with any temp
> tables that may be created there as well.
> How much space is free in rootdbs?
> How busy is rootdbs?
> Can you purge any data from the bar_?????? tables?
> JWC
> _______________________________________________
> Informix-list mailing list
> Informix-l...@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
_______________________________________________
Informix-list mailing list
Informix-l...@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================
Reply » Rate this post: Text for clearing space
End of messages
No comments:
Post a Comment