Suppose you cannot see BCOL.1.1 when you execute dccmd status all. Below, some things to investigate:
1) Try to run it manually. Run:
dccmd start BCOL.1.1
2) Check the proviso.log. Run:
grep "BCOL\.1\.1" proviso.log and search for any error message
3) If you see a WALKBACK error on the log, search for the walkback file and read the first lines to see the main reason for the walkback
4) Check if the component configuration exists in the database. Run:
dccmd debug CMGR "self dbCfgPrint" | grep BCOL.1.1
This should show the component configuration in the database. Check for any mistakes and correct it using the topologyEditor
If you don't see any value, the component was not created on the topologyEditor or was not saved correctly in the database.
5) Check if any filesystem is full. Run:
df -kh and make sure no partition has 100% utilization
6) Restart some datachannel manager components (cmgr, amgr, cns) and try again.
If you still cannot find the reason, it is a good moment to open a ticket towards IBM
Hi Danillo,
ReplyDeleteThis implemntation is done recently. Have started polling on 15th March, 2018 9:00PM. However, i am not sure why DLDR is showing "Waiting for poll interval" since then ??? Also i could see Daily aggregated reports which is being generated by the LDR. I am not sure what functionality will be missing because of no files getting processed by DLDR ?
[pvuser@APPRODPROV2 bin]$ dccmd status all
COMPONENT APPLICATION HOST STATUS ES DURATION EXTENDED STATUS
CME.1.1 CME APPRODPROV2 running 13 Waiting for data after 2018.03.17-03.15.00
DISC.APPRODT DISC APPRODTNPM1 running 2458 running
DLDR.1 DLDR APPRODPROV2 running 1 Waiting for poll interval
FTE.1.1 FTE APPRODPROV2 running 1 [1] Waiting 60 seconds for data after 2018.03.17-03.15.00
LDR.1 LDR APPRODPROV2 running 1 Waiting for poll interval (2018.03.17-02.00.00)
PBL PBL APPRODPROV2 running 27 Waiting for collector advancement
Hi Vikas,
ReplyDeleteThe DLDR is responsible for moving the tablespaces around in the database. It usually runs once per day. In TNPM you have some "data windows" defined which are materiallized using Oracle partitioning. The DLDR move this data around following the TNPM partitioning scheme. Considering you have just started collecting data, you probably did not reach the threshold to activate this feature (usually 3 days)