DSXchange

Infact If now I try for "Menu Bar"(Camel Case) also, it returns many results along with the thread sent by Craig !!

Infact If now I try for "Menu Bar"(Camel Case) also, it returns many results along with the thread sent by Craig !!

Thanks Craig ! It worked, when I deleted registry entries.

But I am still wondering why I did not get "any topics" when I searched for "Menu Bar" before posting this issue !!!! I did a "search for all terms" search also.

~Bandish

Ray, Showing ToolBar from the view menu will show the "ToolBar". But In my case "MenuBar" is not visible.

Menu Bar has 9 pull down Menus like "File/View/Tools.."

Alt-V didn't work.
Yes, by Menu Bar I meant File/View/Tools ... bar.

When I do an Alt-V, it pops-up the window to Show/Hide "Toolbar, Status Bar, Palette, Repository...". Alt-V is behaving similar to a right-click.

Hi All,

I mistakenly hided my DataStage Menu bar and I am not able to view it.
How can I unhide it ?

I pulled the Menu Bar to the DataStage Ascential Banner and left it. After that it's not visible.

Thanks
Bandish

As per my understanding, the three tables can be joined using the following columns: CUSTOMER_ID and INVOICE_NO. Using a single Oracle enterpise stage, you can write a join query and get the desired columns. Else use 3 Oracle Enterprise stages with simple select queries and 2 join/Lookup stages to g...

The problem is basically due to TIMESTAMP(6) column. If you remove all timestamp(6) columns from your source metadata, you can then see that your job doesn't give the error which you are getting. You can talk to your service provider telling them this issue. I think patch needs to be installed in th...

Is your Database Oracle "10g" and Datatype of Timestamp column TIMESTAMP(6)?

Then you have to get some patch installed on your ETL server. We were also facing the same problem and it got resolved after the patch was installed.

You should let your support provider know this issue.

Sorry for the confusion, I actually meant "PEEK" Stage.

Use a Pivot stage after the DB2 API stage to get the rejected records and their reason for rejection.

Yes, Sorting millions of records would be a performance bottleneck. Then probably, after pivoting, we can use few (i think 3 or 4) stage variables to get the min TimeStamp as the number of TimeStamp column would be just one instead of 20. But one doubt I have here: Would pivoted data have all record...

We can create a key column for each record if not already present; and use a Pivot stage and create a single column which will create 20 rows/record. After this we can sort on the Key(generated) and Timestamp field and retain the first record using "Remove Duplicates" stage.

Thanks
Bandish

In my previous reply, I mentioned the following: We had got a patch installed in our ETL server for reading Timestamp fields of Oracle (Datatype: TIMESTAMP(6)). But now the patch is removed and we are getting the following error: [b]main_program: Fatal Error: Caught ORCHESTRATE exception in main pro...

Hi, I am also getting the same error as in this post. The error is : main_program: Fatal Error: Caught ORCHESTRATE exception in main program: APT_Archive::BadData: From: Loading memory archive. We had got a patch installed in our ETL server for reading Timestamp fields of Oracle (Datatype: TIMESTAMP...