we have a oracle replication to mssql2k5 with push transactional replication.
We had massive transactions in oracle and encounter spacing error
ORA-01652: unable to extend temp segment by 12137 in tablespace SYSTEM
Batch processing is in progress. The current batch consists of 17356 commands and 0 transactions. The last transaction was 0x000000000000000070f5, '0x000000000000000070f5'.
And I found many locking in replication process in oracle side and I stopped the replication is mssql2005 but no much help until kill session in oracle.
After massive rollback jobs in oracle and seems return normal in oracle publisher. I tried to re-initial the sychronization with a new snapshot.
After the snapshot created, the monitor stated that 'the initial snapshot for publication 'JHBHK-batch' is not yet available.'
The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.
Any idea Thanks in advance!
Sychronization error - MSSQL_REPL22037
StLuisRey
1. Please make sure that you don't use system tablespace as the default tablespace - this is the main cause of the issue you first encountered with snapshot error with extending TEMP tablespace. Suggested practice is to use seperate default user and temp tablespace for replication user schema on Oracle. Also, make sure you have ample space for rollback & temp tablespace.
2. After reinitializing the subscription - did you run the snapshot agent to generate a valid snapshot If yes, then make sure that no error was encountered by snapshot agent and the snapshot files (includes the data & script files) were generated in snapshot folder. After the snapshot agent completes, log reader needs to complete the reconcillation process before the distribution agent can apply the snapshot to subscriber. The message given by the agent is just a warning - sometimes agent takes long time if there is a huge snapshot to be applied.
3. If you are still having issue - these informatiion will certainly help :
- Version of Oracle server ; Version of oracle client installed on SQL server distributor
- Size & number of oracle tables used in replication, any non-default selection within or outside UI wizard
thanks!
BillGates4ever