Do you have any question about this error?
Message type: E = Error
Message class: HH - (Long) text for check tool 'infcfgcheck'
Message number: 065
Message text: Specified directory cannot be read (due to missing authorizations etc.)
Firstly: This message is not an error! The individual check could not
execute automatically as usual.
No check was made on whether various links point to the same raw device
within the INFORMIXDIR directory.
Check yourself: If you find any such links<(>,<)> then
note the following:
In this situation you can easily overwrite existing chunks
and thereby destroy the database.
Delete redundant links if they are not already being used for existing
chunks (check using 'onstat -d'). If both links are already being used
contact the Hotline to have the situation checked.
Error message extract from SAP system. Copyright SAP SE.
HH065
- Specified directory cannot be read (due to missing authorizations etc.) ?The SAP error message HH065, which states "Specified directory cannot be read (due to missing authorizations etc.)," typically occurs when the SAP system is unable to access a specified directory on the file system. This can be due to various reasons, primarily related to authorization issues or incorrect directory paths.
Causes:
- Missing Authorizations: The user or the SAP application server may not have the necessary permissions to read the specified directory.
- Incorrect Directory Path: The path specified in the configuration may be incorrect or may not exist.
- File System Issues: The directory may be on a file system that is not mounted or is inaccessible due to network issues.
- Operating System Permissions: The underlying operating system may have restrictions that prevent access to the directory.
- SAP Profile Parameters: The parameters related to file handling in the SAP profile may not be set correctly.
Solutions:
Check Authorizations:
- Ensure that the user or the SAP application server has the necessary authorizations to access the directory. This can be done by checking the user roles and authorizations in the SAP system.
- Use transaction code
SU53
to analyze authorization failures after attempting to access the directory.Verify Directory Path:
- Double-check the directory path specified in the configuration. Ensure that it is correct and that the directory exists on the file system.
- You can use transaction
AL11
to check the directories configured in the SAP system.Check File System Access:
- Ensure that the file system where the directory resides is mounted and accessible from the SAP application server.
- If the directory is on a network share, verify that the network connection is stable.
Operating System Permissions:
- Check the operating system-level permissions for the directory. Ensure that the user under which the SAP application server is running has read access to the directory.
Review SAP Profile Parameters:
- Check the SAP profile parameters related to file handling (e.g.,
DIR_EXEC
,DIR_DATA
, etc.) to ensure they are set correctly.- You can view and modify these parameters using transaction
RZ10
.Consult SAP Notes:
- Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
Related Information:
Transaction Codes:
SU53
for authorization checks.AL11
for checking directories.RZ10
for profile parameters.SAP Documentation: Refer to the official SAP documentation for more details on file handling and authorization management.
System Logs: Check the system logs (transaction SM21
) for any additional error messages or warnings that may provide more context about the issue.
By following these steps, you should be able to identify and resolve the cause of the HH065 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
HH064
The specified path points to the same 'raw device' as another path
What causes this issue? The two specified paths (relative from $INFORMIXDIR) point to the same raw device. In this situation you can easily overwrite...
HH063
Freespace of specified dbspace has reached a critical size
o Dbspace is not called 'rootdbs', the maximum next extent size can fit into the freespace, and freespace is 5% or more of the total dbspac...
HH066
Edit the Informix ONCONFIG file
What causes this issue? The ONCONFIG parameter 'PHYSFILE' is configured very low. This parameter defines the size of the physical log file ...
HH067
The no. of Dbspace chunks is (highly) critical (due to ontape/onarchive)
What causes this issue? The specified dbspace consists of many chunks: Background: The Informix backup tools 'ontape' and 'onarchive...
Click on this link to search all SAP messages.