Frozen DSI to the secondary db

Frozen DSI to the secondary db

Post by David BAFFALE » Sat, 11 May 2002 23:51:24



Hi everybody,

I have a problem with replication server.
The stable queue is about to be full and the DSI
which must replicate the transactions to the secondary
dataserver is in awaiting command status. (not down but awaiting)

When I do a `admin who,sqt`, here's the output:

   15 Awaiting Wakeup      102:1  DIST L_GII_P1_ASE.l_Venus          
       0
                   0           1           1           1           0
                   1 st:O,cmds:16994,qid:4706:30:0             0      
    0

...

  21 Awaiting Command     104 VMA_P1_ASE.GII_ES                      
      0
                   0           1           1           1           1
                   0 st:O,cmds:17522,qid:2863:8:3              0      
    1
                    1              0

The spid 15 is the DSI from the primary, inserting 16994 commands into
the queue. The spid 21 is the DSI which is in awaiting command, is
waiting to replicate 17522 commands to the secondary. But it never
does. And the stable queue is filled on and on and never emptied. Have
you any idea ? I'd rather not dump and purge the queue, but if I have
no other solution to this issue...

Thanks,

David.

 
 
 

Frozen DSI to the secondary db

Post by David BAFFALE » Sun, 12 May 2002 00:01:16


Hi everybody,

I have a problem with replication server.
The stable queue is about to be full and the DSI
which must replicate the transactions to the secondary
dataserver is in awaiting command status. (not down but awaiting)

When I do a `admin who,sqt`, here's the output:

   15 Awaiting Wakeup      102:1  DIST L_GII_P1_ASE.l_Venus          
       0
                   0           1           1           1           0
                   1 st:O,cmds:16994,qid:4706:30:0             0      
    0

...

  21 Awaiting Command     104 VMA_P1_ASE.GII_ES                      
      0
                   0           1           1           1           1
                   0 st:O,cmds:17522,qid:2863:8:3              0      
    1
                    1              0

The spid 15 is the DSI from the primary, inserting 16994 commands into
the queue. The spid 21 is the DSI which is in awaiting command, is
waiting to replicate 17522 commands to the secondary. But it never
does. And the stable queue is filled on and on and never emptied. Have
you any idea ? I'd rather not dump and purge the queue, but if I have
no other solution to this issue...

Thanks,

David.

 
 
 

Frozen DSI to the secondary db

Post by Bechev » Sun, 12 May 2002 00:13:55


Sounds like you may have an open transaction at the primary.  Without a commit
the DSI thread will not process the outstanding transaction.
 
 
 

1. Log shipping secondary DB status "(Loading)"

After setting up log shipping (thanks Linda!) when I
expand the list of databases on the secondary server in
Enterprise Manager, the secondary database in the log
shipping pair shows a status of "(Loading)".  According to
the system logs, the logs are being copied and restored on
schedule, but I can't query the secondary database.  When
I initially restored it, I chose the "Read only, capable
of restoring transaction logs" option.  Prior to the first
log shipping restore, I was able to view the tables, etc.  
Any ideas how to make the database available?

2. * Infinite loop

3. Copying .db and associated secondary index files

4. refusing connections based on load ...

5. Log View 1.3 from DSI

6. inserting columns with values from a different table

7. RepServer problem: DSI thread can't exec rs_get_lastcommit

8. What is SwiftLink ?

9. Error #1028 Dsi Exec

10. DB connection freezes application

11. neeed help, client freezes when opening remote db folder

12. DB completely frozen during restore