IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  DB Error: Failed to open file

    Posted 05/22/08 05:12 PM

    Originally posted by: SystemAdmin


    I am using a RUN command to override db settings on a target card using the Resource Registry files. The command line in the audit log created looks correct to me and the alias is resolving correctly from the mrn file. I have tried everything I can think of to get beyond this error but nothing has made any difference.

    Here is the command line:

    <CommandLine>'C:\Documents and Settings\Jennifer\My Documents\IBM Customers\Kaiser Permanente\Claims\maps\C_Mini_837_CFF_to_DB.mmc' -IF1X %cff_temp_folder%Mini837_133052274_520954463_149.txt -IF2X %cff_temp_folder%MiniCFF_133052274_520954463_149.txt -OD1 '%store_edi_uow_db%' -OD2 '%store_app_uow_db%' -OF3 %cff_temp_folder%TRAP_133052274_520954463_149.txt -AER=%inbound837_logs%Mer_4010X096A1_837_CFF_to_DB_20080522165821187000.log</CommandLine>

    Here is the target report showing the alias resolution:

    <TargetReport card="1" adapter="DB" bytes="4815" adapterreturn="-10003">
    <Message>Failed to open file</Message>
    <Settings>-m ..\mdq\KB_Custom_DB.mdq -dn KP Custom DB -traceerr ..\logs\store_edi_uow_db.dbl -proc KPMC.STORE_EDI_UOW</Settings>
    </TargetReport>

    I have tried moving the mdq to the map folder. I have tried adding single quotes, two sets of single quotes and even one set of regular double quotes around the db name. I have removed the -proc setting so it would default to the one compiled in the map. The logs folder does exist, as does the mdq folder specified. Not a single one of these changes has resulted in anything other than the error message above.

    Has anyone seen this? I have to resolve this asap so time is of the urgency! Any and all suggestions are appreciated.

    Regards,
    Jennifer
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: DB Error: Failed to open file

    Posted 05/23/08 07:15 AM

    Originally posted by: SystemAdmin


    If the removing the spaces from the dbname did not help...

    Are you are running from the map designer or the broker? Just to test something, what if you run the c_map map directly, do you see the same behavior? You may have said you tried this, I can’t remember.

    Another suggestion is to try changing the alias to use the db adapter commands for connection instead of the mdq file reference. I think that would be dbtype, connectstring, user and password.

    The strange thing is the error code, looks like more like a network error, it is not one of the db adapter resource return/error codes.
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender