Postal Life Insurance (PLI) – Overview

INTRODUCTION

Postal Life Insurance was started in 1884 as a welfare measure for the employees of Posts & Telegraphs Department under Government of India. Due to popularity of its schemes, various departments of Central and State Governments were extended its benefits. Now Postal Life Insurance is open for employees of all Central and State Government Departments, Nationalized Banks, Public Sector Undertakings, Financial Institutions, Local Bodies like Municipalities and Zila Parisads, Educational Institutions aided by the Government etc.

WHY CHOOSE PLI ?

“ High Bonus Low Premium ”

PLI offers bonus rates higher than all types of policies as compared to that of other insurance agencies.

SALIENT FEATURES

Salient Features of Postal Life Insurance:

Pass book Facility:

Premium can be remitted in any departmental Post Offices in India.

Recovery of premium from Pay:-Facility of recovery of premium from salary is available to some selected Departments.

Loan Facility:

Loan can be obtained at the interest charge of 10% p .a Loan can be obtained from other financial institutions like nationalised bank, HDFC etc on the security of Policies.

Assurance upto 10 Lakhs:

PLI offers policies up to a maximum Sum Assured of Rs.10 lakh for Whole life and Endowment Assurance Policies.

Income Tax Savings:

PLI Premium paid is eligible for Income Tax Savings under section 80C of Income Tax Act.

Non Medical Scheme.

Scheme of Non Medical policies of Endowment Assurance available up to One Lakh Sum Assured ,subject to conditions.

BENEFITS

 Benefits of Postal Life Insurance.

1. 100% security by Government of India
2. Income Tax Rebate under Sec. 88.
3. Low Premium.
4. High Bonus.
5. Options for Loan, Assignment, Surrender, Conversion and Paid Up Value.
6. Repayment of Loan is optional.  However interest is payable every 6 months.
7. Easy transfer to any place in India free of cost.
8. Pass book facility for payment of premia & other payments like loan, interest through any Departmental Post Office.
9. Pay recovery facility for Institutions and Organizations having more than 20 policies.
10. Facility for payment of premia monthly, half yearly and annually on any working day of the month for which it is due.
11. Rebate @ 1% for payment of 6 months premia in advance.
12. Rebate @ 2% for payment of 12 months premia in advance.
13. Nomination facility.
14. Facility for revival of policies lapsed due to non-payment of premium.
15. Payment of policy money through any Post Office, anywhere in India.
16. Centralized accounting for quick and easy settlement of claims through fully computerized office management.

Download Forms for PLI / RPLI

SL NO	NAME	DOWNLOAD
1	Change of Nomination	Download
2	Notice of change of Nomination	Download
3	Loan Assignment	Download
4	Maturity Value of Endowment Assurance	Download
5	PLI Loan	Download
6	Revival of PLI Policy	Download
7	RPLI Surrender	Download
8	RPLI Maturity Value Claim	Download
9	Declaration of Policies above 5 Lakhs	Download
10	PLI / RPLI Credit Certificate	Download
11	Death Claim	Download

JOIN PLI

Take a wise decision now. Earn this year bonus.

7000 per one lakhs for endowment and 9000 per one lakh for Whole Life.

NEED HELP ?

Contact your nearest post office to get more details about Postal Life Insurance.

Web: http://www.indiapost.gov.in/netscape/pli.html

Phone: 91-11-24674794 , 24671317

Ask your queries in the comments section of this blog post.

Source : Central Government Employees News | IMyIdeas

Author: Najiya M Ali

Postal Assistant, Department of Posts.

Postal Life Insurance (PLI)

 

