• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2162
  • Last Modified:

Oracle Failsafe Logging - fslservername log


I would appreciate if anyone can advise on the following scenario on a subject that at present our organisation does not have a great deal of knowledge.  In our environment we are running a COTS document management system using Oracle 9i as the backend database.  In our core offices this system has been configured in in a MSCS environment with Oracle Failsafe.  This cluster environment is configured in an active/passive mode.

In the oracle application folders on both server nodes oracle fail safe generates a log file in the ora92\network\log folder .  This file is called fslservername.log.  On investigation we have discovered that this log is only updated on the server that is active.  Whilst logging entries are made approximatley 4 times a minute.  A sample of the entries are as follows:

"06-SEP-2004 13:25:32 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=erdm_cluster))(COMMAND=status)(ARGUMENTS=64)(SERVICE=Fslmc35glera)(VERSION=153092352)) * status * 0
06-SEP-2004 13:25:45 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=MC34.MC34GLERC.scotland.gov.uk)(CID=(PROGRAM=E:\Objective\Objective 6i SP3 Server\bin\objindex.exe)(HOST=MC35GLERA)(USER=objective))) * (ADDRESS=(PROTOCOL=tcp)(HOST= * establish * MC34.MC34GLERC.scotland.gov.uk * 0
06-SEP-2004 13:26:15 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=MC34.MC34GLERC.scotland.gov.uk)(CID=(PROGRAM=E:\Objective\Objective 6i SP3 Server\bin\objindex."

Regarding this log file I would appreciate if anyone can help on the following points:

What is failsafe generating when writing to this log and should it be checked frequently.  

Is it safe to archive these logs on routinely basis. If so what frequency would be recommended, daily, weekly, monthly etc.

Assistance in this request would be greatly appreciated.

  • 2
1 Solution
This is a listener log file, and will contain an entry for each 'action' requested on the listener - user connections, change of listener config, listener start/stop etc. This explains why you dont get anything reported on your passive node!

The information is purely informational, and is not required by any part of the system - consider it an audit trail.

You can safely ignore it or turn off the logging in your ora92\network\admin\listener.ora file.

On most systems I support, I change the logfile name once a month, and delete / archive off the old one. How often you would want to do this will depend on the size of the files, which in turn usually depends on the number and frequency of user connections.

GraemeTLAuthor Commented:
Thanks very much. This makes perfect sense.  This will now help us correctly archive as per usage as the system grows.

Thanks again.
No probs - good luck!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now