DSXchange

Now I am trying to delete the schema. I tried this (per the link in the previous reply): VERIFY.SQL carlb04; And got these errors: >VERIFY.SQL carlb04; ** Invalid VERIFY.SQL operation. 1 verify operation discontinued. Items marked with a '!' are information messages only. Items marked with a '*' can...

Okay, found a topic that points me in the right direction - project removed outside DataStaage.

To delete the account, I did this - note, the project name is carlb04
That successfully deleted the project.

That did the trick. Thanks!

Brad.

By the way, the project shows up in the list of projects in Administrator. If I try to click on it, I get this:

Failed to connect to host: edwdev2.wellsfargo.com, project: carlb04
( The directory you are connecting to either is not a UV account or does not exist (39125))

Brad.

We had many project directories get deleted recently. Now, we are unable to rebuild some projects. The project directories are gone, but when we try to recreate them in Administrator, we get an error: DSR.ADMIN: An account called 'carlb04' already exists. How do we delete a project we cannot see? Br...

Okay, granted permissions. Having the developer give it a try. Will let you know.

Thanks!

Brad.

We are in the process of recovering from a snafu in our dev environment in which about 75-100 projects were deleted wholesale from our DS7.5 directory structure, many DS libraries and executables were deleted and about 1TB of data was lost from a dev filesystem. No, we don't know how it happened yet...

Believe it or not, I think it is a 'large decimal' issue. My suspicion is that it boils down to a bug either in DataStage 8.1, Teradata v13, or TTU13 (Teradata Tools and Utilities, the API for tools to talk to Teradata). I created a test job that fails with the 2617 error if the datatype is decimal(...

I didn't check any other fields. I guess I thought the error message was specific to the cust_acct_id field:

RDBMS code 2617: Overflow occurred computing an expression involving dly_cust_acct_drv_E2.CUST_ACCT_ID

Bad assumption?

Brad.

The E2 object is a table that is generated at runtime by DataStage. It is a copy of the target table's layout without a unique index on it so that it can capture the entire record without failing uniqueness itself. For the development job, I tested the input dataset and the min/max cust_acct_id are ...

The reqeusted sessions and sessions per player are parameters for the TD Enterprise Stage, not the connector. The connector uses the max sessions and max partitions parameters instead.

Brad.

We have run into this many times and there are many different things to consider. First of all, IBM had suggested a minimum standard of 300 seconds for sync timeouts. also, make sure this is a parameter that can easily be updated. Depending on the volumes you are reading/writing and how busy your da...

We have a job failing in production (and elsewhere) with the following error message: 9713 FATAL Sat Sep 4 08:21:03 2010 heidswk_dly_cust_acct_drv,0: RDBMS code 2617: Overflow occurred computing an expression involving dly_cust_acct_drv_E2.CUST_ACCT_ID SQL statement: LOCK ROW FOR ACCESS SELECT CAST(...

That is for a transformer, right? The question was about the Filter stage.

I thought about that option, but the next question that came to mind was how to dynamically generate the table DDL. This is to be a generate job reading an input dataset and creating a target table to match it. If there is a good way to generate table DDL based on a dataset schema, then we can pass ...