Eligibility : Employers of central and state Government, Defence Services, Extra Department & work charged employees of Department of Post & Department of Telecom, Govt. Aided educational institutions, Universities, Nationalised Banks, Public sector Undertakings of central /state Government, Local Bodies like Municipalities, Zilla Parishads etc. Financial Institutions like IDBI, IFCI, IRCI, UTI, etc. Regional Rural Banks, Departmental canteens. The Policy can be continued by paying premium in cash in post office after quitting the service Type of Policies :        1) 'Suraksha' (Whole Life Assurance)        2) 'Santosh' (Endowment Assurance)        3) 'Suvidha' (Covertible Whole Life Insurance)        4) 'Sumangal' ( Anticipated Endowment Assurance)        5) 'Yugal Suraksha' ( Joint Endowment)        6) 'Children's Policy' Age : Should be between 19 years and 55 years. For 'Sumangal' 15 / 20 year plan, maximum age is 45/40 years respectively & for Yugal Suraksha age at entry of both the spouses should be between 21 to 45 years and age at maturity of older spouse should not be more than 60 years on the next birth day . Low Premium: Premium rates of P.L.I are lower as compared to those of insurance schemes of any other agencies High Bonus : Bonus rates are higher as compared to those of insurance schemes of any other agencies. BONUS RATES (2005-06) (per thousand sum assured per year) Suraksha (Whole Life Assurance)                              Rs. 90/- Santosh (Endowment Assurance)                              Rs. 70/- Sumangal (Anticipated Endowment Assurance)     Rs. 65/- Chilren's Policy (Endowment Assurance)                 Rs. 70/- Income Tax Rebate : PLI premium paid is eligible for income tax rebate under section 80-C of Income Tax Act Risk Cover : Risk is covered on the policy from the date of acceptance of the proposal Advance Deposit 1st Premium : The Development/Field officers of PLI are authorised to collect from proponents advance deposit of amount equivalent to 1st premiums on their proposals and issue receipt thereof. Paid up policies also earn bonus Recovery of premium from pay: Facility of recovery premium from salary is available under the group leader scheme . Maximum Limit of Assurance : PLI offers policies up to a maximum sum assured of Rs. 10 lakhs. Physically handicapped persons are also eligible to take PLI policies up to a face value of Rs. 1,00,000/- under special scheme, subject to certain conditions. Conversion : Whole life policy can be converted into Endowment Assurance Policy. Revival : Revival of policies lapsed due to non payment of premium is allowed on production of good health certificate and payment of arrears premium with interest at 12 % per annum subject to certain conditions under Rule 39/40 of POIF Rules. Loans : Loans can be obtained against the security of PLI policy which have been in force for atleast 3 years/ 4years in case of Santosh/Suraksha respectively. Surrender :    a) Suraksha , Santosh & Suvidha policies which have been in force for atleast 3 years can be surrendered for immediate cash payment. Surrender of policy is not admissible before completition of 36 months of the policy and the amount deposited shall be forfeited.                    b) On surrender, the policy shall attract proportionate bonus on reduced sum assured upto the date for which premium has been paid. However, no bonus shall be payable before completion of 5 years of the policy.                    c) The discontinued policy shall not attact bonus with effect from date from which the premium is discontinued.                    d) The reduction sum assured shall be calculated by multiplying the sum assured with number of installments paid and dividing the same with total number of premiums to be paid.                    e) The surrender value shall be calculated by multiplying the sum of reduced sum assured plus the proportionate bonus if any with surrender factor as applicable on the attained age as on the date of surrender of the policy. After Sales Service : The Policy details of all the insurants have been computerised and this enables us in giving an excellent after sales service to the insurants. Nomination/Assignment : Facility of nomination and assignment is available. Non-medical Policies : Scheme of non-medical policies is available up to Rs. 1 lakh sum assured only (age limit 35 years) under certain conditions.           Reduction :    A policy holder may apply for reduction of his monthly premium and sum  assured without altering the class of his policy. Lapsation of Policy : Policy has been in force for not less then 3 years and premium has not been paid twelve consecutive month and if the policy has been in force for less than 3 years and premium has not been paid for six consecutive months the policy becomes void/lapsed which should be got revived from the Chief DMG (PLI) Rebate @ 2 % is allowed if annual premium is paid in advance and @ 1 % is allowed if six monthly premium is paid in advance. The 'SUMANGAL' policy offers the following attractive benefits 15 years Term 20 years Term 1.  At the end of 6 years, 20 % of the sum       assured is payable At the end of 8 years, 20 % of sum assured is payable 2. At the end of 9 years, 20 % of the sum       assured is payable At the end of 12 years, 20 % of sum assured is payable 3. At the end of 12 years, 20 % of the sum      assured is payable At the end of 16 years, 20 % of the sum assured is payable 4. At the end of 15 years , 40 % pf the sum      assured is payable together with bonus      accrued At the end of 20 years, 40 % of sum assured is payable together with bonus accured Yugal Suraksha Object : Newly introduced Joint Life Endowment Assurance Plan provides insurance coverage to both the spouses. However only one can subscribe the policy. Spouse need not be an employee. Term : Not Les than 5 years & not more than 20 years. Risk cover : Risk on both the lives is covered from the date of acceptance of the proposal. Premium : The premium based on equivalent age at next birthday is calculated by addition to the lower age depending upon difference in age of spouses. Table "A" for addition in lower age and Table "b" shows premium for equivalent age (Next Birthday).  A rebate of 2 %, 10 % or 50% of the premium for ONE MONTH is allowed, if premium is paid in advance for 3, 6 or 12 months respectively. The premium will be payable either up to the date of last premium fixed before maturity or up to the death of one of the spouses, whichever is earlier. Claims : The sum assured along with accured bonus of the policies in full force will be payable to - a) the insurant at the end of endowment term i.e. date of maturity if both the lives survived.                                                                or , b) the survivor on death of one of the spouses before the date of maturity. The survivor is absolved from payment of further premium                                                               or,c) the nominee/Legal heirs on death of both the insured lives simultaneously. Both the spouses should be healthy, confirmed A-I lives by the appropriate medical examiner and should be literate.

