Skip to Content

WAS 640 - Doubt

Hi All ..

I´m installing a MaxDB 7.5 with WAS 640 and I´m having trouble to install database instance. I have another SAPDB installation on same host that has version 7.3.

As I read on another message put here, it seems that or I deleted this old version or try to upgrade to new version 7.5. Am I right?

On file XCMDOUT.LOG, I have this info:

Subprocess starts at 20040621111900

Execute Command : /sapdb/programs/bin/dbmcli -n sapdes0 db_enum

Start subprocess as user with uid: root

Subprocess stops at 20040621111900

Error! Connection failed to node sapdes0 for database (no dbname): connection refused: x_server not running

-

-


Subprocess starts at 20040621111924

Execute Command : /sapdb/programs/bin/dbmcli -s dbm_version

Start subprocess as user with uid: root

Subprocess stops at 20040621111924

OK

VERSION = 7.3.0

BUILD = DBMServer 7.3.0 Build 020-000-084-698

OS = UNIX

INSTROOT = /sapdb/XID/db

LOGON = True

CODE = ASCII

SWAP = normal

UNICODE = YES

INSTANCE = (unknown)

SYSNAME = AIX

-

-


Thanks !

Daniela Godoi

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

7 Answers

  • Posted on Jun 21, 2004 at 03:38 PM

    Hello,

    the message in XCMDOUT.log means that the x_server is not running. The x_server is needed to connect to that database host via dbmcli -n ... db_enum

    Please check first wether the x_server is running or not.

    You can do that with the call:

    /sapdb/programs/bin/x_server

    Please try then again.

    In general it is possible to have several versions of SAP DB on one host.

    Thanks, Stefan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 22, 2004 at 09:48 AM

    Hello,

    sapinst checks wther there is already software installed or not.

    I think the following has happened now:

    - You have unmounted file system which belongs

    to the existent SAP DB installation ( I guess /sapdb ).

    - The registry on UNIX is in /usr/spool/sql

    sapinst has found entries in /usr/spool/sql which leads it to /sapdb... But this directory is not there.

    That's why the error occurs because sapinst found the registry but not the software.

    There are two possibilities now.

    1. Delete the existent software:

    Then you have to delete rm -r /usr/spool/sql

    and /sapdb

    But then also all databases will be lost !!

    2. Keep the existent software:

    Then you have to remount the filesystem again.

    And start the x_server that the command dbmcli -n hostname db_enum will work.

    Best regards, Stefan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 22, 2004 at 12:53 PM

    Hello,

    when you want to keep the old installation you can mount the file system. Then the installation is consistent again and sapinst should not run into problems.

    Best regards, Stefan

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Stefan

      I did your second step (remounted the old file system with our SAPDB 7.3 installation and start x_server)but it seems that didn´t work.

      On same step of installation, I got a lot of warning and error messages:

      ...

      guiengine: login in process..

      File sapdb.inf does exist. Will use the commands in file sapdb.inf.

      ...

      }

      : The database software on the host has the version: 73, the software on cd: 75.The database client software

      ersion is out of range. Upgrade the database client software and retry this installation!

      WARNING 2004-06-22 17:02:41

      The step check_base_software with step key SAPSYSTEM_DB|ind|ind|ind|ind|ind|0|SAPSYSTEM|ind|ind|ind|ind|ind|0|

      SAPComponent|ind|ind|ind|ind|ind|0|DatabaseServer|ind|ind|ada|ind|ind|0|SAPDB_DB_SOFTWARE|ind|ind|ind|ind|ind|

      0|check_base_software was executed with status ERROR.

      WARNING 2004-06-22 17:02:49

      n error occurred during the installation.

      On XCMDOUT.LOG file, I got this :

      Subprocess starts at 20040622170213

      Execute Command : /sapdb/programs/bin/dbmcli -n sapdes0 db_enum

      Start subprocess as user with uid: root

      Subprocess stops at 20040622170214

      OK

      XID /sapdb/XID/db 7.3.0.20 fast offline

      XID /sapdb/XID/db 7.3.0.20 slow offline

      XID /sapdb/XID/db 7.3.0.20 quick offline

      -

      -


      Subprocess starts at 20040622170236

      Execute Command : /sapdb/programs/bin/dbmcli -s dbm_version

      Start subprocess as user with uid: root

      Subprocess stops at 20040622170237

      OK

      VERSION = 7.3.0

      BUILD = DBMServer 7.3.0 Build 020-000-084-698

      OS = UNIX

      INSTROOT = /sapdb/XID/db

      LOGON = True

      CODE = ASCII

      SWAP = normal

      UNICODE = YES

      INSTANCE = (unknown)

      SYSNAME = AIX

      What I´m thinking that I really have to delete my old SAPDB installation (or just desmount /sapdb and /sapdb/SID file system and rename /usr/spool/sql directory)to allow this step to continue.

      Do you have any other hint to help me about this?

      Best regards,

      Daniela

  • Posted on Jun 23, 2004 at 11:10 AM

    Hello,

    there is also a reason for this error.

    You are on Unix and you have a 7.3 SAP DB installation.

    For WebAS MaxDB 7.5 has to be installed.

    With 7.5 on UNIX a new security strategy takes place which have also some influences on the existing software.

    Due to this the existing software will not be upgraded by sapinst. Instead this message comes up.

    In fact the Independend Part of the existing software must be upgraded by hand. After that you can restart sapinst.

    Some words about the new security strategy.

    The owner of the software will be a special user which cannot login to the system. The default name of this user is "sdb". The group for the software will be "sdba" for default.

    The existing 7.3 software under /sapdb/<SID>/db won't be touched. Just the Independend Part will be changed.

    To upgrade your client software you can start SDBINST as user root.

    SDBINST should be on the database software CD.

    Befor you start it shut down the existent databases and stop the x_server ( x_server stop ).

    After SDBINST has started choose "Runtime for SAP AS"

    This will upgrade the client software.

    SDBINST will then suggest the Software Owner "sdb" and the Group "sdba". When sdb does not exists it will be created. But this user will be locked. To use the 7.3 software after the upgrade you have to add your current SAP DB users to the group sdba.

    After that you can restart sapinst.

    When problems occur during the upgrade you can check the directory /sapdb/data/wrk for the logfile of SDBINST. Its name includes the data and the time when SDBINST was started.

    Best regards, Stefan

    Add a comment
    10|10000 characters needed characters exceeded

    • HI Stefan

      Many and many thanks !! I did what you wrote and the installation continues without problems ! I had only one error on DB13 and DB50 for my old SAPDB instance but I will open an OSS about this issue.

      By the way, I had one more question: which sap code page do I have to use? The installation prompts 4102 value.. Is this correct? Other installations that I did (non-unicode) I used 1100.

      Many thanks !

      Daniela

  • Posted on Jun 24, 2004 at 07:56 AM

    Hello,

    for Unicode you have to use 4102 or 4103. This is described in OSS note 552464.

    WebAS 640 is installed as Unicode.

    Because of the problems in DB13 and DB50 you can try note 668849

    Best regards, Stefan

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      Thanks a lot for those notes, but for DB13 and DB50 I still have the same problem. On note 668849, I had to give executation auth to 2 files but I only have 1.

      See what I have on directory:

      sapdes0:xidadm 13> ll

      total 20736

      -r-xr-xr-x 1 sdb sdba 5861581 Nov 21 2003 lserver

      -rwxrwxr-x 1 xidadm sapsys 333472 Jan 08 2002 maketi

      -rwxrwxr-x 1 xidadm sapsys 797183 Jan 08 2002 niserver

      -r-xr-xr-x 1 sdb sdba 395170 Nov 21 2003 regupd

      -rwxrwxr-x 1 xidadm sapsys 1322603 Jan 08 2002 userx

      -rwxrwxr-x 1 xidadm sapsys 570902 Jan 08 2002 vserver

      -rwxrwxr-x 1 xidadm sapsys 1289702 Jan 08 2002 vttest

      sapdes0:xidadm 14> pwd

      /sapdb/programs/pgm

      sapdes0:xidadm 15>

      I got this error on DB50

      Name and Server : XID - sapdes0

      DBMRFC Function : DBM_EXECUTE

      Command : dbm_version

      Error : System Error

      Error message :

      I also found note 637864 but I already have Basis SP 27 on my system

      Thanks a lot !

      Daniela

  • Posted on Jun 29, 2004 at 01:14 PM

    Hello,

    I am sorry but for that you have to open an OSS message.

    Thank you very much,

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 06, 2004 at 08:14 AM

    Hello,

    the error you get means that the dbmsrv Executable was not found on that host.

    The dbmcli ( DB client ) connects to the dbmsrv ( DBM Server ) to execute a database command.

    dbmcli comes wtith the MaxDB Client software.

    dbmsrv comes with the Database kernel software.

    From the message I assume that your kernel software is deleted but not correctly unregistered.

    When you run this : dbmcli inst_enum

    You should see something like:

    C:\temp>dbmcli inst_enum

    OK

    7.4.03.35 c:\sapdb\lca\db

    7.4.02.27 c:\sapdb\lc74\db

    To remove all MaxDB software from your host you can run this command:

    C:\sapdb\programs\bin\sdbuninst -all

    You can also try just to remove the Database kernel software:

    C:\sapdb\programs\bin\sdbuninst -package "Database Kernel"

    Then sdbuninst asks which Kernel installation should be removed.

    I hope that helps.

    Best regards, Stefan

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.