AWA: Two digit number appears after date and time stamp

book

Article ID: 125141

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction



What does it mean when a two-digit number occurs after the date and time stamp in a WP log and WP forced traced file?

WP log:

<Please see attached file for image>

two-digit WP log

WP forced trace file:

<Please see attached file for image>

two-digit WP forced trace

Environment

Linux
Oracle Database

Resolution

The two-digit number after the date and time stamp means the Automation Engine was unable to connect to the Database.

This can be seen in the WP log:
20190114/180010.662 - 27 U02000071 Current directory: /opt/automic/AutomationEngine/bin 
20190114/180010.662 - 27 U00011849 UC4_sys_info: 'UC4 Version 12.1.1+hf.3.build.5423' 
20190114/180010.663 - 27 U00011849 UC4_sys_info: 'BuildTimestamp 2018-03-07 15:34:59' 
20190114/180010.663 - 27 U00011849 UC4_sys_info: 'Buildnr: 0000005423 Changelist: 1520333049' 
20190114/180010.664 - 27 U00045159 45159? MQWorker-1|34|| 
20190114/180010.664 - 27 U00045159 45159? Timer-1|23|| 
20190114/180010.664 - 27 U00045159 45159? Timer-2|24|| 
20190114/180010.665 - 27 U00045159 45159? NetworkWorker-1|27|| 

This is normally where the Database information gets written in the logs when connection is successful. When unsuccessful, then it gets replaced by this instead. 

The WP forced trace file confirms the Database issue: 
20190113/050433.427 - 23 U00011849 UC4_sys_info: 'UC4 Version 12.1.1+hf.3.build.5423' 
20190113/050433.427 - 23 U00011849 UC4_sys_info: 'BuildTimestamp 2018-03-07 15:34:59' 
20190113/050433.428 - 23 U00011849 UC4_sys_info: 'Buildnr: 0000005423 Changelist: 1520333049' 
20190113/050433.428 - 23 U00045159 45159? MQWorker-1|34|| 
20190113/050433.429 - 23 U00045159 45159? Timer-1|23|| 
20190113/050433.429 - 23 U00045159 45159? Timer-2|24|| 
20190113/050433.429 - 23 U00045159 45159? NetworkWorker-1|27|| 
20190113/050433.430 - 23 ------------------------- Java VM ------------------------- 
20190113/050433.430 - 23 Java virtual machine implementation vendor:Oracle Corporation 
20190113/050433.431 - 23 Java virtual machine implementation version:25.144-b01 
20190113/050433.431 - 23 Name:<[email protected]>
20190113/050433.432 - 23 Java virtual machine specification version:1.8 
20190113/050433.432 - 23 Start time of the Java virtual machine :Mon Dec 17 19:40:02 UTC 2018 
20190113/050433.433 - 23 
20190113/050433.433 - 23 --------------------- Operating System -------------------- 
20190113/050433.433 - 23 Operating system architecture:amd64 
20190113/050433.434 - 23 Number of processors available to the Java virtual machine:4 
20190113/050433.434 - 23 Operating system name:Linux 
20190113/050433.435 - 23 Operating system version:3.10.0-862.14.4.el7.x86_64 
20190113/050433.435 - 23 
20190113/050433.435 - 23 ---------------------- Memory system ---------------------- 
20190113/050433.436 - 23 Current memory usage of the heap:init = 262144000(256000K) used = 40158784(39217K) committed = 149946368(146432K) max = 477626368(466432K) 
20190113/050433.437 - 23 Current memory usage of non-heap memory:init = 2555904(2496K) used = 57156352(55816K) committed = 60424192(59008K) max = -1(-1K) 
20190113/050433.438 - 23 
20190113/050433.438 - 23 ----------------------- Stack Trace ----------------------- 
20190113/050433.438 - 23 com.automic.database.api.DBException: java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress 

Attachments

1558691035367000125141_sktwi1f5rjvs16ggu.jpeg get_app
1558691032332000125141_sktwi1f5rjvs16ggt.jpeg get_app