maclezhang
18th January 2007, 10:39
we can access the data of database normally, but now we cannot create or delete table , once create table from baan tools , system report " detected database server terminated", and we have to relogin baan system .
we check oracle system , it is normal . we can also create table with the baan user in oracle through "sqlplus" .


the log.oracle8 is like that:
2007-01-18[14:45:46(UTC-08:00)]:E:bsp: ******* S T A R T of Error message ******
*
2007-01-18[14:45:46(UTC-08:00)]:E:bsp: Log message called from /BAAN/view/port.8
.2b/vobs/tt/lib/al_1/al_sig.c: #173 keyword: CORE DUMPED
2007-01-18[14:45:46(UTC-08:00)]:E:bsp: Pid 1605862 Uid 125 Euid 125 Gid 125 Egid
125 Pset 110011@zjj.it2004.gree.com.cn:4048
2007-01-18[14:45:46(UTC-08:00)]:E:bsp: user_type S language 2 user_name bsp tty
ote locale GB2312/zh_CN
d)07-01-18[14:45:46(UTC-08:00)]:E:bsp: Errno 0 bdb_errno 110 (End of file reache
home/bsp'8[14:45:46(UTC-08:00)]:E:bsp: Log_mesg: core_dumped() signal 11 cwd: '/
2007-01-18[14:45:46(UTC-08:00)]:E:bsp: ******* E N D of Error message *******
home/bsp'

what happened?

Markus Schmitz
18th January 2007, 11:31
In case of oracle, the $BSE/lib/ora/ora_user file specifies, which Oracle user to user for which Baan user in case of normal Baan access.

But for creation and deleteion of tables a different oracle login is used. This is specified in $BSE/lib/oracle_group. Most likely this is the baan login (if you are on unix).

So your problem might happen, due to the fact, that the crypted password in ora_group is not consistent with the actual password of user baan in oracle. Did anybody change that password?

Regards

Markus

naabi0
18th January 2007, 19:50
We had close to the same problem. We just installed LN on a P5 570 / AIX 5.3 only we are running DB2. I think the problem is fixed. I put on porting set 8.3a.01 (just released a couple of weeks ago) and patched C++ to the latest level.

jclju1
31st March 2008, 14:41
patched C++ to the latest level

Naabi0,

could you send output of command lslpp -l | grep xlC. I have same problem on Baan 5 )PS 7.1d.16) and my output is:

lslpp -l | grep xlC
xlC.aix50.rte 9.0.0.0 COMMITTED XL C/C++ Runtime for AIX 5.2
xlC.cpp 6.0.0.0 COMMITTED C for AIX Preprocessor
xlC.msg.en_US.cpp 6.0.0.0 COMMITTED C for AIX Preprocessor
xlC.msg.en_US.rte 9.0.0.0 COMMITTED XL C/C++ Runtime
xlC.rte 9.0.0.0 COMMITTED XL C/C++ Runtime