Kbase P133379: Getting error "(13197) Cannot determine the amount of free space on device " after activating AI Fil
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/24/2009 |
|
Status: Verified
SYMPTOM(s):
Getting error "(13197) Cannot determine the amount of free space on device <name>" after activating AI File Management.
Cannot determine the amount of free space for device <name>. (13197).
A path consisting of only one directory level is specified for the archive directory (-aiarcdir) parameter when starting the database broker with the proserve command.
Database activity stops or hangs after the error is written to the database log file.
The after-image management daemon cannot find a destination in its current list with enough space to continue archiving extents. (13198).
Can't switch to after-image extent it is full. (3775)
Backup ai extent and mark it as empty. (3776)
There are no available EMPTY AI extents. Database activity is stalled until an AI extent becomes available. (12288)
The database does not hang, or get the above errors, if a path of at least two directory levels is specified for -aiarcdir
e.g.
proserve <dbname> -S <port> -aiarcdir /tmp/foo ==> Does not hang or generate the above errors
proserve <dbanme> -S <port> -aiarcdir /tmp ==> Hangs or generates the above errors
FACT(s) (Environment):
The rfutil <dbname> -C aiarchiver enable command is used to activate AI File Management.
The proserve <dbname> -S <port> -aiarcdir /tmp command is used to specify the archive directory.
The database has only fixed after image extents defined.
Sun Solaris SPARC
OpenEdge 10.1B03 32-bit Service Pack
CAUSE:
Bug# OE00171907
FIX:
None at this time.
A work around for this issue is to specify an -aiarcdir path of at least two directory levels.
e.g. proserve <dbname> -S <port> -aiarcdir /tmp/foo