I believe we are getting a connection timeout error when trying to list tables from a UV account. We can pull up table lists from other smaller accounts, but this particular account is huge. It tries to load for 5 minutes or so then displays the message:
DSR.MetaGeta(GET.TABLES)(SQLFetch): BCI Error:
SQLSTATE=IM985,CODE=81001,[DataStage][SQL Client][RPC] error code = 81001
Our uvodbc.config file is configured as:
<Antares>
DBMSTYPE = UNIVERSE
network = TCP/IP
service = uvserver
host = 172.22.42.23:31438
<localuv>
DBMSTYPE = UNIVERSE
network = TCP/IP
service = uvserver
host = 127.0.0.1
Any help is greatly appreciated.
Thanks.
Timeout importing UV account table list?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
See this post (your other post) where I addressed the possibilities.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Didn't you take my recommendation to setup a new account with custom dictionaries and F-pointers seriously?
The VOC is bloated probably due to years of accumulated junk, as well as dictionaries for each file is probably overloaded with unnecessary copies of dictionary items for formatting reasons, as well as I-descriptors and correlatives that are traversing multiple files. You want clean dictionaries that only reference the localized file and use I-descriptors only when you need to surgically extract data from a nasty multivalued attribute.
The VOC is bloated probably due to years of accumulated junk, as well as dictionaries for each file is probably overloaded with unnecessary copies of dictionary items for formatting reasons, as well as I-descriptors and correlatives that are traversing multiple files. You want clean dictionaries that only reference the localized file and use I-descriptors only when you need to surgically extract data from a nasty multivalued attribute.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Yes, I did take your advice and even more so now I just wanted to make sure I had researched all the options before moving forward with an implementation. Management is always looking for that silver bullet and didn't want to maintain a seperate set of DICTS. However, I should now have enough evidence to convince them otherwise.kcbland wrote:Didn't you take my recommendation to setup a new account with custom dictionaries and F-pointers seriously?
The VOC is bloated probably due to years of accumulated junk, as well as dictionaries for each file is probably overloaded with unnecessary copies of dictionary items for formatting reasons, as well as I-descriptors and correlatives that are traversing multiple files. You want clean dictionaries that only reference the localized file and use I-descriptors only when you need to surgically extract data from a nasty multivalued attribute.
Thanks again!
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: