I see. Well, there's really no need for a "script" per se, unless you need to set special environment variables. For example,
under certain versions of linux, you would set the env. variable "LD_KERNEL_ASSUME" prior to starting x_server.
As for starting/stopping x_server, you just do it with the command(as root): ./x_server start or ./x_server stop
The x_server automatically changes the userid of its process to whoever the MaxDB installation owner is. (again, check the file /etc/opt/sdb to find out)
You can verify this with: ps auxww | grep server (to see all of the servers)
This user's account should also be locked (done with passwd -l <sdbowner>)
So you say you get no error if you run start it as root?
JLS
Pius, Edward wrote:
Hello John,
Thanks for taking the time to respond.
Let me try to explain what I had been trying to do. All this KNLDIAGERR started when I tried to delete a table which I created in the SQLStudio. I got the following message "General error;-7500 POS(1) DCOM RESULT:." in the SQLStudio. When I went into the KNLDIAGERR, I found the other messages.
In the mean time I tried to start the x_server on the Solaris machine with root as the user. When I try to do this, there does not appear to have any problem at all. In the instances when I had the errors occurring, I started the x_server using an id which is not root. I think it maybe related to the user-ids with which I am starting the x_server.
Anyway, do you have any idea under which id the x_server must be started. I think the problem maybe related to the PATH.
Lastly, if you have any scripts or links to start and stop the x_server for Solaris, I would really appreciate it.
Again, thanks for your help.
Edward Pius
-----Original Message-----
From: John L. Singleton [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 13, 2004 3:40 PM
To: Pius, Edward
Cc: [EMAIL PROTECTED]
Subject: Re: FW: KNLDIAGERR
Edward,
I'm new to this thread, but --- have you checked to see if those files exist? Have you looked at the permissions?
I propose a few ideas, though I don't know how successful you will find them:
1. What's failing here is a call do dlopen(3) (see "man dlopen") you should check:
a) that the file exists
b) that the MaxDB process has access to that file
2. If step one failed, you may consider these two options: (I am not looking at the code saying this, just an educated guess)
a) If the the code is calling an absolute path, based off of your registry entries for MaxDB, then any inconsistencies would cause it to fail.
Try first locating the file "dbpinstall.so" and then look in the file /etc/opt/sdb:
uber:/# cat /etc/opt/sdb
[Globals]
IndepData=/var/opt/sdb/data
IndepPrograms=/opt/sdb/programs
SdbOwner=sdb
SdbGroup=sdba
uber:/#
Make sure your MaxDB install actually resides in those directories.
For reference, here's what that file looks like on my system:
-r-xr-x--- 1 sdb sdba 98826 Jan 9 18:52 /opt/sdb/7500/lib/dbpinstall.so
b) If the file does exist, and you've tried the above items, then consider this: what is the path to the file MaxDB is trying to load? To find
this out, you can use programs like *truss*, or *strace*---they will give you ALL of this information. Just attach them to the kernel process and grep for dbpinstall.so.
c) As a last ditch attempt you might try adding the path to dbpinstall.so to your linker's search path. Under Linux you can do this by adding the directory the .so file is in, then re-running ldconfig. Though again, I'm not sure if MaxDB absolutely or relatively resolves the path to the .so file --- your mileage may vary.
I hope something here helps --- again, sorry I can't be of more help. If you could perhaps give me your truss/strace output, and let me know what the steps above tell you, perhaps I can help more.
Cheers, JLS Pius, Edward wrote:
Hello SAP folks,
Could you please let me know if there is a solution to this problem?
In appreciation,
Edward Pius
-----Original Message----- From: Pius, Edward [mailto:[EMAIL PROTECTED] Sent: Monday, April 12, 2004 8:38 AM To: [EMAIL PROTECTED] Subject: KNLDIAGERR
Hello,
I am having this error in my KNLDIAGERR file.
2004-04-12 09:02:29 18 ERR 11865 DCOM dlapi(dlopen) Error:ld.so.1:
/opt/oltp/sdb/7500/pgm/kernel: fatal: dbpinstall.so: open failed: No such file or directory
2004-04-12 09:02:29 18 ERR 11258 DCOM-DMP LVC_LoadLibrary - File: dbpinstall
err: ld.so.1: /opt/oltp/sdb/7500/pgm/kernel: fatal: dbpinstall.so: op
2004-04-12 09:02:29 18 ERR 11262 DCOM dispGetClassObject - HRESULT: -2147220976, Context: INPROC
2004-04-12 09:02:29 18 ERR 11263 DCOM COCLSID: {A435CDA8-A24E-11D3-A996-00A0C94311A5}
2004-04-12 09:02:29 18 ERR 51260 HRESULT 10020480
This may be related to a question I asked earlier for which unfortunately nobody had yet responded. I found a similar problem reported in the archives. But the solution proposed cannot be implemented since I do not know where the xregcomp program is in my unix environment.
I would really appreciate a solution to this problem.
Edward Pius
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
