DSXchange

Hi,

I am trying to import the metadata from oracle using orch schema definition from ds manager. But I got the following error messages.
Can anyone help me out with this.

** Error executing command: orchdbutil show GMCC.EX -dbtype oracle -server DEVOTD -dboptions *********
##I TFCN 000001 13:12:04(000) <main_program>
Ascential DataStage(tm) Enterprise Edition 7.5.1A
Copyright (c) 2004, 1997-2004 Ascential Software Corporation.
All Rights Reserved


##I TUTL 000031 13:12:04(001) <main_program> The open files limit is 100; raising to 4096.
##I TCDB 000003 13:12:05(000) <main_program> Oracle: loaded
##I TCDU 000009 13:12:05(001) <main_program> Database connect options: dbname= <unspecified>, server='DEVOTD', dboptions='{user=gmcc,password=gmcc}'.
##I TCDU 000005 13:12:05(002) <main_program> Database connect options: dbname= <unspecified>, server='DEVOTD', dboptions='{user=gmcc,password=gmcc}'DB type 'oracle' presumed to be oracle.
##F TUXX 000002 13:12:15(000) <main_program> Internal Error: (colDesc):orautils.C: 1714: getColDesc failed.
Traceback: [6] APT_FatalPath::msgAssertion(0xfcfbacff, 0xffbe72a0, 0xfcfbad07, 0x6b2, 0x0, 0xccc70), at 0xfe6dad18
[7] APT_OraUtils::querySchema(0x0, 0xfcfdd2e0, 0xffbe7230, 0xffbe7380, 0xffbe738c, 0xfcfd5498), at 0xfcf23dc0
[8] APT_OraUtils::tableSchema(0xffbec9c4, 0x145180, 0xff4c0, 0xffbee664, 0x0, 0xfcf23724), at 0xfcf23644
[9] APT_ORCHESTRATE_main(0x9, 0xffbeef0c, 0x0, 0x0, 0x1003f0, 0x9), at 0x206a8
[10] APT_PMconductorMain(0x14008, 0xffbeec2c, 0x4, 0xff2138b8, 0xffbeec10, 0xffbeeae4), at 0xfedd6908
[11] APT_SharedMain(0x9, 0xffbeef30, 0x14008, 0x9, 0xf, 0xffbeee54), at 0xfee0b220
detaching from process 15298

Thanks in advance.

When you use orch schema to import metadata, you need to have the column descriptions defined on your table, check to see if you have the columns descriptions defined on the table.

Abhi

challahari wrote:Hi,

I am trying to import the metadata from oracle using orch schema definition from ds manager.

Abhi,

I do have table created already.
Here is my table staructure used to create table.

CREATE TABLE PS_G_GC_RU_2AW_STG
(
EMPLID VARCHAR2(33 BYTE) NOT NULL,
G_GC_RSU_DATE TIMESTAMP,
G_GC_CURR_CODE VARCHAR2(6 BYTE) NOT NULL,
G_GC_CASH_LOC NUMBER(19,4) NOT NULL,
G_GC_CASH_US NUMBER(19,4) NOT NULL,
G_GC_STOCK_C INTEGER NOT NULL,
G_GC_STOCK_T INTEGER NOT NULL,
G_GC_PERCENT_DEFER NUMBER(9,4) NOT NULL,
G_GC_CONVTD_SHARES INTEGER NOT NULL
);

Thanks.

[quote="Abhinav"]When you use orch schema to import metadata, you need to have the column descriptions defined on your table, check to see if you have the columns descriptions defined on the table.

Abhi


[quote="challahari"]Hi,

I am trying to import the metadata from oracle using orch schema definition from ds manager.[/quote][/quote]

Whenever you see "internal error" you need to involve your support provider and, through them, the vendor.

Thanks Ray.

I am able to import the metadata using orch schema definition for all the oracle tables except tables have timestamp column.
Let me know if there is any special handling.

Thanks.


[quote="ray.wurlod"]
Whenever you see "internal error" you need to involve your support provider and, through them, the vendor. ...[/quote]

There is no special handling of which I am aware. But this information will be useful to your support provider.

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.

Thanks Bandish.

Database Oracle 9i and Datatype of Timestamp column TIMESTAMP(6).
Do we need to have patch for this versionm too. Pls. let me know if it is required for 9i too.


[quote="bandish"]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.[/quote]

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 this case also.