This note is more as a reminder to myself than anything else…perhaps, it’s time to phase out 9i clients at our site for good, at least on workstations used by our developers. Today, I found a bunch of trace files with:
... *** SERVICE NAME:(SYS$USERS) 2009-05-06 11:49:42.540 *** SESSION ID:(291.1143) 2009-05-06 11:49:42.540 klaflr called ...
Based on my past experience I knew that this kind of trace files containing klafrlr called are a direct consequence of running SQL*Loader 18.104.22.168 in direct path mode. No errors at the user side, thought. It’s just annoying to purge trace files. As a short-term solution I’ll ask part of our team that is still using 9i client to run SQL*Loader from our network based 10g client installation point, but the proper solution is to move on and replace all those old workstations with the ones that include 10g client.