SDE_ORAR1213_ADAPTOR_SDE_ORA_SLAJOURNALFACT

Question

Hi All ,

I have installed OBIA 11.1.1.10.1 successfully and started  load plan for three years of data from Oracle EBS as source and our EBS data source is completely around 300 GB and we have enough data space in ware house .We started the data loading execution and some of the jobs in ODI had executed successfully and now the above job is in running (Job name is in Subject).It is taking long run and failing with some temp space issue in the EBS and ware house .

We have increased the temp table space in 1TB in EBS and ware house .Initaiated the this jobs for execution again and it has given the error as

ODI-1227: Task SrcSet0 (Loading) fails on the source ORACLE connection Oracle_EBS_DEV_12_1_3.

Caused By: java.sql.SQLException: ORA-01555: snapshot too old: rollback segment number 1 with name "_SYSSMU1_2971190618$" too small.

For this we increase the UNDOTBS1 up to 500 Gb again we started execution this job in ODI it is still taking long 12 hours and giving the error as same .It is not inserting any data in to the temp table of ODI i.e c$ table during this job execution .

If any one has experienced this kind of problem please help us .

The job in ODI is SDE_ORAR1213_ADAPTOR_SDE_ORA_SLAJOURNALFACT

Thanks

Bec_Wagner · Answer

You will get a snapshot too old error when too many new transactions/records are entered into the table you are querying from. Since this is a query that is still running in EBS and hasn't moved to inserting any records into the C$ table, that would make sense. The only time I've actually gotten this error myself was during an initial load, against Subledger accounting as well, and when I was using an active dataguard replication as my EBS source database. (Which is technically not supported, btw)

Two suggestions -

1. Follow the recommendations of the performance doc for OBIA 11g (which says to allot 4X temp space in EBS as the size of the data, along with some undo recommendations) - Oracle Business Intelligence Applications Version 11g Performance Recommendations (Doc ID 1963225.1)

2. Try to run when the least amount of activity will be hitting the sub ledger accounting tables. So for example if you have some overnight batch processing, probably not then.

--Bec

993000 · Answer

Can any help me on this .

Thanks