No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Cause for database inconsistency during the OSN3500 equipment database comparison

Publication Date:  2012-07-24 Views:  31 Downloads:  0
Issue Description
The database inconsistency is found through the database comparison of the OSN3500 equipment.
:dbms-compare-all:mdb,drdb;

                          DBMS-COMPARE-ALL-DBF               
      DBF_NO      DBF_NAME                                 

      1           allDBFaresame            

                     Total records :1                            
 
#9-212:szhw [NE212][][2004-10-30 11:26:11]>

:dbms-compare-all:drdb,fdb0;

                                DBMS-COMPARE-ALL-DBF               

                            DBF_NO      DBF_NAME             

                            1           USER.DBF                                 
                Total records :1                                       
#9-212:szhw [NE212][][2004-10-30 11:26:16]>

:dbms-compare-all:drdb,fdb1;

                                DBMS-COMPARE-ALL-DBF                              
 
                            DBF_NO      DBF_NAME                                 

                            1           USER.DBF           

                   Total records :1                         
#9-212:szhw [NE212][][2004-10-30 11:26:22]>

Compare the databases after the backup operation. They are consistent. However, the above information is again reported when the comparison is conducted soon after.

Alarm Information
 None


Handling Process
1. Query the update time of the user.dbf database in the current drdb and fdb0 databases of the OSN equipment.

dbms-get-updatetime:"user.dbf",drdb;

  DBMS-UPDATETIME  : 2004-11-15 17:35:1                                          

#9-212:szhw [NE212][][2004-11-15 17:35:14]>
 
:dbms-get-updatetime:"user.dbf",fdb0;

  DBMS-UPDATETIME  : 2004-11-15 8:52:34                                          

#9-212:szhw [NE212][][2004-11-15 17:35:16]>
 
 2. Log out the NE

:logout

#9-212: [NE212][][2004-11-15 17:35:28]>
 
               EVENT_SM_LOGOUT                         
Dst-NAME      Dst-ADDR           Src-NAME      Src-ADDR      Quit-Type   

szhw    SUBID:9 LOGNEID:212       szhw   SUBID:9 LOGNEID:212  cmd_quit     

#9-212: [NE212][][2004-11-15 17:35:28]>
 
3. Log in to the NE again and then query the update time of the user database in the current drdb and fdb0 databases.

#212:login:"szhw","nesoft";

  LOGIN  : Last log time : 2004-11-15 17:35:01   

#9-212:szhw [NE212][][2004-11-15 17:35:29]>
:dbms-get-updatetime:"user.dbf",drdb;

 DBMS-UPDATETIME  : 2004-11-15 17:35:29            

#9-212:szhw [NE212][][2004-11-15 17:35:31]>
:dbms-get-updatetime:"user.dbf",fdb0;
  DBMS-UPDATETIME  : 2004-11-15 8:52:34               
#9-212:szhw [NE212][][2004-11-15 17:35:36]>
4. As shown in Steps 1, 2 and 3, the information in the user.dbf database of the OSN equipment changes when the user logs in or out. The changes will be recorded in the user.dbf database of the mdb and drdb database. Through manual backup, the data in the mdb, drdb and fdb0/1 databases become consistent. However, the information in the user.dbf database in the mdb and drdb databases changes after some time.
5. Query the update time of the user.dbf database in the current drdb and fdb0 databases of the 2500+ equipment.
:dbms-get-updatetime:"user.dbf",drdb;
  DBMS update time  : 2004-11-15 16:57:02                                 
#9-103:szhw [103-extended][2004-11-15 19:38:48]>
:dbms-get-updatetime:"user.dbf",fdb0;
  DBMS update time  : 2004-11-14 20:13:18                                    
#9-103:szhw [103-extended][2004-11-15 19:38:51]>
6. Log out the NE
:logout;

                                LOGOUT EVENT                               

                                   USER-NAME                                 

                                   szhw                                      

#9-103:szhw [103-extended][2004-11-15 19:38:57]>
 
7. Log in to the NE again and then query the update time of the user database in the current drdb and fdb0 databases.
#103:login:1,"nesoft";
#9-103:szhw [103-extended][2004-11-15 19:39:30]>
:dbms-get-updatetime:"user.dbf",drdb;
  DBMS update time  : 2004-11-15 16:57:02                                    
#9-103:szhw [103-extended][2004-11-15 19:39:32]>
:dbms-get-updatetime:"user.dbf",fdb0;
  DBMS update time  : 2004-11-14 20:13:18                                    
#9-103:szhw [103-extended][2004-11-15 19:39:34]>
8. As shown in Steps 5, 6 and 7, the information in the user.dbf database of the conventional OSN equipment does not change when the user logs in or out. Therefore, the data in the mdb, drdb and fdb0/1 databases are consistent.
<Suggestion and summary>= 1. The modes for the OSN series equipment (including 1500, 2500 and 3500) and the conventional SHD equipment to process the login information are different. The OSN series equipment will record the login information in the database, but the conventional SDH equipment will not.
2.      In the future, you should explain in the OSN equipment inspection standard that the user.dbf database inconsistency is normal.
Root Cause
The database information and processing mode of the OSN equipment are not completely the same as those of the conventional SDH equipment. For the OSN equipment, such information as user login or logout is recorded in the user database.

The change information will update the mdb and the user.dbf database in the drdb database.

Although the OSN equipment provides the auto backup function (backup from drdb to fdb0/1), it conducts backup every 30 minutes. Within the 30 minutes, the user may keep logging in/out (in fact it is quite probable). This may result in inconsistency of the data in the drdb and fdb0/1 databases.

The conventional SDH will not be like this, since the login information is not recorded in the user.dbf database.
Suggestions
See also case in chinese:SC0000005713


END