All - here in Bath we have encountered an error during a live pay run, whereby about 5000 assignments failed with:

"Ora-01003: no statement parsed

Has occurred in table pay_person_latest_balances at location 555"

Before I embark on another epic dialog with support (which will probably end with the instruction to trash latest balances), has anyone else come across this?

Haven't seen it before but its not a table space issue is it?

Delboy

No, but we have found an error that seems to have given rise to these other errors:

APP-PAY-06881: Error ORA-04020: deadlock detected while trying to lock object $BUILD$.<hex number> has occurred in table pay_person_latest_balances at location 555

There is an rdbms bug, 12531263, which mentions rdbms version 11.1.0.7 (which is our current version) as an affected platform

What we don't know yet is what circumstances gave rise to the deadlock. Looks like the payroll worker process didn't deal with it very well though.

Bumping this to see if anyone else gets this error during Security List Maintenance - we appear to be getting this now on a regular basis.

Any takers?