Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I'm having an issue where my app reload is failing during or just after Joining/Keeping but I'm not sure why, I get a random '-129 =' in the log and then it fails (see below). This -129 is not something contained within my script.
20220425T215317.375+0100 0286 Left join (HRLSales) LOAD * Resident salesFact
20220425T215317.376+0100 60 fields found: Transaction_Type, Retailer_Code, ePOS_Product_Code, ePOS_EAN, ePOS_Product_Desc, Qty_Sold, Litre_or_Weight_Volume, Litre_or_Weight_Price_Per, ePOS_Cost_Price, ePOS_Selling_Price, Sales_Before_Discount, Discount_Value, Sales_Value_Gross, VAT_Code, VAT_Rate, ePOS_Dept, ePOS_Sub_Dept, VAT_Value, Vatable_Sales, GP_Value, ePOS_Comm_Group, HR_Commodity_Group, Non_Scan_Indicator, Price_Override_Indicator, ePOS_Pack_Size, ePOS_Supplier_Code, ePOS_Standard_RSP, Date, HRL_Finance_Report_Dept_Desc, HRL Finance Dept, Finance Group, ePOS_Weighted_Indicator, Reduced_Qty, Proj GP %, Static GP Adj, News Delivery, Budget Value, Line_Voided_Indicator, Reduced_To_Price, Reduced_To_Retail, Reduced_By_Retail, Reduced_Cost, IT_Datasource, IT_EAN_Link, IT_Scan_Cm_Link, ProdRetID, IT_Product_EAN_Link, IT_Promo_Sales_Link, Wastage_Qty, Wastage_Cost_Value, Wastage_Retail_Value, Wastage_Code, Wastage_Reason_Code, Budget Nett Sales, Budget GP%, Budget GP Value, Manual Wastage, Coupon Value, Coupon VAT, Coupon Vatable Sales,
20220425T221129.533+0100 860,500,906 lines fetched
20220425T221129.533+0100 Joining/Keeping
20220425T222433.938+0100 -129 =
20220425T222724.667+0100 Execution Failed
20220425T222725.042+0100 Execution finished.
129 generally means the system is out of resources (memory). Either the machine you are working on lacks the resources required to complete the join (quite possible considering the number of lines), or there's something wrong with the join itself causing it to take up more memory than it should.
129 generally means the system is out of resources (memory). Either the machine you are working on lacks the resources required to complete the join (quite possible considering the number of lines), or there's something wrong with the join itself causing it to take up more memory than it should.
Thanks Or, I suspected as much!