hi,

All users are frequently disconnected to the database and baan.

In the file log "log.oracle8", the following error is returned :
BDB - 522

i don't understand what is the matter !

The features of our machine are:
Compaq ES40 Alpha Server
Tru64 Unix v5.1A
Baan IV c4, porting set 6.1c.06.03
Oracle 8.1.7


is there someone who has an experience about this problem ?

Can you please the full log entries and from all $BSE/log files that are updated each time? Are you using the Oracle Listener?

i use oracle listener

I receive the following message in the log file
at the same time

******* S T A R T of Error message *******
Log message called from /vobs/tt/servers/ORACLE_2/ora_native.c: #1991 keyword: Oracle Error
Pid 34445 Uid 244 Euid 244 Gid 125 Egid 125
user_type S language 4 user_name edwige tty ote locale ISO88591/NULL
Errno 2 (No such file or directory) bdb_errno 110 (End of file reached)
dbs_errno = 0Error 522 occurred:
Error ORA-3114 occurred during commit.
ORA-03114: not connected to ORACLE
Error BDB-522 returned.
Flushed at /vobs/tt/servers/ORACLE_2/ora_db.c : #81.
******* E N D of Error message *******

******* S T A R T of Error message *******
Log message called from /vobs/tt/servers/ORACLE_2/ora_native.c: #1991 keyword: Oracle Error
Pid 34445 Uid 244 Euid 244 Gid 125 Egid 125
user_type S language 4 user_name edwige tty ote locale ISO88591/NULL
Errno 2 (No such file or directory) bdb_errno 110 (End of file reached)
dbs_errno = 0Error 522 occurred:
Error ORA-1041 occurred during cancel.
ORA-01041: internal error. hostdef extension doesn't exist
Error BDB-522 returned.
break cursor failed: dbs_errno 522.
See fatal SQL statement in '/baan/bse/log/log.ora.sql'.
Flushed at /vobs/tt/servers/ORACLE_2/ora_cursor.c : #274.
E N D of Error message *******

Do you have any errors in following files:
Oracle alert file
TNS listener log file
Oracle user trace files
How often does the disconnect happen? Are all users impacted? How do users connect? (BA/BW) Do you users connect through a WAN?

i receive errors in 2 files :

log.oracle8 and log.bshell

"the message is the same in the 2 files : lost connection to the database engine"

what is the name of TNS listener file ?

the disconnect happen every hour.

All users are impacted. There are 10 users now. BW. the users are connected through the LAN.

for TNS: look in your $ORACLE_HOME/network/log/

for alert file: look in your $ORACLE_BASE/admin/SID/bdump

The TNS listener file doesn't show any information about the error.

i have not the alert file "bdump"

No 'bdump' is a directory. The alert log file is something like <SID>ALRT.log

Did you by any chance install this Oracle version recently, or rather...did it ever work correctly for you?

I have not worked with 8.i myself yet, but the word on the street is that the install of 8.1.7 can be easily goofed which will result in the ORA-01041 errors that you are seeing.

Two more questions.

Do the disconnects happen around the same time or throughout the day?

What are the properties of your tablespace?

I have not found much info about this error. It seems to be an Oracle bug. In OTN web, a search for the ORA error that appears in your log, results in the link bellow.

http://download-uk.oracle.com/otndoc/oracle9i/901_doc/rac.901/a88810/4admin.htm

"Administering Failover of the Applications
Oracle Real Application Clusters Guard restores service quickly. The application must restart transactions when it receives an Oracle message that indicates that failure has occurred.

Failing over the application when the primary instance fails is straightforward. The application sessions receive the ORA-1089 and ORA-1034 Oracle errors for new requests and the ORA-1041, ORA-3113, and ORA-3114 Oracle errors for active requests. These errors must be trapped by the application. At reconnection, the application connects transparently to the new primary instance. For example, in the case of a web server, the server threads are restarted for each connection pool against the new primary instance. The current transactions are then resubmitted by the clients.

Failing over the application when the primary node fails is not straightforward because of TCP/IP time-out. TCP/IP time-out is a significant problem for high availability. It occurs when a node fails without closing the sockets, because new requests can be made to an IP address that is unavailable. For active requests, the delays to the client are the values for TCP_IP_ABORT_CINTERVAL and TCP_IP_ABORT_INTERVAL. For sessions that are waiting for read/write completion, the delay is the value for TCP_KEEPALIVE_INTERVAL. The values for these TCP/IP parameter should be tuned at each site.


--------------------------------------------------------------------------------
Note:
These parameters are specific to your operating system. See your operating system documentation for more information.

--------------------------------------------------------------------------------




TCP/IP time-outs are addressed in Oracle Real Application Clusters Guard by using relocatable IP addresses and the call-home feature. Because Oracle Real Application Clusters Guard moves the IP addresses, active requests for an address do not wait to time out. Requests for connection are refused immediately and are routed transparently to the new primary instance. Requests that issue SQL statements receive a broken pipe error (ORA-3113), allowing the application to restart. The application should detect this error and take appropriate action."