Marcin,
you have to make embedded connection to the zt1 and create at least one user
there
(probably you need sysdba, probably no):
isql zt1
create user sysdba password 'pwd';
Regards,
Vlad
Hi,
If you have big sort files (you can check their existence manually in
temp folder or use HQbird FBBDataGuard to monitor them for you),
increasing TempCacheLimit to fit all of them can speed up sorting
queries (with GROUP BY and ORDER BY, for example).
However, the better approach is to
Hey
Thanks for the clarification, that is also the only explanation that made
sense to me, after i had a look at the optimized config published at ib-aid.com.
Alexey perhaps you can answer this, is there anything to gain from configuring
TempCacheLimit to use 2, 4 or 6Gb? Or perhaps more
Hi,
I remember I answered incorrectly that time :)
TempCacheLimit is always per server instance.
For Classic it means it is allocated per each connection (since each
connection has own server process), for SuperClassic and SuperServer
temp space will be shared between connections, since
