- #Mac you do not have enough access privileges for this installation install#
- #Mac you do not have enough access privileges for this installation software#
If so, then you will need to do a recursive chmod to enable access to the oraInventory: The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc or /etc/oraInst.loc file or inst_loc in the registry has permissions that restrict the user running the OUI from writing to oraInventory.įix - Ensure that you are the correct user to perform the installation. The user attempting to perform the installation cannot access the inventory location.
#Mac you do not have enough access privileges for this installation software#
If you have an up-to-date backup of this area, try restoring the oraInventory otherwise, you will need to reinstall all 8i, 9i, or 10g software versions that are on the host to repopulate the oraInventory. The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc or /etc/oraInst.loc file or inst_loc in the registry is oraInventory, but has no subdirectories.įix - If the location has no subdirectories, it has been cleaned out accidentally. Modify inventory_loc in oraInst.loc to point to the valid oraInventory directory or the inst_loc in the registry. The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc or /etc/oraInst.loc file or inst_loc in the registry is not the directory oraInventory.įix - The directory pointed to needs to end with oraInventory (/usr/opt/oracle/oraInventory). The oraInventory being pointed to through the inventory_loc reference in the /var/opt/oracle/oraInst.loc or /etc/oraInst.loc file or inst_loc in the registry is a non-existent location or has extra characters in the directory path listed.įix - Search for the oraInventory directory on the system and change the location in oraInst.loc or inst_loc to point to the correct location, or if the path listed is incorrect, correct it. There are several reasons this message can appear: If you are unable to successfully run xclock, refer to your PC-X Server or OS vendor for further assistance. To test that the DISPLAY environment variable is set correctly, run an X11 based program that comes with the native operating system, such as 'xclock'. To enable client users to access the X Server, open an xterm, dtterm, or xconsole as the user that started the session and type the following command:
Make sure that client users are authorized to connect to the X Server. Use one of the following commands for your Unix shell as an example to set the variable: If the DISPLAY environment variable is not set, use the following command to see what shell is being used: Use the following command to view the current DISPLAY environment variable setting: The DISPLAY environment variable is not set properly, or client users are not authorized to connect to the X Server.Ĭheck if the DISPLAY environment variable is set.
#Mac you do not have enough access privileges for this installation install#
Unable to start an interactive install session because of the following error: The DISPLAY environment variable should be set to :, where the is usually ''0.0". Make sure you have write permission on the /locks directory.Įither change the ownership of / to the current user, or include the current user in the group that owns the directory, provided that the group has write permission to the directory. Possibly, the current user is neither the owner nor the member of the group that owns the /locks directory. The current OUI (process) is not able to remove the "writer.lock" file, because the permission for the current user does not allow this. The global inventory (oraInventory) was locked by another process and the writer.lock file still exists even after the process exited. The file "writer.lock" is created under the /locks directory. Make sure you have enough permission to the ''locks'' directory to create/remove the writer.lock file.įor any write operations in the inventory, OUI acquires a lock.
You do not have sufficient permissions to access the inventory, unable to remove an existing inactive writer lock file in the inventory.
0 kommentar(er)
