DSXchange

For any database,
Connector is best Vs ODBC

For Sparse, same rule Input data Volume Vs lookup data volume.

BUT, I won't encourage option #2 as there is another process of replicating AIX version of Mainframe table.

As Ray mentioned, How about federation?

please give more specific details of Oracle EE Stage.

Are you loading using "Load"?
Are you using timestamps Vs Dates?
Changing to insert helps?

Try this Use a "Copy" to split records, Link One goes to "Funnel". Link Two goes to "Aggregator" and same "Funnel." and then output from "Funnel" to "Sequential File" Make sure that all meta-data is fed correctly in Funnel. Hope this helps.

tbtcust,

Can you narate us what was the solution you found?

In our case, option to add to Message handler is grayed out.

Thanks in advance.

K-

IBM Confirmed that DS 7.5.x is not compatible and un-support for Oracle 11g.

The best options

• Downgrade Oracle
  Upgrade DS to 8

Craig,

We have 9i client that too failed.

I'm working on resolving this and will update my finding.

P.s. updated meta-info for this post.

K-

While using 11g for the 1st time, we are facing this issue.
Any link/help is appreciated.

K-

We postponed our pilot to Q3.
Not too far, we will roll it.

I'm ready to deploy it on a sand-box for testing, mid of next month.

K-

Be more specific

There is a situation. I'm creating line numbers for each new batch. e.g. batch, linenumber 1201,1 1201,2 1201,3 1201,4 1202,1 1202,2 1202,3 1203,1 1203,2 I find KeyMgtGetNextValue as appropiate function KeyMgtGetNextValue(Link1.batch) Chulett, Can you send me the modified version and I'll give a try...

We are facing a huge performance deviation when KeyMgtGetNextValue used.

Do anyone have any recommendation for remediation steps?

Stats:

3000 rows/sec without KeyMgtGetNextValue
150 rows/sec with KeyMgtGetNextValue

K-

Thats Right, DSD Run appears when the sequence resets the job prior to running it.

Yes it is called wth the same parameters.
Tried calling the sequence for different parameter sets but still aborts for the same job for the same error.
Most of the Job parameters are PROJDEF.

Also the job is not a multiple instance job.

Job shows PID Failed. However was running very fine until a week before when we last ran it. Tried all of the following, nothing works: 1. Cleared &PH& Directory 2. Unlock user on TCL. (This clears locks indeed but locks are created again on job run) 3.Deleted and redeployed job from version...