TM1 Forum

Hopefully someone has some ideas on how I managed to crash my 9.5.1 x64 Dev server with TI..
I am pretty sure this is not the Oracle/Unicode issue this time - just a mistake in my script.

Background:

Using the sophisticated 'Turbo Integrator' editor, I blindly smashed out a few more lines in my previously working TI process.. (is it just me or would features like easy indentation, sectioning, step through & debug be nice to have or is a plain text editor from the 60's the preferred?).

Anyway, I hit save.. oops a typo in a variable; corrected that and Hit save.. success!

Hit Run.. processing records window pops up and it starts grinding away on a thread for maybe 10 seconds then.. the tm1 server just CRASHES - stops dead. No warning, no TM1ProcessError log file for the process.. and the tm1server.log has no entries in it since start up.

Can anyone spot anything obvious in the attached process? I had just added the lines relating to 'Census Date' (confirmed enrollment) records..

I have logged with Cognos - will post an update if and when I get one if someone on this forum doesn't spot something.

First of all, nothing you do in TI should EVER be able to crash the server. That said, we all know there are issues that pop up now and then with releases, and being that 9.5.1 is fairly new, it is possible something has been introduced. However, TI, in the past has been pretty stable when exeucting; so I would first look at what rules you have running on Census Date.

I have seen cases where there are circular references in the rules and then when you populate it, it ends up crashing the server.

If you don't have any rules that run off these values, then try putting in some ASCII outputs and see where the last point of failure is. Remove it, and run again. If the problem goes away, try manually populating that cell and see what happens.

My sense is that it is not due to the TI script itself; but again, 9.5.1 is new.

Good Luck!

Hi Rollo,

I'm not convinced this should be within the bug section of the forum. I may move it in to the main TM1 forum,

Jim.

Thanks blackhawk. No issues with the rules - all target cells are write-able. Even commented out the rules just in case - same issue. And tried creating a new process and copying in the code, section by section. Same result. Have had server crash issues with the 64bit Oracle 11G driver and TI with Unicode on. Tried it both on and off - same issue. My other processes run just fine (with Unicode off).

Calls to the Oracle ODBC client can crash the server. I know it shouldn't but it does.

It is due to SQLFetchScroll.

You can change the way TM1 does it SQLFetchScroll by adding one of these two options to
the tm1s.cfg file: UseSQLExtendedFetch=T or UseSQLFetch=T

try this and let us know how it goes

Laenen,

Have you noticed this problem on 9.5.1? I know of some earlier versions where this was true, but it seemed to be fixed in the latest version of 9.4, which we are using. Is this a regression issue?

yes it happens in TM1 9.5.1
OS 2008 R2 x64

I am not sure this is the same issue that you are referring too.

rollo19 wrote:Using the sophisticated 'Turbo Integrator' editor, I blindly smashed out a few more lines in my previously working TI process.. (is it just me or would features like easy indentation, sectioning, step through & debug be nice to have or is a plain text editor from the 60's the preferred?).

Sorry, not a help with your problem but CTRL+i does an indent in TI.

laenen wrote:Calls to the Oracle ODBC client can crash the server. I know it shouldn't but it does.

It is due to SQLFetchScroll.

You can change the way TM1 does it SQLFetchScroll by adding one of these two options to
the tm1s.cfg file: UseSQLExtendedFetch=T or UseSQLFetch=T

try this and let us know how it goes

Thanks for this laenen - I tried, UseSQLFetch, UseSQLFetchScroll & UseSQLExtendedFetch (only one at a time) - but with any of my process still crashed the server.

Then I split the process into 2 - exactly the same lines of code, just segregating it into one re Start Date and one the Census Date - and it works. Perhaps it was getting tangled up with the dates, not sure how as the the SQL works fine and all dates were defined with unique variables from SQL through to the DATA script.

Thanks Laenen, UseSQLExtendedFetch=T did the trick for me.

UseSQLExtendedFetch=T also worked for me on 9.5.1, win2008 R2 64 bit

Hi rollo19, atxchillin

I am also on TM1 9.5.1 on x64 on Win03 R2 and having the same issue.
Will now be trying writing UseSQLExtendedFetch=T in the TI script.

Can I also know what is the hotfix version installed on your server?
I am currently on hotfix 12 (951_HF12_x64_server) and planning to install hotfix 16.

Please advice. Thanks