IOP Synchronisation Failure - Cause & Remedies IOP synhcronisation in C-DOT may fail due to various reasons. There are 6 steps of IOP synchronisation. Various files updated in OOS-IOP from INS-ACT IOP are lying in PRCDATAP directory by the name of sync_grpx (where x takes values from 0 to 5) Each sync group file contains, different type of data files to be 'updated in OOS-IOP to bring it in sync with the INS-ACT IOP. It may happen that certain file is not getting updated within prescribed time limit and as a result sync process will be aborted in that particular step to which the file belongs. During sync, various steps of "Sync over" messages will be displayed on console terminal, ood-terminal & printer also. Most likely, the exact file name will be flashed on console terminal just before "Sync-Abort' message. Then some action is required regarding that particular file before repeating the sync procedure again. In case no file is shown on console before 'sync_Abort' message, still particulars of failure can be seen through 'sync_log' file in $DUMPP directory, using following commands in ACT-IOP:- IOP5x> cd $DUMPP IOP5x> tail -50 sync-log from this note down the name of file, just before the "sync-abort" message and take appropriate action as stated in the subsequent paras 1 to 7. GENERAL PRECAUTION Before synchronisation, do delete unwanted files (after taking desired Back-ups) as per standard procedure for Diskcleaning e.g. ioh, trnsf, bc, tf groups giving appropriate date options in bc & tf. Also run utility 'cre-space' in both the IOP's. As far as possible synchronise the IOP's during slack hours. - 36 - 1. ♦ Shutdown/reboot both the IOP's and give frc-swu-ins from acting IOP. ♦ After giving 'put-swu-ins' begins" does not appear on console terminal and process creation does not start on OOS-IOP, then, most likely HDL (VHC or VDE) card of one of the IOP is faulty. Try by replacing VHC/VDE card first in OOS IOP and then in Active IOP. ♦ Process creation has started on OOS-IOP (4 lines) but 'synchronisation of IOP begins" message does not appear on ACT-IOP console, then verify s/w loaded in the IOPs. These may be different. 2. "Synchronisation of IOP begins" has appeared but sync is getting aborted in step 0 itself (i.e. "sync over for step 0" is not coming). Do following: ♦ Run utility cre-space in Active IOP. ♦ If 'cre-space' is not available, then give commands : IOP5x > cd $TEMP IOP5x> mv oodlogDD noodlogDD where 'DD' stands for current date IOP5x> rm oodlog* result* IOP5x> mv noodlogDD oodlogDD ♦ Shutdown and Reboot ACTIVE IOP (using init_iop:2,1; & init-iop:1,1; 5,1), ♦ start synchronisation again (put-swu-oos/ 3. 'Sync-Abort' in step 1 (CURRENT DAY DUMPS) Note down the file name in sync_log file in $DUMPP directory. If it is a traffic file then delete 'tf' grp for current date and synchronise again. However if 'file' is other than traffic related, then contact C-DOT Control Room for further action. Files are: ncbr, tgcbr, tgcntr, locctr*, stdctr* of current date. - 37 - 4. Sync-Abort in step 2 (Subs Initiated Feature Related Files) Repeat sync in late night hours, when no traffic is there. Before synchronization, bring Active IOP to Cold Start (using INIT-IOP:2,1; and INIT-IOP:1,1; 5. Sync-Abort in step 3 (Complete Exchange Data Files) In this step all Ed files are transferred. Note down the file name and consult CDOT Control Room for further action, as 'ed' files are difficult to handle. In some cases, 'copy-in' old Ed in the active IOP in warm start level and then make it active again. Then give "part-init" and start sync. process again. 6. Sync-Abort in step 4 (Maintenance Initialisated Process Data Files) IOP5x> find /u -name *.log - print Note down the directory and *.log file names. Then go to the particular directory and remove log files by giving full names. IOP5x>rm abc.log etc. [where abc.log is the file name] IOP5x>cd $TEMP IOP5x>rm result* IOP5x>cd $FDTDIR IOP5x>rm heal* Now give 'softstart' to the system, using <init-sys command, in crp mode. i.e. <init-sys :, Soft-Start; After System has recovered fully, repeat the synchronisation procedure. - 38 - 7. Sync-Abort in step 5 (PAST DAY DUMPS) This is the most probable step of sync failure. In this step, all "Detail Bill Files", "traffic files" and all "oodlogxx" files are transferred. Normally, by deleting previous 'tf' and 'bc' files will solve the problem. Otherwise, note down exact file name in 'sync_log' file in $DUMPP directory. Then delete that file using <delfgp- file command. Remove all 'oodlog' files in $TEMP directory, as mentioned in para 2. Then repeat the synchronisation process. Following files for past days (Not current day file) are transferred: All 'tf' gp files, ncbr files, tgcbr; tcntr,.
With Regards:- G S Rajawat Bharat Sanchar Nigam Limited (A Govt. Of India Enterprise) Cell: +91-9413424883 --- On Mon, 7/9/09, ramesh kannan <rameshkannan79@
|
Love Cricket? Check out live scores, photos, video highlights and more. Click here.
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch format to Traditional
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
No comments:
Post a Comment