ETL and Data Integration tools - Modern ETL software for everyone

We have VI Enterprise. I have some packages scheduled to run every 90 minutes. VI is freezing every other day. I have to open task manager and kill the program that way ( is the only way). There is nothing on the logs specifying a problem (since application freezes and nothing is logged (I’m assuming)). Is there somewhere I can look to see why or where the program is freezing?

We ran packages individually and they all run fine. We are exporting data from Visual Fox Pro and importing the data into MySQL (Updating about 38K rows and inserting about 100 per run). We have a dedicated server with plenty of memory and processing speed to run VI. We also inspected the Database server and there is no stress from the DB perspective.

Any suggestions?
Thanks,
Michael

Hi.

It could be a problem of our software or repository database problem.
For example Sql Server Transaction log is full.

Also how big is your log files?
I saw some examples when too many records we rejected so it was not possible to exted log file anymore.

Is there any records in log screen saying that package is being executed when you know for sure it is not.

What is memory and processes consumption?

Just to confirm is your repository database MS Sql Server?

Is there sort of magical number like we were able to execute package 70 times after that it fails all the time?

I will try to build same environment by running packages non stop.
May be it will give me an idea what is going on.

Mike

Also how big is your log files? Right now is at 4 KB

I saw some examples when too many records we rejected so it was not possible to extend log file anymore.

Is there any records in log screen saying that package is being executed when you know for sure it is not. No.. Just says “connected”, “Executing” and the source DSN when running. Once it completes, it looks as if nothing is running, but program is locked up.

What is memory and processor consumption? I did not look at that when program froze. I will keep an eye on it next time it happens.

Just to confirm is your repository database MS Sql Server? MS Access

Is there sort of magical number like we were able to execute package 70 times after that it fails all the time? Is one package containing 3 other packages. It executes every 90 minutes. Program freezes every other day or so.

Also, packages continue to fail when running on scheduler. If we run package manually, it works fine. Any news on this one? Thanks

Michael

MS ACCESS repository is ok for development but not robust enough for LIVE systems

Try using SQL server or oracle as repository instead

Mike