Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
In Replicate Oracle source endpoint there was a limitation:
Object names exceeding 30 characters are not supported. Consequently, tables with names exceeding 30 characters or tables containing column names exceeding 30 characters will not be replicated.
The limitation comes from low versions Oracle behavior. However since Oracle v12.2, Oracle can support object name up to 128 bytes, long object name is common usage at present. The limitation in User Guide Object names exceeding 30 characters are not supported can be overcome now.
There are two major types of long identifier name in Oracle, 1- long table name, and 2- long column name.
1- Error messages of long table name
[METADATA_MANAGE ]W: Table 'SCOTT.VERYVERYVERYLONGLONGLONGTABLETABLETABLENAMENAMENAME' cannot be captured because the name contains 51 bytes (more than 30 bytes)
Add an internal parameter skipValidationLongNames to the Oracle source endpoint and set its value to true (default is false) then re-run the task:
2- Error messages of long column name
There are different messages if the column name exceeds 30 characters
[METADATA_MANAGE ]W: Table 'SCOTT.TEST1' cannot be captured because it contains column with too long name (more than 30 bytes)
Or
[SOURCE_CAPTURE ]E: Key segment 'CASE_LINEITEM_SEQ_NO' value of the table 'SCOTT.MY_IMPORT_ORDERS_APPLY_LINEITEM32' was not found in the bookmark
Or (incomplete WHERE clause)
[TARGET_APPLY ]E: Failed to build update statement, statement 'UPDATE "SCOTT"."MY_IMPORT_ORDERS_APPLY_LINEITEM32"
SET "COMMENTS"='This is final status' WHERE ', stream position '0000008e.64121e70.00000001.0000.02.0000:1529.17048.16']
There are 2 steps to solve above errors for long column name :
(1) Add internal parameter skipValidationLongNames (see above) in endpoint
(2) It also requires a parameter called "enable_goldengate_replication" is enabled in Oracle. This can only be done by end user and their DBA:
alter system set ENABLE_GOLDENGATE_REPLICATION=true;
Take notes this is supported when the user has GoldenGate license, and Oracle routinely audits licenses. Consult with the user DBA before alter the system settings.
Internal support case ID: # 00045265.
"C:\Program Files\NPrintingServer\Settings\SenseCertificates"
NOTE: Reminder that the NPrinting Engine service domain user account MUST be ROOTADMIN on each Qlik Sense server which NPrinting is connecting to.
The Qlik NPrinting server target folder for exported Qlik Sense certificates
"C:\Program Files\NPrintingServer\Settings\SenseCertificates"
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
This article explains how to set up OIDC authentication with Auth0 and map Auth0 roles to groups in Qlik Cloud.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.
Note down Client ID and Client Secret
exports.onExecutePostLogin = async (event, api) => {
const namespace = 'https://my-app.example.com';
if (event.authorization) {
api.idToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
api.accessToken.setCustomClaim(`${namespace}/roles`, event.authorization.roles);
api.user.setUserMetadata(`${namespace}/roles`, event.authorization.roles);
}
}
Opening a QlikView document fails.
The QlikView Server event log reads:
Document Load: The document C:/Documents/DocumentName.qvw failed to load because of no file access [3000]
This is caused by someone trying to open a document that they do not have access to (not NTFS or DMS permissions).
To resolve: Verify the user has all required permissions or if they are attempting to open the correct document.
A user is attempting to access a document they do not have access to, most frequently because of an outdated or incorrect bookmark.
What types of storage drives can be used for the Qlik Replicate and Qlik Enterprise Manager data folder?
Using unsupported storage types can lead to issues such as:
Qlik recommends using a block device (physical, virtual or iSCSI-based) for the Qlik Replicate and Qlik Enterprise Manager data folder.
After a DB2 LUW Upgrade, Qlik Replicate tasks fail with:
"ReadNextBufferWait: Error reading buffer Error at 'Reading log records': Unexpected Error. Original SQLCODE -1263: ' message SQL1263N The archive log file "S0673464.LOG" is not a valid log file for database "REP" on database partition "0" and log stream "0".
Reload the task using the DB2 LUW Endpoint.
Qlik Replicate saves the last save stream position when a task is stopped.
Since the DB2 LUW environment was upgraded, the transaction log will be different and the task (tables) need to be reloaded.
An SQL Lite file called DB2LUW_TIMESTAMP_MAP is defined in the tasks directory, which stores the LSN/LRI position with the timestamp for the given task. This file includes the old DB2 LUW transaction log which is pointing to the old DB2 transaction log version.
Opening a local QlikView document (.qvw) using the QlikView Desktop running on ClientOS in WebView mode fails. The Desktop client does not respond as expected and displays:
Lost connection to server.
Reconnecting
The error occurs if:
Upgrade to QlikView 12.90 (May 2024) IR or higher.
As a temporary workaround, turn off WebView mode:
Product Defect ID: QV-25106
While working with the Oracle source endpoint the Unique Index is not displayed in the Qlik Replicate GUI console.
The source table creation SQL statement is as below:
CREATE TABLE FBI2 (ID INTEGER, NAME1 CHAR(20), NAME2 CHAR(20), NAME3 VARCHAR2(20));
CREATE UNIQUE INDEX FBI_IDX2 ON FBI2(NAME1, NAME2, NAME3 DESC);
In the provided sample, the unique index is created as a function-based index. The DESC (default is ASC) property applied to NAME3 makes the index a function-based index (FBI). When querying the table index information, it's clear that the “SYS_NC00005$” field replaces the actual underlying field “NAME3”.
This is a limitation in the Oracle source endpoint, see Function-based indexes are not supported.
Hence the Unique Index cannot show up in the Task Setting GUI.
Case #00168364
Qlik Enterprise Manager (QEM) fails to monitor Qlik Replicate.
The following issues can be observed:
Possible error messages:
This is a known issue and Qlik is actively working on a patch. Please review the release notes for QB-26321 and QB-27571 for updates.
QB-26321 and QB-27571
QB-26321 and QB-27571
With Store Changes (see Change Processing) turned on for CDC tasks, Qlik Replicate tasks may crash or stop unexpectedly.
The following errors may be logged in the task log:
2024-07-30T09:53:22:497564 [AT_GLOBAL ]E: An exception occurred!!! (win32_exception_handler.c:109)
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: Backtrace at exception: !{C:\Program Files\Attunity\Replicate\bin\at_base.dll!4537ab...
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: exception code is 3221225477 (win32_exception_handler.c:112)
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: tid=22112 (win32_exception_handler.c:115)
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: exception as string is EXCEPTION_ACCESS_VIOLATION (win32_exception_handler.c:118)
Upgrade to 2024.5 SP02 (for Windows and Linux) when available.
To work around the issue:
Product Defect ID: QB-28312
Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID QB-28312 for reference.
In this webinar we will discuss:
- Qlik Sense Enterprise on Windows, deployment scenario
- Configuration best practices
- Important settings
Note: For information on deployment of newer product releases, see Deploying Qlik Sense Enterprise on Windows.
Q: It states not recommended to have share on same as node. VM site, SAN mapping a C and D drive to SAN, with C installation and the D drive shared. Is this still not recommended?
A: You should have a separate server for the fileshare for a multi node deployment. That is also to load balance the network traffic and TCP connections to your nodes. You can have on a single node your shared folder on D with your setup. SAN is supported.
Q: Is there a recommended "best practice" approach for a separate dev/test/prod server instance?
A: In this case 3 server cluster
Q: I am trying to install Qlik Sense February 2019 on windows server 2012 r2. So, I faced an error that server dispatcher installation failed. How to solve this error?
A: Open the logs in the %temp% folder, check for the ServiceDispatcher logs. It could be fileshare/database/powershell/user related. If you don’t see anything with value 3 you need to contact Qlik support and attach your log installation files.
Q: Is it possible to install Qlik sense and NPrinting in the same machine?
A: No that is not a supported scenario. In worst case you overwrite the Sense CA certificates while entering.
Q: If we are upgrading then we need to import the extensions from the QMC or we can just simply copy and paste the extensions in Extensions folder?
A: When you upgrade the extensions will stay linked in the DB, you do not need to reimport them, but you might have to adjust them to make them work with the new installation.
Q: Hi, can we get dashboard bundles with silent installation?
A: No right now there is no option for that. We have brought this to the attention via feature request to R&D and hope for an improvement.
Q: When we will be able to connect MySql DB to Qlik Cloud business directly?
A: I will reach out to product management, the current cloud options are limited, but there are some new things coming.
Q: Good day Sebastian, I'd like to know the needed network requirements to enable users from Domain B to use an already up-and-running Qlik Sense Server installation on Domain A. That includes being able to access an Oracle database running on Domain B, all from Domain A.
A: Sense users can be synced from more than one domain, as long as you have domain trust between the system.
Q: I will do a Qlik Sense v.3.2 SR 2 to February 2019 upgrade tomorrow. Any known issues I should know about?
A: If you upgrade from 3.2 SR2 to February 2019 directly there are many things which can go wrong, please contact support before you start. You need to do a few steps in-between.
Q: What kind of issue could occur if not using the .NET framework version 4.7.2?
A: e.g. QlikSenseUtil will not start. So, you can't change connection stings for the Repository Service.
Q: Some time ago there were a problem with the special characters in passwords for repository (both main and logging). is it solved?
A: Yes, more robust, but I would still not use an @ in the password
Q: A lot of my clients have IIS services on their server they want to use. This uses 443 standard and cannot be changed. Is there a way to avoid the standard 443 or 80 ports?
A: Yes, there is, just not under the installation. 80 is disabled by default and can be changed in the system once spun up. You can have 443 changed to another port, just disable IIS on that port during the install.
Q: We just upgraded to Nov 18 Patch 3 release and we created a new QLogs database (standalone) right before. Where can I turn on centralized logging? During upgrade process there was no option to enter the QLogs details.
A: On the help you will find the additional steps to enable Qlogs, after adding the DB. https://help.qlik.com/en-US/sense/February2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Deployment/Qlik-Logging-Service.htm
And also https://qliksupport.force.com/articles/000043238
Q: Does configuring centralized logging prevent single-node logs written to the file system?
A: No, it will log to both by default.
Q: How do we install Qlik Sense February 2019 with a remotely managed database and we can't change user rights?
A: Please contact support for help. There are some issues with Azure standalone Postgres DB instances in the February 2019 release, Support can offer a workaround.
Q: Hi, I've been trying to install Sense Desktop (only) on my laptop. It's saying the install was successful, but I can't see it I the installed programs in control panel. Do you have any suggestions please?
A: Qlik Sense Desktop is a per user installation only rather then per machine. Try to see if the files are on disk: (replace username with your userId form windows)
C:\Users\username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Qlik Sense\ Qlik Sense Desktop.lnk
C:\Users\username\AppData\Local\Programs\Qlik\Sense\QlikSense.exe
If you do not see them, please contact support.
Q: We tried to install it with a remotely managed database and the installation failed.
A: Please send us the installation logs so we can have a look.
Q: How to disable usage of port 4244 in dialog box “Edit proxy” for Authentication listen port? Just make it empty? What is impact on Monitoring apps or others? (Current Qlik Sense version is November 2018)
A: You can’t do that, you still need Windows authentication to work for Sense to validate the users on the system. Your Monitoring apps would stop reloading if you block it.
Q: I configured the file share in the same node of the central node. It is ok?
A: Yes, that is fine as long as you have a small deployment. Beyond 2 nodes you should move to a separate fileserver.
Q: Is what you talked about a brand-new installation? we have Nov 2018 installed so we just need to do an upgrade?
A: This was a new installation, and update has nearly the same but a few steps less. You would just have to do an upgrade from November 2018 to February 2019. Sometimes the Patches can’t be deinstalled automatically, then make sure to deinstall e.g. Nov 2018 Patch 1 first before upgrading.
Q: If we update Qlik Sense from Previous version and we have several Nodes - should we update Central first and Rim then? What will be the process of upgrade?
A: First you stop all the nodes, in the order all Rim, then Central node last. After that you would first upgrade the Central node, and then all the Rim nodes.
Q: How many engine nodes a central node can take?
A: You will only have one Engine service per node, but you can as much rim nodes as you want into the deployment. That is only limited by your license or the database performance.
Q: What license model is required for Multicloud?
A: Signed license model, which was introduced in the February 2019 release.
Q: Why do I need a shared folder for Sense?
A: The binary files for your apps and extensions for all the nodes are stored on this file share.
Watch the video here for more information https://qliksupport.force.com/articles/000028399
Q: Are there Docker install files for Qlik Sense Enterprise?
A: Not for Qlik Sense Enterprise, but for the Multicloud instances. Please reach out to your Account manager to get more information.
Q: How will antivirus program block our installation?
A: The installer has e.g. PowerShell scripts inside and they are running from %appdata%\local\temp which might be blocked and as a result the installation fails.
If you have installed Sense successfully then you need to add the following exceptions, please review: https://qliksupport.force.com/articles/000031189 and
https://qliksupport.force.com/articles/000028726 for more details
Q: After an upgrade, my monitoring apps are no longer working. Is there a reason this has happened?
A: There can be many reasons, please contact support. Review: https://qliksupport.force.com/articles/000036815
And
https://qliksupport.force.com/articles/000060688
Q: Could you please explain the shortly the port of the local dB of 4432 vs 5432
A: 4432 is the standard port for the database in Qlik Sense when using the inbuild database. If you have a standalone Postgres installation the standard port is 5432. Both ports will work with a Sense installation.
Q: General recommendation when is time to upscale QS?
A: When your users start complaining about performance, or you see that the engine need time to calculate heavy requests. Those are just two, but there is no general recommendation, like to it from 100 users onwards. That depends on your needs and your user’s behavior. Give us a call and we can set you up with the right person to discuss this further.
Q: Could you migrate directly from the November 2017 version to Feb 2019 one?
A: Yes, you can.
Q: Why, when the installer asks me to look at the log, why is there no link to the log?
A: The blue text usually brings you to the logs. If you do not see that one, please open %temp% and you should see them there.
Q: Upgrading Question. Integral reference problem when the repository service starts. Where to start checking? Thanks!
A: A good start point is Windows Event logs and C:\programdata\qlik\sense\log\repository\trace\Servername_system_repository.log
They should give you a hint, then just check our knowledgebase or contact us at the support, we are happy to help you out further.
Q: Can we update from the November release to the newest February release without a lot of problems?
A: Yes, November 2018 to February 2019 is not connected with a lot of problems.
Q: We are thinking about cloud deployment. To make it fully elastic, probably it is best to give each of our customer own dedicated environment. for example, we have 20 customers. is it possible to have 20 independent environments, but only 1 QMC?
A: That is the idea, but there could be an issue with the licensing in your model. Please contact the Account Manager for more details.
Q: Do I need to uninstall the antivirus during installation?
A: No just pause it, no need to uninstall.
Q: On which AD group should we put the users?
A: Prior to the installation in the Local Computer\Administrators group. The installer will add it in
“Qlik Sense Service Users” and “Performance Monitor Users”.
How to specify superuser password in a silent installation. (doesn't appear in spc.cfg xml file..)
Qlik_Sense_setup.exe [-silent] … {dbpassword="password}…
Just with the Setup.exe as a parameter.
dbpassword | [password] | Password for the database superuser that creates the user that runs the database. |
Q: Do we need a fresh installation of Qlik Sense Enterprise if we are migrating from one Qlik Sense server to another. My client is currently using services from External IT provider. Now Client wants to have QS enterprise back on premises. What to keep in mind doing this task.
A: Yes, you would do a fresh installation, and then import the DB of your old installation. For this you need to install the same version on the target system as you have on the source system.
Q: Can the file share be running on a Linux server? What kind of configuration would imply from the Windows server and Qlik Sense side?
A: Yes, we support it as long as your server can handle SMB 3.0, but not all distributions might work the same. As also not all NAS vendors are working. I was mistaken about this point in my presentation. The support was added for Sense, just not for QlikView.
See more information here: https://help.qlik.com/en-US/sense/February2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Deployment/Persistence.htm
Note: Qlik cannot verify support for all storage vendors, and recommends that customers test their preferred infrastructure. In the event of an issue arising that is attributed to storage, Qlik Support may request that customers replicate the issue on a Windows hosted file share.
For implementation advice which fits your needs please reach out to your Account owner or Qlik consulting services.
Q: Fileshare can be in the same central node?
A: Yes, that is possible, but if you get beyond a two-node deployment it will makes sense to separate the fileshare, not to have much traffic on the central node.
Q: Can you repeat how access and read logs stored in log-database?
A: You have 3 tables in the Qlogs database
public.log_entries
public.archive_entries
public.settings
the table "log_entries" contain following columns for the logs:
"id","entry_timestamp","entry_level","thread","logger","process_host","process_name","process_id","payload"
example line:
"1","2019-03-18 14:52:25.973511+01","INFO","11","Service.Proxy.Qlik.Sense.Common.Monitoring.HardwareInfo","QlikServer1","proxy",1760,"{""Description"":""Command=Start proxy;Result=0;ResultText=Success"",""ProxySessionId"":""0"",""ProxyPackageId"":""0"",""RequestSequenceId"":""0"",""UserDirectory"":""INTERNAL"",""UserId"":""System"",""ObjectId"":""0"",""ObjectName"":""Not available"",""Service"":""Proxy"",""Origin"":""Not available"",""Context"":""Not available"",""Command"":""Start proxy"",""Result"":""0"",""Message"":""Disk C:\\: Volume label: , Free space: 32221552640 bytes(30.01 GB(s)), Total disk space: 53160701952 bytes (49.51 GB(s)), File system: NTFS""}"
archive is used when cleaning the log database, the deleted entries will be stored defined amount of time and then getting cleaned out as well.
Q: Is advisable allocate Qlik Sense Server in DMZ? Why Y/N.
A: All nodes in a site, including nodes without an engine, require access to both the database and file share. In demilitarized zone (DMZ) deployments this may require opening additional ports, or you would have to add the DB and fileshare in the DMZ as well.
The Fast Change button may stop working after a QlikView upgrade. The button appears not to respond after being clicked.
By default, 'straight table' cannot be used as a fast change option if the table is a linked object. To confirm if a 'straight table' is in use:
Set RestrictLinkedTypeChanges at the below path:
Set the value as either RestrictLinkedTypeChanges=-1 or RestrictLinkedTypeChanges=<greater than the number of linked objects> (Stop the QVS service before making this changes) The other options is to unlink the objects (right click on the chart, and click 'linked objects>unlink this object)
The settings.ini may have been adjusted to allow this. These changes were reset to default after an upgrade. The settings.ini must be backed up and reviewed after an upgrade to ensure all custom settings remain intact.
Jira QV-25359
Due to an issue with MySQL ODBC Driver 8.0.027 to 8.0.033, empty TEXT columns may not be replicated correctly during Full Load.
Qlik Replicate
MySQL ODBC Driver 8.0.027 to 8.0.033
Empty TEXT columns may not be replicated correctly during Full Load. For example, if one table row contains a TEXT column with a value and the same column in the next row contains an empty value (but not NULL), both rows will display the value of the first row on the target. See Limitations and considerations | Qlik Replicate Help.
When the source table has a text column that is blank (not null) the data from the previous row that had data is duplicated.
As an example if have the following 3 rows:
1 'SOME DATA'
2 null
3 '' <---empty string not null
The the output rows will have the following:
1 'SOME DATA'
2 null
3 'SOME DATA'
To resolve the issue, downgrade to MySQL ODBC 8.0.026.
The ODBC parameter no_ssps can also be used to resolve the issue.
Set it to no_ssps=1;
Until MySQL resolved the issue, the parameter should be set on Full Load ODBC connections. See 5.2 Connector/ODBC Connection Parameters | dev.mysql.com.
Applying a transformation on a column and clicking Save does not save the changes. The transformation cannot be applied.
Resolution
This is fixed in the Qlik Replicate 2024.5 SP1 kit and later releases of Qlik Replicate.
Qlik Replicate 2024.5 SP01
Public share: https://files.qlik.com/url/qr2024050247sp01 (expires 9/30/2024)
Qlik Enterprise Manager 2024.5 SP01
Public share: https://files.qlik.com/url/qem2024050249sp01 (expires 9/30/2024)
QB-27669
While accessing the DB2z 13.1 as the source database, the IBM DB2 for z/OS source endpoint reports a warning message during the task startup.
The warning message in task log file:
[ASSERTION ]W: Replicate has not been certified to work with DB2 z/OS version '13.01.0000', and therefore any issues you may encounter with this version are not covered by your license agreement (db2z_ifi_api.c:880)
Upgrade Qlik Replicate to 2023.5 SP02, or higher versions such as 2023.11/2024.5.
Qlik Replicate is certified to support DB2 z/OS version 13 from Qlik Replicate 2023.5 SP02.
#00175112, #00173433
By default, Talend Remote Engine creates job execution logs in a directory below:
TalendRemoteEngineInstallationDirectory\TalendJobServersFiles\jobexecutions\logs
Is there any way we can change the default location of these logs?
This article aims at How to change default location of execution Logs for Remote Engine (R.E)
To change the location of Talend Jobserver files, Please follow below steps
After R.E restart, when new jobs are deployed from TMC you can see execution logs in new location
Qlik Replicate is set to apply prefix replacement to archived redo logs only and specifies file-level access to archive location, yet continues to use the online redo logs and may fail a task as per the following error:
The settings are done correctly, with only Replicate has file-level access to the new archive location checked:
000014626, 00164729
The direct export of QVD files stored on a Tenant is not currently supported.
In order to export a QVD from a Tenant it is necessary to use an external storage solution. This is achieved using one of the available Qlik Web Storage Provider Connectors.
This needs to be included in the Data Load script:
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
The Unified Hub functionality allows for links to QlikView documents (hosted via AccessPoint) to be published in Qlik Sense Hub.
This article covers the steps on how to deploy it in a QlikView and Qlik Sense Enterprise on Windows environment.
For publishing QlikView documents to Qlik Sense SaaS editions via the Multi-Cloud solution, see How to configure QlikView Multi-Cloud deployment and App distribution
Qlik Sense Enterprise on Windows, all versions
QlikView, 12.0 and newer
Note: The steps below illustrates and further details the main configuration steps mentioned in the video above.
In order for the server running QlikView Distribution Service (Publisher or QDS) to connect to the Qlik Sense machine, three settings need to be changed on the Qlik Sense server:
Note: This setting may have only been needed on earlier versions of the Unified Hub deployments and may not be needed in newer versions of Qlik Sense and QlikView.
Starting with all Qlik Sense services in a stopped state, complete these steps:
5. Save the file
6. Start Qlik Sense services
The next step will be to configure the appropriate security rule in order to allow users to view the documents which will be published.
The next step will be to export a set of certificates from Qlik Sense for use by the Publisher machine for use in establishing trust for the distribution.
4. Navigate to the client.pfx file and import it
5. Repeat the import steps for the server.pfx file
6. Now select the Trusted Root Certification Authorities section and import the root.cer certificate
7. Once all the certificates are installed, go back to the QlikClient certificate in the Personal section and double click on it. This will open the properties of the certificate.
8. Now go to the Details tab and scroll to the thumbprint. Copy this value to a notepad window
At this point the distribution should complete successfully and now you should validate that things appear as expected on the Qlik Sense side. Assuming that you’ve distributed the document to at least the user account that you are using then you should see the document appear in the QlikView documents section of the Hub which should have magically appeared:
If you are encountering further issues, then contact Qlik Support for a deeper level of troubleshooting.