Error ‘Archive is corrupted’ While Unzipping through Pentaho


Error ‘Archive is corrupted’ While Unzipping through Pentaho


Occasionally, this issue occurs when you are trying to unzip the archive file you received through FTP transfer. Resolution for this is two-step process.

 Step 1: Checking the FTP transfer data type of file. Please follow the below steps:      

  • Open your FileZilla FTP client. 
  •  Click on ‘Edit’ tab and select ‘Settings’. This will open pop up. 
  • Under ‘Transfers’ section, select ‘File Types’.
  • Please choose ‘Binary’ as your Default transfer type.
Note: Setting the Binary as your default transfer type will prevent your files to become corrupted while ftp transit.

Step 2: Binary Mode check box under ‘Get a File with FTP’ component before ‘Unzip file’ component in Pentaho should be marked as check.

  • Once you tick the Binary Mode under ‘Get a File with FTP’ component, it will download the zip file in Binary format preventing your archive files to become corrupted. Please refer below snippet:


 Note:  So, now when you will try to Unzip a file in next ‘Unzip file’ component of your pentaho job it will work fine. Kudos.

Comments

Post a Comment

Popular posts from this blog

Simple Program to Check Active Requests in ODSOs / ADSOs

In this document, we will create a program to check the whether an ODSO/ADSO is having an Active request or not. Scenario : We have BW data flow which loads data from the Source System to DSO and from DSO to further multiple targets, and at the end of the Process Chain the request should get deleted from the source. Here, we have a case if someone did an ad-hoc load from Source System to DSO and subsequently to targets, and forgot to delete the request from the DSO. This leads to duplicate data into Targets in next Process Chain run. Solution : To take care of the above case we can keep a checkpoint in the Process Chain which will monitor the request in DSO.  If an existing request is found in DSO, then a notification can be displayed and we can go ahead and remove it manually.  Case1 : When we have Extraction Layer as ODSO . As we all know SAP has given a Standard Function Module RSSM_ICUBE_REQUESTS_GET which can be used to get the DTP requests which are presen
Read more

Simplification List for SAP BW/4HANA (SAP Release 18th June’ 2018)

This document is for the consultant who is working on converting the system from SAP Business Warehouse to SAP BW/4HANA. Conversion Type:  in-place conversion System:  SAP BW 7.5 SP5, powered by SAP HANA or higher Program:  RS_B4HANA_CONVERSION_CONTROL to determine which objects are available in or can be converted to SAP BW/4HANA BW4 Transfer Tool:  Program  RS_B4HANA_TRF  or  STC01/STC02  and select Task List as SAP_BW4_TRANSFER_INPLACE Below are the list of Objects which are not available or to be converted in SAP BW4/HANA supported objects: 1.      SAP BW Accelerator ( BWA ) is not available. 2.      The  BW/BI Add-on for SAP GUI  i.e. front-end tools are not available Ø  BEx Query Designer Ø  BEx Web Application Designer Ø  BEx Analyzer Ø  BEx Enterprise Report Designer SAP BW – Data Warehousing: 1.       InfoObject Catalogs  are not available. It has been replaced by InfoAreas. 2.      The following types of  InfoObjects  are not available in SAP
Read more

Unforeseen Issue during SAP BW Data Flow Migration

Purpose : To migrate SAP BW Data Flow from 3.x to 7.x version. Tool :  RSMIGRATE (provided by SAP) SAP makes our life easy by providing a great tool to migrate the BW 3.x version to 7.x version automatically. It also provides supportive SAP Notes/KBA for the known errors and issues. However, there were undocumented few issues which we came across during our migration activities. In this post, we will share 'unforeseen issues' and their resolutions which were mostly manual efforts. 1.     Update Rule -  Return Table Logic:  In SAP BW 3.x version we have  Return Table logic  to replicate the source record into multiple record based on key figures as per the requirement. However, in  Transformation  this return table is unsupported and cannot be converted by RSMIGRATE tool automatically.        We need to correct it manually by writing the split logic in end routine.        Here is the key, which we can use- https://www.sdn.sap.com/irj/servlet/prt/portal/p
Read more