PX warning in Oracle Enterprise stage

edwds · Post by **edwds** » Mon Jun 26, 2006 1:06 pm

A PX job that reads an Oracle table and then Loads another Oracle table finishes ok but with a warning:

When checking operator: When validating export schema: Unrecognized top level format property: nocheck

Has anybody seen this warning before?

kumar_s · Post by **kumar_s** » Tue Jun 27, 2006 1:00 am

I have seen this when using CFF with many levels of records.
Do you use transformer in between?

edwds · Post by **edwds** » Tue Jun 27, 2006 8:34 am

kumar_s wrote:I have seen this when using CFF with many levels of records.
Do you use transformer in between?

Kumar,

Yes, we are using a transformer.

kumar_s · Post by **kumar_s** » Tue Jun 27, 2006 8:53 am

Do you find any level change in the field properties available in the transformer?

edwds · Post by **edwds** » Tue Jun 27, 2006 10:47 am

kumar_s wrote:Do you find any level change in the field properties available in the transformer?

No. Additionally, we have run the job without a transformer and still get the same error.

DSguru2B · Post by **DSguru2B** » Tue Jun 27, 2006 12:34 pm

Can you paste the schema that you have imported.

edwds · Post by **edwds** » Tue Jun 27, 2006 12:51 pm

DSguru2B wrote:Can you paste the schema that you have imported.

record
(
JOB_FUNCTION:string[max=3] {prefix=2};
DESCR:string[max=30] {prefix=2};
EFF_STATUS:string[max=1] {prefix=2};
DESCRSHORT:string[max=10] {prefix=2};
INAIL_CODE:string[max=11] {prefix=2};
)

roblew · Post by **roblew** » Wed Jan 31, 2007 11:44 pm

Did anyone get the resolution for this warning?

I have received the same thing.

"oraVBEP: When checking operator: When validating export schema: Unrecognized top level format property: nocheck "

update:
I've found that this warning occurs even without using a transformer stage. It seems to occur when using the "Load" write method. I used a simple row generator into Oracle Ent. stage and still receive the error.

ray.wurlod · Post by **ray.wurlod** » Thu Feb 01, 2007 4:24 pm

Can you take a look at the generated sqlldr control file to see whether it contains a "nocheck" directive and, if so, whether it's in a syntactically correct location?

roblew · Post by **roblew** » Fri Feb 02, 2007 3:07 am

I don't see nocheck in the ctl file.

Code: Select all

$ more ora.26371.825195.0.ctl
OPTIONS(DIRECT=TRUE, PARALLEL=TRUE, SKIP_INDEX_MAINTENANCE=YES)

LOAD DATA CHARACTERSET UTF8 INFILE 'ora.26371.825195.fifo.0' "FIX 113"
APPEND INTO TABLE OLY_DEV.P1Q_testtable
(
KNB1_KUNNR  POSITION(1:80)   NULLIF  (1:80)  = BLANKS,
KNB1_BUKRS  POSITION(81:112)   NULLIF  (81:112)  = BLANKS

)

roblew · Post by **roblew** » Mon Feb 05, 2007 9:17 pm

By the way, an IBM case has been open for the issue. They have been able to reproduce the error internally and they are currently investigating...

kumar_s · Post by **kumar_s** » Tue Feb 06, 2007 3:10 am

Are you using RCP?
Is it a CFF input stage?
Do you have different level in field specification?

mpouet · Post by **mpouet** » Tue Feb 06, 2007 10:26 am

Hi,

We had the same issue with the the Oracle Loader with Datastage 7.5.2 (it was working well in 6 version) and looked for a solution. The IBM answer was : "use job handler" (!!!).

Bye
Matthieu

roblew · Post by **roblew** » Fri Feb 23, 2007 10:43 am

Just wanted to give an update on this. IBM has given us the same work-around... Use a project-level message handler. They have reproduced the error in-house, but prefer not to spend the time to fix it, since the warning doesn't seem to affect the data.

btw, we're not using RCP; doesn't matter if cff input stage or not; not sure what you mean by "different level of field specification". BUT, in any simple test case in multiple projects across different servers, I have received the error.

jjrbikes · Post by **jjrbikes** » Wed Mar 21, 2007 12:54 pm

I was just searching the forum for this error and don't know if I can help or not, but...
It's not exactly the same, but I was getting a similar error in a job that was sourcing an Oracle table and writing the data to a sequential file,

Code: Select all

"When checking operator: When validating export schema: Unrecognized top level format property: fix_zero"

I was able to correct this error by opening my target stage, clicking on the "format" tab and then removing the property "Allow all zeros = yes" which is in the tree structure under Decimal which is under Type defaults.

"Allow all zeros = yes" is synonymous to "fix_zero".

hope this helps!

DSXchange