Children's Policy-2006           Children's Policy is newly introduced w.e.f. 20-01-2006 and applicable to both PLI/RPLI.  Object : To provide insurance cover to the two children of each policy holder provided that only one such policy will be allowed for an insured against one policy.    Eligibility :      a) This is an independent policy, however this policy can not be issued of its own to any child. If the father/mother (insured) of the child has already taken policy or is proposing to take policy on their life either as whole life or endowmentAssurance for a sum assured not less than the sum assured of children policy then children policy shall be issued to such insured.                    b) Not more than one policy will be allowed for one child. The policy can be taken by insured for his/her own child only.                    c) Not more two children in a family shall be covered under this policy. Thesame child should not be covered under more than one policy. Age Limit :  a) The insured main policy shall not be aged 45 years and above at the time of taking/issue of children policy. Limit of insurance : The minimum limit for insurance under this scheme shall be Rs. 20,000/-. The maximum limit of sum assured should be more than 1,00,000/-   Medical Examination : The policy shall be a non medical policy for a maximum sum assured of Rs. 1,00,000/- per child.  Risk Cover : Risk is covered from the date of acceptance of the proposal.  Loan : No loan is admissible to children policy.   Surrender : Surrendered and made paid up on usual conditions as applicable to main policy provided at least 5 years premiums have been paid. Amount is admissible as per surrender Table/Factor which would be a fraction of premium paid. Term : The out standing term of main policy shall not be less than the premium paying period of children policy. Claim :      a) Sum assured shall be payable on children policy on its Maturity or earlier on death of the child.                b) In the event of death of the insured before the expiry of the children policy, no further premium shall be payable for the balance period of the policy. Any additional information can be obtained from Circle, Divisional office or Development, field officers and PLI Agents.  Source : http://maharashtrapost.gov.in/

ISSUE OF SAs IN JCM SUBJECTS

Click Here




Dear Comrades,

                After the massive attempt made in our Delhi Seminar in getting an exact focus on the what is required for the SAs as democratically decided by SAs has to been submitted in a crystal clear manner  to the NFPE Leadership. In the clarity got from the Delhi Seminar the NFPE leadership has now placed the demand of SAs in the JCM (Standing Committee).

              Those who speak about forming any association should understand what is JCM. The Joint Consultative Missionary (JCM) is the ultimate forum of negotiation between the Government and Staff-side. Staff-side will comprise of Union representatives from the recognised Federation (NFPE & FNPO). The number of representatives of JCM (Staff-side) will be determined based on the strength of the membership in each of the Federations. Hence NFPE being the largest Federation of the Postal employees having more than 70% of the membership will have more number of representatives in the JCM on the other hand FNPO having more or less 30% of the membership will have few representatives accordingly. Hence the bargaining capacity will be more for the Federation having more representatives.

          Hence any individuals having formed any association will not have any legal representation in the JCM which is official negotiating body of Staff issues. Hence in this context the issue of System Administrator as decided by us democractically in the Delhi Seminar is now included in the JCM Subjects submitted. The details of the Subjects submitted to our Department is avaialble in the following link: 

http://www.scribd.com/doc/25981567/JCM-Departmental-Council-Subjects-Final

             Now the date of meeting of JCM Standing Committee will shortly intimated shortly. The meeting in proposed to be held in the month of March. Hence in order get a concrete committment or nod from our DOP placing it as a JCM Subject is very essential. When department has given a nod recordically in JCM almost 60% of the job is over. Then the formal approval from MOF and then finally DOPT has to follow through.

INSPECTOR OF POST - MOVEMENT IN TAMILNADU CIRCLE

Western Region

