Database cleanup Error

Avatar

Avatar
Validate 1
Level 2
uagnihotri
Level 2

Likes

7 likes

Total Posts

23 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
uagnihotri
Level 2

Likes

7 likes

Total Posts

23 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 1
View profile
uagnihotri
Level 2

07-06-2018

While running the DB cleanup workflow, the workflow fails while running the "Updating RDBMS statistics (up_updatestats)...", the workflows fails with error as given below:

2018-06-06 15:40:35.640-06 0000CA88 0000CB30   1 verbose log Updating RDBMS statistics (up_updatestats)...

2018-06-06 15:40:35.988-06 0000CA88 0000CB30   1 error log ODB-240000 ODBC error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Updating NmsOperation SQLState: 01000 (iRc=-2006)

2018-06-06 15:40:35.988-06 0000CA88 0000CB30   1 error log ODB-240000 ODBC error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Updating XtkFileRes SQLState: 01000 (iRc=-2006)

Could anyone provide me any details on this "up_updatestats"? The DB workflow used to run successfully in past. It recently started throwing this error.

Note: Other workflows runs successfully without error (marketing and non-marketing workflows).

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
uagnihotri
Level 2

Likes

7 likes

Total Posts

23 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
uagnihotri
Level 2

Likes

7 likes

Total Posts

23 posts

Correct reply

3 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 1
View profile
uagnihotri
Level 2

08-06-2018

This the only information logged by Campaign. SQLState: 01000 is misleading.

We have resolved the issue by changing the up_updatestats stored procedure. The code in the stored procedure doesn't handle the tables properly which are not owned by the DB owner of the Campaign Database.

Answers (2)

Answers (2)

Avatar

Avatar
Validate 1
MVP
Jean-Serge_Biro
MVP

Likes

353 likes

Total Posts

464 posts

Correct reply

153 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile

Avatar
Validate 1
MVP
Jean-Serge_Biro
MVP

Likes

353 likes

Total Posts

464 posts

Correct reply

153 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile
Jean-Serge_Biro
MVP

08-06-2018

Hi uagnihotri,


We did the same in 2015, by adding a where clause to exclude all objects belonging to another schema than the user neolane (adobe campaign) that owns the AC tables, for our SQL Server DB.

We provided to Adobe Campaign support this information in 2015 in order they could integrate this correction in future releases, but not done yet.


So please take care when upgrading your AC instance (build update), you have to keep changes safe (backup).
It is not managed by the Conflict management of postupgrade process, as far as I know.

Regards
J-Serge

Avatar

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

370 likes

Total Posts

726 posts

Correct reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile

Avatar
Validate 1
Employee
Vapsy
Employee

Likes

370 likes

Total Posts

726 posts

Correct reply

342 solutions
Top badges earned
Validate 1
Boost 50
Boost 5
Boost 3
Boost 250
View profile
Vapsy
Employee

07-06-2018

Hi there,

Can you please share the error message. The 3 lines you have shared don't share much information.

Are these the only error logs or if there is more to it

Regards,
Vipul