My Oracle Support Banner

OWB OMBALTER MAPPING Command Creates New Field in the Target Table (Doc ID 422788.1)

Last updated on MAY 05, 2014

Applies to:

Oracle Warehouse Builder - Version 10.2 and later
Information in this document applies to any platform.

Symptoms

Modifying an OWB mapping to connect a flat file source and target table ends up in adding new column instead of mapping source to target:

OMBCONNECT <repo_user>/<PWD>@<hostname>:<port>:<servicename> 

OMBCC '/CONV_DEV/TARGET_DEPLOYMENT' -- changes the context 

OMBCREATE MAPPING 'MAP1' -- creates a new mapping 

OMBALTER MAPPING 'MAP1' 
ADD FLAT_FILE OPERATOR 'ADJ_MAIN_TXT' 
BOUND TO FLAT_FILE '/CONV_DEV/SERVER_FLAT_FILE_SOURCE/ADJ_MAIN_TXT' 
-- creates source flat file operator which is already imported in to the repository. 

OMBALTER MAPPING 'MAP1' ADD TABLE OPERATOR 
'NOB_ADJ_MAIN' BOUND TO TABLE 
'../LEGACY_SOURCE/NOB_ADJ_MAIN' 
-- creates target table operator which is already imported in to the repository. 

Now when trying to connect to above two operators, 
OMBALTER MAPPING 'MAP1' ADD CONNECTION FROM GROUP 'ADJ_MAIN_TXT' 
OF OPERATOR 'ADJ_MAIN_TXT' TO GROUP 'INOUTGRP1' OF OPERATOR 
'NOB_ADJ_MAIN'


It is creating new fields in the Target table instead of connecting the existing fields.

Changes

OMBALTER command from OMBplus.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.