What are log files and what are they used for? Register or Login. Welcome back! Reset Your Password We'll send an email with a link to reset your password. Stay ahead! Get the latest news, expert insights and market research, tailored to your interests.
Sign in with email Enter the email address associated with your account. You auth link is expired or incorrect, please try again. You set logging levels to specify the events and messages to record in the log file or in the log database. An event is an occurrence in your IBM Cognos 8 environment that is significant enough to be tracked, such as starting or stopping a service. You can set a different logging level for each dispatcher service.
You can do this for each dispatcher or for all dispatchers in the same folder. By setting different logging levels for different services you can reduce the amount of irrelevant logging information.
For example, if you must troubleshoot the batch report service, you can select a detailed logging level for just that service, keeping log messages to a minimum. The logging level for a service applies to all its components. Note: The log service does not have logging levels associated with it. You can maintain system performance by managing the amount of logging performed by the server. Since extensive logging affects server performance, increasing the logging level may negatively affect the performance of IBM Cognos 8.
The default logging level is Minimal. Use Full logging level only for detailed troubleshooting purposes because it may significantly degrade server performance. Or, Query Account. This means someone viewed an account or someone viewed a report.
Hope this helps. Hi Polzovatel, You at least help me understand some of the propeties. I found some documentation about the logging in a few of the Cognos guides. I still haven't found an explanation of the properties. However, looking at the documentation It's possible our current logging level isn't set to the appropriate detail level.
That could explain why I'm having a hard time understanding why certain error's occur. I'll check if this is the case. Techniques for troubleshooting problems Troubleshooting is a systematic approach to solving a problem. Getting product fixes A product fix might be available to resolve your problem.
Troubleshooting Help Find out how to resolve problems accessing the product help. Troubleshooting inter-server communication If you are having problems establishing communication between servers in your deployment, this might be because a server's URL is not configured correctly in the LotusConnections-config. Collecting communities catalog troubleshooting data Collect communities catalog data to help IBM Support diagnose catalog problems. Troubleshooting Search If you experience indexing issues, consider validating Search seedlists to help you identify the source of the problem.
Troubleshooting SAML 2. Troubleshooting virus scanning Find out some of the common causes for scanning-related error messages. Troubleshooting media views and thumbnail generation The Files application provides a grid view to show thumbnails for files of various formats.
Table 1. The log file names include the product name, version, build number, and timestamp. The transfer log file records the activities that the installation wizard performed while transferring files; its file name begins with "tl" as in this example: tl-BISRVR The transfer log file records the activities that the installation wizard performed while transferring files; its file name begins with "tl" as in this example: tl-BITRSFRMR Rate this topic 5 stars 4 stars 3 stars 2 stars 1 star.
0コメント