| Temp objects stops log apply at standby [message #608560] |
Fri, 21 February 2014 01:21  |
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
|
Senior Member |
|
|
Dear All,
On logical standby, temp objects are getting piled-up and stops apply process. We have to skip those transactions manually.
i.e
owner.dbms_tabcomp_temp_cmp
owner.dbms_tabcomp_temp_uncmp
Is there any way to handle it, so that no need of manual work? May be this is happening because at primary side user might be running jobs and through that temp table is creating and getting dropped after it completion and not getting sync at logical side?
Waiting for your kind response on the same...
Regards,
Ashish Kumar Mahanta
|
|
|
|
| Re: Temp objects stops log apply at standby [message #608574 is a reply to message #608560] |
Fri, 21 February 2014 02:50  |
John Watson
Messages: 8804
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I think you have to provide better information. For example:
What are these "temp objects"? Are they, for example, global temporary tables? Or something else?
What does "getting piled up" mean?
You say "temp table is creating and getting dropped". Are you really saying tht your software creates and drops tables dynamically? Why??
What does "not getting sync at logical side" mean?
|
|
|
|
| Re: Temp objects stops log apply at standby [message #608731 is a reply to message #608574] |
Mon, 24 February 2014 00:32 |
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
|
Senior Member |
|
|
Dear John,
Below mentioned tables are global temporary tables. These are getting created during the initiation of batch job and gets dropped before job complete.
How to skip these objects so that ODS database should not be out of sync.
Since, we need to skip these transactions manually to make SYNC with OLTP.
Regards,
Ashish Kumar Mahanta
|
|
|
|
|
|
|
|
|
|
] 
Search
Help
Members
Register
Login
Home
