log4cpp -- Node number in master*.log is always 0

Bug #1412641 reported by gaoruixian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trafodion
New
Medium
Sandhya Sundaresan

Bug Description

Node number in master*.log is always 0, tm.log has correct number.

SQL>select [first 5] * from udf(event_log_reader('f')) where log_file_name='master_exec_0_7476.log';

LOG_TS SEVERITY COMPONENT NODE_NUMBER CPU PIN PROCESS_NAME SQL_CODE QUERY_ID MESSAGE LOG_FILE_NODE LOG_FILE_NAME LOG_FILE_LINE PARSE_STATUS
-------------------------- ---------- ------------------------ ----------- ----------- ----------- ------------ ----------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ------------- -------------------------------------------------------------------------------------------------------------------------------- ------------- ------------
2015-01-19 04:29:53.454000 INFO SQL.ESP 0 2 24361 $Z020JW1 NULL NULL An ESP process is launched. 0 master_exec_0_7476.log 1
2015-01-19 04:29:53.462000 INFO SQL.ESP 0 2 24360 $Z020JW0 NULL NULL An ESP process is launched. 0 master_exec_0_7476.log 2
2015-01-19 04:29:53.452000 INFO SQL.ESP 0 5 31881 $Z050R0W NULL NULL An ESP process is launched. 0 master_exec_0_7476.log 1
2015-01-19 04:35:23.101000 INFO SQL.ESP 0 5 1892 $Z0501J2 NULL NULL An ESP process is launched. 0 master_exec_0_7476.log 2
2015-01-19 04:29:53.454000 INFO SQL.ESP 0 2 24361 $Z020JW1 NULL NULL An ESP process is launched. 0 master_exec_0_7476.log 1

--- 5 row(s) selected.

SQL>select [first 5] * from udf(event_log_reader('f')) where log_file_name like 'tm%';

LOG_TS SEVERITY COMPONENT NODE_NUMBER CPU PIN PROCESS_NAME SQL_CODE QUERY_ID MESSAGE LOG_FILE_NODE LOG_FILE_NAME LOG_FILE_LINE PARSE_STATUS
-------------------------- ---------- ------------------------ ----------- ----------- ----------- ------------ ----------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- ------------- -------------------------------------------------------------------------------------------------------------------------------- ------------- ------------
2015-01-19 03:42:19.803000 INFO TM 2 2 4052 $TM2 NULL NULL Message: DTM_TM_PROCESS_STARTUP 0 tm.log 1
2015-01-19 03:42:31.193000 INFO TM 2 2 4052 $TM2 NULL NULL Message: DTM_RECOV_SYSRECOV_COMPLETE 0 tm.log 2
2015-01-19 03:42:21.090000 INFO TM 5 5 10604 $TM5 NULL NULL Message: DTM_TM_PROCESS_STARTUP 0 tm.log 1
2015-01-19 03:42:31.216000 INFO TM 5 5 10604 $TM5 NULL NULL Message: DTM_RECOV_SYSRECOV_COMPLETE 0 tm.log 2
2015-01-19 03:42:19.803000 INFO TM 2 2 4052 $TM2 NULL NULL Message: DTM_TM_PROCESS_STARTUP 0 tm.log 1

--- 5 row(s) selected.

Tags: sql-exe
Changed in trafodion:
importance: Undecided → Medium
assignee: nobody → Sandhya Sundaresan (sandhya-sundaresan)
milestone: none → r1.1
Changed in trafodion:
milestone: r1.1 → r2.0
tags: added: sql-exe
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.