In most cases, the resulting ODL log record will contain only a timestamp and the message text from the original log entry. The Log Loader can even read unformatted logs, which may not even contain timestamp values.
When log entries do not contain a timestamp, the Log Loader sets the timestamp to the value of the "last known timestamp" for that log. The value of the last known timestamp is determined according to the following rules:. The initial value of the last known timestamp is zero. Note that whenever adding a log record to the repository, a zero value timestamp is converted to the current time.
When the Log Loader reaches the end of the log, it sets the last known timestamp with the current time. If the Log Loader is running regularly, such as once every five minutes, this results in timestamps that are approximate to the actual time the message was written, within a five minute range.
If the Log Loader is not run frequently, the value of these timestamps could be inaccurate. The Application Server Control Console and the Log Loader read Oracle Application Server component diagnostic registration files to determine names, locations, and additional configuration information about diagnostic log files.
Oracle Application Server components may have multiple registration files in the configuration registration directory. The format for the registration files includes a Oracle Application Server component ID, and extension,. Table lists the Oracle Application Server components that support ODL messages but that generate text messages by default.
The directory should be located at the following location:. Using the Application Server Control Console or the dcmctl command line utility, modify the httpd. Scroll down to the Multiple VM Configuration section. The property applies for the entire OC4J instance and it cannot be set to different values for different applications running on OC4J. You can use SQL scripts to create and manage a database repository for diagnostic messages. By creating a database repository for diagnostic messages, you can search, view, and correlate diagnostic messages across multiple Oracle Application Server instances.
Use the SQL scripts described in the following sections to create and manage a repository for diagnostic messages. The scripts are located in the following directory:. The database that hosts the Log Repository can be an Oracle9 i database or an Oracle Database 10 g database. The actual environment variables and values that you have to set depend on the type of your UNIX operating system.
This script requires two arguments: the name of the tablespace to be created and the location of the tablespace datafile, for example:. This script requires three arguments: name of the user, user password, and the default user tablespace. Use the tablespace you designated for the repository for the default user tablespace, for example:. Connect to the new or existing tablespace as the designated user, for example:.
In order for the Log Loader to load diagnostic messages into the repository, you must update the repository element in the logloader. Replace the contents of the repository element with the following:. Store the repository password for your installation in a wallet in the Log Loader configuration directory, using the following command:. If your installation is part of an OracleAS Cluster, update the Log Loader configuration in one instance of the cluster and then run the following command to propagate the changes to the other instances in the cluster:.
The script takes two arguments:. To delete the user and tablespace, connect to the database as administrator and run the SQL commands for dropping a user and dropping a tablespace. The following example drops a user and tablespace, including contents and datafiles:. If you want to use a file-based repository instead of a database repository for the diagnostic message repository, you must update the repository element in the logloader. Note the following limitations and configuration issues with log files:.
However, certain log files are only available at the component level. If you shut down the Log Loader after the database is shutdown, and you restart Log Loader after the database is restarted, some messages may be reloaded to the repository database twice. Usually, Log Loader saves its state after each load. However, if the database is shutdown first, Log Loader does not save its state.
When it restarts, it resets its state to the end of the last successful load and will repeat any load that was unsuccessful. If the repository database was shutdown in the middle of that load, some of the records may have been written to the repository database, but the entire load will be repeated.
See Also: Section 5. Note: By default, the Log Loader is not started. In many cases, to configure component logging options, you need to use the Application Server Control Console Advanced Server Properties page to edit the values in configuration files.
See Also: Oracle Application Server component documentation for information on setting logging configuration options. Click Search to list the log files for the selected components. You can list log files using a search filter by performing the following steps: Select the Logs link on an Application Server Control Console page.
Select a field from the Log File Attribute list. Click Add Row to add a row for the selected log file attribute. Enter the desired search value in the Value field. See: Section 5. Note: The Message Type selection box includes the Unknown option. Some components do not include a message type when the component writes log file entries.
These messages are loaded into the Log Repository with Unknown specified as the message type. Web Cache Supports message correlation.
The following general techniques can assist you in accomplishing this task: Search for errors, or warnings, related to the problem Correlate the errors across components Correlate the errors across a time interval Perform component-based analysis Using a Log Repository can make searching for the root cause of a problem much easier.
Click Log Loader. To change the Log Loader properties, perform the following steps: Enter updated values in the appropriate fields on the Log Loader Properties page. Click Apply to apply the new values. Typically, there are two common types of registration file errors: XML syntax errors that prevent the file from being parsed.
For example, you can use printlogs to: Read log messages from the Log Repository or individual log files Filter log messages according to timestamp or log field value Print log messages in ODL or text format Sort log messages by field Report the number of log messages of a specified type Run in a continuous loop, printing log reports and sleeping for a specified amount of time See Also: Appendix F for more information about the printlogs tool.
The message ID uniquely identifies the message. Older segment files are removed and newer segment files are saved in chronological fashion. Note: The most recent segment file is never deleted. The value of the last known timestamp is determined according to the following rules: The initial value of the last known timestamp is zero.
Most other logs in this directory are treated as unformatted logs, and have timestamps assigned according to the preceding rules.
Note: Components are responsible for creating the component diagnostic registration files. Normally, Oracle Application Server administrators should not modify these files. Select Server Properties in the Instance Properties area.
Note the following when setting the oracle. Choose an existing tablespace or create a new tablespace for the repository. All rights reserved. Home Solution Area Contents Index. Oracle Application Development Framework. CM SDK. Enterprise Manager. HTTP Server. Integration B2B. Log Loader. Oracle Internet Directory.
Port Tunneling. Table of Contents Search. No Results. Change the Reader Step 3. Change the Source Connection Step 4. Back Next.
External Loader Behavior. When you run a session that uses an external loader, the Integration Service creates a control file and a target flat file. The control file contains information such as data format and loading instructions for the external loader. The control file has an extension of.
You can view the control file and the target flat file in the target file directory. When you run a session, the Integration Service deletes and recreates the target file. The external loader uses the control file to load session output to the database. The Integration Service processes datetime data before loading to the database in the following ways:. In the log file you find all Loader commands required to open a session and to execute the required transformation export, import or transport.
Line with messages; these are informative system messages, such as the number of lines inserted and rejected, last completed transaction. Line with error messages; this is used to introduce the two lines with the table and position values as well as the error number or error text for rejected lines. The log file is structured so that parts of it can be easily used to create a command file. In the log file, every command is saved together with information about the execution time, the number of objects for which actions were carried out, and any errors that occurred.
However, the log file does not detail which individual actions were required to execute the command. Transport Mode.
0コメント