TM1 Forum

Hello,

We have the 64-bit Oracle driver installed to obtain our SQL data. I set up a DSN Connection and that's working fine. However, I think we have a problem because Architect is still 32-bit in TM1 10.2.1. When clicking on the Turbo Integrator, Data Source Browser button I get the following error message, which makes sense because there are is no 32-bit ODBC connection:

"An error occurred while retrieving datasource names from the server."

My questions:

1 - Is there any way around this in our 32-bit Architect, keeping only the 64-bit data source and accessing that in Turbo Integrator?
2 - If not, can both the 32-bit and 64-bit Oracle drivers be installed, one with a DSN in the 32-bit admin and the other in the 64-bit admin, or can we only have one?
3 - We don't have the computer web-enabled yet, so I can't bring up the Connector and Congos BI, but when I can would I be able to connect the 64-bit data source there and then access that data source in the 32-bit Architect (via Congos BI)? Please forgive me if this doesn't make any sense at all. Since I don't have BI up and running I can't test this myself.
4 - Can Architect 10.2.2 be installed and run with TM1 10.2.1 or would all the TM1 components have to be upgraded?

I have to be able to bring data into TM1 from an Oracle Database, so please provide any suggestions with the above situation in mind.

Thanks!

The driver should match the TM1 server. If you have 64-bit TM1 server installed, use the 64-bit Oracle driver. Architect is instructing the server to connect to the driver, it doesn't connect directly, so it doesn't matter what version of Architect you're using.

Did you set up the DSN in the "System DSN" tab in Data Sources?

Matt

Hello,

Yes, to answer your question, "Did you set up the DSN in the "System DSN" tab in Data Sources?"

I discovered that I was able to connect via my ODBC connection with 'Planning Sample' and they are both in my Architect session. One difference between them is that 'Planning Sample' is running as a service and the TM1 data server that I created is not. It's running as an application. So I just changed this to run as a service and will be changing the log on information that it opens with to be the same as 'Planning Sample'. I'm hoping after these changes I will be able to connect to my data source in the TM1 data server that I created. I actually copied the .cfg file from 'Planning Sample', but I did make a few changes. I don't see any settings in that file that should make the different.

DHaagenson wrote:One difference between them is that 'Planning Sample' is running as a service and the TM1 data server that I created is not. It's running as an application.

When you run a TM1 service as an application it is running under the ID that was used to start the application. That ID may or may not have the same security to the Oracle database as the account the service runs under. Even though you can, you should probably not run TM1 as an application. There are other gotchas to doing this that aren't always apparent on the surface.

Thank you both for your replies. Your information has been very helpful!

I do have the ODBC Oracle DSN connection working and can pull data into the Application - Yeah!!

I did try to change my application to a service. It created the service, but now it won't run, so another problem to solve. The trouble is, I'm a new employee and am not a Network Admin, so I have limited permissions. I had someone set the Log In for the service I seemingly created, so it matched the other services that I'm running, but it still does't run. I get the following message, 'Error 1067: The process terminated unexpectedly." If you have any suggestions to solve this I would appreciate it.

DHaagenson wrote:I get the following message, 'Error 1067: The process terminated unexpectedly." If you have any suggestions to solve this I would appreciate it.

That typically means that the TM1 server tried to start, failed, and terminated itself. Check tm1server.log for the cause. You probably have an error in the service creation (can't find tm1s.cfg), your tm1s.cfg file (path to database or log dir), or a permissions issue (service account can't read or write to database or log dir).

Matt

Hello,

All problems solved!

Thank you again to those who responded!!

Info below might help others:

- Run cmd as an administrator to create or remove a service.
- My login let me create the service, but apparently I didn't have permissions to actually run the service. I changed the LogIn for the service to the local default service (no userid or password) once the service was created.
- Be sure that if you're running TM1 64-bit that you always use the bin64 directory instead of bin (if that's what your's are named). There is so much information online that's helpful, but keep in mind that sometimes it's old.
- I have TM1 64-bit, Windows 2008 R2 64-bit, so I had the 64-bit Oracle driver installed and that worked fine. This driver will appear in the System32, Admin, odbc dialog box not the SysW0W64, as you might expect. Microsoft has these backwards in my opinion. Of course they may change this, so be careful. I set up the DSN and it allowed me to test it in the Admin, odbc dialog box. I don't think it does that for 32-bit.
- As is mentioned in the posts to my issue, TM1 Architect (as of TM1 10.2.1) is a 32-bit client, but that isn't an issue in bringing up the 64-bit Admin, odbc dialog box to select the DSN as the data source. Just make sure that you're running the TM1 Data service or application from bin64 and not bin or you will get the 32-bit Admin, odbc dialos box instead.

I know this can all get a little confusing when you have an issue like I did, especially when you're new to TM1 Cognos. Good Luck!

Deborah

DHaagenson wrote:I changed the LogIn for the service to the local default service (no userid or password) once the service was created.

You may want to create a domain user to use as a system account for the TM1 server. Down the road, you may want TM1 to import from or export to folders on remote servers, and you'll need the service running under domain credentials to do this.

Matt

Hi Matt!

We have done that for all of the other TM1 services, but I am new here and do not have permissions to do this myself, so I have to contact someone to set the 'LogIn' for my new service to the service account we use. Right now this is a demo account, so it's ok.

Thanks,