DSXchange

Thanks for the interesting quote, something I didn't notice when I peeped at the Help yesterday. It's interesting in the fact that it seems to be false as the jobs I discussed populate an Oracle instance on a remote server, one not residing on the DataStage server.

Curiouser and curiouser...

Is it really so hard to add 'ou' when you mean to spell 'about'? And I don't see the point of chest thumping over ETL tools. Use one or the other, learn it well and unless you need to support both - who cares how the other one does it? Might as well get one of those 'My ETL Tool can beat up your ETL...

Or just double-click on it.

Ya folks, don't be shy! Jump on in with your thoughts and/or suggestions.

And you really only have two choices when dealing with databases: Native or ODBC. Me, I always prefer a 'native' interface over something like ODBC, but that's just me. For Oracle, the native stage is the Oracle OCI stage you mentioned. You will need an appropriate Oracle client installed on the Dat...

Silly question, perhaps, but I don't use this stage in Automatic mode. However, I have inherited a series of jobs that do and I'm getting requests from my DBA for 'the logs'. Specifically, this is the ORAOCIBL stage, aka the Oracle OCI Load or the Oracle 8.1 Bulk Loader stage. There is this quoted f...

us1aslam1us wrote:Also why are you trying to store timestamp in a date field??

Because it's an Oracle DATE field, I would guess.

Two question marks would mean you need two columns. To do that you'd need to send the same batch_id in twice.

In other words, we've done what we can do sitting on the other side of your monitor. Now it's time to find someone on the same side of the glass as you and get another pair of eyes involved.

Hopefully someone DOS batch savvy.

How are you importing the metadata? Via a plug-in?

What you do is correct it by editing the metadata, sometimes you need to be smarter than the tool and clean up any little messes it makes.

In other words, you have a permissions problem.

As far as I know, it just issues a 'truncate' which means it takes the default for storage options. Ask your DBA if you can control that default action, but I believe it does 'Drop Storage' unless explicitly told to 'Reuse Storage'.

Yup... it is setting it once on the first row and then simply setting the value back to itself on every other row. In other words it's a static value. A better solution, IMHO, would be to put CurrentTimestamp call in the Initial Value of the stage variable, then simply leave the derivation blank.

You need to 'source' dsenv first, then run the dsjob command:

Occurred: 5:14:40 AM On date: 12/11/2006 Type: Fatal Event: APT_CombinedOperatorController(1),0: [DataDirect][ODBC Oracle Wire Protocol driver][Oracle]Connection Dead. I would guess you may be running afoul of an idle timeout in the Oracle database. In other words, you connected to it and then didn...