KNLDIAGERR file error

[Former Member]

We recently made a copy of one Livecache DB (LCC) and used it to build another LC DB instance (LCO). After which we got Livecache started and everything apeard to be good. We have since seen the following error in the knldiag log:

2006-10-26 09:29:29 128 ERR 11865 DCOM dlapi(dlopen) Error:ld.so.1: kernel: fatal: /sapdb/LCC/db/sap/libSAPAPO.so: open failed: No such file or directory

2006-10-26 09:29:29 128 ERR 11258 DCOM-DMP LVC_LoadLibrary - File: /sapdb/LCC/db/sap/libSAPAPO err: ld.so.1: kernel: fatal: /sapdb/LCC/db/sap/libSAPAPO.so: open fai

2006-10-26 09:29:29 128 ERR 11262 DCOM dispGetClassObject - HRESULT: 2, Context: INPROC

2006-10-26 09:29:29 128 ERR 11263 DCOM COCLSID: {3E51F8E4-549D-11D3-87F9-00104BB4099E}

2006-10-26 09:29:29 128 ERR 51260 HRESULT 00000002 dcom_hresult

The issue, I believe is it is trying to load from an incorrect path as stated in the error "/sapdb/LCC" when it shoudl be "/sapdb/LCO".

I've checked env files and such adn can't find anything referencing the old (source) name LCC. We did find that the install path was incorrect, so I ran a dbmcli command to correct that.

Any ideas on where it may be reading this path from?

[Former Member · Accepted solution]

Here is teh info you requested:

c5f1n4:lcoadm> dbmcli -s inst_enum

OK

7.5.0.35 /sapdb/LCO/db

c5f1n4:lcoadm> dbmcli -s db_enum

OK

LCO /sapdb/LCO/db 7.5.0.35 fast running

LCO /sapdb/LCO/db 7.5.0.35 quick offline

LCO /sapdb/LCO/db 7.5.0.35 slow offline

c5f1n4:lcoadm> sdbregview -l

PCR 7301 /sapdb/programs 7.3.01.20 valid

PCR 7500 /sapdb/programs 7.5.00.35 64 bit valid

JDBC /sapdb/programs 7.6.00.20 valid

PCR 7403 /sapdb/programs 7.4.03.42 64 bit valid

Server Utilities /sapdb/programs 7.5.00.35 64 bit valid

Database Kernel /opt/sdb/7500 7.5.00.35 64 bit valid

Loader /sapdb/programs 7.5.00.35 64 bit valid

ODBC /sapdb/programs 7.5.00.35 64 bit valid

Base /sapdb/programs 7.5.00.35 64 bit valid

DB Analyzer /sapdb/programs 7.5.00.35 64 bit valid

PCR 7300 /sapdb/programs 7.3.00.55 valid

APO LC APPS /opt/sdb/7500/sap 4.10.012 64 bit valid

c5f1n4:lcoadm> c5f1n4:lcoadm> uname -a

SunOS c5f1n4 5.10 Generic_118822-27 sun4u sparc SUNW,Sun-Fire-15000

c5f1n4:lcoadm>

LCOADM is the user that started x_server. I'll look at the note.

[former_member229109 · Accepted solution]

'sdbregview' shows :

Database Kernel /opt/sdb/7500 7.5.00.35 64 bit valid

APO LC APPS /opt/sdb/7500/sap 4.10.012 64 bit valid

-> Where do you have database software installed on this server?

-> Check the results of 'sdbverify', run it as root user.

< SAP note 546737. >

-> Please review SAP Note No. 604680 "Renaming a SAP DB or liveCache instance"

-> Please update with the following information:

-> Output of the following commands on the target server:

uname -a

ls -l /opt/sdb/7500

ls -l /sapdb/LCO/db

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Ahhh, the database software should be in /sapdb/....

info you requested

c5f1n4:lcoadm> uname -a

SunOS c5f1n4 5.10 Generic_118822-27 sun4u sparc SUNW,Sun-Fire-15000

c5f1n4:lcoadm> ls -l /opt/sdb/7500

/opt/sdb/7500: No such file or directory

c5f1n4:lcoadm> ls -l /sapdb/LCO/db

total 80

dr-xr-xr-x 2 sdblco sdb_np 8192 Oct 18 16:33 bin

dr-xr-xr-x 2 sdblco sdb_np 96 Oct 18 16:33 demo

