Sequential_File_2: Import validation failed.
Sequential_File_2: At field "CREATION_DATE": Unrecognized type-specific format properties: {Key}
main_program: Could not check all operators because of previous error(s)
Hi,
We implemented the same job reading from sequential file and loading into oracle table with a generic approach
for this we used schema files, here is the procedure.
source schema file format will be like
record
{final_delim=none,delim='|',null_field='',quote=none,record_delim_string='{BEG}'
{
ALT_CD:string[max=4] {quote=none};
LAN_CD:string[max=2] {quote=none};
LAST_TIMESTAMP:timestamp {quote=none};
}
In the above schema file ALT_CD is a key but dont need to mention any column as key as it is reading from a sequential file stage.
Suresh Reddy
ETL Developer
Research Operations
"its important to know in which direction we are moving rather than where we are"
In target also use same type of schema file but you have to change format which is first line in schema files and column names according to target database table, dont need to mention any key here also and we loaded using load method not a upsert option.Try with load option there is nothing wrong using that. Its a happy path to load into table when you are aware of all table structure
Suresh Reddy
ETL Developer
Research Operations
"its important to know in which direction we are moving rather than where we are"
sureshreddy2009 wrote:In target also use same type of schema file but you have to change format which is first line in schema files and column names according to target database table, dont need to mention any key here also and we loaded using load method not a upsert option.Try with load option there is nothing wrong using that. Its a happy path to load into table when you are aware of all table structure
And through which property can we specify the schema file in oracle stage?
Basically if columns present in source and oracle are same then dont need to mention any schema file any where while loading.Enable RCP.It will take care otherwise use column export after sequential file stage to convert into string and column import before oracle stage to convert it into desired structure , for transformations use tranformer in between that. there is option schema file option in both column export and column import
Suresh Reddy
ETL Developer
Research Operations
"its important to know in which direction we are moving rather than where we are"
sureshreddy2009 wrote:Basically if columns present in source and oracle are same then dont need to mention any schema file any where while loading.Enable RCP.It will take care otherwise use column export after sequential file stage to convert into string and column import before oracle stage to convert it into desired structure , for transformations use tranformer in between that. there is option schema file option in both column export and column import
For load its working fine now thanks for help.
Now i need to find a method to implement upsert.
Because i have requirement where rows might be there i need to update the value fields as table has primary key and i cannot insert same records.