Upgrade Problem from rel8.0.1 to rel 10.1

[wallacezammit]

Hi,

I am upgrading from rel8.0.1 patch26e to release 10.1.

The upgrade is succesfull apart from the IP Phones. The Ip Phones switch on and tell you to enter the extension number but once I do this they reset and then hang on 5/5 connecting. And they never connect.

It is like the NOE application is not switched on.

I then did a checkdb to release 8.0.1 and found the following errors of which one is regarding IP Phones :

/............ERROR 4351 : DATA INCONSISTENCY, Table ADRFICT, function=addr already used nulog=1127 Coupler=0 Position=46
ERROR 4351 : DATA INCONSISTENCY, Table POSTE, station=5479 eqt already busy=2963 not resu nulog=1127
..ERROR 4351 : DATA INCONSISTENCY, Table SETGPBX, station=5103 pbx_number=8 range_gpbx=1

...............ERROR 2675 : EXCEPTION 11, function ini_ipphone, PC = 0x081676f5
ERROR 4352 : INSTANCE EXCEPTION, Table TAB_IPP, nulog=1127
...ERROR 4351 : DATA INCONSISTENCY, Table NOE_PARAM, nulog=126 Attribut=16


I also tried to upgrade to rel9.1 and everything worked fine but when upgrading to release 10.0 or 10.1 the IP phones do not start.

Any ideas?

Can the errors in the database of rel8.0.1 be repaired?

The following are the incvisu and excvisu logs were we can see the montiel error and the backtrace as well :

29/02/12 03:39:54 000098M|---/--/-/---|=2:1660=Monitel: Lack of resource type 5
29/02/12 03:39:54 000098M|---/--/-/---|=2:1722=Aborted telephone task, PC 0x0943ffdb exc -10 neqt 1134

29/02/12 03:39:57 000098M|---/--/-/---|=2:1660=Monitel: Lack of resource type 5
29/02/12 03:39:57 000098M|---/--/-/---|=2:1722=Aborted telephone task, PC 0x0943ffdb exc -10 neqt 1134

Getting te backtrace

There is a new exception. Its address is : 0X0943FFDB. Monitel time : 055263. Date : Wed Feb 29 03:39:54 2012
GS=000004b5 FS=00003039 ES=00000000 DS=0000002b
EDI=52eca050 ESI=01856b1c EBP=01856b94 ESP0=00000000
EBX=00000009 EDX=fca80000 ECX=000038d8 EAX=0000000a
EIP=0943ffdb CS=00000023 ESP3=01856af8 EFLAGS=00000206
Application-Abort, thread 1205, PC=0x0943ffdb:155451355, eqt=1134, serv=0 --> xevent
* Backtrace: 0x0882c143:142786883 EBP 0x01856b94 --> privtopub_local_overflow
* Backtrace: 0x08a6c2ff:145146623 EBP 0x01856bec --> test_s63
* Backtrace: 0x08a6cb10:145148688 EBP 0x01856c08 --> postbon
* Backtrace: 0x08a6ce82:145149570 EBP 0x01856c3c --> esaploc
* Backtrace: 0x08a6cff9:145149945 EBP 0x01856c60 --> rech_ou_aploc
* Backtrace: 0x08a6d7c9:145151945 EBP 0x01856c6c --> aplourv
* Backtrace: 0x08a6dff8:145154040 EBP 0x01856d28 --> appeloc
* Backtrace: 0x08a6f461:145159265 EBP 0x01856d54 --> loc_rsvp
* Backtrace: 0x08adb4b9:145601721 EBP 0x01856d80 --> reptrad_local_station
* Backtrace: 0x08addf99:145612697 EBP 0x01856d98 --> sui_decreptrad
* Backtrace: 0x08ade274:145613428 EBP 0x01856dbc --> decreptrad
* Backtrace: 0x0874a261:141861473 EBP 0x01856dcc --> allons_faire_nos_courses
* Backtrace: 0x0874a4f7:141862135 EBP 0x01856ddc --> reroute_local
* Backtrace: 0x0874c795:141870997 EBP 0x01856e50 --> demar_rln
* Backtrace: 0x0874cc0d:141872141 EBP 0x01856e70 --> testars
* Backtrace: 0x087fa69d:142583453 EBP 0x01856e78 --> demarnum
* Backtrace: 0x087487fc:141854716 EBP 0x01856e80 --> ars_demarnum
* Backtrace: 0x087fac99:142584985 EBP 0x01856e8c --> numsansjonc
* Backtrace: 0x093b0761:154863457 EBP 0x01856ea4 --> real_main
* Backtrace: 0x093adc0b:154852363 EBP 0x01857fe8 --> start_thread_delayed
GS=000004b5 FS=00003039 ES=00000000 DS=0000002b
EDI=52eca050 ESI=01856b1c EBP=01856b94 ESP0=00000000
EBX=00000009 EDX=fca80000 ECX=000038d8 EAX=0000000a
EIP=0943ffdb CS=00000023 ESP3=01856af8 EFLAGS=00000206
B(53967:001) Eqt=01134 Emi=01134 {00000, 00003, 0x87fa748} wait=0x87faf8c,0x8499ae0
Exception again. Monitel time : 055297. Date : Wed Feb 29 03:39:57 2012
Exception again. Monitel time : 075578. Date : Wed Feb 29 04:13:45 2012




