Cleaner process still giving problems?

[justin_willey]

Re-loading a v12.0.1.3152 database I get this error message

Could not execute statement. User 'another user' has the row in 'Person' locked SQLCODE=-210, ODBC 3 State="40001" Line 23582, column 1 You can continue executing or stop.

ALTER TABLE "pears"."employment" ADD NOT NULL FOREIGN KEY "person" ("personid") REFERENCES "pears"."Person" ("personid")

This is similar to this question (Dec 2009), relating to 10.0.1 where the issue seemed to be the cleaner process, and work was in progress to resolve this.

I don't see anything in the latest readme about cleaner issues since 3152, and wonder if this problem could have returned. The tables in question have several 100,000 rows each, but are much smaller than other tables that have similar keys and re-loaded without problem.

There are of course no other external users connected to the database.

[Breck_Carter]

What is the page size of the database? Does the target database have the same page size?

[justin_willey]

It was 4k to 4k - no change.

[Former Member · Accepted solution]

As far as I'm aware, we had solved this specific problem in 2009. QTS 605792 renamed all background connections so that, in case this sort of problem was reported, a more useful identifier than "other user" would be reported. That fix went into 12.0.0GA, in addition to 10.0.1 and 11.0.1. QTS 609706 embodies the changes made to prevent DDL statements, such as ALTER TABLE, from reporting an error due to cleaner activity. This also shipped in 12.0.0GA.

Is this problem reproducible, Justin? Will your reload.sql script create this problem reproducibly? If so, I would like to see that script and get it to fail here in the lab.

My apologies for the inconvenience.

[justin_willey · Accepted solution]

Glen, thanks for taking a look at this.

I'll try running it again and see if the same thing happens.

The reload data itself is pretty big (50 GB odd) and contains data we can't release; the script itself is no problem, but I suspect that won't be enough.

[justin_willey · Accepted solution]

It didn't happen a re-run, but I'll be doing this a few more times before its finished, so I'll see if it repeats. Thanks.