cancel
Showing results for 
Search instead for 
Did you mean: 

MaxDB 7.6 Patch 35 - x_server not running

Former Member
0 Kudos

Hello,

i try tp patch our maxdb contentserver (2 Databases, EC9 and ES9) from 7.6 18 to 35. Following error occurs.

....

beginning to check sap db instances

start new instance update

cannot start x_server

MaxDB instance update exited abnormally at Mo, Dec 18, 2006 at 20:44:36

In the Upgradelog i find the following:

.....

..

MSG: no installation data to migrate

STDOUT: beginning to check sap db instances

STDOUT: start new instance update

x_server is not running

SYS: /sapdb/programs/bin/x_server start: 12916 XSERVER Found other running x_server with version 'X64/SUN 7.6.00 Bui

ld 018-123-119-055'

SYS: /sapdb/programs/bin/x_server start: 12902 XSERVER started, 'already...'

x_server is not running

STDERR: cannot start x_server

STDERR:

STDERR: MaxDB instance update exited abnormally at Mo, Dec 18, 2006 at 20:44:36

MSG: don't need to write package registry

MSG: install registry successfully unlocked

...

my thought was, there is somewhere a wrong permission, but i can't find anything wrong.

Does anyone know something about this "error"?

thanks

Christian

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Christian,

please stop the x_server process and verify that there are no x_server/vserver processes running. Also verify that no other instances or MAXDB software (for e.g., dbmcli sessions, dbmsrv processes, etc.) are running. Then retry the upgrade and update us of the results.

Thanks,

Ashwath

Former Member
0 Kudos

Hello,

we solved it. The x_server was not the problem. it startet and stopped normaly... SDBUPD just can't verify if x_server is running.

So the solution was, that some entries in /etc/services have failed.

the entries where

sql30 7200/tcp

sql6 7210/tcp

chris

Former Member
0 Kudos

Hi,

so is the upgrade done now? If yes, please close this thread.

Thanks,

Ashwath

Answers (0)