Kbase P6948: Temporary Directory (-T) startup parameter on a mapped network drive
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/7/2006 |
|
Status: Verified
FACT(s) (Environment):
Windows
UNIX
SYMPTOM(s):
Temporary Directory (-T) startup parameter on a mapped network drive
Unable to open or create filename, error 3
temporary file name conflicts
CAUSE:
On Windows, if two or more users share the same working directory and there is a conflict of temporary files. This situation occurs typically in "peer to peer" end user environments, where the -T parameter is specified in the -pf for all users as a remote directory, or not at all:
-db sports2000 -H hot -S test -N TCP -T e:\netapps\Progress\work
where "e:\netapps\Progress\work" is a mapped network drive.
FIX:
Use Temporary Directory (-T) to specify a directory for temporary files. If this parameter is not specified, Progress will put these temporary files into the current working directory by default.
On UNIX and Windows, the temporary filenames begin with a prefix of:
lbi, Local before-image (subtransaction undo)
dbi, Store temporary tables
pge, Edit buffer contents
srt, Temporary sort space; session compile storage
trp, Store Data Dictionary changes until they are saved and end with the process identifier (PID) of the user's Progress session.
On UNIX, temporary filenames end with the process ID of the user's Progress session, thus avoiding filename conflicts. Progress stores these files as "unlinked" with no visible name in the UNIX file system (unless you use Save Temp Files (-t) client startup parameter).
On WINDOWS, temporary filenames end with a random number not related to the PID of the user's Progress session. Use Temporary Directory (-T) to specify a local directory for temporary files.
(eg: prowin32 -db dbname -T C:\%Temp% -pf myclient.pf) Setting this locally, will minimise network traffic, improve performance and resolve temporary_file_name conflicts.