cancel
Showing results for 
Search instead for 
Did you mean: 

Why I cannot start the server and the database after the installation?

Former Member
0 Kudos

Dear all,

I have just installed SAP Netweaver Trial

https://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/60d6c8b7-5d8f-2910-31bf-ebdf74fefd8b

on linux (Fedora Core 11 64 bits). The server was installed successfully (Ok message at the end).

Yet I'm not able to open the database and an attempt to do that generates the following error

message:


n4shost:n4sadm 10> startsap n4shost
 Warning: Could not found virtuell host in ifconfig list

Checking ADA db Database
------------------------------
 ABAP Database is not available via R3trans

Starting SAP-Collector Daemon 
------------------------------
20:54:28 18.06.2009   LOG: Effective User Id is root
***********************************************************************
* This is Saposcol Version COLL 20.89 700 - AMD/Intel x86_64 with Linux, PL:52, Mar 31 2006
* Usage:  saposcol -l: Start OS Collector 
*         saposcol -k: Stop  OS Collector 
*         saposcol -d: OS Collector Dialog Mode
*         saposcol -s: OS Collector Status
* The OS Collector (PID 3276) is already running ..... 
************************************************************************
 saposcol already running
 Running /usr/sap/N4S/SYS/exe/run/startdb 
Trying to start database ...
Log file: /home/n4sadm/startdb.log
Database start failed
DB startup failed
n4shost:n4sadm 11>

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi dariyoosh

If database MaxDB then ignore my previous reply.

I thnk Trial ver has only MaxDB

Thnx

SurendraJain

former_member204746
Active Contributor
0 Kudos

why don't you look at tracefile /home/n4sadm/startdb.log ?

hannes_kuehnemund
Active Contributor
0 Kudos

Another hint is to look into knldiag / KnlMsg files, maybe MaxDB core dumps during startup and writes nothing into the logfiles?

Former Member
0 Kudos

>

> Hi dariyoosh

> If database MaxDB then ignore my previous reply.

> I thnk Trial ver has only MaxDB

> Thnx

> SurendraJain

Hi there,

Thanks a lot for your attention. According to the SAP download page

(I provided the link in my first post), here is what the package contains:

Download SAP NetWeaver 7.0 (2004s) - Trial Version for Linux Platform. This package

includes both ABAP and Java stacks running on SAP's own database Max DB

version 7.5 or IBM DB2 Universal Database for Linux version 8.2. SAP NetWeaver

Developer Studio (Windows Version) is included in the package. It also provides

Web Dynpro for ABAP, Web Dynpro for Java and SAP Interactive Forms by Adobe.

(SAP NetWeaver 7.0, 4.5 GB)

Thanks again,

Regards,

Dariyoosh

Former Member
0 Kudos

>

> why don't you look at tracefile /home/n4sadm/startdb.log ?

Hello there,

Thanks for your answer, Here is the content of this file


n4shost:n4sadm 2> cat /home/n4sadm/startdb.log

------------------------------ Fri Jun 19 07:57:41 CEST 2009
LOGFILE FOR STARTING DATABASE

Trying to start database ...

------------------------------ Fri Jun 19 07:57:41 CEST 2009
Checking required environment variables

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

------------------------------ Fri Jun 19 07:57:41 CEST 2009
Connect to the database to check the database state

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

------------------------------ Fri Jun 19 07:57:41 CEST 2009
Starting XServer

    12798  NISERVER NI support started.
WNG 12453  NISSLSRV NISSL Init: SSL: Could not locate licence file
    12902  XSERVER  started, 'X64/LINUX 7.6.00   Build 018-123-119-055'

------------------------------ Fri Jun 19 07:57:42 CEST 2009
Starting database

Starting Database Instance...
Error! XUser not found!
Opening Database...
Error! XUser not found!

------------------------------ Fri Jun 19 07:57:42 CEST 2009
Connect to the database to verify the database is now open

dbmcli check finished with return code: 0
Database start failed
n4shost:n4sadm 3>

So there are several errors such as:

- Error! XUser not found!

- Database not available

But I cannot find the source of these errors.

Regards,

Dariyoosh

Former Member
0 Kudos

Hi,

Give dbstart.log or go to sql prompt

SQL> startup

wht is the error message if not sucessfully run.

if sucessful then start other instance

SurendraJain

