Page 1 of 1
TM1 32bit on Windows 2003 64bit
Posted: Tue Mar 10, 2009 4:27 pm
by BFranklin
Hi
I am shortly going to be moving TM1 (32 bit instalation on a 32 bit platform) to a 64bit platform.
This is mainly because we have new hardware.
Will be running TM1 9.0 SP3 U9 32bit on Windows 2003 64bit.
Is their any known problems here I should be aware of?
Is the RAM still limited to 3GB or does it get a slight boost?
Will be running in a VMWare environment.
Cheers,
Blair
Re: TM1 32bit on Windows 2003 64bit
Posted: Tue Mar 10, 2009 4:35 pm
by Steve Rowe
You should be able to get 4GB running 32 bit on a 64 bit box.
I'm not aware of any issues in particular, though I believe the ObjectDuplicate issue still exists in 9.0 but if you don't suffer from this now then you probably won't in the future.
Are you moving from the same version in 32bit?
I'd be interested in hearing of any experiences you do have on the move though, I have a similar change coming up.
Cheers,
Re: TM1 32bit on Windows 2003 64bit
Posted: Tue Mar 10, 2009 4:46 pm
by Herman Moller
Blair,
We had a similar query from a client a year ago.
You can utilise up to 4 gb (1 gb of extra ram) using a 32bit tm1 server on a 64 bit box.
At the time Cognos said it’s not formally supported, but they had not been aware of any problems.
Regards
Herman
Re: TM1 32bit on Windows 2003 64bit
Posted: Wed Mar 11, 2009 9:32 am
by BFranklin
We are using the same version of TM1 that we currently run.
The idea is to upgrade the hardware to 64bit, use the extra 1 GB. and then further down the line when when the business case is aproved to upgrade the software to 64bit.
Re: TM1 32bit on Windows 2003 64bit
Posted: Wed Mar 25, 2009 4:48 am
by MarkTM1
Have just moved our 32 bit TM1 Server on to a 64 bit box.
Here’s a couple of things I learnt.
32 bit drivers are used for connection to ODBC data sources. The 32-bit version of the ODBC Administrator tool need to be used. This is the Odbcad32.exe file and is located in the %systemdrive%\Windows\SysWoW64 folder. Add a shortcut to your desktop for easy access.
Our Oracle driver didn’t like the brackets in its default setup location: Program Files (x86) To make it work we removed the brackets when installing it – i) select custom install, unselect all, remove brackets from install location, complete. While nothing is selected Java is installed. ii) Unselect all, select just OBDC and universal installer, remove brackets from the install location.
The other ‘learning experiences’ I had were related to setting up integrated login and the Web.