Bulk data Mode TM1 server not responding

[Jodha]

We have nightly scheduled data loads running every day .

step 1) Dimension build
step 2) Enable bulk data mode
step3) Load data
step 3) Disbale bulk data mode

All TI process are triggered using normal Execute command .

For some reason TM1 server after enabling bulk load mode stop responding . It is not proceeding with rest of the data loads .
TM1 server hangs after step1.This is second time in this week i am facing this issue, It was working fine before .

There are no error messages registered in TM1 logs .

I know many people might have faced this kind of issue ,i am not able to find any resolution on this issue .

Can some one please point me to proper thread or suggest me any suggestions around this issue.

Waiting for you valuable inputs

I am using TM1 10.2.2 windows 2008 R2 server

[sypkens]

Hi Jodha

I believe we encountered this issue as well and our work around at the time was to force a restart of a the instance and then run the chore at which point the chore ran like a dream i.e. the outcome was that there were no logged-on users and hence the server only had to focus on running the chore.

We then had a colleague that stumbled onto the article below. I am not sure if we deployed it but it might be worthwhile looking into?

https://www-304.ibm.com/support/docview ... wg21496755


Regards

Jan

[nick_leeson]

A key question is what are you trying to achieve using bulk load mode ?

[sypkens]

Hi Nick

In our case we had 2 instances (both had Contributor apps). When you log into contributor the behaviour we saw was that contrib would athenticate against every instance listed with the admin server - regardless of where the particular contrib app was pointed to).

when the chore ran in one instance it would get interupted by users logging into the second instance Contributor (the chore would reset in some case as well). Bulk mode was an easy way of telling contributor to butt out and not allow the authentication against the instance running the chore.

Regards

Jan

[nick_leeson]

Perhaps Data Reservation is an alternative.

Don't have to butt your users out.

http://pic.dhe.ibm.com/infocenter/ctm1/ ... D5_2_6_4_4

[sypkens]

I dont believe data reservation addresses the issue we had. Data Reservation merely assists with taking ownership of a node once logged in in Contributor - and it should form part of your overall chore / process if you wish to update data for a locked node regardless.

in our case the simple act of logging into contributor (i.e. going to the contributor landing page http://<servername>:9510/pmpsvc triggered the process
}tp_initialise_session in every available contributor instance that has been configured and in the case of the instance where the chore was runnning looped certain processes).
By doing bulk mode in the instance running the chore it refuses a connection and the contributor instance (i.e. the available instance where no chore is running) just gives a message that that instance is not available and is in bulk mode.

[Jodha]

Thanks for the reply

Jan i will try your suggestion modifying config paramter.

IBM replied to PMR asking to add tm1s.log properties file which is provide by IBM to config folder and wait till issue repeats again so that they can debug it. Not much helpful.