WAS Installation problem

[Former Member]

Hello Everybody,

I have a problem installing WAS SP9. On the 5th step of installation i.e. "MAXDB installation". It stuck up, and didn't go ahead. It utilizes 100% memory of the cpu. We didn't get any information in view log also.

This maxdb installation steps continued upto 4 hours. Then we have stopped the installation.

What could be the reason behind this?

Anybody faced same error?

Regards,

Bhavik Devisha

[Former Member · Accepted solution]

Hi Bhavik,

What is the RAM size you are having. The installation stops like this when the minimum hardware requiement is not met.

Best Regards,

Naresh

[Former Member · Accepted solution]

Hi Naresh,

Thanks for your reply.

We have install 1.5 GB of RAM.

I don't think that is an issue because we were successfull in installing WAS on system with same configration.

[roland_mallmann · Accepted solution]

Hi,

can you check if there's a knldiag.err file written in the Rundirectory (/sapdb/data/wrk/<sid> on Unix or <drive>:\sapdb\data\wrk\<sid> on Windows system) of the MaxDB database?

If you see this file, please show me the last twenty or so lines from this file.

Please also take a look at the knldiag file (if there is one), in the same directory. In that file, please look for the line containing 'current' and show me the 20 lines or so above that.

You might have had a LOG Full situation, which you could easily identify using the Database Manager GUI, should you have this installed.

On the other hand, you might also have a problem with the database sioftware installation (as opposed to the creation of the db instance). In that case, look in the XCMDOUT.LOG file in your installation directory.

Kind regards,

Roland

Ii might be so that

[Former Member · Accepted solution]

Hi Roland,

Yes, knldiag.err file is created in directory <drive>:\sapdb\data\wrk\<sid>.

Content of this file is:

-

---

Date Time TID(hex) Typ MsgID Label Message-Text

-

---

2005-09-09 16:55:42 --- Starting GMT 2005-09-09 16:55:42 7.5.0 Build 018-123-079-776

Yes there is another file named, "knldiag".

Content in this file is given below as you suggested.

Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 18:45:49 0xF84 19651 CONNECT Connection released, T19

2005-09-09 18:51:50 0xF84 19633 CONNECT Connect req. (T19, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 18:51:50 0xF84 19651 CONNECT Connection released, T19

2005-09-09 18:51:50 0xF84 19633 CONNECT Connect req. (T19, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 18:51:51 0xF84 19651 CONNECT Connection released, T19

2005-09-09 18:51:51 0xF84 19633 CONNECT Connect req. (T19, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 18:51:51 0xF84 19651 CONNECT Connection released, T19

2005-09-09 18:51:51 0xF84 19633 CONNECT Connect req. (T19, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:06:25 0xF84 19651 CONNECT Connection released, T22

2005-09-09 19:06:25 0xF84 19651 CONNECT Connection released, T19

2005-09-09 19:10:52 0xF84 19633 CONNECT Connect req. (T19, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:10:52 0xF84 19633 CONNECT Connect req. (T20, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:10:52 0xF84 19651 CONNECT Connection released, T20

2005-09-09 19:10:52 0xF84 19633 CONNECT Connect req. (T20, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:10:52 0xF84 19651 CONNECT Connection released, T20

2005-09-09 19:10:52 0xF84 19633 CONNECT Connect req. (T20, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:10:52 0xF84 19651 CONNECT Connection released, T20

2005-09-09 19:11:19 0xF84 19633 CONNECT Connect req. (T20, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:11:19 0xF84 19651 CONNECT Connection released, T20

2005-09-09 19:11:19 0xF84 19633 CONNECT Connect req. (T20, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:11:19 0xF84 19651 CONNECT Connection released, T20

2005-09-09 19:11:19 0xF84 19633 CONNECT Connect req. (T20, Node:'SGH439062R.inttc.chevrontexaco.net', PID:0)

2005-09-09 19:11:19 0xF84 19651 CONNECT Connection released, T20

2005-09-09 19:21:25 0xF84 19651 CONNECT Connection released, T19

You are right I got lots of statements in this file like,

"LOG FULL: task 16 suspended

Log is full."

What i need to solve this problem?

Regards,

Bhavik

[roland_mallmann · Accepted solution]

Hi,

in order to free up log space, you need to make a LOG BACKUP. But in order to make a first log backup, you have to start the backuphistory with a full DATA BACKUP.

Afterwards, you can also switch on the automatic saving of the log.

The above is most conveniently done using the Database Manager GUI*.

I'll list the steps to be done:

a.] creating backup media

1. create a (full/complete) data backup medium

2. create a log backup medium for normal Log backups

3. create a separate log backup medium for automatic log saving**

b.] backing up data & log

1. start the complete data backup, specify the medium you just created under a1.

2. after the above, you can start a log backup using the medium from a2

3. after the above step, you can now switch on the automatic log saving, specify the medium from a3.

*: Database Manager GUI available from http://dev.mysql.com/doc/maxdb/tools.html

**: Please note that the automatic log saving can amount in quite a lot of backups, which can fill a file system quite quickly, ofcourse dependent on how much log is produced.

Hope the above helps you. Please let me know if you need more details on the above, but the GUI should prove to be quite helpful.

Kind regards,

Roland

Message was edited by: Roland Mallmann

Message was edited by: Roland Mallmann

[Former Member · Accepted solution]

Hi Roland,

I guess this all related to Database. But, while installing WAs server, i won't have database installed on my system. So, how can we do in that case when installation is going on.

Can we do this two things symaltaneously?

Anyway we got success in intalling server after changing DB size to 500MB and this problem is resolved.

But, we want to know what it is all about?

I am new to "Database Manager GUI". Idon't know anything about it. So, if you can tell me in detail then it would be very helpful to us.

Regards,

Bhavik

[roland_mallmann · Accepted solution]

Hi Bhavik,

well, if you receive LOG FULL messages in the knldiag file, you already have a working DB instance.

You could then perform the steps provided in my last answer, the installation should continue after the log was saved.

You can find more information about the Database Manager GUI in the link I gave you. The 'more details' I wanted to provide you with, was meant for a situation in which you needed to perform the steps I wrote, but was unable to do so. But now I see the problem's been resolved.

Nevertheless, your log could still get full, the steps should help you take care of that situation. Please read the information on the link.

Kind regards,

Roland

[Former Member]

Hi Bhavik,

If you have earlier installed a lower version of WAS on the same machine then you need to uninstall it and remove the registry entries for sapdb/maxdb. Doing this might help.

Cheers,

Sanjeev

[Former Member]

Hi Sanjeev,

thanks for your reply.

I am installing WAS server on new system first time. So, no need to to clear registry values.

Regards,

Bhavik