When checking operator: The view adapter has a binding for t

[ravireddy25]

iam facing this warning, from lookup stage , data types and every thing are corect for the mapping columns (CACTIVE is column name)

Lookup_3: When checking operator: The view adapter has a binding for the non-existent destination field "CACTIVE".

[ray.wurlod]

Clearly everything is NOT correct, otherwise you would not get this warning.

Have you performed a Search for this message?

Is CACTIVE a key column? Is the CACTIVE column on both input links or only one?

Is CACTIVE a column on the output link? If so, how is it derived (check the Mapping tab)?

[uegodawa]

I've faced similar errors with lookup stage. Usually this happens when you copy lookup stage from one job and paste it on another job and change the key mappings. Unfortunately .dsx file keeps previous information under binding section of lookup stage.
If you really want to remove this message from logs you may need to follow following procedure.
1. Export the job design and keep it as a backup. if you failed on following steps, you can use that export to restore the job.
2. Get a copy of previous export file.
3. Use word pad to open that dsx file.
4. Goto you lookup_3 definition;

Fo r example you should be able to see a section look likes follows;

#### STAGE: LKP_Children
## Operator
lookup
## Operator options
-table
-key CDR_CLIENT_ID
-allow_dups
-ifNotFound drop

## General options
[ident('LKP_Children'); jobmon_ident('LKP_Children')]
## Inputs
0< [] 'DB_CLIENT_TREE:Lnk_DB.v'
1< [view (
CDR_CLIENT_ID=LEGAL_PARENT_CLIENT_ID;
)] 'DS_CDR_CLIENT_Ln:Lkp_Child.v'
## Outputs
0> [modify (
keep
CDR_CLIENT_ID,PARENT_L1,P2_CLIENT_ID,DISPLAY_NAME,
LEGAL_NAME;)] 'LKP_Children:Lnk_Source2.v'
;

make sure under 1< [View

you have correct definitions. This is the key mapping between source and lookup. If you see a line with CACTIVE but you're not use this as a key lookup, remove taht line.

5. Now save the file and import it to the project.
6. Execute the job and check whether it's working without that warning.
7. If you get any un-desireable output, you've the backup to restotre.

[dvpawankumar]

Are you using database as lookup? If you are using database as lookup please delete the column names specified in database stage and add the columns again. And then specify the key column mapping in lookup. Then run the job.


Thanks