startdb/stopdb missing?

[Former Member]

Hi all,

I'm a bit new to setting up distributed instances of NW so bear with me.

I am attempting to setup a distributed NW7.3EHP1 Java environment on Linux, RHEL 6.3.  Setting up a standard set of instances is no problem, everything seems to work just fine.  However, when I try to setup SCS/ERS on hostA (sapapp1) and the DB instance on hostB (sapdb) things don't go as smoothly.

Prior to installing I did an NFS export of /sapmnt from sapapp1 and mounted it at /sapmnt on sapdb, then when the DB instance installer asked for a profile directory I pointed to /sapmnt/<SID>/profile.  The install seems to go smoothly and the DB *is* up and running at the end of the install, it just doesn't seem to install any of the tools I would have expected - there is not startdb/stopdb anywhere on the filesystem of the DB host and startsap/stopsap jdb doesn't work either.

Am I missing something very simple?

Jason

[Former Member]

Hallo,

what about /usr/sap/<SID>/DVEBMGS<Instance-number>/exe?

The setup of the kernel directories has slightly changed in 7.3.

Also refer to http://help.sap.com/saphelp_nw73/helpdata/en/27/44f17a26a74a8abfd202c4f5dc9a0f/content.htm.

Regards,

Thomas,

[former_member189725]

You are not missing anything . In the database host , only the database specific resources required for running the database are installed. The SAP application specific resources are not installed by sapinst . on the database host. The /sapmnt/<SID>/exe directory has the startdb and stopdb scripts. The /sapmnt/<SID>/exe can either be created locally manually and the kernel files extracted into it or mount the /sapmnt/<SID>/exe directory from the SAP application host .

Login as database administrator user like ora<sid> or db2<sid> and check the environment of the user.

Make sure the database specific environment variables are set for the user.

Then either edit the PATH variable of the user and append /sapmnt/<SID>/exe to it.

Or else directly start the database using /sapmnt/<SID>/exe/startdb.

Regards

Ratnajit

[Former Member]

Hi Ratnajit,

There weren't any startdb/stop DB scripts in the /sapmnt/<SID>/exe directory either (it was shared on both hosts).  I still think I might be doing something wrong.  Are there any easy, step-by-step guides to setting up a distributed Java AS system?  I've read the installation guides and they give some high level direction, but not very crystal clear step-by-step instructions, at least not clear enough for a beginner like myself.

Here is basically what I did, tell me if I missed a step or otherwise did something incorrect:

1. Installed ERS/SCS on sapapp1, system name = RHT

2. Setup an NFS export on sapapp1 for /sapmnt allowing all hosts read write access

3. Mounted sapapp1:/sapmnt on sapdb at /sapmnt

4. Ran the installer on sapdb, pointed to /sapmnt/RHT/profile as the profile directory

After the install the DB was running properly, but again, no startdb/stopdb scripts on either host anywhere in the entire filesystem.  Did I miss something?

I'm planning on doing a re-install, can I put SCS/ERS on the same box as my DB?  If so, do I still need to install ERS/SCS before the DB?

Jason

[former_member189725]

What I suggest is  install SCS on sapapp1 host , then install the database on sapdb host, then install the primary application server on sapapp1 and then the ERS on sapdb host.

Complete the entire installation and then check if everything is in place .

Regards

Ratnajit

[Former Member]

Hi Jason,

ERS instance(Enqueue Replication Server) is only required in High Availability scenario. Installation of ERS

Below is the step by step procedure to Install NW 7.3 EHP1 on distributed environment.

On the host with the global file system (SAP global host), you do the following:
1.You run SAPinst to install the central services instance for Java (SCS) and – optionally – the enqueue replication server instance (ERS) for the SCS.
2.You export global directories in <sapmnt>/<SAPSID> to the database and primary application server instance host.

On the database instance host, you do the following:
1.You mount the global directories in <sapmnt>/<SAPSID> that you exported from the SAP global host
2. You run SAPinst to install the database instance.

On the primary application server instance host, you do the following:
1. You mount the global directories in <sapmnt>/<SAPSID> that you exported from the SAP global host.
2. You run SAPinst  to install the primary application server instance.
3. If you want to use the shared transport directory trans from another system, you also mount [page 62] this directory.

You continue with Post-Installation.

Regards,

Renu