Login DS Designer is very slow..

[xinhuang66]

We are having an issue of logining DS Designer take very very long time.

Instructed by IBM, tested logining Director, it is very faster.

So it comes down to xmeta issue, however, if I test query on xmeta, it response to my query normally, not very slow.

Everytime, Designer login stop at 40% for 1-2 minutes, then get in. We use Oracle as xmeta in a different Server.

Does anyone have a clue to handle these ?

Which xmeta table we can work on ? put more indexes, etc.

Thanks.

[SURA]

We are having an issue of logining DS Designer take very very long time.

Hi Xin

Do you have a client installed in the Datastage Server machine itself?

If yes, how much time it is taking?

[SURA]

Please do consider where the Oracle Server is sitting ? If that is in another Server , then the entire process through "Network" like You PC, DS Server and Oracle Server need to interact!

Anyhow 2 min is tooooo much!

[xinhuang66]

Since the server is Unix version, we can not install the client on the same box as server.

I agree, since xmeta is not at the same box as DS Server, it introduce the risk of network issue, and other factors. However, connect to xmeta by other tools such as Toad is ok.

I opened client trace under IBM instruction, from the log file, I can see how many ms each step takes.

It is this bugger takes time.
query handle (31) XMQL ' select rid(x),x.ParentRID from x in DataStageX::DSItem where x.ReposId = :param1'

So far, IBM has no idea why this takes longer, and how to fix it.

[SURA]

Since the server is Unix version, we can not install the client on the same box as server.

You have chosen WINDOWS OS here

[SURA]

I agree, since xmeta is not at the same box as DS Server, it introduce the risk of network issue, and other factors. However, connect to xmeta by other tools such as Toad is ok.

1) Is this always SLOW?

2) Can you please try to logon after office hours / less Network Traffic time?

3) Can you please check is this due to fire wall settings?

[priyadarshikunal]

check if the statistics of the table in question are correct on oracle database. Apart from that I will let IBM work on the same.