Currently in kdb + tick setup at EOD rdb gets saved to disk in /log/sym folder. Current start hdb script : “q sym /log/sym -p 5012”. Want to change the hdb folder from “log/sym” to “hdb”. Changed the hdb script to “q sym /hdb -p 5012”. Still at EOD tables get written to old dir. Any clue why?
Which script are you loading?
You’ll need to restart your tickerplant. The tickerplant takes two arguments: the schemafile and the name of your hdb directory - it is this you want to change, not the hdb start-up command. Your tickerplant start-up command probably looks like:
q) q tick.q sym /log/sym -p 5010
so you’ll want to change that to
q) q tick.q sym hdb -p 5010
Also your HDB won’t be saved down until it hits end-of-day, but you can manually trigger this by invoking .u.end[.z.d] in the tickerplant.
Hope this helps
Jemma
Hi Jemma,
My tickerplant start-up command looks like:
q tick.q sym log -p 5010 -t 1
here log folder is where tickerplantplant logs go and log/sym is current hdb.
If i change this to point to “hdb” where would my logs go? is there a way to mention dir for tickerplant logs and hdb?
Thanks
Hi If you change the second parameter to point to =E2=80=9Chdb=E2=80=9D, then = your logs will be saved in this directory, with the end of day write down b= eing saved down to hdb/sym. In a normal kdb+ tick setup, the log and hdb di= rectories are intertwined and the file structure is difficult to change wit= hout editing tick.q It is possible to edit tick.q and allow for further configuration, i.e. do = as you wish, or you could google for a contribution kdb+ framework on GitHu= b that would wrap around kdb+tick to provide more functionality. Kind Regards, Jemma
Thanks a lot!!