Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
Ole_Dufour
Contributor III
Contributor III

Environmental errors, examples.

What is meant by "environmental errors"? Are they SQL errors? Can somebody provide me with some examples ? 
As a result we don't know how to configure this on our Oracle source and target database.

I'm talking about this screen:

Ole_Dufour_0-1695280012997.png

The documentation didn't help me much:

https://help.qlik.com/en-US/replicate/May2023/Content/Global_Common/Content/SharedEMReplicate/Custom... 


Thank you.

 

Labels (2)
1 Solution

Accepted Solutions
Arun_Arasu
Support
Support

Hello @Ole_Dufour 

Thank you for contacting Qlik community.

In general, environmental errors are considered errors that occur within the environment where Qlik Replicate is installed.

Below are a couple of examples that are considered environmental errors:

Network Issues: Network interruptions or slowdowns can disrupt data replication processes. Factors like network congestion, packet loss, or firewall configurations can lead to environmental errors in Qlik Replicate.

Hardware Failures: Problems with the physical infrastructure, such as server crashes or storage device failures, can result in errors and data replication issues.

Resource Constraints: Inadequate system resources like CPU, memory, or disk space can lead to performance problems and environmental errors.

Security and Permissions: Improperly configured security settings or permissions on source or target systems can cause errors when trying to access or write data.

Operating System Updates: Environmental errors can occur if there are compatibility issues with operating system updates or patches.

Concurrency and Locking: Issues related to concurrent access to data or locking conflicts can lead to errors during replication.

External Dependencies: Environmental factors, such as changes in third-party APIs or dependencies that Qlik Replicate relies on, can introduce errors.

We hope the above information provides you with valuable insights.

Best regards,
Arun

View solution in original post

2 Replies
Arun_Arasu
Support
Support

Hello @Ole_Dufour 

Thank you for contacting Qlik community.

In general, environmental errors are considered errors that occur within the environment where Qlik Replicate is installed.

Below are a couple of examples that are considered environmental errors:

Network Issues: Network interruptions or slowdowns can disrupt data replication processes. Factors like network congestion, packet loss, or firewall configurations can lead to environmental errors in Qlik Replicate.

Hardware Failures: Problems with the physical infrastructure, such as server crashes or storage device failures, can result in errors and data replication issues.

Resource Constraints: Inadequate system resources like CPU, memory, or disk space can lead to performance problems and environmental errors.

Security and Permissions: Improperly configured security settings or permissions on source or target systems can cause errors when trying to access or write data.

Operating System Updates: Environmental errors can occur if there are compatibility issues with operating system updates or patches.

Concurrency and Locking: Issues related to concurrent access to data or locking conflicts can lead to errors during replication.

External Dependencies: Environmental factors, such as changes in third-party APIs or dependencies that Qlik Replicate relies on, can introduce errors.

We hope the above information provides you with valuable insights.

Best regards,
Arun

SushilKumar
Support
Support

Hello Team,

"environmental errors" consider your Network or you put your Data folder on San or NAS storage . and Qlik replicate is not able to get the reply in term of read or reach to the Configured host. 

The Screen Shows .

1. How many time QR task try to connect/reconnect with Source endpoint.

2. After how much seconds wait; it will try to connect/reconnect with Source endpoint in case of any network issue.

 

Regards,

Sushil Kumar