Hi everyone
someday my tm1 instance cannot restart again, normally it will start up within 10 minutes, but now it cannot restart and the tm1serverlog also stop to record start-up details at particular lines.
anyone has encountered this scenario before?
Thanks!
Tm1 Instance starting up failure
-
Steve Rowe
- Site Admin
- Posts: 2456
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Tm1 Instance starting up failure
Probably best to show the lines it is stopping at.
My best guess is that you have persistent feeders on and this is enabling fast start-up. Sometimes it will decide to rebuild the feeders which can take a v long time and you will see the log pause on these lines for long periods.
Key point is if the processor is showing activity against the server then its still active and working.
My best guess is that you have persistent feeders on and this is enabling fast start-up. Sometimes it will decide to rebuild the feeders which can take a v long time and you will see the log pause on these lines for long periods.
Key point is if the processor is showing activity against the server then its still active and working.
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
hju
- Posts: 15
- Joined: Wed Sep 09, 2015 8:01 pm
- OLAP Product: TM1 / PA
- Version: 11 (PA 2.0)
- Excel Version: 2010
Re: Tm1 Instance starting up failure
Hi Nico,
not sure if your issue is already solved...
I encountered this behaviour in an environment where the logs are written on a partition seperate from the tm1 database.
These partition ran unexpectedly full due to a big log file...
On restart of tm1 the behaviour like your description... when the partition is out of memory tm1 can't write any more logs - even no "out of memory"... and stops.
Holger
not sure if your issue is already solved...
I encountered this behaviour in an environment where the logs are written on a partition seperate from the tm1 database.
These partition ran unexpectedly full due to a big log file...
On restart of tm1 the behaviour like your description... when the partition is out of memory tm1 can't write any more logs - even no "out of memory"... and stops.
Holger