Shared Client Side 'TMP' Directory Causes EDQ Director to Crash on Unix (Client) Systems
(Doc ID 2217187.1)
Last updated on JUNE 09, 2023
Applies to:Oracle Enterprise Data Quality - Version 184.108.40.206.0 and later
Oracle Enterprise Data Quality on Marketplace - Version 220.127.116.11.3 and later
Information in this document applies to any platform.
Enterprise Data Quality (EDQ) UI clients need to store local data on the client system. This is used for both persistent caches (processor library) and temporary jar storage (blueprints & database connectors).
A unique location within the Java temporary directory is used. On a Windows client platform, the Java temporary directory is located within the per-user AppData area. On a Unix client platform the Java temporary directory is /tmp (or /var/tmp), which is shared among all users.
On Unix the cache and blueprints directories are located within a directory which includes the current user name, so will not be shared among different users. Unfortunately, the database connector storage does not use this directory and instead uses a common directory in /tmp. This shared directory is created by the first user to run a client; if a different user on the
system runs a client they will not be able to write to the directory. Errors like:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!