QlikView Server (QVS) reads and writes in PGO files on regular basis in order to keep updated on server settings and configurations.
- BorrowedCalData - Leased license
- TicketData - Ticket details
- IniData - Server settings.ini details
- ServerCounters - Statistics counters
- CalData - CAL allocations
The QVS is a multi-threaded process, where the threads autonomously
will access the varies PGO files based on process needs. A PGO file can only be accessed by one thread at a time. Any concurrent access is declined, and a "PGO file sharing violation" is logged as a warning in QVS event log. The warning message should be noted, but commonly requires no action. In case of a problem or error, the warnings can be helpful in terms of troubleshooting and identifying the root cause.
There are several aspects that affects the number of PGO file lookups, and thereby increase the possibility of a sharing violation warning.
- PGO file sharing violation warning can occur with only one QVS node, since a single node has multiple process threads.
- QVS will access PGO files even without active user sessions
- User sessions adds threads to the QVS process. More users = more PGO file lookups
- PGO lookup is also affected by the number of published application in the QlikView access point. More application = more PGO file lookups
QlikView 11.20 SR11 and later has significant stability improvements which lowers the sharing violations and and also minimizes the risk for the sharing violation warnings to turn in to a actual problem.