x_server start err message

[former_member709110]

Hi ...

I am getting the following error message ... plz advice

% ./x_server start

ERR 11779 NISERVER Error during startup:'dlopen failed:Could not load module /sapdb'

WNG 12457 XSERVER NI Init: Automatic niserver start failed, rc = 1

WNG 12453 NISSLSRV NISSL Init: dlopen failed:Could not load module /sapdb

12902 XSERVER started, 'X64/AIX 7.6.06 Build 010-123-229-880'

Regards,

Neel

[markus_doehr2 · Accepted solution]

It seems your environment is not properly set up.

Is this a SAP installation?

Markus

[former_member709110 · Accepted solution]

Hi Markus,

It is a Content Server ... can you point me to some post / document which talks about environment setting for maxdb to which i can refer to .

Regards,

Neel

[Former Member · Accepted solution]

Please go through the servcie.sap.com/CONTENTSERVER and also there are free MaxDB administration guides avaialble on http://maxdb.sap.com/training/ and the installation guide available https://service.sap.com/~sapdownload/011000358700000771312007E/

Enjoy MaxDB

[former_member229109]

Hello Neel,

According the posted information the niserver restart failed.

Are you SAP customer?

Please update the message with additional information:

1.

What is the OS version of database server?

What database software packages are installed on the server?

'uname -a'

'/sapdb/programs/bin/sdbregview -l'

'/sapdb/programs/bin/xinstinfo'

2.

Did you change the ownership, permissions or copy the database software?

Please login as root user & run '/sapdb/programs/sdbverify' & post the results.

3.

Please update with output of the commands:

id

ls -l /sapdb/programs/pgm

ls -l /sapdb

ls -l /sapdb/programs

ps -efe | grep vserver

ldd /sapdb/programs/pgm/niserver

Thank you and best regards, Natalia Khlopina

[former_member709110]

Hi Natalia ,

Plz find the details below

% uname -a

AIX <hostname> 1 6 00F624B84C00

% /sapdb/programs/bin/sdbregview -l

DB Analyzer /sapdb/programs 7.6.06.10 64 bit valid

Server Utilities /sapdb/programs 7.6.06.10 64 bit valid

PCR 7300 /sapdb/programs 7.3.00.58 valid <- sdbverfy marks it as inconsistent

PCR 7301 /sapdb/programs 7.3.01.22 valid <- sdbverfy marks it as inconsistent

PCR 7500 /sapdb/programs 7.5.00.46 64 bit valid <- sdbverfy marks it as inconsistent

SAP Utilities /sapdb/programs 7.6.03.09 64 bit valid

Base /sapdb/programs 7.6.06.10 64 bit valid

Redist Python /sapdb/programs 7.6.06.10 32 bit valid

JDBC /sapdb/programs 7.6.05.06 valid

Messages /sapdb/programs MSG 0.8215 valid

ODBC /sapdb/programs 7.6.03.09 64 bit valid

Database Kernel /sapdb/MS2/db 7.6.06.10 64 bit valid

Database Kernel /sapdb/MD2/db 7.6.03.09 64 bit valid

Loader /sapdb/programs 7.6.06.10 64 bit valid

SQLDBC /sapdb/programs 7.6.03.09 64 bit valid

SQLDBC 76 /sapdb/programs 7.6.03.09 64 bit valid

Fastload API /sapdb/programs 7.6.03.09 64 bit valid

PCR 7403 /sapdb/programs 7.4.03.49 64 bit valid <- sdbverfy marks it as inconsistent

% /sapdb/programs/bin/xinstinfo

IndepData : /sapdb/data

IndepPrograms : /sapdb/programs

sdbverify output:

VERIFICATION SUMMARY:

*********************

INVALID PACKAGES: 0

VALID PACKAGES: 18

INCONSISTENT PACKAGES: 4

TOTAL FILES: 499

MISSED FILES: 0

MODIFIED FILES: 1

FILES WITH MODIFIED PERMISSIONS: 0

% ps -ef|grep vserver

sdb 17694988 1 0 12:19:30 pts/6 0:00 /sapdb/programs/pgm/vserver start

% ldd /sapdb/programs/pgm/niserver

ldd: /sapdb/programs/pgm/niserver: File is not an executable XCOFF file.

Any suggestion regarding the inconsistent packages ? how to handle them ?

Regards,

Neel

Edited by: Neelabha Banerjee on Nov 17, 2010 9:38 PM

[former_member229109]

Hello Neel,

1.

Are you SAP customer?

2.

According the posted information the niserver restart failed.

A.

Run the commands:

env

/sapdb/programs/bin/x_niserver start