01. shri.c.kamalesh, ip, tech, ro, coimbatore to be ip, legal cell, ro, coimbatore.
02. shri.r.venkat ragavan, ip, ooty sub dn to be ip, tech, ro, coimbatore.
New IP posting orders.
03. smt.radha to be ip, bd, ro, coimbatore.
04. smt.jayageetha to be ip, dharapuram sub dn, tirupur dn.
05. shri.rajasundaram to be ip, ooty sub dn, nilgiri dn.
06. shri.selvam to be ip, gudalur sub dn, nilgiri dn.
07. ms.bharathi to be ip, atur salem sub dn.
08. ms.hemavathi to be krishnagiri east sub dn, dharamapuri dn.
09. ms.kanimozhi to be rasipuram sub dn, namakkal dn.


Southern Region


01. Shri.Saravanan, IP, MA 4 Sub Dn, Madurai to be OS, RMS MA Dn.
02. Shri.S.Subramanian, IP, Sivaganga to be IP, Karaikudi.
03. Ms.Meenakshi to be IP, Vallioor.
04. Ms.M.Jothilakshmi to be IP, Vedasandur.
05. Ms.Annalakshmi to be IP, Nagercoil West.
06. Ms.M.Uma to be IP, Sivaganga.
07. Shri.P.Selvam to be IP, Gudalur in WR.


CCR  Region


01. Shri.GUnasekar to be IP, Cuddalore to be IP, Vandavasi.
02. Ms.L.Srividya, IP, Pattukottai East to be IP, Sriperumbadur.
03. Ms.Indra, IP, Kallakurichi to be IP, Vellore West.
04. Shri.T.Vivekananda, IP, Gingee.
05. Ms.G.S.Sujatha to be IP, Tiruttani East.
06. Ms.Pratheeba to be IP, Polur.


Central Region
01. Ms.Kalaivani to be IP, Kumbakonam South.
02. Shri.Prabu Sankar to be IP, Thirukoilur.
03. Ms.Sharmila to be IP, Pudukottai South.
04. Shri.Arunachalam to be IP, Alangudi.
05. Shri.Hussain Ahmed to be IP, Orathanad.
06. Shri.Ravishankar to be IP, Pattukottai East.
07. Shri.Thanikachalam to be IP, Cuddalore.


 CONGRATULATIONS TO ALL IPs.

SQL Mirroring Using Batch Files

By : R.SENTHIL KUMAR, SYSTEM ADMINISTRATOR, CHENNAI CITY NORTH DIVISION

MOBILE 9884373390

---

I HOPE OUR SYSTEM ADMINISTRATORS WILL HAVE THE PATIENCE TO READ THE FOLLOWING AND ALSO SUGGEST ANY OTHER BETTER METHODS WHICH THEY ARE ADOPTING AT THEIR RESPECTIVE WORK PLACE

In today's scenario of our department after three to four years of implementation of Total Computerisation we encountering frequent server breakdowns. The AMC service providers also do not attend the Server breakdowns in time which results in total stoppage of office functioning till the Server is set right. Even after the Server is set right we still rely on the automatic "Database maintenance plan" which we configure in SQL Server. But how many of us have consiously made an effort to frequently restore the backup files created vide the Maintenance plans.
In this context recently I have been trying to configure a SQL server mirroring with the existing provision available in SQL server which is called "Replication". Unfortunately though it is an built-in utility available in SQL Server I tried it but its not effective enough because if you configure replication SQL databases from one server to another Server it slows down the entire process on the both the Server which is not desirable.
Hence recently I had glimpse reading about the "OSQL Utility". In OSQL Utility you can display the results of any SQL Query in the command prompt. Just simply try typing the following command in DOS prompt.
osql ?

The above command will show the osql switches that can be used. With this as the baseline I tried to develop a batch program which runs on a client machine automatically when the user logs in. Immediatly when the user logs this batch program will fire in the startup. The prerequisites for running is batch program and the procedure of how to configure a backup server is given below:

1. Configure another client machine and load Windows Server 2003 / 2008 OS. While doing "dcpromo" select the option "Additional Domain Controller for an existing Domain" and give the administrator password and Domain name of the Main Server. At the end of the dcpromo wizard you restart the please check in "Active Directly User and Computers" that the same Domain Users of the Main Server is shown in this also.

2. If you are having all the database files (i.e mdf,ldf and dat files) in a drive other than "C" drive please ensure that the same drive is available in the client machine. Because while restoring the database from a backup file it will be restored in the same drive only. Let us say for example you have all your database files in D drive in the Main Server. In that case create a D drive partion in the client machine also with enough disk space.

3. Create a folder named "backup" in E drive of you Main Server(or any other drive as you wish) share the folder with permissions as "Full control".