markus_doehr2
Active Contributor
0 Kudos

> SQL> startup

This is a MaxDB database and is not started by sql and "startup" (that is for Oracle).

Try

dbmcli -U c db_online

If that fails, check the knldiag in /sapdb/data/wrk/N4S

Markus

Former Member
0 Kudos

>

> Try

>

>

dbmcli -U c db_online

>

> If that fails, check the knldiag in /sapdb/data/wrk/N4S

Hello there,

Thanks for your answer. Here is the output of dbmcli.


$ su n4sadm
Password: 
setenv: Too many arguments.
n4shost:n4sadm 1> dbmcli -U c db_online
Error! XUser not found!
n4shost:n4sadm 2> 

In the case where you're interested, here is the link to knldiag and knldiag.err files

http://dl.free.fr/bdJAkVGWZ/knldiag.tar.gz

Here is an exteact of the begining of knldia.err


--------------------------------------------------------------------------------
Date       Time       TID Typ MsgID Label    Message-Text
--------------------------------------------------------------------------------
2006-06-23 18:04:40                          --- Starting GMT 2006-06-23 16:04:40           7.6.00   Build 018-123-119-055 
2006-06-23 18:16:03                          ___ Stopping GMT 2006-06-23 16:16:03           7.6.00   Build 018-123-119-055 
2006-06-23 18:16:18                          --- Starting GMT 2006-06-23 16:16:18           7.6.00   Build 018-123-119-055 
2006-06-23 18:16:31    26 ERR 11000 d0_vatta Cannot open volume, No such file or directory 
2006-06-23 18:16:31    26 ERR 11000 d0_vatta Volume name 'DATA0001' 
2006-06-23 18:16:31    24 ERR 11000 vattach  dev0_vattach returned FALSE
2006-06-23 18:16:31    24 ERR 20031 IOMan    IOMan_Volume.cpp:976
2006-06-23 18:16:31    24 ERR 20031 IOMan    2006-06-23 18:16:31 IOMan Error 20031
2006-06-23 18:16:31    24 ERR 20031 IOMan    Attach error on Data volume 1: Could not open volume
2006-06-23 18:16:31    24 ERR 20040 IOMan    IOMan_Manager.cpp:585
2006-06-23 18:16:31    24 ERR 20040 IOMan    2006-06-23 18:16:31 IOMan Error 20040
2006-06-23 18:16:31    24 ERR 20040 IOMan    Bad restart page on Data volume 0 blockno 0
.
.
.

Regards,

Dariyoosh

markus_doehr2
Active Contributor
0 Kudos

> $ su n4sadm

> Password:

> setenv: Too many arguments.

> n4shost:n4sadm 1> dbmcli -U c db_online

> Error! XUser not found!

If you do it like this it's expected.

Doing an "su" to another user like this means, that you switch the user only but you don't get the users environment. Since the "-U" looks for a $HOME/.XUSER62 file in the roots home directory it won't find it.

You need to do a

su - n4sadm (including a dash).

> -


> Date Time TID Typ MsgID Label Message-Text

> -


> 2006-06-23 18:04:40 --- Starting GMT 2006-06-23 16:04:40 7.6.00 Build 018-123-119-055

> 2006-06-23 18:16:03 ___ Stopping GMT 2006-06-23 16:16:03 7.6.00 Build 018-123-119-055

> 2006-06-23 18:16:18 --- Starting GMT 2006-06-23 16:16:18 7.6.00 Build 018-123-119-055

> 2006-06-23 18:16:31 26 ERR 11000 d0_vatta Cannot open volume, No such file or directory

> 2006-06-23 18:16:31 26 ERR 11000 d0_vatta Volume name 'DATA0001'

> 2006-06-23 18:16:31 24 ERR 11000 vattach dev0_vattach returned FALSE

> 2006-06-23 18:16:31 24 ERR 20031 IOMan IOMan_Volume.cpp:976

> 2006-06-23 18:16:31 24 ERR 20031 IOMan 2006-06-23 18:16:31 IOMan Error 20031

> 2006-06-23 18:16:31 24 ERR 20031 IOMan Attach error on Data volume 1: Could not open volume

> 2006-06-23 18:16:31 24 ERR 20040 IOMan IOMan_Manager.cpp:585

