Jobs & Executions

how is it possible to have the job stuck with status “waiting”, and if I try to manually run the job, I get the error “job is already queued“i’m running TX version 6675

Hi Following an upgrade to the latest version of TimeXtender (6675.2) on one of our customers environments I have since had a problem where some of my scheduled jobs do not run at their scheduled times. When digging about I noticed in the event viewer the following; Rerunning the [TimeXtender Execution Server Configuration 6675.2] tool has since resolved this particular issue but I still have issues with the scheduled jobs. I have also deleted and recreated the problematic jobs but this did not resolve the issue. Running the jobs manually work fine. Please advise on next steps

Ik have one job running and then started a second job manually. However for some reason the second jobs keep waiting. The both run on the same execution server but why does not it start a second job. Is there a setting which prevents the second job from starting or happens this only if you start multiple jobs manually?

I’m in version 6590.1 I manually started a job. However when I look in the execution log from that job I don’t see an active running job.If I look at the executions then I can see in that log that an execution is runnning. What do I need to do to be able to see the current running job or is it a bug that running jobs are not visible? (then the status ‘Running’ which you can toggle does not make much sense in the ‘view execution log’ window). greetings, Roy

Hi, I activated Trace to text file. I get logging in the file when deploying and executing objects manually. But nothing when running Jobs.Is it possible to use Tracing when running jobs. If so, what have I missed.BRAnders

I am having some issues with the transfer step when loading incremental using direct read. The problem seems to be that the generated procedures do not utilize indices on the underlying tables, resulting in full PK scans for every run. I was especially having problems when running on azure general compute. Switching to hyperscale helped some, but the transfer step still uses approx 40sec scanning ~90m rows causing bottlenecks. When using ADO.NET I could set an index on the incremental rule-field speeding up the search to <1sec. The execution-plan generated by TX looks like this: Here we get a PK index-scan even when there is an index on dw-timestamp. Testing on a subset of the data (~10mill rows): Adding the option(recompile) to the procedure results in the procedure using the dw-timestamp index: Is there a good reason for why these procedures are generated without the recompile flag? Is it something that could be added in a later release? And is there a way to work around this other t

Hi Team, I am getting the follwing error while executing the table. Please note i do not have a column named ‘ORDER’. I have no idea what it is refering to.

Hello, TimeXtender 20.10.31.64ODX: 20.10.31 We are currently running a database on hyperscale with 12vcores and premium memory optimized hardware. ODX is a data lake. We are running execution packages on 4 threads and we want to reduce our odx transfer times as that is out biggest impact right now. This is an example of a load. I am seeing long ODX transfer times for very small tables that I cant find the cause of or explain. We have alot of small tables (see example below) that is taking 1-3 minutes, while some tables doing data cleansing on 1million + rows is doing it in the same amount of time. See this small table that is 400 rows, no transformations and only 10 columns. I can see we are peaking log io at 100% during certain periods. However, that seems to be during the later parts of the loads and not during odx transfer in the start. Is there any thing that can cause this or possibility to improve it? Thank you,Victor​​​​​

I have been playing around with the on-demand load and set up some SQL Sources to use this. When I right-click Execute a table in MDW that loads from an on-demand source (TimeXtender SQL Source, ADO.Net transfer) I do not see any new extract to ODX - so I decided to run a Job: I subsequently right-clicked a Job that reloads my MDW layer and chose Execute. If I try to Execute again I get a message “The job xxx is already queued”, it does not ever seem to Execute the job however. Is there somewhere where I can see the job queue?

Good morning Yesterday on the development vm I created a job to be executed on a production vm (which has the related instance marked in the execution server). However it did not run last night. Is it necessary to log in in TimeXTender desktop in the production vm for the job to become active on that vm?

I have a job that reloads a DWH instance that seems to be stuck on ‘Active’. This job is months old and may have been killed by a VM being shut down automatically. This job blocks executions with a ‘Job already queued’ error. Is there any way to remove this from the queue?

Hello, I have a data export object/task. I have created an execution package that runs this export. When I start this execution via a schedule it fails with this error (table does not exist): Execute ReaturnPortefeu:Info:Initialized -Execute ReaturnPortefeuExecute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_Export:Info:Initialized -Execute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_ExportFill Data Export Table 'vw_ReaturnPortefeuille_Export':Error:Failed -Fill Data Export Table 'vw_ReaturnPortefeuille_Export' 'Failed' The table vw_ReaturnPortefeuille_Export does not exist! When I start the execution manually (right click and execute) it works without issue. Execution log The source table for the export is a view: Source table Why does it fail when scheduled and not when run manually?

