cancel
Showing results for 
Search instead for 
Did you mean: 

BODS maximum number of rows per partition reached for table

Former Member
0 Kudos

HI All,

When we are trying to run our BODS job in Q1 , we are facing the below issue, But job is running fine in DEV with same source file.

Our Source is Flatfile and loading data to SAP HANA.

ODBC data source <bgc9158> error message for operation <SQLExecute>: <[SAP AG][LIBODBCHDB DLL][HDBODBC] General error;2055

  maximum number of rows per partition reached for table: 'BGC_CAR:SECA_INSERT'>.

Dataflow DF_RECA_INSERT|EECA_INSERT

                                                     ODBC data source <bgc9158> error message for operation <SQLExecute>: <[SAP AG][LIBODBCHDB DLL][HDBODBC] General error;2055

                                                     maximum number of rows per partition reached for table: 'ECC_DQ:EECA_INSERT'>.

(14.2) 10-21-15 17:32:11 (E) (5084:6900) DBS-070407: SQL submitted to database <> resulted in error <[SAP AG][LIBODBCHDB DLL][HDBODBC] Integrity constraint violation;301 unique

                                                     constraint violated: TrexUpdate failed on table 'ECC_DQ:PIRE_CUST_COMP' with error: unique constraint violation on

                                                     pos=1048575 for table ECC_DQ:PIRE_CUST_COMPen, key: $t>. The SQL submitted is <INSERT INTO ECC_DQ.PIRE_CUST_COMP

                                                     SELECT * FROM ECC_DQ.HCC_temp>.

(14.2) 10-21-15 17:32:12 (E) (5084:6900) DBS-070407: |Session JACCA_pirengageAssign|Work flow WF_JECA

                                                     SQL submitted to database <> resulted in error <[SAP AG][LIBODBCHDB DLL][HDBODBC] Integrity constraint violation;301 unique

                                                     constraint violated: TrexUpdate failed on table 'ECC_DQ:PIRE_CUST_COMP' with error: unique constraint violation on

                                                     pos=1048575 for table ECC_DQ:PIRE_CUST_COMPen, key: $t>. The SQL submitted is <INSERT INTO ECC_DQ.PIRE_CUST_COMP

                                                     SELECT * FROM ECC_DQ.HCC_temp>.

(14.2) 10-21-15 17:32:12 (E) (5084:6900) RUN-050304: |Session JACCA_pirengageAssign|Work flow WF_JECA

                                                     Function call <sql ( etl_ds_kd2, INSERT INTO ECC_DQ.PIRE_CUST_COMP SELECT * FROM ECC_DQ.HCC_temp ) > failed, due to error

                                                     <70407>: <SQL submitted to database <> resulted in error <[SAP AG][LIBODBCHDB DLL][HDBODBC] Integrity constraint violation;301

                                                     unique constraint violated: TrexUpdate failed on table 'ECC_DQ:PIRE_CUST_COMP' with error: unique constraint violation on

                                                     pos=1048575 for table ECC_DQ:PIRE_CUST_COMPen, key: $t>. The SQL submitted is <INSERT INTO ECC_DQ.PIRE_CUST_COMP

                                                     SELECT * FROM ECC_DQ.HCC_temp>.>.

(14.2) 10-21-15 17:32:12 (E) (5084:6900) DBS-070407: |Session JACCA_pirengageAssign|Work flow WF_JECA

                                                     SQL submitted to database <> resulted in error <[SAP AG][LIBODBCHDB DLL][HDBODBC] Integrity constraint violation;301 unique

                                                     constraint violated: TrexUpdate failed on table 'ECC_DQ:PIRE_CUST_COMP' with error: unique constraint violation on

                                                     pos=1048575 for table ECC_DQ:PIRE_CUST_COMPen, key: $t>. The SQL submitted is <INSERT INTO ECC_DQ.PIRE_CUST_COMP

                                                     SELECT * FROM ECC_DQ.HCC_temp>.

Thanks

vinay

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member198401
Active Contributor
0 Kudos

It  seems that there is an integrity check on a primary key in SAP HANA which is getting failed while loading data.

Check for other parameters on the table like read/write rights

Regards

Arun Sasi

Former Member
0 Kudos

Thanks Arun for quick reply, All our staging Tables are TEMP table ,only final Target table is RDBMS Tables. we are loading more that 12 million records.