Step2 N4S TestDrive: Error in Starting the server

[Former Member]

I am installing N4S (NW 2004s testdrive) on SUSE Linux 64bit running in AMD 64 platform.

1) I got the license key but it was a N4S.txt (text file) instead of rpm file.

2) try to start db by su loging as n4sadm and get a message "Database Start failed..."

3) I did not have .rpm so did not install license.

The log file from database start

_____

-

---

Fri May 22 19:12:45 CDT 2009

LOGFILE FOR STARTING DATABASE

Trying to start database ...

-

---

Fri May 22 19:12:45 CDT 2009

Checking required environment variables

SAPSYSTEMNAME is >N4S<

Start database with xuserkey >c<

-

---

Fri May 22 19:12:45 CDT 2009

Connect to the database to check the database state

dbmcli: connect check finished with return code: 0

Database not available

-

---

Fri May 22 19:12:45 CDT 2009

Starting XServer

12916 XSERVER Found other running x_server with version 'X64/LINUX 7.6.00 Build 018-123-119-055'

12902 XSERVER started, 'already...'

-

---

Fri May 22 19:12:45 CDT 2009

Starting database

Starting Database Instance...

OK

Opening Database...

ERR

-24988,ERR_SQL: Sql error

-902,I/O error

3,Database state: OFFLINE

6,Internal errorcode, Errorcode 9050 "disk_not_accessible"

20014,RestartFilesystem failed with 'I/O error'

-

---

Fri May 22 19:12:53 CDT 2009

Connect to the database to verify the database is now open

dbmcli check finished with return code: 0

Database start failed

-

---

After this I try startsap but I get a error message "No start profiles found"

Thanks for you help

[Former Member · Accepted solution]

while opening the db, it's showing i/o error and disk error, you might want to check the filesystem and the permissions and in the last it's showing 'Database start failed', check whethere database is up or not. and listener is running or not.

check R3trans -d as sidadm and rc, check trans.log file

and for startsap message, that message comes when either you are using the incorrect syntax in startsap command or check the permission of profile path

[Former Member · Accepted solution]

R3trans -d return code is 0012.

I tried "startdb command again and after long time came back with the message "Database start failed"

i viewd the /home/n4sadm/startdb.log and found a new error message as shown below

Starting database

Starting Database Instance...

Error! Connection failed to node n4shost for database N4S: cannot connect to server socket

Opening Database...

Error! Connection failed to node n4shost for database N4S: cannot connect to server socket

-

---

this seems to be a completely different issue. Any hints to address this particular problem.

[hannes_kuehnemund · Accepted solution]

Dear Ashok,

it is impossible to install a license if the database it not started. As you can see, the database cannot access the disk. Normally, you have to check the knldiag file and search for ERR in there.

But as you already stated, that you had problems of tar, please give md5sums of your 7 files.

md5sum <file1>
md5sum <file2>
...
md5sum <file7>

I can then tell you, if your files are corrupt.

Thanks,

Hannes

[Former Member · Accepted solution]

I am providing the md5sum of the seven files in order below.

8a2459a8396e7e937fa1301eda5c77e0 *N4S_TestDrive_MaxDB.iso_Part_aa

638be1e5d39e389008247b82a54ef784 *N4S_TestDrive_MaxDB.iso_Part_ab

0fa22828317a1721ff1fd73be46b0709 *N4S_TestDrive_MaxDB.iso_Part_ac

b5f0b83f549009d69cc0f209f14f49a9 *N4S_TestDrive_MaxDB.iso_Part_ad

8b934c1c18240158974fcfa15dae62a4 *N4S_TestDrive_MaxDB.iso_Part_ae

3cd5fe69b322d40d4790d3809348f4b5 *N4S_TestDrive_MaxDB.iso_Part_af

28b348d803c9b68fe82350fb302be751 *N4S_TestDrive_MaxDB.iso_Part_ag

Thanks,

Ashok

[hannes_kuehnemund · Accepted solution]

Dear Ashok,

mine are:

8a2459a8396e7e937fa1301eda5c77e0  N4S_TestDrive_MaxDB.iso_Part_aa
638be1e5d39e389008247b82a54ef784  N4S_TestDrive_MaxDB.iso_Part_ab
0fa22828317a1721ff1fd73be46b0709  N4S_TestDrive_MaxDB.iso_Part_ac
b5f0b83f549009d69cc0f209f14f49a9  N4S_TestDrive_MaxDB.iso_Part_ad
3df0c19f7e65eb18947e0c50bdfaf721  N4S_TestDrive_MaxDB.iso_Part_ae
3cd5fe69b322d40d4790d3809348f4b5  N4S_TestDrive_MaxDB.iso_Part_af
28b348d803c9b68fe82350fb302be751  N4S_TestDrive_MaxDB.iso_Part_ag

your 5th part was broken ... download it again and create new DVD iso. You don't have to burn the iso, you can mount it loopback, e.g.

mount -o loop,ro N4S_TestDrive_MaxDB.iso /mnt/loop

and then access installation program via /mnt/loop/install.sh

Thanks,

Hannes

