Kbase P120376: Automated AI file management fails when -aiarcdir is set to an UNC path
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/6/2009 |
|
Status: Verified
SYMPTOM(s):
Automated AI file management fails when -aiarcdir is set to an UNC path
-aiarcdir is set to an UNC path in other server arguments
user starting AdminService has access to remote directory (domain user)
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)
A mapped drive with required privileges result in the database not starting with error 13187
The directory J:\aiarch specified with -aiarcdir does not exist. (13187)
-aiarchdir set to UNC path in the cmd line fails with errors 13197 13198
user starting database from the cmd line has access and full control to the remote directory
FACT(s) (Environment):
OpenEdge 10.1A
Windows 2003
Windows XP
OpenEdge 10.1B
OpenEdge 10.1C
CAUSE:
Bug# 20061113-004
CAUSE:
Bug# OE00166346
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:
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 transferred 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.