With TOS 2.3.1, under Linux Ubuntu 7.10 (Gutsy), I don't reproduce the problem with an exported script. In the zip archive, I have the Mysql.pm module:

[pierrick@plegall] /tmp/topic2439_0.1
$ tree
.
`-- topic2439
    |-- SUSE.job_topic2439.pl
    |-- SUSE.job_topic2439_Default.pl
    |-- lib
    |   |-- routines
    |   |   |-- SUSE
    |   |   |   `-- topic2399.pm
    |   |   `-- system
    |   |       |-- Date.pm
    |   |       |-- Misc.pm
    |   |       |-- Numeric.pm
    |   |       `-- String.pm
    |   |-- tMysqlOutput
    |   |   `-- Mysql.pm
    |   `-- talend
    |       |-- dbOp.pm
    |       |-- filesOp.pm
    |       |-- runstat.pm
    |       `-- trace.pm
    |-- src
    |   |-- talend.project
    |   |-- topic2439_0.1.item
    |   `-- topic2439_0.1.properties
    |-- topic2439_run.bat
    `-- topic2439_run.sh

8 directories, 17 files

In the zip archive, do you see the Mysql.pm module? What is the content of your *run.bat, and *run.sh files?

raton wrote:

Hum, I use the option "Export Talend projects" (and I am on windows) and I don't think this option creates the same structure of Zip archive. (as I can't see any "lib" folder for example ...)

OK, I misunderstood your words. In Talend Open Studio, we have 2 types of export : item export and script export. When you want to import an item (a job, a metadata or a routine) in another project, you first export the related item from the source project. If you want to deploy the job on your production server, then you export the script corresponding to the job.

raton wrote:

BUT, worst than that, if I am using a new tMysqlOutput component in a new job, it still does work with the same error message than in my previous post

Here is the real problem. As I don't reproduce the problem, I need more information. Can you describe the job and give screenshots?

raton wrote:

[...] AND tMysqlOutput appears with status "Not installed" in the list of module.

This is a known bug that is fixed in TOS 2.3.2 see [Bugtracker, bug 3225, fixed] [Module View] Specific perl modules from other components exists but an error is shown.

raton wrote:

Thanks again for the reply. "know bugs", I like that ... may I have an insight about when TOS v2.3.2 would be out?? ;-)

It's a matter of days. It should be available before the end of the week if we don't find a blocking bug.

Ok, I think I worked it out.

As I wrote previously, same jobs were working on different computers with the same version of TOS. So I re-unzip TOS on the server (that wasn't working) imported the project and it did work out just fine. So know I am not going to change anything for a bit of time.

On of the things I had previously changed on the TOS v2.3.1 that wasn't working was the "components" paths as I was working on developping my own TOS components. I previously changed the paths back with Restore Defaults but it didn't change anything ... there is something fishy with these three component paths "User component folder", "Component default filepath" and "Component Project" in the Talend Component Designer preferences. Which I am not going to try now that I have my job working again ...

Anyway, many thanks again to the Talend Team, very helpful as usual.

Thanks for this detailed investigation, I'll try to reproduce.

What are the names of your own components?

A tiny bit more information ( I am not investigating but I needed a "quick" fix today to process some files... ;-) )

I re-unzipped TOS v2.3.1 to get a new clean start of the day.
I had to define in the preferences the folder with my components otherwise the job with the custom components won't load. But if I de-activate the custom components, I can run the rest of the job all sweet, with the tMysqlOutput working.

Then as soon as I activate the custom components, the tMysqlOutput are gone, forever and for every jobs (even those without custom components) until I use a "fresh" TOS ...

I hope this helps.

Step 1 to 4 seem to be exactly the same than what I do.

In step 5, did you use the tApacheLogInput component in your job? I can put my custom component in the job and de-activate it and tMysqlOutput still works but as soon as I activate it I have the issue with tMysqlOutput.

Note: I am not sure if it is related but my TOS folder is "C:\TOS" while my custom components folder is "F:\My_components". (sorry for indicating the wrong folder name yesterday)

Bad news of the day, the problem is still there .... it ("it" as "the problem") just seems to be behaving differently now.

I haven't had time to do any investigation yet but from what I did, I started TOS v2.3.2, ran many jobs, modified them, closed/restarted TOS many times ... it was all working very well. (note: all my jobs use tMysqlOutput)

Then I had to use one of these jobs that uses one of my custom made components, I mapped my custom component folder, opened the job, ran it and modified it many time ... all working very well. Then I closed TOS and after restarting it, tMysqlOutput doesn't work anymore, same error message than previously:
"Undefined subroutine &tMysqlOutput::Mysql::performTableAction"
...

Hi,

Iam new to talend and dealing with scd type1

If it's a brand new record then Insert it with REC_ADD_TS as Sysdate
If record exists then compare all non key source attributes with target attributes
If atleast one field changes then update values in Target based  on keys and also maintain REC_CHG_TS as Sysdate for updated records.

Any solutions for this