[Former Member · Accepted solution]

Thanks for identifying the corrupted download. I have started the download and after it is complete will follow the steps to install again. This leads me to another question:

How do I cleanup or uninstall the previous installation done with a corrupted download? Appreciate your help in this.

Thanks,

Ashok

[hannes_kuehnemund · Accepted solution]

Well,

good question, I never removed an N4S installation.

I'd guess, that everything the install.sh files does should be revoked. This means

• remove /etc/opt/sdb

• remove /usr/sap

• remove database (/sapdb ?)

• remove service ports

• remove user and groups

If any one in the forum already de-installed an N4S testdrive, your help is appreciated

Thanks,

Hannes

[Former Member · Accepted solution]

I have reinstalled the system and installationi finished without errors.

(I mounted the *.iso file instead of writing to DVD)

I started NW04s with command (after su to n4sadm user) "startsap n4shost".

The database and SAP instance starts succesfully. I tried to run the Javagui

to install the license but run into the same problem even after installing

32 bit jre as indicated in Step 3 post separately.

I shutdown down linux (after proper "stopsap n4shost") and after some time reboot

the system and try to start NW04s but this time DB could not be started. I need

help in solving this issue. I have pasted below screen output both when the system

started successfully right after installation and when it failed when I tried to

start NW04s after linux boot.

-

---

successfull start output----

---

n4shost:n4sadm 51> startsap n4shost

Checking ADA db Database

-

---

ABAP Database is not available via R3trans

Starting SAP-Collector Daemon

-

---

21:08:23 25.05.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 linux-mtl1 started

Running /usr/sap/N4S/SYS/exe/run/startdb

Trying to start database ...

Log file: /home/n4sadm/startdb.log

N4S database started

/usr/sap/N4S/SYS/exe/run/startdb completed successfully

Starting SAP Instance SCS00

-

---

Startup-Log is written to /home/n4sadm/startsap_SCS00.log

Instance Service on host linux-mtl1 started

Instance on host linux-mtl1 started

Starting SAP Instance DVEBMGS01

-

---

Startup-Log is written to /home/n4sadm/startsap_DVEBMGS01.log

Instance Service on host linux-mtl1 started

Instance on host linux-mtl1 started

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

-

---

FAILED to start output -

---

n4shost:n4sadm 57> 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

-

---

22:41:40 25.05.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 linux-mtl1 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 58> cat /home/n4sadm/startdb.log

-

---

Mon May 25 22:41:48 CDT 2009

LOGFILE FOR STARTING DATABASE

Trying to start database ...

-

---

Mon May 25 22:41:48 CDT 2009

Checking required environment variables

SAPSYSTEMNAME is >N4S<

Start database with xuserkey >c<

-

---

Mon May 25 22:41:48 CDT 2009

Connect to the database to check the database state

dbmcli: connect check finished with return code: 0

Database not available

-

---

Mon May 25 22:41:54 CDT 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'

-

---

Mon May 25 22:41:55 CDT 2009

Starting database

Starting Database Instance...

Error! Connection failed to node n4shost for database N4S: cannot connect to server socket

Opening Database...

Error! Connection failed to node n4shost for database N4S: cannot connect to server socket

-

---

Mon May 25 22:42:04 CDT 2009

Connect to the database to verify the database is now open

dbmcli check finished with return code: 0

Database start failed

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

Thanks,

Ashok

[Former Member · Accepted solution]

Any trick to keep the linebreaks intact so that the text does not concatenate as above.

[hannes_kuehnemund · Accepted solution]

> Any trick to keep the linebreaks intact so that the text does not concatenate as above.

Yes, when creating a reply, have a look at the Further Markup Possibilities box on the lower right. There are "code" tags, which prevent the forum to remove spaces. But is looks like, that these tags aren't working any longer when using long replies. I'll check with my colleagues if they are already familiar with this issue.

Anyway, regarding your error, there seem to be problems with your network configuration.

...

Warning: Could not found virtuell host in ifconfig list

This doesn't look good. Could you give the output of

hostname
ifconfig
cat /etc/hosts

I suspect that there is no virtual hostname and ip address for n4shost in your system.

Thanks,

Hannes

[Former Member · Accepted solution]

It is bit strange because right of installation NW04s starts without any problem. I can see the virtual host also running (ifconfig output as eth0:0) right after installation and the server starts without any problem as posted in my previous post of a successfull start.<br />

It is going into this problem only the next time when we start the computer and try to start NW04s. This time even the virtual host does not show in the ifconfig output.<br />

<br />

I am pasting the information as requested

<br />

-

---

hostname output -

---

> linux-mtl1<br />

<br />

-

---

ifconfig output -

---

V<br />

linux-mtl1:~ # ifconfig<br />

eth0 Link encap:Ethernet HWaddr 00:23:5A:29:57:22 <br />

inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0<br />

inet6 addr: fe80::223:5aff:fe29:5722/64 Scope:Link<br />

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br />

RX packets:1590 errors:0 dropped:0 overruns:0 frame:0<br />

TX packets:1870 errors:0 dropped:0 overruns:0 carrier:0<br />