4. Install SQL Server 2000 / 2005 in the newly configured client machine (i.e your additional domain controller).

5. Create a folder name "restore" in the newly configured client machine in the D drive.

6. Open SQL query analyser in the newly configured client machine and type the following coding given below and save it with a file name "bkpquery1.sql" in D drive.

BACKUP DATABASE BPRO TO DISK='E:\BACKUP\BPRO.BAK'
BACKUP DATABASE BPLOG TO DISK='E:\BACKUP\BPLOG.BAK'
BACKUP DATABASE COUNTER TO DISK='E:\BACKUP\COUNTER.BAK'
BACKUP DATABASE ECOUNTER TO DISK='E:\BACKUP\ECOUNTER.BAK'
BACKUP DATABASE EMO TO DISK='E:\BACKUP\EMO.BAK'
BACKUP DATABASE EIOD TO DISK='E:\BACKUP\EIOD.BAK'
BACKUP DATABASE IPO TO DISK='E:\BACKUP\IPO.BAK'
BACKUP DATABASE PATCH TO DISK='E:\BACKUP\PATCH.BAK'
BACKUP DATABASE POSPCC TO DISK='E:\BACKUP\POSPCC.BAK'
BACKUP DATABASE POSPCCBACKUP TO DISK='E:\BACKUP\POSPCCBACKUP.BAK'
BACKUP DATABASE POST TO DISK='E:\BACKUP\POST.BAK'
BACKUP DATABASE POSTMAN TO DISK='E:\BACKUP\POSTMAN.BAK'
BACKUP DATABASE PROJECT TO DISK='E:\BACKUP\PROJECT.BAK'
BACKUP DATABASE ROUTING TO DISK='E:\BACKUP\ROUTING.BAK'
BACKUP DATABASE SIGN TO DISK='E:\BACKUP\SIGN.BAK'
BACKUP DATABASE SOSB TO DISK='E:\BACKUP\SOSB.BAK'
BACKUP DATABASE SUBTREASURY TO DISK='E:\BACKUP\SUBTREASURY.BAK'
BACKUP DATABASE TREASURY TO DISK='E:\BACKUP\TREASURY.BAK'

(The above code when executed from the client machine after connecting to the SQL Server instance of Main Server will backup all you databases in the path E:\Backup of the Main Server.)
(Note: in the above coding I have just included the databases of a Sub-Offices only if you are working in an head office incorporate the databases like Accounts, Schedules, CashBook and all other Sanchay Post Sub Office databases)


7. In the same way open SQL Query Analyser in the newly configured client machine and type the following code and save it with the name "restorequery1.sql" in the path "d:\restore".

RESTORE DATABASE BPRO FROM DISK='D:\RESTORE\BPRO.BAK'
RESTORE DATABASE BPLOG FROM DISK='D:\RESTORE\BPLOG.BAK'
RESTORE DATABASE COUNTER FROM DISK='D:\RESTORE\COUNTER.BAK'
RESTORE DATABASE ECOUNTER FROM DISK='D:\RESTORE\ECOUNTER.BAK'
RESTORE DATABASE EMO FROM DISK='D:\RESTORE\EMO.BAK'
RESTORE DATABASE EIOD FROM DISK='D:\RESTORE\EIOD.BAK'
RESTORE DATABASE IPO FROM DISK='D:\RESTORE\IPO.BAK'
RESTORE DATABASE PATCH FROM DISK='D:\RESTORE\PATCH.BAK'
RESTORE DATABASE POSPCC FROM DISK='D:\RESTORE\POSPCC.BAK'
RESTORE DATABASE POSPCCRESTORE FROM DISK='D:\RESTORE\POSPCCRESTORE.BAK'
RESTORE DATABASE POST FROM DISK='D:\RESTORE\POST.BAK'
RESTORE DATABASE POSTMAN FROM DISK='D:\RESTORE\POSTMAN.BAK'
RESTORE DATABASE PROJECT FROM DISK='D:\RESTORE\PROJECT.BAK'
RESTORE DATABASE ROUTING FROM DISK='D:\RESTORE\ROUTING.BAK'
RESTORE DATABASE SIGN FROM DISK='D:\RESTORE\SIGN.BAK'
RESTORE DATABASE SOSB FROM DISK='D:\RESTORE\SOSB.BAK'
RESTORE DATABASE SUBTREASURY FROM DISK='D:\RESTORE\SUBTREASURY.BAK'
RESTORE DATABASE TREASURY FROM DISK='D:\RESTORE\TREASURY.BAK'



