HiPath 4000 Upload Crash

[synstsia]

Hoping someone can help- Recently, running the upload option from the Assistant has been crashing Unixware- IE, when I run it, it will report that the upload is running, but then a few seconds later, the assistant goes down and Unixware also closes any telnet sessions open. (it comes back up after a few minutes) I have run both EX-UPDAT:BP,ALL; and EXE-UPDAT:A1,ALL; from the MML dialog and this completes successfully- but running upload from assistant crashes.

Does anyone know of any log files I can look at from a telnet session or can I tail any logs that may be useful? Better yet, is there any manual way of syncing the databases other than the EX-UPDAT?

Thanks for any help!!

 

[sbcsu]

Firstly try to activate all the areas of the hard disk just in case.

ACT-DSSM:A1,1;

Then try again.

 

[Moriendi]

What software version is the hipath and what patch leve for Assistant? Can't tell if it's the ADP making a soft restart (which will restart Unixware on V5 and below) or just the Assistant having a problem. Logs are something like /opt/cm/sad/diabatch/SAVE but that's from memory. Exec-updat is only writing the DB from memory to HD. UPLO2 will create the file for the Assistant, UPLO2 comes after the UPDAT. You could try lots of TSN; just after you've started the Assistant upload to see what's happening, or use STA-LOGBK. STA-HISTA:SEARCH; will show if the ADP is restarting. Search on it's own gives 2 hours of logs so make sure you've tried it in the last two hours. Maybe UPLO2 is failing to write to DMS area, may need an init...or there's some DB corruption causing a soft in the ADP, or an Assistant HF may help, or a soft restart on BP to clear out some rubbish... I'd start with hista.

 

[synstsia]

