TM1 Forum

Hi,

I have made some changes in the TM1 configuration ( before this i had no problems, this changes where made to optimize the run time).
I have changed Maximum Core Cube Load from 0 to 2, persistence feeder = T, and feeder optimization.

Now when a user is trying to load data, the TM1 may crash. This is happening 1-2 times a day.( we can have 5-6 load successful then for no reason when another load starts is crashing.
Also the TM1 crashed when no user was loged in and no process was running.
What can be the cause of all this? Did the changes i implement are the cause?

Thank you.

What happens when you revert to the previous parameters? Are you monitoring memory usage? Anything in the log files?

Hi, thank you for fast reply. I didn t try to revert the changes.
The memory is not the issue, because it was plenty of memory when it restarts.
this is all that the log returns.

TM1.Server Closing...
TM1.Server Saving...
TM1.Server The server is coming down...
TM1.Server TM1ServerImpl::Destroy: disconnect clients
TM1.Server TM1ServerImpl::Destroy: Deactive all chores
TM1.Server Terminating Admin Server poller thread.
TM1.Server TM1ServerImpl::Destroy: Save server data
TM1.Server TM1ServerImpl::Destroy: destroy chores
TM1.Server TM1ServerImpl::Destroy: destroy processes
TM1.Server TM1ServerImpl::Destroy: destroy blobs
TM1.Server TM1ServerImpl::Destroy: destroy sets
TM1.Server TM1ServerImpl::Destroy: destroy groups
TM1.Server TM1ServerImpl::Destroy: destroy clients
TM1.Server TM1ServerImpl::Destroy: destroy cubes
TM1.Server TM1ServerImpl::Destroy: destroy dimensions
TM1.Server TM1ServerImpl::Destroy: destroy connections
TM1.Server TM1ServerImpl::Destroy: Destroy unregistered objects
TM1.Server TM1ServerImpl::Destroy: Commit changes
TM1.Server Server shutdown

This is what i get form the Log file.

AnonimusMax wrote:Hi,

I have made some changes in the TM1 configuration ( before this i had no problems, this changes where made to optimize the run time).
I have changed Maximum Core Cube Load from 0 to 2, persistence feeder = T, and feeder optimization.

This is just a guess, but have you set the MaximumCubeLoadThreads parameter to the number of cores - 1? Or does your server have only 2 cores? If so, that may be the issue. As the IBM documentation on this parameter explains (http://www.ibm.com/support/knowledgecen ... s_tm1.html) You should set the value to be the number of cores - 1, to allow for the leftover core to run other applications.

Thanks.

Hi,

My server is a quad core. now we set the value back for the number of MaximumCubeLoadThreads to 0, but the TM1 still is crashing. we still have persistence feeder = T, and feeder optimization.
What can be the problem?

Thank you

Just check your disc is not full, turning on persistent feeders can generate massive files.

Have you done your feeder optimization (maybe multiple steps) after you had turned on PersistantFeeders? Then your .feeders files contain all versions of feeding that you have tried. In such a case you should force a recreation of these files. Fastest way is to delete *.feeders while the server is down.

Since crashing is pretty clearly a bug in the product, you'll find IBM to be the best resource for solving this. That being said, any chance you're using Bulk Load Mode at all for any of your data loads?

Hi

We are only using bulk load mode for an export to Oracle. For loading data into TM1 we don t use Bulk Mode.
we did t do any feeder optimization.The disc was almost full and i deleted the files.

Thank you

AnonimusMax wrote:We are only using bulk load mode for an export to Oracle.

I've never heard of BLM being used for data export before. What's the reasoning?

BrianL wrote:

AnonimusMax wrote:We are only using bulk load mode for an export to Oracle.

I've never heard of BLM being used for data export before. What's the reasoning? Was this a recent change?

No it was not a recent change. We export data from a cube intro a csv and after that we load the CSV bulk mode intro ORACLE. Before that we were righting line by line from TI directly into Oracle and it took a lot of time. This was a optimization.

The benefits provided by bulk load mode would't help when creating an export file. There would be no locking involved and keeping people from logging in to TM1 during the export would provide only a minimal minimal benefit.

BTW, why did you say you were loading data when in fact you are exporting, not loading? You just wasted everyone's time with false information.

tomok wrote:The benefits provided by bulk load mode would't help when creating an export file. There would be no locking involved and keeping people from logging in to TM1 during the export would provide only a minimal minimal benefit.

BTW, why did you say you were loading data when in fact you are exporting, not loading? You just wasted everyone's time with false information.

Some one asked if i use bulk load mode. I gave an example where i used this bulk load.
THE PROBLEM is when a USER LOADS data intro the cube, not exports.
read all posts....

Hi,

The server crashed again 2 times.( i have MaximumCubeLoadThreads commented now and persistent feeders turned on)
I don t use bulk load mode when i right data into TM1.
I load the data, then I do some calculation and after that I have a process that export a CSV file.Then a process runs a bat file with a oracle command that imports bulk mode into the oracle DB. ( this is my master load process ).
There are moments when two bulks are inserted into Oracle DB at the time, but i thought this can not be a reason.
Can this bulk export causing the crashes?

Thank you,

This is information from my last log.
All my client confidential information will be replaced by: confidential
The last executed actions before crash were 2 automatically chores that start a data load.

27756 [] INFO 2017-02-02 16:48:20.961 TM1.Chore Chore "confidential" time = 0.91 seconds
27756 [] INFO 2017-02-02 16:48:20.961 TM1.Chore Chore "confidential" finished executing
8672 [11a] INFO 2017-02-02 16:49:20.961 TM1.Process Process confidentialexecuted by user "confidential
8672 [11a] ERROR 2017-02-02 16:49:24.773 TM1.Process Process confidential: : Execution was aborted by ProcessQuit Function.
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Data Directory: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Admin Host: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Logging Directory: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Configuration Directory: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Raw Store Directory: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Port: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Client Message Port: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Client Message Port does not accept Tm1Top connections.
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Export Admin Server Certificate: 0
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Admin Server Certificate Authority: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Admin Server SSL Cert ID: tm1adminserver
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server IP Version: ipv4
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server SSL Mode: 1
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Export Server Certificate: 0
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server SSL Certificate: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Certificate Authority: tm1ca_v2.pem
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Client Export Server Certificate: 0
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server DH 512 File: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server DH 2048 File: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Private Key Password File: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Password Key File: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Security Mode: 5
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Use Generic Login Connect Error:
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Server CAM URI: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Server CAM URI Retry Attempts: 1
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Client CAM URI: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Web CAM URI: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Client Ping CAM Passport: confidential
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Start time: Thu Feb 02 2017 09:32:50 PM
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server The server will use Parallel Interaction.
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Server threading mode is thread per connection.
23460 [] INFO 2017-02-02 20:32:50.834 TM1.Server Client Message Port does not accept Tm1Top connections.
23460 [] INFO 2017-02-02 20:32:51.053 TM1.Server MTQ is enabled with 8 threads
23460 [] INFO 2017-02-02 20:32:51.053 TM1.Server Using javaextensions.policy from confidential
23460 [] INFO 2017-02-02 20:32:51.053 TM1.Server Creating Java Virtual Machine with arguments:
23460 [] INFO 2017-02-02 20:32:51.053 TM1.Server -Djava.security.policy=confidential
23460 [] INFO 2017-02-02 20:32:51.053 TM1.Server -Djava.class.path=java_classes;confidential
23460 [] INFO 2017-02-02 20:32:51.053 TM1.Server -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=confidential
23460 [] INFO 2017-02-02 20:32:51.053 TM1.Server end JVM args
30220 [] INFO 2017-02-02 20:32:51.896 TM1.Server --------------------Session Start--------------------
30220 [] INFO 2017-02-02 20:32:51.896 TM1.Server TM1 Build Number: 10.2.20500.75