topic Re: Logging to database - There is already an object named... in Talend Studio

Logging to database - There is already an object named...

Anonymous — Sat, 16 Nov 2024 04:43:59 GMT

Hi,

I want to write logs to my database, and I changed the Project Settings > Job Settings > Stats & Logs to write to my Azure SQL Database.

This went well the first time, but the second time I ran the job, Talend threw an error complaining that "There is already an object named 'TALEND_STATS' in the database." I got the same error for my TALEND_LOGS table.

I would expect the Stats & Logs feature to simply insert stats and logs records into these tables.

Any ideas?

Re: Logging to database - There is already an object named...

Anonymous — Tue, 10 Sep 2019 09:34:02 GMT

Hello,

Could you please show us your setting screenshot of Project Settings > Job Settings > Stats & Logs? On which talend build version you got this issue?

Best regards

Sabrina

Re: Logging to database - There is already an object named...

Anonymous — Tue, 10 Sep 2019 10:48:38 GMT

Hi,

I am using build version:

And my project settings are like so:

Re: Logging to database - There is already an object named...

Anonymous — Sat, 14 Sep 2019 16:47:57 GMT

Hi Sabrina,

What did you make of my reply?

Trond

Re: Logging to database - There is already an object named...

Sujay1 — Sat, 14 Sep 2019 17:02:01 GMT

@trondis80_old would you mind sharing your table schema's . I'm also planning to store logs in database if the performance is not impacted. Could be handy if you can share the 3 table schema's.

Re: Logging to database - There is already an object named...

Anonymous — Mon, 16 Sep 2019 07:40:35 GMT

Hi,

I am only using log and stats. The tables have been created by the jobs by Talend. Here are the definitions:

CREATE TABLE [OP].[TALEND_LOGS](
[moment] [datetime] NULL,
[pid] [varchar](20) NULL,
[root_pid] [varchar](20) NULL,
[father_pid] [varchar](20) NULL,
[project] [varchar](50) NULL,
[job] [varchar](255) NULL,
[context] [varchar](50) NULL,
[priority] [int] NULL,
[type] [varchar](255) NULL,
[origin] [varchar](255) NULL,
[message] [varchar](255) NULL,
[code] [int] NULL
) ON [PRIMARY]

CREATE TABLE [OP].[TALEND_STATS](
[moment] [datetime] NULL,
[pid] [varchar](20) NULL,
[father_pid] [varchar](20) NULL,
[root_pid] [varchar](20) NULL,
[system_pid] [bigint] NULL,
[project] [varchar](50) NULL,
[job] [varchar](255) NULL,
[job_repository_id] [varchar](255) NULL,
[job_version] [varchar](255) NULL,
[context] [varchar](50) NULL,
[origin] [varchar](255) NULL,
[message_type] [varchar](255) NULL,
[message] [varchar](255) NULL,
[duration] [bigint] NULL
) ON [PRIMARY]

Re: Logging to database - There is already an object named...

Sujay1 — Mon, 16 Sep 2019 11:00:15 GMT

thanks alot @trondis80_old for table schema.

Re: Logging to database - There is already an object named...

Anonymous — Mon, 16 Sep 2019 18:18:39 GMT

@trondis80_old
Are you using tStatCatcher and tLogCatcher components in your job?
Also if could share screenshot of your Job Design. So it will be easy to identify the issue.