8. Now comes the actual part where we are going to write a batch program incorporating the OSQL Utility which will call the backup.sql and restore.sql in its program. The coding of the batch program is as follows given in colours. Type the following code in notepad and save it with some name with extention as *.bat for eg.senthil.bat and not the default as *.txt. Further after creating this batch create a shortcut and paste the shortcut in C:\Documents and Setting\All Users\Startmenu\Program\Startup
:BEGIN
@ECHO OFF
ECHO.
CD\
D:
CD RESTORE
DEL *.BAK
ECHO.
BACKING UP FILES
osql -U SA -P password1 -S SQL_SERVER1 -i D:\RESTORE\BKPQUERY1.sql
ECHO COPYING BACKUP FILES
COPY \\MainServerName\backup D:\RESTORE
ECHO.
ECHO COPY FILES COMPLETED
DEL file://mainservername/backup *.bak
ECHO.
ECHO RESTORATION PROCESS GOING ON PLEASE WAIT
osql -U SA -P password2 -S SQL_SERVER2 -i D:\RESTORE\restorequery1.sql
GOTO BEGIN


INDEX
-----

SQL_SERVER1= The SQL instance name of the Main Server
SQL_SERVER2= The SQL instance name of the newly configure Server (i.e the clinet machine which you loaded with Win 2k3 OS)
password1= The SA password of the Main Server
password2= The SA password of the newly configured Server

DESCRIPTIVE EXPLANATION OF THE ABOVE BATCH PROGRAM STEP BY STEP.

I. I have created a loop with the key words :BEGIN AND GOTO BEGIN which is first and last line of the batch program. This will create a loop so that when the program ends the GOTO will direct the control to the place where it find the word BEGIN. Hence a loop is created.
II. In the next few steps reproduced below I am opening the folder d:\restore (you can know this if you are familiar with DOS commands)
CD\
D:
CD RESTORE

III. In the next step reproduced below I am deleting the existing backup files which are present in the path "d:\restore" as they are file created during previous cycle.
DEL *.BAK

IV. Then I am logging into the SQL Server of the main server and backing up file in the main server itself in the path "E:\BACKUP" of main Server by calling the SQL Query "backup.sql" which we have saved in the client machine in the line given below.

osql -U SA -P password1 -S SQL_SERVER1 -i D:\RESTORE\BKPQUERY1.sql

(Leave a black space between each work after "osql" in the above line except the place where I have written the path)

V. Then in the next step reproduced below I am copying the backup files (*.bak files) from the shared folder of the Main Server to the local folder "d:\restore" of the client machine which we have newly configured.
COPY \\MainServerName\backup D:\RESTORE
After copying the backup files to the client using I am deleting the backup files in the Shared folder of the Main Server with the command
DEL \\MainServerName\backup *.bak

in order to clear the disk space in the Main Server.

VI. Then I am logging into the SQL Server of client machine and calling and executing the SQL Queries stored in the file restorequery1.sql in order to restore the backed up data into the SQL server of the client machine in the following code:

osql -U SA -P password2 -S SQL_SERVER2 -i D:\RESTORE\restorequery1.sql

VII. Then the program completes and starts from the beginning. 




Now the main advantage of using the above program is that you can have a back to back replication of the databases from one Server to another. Further if you are relying on "SQL Database Maintenance Plans" you are not sure whether the backup created can be restored properly. Where as in the above case as the backup and restoration happens back-to-back there wont be any problem.
Further the workload will only be on the Client Machine or the Additional Server which we newly configure and this process will not affect the performance of the Main Server thus ensuring normal functioning.
In the event of failure of the Main Server just go that office edit all the "config.xml" files of our Meghdoot programs in the each of the client machine with the new SQL Server Name and the office is up and running. For Sanchay Post as usual run the DB Analyser and updating the DCL user and the office is up and running.
Yes there will be data loss in the event of failure of the Main Server but the loss will be very minimum to quantity of just data fed in before 20 minutes of 30 minutes would have been lost. The reason being the above batch program to complete one cycle will take some 20 minutes time. If it is an HO and if the databases are more it may take time accordingly.

I HOPE THE ABOVE METHOD IS SUGGESTED WOULD BE USEFUL TO EVERYONE IN REDUCING THE DOWNTIME OF OUR OFFICE FUNCTIONING IN THE EVENT OF A SERVER BREAKDOWN. ANY OTHER BETTER SUGGESTION PLEASE POST IN THIS THREAD IF THIS METHOD IS NOT USEFUL ALSO PLEASE GIVE YOU FEEDBACK IT WILL HELP ME IN REFINING OF FINE TUNING THIS METHODOLOGY.

