Solution Manager 7.1 SR1 with Sybase ASE on Linux Installation Error!

[Former Member]

Hi,

I am trying to install SAP Solution Manager SR1 with latest Sybase ASE RDBMS on CentOS 6.3 (Sandbox environment) and getting following error message on Install Sybase ASE Server:

       An error occurred while processing option SAP Solution Manager 7.1 SR1 > SAP Systems > Sybase ASE > Central System > Central System( Last error reported by the step: System call failed. Error 13 (Permission denied) in execution of system call 'openU' with parameter (/sybase/SMD/.cshrc.1, O_WRONLY | O_TRUNC | O_CREAT, S_IRWXU | S_IRWXG | S_IRWXO), line (409) in file (syuxcfile.cpp), stack trace: iaxxejsctl.cpp: 146: EJS_ControllerImpl::executeScript() iaxxejsbas.hpp: 461: EJS_Base::dispatchFunctionCall() iaxxejsexp.cpp: 178: EJS_Installer::invokeModuleCall() iaxxbfile.cpp: 210: CIaOsFile::saveVersion_impl() syxxcnode.cpp: 520: CSyNodeImpl::saveVersion() syuxcfile.cpp: 310: CSyFileImpl::copy(const CSyPath & /sybase/SMD/.cshrc.1, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const .). You can now: 
 Choose Retry to repeat the current step. 
 Choose Log Files to get more information about the error. 
 Stop the option and continue with it later.       

I have verified that user <SID>adm (smdadm) does have permissions on directory /sybase/SMD.

I am also aware that CentOS is not officially supported by SAP but since CentOS is derived from RHEL itself and is available free I thought I would give it a try with this instead of the 30-day RHEL Eval. I am using this document from Red Hat and the actual SAP installation guide as reference for installation.

I have also gone through SAP Notes 1606654 & 1716201 and done the suggested changes and still the same error.

Can anyone please give any pointers on fixing this problem? Appreciate your response.

Thanks!

[Former Member · Accepted solution]

Hi Shrinivas,

Could you please provide a snippet of the debug log from either sapinst.log or sapinst_dev.log? It would be great if you could include some of the lines above/below the error.

Also, the error seems to happen during a call to copy. Have you checked the disks for sufficient space? CentOS should support 'df -h | column -t' and give a readable, clean output.

Ninad

[Former Member · Accepted solution]

Hi Ninad,

I have copied & pasted last 1000+ lines for sapinst_dev.log here and for sapinst.log here. Below is output for `df -h | column -t`.

Filesystem                         Size  Used  Avail  Use%   Mounted       on
/dev/mapper/vg_centos4sap-lv_root
50G                                44G   3.7G  93%    /
tmpfs                              1.9G  260K  1.9G   1%     /dev/shm
/dev/sda1                          485M  90M   371M   20%    /boot
/dev/mapper/vg_centos4sap-lv_home
9.5G                               152M  8.9G  2%     /home
/dev/sdb                           252G  1.4G  238G   1%     /usr/sap/SMD
/dev/sdb                           252G  1.4G  238G   1%     /sapmnt/SMD
/dev/sdb                           252G  1.4G  238G   1%     /sybase/SMD
none                               4.0T  0     4.0T   0%     /media/psf

Thanks,

Shrinivas

[Former Member · Accepted solution]

Hi Shrinivas,

Although your root partition seems to be close to filling up, I do not think that is the root cause for this error. According to the sapinst*log files, this is the first step where it is accessing the /sybase/SMD. Try the following 2 options, one of them should give us more answers:

1. Do an lsof on /sybase/SMD/.cshrc and see if any other process has opened the file. The open call seems to ask for an exclusive write only mode, so if another process has opened the file, that will conflict.
2. Log in as smdadm, try to create a new file in /sybase/SMD. If this throws an error, check the write permissions all through the hierarchy (for /sybase as well as /sybase/SMD). One of them would not give smdadm write permissions, which means it cannot write inside that tree.

Depending on the result, please choose the right course of action. If any of them works, please post your solution to this thread.

Thanks,

Ninad

[Former Member · Accepted solution]

Thanks Ninad for the tip. My issue has now been resolved.

The problem was in fact with missing permissions for <sid>adm on /sybase/<SID> folder. The permissions were set as 755 for syb<sid>:sapsys and hence <sid>adm couldn't write files. I changed the permissions to give write privileges to sapsys group (775) and issue got resolved.

Thanks again!