dr-xr-xr-x 3 sdblco sdb_np 96 Oct 18 16:33 doc

dr-xr-xr-x 3 sdblco sdb_np 8192 Oct 18 16:33 env

dr-xr-xr-x 2 sdblco sdb_np 96 Oct 18 16:33 etc

dr-xr-xr-x 4 sdblco sdb_np 96 Oct 18 16:33 lib

dr-xr-xr-x 4 sdblco sdb_np 8192 Oct 18 16:33 misc

dr-xr-xr-x 3 sdblco sdb_np 8192 Oct 18 16:33 pgm

dr-xr-xr-x 2 sdblco sdb_np 8192 Oct 18 16:33 sap

sdbverify outputs that the:

APO LC APPS 4.10.012 64 bit in /opt/sdb/7500/sap

-

---

check files... failed

/opt/sdb/7500/sap/libSAPREP.lst not found

/opt/sdb/7500/sap/libaps_base.so not found

/opt/sdb/7500/sap/libaps_peg.so not found

/opt/sdb/7500/sap/libSAPAPO.so not found

/opt/sdb/7500/sap/libSAPSIM.so not found

/opt/sdb/7500/sap/libSAPTS.so not found

etc....

It seems the install is all messed up. Do I need to re-do the install and start the recovery over or is there a way to correct where it's pointing for these directories? Thanks very much for your help!

[former_member229109 · Accepted solution]

1)The problem should no longer occur with the following versions even if

the LD_LIBRRARY_PATH_64 environment variable is set:

MaxDB 7.5.00 Build 23 or higher

< SAP note 801074 >

And according your information you have - 7.5.0.35 .

2)Please update with the following information:

Output of the following commands on the target server:

ls -l /sapdb/data/config

-> How many incorrect dabase packages reported by 'sdbverify'?

-> Did you copy the database software to the target server?

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

More info for you:

c5f1n4:lcoadm> ls -l /sapdb/data/config

total 272

-rw-rw---- 1 sdblco sdb_np 54 Oct 25 15:52 Databases.ini

-rw-rw---- 1 lcoadm sapsys 54 Oct 25 15:39 Databases.ini_orig

-rrr-- 1 sdblco sdb_np 40 Oct 25 15:52 Installations.ini

-rw-rw---- 1 sdblco sdb_np 7582 Oct 25 15:53 LCO

-rr--- 1 sdblco sdb_np 7582 Oct 19 10:58 LCO.01

-rw-rw---- 1 sdblco sdb_np 4830 Oct 25 15:59 LCO.cfg

-rw-rw---- 1 sdblco sdb_np 836 Oct 20 05:05 LCO.mmm

-rw-rw---- 1 sdblco sdb_np 51145 Oct 18 23:29 LCO.pah

-rw-rw---- 1 sdblco sdb_np 2560 Oct 24 14:48 LCO.upc

-rrr-- 1 sdblco sdb_np 48 Oct 18 16:33 Runtimes.ini

drwxr-xr-x 2 sdblco sdb_np 8192 Oct 18 16:32 install

also, here's the verify:

VERIFICATION SUMMARY:

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

INVALID PACKAGES: 0

VALID PACKAGES: 12

INCONSISTENT PACKAGES: 4

TOTAL FILES: 324

MISSED FILES: 188

MODIFIED FILES: 1

FILES WITH MODIFIED PERMISSIONS: 0

Originally I believe the db software was copied; however, I did a re-install as the software did not look complete (I didn't do the original copy). The install seemed successful and I was sure I gave the correct paths during install.

[Former Member · Accepted solution]

I just noticed, one of my colleagues renamed the directory

c5f1n4:lcoadm> pwd

/opt/sdb/7500_old

c5f1n4:lcoadm>

Sorry, that probably threw you off. This is the /opt/sdb/7500 that the system is referring to.

[former_member229109 · Accepted solution]

1) According the information from the sdbverify you

need to fix the incorrect installed database software on the

target server. Please run as root user:

Cd /sapdb/programs/bin

./sdbverify > check.txt

=> send me by e_mail the check.txt file.

-> Did you download the 41 .12 PL 002 + 7.5.00.35 package, SAP note 951555,

From the Market place?

-> Did you create the OSS message on this issue?

2)

"

We recently made a copy of one Livecache DB (LCC) and used

it to build another LC DB instance (LCO).

"

Please give more details on how did you do that.

