Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Recent Documents
-
Qlik Fix: How to use Automated Log Cleanup in Replicate
This video demonstrates to how to use automated log cleanup on Replicate. Automated cleanup simplifies the process of purging outdated logs in Replic... Show MoreThis video demonstrates to how to use automated log cleanup on Replicate. Automated cleanup simplifies the process of purging outdated logs in Replicate, requiring just a few simple steps.
Transcript
Hi and welcome to Qlik Fix.This video will demonstrate how to use automated log Cleanup in Replicate.Within the replicate UI, in the top left corner, click the drop- down menu.And choose Server. Under 'Logging" choose 'Log file Management'.Enable 'Automatic Log Clean Up'. Specify thedays that you would like, and the system will purge the logs older than those days.Thankyou! -
Qlik Fix: How to add a table to logstream task on Qlik Replicate
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos. Environment Qlik Replicate ... Show MoreThis video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
Environment
- Qlik Replicate
This video demonstrates how to safely add a table to an existing Log stream task in Qlik Replicate without affecting the parent tasks.
Here is a link to more information in the Support Knowledge Base
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.
Transcript
Hi and Welcome to Qlik Fix
This video will demonstrate how to safely add a table to an existing Log stream task in Qlik Replicate.
Here is an example Log Stream Staging or Parent task
With a PostgreSQL Source and a Log Stream target already configured.
There are three tables: Branch, Branch Supplier and Csub Test that have been fully loaded.
The task is running and Change Data Capture or CDC is in progress.
Here is the child task that also points to PostgreSQL for the full load and then the log stream for CDC changes.
It’s using a File target for this demo.
In order to add a new table without impacting other tables,
First, stop the parent task.
Notice back on the child task, there is a warning log message stating that changes are not being captured.
Once the parent task is restarted the child task will pick up and continue where it left off.
Now stop the child task.
Back to the parent task, click on Table Selection to choose the table to add
Search, the trailspace table is the one that will be added. Add it with the arrows, OK.
Save that with the new table added.
Now from the Child task, Table Selection, Search
Notice that this new table isn’t available on the child task yet, as the parent task hasn’t been restarted yet.
Now from the Parent task, select Run > Resume Processing.
This will pick up where it left off with the original tables, and it will initiate a Full Load on the newly added table.
You can see this demonstrated with the different load time stamps of 1:08 for the original three tables and 1:17 for the fourth table.
Now that the parent task has completed a full load on the new table,
Go to the child task, table selection, search, and now the new table is available.
Bring that over, click ok.
Save.
And Run > Resume Processing on the child task.
Again, it initiated a Full Load only on the trailspace table, and not impacting the original tables.
Now Change Data Capture is running.
I’ll just add some inserts into that new trailspace table from PGAdmin to demonstrate this.
Qlik Replicate picks up those changes on the parent and child tasks and applies those changes to target.
I hope that helped.If you'd like more information
Take advantage of the expertise of peers, product experts, Community MVPs and technical support engineers
by asking a question in a Qlik Product Forum.
Hiding in plain sight is the Search tool.
This engine allows you to search Qlik Knowledge Base Articles,
Qlik Community forums,
Help dot Qlik dot com, Qlik Gallery,
multiple Qlik YouTube channels and more, all from one place.
There’s also the Support space.
We recommend you subscribe to the Support Updates Blog,
And learn from Qlik experts via a webinar, like Techspert Talks or Q&A with Qlik.
Thanks for watching.
(music)
Nailed it!
-
Qlik Fix: How to Find Qlik Connector Logs
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.This video demonstrates how to fi... Show MoreThis video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video demonstrates how to find two different types of Qlik Connector log files: the Connector logs themselves, and the Driver logs.
Here is a link to more information in the Support Knowledge Base:
Article - How To Collect Logs From Qlik ODBC Connector Package
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.
#QlikSupport
Video Transcript:
Hi and welcome to Qlik Fix.
This video will demonstrate how to find the two different types of Qlik Connector log files, the Connector logs themselves, and the Driver logs.
Both types of log files will be necessary when investigating a Qlik Connector related issue.
The default location for Qlik Connector logs is on the C: drive
Program Data, Qlik, Custom Data.
There is a separate folder for each connector or connector package.
In this example, we’re be looking for an error with a connection to Microsoft SQL server, which is part of the ODBC Connector package.
The name of the log file begins with the name of the server machine where the Qlik Connector is installed.
Opening the log file, and scrolling to find the error message I’m interested in,
There was an error at this time, and it was a ‘Login failed’ error.
The connector log indicates the specific driver that was used for this connection,
in this case it’s MS SQL server, mssql.
That will be useful for the next step of turning on Driver logging.
By default, Driver logs are disabled.
To enable them while troubleshooting, Open the registry editor,
Locate the registry entries under Local Machine, Software, Qlik.
This folder contains subfolders for every driver that comes bundled with the ODBC connector package.
We want to look at the MS SQL Server, so locate this.
All of the subfolders have the same structure and similar registry settings.
Adjust the Log Level and Log Path settings.
The log level can be a value from 1 to 6, with 6 being the highest level of logging.
For troubleshooting connections, set this to 6.
It’s recommended to use the same path as the connector logs, just to make it easier to find all connector logs.
Copy that folder path.
Paste in the registry value for Log Path.
Save.
The next time the connection is attempted, the driver log file will be generated.
The file is called Qlik Server ODBC Driver.
There is a lot of information and tracing date in these files.
Be aware when driver logging is enabled, and disable them once troubleshooting and log file collection has been done.
The file size for these logs even when everything is working fine is quite large and will affect performance in a production environment if left on.I hope this helped.
If you’d like more information,
Take advantage of the expertise of peers, product experts, and technical support engineers
by asking a question in a Qlik Product Forum on Qlik Community.
Or check out the Support Programs space.
Here you can search for answers in the Support Knowledge Base,
Learn directly from Qlik experts via a Support webinar, like Techspert Thursdays.
And don’t forget to subscribe to the Support Updates Blog.
Thanks for watching.Nailed it!
-
Qlik Fix: How to Fix Script Log Download Error
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos. This video will demonstrate how... Show MoreThis video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video will demonstrate how to resolve the insufficient Priviledges error when downloading script logs.
Here is a link to more information in the Support Knowledge Base:
https://support.qlik.com/articles/000080215
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.
#QlikSupport
-
Qlik Fix: How to Collect Windows Event Logs
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos. This video will demonstrate how... Show MoreThis video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video will demonstrate how to manually collect Windows Event log files. You will need to be on the Windows
machine where the issue took place, and know the time frame of the incident being investigated.Here is a link to more information in the Support Knowledge Base:
https://support.qlik.com/articles/000007495
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.
#QlikSupport
