Heterogeneous Installation: shared /usr/sap/<SID> and /sapmnt/<SID>

[Former Member]

Hey,

we have heterogeneous system installation:

ASCS and ERS: Linux x86

DVEBMGS and 😧 Linux x86

Database: Solaris SPARC 64 Bit

We have one shared filesystem /usr/sap/<SID> and /sapmnt/<SID> on all servers.

After installation we have changed the user-Environment SAPEXE from /usr/sap/<SID>/SYS/exe/run to /usr/sap/<SID>/SYS/exe/"$_UC_NUC"/"$_PLATFORM"

Now we are facing the following problem:

In the directory /usr/sap/<SID>/exe there is a link from run to /sapmnt/<SID>/exe/nuc/linuxx86_64

Our backup tools (backint) cannot be started on the database servers because the binaries of /usr/sap/<SID>/exe/run are started.

We have already checked sap note 1067221 - Composite SAP Note for heterogeneous installation

Is it possible to have a heterogeneous system installation with one shared filesystem for /usr/sap/<SID> and /sapmnt/<SID> on all servers?

Best regards

Alexander

[former_member188883 · Accepted solution]

Hi Alex,

It may not work as backup tools will look into default kernel directory as /usr/sap/<SID>/exe/run

Best option is not to share the /usr/sap/SID to all app server. Keep them local and try again.

Hope this helps.

Regards,

Deepak Kori

[Former Member · Accepted solution]

As mentioned in SAP note 531069 "All Unix flavours supported by SAP are 100% compatible with each othe" and "Integration of important functionality like mounting of shared file systems across all servers of the system is required"

Keeping the filesysten local is not an option.

[Former Member · Accepted solution]

Hi Alexander,

I may be confused here as to the problem, but although the Unix systems are 100% compatible, the kernel programs most certainly are not.  You don't want to be sharing the same kernel programs between the Solaris and Linux servers because that won't work. You are going to need to install the appropriate kernel programs on the DB server for Solaris Sparc 64 bit for backint to work.

Regards,

Graham

[Former Member · Accepted solution]

Dear Graham,

since at least SAP release 7.3 there is a new directory structure for /sapmnt

/sapmnt/<SID>/exe/(n)uc

In our case we have two kernels in /sapmnt (non-unicode)

/sapmnt/<SID>/exe/nuc/linuxx86_64

/sapmnt/<SID>/exe/nuc/sun_64

Everything is working fine (starting sap, sapcpe, etc).

The only problem we have is with the directory softlink /usr/sap/<SID>/SYS/exe/run. This softlink links to the /sapmnt/<SID>/exe/nuc/linuxx86_64 directory. If a db13-job is started p.e. brconnect is started in sun_64. Only the backint tool wants to be started through /usr/sap/<SID>/SYS/exe/run.

Best regards

Alexander

[Former Member · Accepted solution]

Usually TDP for SAP creates soft link to backint utility in /usr/sap/<SID>/exe/run directory. Check it's real location.

[Former Member]

Thank you guys for your support!

We have solved our problem. With the new directory structure you should use only one filesystem which should be shared on all unix servers (linux, sun, HPUX etc).

Therefore you must change your environment. There are two steps which have to be done:

1. Edit .dbenv.sh and .dbenv.csh

comment line: setenv SAPEXE /usr/sap/<SID>/SYS/exe/run

uncomment line: #setenv SAPEXE /usr/sap/<SID>/SYS/exe/"$_UC_NUC"/"$_PLATFORM"

2. If you have to use backint etc,

edit line

set _DEF_EXE2=/usr/sap/"$SAPSYSTEMNAME"/SYS/exe/run

into

set _DEF_EXE2=/usr/sap/"$SAPSYSTEMNAME"/SYS/exe/"$_UC_NUC"/"$_PLATFORM"

I hope that will help you.

Best regards

Alexander

[srinivasan_vinayagam]

Dear Alexander,

The default executables (Kernel Directory) in Unix /sapmnt/SID, /usr/sap/SID is softlink to /sapmnt/SID

Thanks & Regards,

V Srinivasan