Select to view content in your preferred language

Got error when registered a DB2 database

7474
11
04-18-2014 01:18 AM
by Anonymous User
Not applicable
Original User: lisa_qian

Our server is 64-bits windows 2008 R2 Enterprise. The DB2 installed was 64-bits which includes client with both 64 and 32 bits drivers. We installed ArcGIS server and ArcGIS Desktop 10.2.1. We have enabled geodatabase successfully. Then we were trying to register database using ArcCatalog or ArcGIS server. There is no problem in the database connection from ArcCatalog (using configured ODBC either from 32-bit or 64-bit ODBC configuration). But when we tried to use that connection sde file or input manually, we got error as below.
The connection property set was missing a required property or the property value was unrecognized. Underlying DBMS error[Unknown errorNo extended error.] DataValidator.GPServer

Could anybody help to identify the reason why this failed? Thanks!

[ATTACH=CONFIG]33190[/ATTACH]
[ATTACH=CONFIG]33191[/ATTACH]
[ATTACH=CONFIG]33192[/ATTACH]
0 Kudos
11 Replies
ShaunaHarris
Deactivated User
I am also having this issue. Please let me know if you get passed it. Thanks
0 Kudos
by Anonymous User
Not applicable
Original User: rlwatson

I have not used DB2 so I can't comment on that but I have used Oracle.  The desktop applications such as ArcMap and ArcCatalog are 32 bit and the server applications are 64 bit.  I remember that when you configure Oracle that you had to add both 32 and 64 bit paths to the PATH environment variable if you want to run both desktop and server.  There was a trick in that you had to list the 64 bit path in the PATH first.
0 Kudos
ShaunaHarris
Deactivated User
Thanks for your response the strange thing is I have a second environment windows 7 64 bit which I have installed ArcGIS Server, Desktop and DB2 9.7 client which has a database cataloged. This environment works fine and I didn't have to do anything with libraries. I read online the issue with bin files you outlined for oracle but there doesn't seem to be anything similar with db2. I do have the 32 and 64 bit libraries in the db2 bin folder though. I also read on another post to try putting then in the arcgis server bin folder in case there is a path issue. This didn't work so I removed them.. Any other suggestions greatly appreciated! Thank you in advance.
0 Kudos
by Anonymous User
Not applicable
Original User: rlwatson

I went though something similar with Oracle.  The trick I learned was to test the 64 bit connection using some type of tool.  I wrote one myself but I suspect that there must be a 64 bit DB2 tool that you can use.  The best case is that this fails and resolving that problem will resolve the ArcGIS Server issue.

Best of luck!
0 Kudos
LisaQian
Emerging Contributor
I went though something similar with Oracle.  The trick I learned was to test the 64 bit connection using some type of tool.  I wrote one myself but I suspect that there must be a 64 bit DB2 tool that you can use.  The best case is that this fails and resolving that problem will resolve the ArcGIS Server issue.

Best of luck!


Thanks for the reply! I tried the ODBC connection of both 32-bits and 64-bits (C:\Windows\System32\odbcad32 and C:\Windows\SysWOW64\odbcad32) and no problem there. Could provide more information/requirements of that type of tool? Thanks!
0 Kudos
by Anonymous User
Not applicable
Original User: lisa_qian

More information.

DB2 64-bits installation already include the library of both 32-bits and 64-bits.

[ATTACH=CONFIG]33208[/ATTACH]

The DLLs of both 32-bits and 64-bits are provided.

[ATTACH=CONFIG]33209[/ATTACH]
0 Kudos
by Anonymous User
Not applicable
Original User: crafty762

At first glance, this sounds to me like NIM084080 - Allow users to register OLE DB connections with the data store.  When I read your post and look closer at your screenshots, it looks like you are trying to register an OLE DB connection for your 'maximo' database with ArcGIS for Server.  I found this thread which seemed to discuss similar issues.  What's odd, however, is that the bug report indicates the fix version is 10.2 yet you indicated you are using 10.2.1.  It's possible that what you're seeing is a different issue, but I still think it sounds very similar to the bug nonetheless.  You might want to try contacting Tech Support to determine if this actually is NIM084080 or not.
0 Kudos
LisaQian
Emerging Contributor
At first glance, this sounds to me like NIM084080 - Allow users to register OLE DB connections with the data store.  When I read your post and look closer at your screenshots, it looks like you are trying to register an OLE DB connection for your 'maximo' database with ArcGIS for Server.  I found this thread which seemed to discuss similar issues.  What's odd, however, is that the bug report indicates the fix version is 10.2 yet you indicated you are using 10.2.1.  It's possible that what you're seeing is a different issue, but I still think it sounds very similar to the bug nonetheless.  You might want to try contacting Tech Support to determine if this actually is NIM084080 or not.


Thanks for the information Crafty! Actually I tried to the ways of using both ODBC Connection and writing the connection string directly. But neither of them worked.

[ATTACH=CONFIG]33210[/ATTACH]

[ATTACH=CONFIG]33211[/ATTACH]
0 Kudos
LisaQian
Emerging Contributor
Does anybody know how to contact the global technical support? I got the license from a colleague of Brazil, and registered the license using internet successfully. So how can I know my customer number? I asked the colleague from Brazil who told me he did not have that number. I tried to request a support form (using part of the license number as the customer number) and submitted that request successfully (got a email notification) but can not view that request again from website because it said the customer number entered could not be recognized when checking support requests. I actually contacted the local technical support by calling. But they said because I could not provide a local customer number their support would be very limited with low priority. Currently it seemed that they had very little experience on DB2 on ArcGIS....
0 Kudos