SanchayPost Frequently Asked Questions

FAQ on Version 6.5

Upgradation (1) 1. While running DBAnalyzer >> Check Databases >> Version 6.5, the message "Upgradation to version 6.5 is not successful. Error Code1 : Z" is displayed. a) Run upgradation once again using Start Menu -    "Sanchay Post >> Upgrade DB >> Patch for SQL 70/ Patch for SQL 2000 & 2005 (Version 6.0 to 6.5)" b) Use DB Analyzer >> Check Databases >> Version 6.5 again, to check if the upgradation is successful.

Online Transactions (2) 1. In RD Bulk Acceptance, the error message "Not a valid agent, exiting application" is displayed. a) Copy the patches for Version 6.5 to the respective folders b) Use 'DBAnalyzer >> Database Discrepancies >> RD >> Agent Updation' option. c) Also, check the expiry date of the Agent's authority in Sanchay Post Form no. 0403   2. No. of accounts scanned not correctly displayed in ‘Signature Scanning’ report in DBAnalyzer. Based on the feedback received from various sites, some changes have been made in the ‘Signature scanning report’ available under ‘Reports’ option of DBAnalyzer. Before using Reports option go to ‘Database Discrepancies’ >> ‘Scheme’ (SB, PPF & NSS) >> ‘Account numbers with blank account status’ and rectify the discrepancies using the 'Update' button provided in the screen.

Online Transactions - SCS (4) 1. How to Extend an SCS account? Extension of SCS accounts can be performed in the software only after payment of the partial interest for the last quarter. After payment of the final partial interest, the Supervisor can extend the account (Using form no 1418). 2. While closing SCS accounts on date of maturity, in the closure screen, partial interest is not displayed. Run DBAnalyzer (exe dated 20/08/2009 or later). Select ‘Database Discrepancies >> SCS >> Updation of maturity date’ and click on ‘Display’ and wait till the message ‘Updation completed’ is displayed. Subsequent to this updation, closure can be done in Sanchay Post Online module.   3. Unable to extend SCS accounts having withdrawal type as ‘Standing Instructions’, since the final partial interest cannot be paid in cash. Run DBAnalyzer (exe dated 20/08/2009 or later). Select ‘Database Discrepancies >> SCS >> Updation of Withdrawal Type for matured accounts’ and click on ‘Display’ and enter the account number for which extension has to be performed and click 'OK'. Then, withdrawal of interest can be done in Sanchay Post Online module and subsequently extension can be performed by the Supervisor. After extension, standing instruction, if requested by the customer for the extended period, is to be added afresh using ‘Common >> SI Entries’ form.   4. Standing Instructions in respect of SCS extended accounts not posted in SB accounts The problem does exist in the software. After day-begin and the execution of SI (on the due date of interest posting for each quarter), the list of SCS accounts for which SI has not be executed can be printed from DBAnalyzer using ‘Database Discrepancies >> SCS >> Account numbers with SI without previous quarter interest withdrawal’. This list can be used for cross-verification. For the present quarter withdraw interest from such SCS accounts individually using the ‘Withdraw Interest’ Form in Online Module and select ‘Transfer to SB Account’ in the payment options and enter the SB account number. To alter the withdrawal type from ‘SI’ to cash use DB Analyzer >> Database Discrepancies >> SCS >> Select ‘updation of withdrawal type for matured accounts’ >> Enter account number and update withdrawal type.

Data Conversion V2SBCO to Sanchay Post (1) 1. After conversion from V2SBCO to Sanchay Post, while checking the "Passbook View", error message "Invalid account number" is displayed. a. Check whether the account number block is available in ‘Initialisation >> Account numbers’ in     supervisory login of Online module of Sanchay Post. b. Check whether any account numbers are displayed in ‘DBAnalyzer >> Database Discrepancies >>     [scheme] >> Index entries with different POCode’. c. Check whether any account numbers are displayed in ‘DBAnalyzer >> Database Discrepancies >>     [scheme] >> Ledger entries without index entries’

