Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Guys,
I have Qlik Sense Qlik Sense June 2020 Patch 6. After a reboot of the server machine, we are not available to run Operation Monitor app, In the "Load_Database_Logs" section of the script, when try to run this part of code it fails:
CONCATENATE (working)
LOAD
Round((entry_timestamp),1/1440) &'|' & Round((entry_timestamp),1/1440) AS _date_time_link,
Timestamp((Round(entry_timestamp,1/86400))) AS LogEntryPeriodStart,
Timestamp((Round(entry_timestamp,1/86400))) AS LogTimeStamp,
id AS Id_temp, // For incremental reload
id AS _proxySessionPackage,
lower(process_host) AS Hostname,
process_name,
logger AS Logger,
entry_level AS Severity,
message AS Message,
exception AS Exception,
stack_trace AS [Stack Trace],
thread AS Thread,
proxy_session_id AS [ProxySessionId], // This is sparsely populated! Not reliable at all
subfield(logger,'.',2) AS Service,
// Engine specific entries
engine_thread AS [Engine Thread],
active_user_directory AS [Active User Directory],
active_user_id AS [Acitve User Id],
process_id AS [Process Id],
Timestamp((engine_timestamp)) AS [Engine Timestamp],
// Scheduler specific entries
task_id AS [TaskId],
task_id AS ObjectId,
execution_id AS [Execution Id],
task_name AS [Scheduler Task Name],
task_name AS ObjectName,
app_id AS [Scheduler AppId],
app_name AS [App Name],
user AS [Scheduler User]
;
SELECT * FROM "public"."view_system_errors_warnings"
WHERE entry_timestamp >= '$(LastReloadTime)';
The error is "entry_timestamp" doesn't exists.
We did a test reading the same table:
SELECT process_name, logger, entry_level, message, exception, stack_trace
FROM "public"."view_system_errors_warnings";
Only 6 fields of the table and the error message was different. See the PNG file.
Any Idea or suggestion will be appreciate.
Gabriel
Hi,
Thanks for your assistance. We will update the Operation Monitor app according to support article.
But, we did the following test, we did a Select to “public”.”view_system_errors_warnings” with some fields, like: process_name, logger, entry_level, message and exception
And we received the following message:
ERROR [22P05] [Qlik] [PostgreSQL] (30) Error occurred while trying to execute a query: (SQLState 22P05) ERROR: Unsupported Unicode escape sequence.
DETAIL: \u0000 cannot be converted to text.
The same error message I found in the following link: https://community.pivotal.io/s/article/loading-data-report-error-unsupported-Unicode-escape-sequence...
This is due to design change in postgresql v9.4 (GPDB v6).
Any suggestion?
Hi, resolved this error? I have this problem too.
Is the operations monitor failing with the same error ? What version of software you are using and if possible attach the failed snap shot