post the results & niserver* protocol errors located in /sapdb/data/wrk

B.

Run the commands:

ls -l /sapdb/programs/bin

ls -l /sapdb/programs/pgm

/sapdb/programs/bin/x_server stop

ps -efe | grep vserver

< check that there no hanging vserver processes >

/sapdb/programs/bin/x_server -Y

< test if you can start the Xserver without the Niserver. >

3.

"Any suggestion regarding the inconsistent packages ? how to handle them ?"

PCR, runtime database packages could be corrected with the next database upgrade, for example.

It will be helpful to see more details in sdbverify output.

It's not related to the niserver issue posted by you.

Thank you and best regards, Natalia Khlopina

[former_member709110]

Hi Natalia ,

Plz find the info as requested

1 . I am consultant with SAP's partner , and this issue is related to one of SAP's customers; btw maxdb is not my area of specialization so i have very limited knowledge.

2. Yes as pointed by you the niserver start fails , but the x_server starts and i am able to connect through the database manager also.

I have also tried to start x_server with -X and -Y option x_server start fine.

A.

/sapdb/programs/bin/x_niserver ... i dont see it ... am i missing something ?

B.

% ls -l /sapdb/programs/bin

total 411136

-r-xr-xr-x 1 sdb sdba 13194 Feb 15 2010 SDBINST

-r-xr-xr-x 1 sdb sdba 13194 Feb 15 2010 SDBINST.mod0

-r-xr-xr-x 1 sdb sdba 13194 Feb 15 2010 SDBINST.mod1

-r-xr-xr-x 1 sdb sdba 15738 Feb 15 2010 SDBSETUP

-r-xr-xr-x 1 sdb sdba 15738 Feb 15 2010 SDBSETUP.mod0

-r-xr-xr-x 1 sdb sdba 15738 Feb 15 2010 SDBSETUP.mod1

-r-xr-xr-x 1 sdb sdba 3558288 Feb 15 2010 dbanalyzer

-r-xr-xr-x 1 sdb sdba 3558288 Feb 15 2010 dbanalyzer.mod0

-r-xr-xr-x 1 sdb sdba 3558288 Feb 15 2010 dbanalyzer.mod1

-r-xr-xr-x 1 sdb sdba 9076827 Feb 15 2010 dbmcli

-r-xr-xr-x 1 sdb sdba 9076827 Feb 15 2010 dbmcli.mod0

-r-xr-xr-x 1 sdb sdba 9076827 Feb 15 2010 dbmcli.mod1

-r-xr-xr-x 1 sdb sdba 3618769 Feb 15 2010 dbmevtdisp

-r-xr-xr-x 1 sdb sdba 3618769 Feb 15 2010 dbmevtdisp.mod0

-r-xr-xr-x 1 sdb sdba 3618769 Feb 15 2010 dbmevtdisp.mod1

-r-xr-xr-x 1 sdb sdba 1567432 Oct 25 2007 dbmgetf

-r-xr-xr-x 1 sdb sdba 9588064 Oct 25 2007 dbmrfc

-r-ssx 1 sdb sdba 1196352 Feb 15 2010 getdbroot

-r-ssx 1 sdb sdba 1196352 Feb 15 2010 getdbroot.mod0

-r-ssx 1 sdb sdba 1196352 Feb 15 2010 getdbroot.mod1

-r-xr-xr-x 1 sdb sdba 7890179 Feb 15 2010 loadercli

-r-xr-xr-x 1 sdb sdba 7890179 Feb 15 2010 loadercli.mod0

-r-xr-xr-x 1 sdb sdba 7890179 Feb 15 2010 loadercli.mod1

-r-xr-xr-x 1 sdb sdba 1338060 Feb 15 2010 protconv

-r-xr-xr-x 1 sdb sdba 1338060 Feb 15 2010 protconv.mod0

-r-xr-xr-x 1 sdb sdba 1338060 Feb 15 2010 protconv.mod1

-r-xr-xr-x 1 sdb sdba 1069573 Feb 15 2010 sdbconfig

-r-xr-xr-x 1 sdb sdba 1069573 Feb 15 2010 sdbconfig.mod0

-r-xr-xr-x 1 sdb sdba 1069573 Feb 15 2010 sdbconfig.mod1

-r-xr-xr-x 1 sdb sdba 40079 Feb 15 2010 sdbinfo

-r-xr-xr-x 1 sdb sdba 40079 Feb 15 2010 sdbinfo.mod0

-r-xr-xr-x 1 sdb sdba 40079 Feb 15 2010 sdbinfo.mod1

