DSXchange

In order to use OCI LOB locators for all LongVarchar, LongNVarchar, and LongVarBinary columns, set the CC_ORA_LOB_LOCATOR_COLUMNS environment variable to (all) More information on https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.conn.envvar.ref.doc/topics/r_envvarora_cc_o...

Finally we were able to resolve the same. In order to use OCI LOB locators for all LongVarchar, LongNVarchar, and LongVarBinary columns, set the CC_ORA_LOB_LOCATOR_COLUMNS environment variable to (all) More information on https://www.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.c...

That's correct - I am using the string 'NULL' and it finishes without any errors.

The only concern is Inserts works without any issues, It inserts Nulls in the field, It aborts only if the Update gets executed.

Thanks

Hi all, Please note, this is a similar issue to the below mentioned post. http://www.dsxchange.com/viewtopic.php?t=155789 Am trying to read and load 2 CLOB fields, I am using LongVarchar (4000) to read and load the data, Array size is set to 1 and the columns are at the end or the Oracle connector (...

Hi all, Am trying to import a Sybase IQ table definition using the 'Orchestrate Schema Definition', The import wizard populates incorrect length for CHAR fields. Irrespective of the column length in the table - the import wizard populates CHAR (20) for all CHAR columns, When i try the Plug-in method...

Thanks Ray,

We don't have Unicode/UTF enabled for this job, Am unable to avoid this warning , Am forced to use the Sybase Server stage to process data.

Let me know if there is any other way to fix this issue.

Use a start and end loop activity with the counter value as a parameter, You pass the required value at runtime and the job would loop from 1 to n.

Use the counter value as the INV_ID while calling the parallel job.

Thanks

Hi all, We have a column defined as a CHAR (2) in Sybase, but when I read the column as a CHAR(2) in Datastage, I get the below mentioned warning . Implicit conversion from source type "string[4]" to result type "string[2]" I know that Sybase uses 2 bytes for a single CHAR value ...

Hi All,

Any thoughts as to why RCP without column definitions/properties would default large numbers ?

Hi ,

I did a quick test by giving the column details (Declared it as a DECIMAL 38,10) and it loads the values correctly without rounding it off.

But there are almost 300 tables that needs to be copied, I would like to get suggestions as to why this can happen with such large numbers.

Thanks

Hi Ray,

Since we had to copy a lot of tables, we didn't specify any column name/property.

RCP is enabled and we use a plain SELECT * FROM #TBL# and Bulk load to the target, I just have a copy stage in between the source connector and target connector.

Thanks

Hi All, We are using Datastage 8.7 to copy tables over from Oracle 10G to Oracle 12c Exadata platform. Looks like Datastage is rounding off a large number. The number is defined as NUMERIC in both source and target. Am using a generic job having RCP enabled and a parameter that passes the table name...

Thanks ArndW , I tried to extract only one column that's a key column at the Source and the target and applied Null handling as well, But I got the same error using bulk load, I have requested the admins to raise the request with the official support provider. I will keep the forum updated once I ge...

Please note we are unable to use Bulk load on Oracle 12C Exadata server - The jobs are aborting with the below mentioned error FAC_CMC_SBSB_SUBSC,0: The OCI function OCIDirPathPrepare returned status -1. Error code: 604, Error message: ORA-00604: error occurred at recursive SQL level 1 ORA-01405: fe...

Thanks for the information Craig.