DSXchange

No, as a Timestamp with generated SQL there should be no problem if the DB2 timestamp is indeed in the format you say it is. Post the TO_DATE() portion of your insert sql for this field. This is resolved. Initially iam using the substring function its not working then i used left function. Target i...

chulett wrote:Change the datatype to Timestamp in your job and ensure the stage generates the SQL. Do that, remove the milliseconds and then you'll be fine.

I am getting the following error

db2cobr_orclcobr_TEST_1..Transformer_1: ORA-01843: not a valid month.

Should i need to edit the sql in the stage?

DSguru2B wrote:What if you chop off the milliseconds, does it work then?

I am getting the same errros

What happens when you send it directly to oracle without any conversion? Do you get any errors/warnings? If yes, can you paste it here? ... In the transformer i am keeping db2 datatype as timestamp and in oracle datatype as date. The format in oracle should be mm/dd/yyyy hh:mi:ss AM/PM when i ran t...

DSguru2B wrote:If your DB2 timestamp is in YYYY-MM-DD 24HH:MI:SS then no conversion is required. You can send it as it is.

The format of DB2 is yyyy-mm-dd hh24:mi:ss.msecs(6digits)

Hi,

Can any one help me in converting the db2 timestamp to oracle (ORAOCI9 STAGE) Timestamp.

Hi Koolnitz, I solved the issue. This is due to the communication problem between the database and datastage. When ever we create a DSN for the datastage we bind the ODBC / CLI connections to the database. Previously my connections were binded and my datastage was running fine. For maintainance we r...

yes koolnitz, the user thru which i am connecting to the database has select, create all the privileges. and the user id i used to logon into the datastage has administrator privileges.

raj

Ya i even checked that. The user i am using for Datastage has all the privileges.

raj

Hi folks, I am getting following error when i try to run the mapping. i am not even able to import the table also. "[IBM][CLI Driver][DB2/NT] SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an error SQLSTATE with diagnostic text "SYSIBM:CLI:-80...

Hi Stiwari,

If your DB is tuned and working fine then your DS job shud run at a minimun of 1000 records per second.

Thanks,
raj

Hi Jane, With my experience I feel that the query u r using in the job needs some tuning. try running the same query in the database instead of running thru the datastage. This may fix your problem. If not, then the query/ job must be in waiting state as the table on which your are trying to perform...

Hi DS Guru, I also tried using ODBC Stage. In this case i am able to import the procedure but during the runtime i am getting a warning. This warning contains the same previous error message. I dont find any STP stage. U mean this by stored procedure stage or what? Previosuly I used Stored Procedure...

Hello DS Guru, I do have IN Parameters but no OUT params. Its throwing the error while importing the procedure itself. I feel I need to change my Databse Configurations. The following is what i found on the web. But need to give that a try. Or you guys hav any other suggestions please let me know. &...

Hi folks, My Database is IBM DB2. I created a Dynamic stored procedure. I tried running this from the database only and is working fine. When i am trying to run the same procedure importing into the Datastage its throwing the following error. TESTING is the name of the procedure. "TES..Stored_P...