You are on page 1of 2

7762 RNW DATABASE OPERATION FAILURE Meaning

RNW database operation has failed. This reading or writing operation was tried to be carried out for some of the following scenarios: - WBTS reset - WBTS initialization - Cell activation - Cell blocking - Cell unblocking - Modification of configuration data - Storing the pids - Storing the WBTS capability information - Storing cch parameters - Cell unlocking - Cell reconfiguration - RNC restart - Audit handling - Iu service barring - Resource status indication handling - Common measurement supervision Depending on the scenario, this failure has lead to a situation where cell state could not be modified from blocked to working state or vice versa in RNC or it was not possible to send configuration data to WBTS. Failure in pid updating can cause troubles to other O&M scenarios where that information is needed, and failure in WBTS capability updating or cch parameter updating can cause inconsistent data to be used in RNC and thus problems in signalling or in actual calls.

Supplementary information fields


1 specifies if the error occurred during reading from or writing to database 01 02 2 Reading failure Writing failure

reason of the failure 00 01 02 03 04 05 11 12 Not specified Failure at initialization Configuration data Inactivation of the cell has failed Activation of the cell has failed NBAP-link state updating failure Failure in cell setup, 3GPP iub Failure in cell reconfiguration, 3GPP iub

scenario that was being carried out when the failure occured 01 02 03 04 05 06 07 08 09 0A 0B WBTS initialization Cell unlocking Configuration data modification RNC restart Local cell resource state change Forced handover WBTS reset WBTS capability information update Pid update CCH data update Link failure/link failure cancel

0C 0D 0E 81 82 83 84 8D 8E 8F 90 91 4

CCH Supervision Audit handling, 3GPP iub Iu service barring WBTS initialization, 3GPP iub Cell unlocking, 3GPP iub Cell reconfiguration, 3GPP iub RNC restart, 3GPP iub WBTS restart, 3GPP iub WBTS cell block, 3GPP iub WBTS cell unblock, 3GPP iub Resource status indication handling, 3GPP iub Common measurement supervision

general error code of the system. You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References

Instructions
At first check the functionality of Radio Network database with following MML-commands: ZDBS:RAQUEL,0; State of database should be normal and memory (and disk) updates are not prevented. If updates are prevented, you can resume them with command ZDBR:RAQUEL,0:<mem or disk>; If database state is "waiting for dumping" or "dumping", database should return to normal state automatically after dumping is ready. Also status of the disk updating system can be check with MML-command ZDBD:OMU; Line "RAQUEL" specifies the state of Radio Network database. If database state is working (or becomes working after while), do as follows: 1. Try to lock the cell and then unlock the cell with RNC Object Browser. If this does not clear the alarm, WBTS reset can be tried 2. If database state stays abnormal for long time or the alarm appears constantly for several WBTSs and cells, contact the local Nokia Siemens Networks representative. Also RNC reset might help if it is possible to make. 3. More information about the exact fail reason can be found by examining the supplementary info field 4 (error code). In many cases there also more info in OMU computer log. It can be studied with MML-command ZDDE::"ZGSC"; 4.

Cancelling
Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected.

You might also like