Preparation of Data for CBS.pdf

Viewer
Transcript

Updated on : 17/04/2014 1233 hrs DATA MIGRATION COMMAND CENTRE, Chennai 600 002 [email protected]

Preparatory checklist for CBS (I)

Pre Requisites 1. A node with Windows 7 along with SQL2005/ SQL 2008 to be kept ready for uploading data through SFTP server. Latest Antivirus software has to be installed in this node. This node will be used as backup server. 2. Download Filezilla software from the below said link and the install the same in this node. https://drive.google.com/file/d/0B25bTWT2-kXgaU1qcW56VElyM1E 3. Restore post , sign ,sosb, bpro, blog in the backup server (i.e Node mentioned in Slno.1) Check whether the sanchay post software is working with this Sql server connectivity in this node only (Caution : No change is required in the original server in respect of SQL version and the regular server will continue to serve the Sanchaypost network)

(II)

Pre requisites – Data cleansing

1. Scheme-wise, account-wise balance agreement has to be completed and consolidated balances certified by the postmaster & the Divisional head. 2. 100% manual records have to be digitized using Sanchaypost Ver 7.5 and Manual Data Entry tool published in SDC portal. 3. 4 Years history data of NSS-87 should be completed using the Manual Data Entry Tool said in item(2) 4. Manual data relating to KVP, NSC 8 and NSC 9 should be updated in Sanchaypost 7.5 5. On the date of actual migration this manual data should have the updated entries deleting the details of KVP/NSCs discharged and accounts closed. 6. Many post offices are in the habit of discharging the certificates by selecting the option “Issued at other office / Manual” even though these certificates were issued in the same office. 7. This discrepancy could be viewed using, DB Analyzer--> Reports—live account. Post offices are instructed to ensure that the live accounts list so generated should match with the office records. The certificates already discharged are to be cleared using online discharge option.

(III)

Steps to be followed for Go Live (Points 1 to 8 to be performed in the Live Server)

1. Download the Latest DB Analyzer including (DBA+ Tool dt. 14-04-2014) through the link below and execute the same. https://drive.google.com/folderview?id=0B25bTWT2-kXgUmtISzgwdURmUUk 2. Each and every option in Database Discrepancies, CBS Additional Discrepancies and CBS Discrepancies (II) for all schemes in DB Analyzer have to be checked and discrepancies cleared. 3. All agents (ie. MBKBY ,PRSS & SAS Agents) should be linked with PO Savings Account Number and PanNumber. Provision available in the latest DB Analyser – Miscellaneous option to check the Agents linked / Not linked with Saving Accounts. 4. It is also requested to ensure that all the accounts closed under Claim closure status are marked as ‘CLOSED’ in Ledger/Index tables, as the accounts having remarks as ‘Claim closure’ will be migrated as Live accounts in FINACLE. 5. During the Go-live migration, it is requested to change the BO details. Please verify the BO details today if applicable and take necessary corrective actions before Go-live. It is very difficult to accommodate due to stringent timelines. 6. Take backup of Post Database. If any problem faced in the coming process you have to restore the post database. If you fail to take backup dmcc will be not provide any solution thereafter. 7. Download the Premigrationtool _2_31 dt.16-04-2014 and execute the tool from the below said link https://drive.google.com/folderview?id=0B25bTWT2-kXgTWtPQXM5ejVESUk Check for sample data whether it has not effected correct data like name,address.etc. If any there is any major change in correct data restore the database and contact DMCC, Chennai for solution. 8. Execute DPT Tool 2.9 and DB Analyzer consolidation report and ensure that zero discrepancy exists. DPT Tool 2.9 Link : https://drive.google.com/folderview?id=0B25bTWT2-kXgeC01NTFGVF9hSW8 9. Download the SP-Link Aadhaar Number.exe from the below said link and execute the same to create UIDAI related tables. https://drive.google.com/file/d/0B25bTWT2-kXgdnFQdmxDTUtYekU

10. Ensure Agt_act and UIDAI table exists in the Post database.(this will get created when we use option to link adhaar and linking agent with SB account number 11. Check the Database consistency using DB Analyser for Post and Sign database and ensure that there is no error in the database. If error is reported kindly send email to [email protected] for solution. This is a very important step as it is related to data integrity of post and sign.