8.0 Upgrade Fails (OpenInsight 32-Bit)
At 14 MAY 2009 05:16:22PM Barbara F Evans wrote:
I've been trying to upgrade one of my clients OI 7.2.1 to 8.0 (and, potentially, further to 8.08), but get the message 'Startup failed to open system files'. This is followed by the 'OpenInsight boot up failed' message. I tried 7.2.1 upgrade to 8.0. When it failed, I tried incremental upgrades of 7.2.2, 7.3, 8.0, but same results.
The following is found in the upgrade log:
Upgrade Log
Started: 13:26:06 14 MAY 2009
Create table failed in line 7
Create table failed in line 8
Create table failed in line 9
Create table failed in line 10
Create table failed in line 15
Error (100) deleting row "DICT.MFS" in line 18
Error (100) deleting row "UPDATE_INDEX" in line 19
Error (100) deleting row "T_RJC" in line 20
Error (100) deleting row "CACHE_MFS" in line 21
Error (100) deleting row "CACHE_MFS_COMMON" in line 22
Error (100) deleting row "GET_BFS_INFO" in line 23
Error (100) deleting row "MAPDICT_CONVCORR" in line 24
Error (100) deleting row "U2_BFS" in line 27
Error (100) deleting row "U2_BFS_GET_SERVER_DBS" in line 28
Error (100) deleting row "U2_BFS_GET_SERVER_NAMES" in line 29
Error (100) deleting row "U2_BOND_SUBS" in line 30
Error (100) deleting row "U2_BOND_VOLUMEINFO_SUB" in line 31
Error (100) deleting row "U2_BTREE_EXTRACT" in line 32
Error (100) deleting row "U2_CONNECTION_INFO" in line 33
Error (100) deleting row "U2_CONV" in line 34
Error (100) deleting row "U2_CONVERT_OI_TO_U2" in line 35
Error (100) deleting row "U2_DEFINE_VOLUME_INFO" in line 36
Error (100) deleting row "U2_DICTIONARY_CONVERTER_EVENTS" in line 37
Error (100) deleting row "U2_ERROR" in line 38
Error (100) deleting row "U2_EXAMPLE" in line 39
Error (100) deleting row "U2_EXECITYPE" in line 40
Error (100) deleting row "U2_EXECPROC" in line 41
Error (100) deleting row "U2_GET_SERVERTYPE" in line 42
Error (100) deleting row "U2_GET_SERVER_FILENAME" in line 43
Error (100) deleting row "U2_ICONV" in line 44
Error (100) deleting row "U2_MAPDICT" in line 45
Error (100) deleting row "U2_MAPDICT_FROM_OI" in line 46
Error (100) deleting row "U2_MAP_V_CORRELATIVE" in line 47
Error (100) deleting row "U2_MEDIA" in line 48
Error (100) deleting row "U2_OCONV" in line 49
Error (100) deleting row "U2_PROFILE" in line 50
Error (100) deleting row "U2_REFRESH_SHADOW" in line 51
Error (100) deleting row "U2_REGISTEROM" in line 52
Error (100) deleting row "U2_SELECT" in line 53
Error (100) deleting row "U2_SETTRACE" in line 54
Error (100) deleting row "U2_SUBCALL" in line 55
Error (100) deleting row "U2_SYNCMAP" in line 57
Error (100) deleting row "U2_UD_SUBR" in line 58
Error (100) deleting row "SYSPROGBRW_GROUPING" in line 59 Error (100) deleting row "SYSPROGBRW_IMAGE_DET" in line 60
Error (100) deleting row "SYSPROG**BRW_LABEL_DET" in line 61
Error (125) writing upgrade row "SYSTEMTABLE" in line 78
Error (145) opening the "MD" file in line 79
Error (145) opening the "MD" file in line 80
Error (145) opening the "MD" file in line 81
Error (145) opening the "MD" file in line 82
Error (145) opening the "MD" file in line 83
Error (145) opening the "MD" file in line 84
Error (145) opening the "MD" file in line 85
Error (145) opening the "MD" file in line 86
Error (145) opening the "MD" file in line 87
Error (145) opening the "MD" file in line 88
Error (145) opening the "MD" file in line 89
Error (145) opening the "MD" file in line 90
Error (145) opening the "MD" file in line 91
Error (145) opening the "MD" file in line 92
Error (145) opening the "MD" file in line 93
Error (145) opening the "MD" file in line 94
Error (145) opening the "MD" file in line 95
Error (145) opening the "MD" file in line 96
Error (145) opening the "MD" file in line 97
Error (145) opening the "MD" file in line 98
Error (145) opening the "MD" file in line 99
Error (145) opening the "MD" file in line 100
Error (145) opening the "MD" file in line 101
Error (145) opening the "MD" file in line 102
Error (145) opening the "MD" file in line 103
Error (145) opening the "MD" file in line 104
Error (145) opening the "MD" file in line 105
Error (145) opening the "MD" file in line 106
Error (145) opening the "MD" file in line 107
Error (145) opening the "MD" file in line 108
Error (145) opening the "MD" file in line 109
Error (145) opening the "MD" file in line 110
Error (145) opening the "MD" file in line 111
Error (145) opening the "MD" file in line 112
Error (145) opening the "MD" file in line 113
Error (145) opening the "MD" file in line 114
Error (145) opening the "MD" file in line 115
Error (145) opening the "MD" file in line 116
Error (145) opening the "MD" file in line 117
Error (145) opening the "MD" file in line 118
Error (145) opening the "MD" file in line 119
Error (145) opening the "MD" file in line 120
Error (145) opening the "MD" file in line 121
Error (145) opening the "MD" file in line 122
Error (145) opening the "MD" file in line 123
Error (145) opening the "MD" file in line 124
Error (145) opening the "MD" file in line 125
Error (145) opening the "MD" file in line 126
Error (145) opening the "MD" file in line 127
Error (145) opening the "MD" file in line 128
Error (145) opening the "MD" file in line 129
Error (145) opening the "MD" file in line 130
Error (145) opening the "MD" file in line 131
Error (145) opening the "MD" file in line 132
Error (145) opening the "MD" file in line 133
Error (145) opening the "MD" file in line 134
Error (145) opening the "MD" file in line 135
Error (145) opening the "MD" file in line 136
Error (145) opening the "MD" file in line 137
Error (145) opening the "MD" file in line 138
Error (145) opening the "MD" file in line 139
Error (145) opening the "MD" file in line 140
Error (145) opening the "MD" file in line 141
Error (145) opening the "MD" file in line 142
Error (145) opening the "MD" file in line 143
Error (145) opening the "MD" file in line 144
Error (145) opening the "MD" file in line 145
Error (145) opening the "MD" file in line 146
Error (145) opening the "MD" file in line 147
Error (145) opening the "MD" file in line 148
Error (145) opening the "MD" file in line 149
Error (401) opening the "SYSPRINTERS" file in line 1458
Error (401) opening the "SYSPRINTERS" file in line 1459
Finished: 13:26:11 14 MAY 2009
Can anyone suggest reasons for the upgrade failure?
Thanks for any input.
Barb
At 18 MAY 2009 06:04PM Bob Carten wrote:
Hi Barbara,
It looks like OI is not able to create the MD table in the revboot folder, and or the files in the AREV_DIR. Does the install work if you copy the system to a local drive?
At 19 MAY 2009 08:05PM Barry Stevens wrote:
You didnt copy the server system to a C drive did you and still have the revparam file(s) set to serveronly=1
At 21 MAY 2009 03:55PM Barbara F Evans wrote:
I finally figured out the problem trying the upgrades on my local machine. They failed as well. But in trying to determine what might be the problem of my MD table, you sent me in the right direction.
It turns out I had a bad revmedia file in the OI root directory. I found this by trying to list the revboot volume and got a message about a group # and linkage/frame error. When I tried the same with a refreshed revmedia from a backup, the listvolume showed me all the files. After the restore, the upgrades went in with no problem.
Thanks for all responses.