CLEANING UP REDUNDANT NODES

IN OPTIMA SCHEMAs FOR IVLP

Description of Procedure
Below is the deletion procedure to be used for cleaning up decommissioned nodes.
AIRCOM.SP_DELETE_ENTITY_PROC('ENTITY_NAME','SCHEMA_NAME','AFFECT_LEVEL')

*Enter all variables as-is in live network

1. Possible values for ENTITY_NAME are in bold print below;

A 2G e.g. 1234A
A 3G e.g. 1234A1
An LTE cell e.g. L1234A1
A 2G site e.g. T1234
A 3G NODEB e.g. U1234
Or LTE enodeb e.g. L1234
Note: The entity name specified will be dictated by the AFFECT_LEVEL of interest and should correspond to the
correct SCHEMA_NAME. Entity names requiring deletion should be entered AS-IS in live network.

2. Possible values for SCHEMA_NAME are in bold print below;

ERICSSON_GERAN
ERICSSON_CMUMTS
ERICSSON_EUTRAN
HUAWEI_R15_GERAN
HUAWEI_R15_UTRAN
HUAWEI_R15_EUTRAN
ZTE_GERAN_CM
ZTE_UTRAN_CM
ZTE_EUTRAN_CM
Note: SCHEMA_NAME specified should correspond to ENTITY_NAME of interest and corresponding
AFFECT_LEVEL.

3. Possible values for AFFECT_LEVEL are listed in bold print below;

MSC: For MSC cleanups as regards 2G and 3G interfaces on any of the 3 vendors dependent on specified
SCHEMA_NAME
BSC: For BSC cleanups as regards GERAN on any of the 3 vendors dependent on specified SCHEMA_NAME i.e.
%GERAN%
RNC: For RNC cleanups as regards UTRAN on any of the 3 vendors dependent on specified SCHEMA_NAME i.e.
%UTRAN%
CELL: For CELL cleanups as regards 2G, 3G and LTE cells on any of the 3 vendors dependent on specified
SCHEMA_NAME

SITE: For SITE cleanups as regards 2G SITEs any of the 3 vendors dependent on specified SCHEMA_NAME i.e.
%GERAN%
NODEB: For NODEB cleanups as regards 3G NODEBs on any of the 3 vendors dependent on specified
SCHEMA_NAME i.e. %UTRAN%
ENODEB: For ENODEB cleanups as regards LTE ENODEBs on any of the 3 vendors dependent on specified
SCHEMA_NAME i.e. %EUTRAN%

Steps to Run Procedure and Examples

Single Entry Deletions
The clean-up procedure can be run as follows for single entry deletions;
BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('L00964','ERICSSON_EUTRAN','ENODEB');
END;

Above will delete the ENTITY_NAME = L00964 from ERICSSON_EUTRAN schema whose affect level is ENODEB.
More examples listed below;
To delete 2G cell 964A:
BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('964A','ERICSSON_GERAN','CELL');
END;

To delete 3G cell 964A1:

BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('964A1','ERICSSON_UTRAN','CELL');
END;

To delete LTE cell L0964A1:

BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('L0964A1','ERICSSON_EUTRAN','CELL');
END;

To delete 2G site T0964:

BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('T0964','ERICSSON_GERAN','SITE');
END;

To delete NodeB U0964:

BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('U0964','ERICSSON_UTRAN', 'NODEDB');
END;

To delete ENodeB L0964

BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('L0964','ERICSSON_EUTRAN', 'ENODEDB');
END;

To delete JHBSC1
BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('JHBSC1','ERICSSON_GERAN', 'BSC');
END;

To delete JHRNC1
BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('JHRNC1','ERICSSON_UTRAN','RNC');
END;

To delete JHMBC1
BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC('JHMBC1','ERICSSON_GERAN','MSC');
END;

Bulk Deletions
For bulk deletes, it can as well be run dynamically by referencing records in Emmanuels table for delete entities.
Examples:
To delete all records as per select statement in ZTE EUTRAN schema
DECLARE
BEGIN
FOR REC IN (SELECT ENODEB FROM ZTE_EUTRAN_CM.VW_LOAD_DELETEDENODEBS)
LOOP
BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC (REC.ENODEB, 'ZTE_EUTRAN_CM', 'ENODEB');
END;
END LOOP;
END;

To delete all records as per select statement in ERICSSON EUTRAN schema

DECLARE
BEGIN
FOR REC IN (SELECT CELLNAME FROM ERICSSON_EUTRAN.VW_LOAD_DELETEDGCELLS)
LOOP
BEGIN
AIRCOM.SP_DELETE_ENTITY_PROC (REC.CELLNAME, 'ERICSSON_EUTRAN', 'CELL');
END;
END LOOP;
END;

Note that care should be taken when deleting higher level entities like MSCs, RNCs, BSCs because these will obviously
delete lower level entities e.g. BTSs, NodeB, eNodeBs and Cells under them.