Kbase P120377: Windows 2000 Automated AI file managment fails when -aiarcdir is set to an UNC path
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/18/2008 |
|
Status: Verified
FACT(s) (Environment):
OpenEdge 10.1A
OpenEdge 10.1B
Windows 2000
OpenEdge 10.1C
SYMPTOM(s):
Automated AI file managment fails when -aiarcdir is set to an UNC path
-aiarcdir is set to an UNC path
user starting the database has access and full control to the remote directory
Cannot determine the amount of free space for device \\<server>\<shared Directory> (13197)
The after-image management daemon cannot find a destination in its current list with enough space to continue archiving extents. (13198)
CAUSE:
Bug# OE00134973
CAUSE:
UNC paths are not recognised by the new aiarchive functionality.
FIX:
New function calls have been added in OpenEdge 10.1B01 in order to be able to see UNC paths (utGetDiskSpace API calls utGetDriveFromPath)
As an alternative or workaround for Windows 2000:
1.) Set the runtime -aiarcdir locally.
Include the archiving of these ai files as part of the backup routine, where after the probkup is taken, the probkup is part of today's set and the ai archived files from today are zipped and transfered to yesterday's probkup location on the shared network drive.
It is suggested that ai files are not archived during runtime to a remote directory. There have been several reported incidents with manual ai extent archivings accross the network, where for example, the network has gone down or packets are lost in the the transfer, resulting in failure to roll forward these archives when needed.
2.) Set the -aiarcdir to a mapped network drive