collisions:0 txqueuelen:1000 <br />

RX bytes:1175703 (1.1 Mb) TX bytes:439829 (429.5 Kb)<br />

Interrupt:251 Base address:0x6000 <br />

<br />

lo Link encap:Local Loopback <br />

inet addr:127.0.0.1 Mask:255.0.0.0<br />

inet6 addr: ::1/128 Scope:Host<br />

UP LOOPBACK RUNNING MTU:16436 Metric:1<br />

RX packets:6 errors:0 dropped:0 overruns:0 frame:0<br />

TX packets:6 errors:0 dropped:0 overruns:0 carrier:0<br />

collisions:0 txqueuelen:0 <br />

RX bytes:340 (340.0 b) TX bytes:340 (340.0 b)<br />

<br />

wlan0 Link encap:Ethernet HWaddr 00:24:2B:7B:A9:FE <br />

UP BROADCAST MULTICAST MTU:1500 Metric:1<br />

RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br />

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br />

collisions:0 txqueuelen:1000 <br />

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)<br />

<br />

wmaster0 Link encap:UNSPEC HWaddr 00-24-2B-7B-A9-FE-00-00-00-00-00-00-00-00-00-00 <br />

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br />

RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br />

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br />

collisions:0 txqueuelen:1000 <br />

RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)<br />

<br />

-

---

etc/hosts file content below (observed thatevery reinstalltion appends a new virtual host line at the end<br />

linux-mtl1:~ # cat /etc/hosts<br />

#<br />

1. hosts This file describes a number of hostname-to-address<br />

2. mappings for the TCP/IP subsystem. It is mostly<br />

3. used at boot time, when no name servers are running.<br />

4. On small systems, this file can be used instead of a<br />

5. "named" name server.<br />

6. Syntax:<br />

7. <br />

8. IP-Address Full-Qualified-Hostname Short-Hostname<br />

#<br />

<br />

127.0.0.1 localhost<br />

198.168.1.100 linux-mtl1.mymach.org linux-mtl1<br />

<br />

1. special IPv6 addresses<br />

::1 localhost ipv6-localhost ipv6-loopback<br />

<br />

fe00::0 ipv6-localnet<br />

<br />

ff00::0 ipv6-mcastprefix<br />

ff02::1 ipv6-allnodes<br />

ff02::2 ipv6-allrouters<br />

ff02::3 ipv6-allhosts<br />

<br />

192.168.155.1 n4shost<br />

192.168.155.1 n4shost<br />

-

---

<br />

<br />

Thanks,<br />

Ashok<br />

This time I manually added html tag for new line "br" at every line break so readability is preserved. Let me know if it is still concatenated when you view at your end.

[hannes_kuehnemund · Accepted solution]

Dear Ashok,

the N4S installation creates a new interface, eth0:0 with an IP address that is listed in the /etc/hosts file. It looks like that your network scripts simply restore the original network settings which prevent a successful SAP startup after a reboot.

I'd suggest that you try to create the eth0:0 device manually. As root user call

ifconfig eth0:0 192.168.155.1 up

and then try to start the SAP system as n4sadm.

Thanks,

Hannes

[Former Member · Accepted solution]

Dear Hannes,

As you suggested manually starting the virtual host solved the problem and NW04s jumps to life almost instantaneously. Later I will try to figure out why this is not getting started automatically even though it is listed in hosts file, but now I will move on to Step 3 and try to install the license.

Thanks for your help.

Ashok

[Former Member]

and licensy key file is delievered in text file, not in .rpm format

you have to install it using saplicense utility from os level, if sap not up yet

[Former Member]

Kindly briefly tell me hHow to install the license from OS level?

[Former Member]

Hi Ashok

Refer the links, and their sublinks too

http://help.sap.com/saphelp_nw04/Helpdata/EN/1a/6cd7c6e8a111d18d970000e816c2ff/content.htm

http://help.sap.com/saphelp_nw04/Helpdata/EN/a7/512c88407a11d1893b0000e8323c4f/content.htm

Edited by: Bhudev on May 23, 2009 9:45 PM

[Former Member]

Thanks for the help

I used the following command to install the license from the file

/usr/sap/N4S/SYS/exe/run/saplicense -install ifile=N4S.txt

after about 20 mins I get the following error

• SAPLICENSE (Release 700) ERROR ***

ERROR: Connect to database failed

DETAILS: DbSlConnect failed with return code 99

SQL-ERROR -10709 (check DB manual for explanation)

-

---

It seems I need to have DB up and running first even to do OS level lilcense installation.

My DB installation had some "tar" extraction errors as shown below

-

---

unpacking /media/D50077574/server/TAR/x86_64/SAPDB_II.tar.bz2

bzip2: Data integrity error when decompressing.

Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.

You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover

data from undamaged sections of corrupted files.

-

---

Is there a way to indentify which of the 7 *.iso files in SDN download might contain this SAPDB_II.tar.bz2 file so that I can download only those files and try reinstall again with the assumption the corruption happened during the download process.

[Former Member]

I am really not sure for this info, may be our other members should help us here