SO to HO Data Transfer (7) 1. How to reset the sequence number to 1 at SO? Use the option ‘DBAnalyzer >> Data Transfer >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme. This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post. 2. How to reset the sequence number to 1 at HO for a SO? Use the option ‘DBAnalyzer >> Data Transfer >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO. 3. What are the preparatory steps for commencement of SO to HO data transfer? The following points are to be ensured: a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code. b. Include HO name in SOs (Using PO Name & Address Form) in a separate row. c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed. d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which data     transfer is to be commenced. e. Rectify the discrepancies listed in DBAnalyzer.   4. Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated. Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check  ‘Initialisation >> PO Name & Address’ form and ensure that  the scheme is selected  in ‘Set Scheme Computerisation Status’ option.   5. Files generated at SO are without extension and hence cannot be imported at HO HO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row.   6. 'Data does not belong to [soname]’ message displayed while importing data. Select the file again and retry Logout and login to SOSB module and retry Ask SO to re-generate the file & resend. If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO. 7. RD bulk posting data not transferred. RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).

Project Arrow / Meghdoot Accounts MIS (5) 1. While running Accounts MIS client, error message displayed as “Unable to continue due to the following error: There is a problem with SQL server. Login failed for user 'arrow'.”   If Accounts MIS application was being used in Meghdoot Version 6.5 earlier and you have upgraded to Meghdoot Version 6.6, contact PTC Mysore for solution. In offices where ‘Sanchay Post Project Arrow Interface’ was installed from Meghdoot 6.6 CD uninstall the ‘Sanchay Post Project Arrow Interface’ module and also delete ‘Project arrow reports’ shortcut if available in the desktop. If Accounts MIS application is installed afresh and the above mentioned error occurs, following are the possible actions: a) If Sanchay Post Version 6.0 or earlier version is used, upgrade to Version 6.5 immediately. b) If you are already using Sanchay Post Version 6.5, use DBAnalyzer to check whether you have    upgraded to Version 6.5 successfully. While checking, if DBAnalyzer displays error code 1: Z, run    ' ARROW.EXE' to create the Project database & login. c) If you have shifted operations to a new server after upgradation to Sanchay Post Version 6.5,     run 'ARROW.EXE'' to create the Project database & login and then restore the Project database's     backup, if available. Not restoring your backup of Project database or removal of the existing     Project database and recreating it using 'ARROW.EXE' will result in loss of previous transaction data. d) Use patchstatus.exe to ensure that all the patches available are installed in all the systems     running Sanchaypost and especially in the system from which day end is performed. The KPIs are updated during day end process automatically.   2. While running Accounts MIS client, error message displayed as “There is some application error. Either day end has not happened in Sanchaypost or the arrow related information for Sanchaypost is not available. Application cannot continue.”   Use PatchStatus.exe to ensure that all the patches available are installed in all the systems running Sanchaypost and especially in the system from which day-end is performed. Uninstall the ‘Sanchay Post Project Arrow Interface’ module. Delete ‘Project arrow reports’ shortcut if available in the desktop.  To view the KPIs, the option ‘Sanchay Post >> Project Arrow >> Transaction Time Report’ should only be used. The KPIs are updated during day end process automatically.   3. INSTRUCTIONS FOR USING ARROW.EXE 1. Click here to download ARROW.EXE 2. Unzip the downloaded file, copy it to the DBAnalyzer folder and run the exe file. 3. Use latest DBAnalyzer >> 'Check databases' >> Version 6.5 and verify if the message     'Upgraded successfully to Version 6.5' is displayed.   4. Offices having problem in uploading SB KPI's using Account MIS should ensure the following: In offices where ‘Sanchay Post Project Arrow Interface’ was installed from Meghdoot 6.6 CD uninstall the ‘Sanchay Post Project Arrow Interface’ module and also delete ‘Project arrow reports’ shortcut if available in the desktop. This should be done in all the systems in which the interface was installed. Ensure that Sanchay Post Version 6.5 is installed. Use DBAnalyzer to check whether you have upgraded to Version 6.5 successfully. Use patchstatus.exe to ensure that all the patches available are installed in all the systems running Sanchaypost. While performing day end ensure that the message ‘Day end completed successfully’ is received. 5. Offices having difference in the number of signatures scanned shown in SB KPI's and DBAnalyzer. Use DBAnalyzer with latest exe (dated 12/11/2009 or later) Check for patches installed in all clients using 'Patch Status' Go to ‘Database discrepancies’ >> ‘Account numbers with blank account status’ for ‘SB’, ‘NSS’ and ‘PPF’ and update. Go to ‘Reports’ >> ‘Signatures without index entries’ >> and delete the entries after confirming that the account numbers listed are not existing. Go to ‘Reports’ >> 'signature scanning report' and verify. click on the button 'List of accounts - signature not scanned' to obtain account numbers for which Specimen Signature is not scanned. The file generated can be opened and signatures to be scanned for the accounts listed in it.