-r-xr-xr-x 1 sdb sdba 13194 Feb 15 2010 sdbpack

-r-xr-xr-x 1 sdb sdba 13194 Feb 15 2010 sdbpack.mod0

-r-xr-xr-x 1 sdb sdba 13194 Feb 15 2010 sdbpack.mod1

-r-xr-xr-x 1 sdb sdba 13186 Feb 15 2010 sdbreg

-r-xr-xr-x 1 sdb sdba 13186 Feb 15 2010 sdbreg.mod0

-r-xr-xr-x 1 sdb sdba 13186 Feb 15 2010 sdbreg.mod1

-r-xr-xr-x 1 sdb sdba 12966 Feb 15 2010 sdbregview

-r-xr-xr-x 1 sdb sdba 12966 Feb 15 2010 sdbregview.mod0

-r-xr-xr-x 1 sdb sdba 12966 Feb 15 2010 sdbregview.mod1

-r-xr-xr-x 1 sdb sdba 12958 Feb 15 2010 sdbuninst

-r-xr-xr-x 1 sdb sdba 12958 Feb 15 2010 sdbuninst.mod0

-r-xr-xr-x 1 sdb sdba 12958 Feb 15 2010 sdbuninst.mod1

-r-xr-xr-x 1 sdb sdba 12966 Feb 15 2010 sdbverify

-r-xr-xr-x 1 sdb sdba 12966 Feb 15 2010 sdbverify.mod0

-r-xr-xr-x 1 sdb sdba 12966 Feb 15 2010 sdbverify.mod1

-r-xr-xr-x 1 sdb sdba 4911748 Feb 15 2010 sqlcli

-r-xr-xr-x 1 sdb sdba 4911748 Feb 15 2010 sqlcli.mod0

-r-xr-xr-x 1 sdb sdba 4911748 Feb 15 2010 sqlcli.mod1

-r-xr-xr-x 1 sdb sdba 4814384 Feb 15 2010 sqldbc_cons

-r-xr-xr-x 1 sdb sdba 4814384 Feb 15 2010 sqldbc_cons.mod0

-r-xr-xr-x 1 sdb sdba 33737 Feb 15 2010 sqlver

-r-xr-xr-x 1 sdb sdba 33737 Feb 15 2010 sqlver.mod0

-r-xr-xr-x 1 sdb sdba 33737 Feb 15 2010 sqlver.mod1

-r-xr-xr-x 1 sdb sdba 33331 Feb 15 2010 sqlwhat

-r-xr-xr-x 1 sdb sdba 33331 Feb 15 2010 sqlwhat.mod0

-r-xr-xr-x 1 sdb sdba 33331 Feb 15 2010 sqlwhat.mod1

dr-x------ 2 sdb sdba 96 Nov 17 10:31 starter

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 sysmon

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 sysmon.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 sysmon.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_analys

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_analys.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_analys.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_cons

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_cons.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_cons.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_maketi

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_maketi.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_maketi.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_ping

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_ping.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_ping.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_python

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_python.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_python.mod1

-r-sr-s--x 1 sdb sdba 1711632 Feb 15 2010 x_server

-r-sr-s--x 1 sdb sdba 1711632 Feb 15 2010 x_server.mod0

-r-sr-s--x 1 sdb sdba 1711632 Feb 15 2010 x_server.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_start

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_start.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_start.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_stop

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_stop.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_stop.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wiz

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wiz.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wiz.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wizard

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wizard.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wizard.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wizstop

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wizstop.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wizstop.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wiztrc

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wiztrc.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 x_wiztrc.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xbackup

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xbackup.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xbackup.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xinstinfo

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xinstinfo.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xinstinfo.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xpu

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xpu.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xpu.mod1

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xsysrc

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xsysrc.mod0

-r-xr-xr-x 1 sdb sdba 1711632 Feb 15 2010 xsysrc.mod1

-r-xr-xr-x 1 sdb sdba 1186396 Feb 15 2010 xuser

-r-xr-xr-x 1 sdb sdba 1186396 Feb 15 2010 xuser.mod0

-r-xr-xr-x 1 sdb sdba 1186396 Feb 15 2010 xuser.mod1

%

ls -l /sapdb/programs/pgm

total 116256

-r-xr-xr-x 1 sdb sdba 7896284 Feb 15 2010 lserver

-r-xr-xr-x 1 sdb sdba 7896284 Feb 15 2010 lserver.mod0

-r-xr-xr-x 1 sdb sdba 7896284 Feb 15 2010 lserver.mod1

-r-xr-xr-x 1 sdb sdba 1132675 Feb 15 2010 maketi

