cancel
Showing results for 
Search instead for 
Did you mean: 

Database error for NW7.02 TestDrive Linux 86_64

Former Member
0 Kudos

Hi,

We've just had a short blackout of the area and when I turned my Fedora box back on and attempted to start my NW7.02 TestDrive, I'm getting the following errors. Could anyone help please? Thanks.

------------------------------ Thu Aug 16 11:15:08 EST 2012
LOGFILE FOR STARTING DATABASE

Trying to start database ...

------------------------------ Thu Aug 16 11:15:08 EST 2012
Checking required environment variables

SAPSYSTEMNAME is >NPL<
Start database with xuserkey >c<

------------------------------ Thu Aug 16 11:15:08 EST 2012
Connect to the database to check the database state

dbmcli: connect check finished with return code: 0
Database not available

------------------------------ Thu Aug 16 11:18:18 EST 2012
Starting XServer

2012-08-16 11:18:18 28864 INF  12903          XServer on port 7200 started
2012-08-16 11:18:18 28864 INF  13010            installation NPL  - path: /sapdb
/NPL/db
2012-08-16 11:18:18 28000 INF  12798 NISERVER NI support started.
2012-08-16 11:18:19 49216 WNG  12453 NISSLSRV NISSL Init: SSL: Could not locate
ticket file
2012-08-16 11:18:19 33472 INF  12903          sdbgloballistener on port 7210 sta
rted

------------------------------ Thu Aug 16 11:18:19 EST 2012
Starting database

Starting Database Instance...
Error! Connection failed to node nplhost for database NPL:
cannot connect to server socket
Opening Database...
Error! Connection failed to node nplhost for database NPL:
cannot connect to server socket

------------------------------ Thu Aug 16 11:24:38 EST 2012
Connect to the database to verify the database is now open

dbmcli check finished with return code: 0

In addition, i have also used sdbverify to check the database and below is the log:

Checking installation "Global" (/sapdb/programs, 7.8.01.19)

Checking package Installer

Checking package SAP Utilities Compatibility

Checking package Global Listener

Checking package Installation Compatibility

Checking installation "Legacy" (/sapdb/programs, )

Checking installation "CL_NPL" (/sapdb/clients/NPL, 7.8.01.20)

Checking package Base

Checking package SQLDBC

Checking package SQLDBC 77

Checking package Fastload API

Checking package SQLDBC 76

Checking package SAP Utilities

Checking package Redist Python

Checking package Loader

Checking package ODBC

Checking package Messages

Checking package JDBC

Checking installation "NPL" (/sapdb/NPL/db, 7.8.01.20)

Checking package Base

Checking package SQLDBC

Checking package SQLDBC 77

Checking package Fastload API

Checking package SQLDBC 76

Checking package SAP Utilities

Checking package Server Utilities

Checking package Database Kernel

Checking package Redist Python

Checking package Loader

Checking package ODBC

Checking package Messages

Checking package JDBC

Checking package DB Analyzer

ERR:  Failed

ERR:    Checking installation "Global" failed

ERR:      Global state directory /var/lib/sdb has wrong mode

ERR:    Checking installation "Legacy" failed

ERR:      Global state directory /var/lib/sdb has wrong mode

ERR:    Checking installation "CL_NPL" failed

ERR:      Directory /sapdb/clients/NPL/data/pipe doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/ipc doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/dbspeed doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/diag doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/fifo doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/pid doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/ppid doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/wrk doesn't exist

ERR:      Directory /sapdb/clients/NPL/data/config doesn't exist

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Shan,

Just check if the file system /sapdb and subsquent ones under it are mounted.

Regards.

Ruchit

Former Member
0 Kudos

hi Ruchit,

Thanks for the reply. All directories/folders under /sapdb have been properly mounted.

total 16

drwxrwxr-x. 12 sdb  sdba  4096 Jan 10  2011 data

dr-xr-xr-x.  9 root scong 4096 Jan 10  2011 programs

dr-xr-xr-x.  3 root scong 4096 Jan 10  2011 clients

dr-xr-xr-x.  6 root scong 4096 Jan 10  2011 NPL

Former Member
0 Kudos

Hi Shan,

Just try to change ownership to sdb:sdba for directories. Also what is command for which you puhave published the output. I hope it is not ls

Regards.

Ruchit.

Former Member
0 Kudos

That worked. Thanks.

Cheers.

Answers (0)