Did you follow the recommended SAP notes 457425 & 877203?

Could you please reload system tables:

dbmcli -d LCO -u control,control load_systab -u superdba,<password>

< default password of the superdba user is admin >

From the APO system connected to the target liveCache instance:

-> Did you setup LCA connection correctly?

If the LCA connection was changed & pointed now to the target

liveCache instance => did you restart the application after

the LCA connection changed?

-> run LCApps register in LC10 -> liveCache:Administration ->

Operating

==> send me the knldiag,knldiag.err, dbm.prt & lcinit.log files

after that.

Thank you & best regards, Natalia Khlopina

Message was edited by: Natalia Khlopina

[Former Member · Accepted solution]

I sent you the file as you requested.

I did download the 41 .12 PL 002 + 7.5.00.35 package.

I get an error loading that table -

c5f1n4:lcoadm> dbmcli -d LCO -u control,control load_systab -u superdba,admin

ERR

-24908,ERR_DOMPUNKNOWN: DOMAIN password unknown

It lets me login to DBM GUI with superdba/admin so I'm pretty sure this is correct. Why the error?

The new LC instance has been restarted.

When I try to register the app I get the same error regarding DOMAIN. IS this user necessary? It seems we have sevral users defined as DBA for this instance (DOMAIN, SAPLCO, SYS) I'd liek to delete them all except SAPLCO, but it won't let me delete.

[former_member229109 · Accepted solution]

1) I got check.txt by e-mail.

-> Did you create the OSS message on this issue?

Please let me know ( as root 😞

ls -l /sapdb/programs/pgm/starter

ls -l /sapdb/programs/bin

ls -l /sapdb/programs/bin/starter

2)

I didn't get the knldiag,knldiag.err, dbm.prt & lcinit.log files from you.

->"c5f1n4:lcoadm> dbmcli -d LCO -u control,control load_systab -u superdba,admin

ERR

-24908,ERR_DOMPUNKNOWN: DOMAIN password unknown

"

==> Please run

dbmcli -d LCO -u control,control load_systab -u superdba,admin -ud domain

->"When I try to register the app I get the same error regarding DOMAIN. IS this user necessary? It seems we have sevral users defined as DBA for this instance (DOMAIN, SAPLCO, SYS) I'd liek to delete them all except SAPLCO, but it won't let me delete.

"

==> Please don't do that.

More information about database users please see at::

&

Please review the Definition, list of the properties, Authorization

Concept and more for the Database User & Database System Administrator

(SYSDBA User) at http://dev.mysql.com/doc/maxdb

MAXDB library -> Basic Information -> Concepts of the Database System

-> Administration -> Users, Authentication and Authorizations

Thank you & best regards, Natalia Khlopina

[Former Member · Accepted solution]

Natalia, I was able to resolve my issue. Once I saw that certain programs were installed incorrectly I uninstalled them and re-installed. Here is a re-cap of what I did:

We ran the inst_unreg /opt/sdb/7500 command to unregister the incorrect install path. Then we ran inst_reg /sapdb/LCO/db to register the correct install path. Now the Install Path shows correctly. This still didn't fix the issue, dunps still occur and the KN LDIAGERR og still has the error in it. Incidentally, make sure the app is stopped before doing this.

Running sdbregview -l showed

PCR 7301 /sapdb/programs 7.3.01.20 valid

PCR 7500 /sapdb/programs 7.5.00.35 64 bit valid

JDBC /sapdb/programs 7.6.00.20 valid

PCR 7403 /sapdb/programs 7.4.03.42 64 bit valid

Server Utilities /sapdb/programs 7.5.00.35 64 bit valid

<b>Database Kernel /opt/sdb/7500 7.5.00.35 64 bit valid</b>

Loader /sapdb/programs 7.5.00.35 64 bit valid

ODBC /sapdb/programs 7.5.00.35 64 bit valid

Base /sapdb/programs 7.5.00.35 64 bit valid

DB Analyzer /sapdb/programs 7.5.00.35 64 bit valid

PCR 7300 /sapdb/programs 7.3.00.55 valid

<b>APO LC APPS /opt/sdb/7500/sap 4.10.012 64 bit valid</b>

c5f1n4:lcoadm> c5f1n4:lcoadm> uname -a

SunOS c5f1n4 5.10 Generic_118822-27 sun4u sparc SUNW,Sun-Fire-15000