Any ideas?

Regards
Wallace Zammit

[OXE_4400]

Which patches You had tried in R10.0 or R10.1 ?

[charpdy]

We had the same problem at customer site

Customer upgraded from g1.302.12 to j2.501.16.b. After upgrade IP phones are not recconecting.


Here are the response from TS :
Diagnosis:
Analyzed the infocollect, found there is a database issue,
“ERROR 4351 : DATA INCONSISTENCY, Table ADRFICT, function=addr already used nulog=222 Coupler=0 Position=13”

Found that this is a known issue as per crms00347470 & crms00369709 and is fixed in patch j1.410.46.

Solution:

Suggested to upgrade using the below process

( Upgrade from R8.0. to R10.1)
=========================

Release 8.0 (g1.302.12)
=====================

1).back up database
2).get DATABASE to PC


Release 9.0(h1.301.50.a)
====================
1).Restore DATABASE
2)."RUNTEL"
3).RECOVERY by "fichges force_recover_dico" command
4).use "checkdb" don't have error
5).BACKUP DATABASE
6).get DATABASE to PC


Release 9.1 (i1.605.39)
=======================

1).Restore DATABASE
2)."RUNTEL"
3).RECOVERY by "fichges force_recover_dico" command
4).use "checkdb" don't have error
5).BACKUP DATABASE
6).get DATABASE to PC

Release 10.0 (j1.410.46)
=======================

1).Restore DATABASE
2)."RUNTEL"
3).RECOVERY by "fichges force_recover_dico" command
4).use "checkdb" don't have error
5).BACKUP DATABASE
6).get DATABASE to PC

Release 10.1(j2.501.17)
====================

1).Restore DATABASE
2)."RUNTEL"
3).RECOVERY by "fichges force_recover_dico" command
4).use "checkdb" don't have error


BR

Per

[wallacezammit]

Hi,

Im upgrading to rel 10.1

I checked for these releases but couldn't find releases 10.0 j1.410.46 - there is j1.410.49. I think this should be ok.

But for release 10.1 j2.501.17 is a limited edition release. Didi they specify that you need this? or can I use j2.501.16?

Regards
Wallace

[OXE_4400]

Customer upgraded from g1.302.12 to j2.501.16.b. After upgrade IP phones are not recconecting.
Here are the response from TS :
Suggested to upgrade using the below process
( Upgrade from R8.0. to R10.1)
=========================
Release 8.0 (g1.302.12)
=====================
Release 9.0(h1.301.50.a)
====================
Release 9.1 (i1.605.39)
=======================
Release 10.0 (j1.410.46)
=======================
Release 10.1(j2.501.17)
====================
Per

Are they kidding?
Migration from 8.0 to R10.1 with all intermediate versions. First time I see such proposal.
Exist some cases with one intermediate version, but not with all.

[krzysioD]

And R&D don't seem to even notice the problem.
It should be done by db translation in upgrade process.
I would expect - 1st upgrade to the very latest R8.0.1 patchlevel, and then to R10.1 not so many steps...
BTW: update a R2.1 to R10.1 - it's a challenge

[OXE_4400]

BTW: update a R2.1 to R10.1 - it's a challenge

I would say not so big. 2 or 3 steps max.
R2.1=>R5.0 or R6.1 => R8.0.1?=>R10.1

[wallacezammit]

Hi,

even to me thats what they said - rel8.0.1 to 9.0 to 9.1 to 10.0 and then 10.1

I tried it but didn't work out.

They I installed PC installer by downloading it directly from site instead of installing it from the release. I did the installation again and everything worked.

But I'm still concerned because when I do the fiscges command there are a lot of errors like the following :

Recovering data/index files for table EXTMGT (349/350)...Open file EXTMGTM faile
d
Error -16002
done
Recovering data/index files for table CACSERVE (350/350)...Open file CACSERVEM f
ailed
Error -16002
done


Even when I went from release 8 to rel 9.0 and did fisches I got a lot of errors like these - dnt know if its normal or not.

[wallacezammit]

Hi Charpdy,

did it solve your problem the procedure which they gave you?

[krzysioD]

Some time ago - i got strange errors when doing a big upgrade to R9.1 - there were missing .DAT files in R3, in old R3 - it was not being noticed, but in R9.1 the ARS simply didn't work. So i gather empty DAT files from vanilla R9.1 install and merged into the upgraded system. It works.
But it's a process - for an very advanced guys, not end user - you need to know what you are doing and what ID's are connected to other DAT files.
Maybe - better to send eSR with old DB, write to alu that this procedure does not work and - let them do the upgrade?

BTW: there is some TC about that - in very rare case - asks to upgrade via immediate step on - virtual machine (some rare, rare case with change of CPU type).

Tried to start with R8.0.1 with patch level 35 - h ?