Tm1 and ibm cloud
-
- Posts: 14
- Joined: Tue Aug 31, 2021 12:04 pm
- OLAP Product: Cognos Analytics
- Version: 10.2.2
- Excel Version: 2017
Tm1 and ibm cloud
Hello everyone.
Need really urgent help.
Case: I work with tm1 in conjunction with ibm cloud.
We have a tm1 web application. Users enter values for consolidation and spread values. Recently they had a problem that performance very low. But we didn't make any updates. We also found in the bucket in ibm cloud that
"Inconplete Upload Part of your upload was not completed, incomplete objects will not appear in the object list but will occupy billable space in storage."
We also found that bucket size is constantly increasing. in the morning he was 4 tb, after a few hours already 7 tb
We assume that users write data to the cube for consolidation and something happens wrong.
Who can help figure out what the problem is?
- Attachments
-
- 1.png (5.83 KiB) Viewed 1754 times
-
- 2.png (695 Bytes) Viewed 1754 times
- Steve Rowe
- Site Admin
- Posts: 2421
- 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 and ibm cloud
You'll first need to identify which of the services on the box are causing the RAM spike. It might not even be a TM1 problem, can you get to the task managed or similar on the box?
I'm going to assume it is the Tm1 DB. You'd have to make some significant changes to the config of T1Web to allow it to hit that much RAM without it failing.
Do you know what size you would consider normal for your TM1 DB?
Turn on the performance monitor of TM1 and identify which cube is consuming the most RAM.
Diagnoise what might have changed.
Use TM1Top or the admin page of PAW to identify any long running threads and understand what they are doing, i.e. if you have a very large cube and a user tried to ascii export it all this might hit the RAM hard.
Unless your application is already consuming TBs of RAM in in its normal state then something is clearly very wrong. Since the overage cost of this RAM might cost your company significat £££, I'd be inclined to stop all the applications / restart the box. This may of course prevent you from understanding what is going wrong.
Good luck!
I'm going to assume it is the Tm1 DB. You'd have to make some significant changes to the config of T1Web to allow it to hit that much RAM without it failing.
Do you know what size you would consider normal for your TM1 DB?
Turn on the performance monitor of TM1 and identify which cube is consuming the most RAM.
Diagnoise what might have changed.
Use TM1Top or the admin page of PAW to identify any long running threads and understand what they are doing, i.e. if you have a very large cube and a user tried to ascii export it all this might hit the RAM hard.
Unless your application is already consuming TBs of RAM in in its normal state then something is clearly very wrong. Since the overage cost of this RAM might cost your company significat £££, I'd be inclined to stop all the applications / restart the box. This may of course prevent you from understanding what is going wrong.
Good luck!
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- Posts: 14
- Joined: Tue Aug 31, 2021 12:04 pm
- OLAP Product: Cognos Analytics
- Version: 10.2.2
- Excel Version: 2017
Re: Tm1 and ibm cloud
Yesterday it was 8 gb - and i think it is ok.
- Steve Rowe
- Site Admin
- Posts: 2421
- 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 and ibm cloud
Just to follow up.
Is the bucket size referring to the RAM or the disc consumption?
If it disc consumption rather than RAM, then you need to look at and understand how the logging is configured on TM1.
Areas to check.
Cheers,
Is the bucket size referring to the RAM or the disc consumption?
If it disc consumption rather than RAM, then you need to look at and understand how the logging is configured on TM1.
Areas to check.
- Make sure you understand how the disc is used, can it only be TM1 causing the issue?
- Are you loading alot of data frequantly and do you have logging turned on during the data load?
- Is the performance monitor turned on and the transaction logging of the performance monitor cubes turned on? This can generate very large log files, very quickly.
- The audit log can generate a lot of records on a busy server.
- Look in the logging directory for TM1 and see if there are any very large log files. You'll then need to analyse them to try and determine what is causing the log records.
- It's possible but very unlikley this is being caused by a TI running at a high frequency and generating errors. There are controls in place to prevent a TI generating very long error logs, but if you have a lot of TIs running in a chore at a high frequency then this could eat up your disc too.
Cheers,
Technical Director
www.infocat.co.uk
www.infocat.co.uk
- gtonkin
- MVP
- Posts: 1209
- Joined: Thu May 06, 2010 3:03 pm
- OLAP Product: TM1
- Version: Latest and greatest
- Excel Version: Office 365 64-bit
- Location: JHB, South Africa
- Contact:
Re: Tm1 and ibm cloud
Would recommend logging in to the Rich Environment and mapping a drive so that you can view the data and logs folder in Windows Explorer.
At least this way you are likely to see it it is one large file, multiple smaller files e.g. Logs etc.
At least this way you are likely to see it it is one large file, multiple smaller files e.g. Logs etc.
-
- Posts: 14
- Joined: Tue Aug 31, 2021 12:04 pm
- OLAP Product: Cognos Analytics
- Version: 10.2.2
- Excel Version: 2017
Re: Tm1 and ibm cloud
Probles was with transaction log
I created a chor that do "Save data" and after that all working good
I created a chor that do "Save data" and after that all working good
-
- Community Contributor
- Posts: 295
- Joined: Mon Mar 23, 2009 10:50 am
- OLAP Product: PAW/PAX 2.0.72 Perspectives
- Version: TM1 Server 11.8.003
- Excel Version: 365 and 2016
- Location: South London
Re: Tm1 and ibm cloud
Watch out with spreading esp auto spread. When you have loads of dimensions you can inadvertently generate a massive query. We had this and turned spreading off.