OWB 11GR2: Runtime Logging - Control Center Logs

        Previously a colleague of mine discusses Logging for the OWB Design Client. In this article, I’d like to discuss logging for the OWB Runtime. In OWB 11GR2, besides the Control Center Service, we have expanded OWB Runtime with a new component that we called Control Center Agent. For this blog, we’ll discuss logging only on Control Center Service.

        In OWB 11gR2, the Control Center log files are by default located under <owb-home>/owb/log on the server where the Control Center Service runs (where <owb-home> is the installation directory of OWB product). The logs contain useful diagnostic information of the Control Center Service, such as the states of the Service, deployment or execution failures, resource usage, etc. The names of the logs are in the format of OWBSYS.xxxxx.log, where xxxxx is the version tag that starts from the number 00001 and will be increased by 1 with each new log file generated.

Version Tag

        A new log file will be generated when we start or re-start the Control Center Service, or when the existing log file reaches its maximum size (log file size is configurable, see below). The name of the new log file will have a version tag of the one used in the previous log file with an addition of 1. For example, if the latest file is OWBSYS.00015.log, then the new file will be named OWBSYS.00016.log.

Configuring Logging

        We have some control on the Control Center logs, To do so, we need to modify the Runtime.properties under <owb-home>/owb/bin/admin. This file is used to store the Control Center properties that will be read when the Control Center Service is started. So if there are any changes made to this file, we will need to restart the CCS.

        The content of the file is quite straight-forward (in the name=value format…) and there are several logging-related configurations:

clip_image002

max_number_logfiles” – this property is used to set the maximum number of log files. The valid range is 2-99999. If this property is not set, then the default value is 99999.

logfile_max_size” – this property is the maximum number of statements in the log file. When the limit is exceeded, the logging process will switch to a new log file. Setting this property to the value “0” means the limit is not set.

exceptions” – this property indicates where the exceptions (error message??) will be logged to, including the name of the log and the place where to place the log. %RTHOME% refers to the runtime home, which is set during the repository install. You can change this value by running <owb-home>/owb/rtp/sql/reset_owbcc_home.sql, and enter “<owb-home>” when prompted.

messages” – this property indicates where the messages will be logged to, similar settings to the one above . By default, the exceptions and messages are logged to the same log file.

 

        Another related property is “propertyInfo”, if this is set to true, extra information about properties handling will be logged. For example, information about when the Control Center Service reads properties from the Runtime.properties file or from the wb_rt_platform_properties table will be logged; some debug information will be printed to the log, such as “Found {property.RuntimePlatform.0.trace_control_on} in property file” etc.

clip_image002[7]

Other Logs

        Besides the Control Center logs, there are some other runtime logs, such as the SQL*Loader logs under the directory <owb-home>/owb/temp. The SQL*Loader logs are generated with each SQL*Loader job execution. It is a good idea to clean out the temporary files in this temp directory periodically.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

ETL, CDC, Real-Time DI and Data Quality for the Oracle Database from the inside.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today