> 2006-06-23 18:16:31 24 ERR 20040 IOMan 2006-06-23 18:16:31 IOMan Error 20040

> 2006-06-23 18:16:31 24 ERR 20040 IOMan Bad restart page on Data volume 0 blockno 0

The problem is, that the first database volume is not found.

What happened prior to this problem? Did you reboot the machine without stopping the database?

Markus

Former Member
0 Kudos

>

> If you do it like this it's expected.

>

> Doing an "su" to another user like this means, that you switch the user only but you don't get the users environment. Since the "-U" looks for a $HOME/.XUSER62 file in the roots home directory it won't find it.

>

> You need to do a

>

> su - n4sadm (including a dash).

> Markus

I Proceeded once again, this time including a dash, but the result was the same.


Error! XUser not found!

>

> The problem is, that the first database volume is not found.

>

> What happened prior to this problem? Did you reboot the machine without stopping the database?

>

> Markus

Actually, this was the first time that I wanted to start the server just after installing SAP Netweaver.

As a result, there were no prior action.

Thanks again,

Regards,

Dariyoosh

hannes_kuehnemund
Active Contributor
0 Kudos

Hi,

the solution is simple, you have to recreate the .XUSER.62 file. This can be done by executing the following four commands as user n4sadm:


/sapdb/programs/bin/xuser -U DEFAULT -u sapn4s,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set
/sapdb/programs/bin/xuser -U c -u control,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set
/sapdb/programs/bin/xuser -U c_J2EE -u control,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set
/sapdb/programs/bin/xuser -U w -u superdba,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set

Thanks,

Hannes

hannes_kuehnemund
Active Contributor
0 Kudos

Hi,

the snippet:


Warning: Could not found virtuell host in ifconfig list

looks suspicious. We had several problems with the N4S testdrive because distributions removed the eth0:0 device needed to start the testdrive. Could you execute the following command (it creates a virtual network interface) as user root before you start the system as n4sadm?


ifconfig eth0:0 192.168.155.1 up

Best Regards,

Hannes

Former Member
0 Kudos

Dear Hannes,

Thanks a lot for your answer.

Here is what I obtain when I run ifconfig as you asked me to do:


$ su root
password
#
#
#
# ifconfig eth0:0 192.168.155.1 up
#
# su n4sadm
$
$
setenv: Too many arguments.
n4shost:n4sadm 1> startsap n4shost

Checking ADA db Database
------------------------------
 ABAP Database is not available via R3trans

Starting SAP-Collector Daemon
------------------------------
07:57:34 19.06.2009   LOG: Effective User Id is root
******************************************************************************
* This is Saposcol Version COLL 20.89 700 - AMD/Intel x86_64 with Linux, PL:52, Mar 31 2006
* Usage:  saposcol -l: Start OS Collector
*         saposcol -k: Stop  OS Collector
*         saposcol -d: OS Collector Dialog Mode
*         saposcol -s: OS Collector Status
* Starting collector (create new process)
******************************************************************************
 saposcol on host alborz started
 Running /usr/sap/N4S/SYS/exe/run/startdb
Trying to start database ...
Log file: /home/n4sadm/startdb.log
Database start failed
DB startup failed
n4shost:n4sadm 2>

Again the same problem.

Regards,

Dariyoosh

hannes_kuehnemund
Active Contributor
0 Kudos

[edited and moved parts from above thread to this reply]

I also checked the R3trans file in order to see the corresponding architecture


n4shost:n4sadm 11> file /usr/sap/N4S/SYS/exe/run/R3trans
/usr/sap/N4S/SYS/exe/run/R3trans: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
 linked (uses shared libs), for GNU/Linux 2.4.1, not stripped
n4shost:n4sadm 12>

Any idea? Why I'm not able to start the server and open the database?

Thanks in advance,

For information:

Operating System: Fedora Core 11


$ uname -a
Linux alborz 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
$


n4shost:n4sadm 12> cat /home/n4sadm/startdb.log

------------------------------ Thu Jun 18 20:54:28 CEST 2009
LOGFILE FOR STARTING DATABASE

Trying to start database ...

------------------------------ Thu Jun 18 20:54:28 CEST 2009
Checking required environment variables

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

------------------------------ Thu Jun 18 20:54:28 CEST 2009
Connect to the database to check the database state

dbmcli: connect check finished with return code: 0

.
. 
.