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
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
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
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
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
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
Hello,
I am sorry but for that you have to open an OSS message.
Thank you very much,
Stefan
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