zaidlaz
6th September 2001, 07:27
Hi,

I've tried to change the baan database user/group password.
There were no impact on normal user transactions but our developers/baan administrators will encounter bdb error 2017 when performing the following:-
1) Any customisations, update baan patches, svc packs that creates new baan tables.

Why is this so?

:confused:

Best Wishes,
Zaid

patvdv
6th September 2001, 10:03
That's because the baan user/group matches the the user baan in your database. Hence the encrypted password in $BSE/lib/ora_groups must match the one of your database user.

How did you change the baan user password? Did you use the ora_adminx.x (inf_adminx.x) tools?

zaidlaz
6th September 2001, 11:13
Managed to solve the mystery..

Below are the step:-
To change baan user passwd
=====================
1) Login as superuser e.g. baan
2) execute session ttdba0115m000
3) change the password
4) click "yes" when prompted "Change password in database"
(The baan user" passwd will be update and the database passwd synchronised, it will also perform a dump of users file (ora_users))
5) login a new client as superuser e.g. baan
6) execute session ttadv0143m000
7) change the password the same as 3)


To change baan group passwd
======================
1) Login as superuser e.g. baan
2) execute session ttdba0120m000
3) change the password
(This will automatically change database passwd for baandb, it will also perform a dump of the user_groups file)


PS: I'm doing this test at my test server and I have not come to any conclusion if this is a proven solution as there are many scenarios to test. Pls do not try this...




Best Wishes,
Zaid