Skip to Content
0

How to solve the message duplicate column in the custom pass.

Apr 03, 2017 at 06:48 AM

69

avatar image
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Lambert Boskamp Apr 03, 2017 at 08:20 AM
0

Hi René,

do you get this error at designtime (in Eclipse) or at runtime (in the job log)? Can you please post the full error message or a screenshot of it?

The pass, specifically the destination, looks OK to me in the screenshots. Maybe there's a problem in SAP IDM trying to modify/alter the definition (i.e., columns/data types) before actually dealing with the data to be inserted/updated.

To solve such schema problems, what I typically do is drop the table using SQL, then re-run the job to have it recreated from scratch. Please note, however, that this approach is only applicable if the table contains purely temporary data that can be restored at any time. This is something you need to check based on your specific environment.

If manually dropping the table is an option, try a "DROP TABLE db_imsrepprivassign" from an SQL client connected as runtime user (MXMC_RT, by default).

Kind regards,

Lambert

Share
10 |10000 characters needed characters left characters exceeded
E.R. Silooy Apr 03, 2017 at 10:15 AM
0

Hi Lambert,




I tried onde again to start the complete job . I stil get the same errors.

The pass is called from a job. The first step of the job is dropping the database.

The Systemlog at the runtime is u26-idmrenefigure-6-systemlog-on-the-rumtime.jpg

and the log of the job at the eclipse u26-idmrenefigure-7-job-log-on-the-eclipse.jpg

We are running on the Oracle version 12 .

Kindly regards,

René


Share
10 |10000 characters needed characters left characters exceeded
Lambert Boskamp Apr 04, 2017 at 11:24 AM
0

From the runtime job log, it seems the SQL executed at runtime, which really has the column name 'MX_PRIVILEGE' two times, doesn't match the definition of your pass destination at designtime.

Try a package export containing this job and look at the pass definition in XML. Maybe the destination line with attribute "MX_PRIVILEGE" really occurs two times in XML or at least looks different than what is displayed in Eclipse.

To fix it, I would try to manually re-create the buggy toDatabase pass by creating a new toDatabase pass in the job from scratch as a replacement for the current one. Don't use copy pass & paste for the whole pass. Instead, create a new toDatabase pass manually and adjust all data as needed. Move it to the appropriate position, disable the old one and try again.

Hope that helps,

Lambert

Share
10 |10000 characters needed characters left characters exceeded