MaxDB upgrade - SDBSETUP 7.6.03.09 fails

[matthew_partington]

Hi,

I'm trying to upgrade MaxDB 7.6.03.09 to 7.6.06.10 (for use with a SAP Content Server Cache) using the installation manager and note 1092397

The upgrade fails with the following info;

Error: Checking package Base failed!: Test extraction failed!:

Following programs are running:

SDBSETUP.EXE [pid = 3832]

Anybody got any advice?

Thanks, Matt

[markus_doehr2 · Accepted solution]

> Error: Checking package Base failed!: Test extraction failed!:

> Following programs are running:

> SDBSETUP.EXE [pid = 3832]

don't use SDBSETUP to upgrade but SDBUPD.

Markus

[matthew_partington · Accepted solution]

Hi Markus,

Note 1092397 says;

The tool SDBSETUP is available as of Version 7.6. It is a part of the MaxDB delivery and, in the same way as SDBUPD, you can use it to import a new database version (instance upgrade).

I think I'm using the wrong SDBSETUP, i.e. version 7.6.03.09 not the new 7.6.06.10.

I will try again and report back.

[matthew_partington · Accepted solution]

Yes I foolishly started SDBSETUP from the desktop and not the new version from the folder created from the SAR file. So even though I pointed it at the folder containing the new version the old version was obviously in use.

The install finished without problems but I did have to add the TCPIP port to the services file.

[Former Member · Accepted solution]

Hello All,

I am trying to install MaxDB with the following distribution " maxdb-all-sun-64bit-x86_64-7_7_07_16.tar" on Solaris 10. I get a failed error message from running SDBSETUP.

Here is error message.

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Here is my environment:

INSTALLER_INFO: Version = 7.7.07 Build 016-123-231-153

INSTALLER_INFO: Changelist = 231153

INSTALLER_INFO: MakeId = 468595

INSTALLER_INFO: Type = kit

SYS_INFO: Host name = horus

SYS_INFO: System = Solaris

SYS_INFO: Architecture = X86-64

SYS_INFO: Version = 11

CALL: SDBUPD -INSTANCE -profile APO LiveCache

STDOUT:

Any idea how I can get past this error log:

Thanks

All

Edited by: Router Db on May 22, 2010 10:35 PM

[markus_doehr2 · Accepted solution]

> GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

> GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

> GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

> GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

GConf? Are you using NFS for sharing the home directory of the user running the database software?

Markus

[Former Member · Accepted solution]

I unshared the user's home directory and I still have the same problem. This error occurs when logged in as root. when logged in as the a user. SDBSETUP core dumps.

SDBINFO yeilds a n openwin install, when in actuality the directory /usr/X11/openwin exist with all contents.

I ran SDBSETUP from an older Solaris 10 x86 server and everything worked fine apparently there is some issue with a later distribution.

Tried on all newer Solaris 10 (5.11) distributions and it failed on all machines.

I have tried the following work rounds without any luck

1) killed the gconf daemon and ran SDBSETUP : no success

2) Remove ~/.dbus direcory : no success

3) ln -s ~/.gconfd /tmp/gconf-username

4) I did a remote mount of the install-directory on the machine to an older machine where it works, and installed from the remote machine and updated etc/services and data directory. Install went fine. But still could not run SDBSETUP from the local machine.

Perhaps I could rebuild build SDBSETUP from the sources, but need a source link.

This is an annoying bug. Did the entire development using MaxDB on an older solaris 10 distribution. QA/UAT machines are later solaris 10 distribution

any help will be appreciated

Regards

[markus_doehr2 · Accepted solution]

> I unshared the user's home directory and I still have the same problem. This error occurs when logged in as root. when logged in as the a user. SDBSETUP core dumps.

I would guess that there is an incompatibility between the libwx* and the bound gnome libraries between your installation and the installation SAP distributes.

> Tried on all newer Solaris 10 (5.11) distributions and it failed on all machines.

Well - that is actually Solaris 11 (OpenSolaris)

> Perhaps I could rebuild build SDBSETUP from the sources, but need a source link.

Believe, even if the sources were still available you don't want to do that

> This is an annoying bug. Did the entire development using MaxDB on an older solaris 10 distribution. QA/UAT machines are later solaris 10 distribution

They use the "first" distribution supported the ensure upward compatibility. I wouldn't blame SAP in that case but open a ticket with Sun to find out what's the incompatibility.

I tend to not use the graphical installer at all but install with the command line version (unset DISPLAY).

Markus

[Former Member · Accepted solution]

Hi markus,

Where is the command line install script. or does SDBSETUP have cli arguments ? If so can provide some guidance.

PS: SDBSETUP actuall dumps core when it is started so giving it command line options will not work in this case

Is there another command other than SDBSETUP?

[markus_doehr2 · Accepted solution]

> Where is the command line install script. or does SDBSETUP have cli arguments ? If so can provide some guidance.

There is SDBINST.

If you install a live cache, why don't you use the documented way?

Usually it's called by sapinst as

./SDBINST -indep_prog /sapdb/programs \
-indep_data /sapdb/data \
-depend /sapdb/<SID>/db \
-profile Server \
-o <owner>\
-g <group> \
-b

Markus