-r-xr-xr-x 1 sdb sdba 1132675 Feb 15 2010 maketi.mod0

-r-xr-xr-x 1 sdb sdba 1132675 Feb 15 2010 maketi.mod1

-r-x------ 1 sdb sdba 1518715 Feb 15 2010 niserver

-r-x------ 1 sdb sdba 1518715 Feb 15 2010 niserver.mod0

-r-x------ 1 sdb sdba 1518715 Feb 15 2010 niserver.mod1

-r-x------ 1 sdb sdba 1517934 Feb 15 2010 nisslserver

-r-x------ 1 sdb sdba 1517934 Feb 15 2010 nisslserver.mod0

-r-x------ 1 sdb sdba 1517934 Feb 15 2010 nisslserver.mod1

-r-xr-xr-x 1 sdb sdba 3550136 Feb 15 2010 python

-r-xr-xr-x 1 sdb sdba 3550136 Feb 15 2010 python.mod0

-r-xr-xr-x 1 sdb sdba 3550136 Feb 15 2010 python.mod1

-r-xr-xr-x 1 sdb sdba 1203564 Feb 15 2010 regupd

-r-xr-xr-x 1 sdb sdba 1203564 Feb 15 2010 regupd.mod0

-r-xr-xr-x 1 sdb sdba 1203564 Feb 15 2010 regupd.mod1

-r-xr-xr-x 1 sdb sdba 1348564 Feb 15 2010 sqlping

-r-xr-xr-x 1 sdb sdba 1348564 Feb 15 2010 sqlping.mod0

-r-xr-xr-x 1 sdb sdba 1348564 Feb 15 2010 sqlping.mod1

dr-x------ 2 sdb sdba 96 Nov 17 10:31 starter

-r-x------ 1 sdb sdba 1641791 Feb 15 2010 vserver

-r-x------ 1 sdb sdba 1641791 Feb 15 2010 vserver.mod0

-r-x------ 1 sdb sdba 1641791 Feb 15 2010 vserver.mod1

As mentioned earlier , i don't think i have any issue with the x_server , i am able to start /stop and also there is no hanging vserver process

C.

I am pasting the inconsistent packages :

PCR 7300 7.3.00.58 in /sapdb/programs

-

---

check files... ok

check dependencies... ok

check rte registration of package... failed

package data is inconsistent

PCR 7301 7.3.01.22 in /sapdb/programs

-

---

check files... ok

check dependencies... ok

check rte registration of package... failed

package data is inconsistent

PCR 7500 7.5.00.46 64 bit in /sapdb/programs

-

---

check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

PCR 7403 7.4.03.49 64 bit in /sapdb/programs

-

---

check files... ok

check dependencies... ok

check rte registration of package... failed

package data is inconsistent

I am on 7.6 are these package relavent ...

Regards,

Neel

env

TERM=vt100

AUTHSTATE=files

SHELL=/usr/bin/csh

HOME=/usr/sap/ms2cs

USER=ms2cs

PATH=/opt/SUNWstudio12/SUNWspro/bin:/usr/sbin:/usr/bin:/usr/ccs/bin

TZ=America/Los_Angeles

LANG=C

LOCPATH=/usr/lib/nls/loc

LC__FASTMSG=true

ODMDIR=/etc/objrepos

LOGNAME=ms2cs

LOGIN=ms2cs

CFLAGS=-xarch=v9

LDFLAGS=-xarch=v9

NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat

LD_LIBRARY_PATH=lib/64:/usr/lib/64

%

Edited by: Neelabha Banerjee on Nov 18, 2010 9:37 AM

[former_member709110]

Natalia ,

Not sure if you can read the info i have posted above ...bcoz of the formatting ... if you cant let me know i will email it on the email address in ur buisness card

Regards,

Neel

[former_member229109]

Hello Neel,

I read the above reply with Edit option.

The Niserver is Part of the X Server, responsible for NI support in SAP systems.

When the SAP support need to access to the database usung the DB connection,

customer need to check that the niserver is running on the database server.

1. Did customer create the SAP message on this issue?

As this issue is related to one of SAP's customers and the MAXDB is not your area of specialization for the consulting,

then it's better for the customer's database administrator to communicate with SAP support.

2. It will be helpful to ligin to the database server and check the niserver protockol and trace first, located in /sapdb/data/wrk as I wrote above.

Directory : /sapdb/data/wrk

Run command - 'ls -l /sapdb/data/wrk | grep server'

Files to check, first :

xserver_<serverName>.nitrace

< .... niserver_ <serverName>.trace >

xserver_<serverName>.prt

Thank you and best regards, Natalia Khlopina