on 05-17-2008 12:46 PM
Hello,
we have 2 Livecache SAPDB 7.4.03 Databases installed on one AIX Server, called LCD and LCT.
The databases were running well, but after some changes on the filesystem preparing backup with adint, one of the databases is not able to start.
-24994,ERR_RTE: runtime environment error
1,Check knldiag! Kernel died before reaching ADMIN state
I see only this error in file knldiag from LCT
ERR 11270 console e87_create_diag_fifo: chown error, Not owner
What I have noticed in the file, that some ENV parameters are wrong because these are settings from the other database like this:
2008-05-17 13:25:50 1 12898 ENVIRON HOME=/home/lcdadm
2008-05-17 13:25:50 1 12898 ENVIRON USER=lcdadm
P2008-05-17 13:25:50 1 12898 ENVIRON LOGNAME=lcdadm
2008-05-17 13:25:50 1 12898 ENVIRON LOGIN=lcdadm
2008-05-17 13:25:50 1 12898 ENVIRON ADINT=/usr/tivoli/tsm/adint64
2008-05-17 13:25:50 1 12898 ENVIRON ADA_OPT=/sapdb/LCD/adint/initLCD.utl
I checked env of the user lctadm everythings seems to be ok. When I changed one option with this
dbmcli -d LCT -u control,***** dbm_configset -raw ADA_OPT /sapdb/LCT/adint/initLCT.utl
When I restart the database i have the same result and the wrong env.setting.
Where are the settings stored and what be the reason for this issue ?
Check /etc/opt/sdb if you see anything strange.
Also have a look at
/sapdb/data/config/<SID>.cfg
The error you see comes from a chown() call for /usr/spool/sql/fifo (which is a link to /sapdb/data/fifo)
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I logged on now to another AIX server with multiple livecache instances, difference is version 7.5 instead of 7.4
There is an file under /etc/opt/sdb and includes
[Globals]
IndepData=/sapdb/data
IndepPrograms=/sapdb/programs
SdbOwner=sdb
SdbGroup=sdba
But this user/group does not exist on this server, so i tried to create this file wih SdbOwner lctadm SdbGroup sapsys and second with SdbGroup root , but it doesn't help.
I logged on now to another AIX server with multiple livecache instances, difference is version 7.5 instead of 7.4
There is an file under /etc/opt/sdb and includes
IndepData=/sapdb/data
IndepPrograms=/sapdb/programs
SdbOwner=sdb
SdbGroup=sdba
yes - that´s the reason - 7.4 does not create that directory, the configure is under /usr/spool/sql - I wasn´t reading attentively - sorry for confusion...
who is owner of the directory /usr/spool/sql/fifo? The correct user?
Markus
This directory looks like this
[...x:root:/usr/spool/sql/fifo:] ls -al
total 0
drwxrwxr-x 2 lcdadm sapsys 256 May 17 15:50 .
drwxrwxr-x 10 lcdadm sapsys 256 Mar 17 13:54 ..
prwww- 1 lcdadm sapsys 0 May 17 16:07 LCD
prw-rw---- 1 lcdadm sapsys 0 May 17 16:14 xserver_depflalc02x_logger
prw-rw---- 1 lcdadm sapsys 0 May 14 08:26 xserver_depflalc02x_update
So this looks like the "wrong" user or with the other db-owner user.
But does it make a sense to change it to lctadm and create a file named LCP ?
I am afraid that in this case the other db will also not start
Frank
> [...x:root:/usr/spool/sql/fifo:] ls -al
> total 0
> drwxrwxr-x 2 lcdadm sapsys 256 May 17 15:50 .
> drwxrwxr-x 10 lcdadm sapsys 256 Mar 17 13:54 ..
> prwww- 1 lcdadm sapsys 0 May 17 16:07 LCD
> prw-rw---- 1 lcdadm sapsys 0 May 17 16:14 xserver_depflalc02x_logger
> prw-rw---- 1 lcdadm sapsys 0 May 14 08:26 xserver_depflalc02x_update
>
> So this looks like the "wrong" user or with the other db-owner user.
What you can try is to give the group (sapsys) write permissions on /usr/spool/sql - and also on the link and the target directory it points to.
Markus
the group had already rw permissions on /usr/spool/sql
But now i have stopped the other database and kill all other processes related, cleaned shared memory, restart x_server now with user lctadm and now i was able to start both databases !
The problem is solved and although i am not sure what the reason was, i am happy now.
Thank you very much for your help.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.