PEP Read Me First
=================

PEP Number: CP202S03G22S
Pep Title:  Infinite loop in Version Manager because of data corruption


(0) Target Release
==================
CallPilot 02.01.27.05 SU03


(1a) Target Platform
====================
CallPilot Server - 200i/201i/702t/703t/1001rp/1002rp


(1b) Affected Connectivities
============================
Meridian 1 / Succession 1000		


(2) Problem Description
=======================
Q00996757:
A potential problem has been identified within the Notification Service, 
that if experienced results in 100% CPU Utilization which may cause 
call processing issues such as slow call answering requiring additional 
system maintenance to be performed.  This issue usually occurs during 
the Version Manager Audit.

CallPilot uses a Version Manager to track the current and obsolete 
versions of the applications that are currently being used on the 
server. The applications that are tracked by the Version Manager 
are both Appbuilder and imbedded applications ("Voice Item Maintenance", 
"Voice Messaging", etc). An issue was identified within the Version 
Manager Data table. The issue is related to the current and obsolete 
versions for an application are the same in the data table. This 
condition results in an infinite loop during Version Manager Audit. 

Q00982422:
CallPilot uses a database population process which occurs automatically 
during the initial configuration phase after completing an upgrade.  
If Service Update 3 (SU03) is installed immediately after completing 
the upgrade to CP2.02 but prior to being booted into full service 
and accepting calls, the database is not properly populated and 
AppBuilder Applications will not be accessible or available. 
   
Q00937327, Q00940757, and Q00986040:
CallPilot automatically runs audits on a nightly basis. It has been 
identified that a condition exist were the Version Manager audit 
will fail to complete successfully, leaving the Notification 
Server consuming more than 90% of the available CPU.

Q00959966:
Two new events were added in the audit routine indicating the successful 
start (55045) and completion (55046) of the Version Manager audit. 
This change is in conjunction with Q00937327


(3) List of CRs that are fixed by this PEP 
==========================================
Q00996757 Infinite loop in Version Manager because of data corruption
Q00982422 AppBuilder Applications inaccessible and unavailable after SU03 was applied
Q00937327 Notification server consumes more than 90% CPU
Q00959966 Events 55045 and 55046 added into Fault Manager


(4) Dependencies
================
This PEP requires the CP20127SU03S (SU03).

This PEP replaces the following PEP:

   - CP202S03G17S

The replaced PEP will be automatically uninstalled when CP202S03G22S is installed.


(5) How to install this PEP
===========================
(i) Stop all CallPilot services.

(ii) Copy the file as follows:

	#   File		Destination directory
	----------------------------------------------
	1.  nmflteve.sql	D:\Nortel\Mpcx\Data
	2.  nmflteve_upg.sql	D:\Nortel\Mpcx\Data
	3.  nmfltevec.sql	D:\Nortel\Mpcx\Data
	4.  nmfltevec_upg.sql	D:\Nortel\Mpcx\Data
	5.  nmfltobj.sql	D:\Nortel\Mpcx\Data
	6.  nmfltobj_upg.sql	D:\Nortel\Mpcx\Data
	7.  nmfltobjc.sql	D:\Nortel\Mpcx\Data
	8.  nmfltobjc_upg.sql	D:\Nortel\Mpcx\Data
	9.  Nbfltmsg.dll	D:\Nortel\bin
	10. Nbfltcat.dll	D:\Nortel\bin
	11.  nmvmupdate.dll	d:\Nortel\Mpcx\bin          
	12.  nmnss.exe		d:\Nortel\Mpcx\bin          
	13.  nmvmmapfile.dll	d:\Nortel\Mpcx\bin          
              
(iii) Run from D:\Nortel\Mpcx\Data:

	dbisqlc -q -c "UID=blue;PWD=****" read nmflteve.sql
   	Wait 10 seconds

	dbisqlc -q -c "UID=blue;PWD=****" read nmfltobj.sql
	Wait 10 seconds

(iv) Run Fault Management Compiler:

	D:\Nortel\bin\nbfltdbcm.exe D:\Nortel\Mpcx\data	

(v) Reboot the server


(6) List of suggested test cases
================================
6.1.1 Stop the following services:
       - Service Manager
       - SLEE
       - Notification Service
       - AOS
       - LDAP
6.1.2 Place VM data file to d:\nortel\mpcx\data
6.1.3 Start the following services:
       - LDAP
       - AOS
       - Notification Service
       - SLEE
       - Service Manager
6.1.4 Start Garbage Daemon audit
6.1.5 In MAS trace window check that VM audit started
6.1.6 In MAS trace window check that VM audit completed
6.1.7 In Windows Task Manager check that CPU is not 100% busy.

6.2.1 Check that the registry key exists:
       - HKEY_LOCAL_MACHINE\SOFTWARE\Nortel\mpcx\nmvm\RebootKey
6.2.2 Change startup type to DISABLE and stop the following services:
       - Service Manager
       - SLEE
       - Notification Service
       - AOS
       - LDAP
6.2.3 Delete file d:\nortel\mpcx\data\NMVMmem_map
6.2.4 Start the following services:
       - LDAP
       - AOS
       - Notification Service
       - SLEE
       - Service Manager
6.2.5 Change startup type of these services to initial values
6.2.6 Check that d:\nortel\mpcx\data\NMVMmem_map file was re-create
6.2.7 Try to open any application using AppBuilder
6.2.8 Check that application can not be opened and you get error
        "Please check connection..."

6.3.1 Check that the registry key exists:
       - HKEY_LOCAL_MACHINE\SOFTWARE\Nortel\mpcx\nmvm\RebootKey
6.3.2 Change startup type to DISABLE and stop the following services:
       - Service Manager
       - SLEE
       - Notification Service
       - AOS
       - LDAP
6.3.3 Delete the file d:\nortel\mpcx\data\NMVMmem_map
6.3.4 Change startup type of these services to initial values
6.3.5 Reboot CallPilot
6.3.6 Wait until CallPilot is up and running     
6.3.7 Check that the d:\nortel\mpcx\data\NMVMmem_map file was re-create
6.3.8 Try to open any application using AppBuilder
6.3.9 Check that application can be opened and saved successfully
6.3.10 Check that CallPilot can accept calls to SDN with AppBuilder applications
6.3.11 Check that the registry key exists:
       - HKEY_LOCAL_MACHINE\SOFTWARE\Nortel\mpcx\nmvm\RebootKey


(7) Special instructions
========================
None.