When choosing a execution job, just a single execution job, it’s grayed out and I’m not able to choose it.it’s deployed and the execution jobs works, when I run it manually. I’m running Timextender version 6590.1

I have set up two completly new enviorments in AZURE.Project name is same in both (i also have tried to append _PROD in Production) Why is this an issue? How do i come around this?

Hello, I added an execution package to my production instance. I want to add it to a certain job, but that job cannot find my package. In fact, it finds all packages except for the one I just added. How can this be?

Hello, In Timextender there is a report called ODX Execution Log (see image). I was wondering in which tables the underlying data is stored. My company has a dashboard / chat bot that we use to check on our nightly DWH executions. For this we use the tables ExecutionPackageLogs, ExecutionPackageLogDetails, Projects, etc. I want to expand these reports with data regarding the ODX Transfer Tasks. I checked most of the tables in the metadata database (e.g. ScheduleJobs, ScheduleJobLogs) but I was not able to find it.

Recently we identified that our Azure SQL Database Backup Costs for our TimeXtender environment are very high, almost even higher then the regular storage costs itself. We now try to minimize these Backup Costs. We already minimized the Backup Retention policies: Now, when analysing some Backup data in the Azure Portal we found that the Log Backup Storage Size is growing the the multiple TeraBytes, even though our PROD database uses around 28GB. Does anybody know how we can further analyse and minimize these backup costs and data? I found the following regarding the transaction log, but I can't seem to dive in the transaction log/size per table or execution for example. -------------------------------------------------------------------------------------------------------------------- In Azure SQL Database, transaction logs record changes made to the database to ensure data durability and provide for features like point-in-time restore and disaster recovery. Various operations within A

I want to start an Execution Package at another server. I have attached the PS1 script. This script is working on the TimeXtender server. But not on our Qlik server. We use the same credentials. Also the credentials have access to the timextender.exe and the shares mentioned in the script on our Qlik server. I think the parameters package name and project name are not recognized when starting the script on an other server. Can you help me out to start an execution package on an other location then the timextender server?

Hi, We are running Timextender 6536.1 with execution server 6536.1 on on-premise sql server 2019. We seems to be having some strange behaviour with the “Manage schedule” option in with editing a job. Whenever we open the schedule it seems to trigger the job itself. I don't know if others experienced the same. I also don't know if it is related to Timextender 6536.1 since we had to do a lot of updates and configuration changes to the server lately due to a tempdb problem. Below I added a screenshot of the option, it applies to any job not only the odx one I'm highlighting.

One of my clients has a file data source that arrives at unpredictable times of the day. Has anyone found a good way to external-trigger-load such data source when it arrives? E.g. Webhooks, Logic Apps, ... The question is for 20.10.43, but I’m equally interested in hearing if there are solutions for v6284.1 as we’ll be moving in that direction. Thanks!

Hi everybody, Probably unnecessary but for the ones living/working in Europe I just wanted to inform that daylight saving time will change to winter time this weekend. This means that for those who have an ODX server or the “new” version (6XXX) of TimeXtender, the scheduled tasks/jobs will take place one hour earlier than currently set. This also brought me to the question how we could automate this? Any thoughts about this? Maybe an option in TimeXtender to use local time instead of UTC? Kind regards, Devin

Hi all, We experience a weird issue where our execution package seems to run itself? This happens for a total of 3 times in the execution. Then, when it succeeds it'll kick off the next package where it will happen again. This just started to occur in the past week, before everything worked normally. Has anyone else experienced this? This is the setup of the package. Any help would be appreciated.

The %Status% and %ExecutionPackage% work nicely in the subject line of notifications but I can’t make the %Instance% parameter work. Does anyone have a fix for this? (aside from creating instance-specific jobs/notifications and type the instance name in the subject line)

Hi Folks, I have a painful process that involves uploading csv files into my ODX on ad-hoc basis. In the DSA, i use transformations to pull the existing fields apart into various new fields. This table has history enabled to track when key values change. I then push to the MDW, minus some of the ugly data and using SCD To and From dates to track changing dimensions. A new set of entries with some extra parenthesis broke my job. I have a new set of case statements to deploy to the DSA history table, but as I went to deploy it, I panicked. The normal deploy and execute for a table without history will clear existing data and reload from scratch. Does the same happen with a history table? This table would be a nightmare to rebuild. TX version 19.11.7.64

I have set-up an Execution job that builds a table based on a view. The view generation is in DSA. The tables in the view have saperate Execution package that runs (before this job) without failing.Because of the limitations on how often the data can be extracted with API-endpoints in DSA_ tables, the following Execution job failed previously.I wanted to exclude the tables that are already updated so i have defined the tables that i dont want to run. Is this the right way to do it?