SAP-suggested "work-around" not a true solution ...

[Former Member]

Hello all,

When logging in, I get a DOTKL access error (because the table is clustered). Earlier, I used note 1054467 to solve a problem and then set

rdisp/tolerate_loopback_addr to true.

I got past the problem but still ran into others later on.

Because DOTKL is a cluster table, According to the note above, the "work-around" does not work if you are accessing clustered tables. Because of the error message above, one CANNOT log into the system - AT ALL.

Question: is there another way around this? A "work around" that will allow you to log into the system? It seems that /dev/eth0 is requred to be defined and - unfortunately - this will not be possible.

Will a wireless connection allow one to get round the problem?

Any help, hints or advice is appreciated ..

TIA

Edited by: Casey Harris on Aug 24, 2008 6:37 PM

[Former Member]

Found answer on another board ..

Edited by: Casey Harris on Sep 1, 2008 3:53 PM

[markus_doehr2]

The "solution" is to use a supported network infrastructure. The system must be able to resolve its IP addresse not pointing to "localhost".

It´s very unlikely, that the network is responsible for an access (or not access) of a (clustered) table, I´m pretty sure there were other things preventing the access and the change in the instance profile and the following reboot "solved" the problem temporarily.

You could try to enter the hostname in /etc/hosts and give a whatever IP which is not defined as "local" (so a non-127.x IP.

Markus

[Former Member]

Markus - thanks for the response

The thing is that one requires a working ethernet connection (or perhaps some kind of connection - wireless or what not) so that the loopback address 127.0.0.1 is not used.

From what I have seen, you cannot define an arbitrary IP address for a machine unless there is some kind of device in the machine (/dev/eth0 for example). In YAST2, one can assign arbitray IP addresses BUT, there must be some kind of device out there available to use (again, like eth0) - please see this for yourself.

The current problem is that the ethernet card is not being recognized by the OS (but is recognized by the BIOS) - a driver is needed. So, the search goes on for a driver to apply to the OS - or - to see if one can purchase a new ethernet card that is supported by every OS out there - and install that in a free PCI slot.

Until either is done, for all intensive purposes, the machine does not have an ethernet card/access at this time (leaving only the loopback address accessible for use). In other words, if you get the following when typing these commands (when only having one ethernet device on the system):

--> ifup eth0

Interface eth0 is not available

--> ifdown eth0

Interface eth0 is not available

--> ifconfig -a

just shows the loopback address (lo) - nothting for eth0 (or any other ethernet card)

then, there is nothing that YAST2 has access to to assign an arbitrary IP address (like 192.168.x.x).

If YAST2 cannot assign an arbitrary IP address (like 192.168.x.x), then the only thing left is 127.0.0.1 (which just uses the TCP/IP stack - so I hear) and cannot be changed for the loopback address (lo).

If only the loopback address available, then the hostname of the machine cannot be assigned to anything like 192.168.x.x

So, when installing SAP on such a machine, the clustered tables are not available.

The system will come up, you can use the SAPGui to get to the login screen for the SID but when attempting to log in, this will not work as the login accesses clustered table DOKTL from-the-jump.

If you can't access the clustered tables, you cannot log in.

If you cannot log in, you can't use the system.

All of this because (seemingly) there is no ethernet device on the system. The initial thought was to make this a stand-alone system, test it, and then eventually integrate it to the internet for access. But - it seems that this approach will not be possible.

Edited by: Casey Harris on Aug 25, 2008 4:22 PM

[markus_doehr2]

I wonder what you will do with a SAP system without network access... I leave that up to you

What kind of dump do you get when you access that table?

Markus

[Former Member]

Well, the idea was to work on getting the system up and going and then configure the cards/network to attach it to the internet later on. You know - a stand alone system that really stands alone?

Anywho, I was looking for a SAP software solution - but - you can see what I have been going through here. I put the link below to conserve bandwidth

http://forums.nvidia.com/index.php?act=ST&f=25&t=75858&st=0#entry430901

Oh BTW, I was wrong - the ethernet interface is part of the NVIDIA chipset. It is not standing by itself alone ..

Casey

Edited by: Casey Harris on Aug 25, 2008 5:38 PM

[markus_doehr2]

Well - I was asking for the SAP problem - not your hardware problem (the "DOKTL-thing")

Anyhow:

- OpenSUSE ist not supported (it's missing some (more or less important) parts in the kernel)

- Your hardware doesn't seem to be supported...

Seems that machine was built for Windows-only proprietary drivers...

Markus

[Former Member]

Well, my problem is basically the same as this guy's:

In it, it says:

_______________________________________________

This error occurs only when you run the system on a PC without a network connection. To solve this problem, install the MS Loopback Adapter as described on the first CD.

_______________________________________________

Of course, I have Linux (Suse) so the MS Loopback will not work in this case.

He also could not log into his system because of the DOTKL (clustered table) error. This goes back to my initial point: Sure one, can set rdisp/tolerate_loopback_addr so that a box without network connection will work, but in the end, it is not a solution because the person cannot log in (because of the "DOTKL-thing").

Anywho, I think I will resort to sacrificing one of the free PCI ports on the machine for an ethernet card that is recognized by the OS.I understand the point regarding a supported OS being used (as well as a supported machine) but I am using a machine from HP (64-bit) that was just recently purchased (a few weeks ago). As mentioned before, the only reason why I was using this OS is because SLES 10 did not have the drivers for the USB disks, the ethernet interfaces, or even the CD 😐

I don't think this particular problem has anything to do with the machine being used or the OS at this time. The same problem would happen whether or not the OS/machine was "official".

But ...

If you have an SAP solution around this problem, I would be all ears (or in this case eyes).

Edited by: Casey Harris on Aug 26, 2008 4:19 PM

[markus_doehr2]

> In it, it says:

So you have the "verify own hostname" problem? The DBIF* is just a general error message saying that some error in the DataBaseInterFace went wrong.

I still doubt, that this problem is caused by a missing loopback adapter (I may be wrong though) since you have it (you have lo0 - which is exactly that - the loopback adapter).

Markus

[Former Member]

Well, trying something new now to see if I can get around the problem. Druken Sie bitte mir die Daumen 😐

It seems that there is a something to fix the problem for systems installed on Microsoft. But, there seems to be no "Loopback Adapter" solution for any UNIX systems that are in the same boat

[Former Member]

Building/installing new kernel (old : 2.6.22 to new: 2.6.26.3) worked. The ethernet card was recognized (even though modprobe had to be ran to run the forcedeth driver) and I was able to assign 192.168.x.x to it and was able to continue with the installation. The ABAP part is totally complete - I can log in with no problem - no DOTKL errors.

The JAVA installation ran out of space on the hard disk but that is another issue ...