PG source and DB2 Target DDL's are matching but getting Null value to not null column/duplicate records error
Hi All,
We are trying to perform full load from PostGres DB to Mainframe DB2 Target.
We are matching with DDL's but still getting below errors :
1) execute statement failed RetCode: SQL_ERROR SqlState: 23502 NativeError: -407 Message: [IBM][CLI Driver][DB2] SQL0407N Assignment of a NULL value to a NOT NULL column "*N" is not allowed. SQLSTATE=23502 Line: 66 Column: -2
What is *N column in above statement ?
2) RetCode: SQL_ERROR SqlState: 23505 NativeError: -803 Message: [IBM][CLI Driver][DB2] SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "ITOM0582" constrains table "0000002201" from having duplicate values for the index key. SQLSTATE=23505
I did a quick search and found that this may be a know limitation. Please check out the following:
From the logs, it appears as expected behaviour, We do have limitation "The default configuration of Replica identity is supported only" when you are using as "PostgreSQL" endpoint.
You need to open FeatureRequest to support FULL IDENTIFY.
To submit Feature Requests going forward please use our Qlik Community "Product Insight and Ideas" forum as these requests will no longer be handled as technical support cases. As a Qlik Community member, you can actively engage with our Product Management team, vote on a product idea coming for other Qlik customers, submit your own ideas and get feedback from other members.
You will be required to have a Qlik ID to logon to the Community which is not the same as your support portal logon. If you have previously registered for a Qlik ID such as one you use to access the downloads site, you can use the same to logon for the Community. First time accessing Community with a Qlik idea will prompt for a username alias to be used when posting to the Community. This alias is not a logon but for display purposes when posting. If you do not have a Qlik ID for logon, you can register at the logon screen. The Ideas blog post will provide information on how to use the Ideas board and how to access it.
If you have any issues registering or logging on to the Community, please submit a new case with the issue you are having so we can direct the case to our Customer Service team for assistance. Please let us know if there is anything else we can do for you at this point as this is no longer the place to submit feature requests.
I did a quick search and found that this may be a know limitation. Please check out the following:
From the logs, it appears as expected behaviour, We do have limitation "The default configuration of Replica identity is supported only" when you are using as "PostgreSQL" endpoint.
You need to open FeatureRequest to support FULL IDENTIFY.
To submit Feature Requests going forward please use our Qlik Community "Product Insight and Ideas" forum as these requests will no longer be handled as technical support cases. As a Qlik Community member, you can actively engage with our Product Management team, vote on a product idea coming for other Qlik customers, submit your own ideas and get feedback from other members.
You will be required to have a Qlik ID to logon to the Community which is not the same as your support portal logon. If you have previously registered for a Qlik ID such as one you use to access the downloads site, you can use the same to logon for the Community. First time accessing Community with a Qlik idea will prompt for a username alias to be used when posting to the Community. This alias is not a logon but for display purposes when posting. If you do not have a Qlik ID for logon, you can register at the logon screen. The Ideas blog post will provide information on how to use the Ideas board and how to access it.
If you have any issues registering or logging on to the Community, please submit a new case with the issue you are having so we can direct the case to our Customer Service team for assistance. Please let us know if there is anything else we can do for you at this point as this is no longer the place to submit feature requests.
