How do I fix "ORA-01555: snapshot too old" in Oracle Fusion?

1. Cancel the current run, using the etiquette ladder (Cancel → Force Cancel after 30 min → SR if stuck) 2. Run the timings SQL to see exactly where the hours went 3. Compare with the last healthy run: when was it, what request id, what changed in volume since 4. Rerun with a tighter cutoff date; recurring at normal volume → SR

Home / Troubleshooting / Cost Processor Errors / this error

Oracle Fusion Cost Management · cost processor error · cause and fix

ORA-01555: snapshot too old

Error code: ORA-01555

The run lived longer than the database could hold a consistent picture of the data for it, the signature of a run that has grown too big or too slow. (The ValidatePeriod flavor of this error usually just means uncosted transactions are pending: rerun all the cost processes in sequence.)

Root cause

Pure performance: the run outlived database undo.

How to fix it

Cancel the current run, using the etiquette ladder (Cancel → Force Cancel after 30 min → SR if stuck)
Run the timings SQL to see exactly where the hours went
Compare with the last healthy run: when was it, what request id, what changed in volume since
Rerun with a tighter cutoff date; recurring at normal volume → SR

Where to go in Fusion

Navigator, Tools, Scheduled Processes → Cancel Process on the stuck run
Cost Accounting work area, Review Cost Accounting Processes (find your request id)
Cost Accounting work area, Create Cost Accounting Distributions (the cost processor)

Diagnostic SQL

Where did the time go?

select * from cst_sql_timings where request_id = &request_id

Last five runs of the processor

select * from (select * from cst_cp_requests order by creation_date desc) where rownum <= 5

Read-only diagnostic queries. Substitute the bind values for your instance; run in a test environment first.

Oracle references

My Oracle Support document IDs for readers with access: 2257853.1. We do not reproduce their content.

Checked Cost processor behavior for Oracle Fusion Cost Management, rewritten in plain words from publicly known troubleshooting practice and reviewed by a working consultant. Checked against the current release, Jul 2026. Amounts, account names and navigation vary by configuration; verify in your own instance and test before acting.

Solve it, then prevent it

This page explains one error. These help with the rest:

🔧Search any cost processor errorThe interactive triage: paste your error, get the card.→🧾The setup behind these errorsThe Cost Management implementation guide.→✅Close without surprisesThe dependency-ordered SCM period close checklist.→

More cost processor errors