Common Application Logs
When the application is operating, the infrastructure logs messages within its own logs. For example, the database will log database errors or messages to the database logs, Oracle WebLogic will log web application errors or messages to the Oracle WebLogic server logs and so on. The name and location of these logs is set by relevant vendors of those logs. Refer to the documentation provided with that software on where logs are stored and their logging conventions.
Additionally, the application writes several application specific logs to $SPLSYSTEMLOGS. Some of these logs are further classified into technical and user logs. As the name suggests, the technical logs contain tracing information for SQLs, stack traces of Java code and other similar technical traces. Essentially, these are errors that suggest the system is misconfigured or is being run in a way that is not expected and contain Application Trace Data which is required for diagnostic purposes. Whereas the user log consists of a Business logic messages, Business trace data.
The following are the logs:
• spl_web-tech.log - Web application server application messages that are technical n nature.
• spl_web-user.log - Web application server application messages that contain user/business data or traces.
• spl_service-tech.log – Technical messages for the business application server. If the business application server exists on the same Oracle WebLogic Server instance (that is, as per a local install) as the web application server for an environment, then this log does not exist and all messages are written to the spl_web-tech.log.
• spl_service-user.log – Business logic/trace messages for the business application server. If the business application server exists on the same Oracle WebLogic Server instance (that is, as per a local install) as the web application server for an environment then this log does not exist and all messages are written to the spl_web-user.log.
• spl_iws.log – Web Services Adapter messages.
• Background processing logs are also categorized into technical and business logs and are in $SPLOUTPUT for the following:
• threadpoolworker.<threadpool>.<datetime>-tech.log - The threadpoolworker technical log for threadpool <threadpool> started at <datetime>.
• threadpoolworker.<threadpool>.<datetime>-user.log - The threadpoolworker business log for threadpool <threadpool> started at <datetime>.
• <batch_cd>.<datetime>.THD<thread>.stderr/<batch_cd>.<datetime>.THD<thread>.stdout - The submitter log for thread <thread> of background process <batch_cd> started at <datetime>.
The format of all logs is as follows:
Field
Comments
<userid>
User ID of transaction (blank or "-" for system generated messages).
<transactionId>
Transaction identifier.
<ECID>
Execution Context Identifier (weblogic).
<date/time>
Time of transaction in format YYYY-MM-DD HH24:MM:SS,SSS
<threadinfo>
Information of the thread.
<log level>
Logging level enabled.
(<class>)
Java class generating message (see Javadocs) (applicable for tech logs).
<message>
<message contents>
Sample log entries:
User Application Error logs:
SPLRXO - 364812-788-1 2016-11-16 13:08:44,371 [[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO (support.changehandlers.ChangeEventHandler) PK1 PK2 combination not found. Check if the fields are populated. Message Number 11001, 402.
Tech Application Error logs:
SPLRXO - 364812-788-1 2016-11-16 13:08:44,371 [[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO (support.changehandlers.ChangeEventHandler) The following rule was violated: Characteristic Value should be valid : userCharacteristic:Characteristic Value should be valid for entity 'F1US'