c5f1n4:lcoadm>

The bold entries have incorrect paths, so Otto and I did the following:

We stopped LC and x-server.

Ran the sdbuninst -l to show the install programs (shows the same things as above) however, there were two entries for Database Kernel and APO LC Apps , one entry with the correct path and one without.

We did an uninstall on them by running sdbuninst -package "Database Kernel" -autoresolve. This brings up a menu of choices to select what to uninstall (I think it just listed two options all and kernel). I chose kernel and the next screen confirmed that it would remove kernel and APO LC Apps.

At this point we ran the sdbinst program. We selected all as we were unsure of what other option to choose. This proved to be the best choice as it checks everything and installs what it needs. It installed the kernel and APO LC apps and skipped the other pieces.

Running sdbregview -l shows

PCR 7301 /sapdb/programs 7.3.01.20 valid

PCR 7500 /sapdb/programs 7.5.00.35 64 bit valid

JDBC /sapdb/programs 7.6.00.20 valid

PCR 7403 /sapdb/programs 7.4.03.42 64 bit valid

Server Utilities /sapdb/programs 7.5.00.35 64 bit valid

Database Kernel /sapdb/LCO/db 7.5.00.35 64 bit valid

Loader /sapdb/programs 7.5.00.35 64 bit valid

ODBC /sapdb/programs 7.5.00.35 64 bit valid

Base /sapdb/programs 7.5.00.35 64 bit valid

DB Analyzer /sapdb/programs 7.5.00.35 64 bit valid

PCR 7300 /sapdb/programs 7.3.00.55 valid

APO LC APPS /sapdb/LCO/db/sap 4.10.012 64 bit valid

c5f1n4:lcoadm>

We started x_server and took the LC into Admin mode. All looked good. Tried starting LC and it took a long time. Once it came up I tried to force an error into the KNLDIAGERR log by executing /n/sapapo/om13 again. It still showed the error (same as first one above). I then tried to re-register the LC in LC10 and got an error:

ERR

-24908,ERR_DOMPUNKNOWN: DOMAIN password unknown

I tried executing this at the OS level - c5f1n4:lcoadm> dbmcli -d LCO -u control,control load_systab -u superdba,admin and got the same thing. I then tried this - dbmcli -d LCO -u control,control load_systab -u superdba,admin -ud domain and was able to load it successfully:

dbmcli on LCO>load_systab -u superdba,admin -ud domain

OK

0,OK: everything works fine

0,/sapdb/LCO/db/bin/x_python /sapdb/LCO/db/env/lsystab.py -R /sapdb/LCO/db -d LCO -u superdba,*

Removing obsolete objects

Installing Loader tables

Installing messages and help

Installing SYSDBA tables

Installing comments for SYSDBA tables

Installing precompiler tables

Installing system tables for R3 backup information

Installing ODBC and JDBC tables

Installing system tables for ORACLE (V7) mode

Installing data dictionary tables and views

Installing synonyms for oracle system tables

Installing comments on oracle sytem tables

Installing tables for SQL Studio

Installing suppose list

Installing tables for WebAgent

Installing tables for WebDAV

Installing tables for WebDAV XML Indexing

Installing DOMAIN tables

Installing comments for DOMAIN tables

Installing Views as replacement for SHOWs

Installing Database Manager tables

Installing SYSINFO tables

Installing comments for SYSINFO tables

==================================

Installation successfully finished

==================================

Then I tried to re-register the LC again inside LC10 and got a successful load. I bounced the LC and now when I run /n/sapapo/om13 all is good (no dumps). I also had the functional team validate and so far there are no problems.

Thanks for your help and showing me how to use some info gathering commands, it helped me figure it out!

Message was edited by: Doyle Tipler

[former_member229109]

Hello Doyle,

Please update with the following information:

-> Output of the following commands on the target server:

dbmcli -s inst_enum

dbmcli -s db_enum

sdbregview -l

uname -a

-> Check the results of 'sdbverify', run it as root user.

< SAP note 546737. >

-> What user started the x_server?< check in xserver protockol>

-> Check in the knldiag file, if the variable LD_LIBRARY_PATH_64

listed under the OS user env. Settings.

-> Please review the SAP note 675504

-> Please review SAP Note No. 604680 "Renaming a SAP DB or liveCache instance"

Thank you and best regards, Natalia Khlopina

Message was edited by: Natalia Khlopina