Thursday, April 6, 2017

Why DIP or DIPPATCH did not complete or hung?


Problem

Why DIP or DIPPATCH did not complete or hung?


Environment/Conditions/Configuration

TDBMS 14.10.07.03


Cause

Blocking / leftover HUT locks


Solution

Clear leftover HUT locks:
               1) Logon to database as DBC
               2) release lock DATABASE_ABC, override;


Additional Information

How to check for locks:

## From lokdips utility
smp0018#
cnsterm 6
Input Supervisor Command:
> start lokdisp
Please enter your selection from the list:
> blocker
Which amp(s) do you want to request on (S=Sampling/A=all/C=cancel/Q=quit):
> all
AMP
182 REPORTS 1 LOCK ENTRIES Number
of Blocked Trans displayed : 1
=========================================
Blocked Trans : 30709 0011AB40
Number of blockers displays : 1
Number of blockers exists : 1
Blocker Trans : 7800 00000001
lock mode : Exclusive
lock status : Granted
lock objectType : Database
lock objectID : DBID : 000003ED
: DBNAME : SYSADMIN
: TableID : 00000000,0000
: TableName : ALL
: RowHashS : 00000000
: RowHashE : 00000000

END OF OUTPUT >
##Showlocks
smp0018#
cnsterm 6
Input Supervisor Command:
> start showlocks
smp0018#
cnsterm 1 (<From
Started
'showlocks' in window 1)

DATABASE_ABC
USER DBC MODE Excl AMP All Amps

DATABASE_DEF
USER DBC MODE Excl AMP All Amps

DATABASE_XYZ
USER DBC MODE Excl AMP All Amps


ShowLocks Processing Complete

Note: Showlocks utility will only show a limit of 6 HUT locks database per screen. If you see 6 locking databases on the screen then note likely there are more. Perform the release lock command and run another showlocks and continue the steps until there are no more locks.

1 comment:

  1. After reading this blog i very strong in this topics and this blog really helpful to allBig Data Hadoop Online Course

    ReplyDelete