Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Frank Langelage ran IDS 11.10.UB4TL beta on Solaris and found rootdbs repeatedly filling, with SCHAPI errors -271 and -131 for the mon_vps sensor in online.log. Fernando Nunes pointed to scheduled tasks in sysadmin. Art Kagel explained that IDS 9.40+ adds logical logs automatically in the ROOTDBS when logs are unarchived, and advised moving logs to another dbspace and archiving continuously. David suggested oncheck -pe.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
I run IBM Informix Dynamic Server Version 11.10.UB4TL on Solaris SPARC
10 supporting the public beta program.
I recognized that the rootdbs got filled up a few days ago.
I removed a logical log to free 256M of space, but now the rootdbs is
filled again.
I get these messages in the online.log file:
21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
What's filling up the rootdbs. How can I stop it?
The server seems to continue to run without any problems.
Regards,
Frank
↪ replying to Frank Langelage
Fernando Nunes — — source: Usenet: comp.databases.informix
Frank Langelage wrote:
> I run IBM Informix Dynamic Server Version 11.10.UB4TL on Solaris SPARC
> 10 supporting the public beta program.
>
> I recognized that the rootdbs got filled up a few days ago.
> I removed a logical log to free 256M of space, but now the rootdbs is
> filled again.
> I get these messages in the online.log file:
> 21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
>
> What's filling up the rootdbs. How can I stop it?
> The server seems to continue to run without any problems.
>
>
> Regards,
> Frank
Did you configure any tasks on the internal "cron"?
The errors seem to be related to scheduled tasks on sysadmin database...
I've noticed you posted the same question on Cheetah support forum, so probably someone will answer you.
Regards
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
↪ replying to Frank Langelage
Art S. Kagel — — source: Usenet: comp.databases.informix
Frank Langelage wrote:
> I run IBM Informix Dynamic Server Version 11.10.UB4TL on Solaris SPARC
> 10 supporting the public beta program.
>
> I recognized that the rootdbs got filled up a few days ago.
> I removed a logical log to free 256M of space, but now the rootdbs is
> filled again.
> I get these messages in the online.log file:
> 21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
>
> What's filling up the rootdbs. How can I stop it?
> The server seems to continue to run without any problems.
IDS 9.40 and later will allocate new logical logs if the logical logs on
disk all fill up and are not archived/cleared out. By default new logical
logs are added from the dbspace that contained the last logical log added.
By default, unless you created new logs yourself after the initial startup,
is the ROOTDBS dbspace. Exactly what you are seeing.
Fix: Create new/more logical logs in a different dbspace, drop the original
few logs that the startup created in the ROOTDBS and set things up to
continuously archive the logical logs using ontape -c or the onbar
equivalent or to archive each log as it fills using the ALARMPROGRAM
parameter (my utils4_ak package contains a script and an executable
ALARMPROGRAM that will do this for you).
Art S. Kagel
On 26 Feb, 20:52, Frank Langelage <f...@lafr.de> wrote:
> I run IBM Informix Dynamic Server Version 11.10.UB4TL on Solaris SPARC
> 10 supporting the public beta program.
>
> I recognized that the rootdbs got filled up a few days ago.
> I removed a logical log to free 256M of space, but now the rootdbs is
> filled again.
> I get these messages in the online.log file:
> 21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -271 Could not insert new row into the table.
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
> 21:18:49 SCHAPI: Error -131 ISAM error: no free disk space
> 21:18:49 SCHAPI: Type: SENSOR, Name: mon_vps, Location: NULL.
>
> What's filling up the rootdbs. How can I stop it?
> The server seems to continue to run without any problems.
>
Run oncheck -pe and that will show you what is in the roodbs.
> Regards,
> Frank
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.