The version info is: Assistant V4 (RMX V4 R1.6.24 / UW7 V4 R2.0.16). Our Siemens contract ended some time ago, so I am not familiar with how to keep it up to date.. have mostly just been able to figure things out as I go. The output of the history log right after I start the assistant upload is below. (I've also run act-dssm:a1,1 I have highlighted a DBSYNC error, but I'm not sure what to do about it or if thats the cause. (Any help is greatly appreciated)



F2204 M4 N1038 NO ACT BPA PROC INT INFO TEMPORARY SUSY 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
FORMAT:17 MESSAGE-ID: 00084
:AMO:UPLOL/C????????????????????
2C4C0095 45C40F57 D8F0074D D3B05BE8 2D440003 A20418E7 48F42ED2 46AC06FD
7D1405D8 FD000361 48AC0021 3D9403B5 33D404A0 455C1940 46440045 497C06B7

F2204 M4 N1039 NO ACT BPA PROC INT INFO TEMPORARY SUSY 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
FORMAT:17 MESSAGE-ID: 00084
:AMO:UPLOL/C????????????????????
437C0209 FDD80D0A D4B01250 3D50139C 32B402A7 45BC1849 44AC0023 FB4005B5
4364062B 49E40007 46C40B12 4B4C013D 318C002B 42DC06C4 41040181 FD400252

F2204 M4 N1040 NO ACT BPA PROC INT INFO TEMPORARY SUSY 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
FORMAT:17 MESSAGE-ID: 00084
:AMO:UPLOL/C????????????????????
FD80009F 48E408C6 48DC01D2

F2201 M4 N1041 NO ACT BPA PROC INT STACK 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
CC:00000 EC:00000 UA:A300:5BA2 SP:620C:4954 BP:495A LD:00-00-000-000
FORMAT:45 MESSAGE-ID: 00084
STACK-DATA-MESSAGE 01 OF 03
---4---6 ---8---A ---C---E ---0---2 ---4---6 ---8---A ---C---E ---0---2
A248587A 000049C8 000002B4 D4B04971 620C0800 4AA8620C 00004AA4 00001600
39002D30 50585352 20202020 20202020 02200000 00012020 20202020 F01A7528
20202020 EFBE7528 00180100 000149CC 000049B6 18A1A280 49CE620C 0001022E
022E49D2 D4BAA300 49CE620C 00010000 03090000 4B081220 03090000 000A4AC8
620C0000 49F2620C 00004AA4 0F0007FF 00004AA4 00004AA4 02640019 0019040A
07000504 01040309 4C045445 44450D3B 200A2020 024F5054 54554F20 20464D44

F2201 M4 N1042 NO ACT BPA PROC INT STACK 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
CC:00000 EC:00000 UA:A300:5BA2 SP:620C:4A14 BP:495A LD:00-00-000-000
FORMAT:45 MESSAGE-ID: 00084
STACK-DATA-MESSAGE 02 OF 03
---4---6 ---8---A ---C---E ---0---2 ---4---6 ---8---A ---C---E ---0---2
20534552 0E4C4853 53414948 50205245 41534455 53204957 43544948 474E0101
494E2054 36282933 0A0D5845 43454320 4D4F4C50 54454445 0D3B080A B4BC353A
43374E4F 49465547 45522E44 5020454C 03200800 00000600 0605002A BC083AB4
36354953 474E0D3A 200A2020 20204441 20440003 00080000 04062A05 0000F15C
3737382C 302C222C 4C432049 554E424D 52450320 08000000 06000522 002AF400
40C73040 30313030 41344550 55533130 32302031 30343437 34353931 34335858

F2201 M4 N1043 NO ACT BPA PROC INT STACK 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
CC:00000 EC:00000 UA:A300:5BA2 SP:620C:4AD4 BP:495A LD:00-00-000-000
FORMAT:45 MESSAGE-ID: 00084
STACK-DATA-MESSAGE 03 OF 03
---4---6 ---8---A ---C---E ---0---2 ---4---6 ---8---A ---C---E ---0---2
58585858 58585858 58580058 00000000 00000000 03090001 00000019 00010007
03090000 07FF010A 000A0101 00011000 0F000101 4B180119 FD400000 4AA40000
4AA44B26 4B26008A 48E40000 4AA40000 4AA44B30 016C48DC 00004AA4 4B3800BE
00004AA4 4B460000 01180000 4AA40000 4AA40000 FFFF2E68 00F048DC

F2203 M4 N1044 NO ACT BPA PROC INT TASK ADDRESS 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
FORMAT:17 MESSAGE-ID: 00084
TASKADDRESS 48DC:00F0

F2218 M4 N1045 SOFTREST BPA PROC INT GENERAL PROTECTION 17-01-11 07:50:32
ALARM CLASS:CENTRAL:005
INTERRUPT:0D AX:587A BX:0000 CX:0025 DX:0000 BP:495A SI:587A DI:4971
CS:A300 IP:5BA2 CSLIM:EC81 CSAR:9B SS:620C SP:4954 SSLIM:4B4F SSAR:93
DS:0000 DSLIM:4B4F DSAR:4B ES:620C ESLIM:4B4F ESAR:93 NMI REG:0000
FLAG:00000202 ERR_CODE:0000 LDT:0820 TASK:0690 TASK_BACK_LINK:0000
FORMAT:2B MESSAGE-ID: 00084

F4706 M4 N1046 SR CC BPA DEP RESTART LEVEL 17-01-11 07:50:38
ALARM CLASS:CENTRAL:005
RESTART TYPES: SOFT RESTART

FORMAT:41

[highlight #FCE94F]F6701 M4 N1047 NO ACT BPA DBSYNC ERROR 17-01-11 07:50:39
ALARM CLASS:CENTRAL:023
FORMAT:17
SYBSYNC/LOGBUCH06822: ACCESS ERROR (FAM/DMS ERROR CODE = 0003F)

F6701 M4 N1048 NO ACT BPA DBSYNC ERROR 17-01-11 07:50:39
ALARM CLASS:CENTRAL:023
FORMAT:17
ERROR OCCURED DURING TASK INIT OF DBSYNC

F6700 M4 N1049 NO ACT BPA DBSYNC MESSAGE 17-01-11 07:50:39
ALARM CLASS:CENTRAL:023
FORMAT:17
DBSYNC TERMINATED[/highlight]

F4604 M4 N1050 NO ACT BPA DB MAINTENANCE 17-01-11 07:50:39
ALARM CLASS:CENTRAL:029
FORMAT:33
AUTO TRACER: BUFFER 00058 STORED ON HD. RESTART TIME: 07:50:35

F8281 M4 N1051 NO ACT BPA TRANSSYS ETH LS LINK DOWN 17-01-11 07:50:39
ALARM CLASS:CENTRAL:017
PARTNER:-- IP-ADDR:-- TCP-PORT:--
LOCAL: IP-ADDR:-- TCP-PORT:--
P101: :CC A :002: Q2311-X300 DSCXL BST:12 FW: H062-N
FORMAT:3C
SUB-MSG-NO:1
E3171827440865000F9B04210100001F ...'D.e....!....
3F000000000000000000000000A101A1 ?...............
0100003F003F0000000000010019002A ...?.?.........*
01EC1F20274C69950A00000000000000 ... 'Li.........
EA0800068559B70200C0000203080022 .....Y........."
002200000000002A000000504F52543A .".....*...PORT:
495044412D4C414E2020204D2F493A20 IPDA-LAN M/I:
001AE81A4798AC10640B002B00310000 ....G...d..+.1..
0000 ..

F4385 M4 N1052 NO ACT BPA REC END CC SOFT RESTART 17-01-11 07:50:39
ALARM CLASS:CENTRAL:024
FORMAT:0

F5572 M4 N1053 NO ACT BPA CLOCK CLOCK SYNC 17-01-11 07:50:39
ALARM CLASS:CENTRAL:019
** :LTG1 :LTU1 :003: 00 : 0 Q2216-X DIU2U-M BST:01 PLS:-06
FORMAT:22
00000000FFFFFFFFFFFFFFFFFFFFFFFF 04000700010000000000010000010002
00000400010000FC08030000140202FF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF

A9012 M4 N1054 NO ACT A1 NMCALARM PER-MIRR: CENTRAL GRP 17-01-11 07:50:39
DEVICE ALARM: 0000000000000000
MINOR ALARM: 0000000000000000
MAJOR ALARM: 0000000000000000
FORMAT:30

A9015 M4 N1055 NO ACT A1 NMCALARM PER-MIRR: SMPER GRP 17-01-11 07:50:39
DEVICE ALARM: 000000
MINOR ALARM: 000000
MAJOR ALARM: 000000
FORMAT:30

F7662 M4 N1056 NO ACT A1 LCX-CHAN DONGLE/SIM ATTACHED 17-01-11 07:50:35
ALARM CLASS:SM-PER: 000
CHAN NO:00 CHAN TYPE:NO CHAN TYPE CHAN SI:NO SERV
FORMAT:10
5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A 5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A
5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A 5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A
5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A 5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A
5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A 5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A
5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A 5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A5A
5A

F8258 M4 N1057 NO ACT A1 TRANSSYS ETH LINK AGAIN 17-01-11 07:50:36
ALARM CLASS:CENTRAL:017
PARTNER:-- IP-ADDR:-- TCP-PORT:--
LOCAL: IP-ADDR:-- TCP-PORT:--
** : :A1 B :001: Q2311-X300 DSCXL BST:12 FW: H062-N
FORMAT:3C
SUB-MSG-NO:1
9E171827310865000F9B04200100001F ...'1.e.... ....
3F000000000000000000000000A101A1 ?...............
0100000100010000000000010001002A ...............*
01EC1F20274C69950A00000000000000 ... 'Li.........
DAFFFFFFFFFFFF0200C0000203080600 ................
0000000000000000000000504F52543A ...........PORT:
52544D2D424F41524420204D2F493A20 RTM-BOARD M/I:
0200C0000203C0000203003B00310000 ...........;.1..
0000 ..

F6506 M4 N1058 SOFTREST A1 SM-DEP RESTART LEVEL 17-01-11 07:50:36
ALARM CLASS:CENTRAL:005
RESTART TYPES: SOFT RESTART

FORMAT:41

F2102 M4 N1059 NO ACT A1 IX UNIX MESSAGE 17-01-11 07:50:39
ALARM CLASS:CENTRAL:027
UNIX NAME: UNIX TIME:-------- --:--:-- RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
FORMAT:3A
IX-TASK: Saving UNIX diagnosis information under BDA:UNIX/...

F5130 M4 N1060 NO ACT BPA SM/UNIT ON-LINE 17-01-11 07:50:40
ALARM CLASS:CENTRAL:026
SLOT TYPEP-SM ERROR LOCATION:A1
FORMAT:29

F2102 M4 N1061 NO ACT A1 IX UNIX MESSAGE 17-01-11 07:50:42
ALARM CLASS:CENTRAL:027
UNIX NAME: UNIX TIME:-------- --:--:-- RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
FORMAT:3A
IX-TASK: UNIX mem sufficient Avail. RAM: 838 MB
Required minimum: 56 MB

F2102 M4 N1062 NO ACT A1 IX UNIX MESSAGE 17-01-11 07:50:42
ALARM CLASS:CENTRAL:027
UNIX NAME: UNIX TIME:-------- --:--:-- RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
FORMAT:3A
LD-TASK: IX-BIOS initialized

A9008 M4 N1063 NO ACT BPA NMCALARM MIRROR: CENTRAL GRP 17-01-11 07:50:43
DEVICE ALARM: 0000000000000000
MINOR ALARM: 0000000000000000
MAJOR ALARM: 0000000000000000
FORMAT:30

A9009 M4 N1064 NO ACT BPA NMCALARM MIRROR: SWUPER GRP 17-01-11 07:50:43
DEVICE ALARM: 00000000
MINOR ALARM: 00000000
MAJOR ALARM: 02000000
FORMAT:30

A9010 M4 N1065 NO ACT BPA NMCALARM MIRROR: SWULOG GRP 17-01-11 07:50:43
DEVICE ALARM: 000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000
MINOR ALARM: 000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000
MAJOR ALARM: 000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000
FORMAT:30

F2102 M4 N1066 NO ACT A1 IX UNIX MESSAGE 17-01-11 07:50:44
ALARM CLASS:CENTRAL:027
UNIX NAME: UNIX TIME:-------- --:--:-- RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
FORMAT:3A
LD-TASK: IX-BIOS started

F4387 M4 N1067 NO ACT BPA REC END CC SR CLEAN-UP 17-01-11 07:50:45
ALARM CLASS:CENTRAL:024
FORMAT:0

F2102 M4 N1068 NO ACT A1 IX UNIX MESSAGE 17-01-11 07:50:48
ALARM CLASS:CENTRAL:027
UNIX NAME: UNIX TIME:-------- --:--:-- RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
FORMAT:3A
LD-TASK: BASE system loaded and started

F8261 M4 N1069 NO ACT A1 TRANSSYS TCP SUSY ERROR INFO 17-01-11 07:51:19
ALARM CLASS:CENTRAL:023
FORMAT:3B
SUB-MSG-NO:1 ADDR:2668:1441 MODULE:RX_IP_READY
00003B01000000000000411468266A06 58139C060050C0000203FFFFFFFFFFFF
FFFF00000000FFFFFFFF00000000FFFF FFFF00000000FFFFFFFF00000000FFFF
FFFF00000000FFFFFFFF00000000FFFF FFFF0000000000C00B3E000000010000
000000000000

A9000 M4 N1070 NO ACT BPA NMCALARM MINOR ALARM ON 17-01-11 07:51:45
ALARM CLASS:CENTRAL:005
ALARM NAME:CC RESTARTS
FORMAT:2C

F2102 M4 N1071 NO ACT A1 IX UNIX MESSAGE 17-01-11 07:52:22
ALARM CLASS:CENTRAL:027
UNIX NAME: UNIX TIME:-------- --:--:-- RESTART COUNT:0
-- :-- :-- :000: -- -- BST:-- FW: --
FORMAT:3A
CT-TASK: BASE system running

 

[synstsia]

For reference, the output of ACT-DSSM:A1,1; & DIS-DDSM; are below:


H500: AMO DSSM STARTED
H04: AREA <:A1H1E:> ALREADY ACTIVATED
H04: AREA <:A1H1F:> ALREADY ACTIVATED
H04: AREA <:A1H1G:> ALREADY ACTIVATED
H04: AREA <:A1H1H:> ALREADY ACTIVATED
H04: AREA <:A1H1I:> ALREADY ACTIVATED
H04: AREA <:A1H1J:> ALREADY ACTIVATED
H04: AREA <:A1H1K:> ALREADY ACTIVATED

AMO-DSSM -111 DISK SWITCHOVER
ACTIVATE COMPLETED;

H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE, LOAD AREA IS: DS:
TYPE: HD SS-NO : <STDH4> SIZE : 3346 MB ( 53550*64KB) GRAN : 512
NON-RMX PARTITIONS:
SYSTEM ID SYSTEM NAME BEGIN / NO OF SECTOR(S) SIZE
H'12 UNIXWARE H' 68ABEB H' 139C5 39 MB ( 627*64KB)
H'63 UNIXWARE H' 69E5B0 H' 633F7CE 50814 MB ( 813039*64KB)
H'63 UNIXWARE H' 69DDD7E H' 5DE2BF 3004 MB ( 48069*64KB)
AREA: A NAME : A1H1A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
ACTIVATED LOGICAL NAMES:
DS:
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
ACTIVATED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
ACTIVATED LOGICAL NAMES:
:CGD:
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
ACTIVATED LOGICAL NAMES:
MS:,SY:
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:SCR:
ACTIVATED LOGICAL NAMES:
:SCR:
AREA-SZ: 2047 MB (32767*64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:GLA:
ACTIVATED LOGICAL NAMES:
:GLA:
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
IAG:
ACTIVATED LOGICAL NAMES:
IAG:
AREA-SZ: 616 MB (9868 *64KB) A-GRAN: 4096
CONTROLLER: 6
TYPE: HD SS-NO : <CF1G3> SIZE : 1183 MB ( 18932*64KB) GRAN : 512
AREA: A NAME : A1H6A STATUS : B L O C K E D B Y A M O
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H6E STATUS : B L O C K E D B Y A M O
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H6F STATUS : B L O C K E D B Y A M O
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H6G STATUS : B L O C K E D B Y A M O
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 50 MB (800 *64KB) A-GRAN: 4096
AREA: H NAME : A1H6H STATUS : B L O C K E D B Y A M O
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H6I STATUS : B L O C K E D B Y A M O
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:MOD-SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 801 MB (12817*64KB) A-GRAN: 4096

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;

 

[Moriendi]

When you start the upload are you starting the LCR upload as well ?

What happens if you do a normal system upload but not the LCR?

If the ADP makes another soft post the hista again.

 

[synstsia]

I don't think I have the option (at least from by version of Assistant) to choose the upload- it usually does an 'upload all' by default from the Action menu. I've started the upload and monitored with multiple TSN; commands and can see that it moves on to UPLOL before it crashes..

I've also managed to find the following error log while tooling through the shell in /opt/cm/sad/ERROR/DBSynchronization.noterm.err but not sure what to make of it:

*** Unable to build message 894 ***, Error: No such file or directory, File:
/cm/dms/src/cm/dbsynch/uxsutilx.C, Line: 348
00870 11.01.2017 00:04:41 norig noterm DBSynchronization /cm/dms/src/cm/dbs$
*** Unable to build message 870 ***, Error: No such file or directory, File:
/cm/dms/src/cm/dbsynch/uxsutilx.C, Line: 348
00870 11.01.2017 00:04:41 norig noterm DBSynchronization /cm/dms/src/cm/dbs$
*** Unable to build message 870 ***, Error: No such file or directory, File:
/cm/dms/src/cm/dbsynch/uxsutilx.C, Line: 348
00870 11.01.2017 00:04:41 norig noterm DBSynchronization /cm/dms/src/cm/dbs$
*** Unable to build message 870 ***, Error: No such file or directory, File:
/cm/dms/src/cm/dbsynch/uxsutilx.C, Line: 348

 

[Moriendi]

On the System page, where you make Action/Upload, are you able to untick something about "System supports LCR"? Try to untick it and then click "Save". I can't remember if V4 lets you change that. If it does, it won't stop LCR working, it'll stop CM uploading LCR data. Or it will tell you you can't change that.

So the UPLOL is crashing the ADP for some reason. It might be a problem creating the files but the proc int stack occurs before the DBSYNC error so maybe not.

There are three things I would try.

1 - Make an init of the dms/dsy area, area H.
Deactivate area H only with DEA-DSSM:A1,1,H;
Init it with STA-INIT:A1,A1H1H;
Activate with ACT-DSSM:A1,1;
Then try again

2 - Make a soft restart of the SWU with EXEC-REST:UNIT,BP,SOFT;
If you have a dual processor it will switch the processors over, if not it can cause loss of dialtone for a few seconds. Any attendant consoles you have will drop connection and reconnect. The 4K may escalate it to a hard restart where everything will go off and the cards will reload. Unlikely but be warned it may happen. If you have a dual processor do it anytime, if it's mono processor you could wait until after hours.

3 - If the problem is still there, maybe you need a new version of the UPLOL AMO but without a maintenance contract you're going to struggle to get it, unless someone with a V4 can send them to you. Check with STA-LIST:"DS:APSN/S/UPLOL/",,100,B,N; You are V4 R1 which was old... UPLOL is sure to have been replaced by something newer than what you have.

 

[synstsia]

It doesn't let me untick the LCR option. I tried the sequence you suggested, but still crashes- I confirmed that it switches to UPLOL right before the crash. I think whats most puzzling is that uploads were working fine right before the holidays, then this problem started suddenly. Do you know if I'm able to run the UPLOL from expert and tell it not to do the LCR data? I can't figure out from the macro command how to do that or if I'd screw anything up


<TSN;
TSN | NOUN | LOG DEV | TIME | USER
------+-------+---------+----------+----------
2788 STTAB TASK 07 09 16
2789 TASK 07 09 16
2819 FBT * 07 27 22 ENGR1
2806 FBT * 07 18 18 SYSTEM
2804 UPLOL FBT * 07 18 15 SYSTEM

 

[Moriendi]

Had another look at the hista on a screen instead of a phone - it's the SWU that is restarting anyway, not the ADP. But either way it's UPLOL causing it.

You can't tell UPLOL not to upload the LCR, UPLOL is solely for the LCR data. UPLO2 does everything else.

What's the version of the UPLOL AMO - run that sta-list command. You can replace the AMO on the hard disc the same as you replace any file - just overwrite it with a newer version. If you are V4 R1 there will surely be a newer one.

If there's some DB corruption it'll need a DB retype.

 

[donb01]

Is it possible that one of the partitions/volumes/areas is filling up with logs or something and running out of disk space?


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[Moriendi]

No - nothing good ever happens after a proc int stack. The UPLOL takes the RMX DB and puts it into a delimited format on the DMS area. When finished that file is then transferred to the Assistant and used to build the informix DB for CM.

The UPLOL is causing a proc int stack which causes a soft restart which stops the AMO working, so the DMS file is never created and Assistant doesn't see it (or it gets a messed up version, doesn't matter either way). There is something in the LCR config that is causing a problem for UPLOL. It could be corruption, which you could maybe test for by seeing if everything regens OK, or it's a bug in the AMO which as V4 is M44, you'd just have to hope it's fixed in a newer AMO. Software is V4 R1 so there's a chance it's fixed.

He needs to replace the AMO as the next step. If the fault was still there a GENDB would probably help.

 

[synstsia]

Found the problem finally, so I wanted to thank you for the help Moriendi. Since you helped me pinpoint that it was an LCR issue, I dug deeper and there was an errant CLIMA table entry that had a CLI number with an ascii character.. deleted the entire entry and reran Uplol with success.. at some point I guess this must have gotten corrupted. One thing is for certain, the hipath 4000 is the most proprietary system I've ever dealt with.

 

[Moriendi]

Well done! Not an easy thing to find. Impossible to say what would have caused that but corruption does happen sometimes. There's probably a newer CLIMA version than you have, you have an early V4 version and I think CLIMA itself was new in V4, I don't think it was in V3 so you'll have an early edition of the AMO. I don't think a new UPLOL would have solved the problem, a GENDB would. Much easier if you found the AMO responsible.