SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-19-2008, 07:51 PM
| ||||
| ||||
 Reversion from IDS 9.40 to 9.21 fails HP-UX 11.11 IDS 9.20 FC4 to IDS 9.40 FC2 We are testing the above upgrade. On three of the four databases to be converted we have had no problems in the conversion process (we did encounter a bug with slow index builds, a known problem kindly identified by Jonathan Leffler due to be fixed in 9.40 FC3). On the fourth, it also converts OK but sporadically - perhaps 2 times in 10 - the reversion back from 9.40 (level 0) to 9.21 will fail. This is an *absolute* show-stopper for this client. The database in question is mission-critical, and is 500GBytes in size, so dbexport/dbimport, or a restore, is not viable. A call has been raised with Tech Support (389466). Because this is not a "down" system we will have to work hard to ensure that it receives a prioroty that refelects the imprtance of the issue to the client. Any insight gratefully received. I attach the online log from the reversion process and the subsequent attempt to bring the server back online. thanks Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com ==================================== 11:37:18 Maximum server connections 0 11:37:18 Update reserved page status of conversion 11:37:18 Quiescent Mode 11:37:18 Succeeded 11:37:19 Checkpoint Completed: duration was 0 seconds. 11:37:19 Checkpoint loguniq 112336, logpos 0x28ac018, timestamp: 761991795 11:37:19 Maximum server connections 0 11:37:19 Internal Conversion Completed Successfuly 11:37:19 Conversion Enabling Client Connections 11:37:19 Building 'sysmaster' database ... 11:37:20 On-Line Mode 11:37:24 Booting Language <spl> from module <> 11:05:03 Maximum server connections 3 11:08:53 Shutdown Mode 11:08:54 Quiescent Mode 11:08:55 Checkpoint Completed: duration was 0 seconds. 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 11:08:55 Maximum server connections 3 11:08:56 Reversion to version 9.2 Started 11:08:56 Beginning process of reverting system to 9.2 ... 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be truncated from decimal value 4.000 to integer value 4. Please check onconfig parameter value before reinitializing the Server. 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be truncated from decimal value 2.000 to integer value 2. Please check onconfig parameter value before reinitializing the Server. 11:08:58 Booting Language <spl> from module <> 11:08:58 Loading Module <SPLNULL> 11:08:58 On-Line Mode 11:08:58 ON-Bar reversion test start: 11:08:58 ON-Bar reversion test completed successfully. 11:08:58 'onpload' reversion test start: 11:08:59 'onpload' reversion test completed successfully. 11:09:00 Reversion test for R-tree indexes started 11:09:01 Reversion test for R-tree indexes completed successfully 11:09:02 PAM reversion test completed successfully. 11:09:06 Quiescent Mode 11:09:10 Checking database trade for revertibility ... 11:09:11 Database trade is revertible ... 11:09:12 Checking database bo_repositoryo for revertibility ... 11:09:13 Database bo_repositoryo is revertible ... 11:09:14 Checking database bo_docagento for revertibility ... 11:09:15 Database bo_docagento is revertible ... 11:09:16 Checking database onpload for revertibility ... 11:09:17 Database onpload is revertible ... 11:09:18 Checking database startup for revertibility ... 11:09:20 Database startup is revertible ... 11:09:20 Checking database stores7 for revertibility ... 11:09:21 Database stores7 is revertible ... 11:09:22 Checking database dba for revertibility ... 11:09:23 Database dba is revertible ... 11:09:24 Checking database cats for revertibility ... 11:09:26 Database cats is revertible ... 11:09:26 Checking database live for revertibility ... 11:09:30 Database live is revertible ... 11:09:30 Checking database londis_syn for revertibility ... 11:09:32 Database londis_syn is revertible ... 11:09:32 Checking database londis_vw for revertibility ... 11:09:35 Database londis_vw is revertible ... 11:09:36 Checking database live_dummy for revertibility ... 11:09:40 Database live_dummy is revertible ... 11:09:41 On-Line Mode 11:09:41 ON-Bar reversion start: 11:09:41 WARNING:Target server version must have a certified Storage Manager installed after conversion/reversion and before bringing up server. 11:09:41 ON-Bar reversion completed successfully. 11:09:42 ... reverting 'onpload' database. 11:09:42 ... 'onpload' reversion completed successfully. 11:09:42 PAM reversion completed successfully. 11:09:46 ... dropping 'sysmaster' database "crap.txt" 181 lines, 9064 characters $ wc crap* 181 1145 9064 crap.txt $ cat crap.txt 11:05:03 Maximum server connections 3 11:08:53 Shutdown Mode 11:08:54 Quiescent Mode 11:08:55 Checkpoint Completed: duration was 0 seconds. 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 11:08:55 Maximum server connections 3 11:08:56 Reversion to version 9.2 Started 11:08:56 Beginning process of reverting system to 9.2 ... 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be truncated from decimal value 4.000 to integer value 4. Please check onconfig parameter value before reinitializing the Server. 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be truncated from decimal value 2.000 to integer value 2. Please check onconfig parameter value before reinitializing the Server. 11:08:58 Booting Language <spl> from module <> 11:08:58 Loading Module <SPLNULL> 11:08:58 On-Line Mode 11:08:58 ON-Bar reversion test start: 11:08:58 ON-Bar reversion test completed successfully. 11:08:58 'onpload' reversion test start: 11:08:59 'onpload' reversion test completed successfully. 11:09:00 Reversion test for R-tree indexes started 11:09:01 Reversion test for R-tree indexes completed successfully 11:09:02 PAM reversion test completed successfully. 11:09:06 Quiescent Mode 11:09:10 Checking database trade for revertibility ... 11:09:11 Database trade is revertible ... 11:09:12 Checking database bo_repositoryo for revertibility ... 11:09:13 Database bo_repositoryo is revertible ... 11:09:14 Checking database bo_docagento for revertibility ... 11:09:15 Database bo_docagento is revertible ... 11:09:16 Checking database onpload for revertibility ... 11:09:17 Database onpload is revertible ... 11:09:18 Checking database startup for revertibility ... 11:09:20 Database startup is revertible ... 11:09:20 Checking database stores7 for revertibility ... 11:09:21 Database stores7 is revertible ... 11:09:22 Checking database dba for revertibility ... 11:09:23 Database dba is revertible ... 11:09:24 Checking database cats for revertibility ... 11:09:26 Database cats is revertible ... 11:09:26 Checking database live for revertibility ... 11:09:30 Database live is revertible ... 11:09:30 Checking database londis_syn for revertibility ... 11:09:32 Database londis_syn is revertible ... 11:09:32 Checking database londis_vw for revertibility ... 11:09:35 Database londis_vw is revertible ... 11:09:36 Checking database live_dummy for revertibility ... 11:09:40 Database live_dummy is revertible ... 11:09:41 On-Line Mode 11:09:41 ON-Bar reversion start: 11:09:41 WARNING:Target server version must have a certified Storage Manager installed after conversion/reversion and before bringing up server. 11:09:41 ON-Bar reversion completed successfully. 11:09:42 ... reverting 'onpload' database. 11:09:42 ... 'onpload' reversion completed successfully. 11:09:42 PAM reversion completed successfully. 11:09:46 ... dropping 'sysmaster' database 11:09:47 Quiescent Mode 11:09:47 Revert system catalogs for 9.2 11:09:47 Starting reversion of database trade ... 11:09:48 Database trade SUCCESSFULLY reverted ... 11:09:49 Starting reversion of database bo_repositoryo ... 11:09:50 Database bo_repositoryo SUCCESSFULLY reverted ... 11:09:51 Starting reversion of database bo_docagento ... 11:09:52 Database bo_docagento SUCCESSFULLY reverted ... 11:09:53 Starting reversion of database onpload ... 11:09:54 Database onpload SUCCESSFULLY reverted ... 11:09:55 Starting reversion of database startup ... 11:09:56 Database startup SUCCESSFULLY reverted ... 11:09:57 Starting reversion of database stores7 ... 11:09:58 Database stores7 SUCCESSFULLY reverted ... 11:09:59 Starting reversion of database dba ... 11:10:00 Database dba SUCCESSFULLY reverted ... 11:10:00 (211) connection rejected - no calls allowed for sqlexec 11:10:00 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 11:10:01 Starting reversion of database cats ... 11:10:01 (212) connection rejected - no calls allowed for sqlexec 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 11:10:01 (213) connection rejected - no calls allowed for sqlexec 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 11:10:01 (214) connection rejected - no calls allowed for sqlexec 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 11:10:02 (215) connection rejected - no calls allowed for sqlexec 11:10:02 listener-thread: err = -27002: oserr = 0: errstr = : No connections are allowed in Dynamic Server quiescent mode. 11:10:02 Database cats SUCCESSFULLY reverted ... 11:10:03 Starting reversion of database live ... 11:10:06 Database live SUCCESSFULLY reverted ... 11:10:07 Starting reversion of database londis_syn ... 11:10:08 Database londis_syn SUCCESSFULLY reverted ... 11:10:09 Starting reversion of database londis_vw ... 11:10:10 Database londis_vw SUCCESSFULLY reverted ... 11:10:11 Starting reversion of database live_dummy ... 11:10:15 Database live_dummy SUCCESSFULLY reverted ... 11:10:18 Checkpoint Completed: duration was 1 seconds. 11:10:18 Checkpoint loguniq 112336, logpos 0x28a93d4, timestamp: 761967468 11:10:18 Maximum server connections 3 11:10:18 Reverting Partition Header Pages Started 11:10:20 Reverting Partition Header Pages Succeeded 11:10:20 Checkpoint Completed: duration was 0 seconds. 11:10:20 Checkpoint loguniq 112336, logpos 0x28aa018, timestamp: 761979583 11:10:20 Maximum server connections 3 11:10:20 Reversion complete. Install INFORMIX-OnLine Version 9.2 before reinitializing OnLine. 11:10:21 Reversion to version 9.2 Succeeded 11:10:23 IBM Informix Dynamic Server Stopped. 11:58:38 Informix Dynamic Server 2000 Started. 11:58:44 Segment locked: addr=0x39bbc000, size=1077215232 Wed Jan 7 11:58:46 2004 11:58:46 Event alarms enabled. ALARMPROG = '/opt/informix/9.21/etc/log_full.sh' 11:58:46 Booting Language <c> from module <> 11:58:46 Loading Module <CNULL> 11:58:46 Booting Language <builtin> from module <> 11:58:46 Loading Module <BUILTINNULL> 11:59:05 Informix Dynamic Server 2000 Version 9.21.FC4 Software Serial Number AAD#J130447 11:59:07 HPUX Version B.11.11 -> Using flag/select style KAIO 11:59:07 HP KAIO concurrent requests changed from 1000 to 2300 11:59:10 Informix Dynamic Server 2000 Initialized -- Shared Memory Initialized. 11:59:10 Physical Recovery Started at Page(2:38285). 11:59:10 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. 11:59:10 Logical Recovery Started. 11:59:10 10 recovery worker threads will be started. 11:59:10 Assert Failed: Dynamic Server 2000 must abort 11:59:10 Informix Dynamic Server 2000 Version 9.21.FC4 11:59:10 Who: Session(14, informix@hamilton, 0, 2047781160) Thread(209, fast_rec, c00000007a0c2028, 1) File: rslog.c Line: 3202 11:59:10 Results: Dynamic Server 2000 must abort 11:59:10 Action: Reinitialize shared memory 11:59:10 stack trace for pid 17358 written to /var/tmp/af.4b9f48e 11:59:10 See Also: /var/tmp/af.4b9f48e 11:59:19 rslog.c, line 3202, thread 209, proc id 17358, Dynamic Server 2000 must abort. 11:59:19 PANIC: Attempting to bring system down 12:05:11 Informix Dynamic Server 2000 Started. 12:05:17 Segment locked: addr=0x39bbc000, size=1077215232 Wed Jan 7 12:05:19 2004 12:05:19 Event alarms enabled. ALARMPROG = '/opt/informix/9.21/etc/log_full.sh' 12:05:19 Booting Language <c> from module <> 12:05:19 Loading Module <CNULL> 12:05:19 Booting Language <builtin> from module <> 12:05:19 Loading Module <BUILTINNULL> 12:05:38 Informix Dynamic Server 2000 Version 9.21.FC4 Software Serial Number AAD#J130447 12:05:39 HPUX Version B.11.11 -> Using flag/select style KAIO 12:05:39 HP KAIO concurrent requests changed from 1000 to 2300 12:05:42 Informix Dynamic Server 2000 Initialized -- Shared Memory Initialized. 12:05:42 Physical Recovery Started at Page(2:38285). 12:05:42 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. 12:05:42 Logical Recovery Started. 12:05:42 10 recovery worker threads will be started. 12:05:42 Assert Failed: Dynamic Server 2000 must abort 12:05:42 Informix Dynamic Server 2000 Version 9.21.FC4 12:05:42 Who: Session(14, informix@hamilton, 0, 2047781160) Thread(209, fast_rec, c00000007a0c2028, 1) File: rslog.c Line: 3202 12:05:42 Results: Dynamic Server 2000 must abort 12:05:42 Action: Reinitialize shared memory 12:05:42 stack trace for pid 17706 written to /var/tmp/af.4b9f615 12:05:42 See Also: /var/tmp/af.4b9f615 12:05:50 rslog.c, line 3202, thread 209, proc id 17706, Dynamic Server 2000 must abort. 12:05:50 PANIC: Attempting to bring system down 11:36:35 IBM Informix Dynamic Server Started. 11:36:41 Segment locked: addr=0xc000000039c49000, size=1080684544      |
|
04-19-2008, 07:51 PM
| |||
| |||
| Re: Reversion from IDS 9.40 to 9.21 fails Neil, On the failure below, I'm not seeing something that I think is rather important. That is, I don't see any evidence of a hard checkpoint (i.e. non-fuzzy) after the reversion has been done. I think that is probably causing the failure because otherwise, the 9.21 server will be trying to process 9.4 log records. I do know that a couple of the log records changed a bit with 9.4 because of some 64-bit alignment issues. You might want it try to issue an onmode -c as part of the reversion process. M.Pruet "Neil Truby" <neil.truby@ardenta.com> wrote in message news:btjhun$7r28c$1@ID-162943.news.uni-berlin.de... > HP-UX 11.11 > IDS 9.20 FC4 to IDS 9.40 FC2 > > We are testing the above upgrade. On three of the four databases to be > converted we have had no problems in the conversion process (we did > encounter a bug with slow index builds, a known problem kindly identified by > Jonathan Leffler due to be fixed in 9.40 FC3). On the fourth, it also > converts OK but sporadically - perhaps 2 times in 10 - the reversion back > from 9.40 (level 0) to 9.21 will fail. This is an *absolute* show-stopper > for this client. The database in question is mission-critical, and is > 500GBytes in size, so dbexport/dbimport, or a restore, is not viable. > > A call has been raised with Tech Support (389466). Because this is not a > "down" system we will have to work hard to ensure that it receives a > prioroty that refelects the imprtance of the issue to the client. > > Any insight gratefully received. I attach the online log from the reversion > process and the subsequent attempt to bring the server back online. > > thanks > Neil Truby t:01932 724027 > Director m:07798 811708 > Ardenta Limited e:neil.truby@ardenta.com > > ==================================== > 11:37:18 Maximum server connections 0 > 11:37:18 Update reserved page status of conversion > 11:37:18 Quiescent Mode > 11:37:18 Succeeded > 11:37:19 Checkpoint Completed: duration was 0 seconds. > 11:37:19 Checkpoint loguniq 112336, logpos 0x28ac018, timestamp: 761991795 > > 11:37:19 Maximum server connections 0 > 11:37:19 Internal Conversion Completed Successfuly > 11:37:19 Conversion Enabling Client Connections > 11:37:19 Building 'sysmaster' database ... > 11:37:20 On-Line Mode > 11:37:24 Booting Language <spl> from module <> > > 11:05:03 Maximum server connections 3 > 11:08:53 Shutdown Mode > 11:08:54 Quiescent Mode > 11:08:55 Checkpoint Completed: duration was 0 seconds. > 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 > > 11:08:55 Maximum server connections 3 > 11:08:56 Reversion to version 9.2 Started > 11:08:56 Beginning process of reverting system to 9.2 ... > 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be > truncated from decimal value 4.000 to integer value 4. > Please check onconfig parameter value before reinitializing the Server. > > 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be > truncated from decimal value 2.000 to integer value 2. > Please check onconfig parameter value before reinitializing the Server. > > 11:08:58 Booting Language <spl> from module <> > 11:08:58 Loading Module <SPLNULL> > 11:08:58 On-Line Mode > 11:08:58 ON-Bar reversion test start: > 11:08:58 ON-Bar reversion test completed successfully. > 11:08:58 'onpload' reversion test start: > 11:08:59 'onpload' reversion test completed successfully. > 11:09:00 Reversion test for R-tree indexes started > 11:09:01 Reversion test for R-tree indexes completed successfully > 11:09:02 PAM reversion test completed successfully. > 11:09:06 Quiescent Mode > 11:09:10 Checking database trade for revertibility ... > 11:09:11 Database trade is revertible ... > 11:09:12 Checking database bo_repositoryo for revertibility ... > 11:09:13 Database bo_repositoryo is revertible ... > 11:09:14 Checking database bo_docagento for revertibility ... > 11:09:15 Database bo_docagento is revertible ... > 11:09:16 Checking database onpload for revertibility ... > 11:09:17 Database onpload is revertible ... > 11:09:18 Checking database startup for revertibility ... > 11:09:20 Database startup is revertible ... > 11:09:20 Checking database stores7 for revertibility ... > 11:09:21 Database stores7 is revertible ... > 11:09:22 Checking database dba for revertibility ... > 11:09:23 Database dba is revertible ... > 11:09:24 Checking database cats for revertibility ... > 11:09:26 Database cats is revertible ... > 11:09:26 Checking database live for revertibility ... > 11:09:30 Database live is revertible ... > 11:09:30 Checking database londis_syn for revertibility ... > 11:09:32 Database londis_syn is revertible ... > 11:09:32 Checking database londis_vw for revertibility ... > 11:09:35 Database londis_vw is revertible ... > 11:09:36 Checking database live_dummy for revertibility ... > 11:09:40 Database live_dummy is revertible ... > 11:09:41 On-Line Mode > 11:09:41 ON-Bar reversion start: > 11:09:41 WARNING:Target server version must have a certified Storage > Manager > installed after conversion/reversion and before bringing up > server. > 11:09:41 ON-Bar reversion completed successfully. > 11:09:42 ... reverting 'onpload' database. > 11:09:42 ... 'onpload' reversion completed successfully. > 11:09:42 PAM reversion completed successfully. > 11:09:46 ... dropping 'sysmaster' database > "crap.txt" 181 lines, 9064 characters > $ wc crap* > 181 1145 9064 crap.txt > $ cat crap.txt > 11:05:03 Maximum server connections 3 > 11:08:53 Shutdown Mode > 11:08:54 Quiescent Mode > 11:08:55 Checkpoint Completed: duration was 0 seconds. > 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 > > 11:08:55 Maximum server connections 3 > 11:08:56 Reversion to version 9.2 Started > 11:08:56 Beginning process of reverting system to 9.2 ... > 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be > truncated from decimal value 4.000 to integer value 4. > Please check onconfig parameter value before reinitializing the Server. > > 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be > truncated from decimal value 2.000 to integer value 2. > Please check onconfig parameter value before reinitializing the Server. > > 11:08:58 Booting Language <spl> from module <> > 11:08:58 Loading Module <SPLNULL> > 11:08:58 On-Line Mode > 11:08:58 ON-Bar reversion test start: > 11:08:58 ON-Bar reversion test completed successfully. > 11:08:58 'onpload' reversion test start: > 11:08:59 'onpload' reversion test completed successfully. > 11:09:00 Reversion test for R-tree indexes started > 11:09:01 Reversion test for R-tree indexes completed successfully > 11:09:02 PAM reversion test completed successfully. > 11:09:06 Quiescent Mode > 11:09:10 Checking database trade for revertibility ... > 11:09:11 Database trade is revertible ... > 11:09:12 Checking database bo_repositoryo for revertibility ... > 11:09:13 Database bo_repositoryo is revertible ... > 11:09:14 Checking database bo_docagento for revertibility ... > 11:09:15 Database bo_docagento is revertible ... > 11:09:16 Checking database onpload for revertibility ... > 11:09:17 Database onpload is revertible ... > 11:09:18 Checking database startup for revertibility ... > 11:09:20 Database startup is revertible ... > 11:09:20 Checking database stores7 for revertibility ... > 11:09:21 Database stores7 is revertible ... > 11:09:22 Checking database dba for revertibility ... > 11:09:23 Database dba is revertible ... > 11:09:24 Checking database cats for revertibility ... > 11:09:26 Database cats is revertible ... > 11:09:26 Checking database live for revertibility ... > 11:09:30 Database live is revertible ... > 11:09:30 Checking database londis_syn for revertibility ... > 11:09:32 Database londis_syn is revertible ... > 11:09:32 Checking database londis_vw for revertibility ... > 11:09:35 Database londis_vw is revertible ... > 11:09:36 Checking database live_dummy for revertibility ... > 11:09:40 Database live_dummy is revertible ... > 11:09:41 On-Line Mode > 11:09:41 ON-Bar reversion start: > 11:09:41 WARNING:Target server version must have a certified Storage > Manager > installed after conversion/reversion and before bringing up > server. > 11:09:41 ON-Bar reversion completed successfully. > 11:09:42 ... reverting 'onpload' database. > 11:09:42 ... 'onpload' reversion completed successfully. > 11:09:42 PAM reversion completed successfully. > 11:09:46 ... dropping 'sysmaster' database > 11:09:47 Quiescent Mode > 11:09:47 Revert system catalogs for 9.2 > 11:09:47 Starting reversion of database trade ... > 11:09:48 Database trade SUCCESSFULLY reverted ... > 11:09:49 Starting reversion of database bo_repositoryo ... > 11:09:50 Database bo_repositoryo SUCCESSFULLY reverted ... > 11:09:51 Starting reversion of database bo_docagento ... > 11:09:52 Database bo_docagento SUCCESSFULLY reverted ... > 11:09:53 Starting reversion of database onpload ... > 11:09:54 Database onpload SUCCESSFULLY reverted ... > 11:09:55 Starting reversion of database startup ... > 11:09:56 Database startup SUCCESSFULLY reverted ... > 11:09:57 Starting reversion of database stores7 ... > 11:09:58 Database stores7 SUCCESSFULLY reverted ... > 11:09:59 Starting reversion of database dba ... > 11:10:00 Database dba SUCCESSFULLY reverted ... > 11:10:00 (211) connection rejected - no calls allowed for sqlexec > 11:10:00 listener-thread: err = -27002: oserr = 0: errstr = : No > connections are allowed in Dynamic Server quiescent mode. > > 11:10:01 Starting reversion of database cats ... > 11:10:01 (212) connection rejected - no calls allowed for sqlexec > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > connections are allowed in Dynamic Server quiescent mode. > > 11:10:01 (213) connection rejected - no calls allowed for sqlexec > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > connections are allowed in Dynamic Server quiescent mode. > > 11:10:01 (214) connection rejected - no calls allowed for sqlexec > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > connections are allowed in Dynamic Server quiescent mode. > > 11:10:02 (215) connection rejected - no calls allowed for sqlexec > 11:10:02 listener-thread: err = -27002: oserr = 0: errstr = : No > connections are allowed in Dynamic Server quiescent mode. > > 11:10:02 Database cats SUCCESSFULLY reverted ... > 11:10:03 Starting reversion of database live ... > 11:10:06 Database live SUCCESSFULLY reverted ... > 11:10:07 Starting reversion of database londis_syn ... > 11:10:08 Database londis_syn SUCCESSFULLY reverted ... > 11:10:09 Starting reversion of database londis_vw ... > 11:10:10 Database londis_vw SUCCESSFULLY reverted ... > 11:10:11 Starting reversion of database live_dummy ... > 11:10:15 Database live_dummy SUCCESSFULLY reverted ... > 11:10:18 Checkpoint Completed: duration was 1 seconds. > 11:10:18 Checkpoint loguniq 112336, logpos 0x28a93d4, timestamp: 761967468 > > 11:10:18 Maximum server connections 3 > 11:10:18 Reverting Partition Header Pages Started > 11:10:20 Reverting Partition Header Pages Succeeded > 11:10:20 Checkpoint Completed: duration was 0 seconds. > 11:10:20 Checkpoint loguniq 112336, logpos 0x28aa018, timestamp: 761979583 > > 11:10:20 Maximum server connections 3 > 11:10:20 Reversion complete. > Install INFORMIX-OnLine Version 9.2 before reinitializing OnLine. > 11:10:21 Reversion to version 9.2 Succeeded > 11:10:23 IBM Informix Dynamic Server Stopped. > > 11:58:38 Informix Dynamic Server 2000 Started. > 11:58:44 Segment locked: addr=0x39bbc000, size=1077215232 > > Wed Jan 7 11:58:46 2004 > > 11:58:46 Event alarms enabled. ALARMPROG = > '/opt/informix/9.21/etc/log_full.sh' > 11:58:46 Booting Language <c> from module <> > 11:58:46 Loading Module <CNULL> > 11:58:46 Booting Language <builtin> from module <> > 11:58:46 Loading Module <BUILTINNULL> > 11:59:05 Informix Dynamic Server 2000 Version 9.21.FC4 Software Serial > Number AAD#J130447 > 11:59:07 HPUX Version B.11.11 -> Using flag/select style KAIO > 11:59:07 HP KAIO concurrent requests changed from 1000 to 2300 > 11:59:10 Informix Dynamic Server 2000 Initialized -- Shared Memory > Initialized. > > 11:59:10 Physical Recovery Started at Page(2:38285). > 11:59:10 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > > 11:59:10 Logical Recovery Started. > 11:59:10 10 recovery worker threads will be started. > 11:59:10 Assert Failed: Dynamic Server 2000 must abort > 11:59:10 Informix Dynamic Server 2000 Version 9.21.FC4 > 11:59:10 Who: Session(14, informix@hamilton, 0, 2047781160) > Thread(209, fast_rec, c00000007a0c2028, 1) > File: rslog.c Line: 3202 > 11:59:10 Results: Dynamic Server 2000 must abort > 11:59:10 Action: Reinitialize shared memory > 11:59:10 stack trace for pid 17358 written to /var/tmp/af.4b9f48e > 11:59:10 See Also: /var/tmp/af.4b9f48e > 11:59:19 rslog.c, line 3202, thread 209, proc id 17358, Dynamic Server 2000 > must abort. > 11:59:19 PANIC: Attempting to bring system down > 12:05:11 Informix Dynamic Server 2000 Started. > 12:05:17 Segment locked: addr=0x39bbc000, size=1077215232 > > Wed Jan 7 12:05:19 2004 > > 12:05:19 Event alarms enabled. ALARMPROG = > '/opt/informix/9.21/etc/log_full.sh' > 12:05:19 Booting Language <c> from module <> > 12:05:19 Loading Module <CNULL> > 12:05:19 Booting Language <builtin> from module <> > 12:05:19 Loading Module <BUILTINNULL> > 12:05:38 Informix Dynamic Server 2000 Version 9.21.FC4 Software Serial > Number AAD#J130447 > 12:05:39 HPUX Version B.11.11 -> Using flag/select style KAIO > 12:05:39 HP KAIO concurrent requests changed from 1000 to 2300 > 12:05:42 Informix Dynamic Server 2000 Initialized -- Shared Memory > Initialized. > > 12:05:42 Physical Recovery Started at Page(2:38285). > 12:05:42 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > > 12:05:42 Logical Recovery Started. > 12:05:42 10 recovery worker threads will be started. > 12:05:42 Assert Failed: Dynamic Server 2000 must abort > 12:05:42 Informix Dynamic Server 2000 Version 9.21.FC4 > 12:05:42 Who: Session(14, informix@hamilton, 0, 2047781160) > Thread(209, fast_rec, c00000007a0c2028, 1) > File: rslog.c Line: 3202 > 12:05:42 Results: Dynamic Server 2000 must abort > 12:05:42 Action: Reinitialize shared memory > 12:05:42 stack trace for pid 17706 written to /var/tmp/af.4b9f615 > 12:05:42 See Also: /var/tmp/af.4b9f615 > 12:05:50 rslog.c, line 3202, thread 209, proc id 17706, Dynamic Server 2000 > must abort. > 12:05:50 PANIC: Attempting to bring system down > 11:36:35 IBM Informix Dynamic Server Started. > 11:36:41 Segment locked: addr=0xc000000039c49000, size=1080684544 > > |
|
04-19-2008, 07:51 PM
| |||
| |||
| Re: Reversion from IDS 9.40 to 9.21 fails Thanks Madison. As you can see from below, the onmode -b revision process leaves the database offline. So at what point could we issue a checkpoint? What do you infer from the absence of the checkpoint? cheers Neil "Madison Pruet" <mpruet@comcast.net> wrote in message news:2KeLb.88807$I07.421506@attbi_s53... > Neil, > > On the failure below, I'm not seeing something that I think is rather > important. That is, I don't see any evidence of a hard checkpoint (i.e. > non-fuzzy) after the reversion has been done. I think that is probably > causing the failure because otherwise, the 9.21 server will be trying to > process 9.4 log records. I do know that a couple of the log records changed > a bit with 9.4 because of some 64-bit alignment issues. > > You might want it try to issue an onmode -c as part of the reversion > process. > > M.Pruet > > > "Neil Truby" <neil.truby@ardenta.com> wrote in message > news:btjhun$7r28c$1@ID-162943.news.uni-berlin.de... > > HP-UX 11.11 > > IDS 9.20 FC4 to IDS 9.40 FC2 > > > > We are testing the above upgrade. On three of the four databases to be > > converted we have had no problems in the conversion process (we did > > encounter a bug with slow index builds, a known problem kindly identified > by > > Jonathan Leffler due to be fixed in 9.40 FC3). On the fourth, it also > > converts OK but sporadically - perhaps 2 times in 10 - the reversion back > > from 9.40 (level 0) to 9.21 will fail. This is an *absolute* show-stopper > > for this client. The database in question is mission-critical, and is > > 500GBytes in size, so dbexport/dbimport, or a restore, is not viable. > > > > A call has been raised with Tech Support (389466). Because this is not a > > "down" system we will have to work hard to ensure that it receives a > > prioroty that refelects the imprtance of the issue to the client. > > > > Any insight gratefully received. I attach the online log from the > reversion > > process and the subsequent attempt to bring the server back online. > > > > thanks > > Neil Truby t:01932 724027 > > Director m:07798 811708 > > Ardenta Limited e:neil.truby@ardenta.com > > > > ==================================== > > 11:37:18 Maximum server connections 0 > > 11:37:18 Update reserved page status of conversion > > 11:37:18 Quiescent Mode > > 11:37:18 Succeeded > > 11:37:19 Checkpoint Completed: duration was 0 seconds. > > 11:37:19 Checkpoint loguniq 112336, logpos 0x28ac018, timestamp: > 761991795 > > > > 11:37:19 Maximum server connections 0 > > 11:37:19 Internal Conversion Completed Successfuly > > 11:37:19 Conversion Enabling Client Connections > > 11:37:19 Building 'sysmaster' database ... > > 11:37:20 On-Line Mode > > 11:37:24 Booting Language <spl> from module <> > > > > 11:05:03 Maximum server connections 3 > > 11:08:53 Shutdown Mode > > 11:08:54 Quiescent Mode > > 11:08:55 Checkpoint Completed: duration was 0 seconds. > > 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 > > > > 11:08:55 Maximum server connections 3 > > 11:08:56 Reversion to version 9.2 Started > > 11:08:56 Beginning process of reverting system to 9.2 ... > > 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be > > truncated from decimal value 4.000 to integer value 4. > > Please check onconfig parameter value before reinitializing the Server. > > > > 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be > > truncated from decimal value 2.000 to integer value 2. > > Please check onconfig parameter value before reinitializing the Server. > > > > 11:08:58 Booting Language <spl> from module <> > > 11:08:58 Loading Module <SPLNULL> > > 11:08:58 On-Line Mode > > 11:08:58 ON-Bar reversion test start: > > 11:08:58 ON-Bar reversion test completed successfully. > > 11:08:58 'onpload' reversion test start: > > 11:08:59 'onpload' reversion test completed successfully. > > 11:09:00 Reversion test for R-tree indexes started > > 11:09:01 Reversion test for R-tree indexes completed successfully > > 11:09:02 PAM reversion test completed successfully. > > 11:09:06 Quiescent Mode > > 11:09:10 Checking database trade for revertibility ... > > 11:09:11 Database trade is revertible ... > > 11:09:12 Checking database bo_repositoryo for revertibility ... > > 11:09:13 Database bo_repositoryo is revertible ... > > 11:09:14 Checking database bo_docagento for revertibility ... > > 11:09:15 Database bo_docagento is revertible ... > > 11:09:16 Checking database onpload for revertibility ... > > 11:09:17 Database onpload is revertible ... > > 11:09:18 Checking database startup for revertibility ... > > 11:09:20 Database startup is revertible ... > > 11:09:20 Checking database stores7 for revertibility ... > > 11:09:21 Database stores7 is revertible ... > > 11:09:22 Checking database dba for revertibility ... > > 11:09:23 Database dba is revertible ... > > 11:09:24 Checking database cats for revertibility ... > > 11:09:26 Database cats is revertible ... > > 11:09:26 Checking database live for revertibility ... > > 11:09:30 Database live is revertible ... > > 11:09:30 Checking database londis_syn for revertibility ... > > 11:09:32 Database londis_syn is revertible ... > > 11:09:32 Checking database londis_vw for revertibility ... > > 11:09:35 Database londis_vw is revertible ... > > 11:09:36 Checking database live_dummy for revertibility ... > > 11:09:40 Database live_dummy is revertible ... > > 11:09:41 On-Line Mode > > 11:09:41 ON-Bar reversion start: > > 11:09:41 WARNING:Target server version must have a certified Storage > > Manager > > installed after conversion/reversion and before bringing up > > server. > > 11:09:41 ON-Bar reversion completed successfully. > > 11:09:42 ... reverting 'onpload' database. > > 11:09:42 ... 'onpload' reversion completed successfully. > > 11:09:42 PAM reversion completed successfully. > > 11:09:46 ... dropping 'sysmaster' database > > "crap.txt" 181 lines, 9064 characters > > $ wc crap* > > 181 1145 9064 crap.txt > > $ cat crap.txt > > 11:05:03 Maximum server connections 3 > > 11:08:53 Shutdown Mode > > 11:08:54 Quiescent Mode > > 11:08:55 Checkpoint Completed: duration was 0 seconds. > > 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 > > > > 11:08:55 Maximum server connections 3 > > 11:08:56 Reversion to version 9.2 Started > > 11:08:56 Beginning process of reverting system to 9.2 ... > > 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be > > truncated from decimal value 4.000 to integer value 4. > > Please check onconfig parameter value before reinitializing the Server. > > > > 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be > > truncated from decimal value 2.000 to integer value 2. > > Please check onconfig parameter value before reinitializing the Server. > > > > 11:08:58 Booting Language <spl> from module <> > > 11:08:58 Loading Module <SPLNULL> > > 11:08:58 On-Line Mode > > 11:08:58 ON-Bar reversion test start: > > 11:08:58 ON-Bar reversion test completed successfully. > > 11:08:58 'onpload' reversion test start: > > 11:08:59 'onpload' reversion test completed successfully. > > 11:09:00 Reversion test for R-tree indexes started > > 11:09:01 Reversion test for R-tree indexes completed successfully > > 11:09:02 PAM reversion test completed successfully. > > 11:09:06 Quiescent Mode > > 11:09:10 Checking database trade for revertibility ... > > 11:09:11 Database trade is revertible ... > > 11:09:12 Checking database bo_repositoryo for revertibility ... > > 11:09:13 Database bo_repositoryo is revertible ... > > 11:09:14 Checking database bo_docagento for revertibility ... > > 11:09:15 Database bo_docagento is revertible ... > > 11:09:16 Checking database onpload for revertibility ... > > 11:09:17 Database onpload is revertible ... > > 11:09:8 Checking database startup for revertibility ... > > 11:09:20 Database startup is revertible ... > > 11:09:20 Checking database stores7 for revertibility ... > > 11:09:21 Database stores7 is revertible ... > > 11:09:22 Checking database dba for revertibility ... > > 11:09:23 Database dba is revertible ... > > 11:09:24 Checking database cats for revertibility ... > > 11:09:26 Database cats is revertible ... > > 11:09:26 Checking database live for revertibility ... > > 11:09:30 Database live is revertible ... > > 11:09:30 Checking database londis_syn for revertibility ... > > 11:09:32 Database londis_syn is revertible ... > > 11:09:32 Checking database londis_vw for revertibility ... > > 11:09:35 Database londis_vw is revertible ... > > 11:09:36 Checking database live_dummy for revertibility ... > > 11:09:40 Database live_dummy is revertible ... > > 11:09:41 On-Line Mode > > 11:09:41 ON-Bar reversion start: > > 11:09:41 WARNING:Target server version must have a certified Storage > > Manager > > installed after conversion/reversion and before bringing up > > server. > > 11:09:41 ON-Bar reversion completed successfully. > > 11:09:42 ... reverting 'onpload' database. > > 11:09:42 ... 'onpload' reversion completed successfully. > > 11:09:42 PAM reversion completed successfully. > > 11:09:46 ... dropping 'sysmaster' database > > 11:09:47 Quiescent Mode > > 11:09:47 Revert system catalogs for 9.2 > > 11:09:47 Starting reversion of database trade ... > > 11:09:48 Database trade SUCCESSFULLY reverted ... > > 11:09:49 Starting reversion of database bo_repositoryo ... > > 11:09:50 Database bo_repositoryo SUCCESSFULLY reverted ... > > 11:09:51 Starting reversion of database bo_docagento ... > > 11:09:52 Database bo_docagento SUCCESSFULLY reverted ... > > 11:09:53 Starting reversion of database onpload ... > > 11:09:54 Database onpload SUCCESSFULLY reverted ... > > 11:09:55 Starting reversion of database startup ... > > 11:09:56 Database startup SUCCESSFULLY reverted ... > > 11:09:57 Starting reversion of database stores7 ... > > 11:09:58 Database stores7 SUCCESSFULLY reverted ... > > 11:09:59 Starting reversion of database dba ... > > 11:10:00 Database dba SUCCESSFULLY reverted ... > > 11:10:00 (211) connection rejected - no calls allowed for sqlexec > > 11:10:00 listener-thread: err = -27002: oserr = 0: errstr = : No > > connections are allowed in Dynamic Server quiescent mode. > > > > 11:10:01 Starting reversion of database cats ... > > 11:10:01 (212) connection rejected - no calls allowed for sqlexec > > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > > connections are allowed in Dynamic Server quiescent mode. > > > > 11:10:01 (213) connection rejected - no calls allowed for sqlexec > > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > > connections are allowed in Dynamic Server quiescent mode. > > > > 11:10:01 (214) connection rejected - no calls allowed for sqlexec > > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > > connections are allowed in Dynamic Server quiescent mode. > > > > 11:10:02 (215) connection rejected - no calls allowed for sqlexec > > 11:10:02 listener-thread: err = -27002: oserr = 0: errstr = : No > > connections are allowed in Dynamic Server quiescent mode. > > > > 11:10:02 Database cats SUCCESSFULLY reverted ... > > 11:10:03 Starting reversion of database live ... > > 11:10:06 Database live SUCCESSFULLY reverted ... > > 11:10:07 Starting reversion of database londis_syn ... > > 11:10:08 Database londis_syn SUCCESSFULLY reverted ... > > 11:10:09 Starting reversion of database londis_vw ... > > 11:10:10 Database londis_vw SUCCESSFULLY reverted ... > > 11:10:11 Starting reversion of database live_dummy ... > > 11:10:15 Database live_dummy SUCCESSFULLY reverted ... > > 11:10:18 Checkpoint Completed: duration was 1 seconds. > > 11:10:18 Checkpoint loguniq 112336, logpos 0x28a93d4, timestamp: > 761967468 > > > > 11:10:18 Maximum server connections 3 > > 11:10:18 Reverting Partition Header Pages Started > > 11:10:20 Reverting Partition Header Pages Succeeded > > 11:10:20 Checkpoint Completed: duration was 0 seconds. > > 11:10:20 Checkpoint loguniq 112336, logpos 0x28aa018, timestamp: > 761979583 > > > > 11:10:20 Maximum server connections 3 > > 11:10:20 Reversion complete. > > Install INFORMIX-OnLine Version 9.2 before reinitializing OnLine. > > 11:10:21 Reversion to version 9.2 Succeeded > > 11:10:23 IBM Informix Dynamic Server Stopped. > > > > 11:58:38 Informix Dynamic Server 2000 Started. > > 11:58:44 Segment locked: addr=0x39bbc000, size=1077215232 > > > > Wed Jan 7 11:58:46 2004 > > > > 11:58:46 Event alarms enabled. ALARMPROG = > > '/opt/informix/9.21/etc/log_full.sh' > > 11:58:46 Booting Language <c> from module <> > > 11:58:46 Loading Module <CNULL> > > 11:58:46 Booting Language <builtin> from module <> > > 11:58:46 Loading Module <BUILTINNULL> > > 11:59:05 Informix Dynamic Server 2000 Version 9.21.FC4 Software > Serial > > Number AAD#J130447 > > 11:59:07 HPUX Version B.11.11 -> Using flag/select style KAIO > > 11:59:07 HP KAIO concurrent requests changed from 1000 to 2300 > > 11:59:10 Informix Dynamic Server 2000 Initialized -- Shared Memory > > Initialized. > > > > 11:59:10 Physical Recovery Started at Page(2:38285). > > 11:59:10 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > > > > 11:59:10 Logical Recovery Started. > > 11:59:10 10 recovery worker threads will be started. > > 11:59:10 Assert Failed: Dynamic Server 2000 must abort > > 11:59:10 Informix Dynamic Server 2000 Version 9.21.FC4 > > 11:59:10 Who: Session(14, informix@hamilton, 0, 2047781160) > > Thread(209, fast_rec, c00000007a0c2028, 1) > > File: rslog.c Line: 3202 > > 11:59:10 Results: Dynamic Server 2000 must abort > > 11:59:10 Action: Reinitialize shared memory > > 11:59:10 stack trace for pid 17358 written to /var/tmp/af.4b9f48e > > 11:59:10 See Also: /var/tmp/af.4b9f48e > > 11:59:19 rslog.c, line 3202, thread 209, proc id 17358, Dynamic Server > 2000 > > must abort. > > 11:59:19 PANIC: Attempting to bring system down > > 12:05:11 Informix Dynamic Server 2000 Started. > > 12:05:17 Segment locked: addr=0x39bbc000, size=1077215232 > > > > Wed Jan 7 12:05:19 2004 > > > > 12:05:19 Event alarms enabled. ALARMPROG = > > '/opt/informix/9.21/etc/log_full.sh' > > 12:05:19 Booting Language <c> from module <> > > 12:05:19 Loading Module <CNULL> > > 12:05:19 Booting Language <builtin> from module <> > > 12:05:19 Loading Module <BUILTINNULL> > > 12:05:38 Informix Dynamic Server 2000 Version 9.21.FC4 Software > Serial > > Number AAD#J130447 > > 12:05:39 HPUX Version B.11.11 -> Using flag/select style KAIO > > 12:05:39 HP KAIO concurrent requests changed from 1000 to 2300 > > 12:05:42 Informix Dynamic Server 2000 Initialized -- Shared Memory > > Initialized. > > > > 12:05:42 Physical Recovery Started at Page(2:38285). > > 12:05:42 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > > > > 12:05:42 Logical Recovery Started. > > 12:05:42 10 recovery worker threads will be started. > > 12:05:42 Assert Failed: Dynamic Server 2000 must abort > > 12:05:42 Informix Dynamic Server 2000 Version 9.21.FC4 > > 12:05:42 Who: Session(14, informix@hamilton, 0, 2047781160) > > Thread(209, fast_rec, c00000007a0c2028, 1) > > File: rslog.c Line: 3202 > > 12:05:42 Results: Dynamic Server 2000 must abort > > 12:05:42 Action: Reinitialize shared memory > > 12:05:42 stack trace for pid 17706 written to /var/tmp/af.4b9f615 > > 12:05:42 See Also: /var/tmp/af.4b9f615 > > 12:05:50 rslog.c, line 3202, thread 209, proc id 17706, Dynamic Server > 2000 > > must abort. > > 12:05:50 PANIC: Attempting to bring system down > > 11:36:35 IBM Informix Dynamic Server Started. > > 11:36:41 Segment locked: addr=0xc000000039c49000, size=1080684544 > > > > > > |
|
04-19-2008, 07:51 PM
| |||
| |||
| Re: Reversion from IDS 9.40 to 9.21 fails - problem identified Thanks to Eric, Jerry, Madison and all who replied. It turns out that, just as with 9.30 and 9.40 FC1 and 2 with this client, we have discovered through our testing a problem already known to IBM, viz: 165122 REVERSION FROM 9.4 SHOULD FINISH WITH APPROPRIATE (PRE94) CHECKPOINT LOG RECORD. There's no workaround. The problem will be fixed in 9.40 FC4, currently scheduled for mid-May 2004. As the absence of a reversion path is a complete show-stopper for the end-user, I don't think they're going to be very happy .... cheers Neil "Neil Truby" <neil.truby@ardenta.com> wrote in message news:btjhun$7r28c$1@ID-162943.news.uni-berlin.de... > HP-UX 11.11 > IDS 9.20 FC4 to IDS 9.40 FC2 > > We are testing the above upgrade. On three of the four databases to be > converted we have had no problems in the conversion process (we did > encounter a bug with slow index builds, a known problem kindly identified by > Jonathan Leffler due to be fixed in 9.40 FC3). On the fourth, it also > converts OK but sporadically - perhaps 2 times in 10 - the reversion back > from 9.40 (level 0) to 9.21 will fail. This is an *absolute* show-stopper > for this client. The database in question is mission-critical, and is > 500GBytes in size, so dbexport/dbimport, or a restore, is not viable. > > A call has been raised with Tech Support (389466). Because this is not a > "down" system we will have to work hard to ensure that it receives a > prioroty that refelects the imprtance of the issue to the client. > > Any insight gratefully received. I attach the online log from the reversion > process and the subsequent attempt to bring the server back online. > > thanks > Neil Truby t:01932 724027 > Director m:07798 811708 > Ardenta Limited e:neil.truby@ardenta.com |
|
04-19-2008, 07:52 PM
| |||
| |||
| Re: Reversion from IDS 9.40 to 9.21 fails There needs to be a reverted format style checkpoint at the end of the reversion or the old version of the instance will have to try to process log records from the 9.4 server. If any of the log records have changed their format, then that would create a problem. Fundamentally - 9.4 knows about 9.21, but 9.21 knows nothing about 9.4. M.P. "Neil Truby" <neil.truby@ardenta.com> wrote in message news:btk2a3$7v6dq$1@ID-162943.news.uni-berlin.de... > Thanks Madison. > As you can see from below, the onmode -b revision process leaves the > database offline. So at what point could we issue a checkpoint? > > What do you infer from the absence of the checkpoint? > > cheers > Neil > > "Madison Pruet" <mpruet@comcast.net> wrote in message > news:2KeLb.88807$I07.421506@attbi_s53... > > Neil, > > > > On the failure below, I'm not seeing something that I think is rather > > important. That is, I don't see any evidence of a hard checkpoint (i.e. > > non-fuzzy) after the reversion has been done. I think that is probably > > causing the failure because otherwise, the 9.21 server will be trying to > > process 9.4 log records. I do know that a couple of the log records > changed > > a bit with 9.4 because of some 64-bit alignment issues. > > > > You might want it try to issue an onmode -c as part of the reversion > > process. > > > > M.Pruet > > > > > > "Neil Truby" <neil.truby@ardenta.com> wrote in message > > news:btjhun$7r28c$1@ID-162943.news.uni-berlin.de... > > > HP-UX 11.11 > > > IDS 9.20 FC4 to IDS 9.40 FC2 > > > > > > We are testing the above upgrade. On three of the four databases to be > > > converted we have had no problems in the conversion process (we did > > > encounter a bug with slow index builds, a known problem kindly > identified > > by > > > Jonathan Leffler due to be fixed in 9.40 FC3). On the fourth, it also > > > converts OK but sporadically - perhaps 2 times in 10 - the reversion > back > > > from 9.40 (level 0) to 9.21 will fail. This is an *absolute* > show-stopper > > > for this client. The database in question is mission-critical, and is > > > 500GBytes in size, so dbexport/dbimport, or a restore, is not viable. > > > > > > A call has been raised with Tech Support (389466). Because this is not > a > > > "down" system we will have to work hard to ensure that it receives a > > > prioroty that refelects the imprtance of the issue to the client. > > > > > > Any insight gratefully received. I attach the online log from the > > reversion > > > process and the subsequent attempt to bring the server back online. > > > > > > thanks > > > Neil Truby t:01932 724027 > > > Director m:07798 811708 > > > Ardenta Limited e:neil.truby@ardenta.com > > > > > > ==================================== > > > 11:37:18 Maximum server connections 0 > > > 11:37:18 Update reserved page status of conversion > > > 11:37:18 Quiescent Mode > > > 11:37:18 Succeeded > > > 11:37:19 Checkpoint Completed: duration was 0 seconds. > > > 11:37:19 Checkpoint loguniq 112336, logpos 0x28ac018, timestamp: > > 761991795 > > > > > > 11:37:19 Maximum server connections 0 > > > 11:37:19 Internal Conversion Completed Successfuly > > > 11:37:19 Conversion Enabling Client Connections > > > 11:37:19 Building 'sysmaster' database ... > > > 11:37:20 On-Line Mode > > > 11:37:24 Booting Language <spl> from module <> > > > > > > 11:05:03 Maximum server connections 3 > > > 11:08:53 Shutdown Mode > > > 11:08:54 Quiescent Mode > > > 11:08:55 Checkpoint Completed: duration was 0 seconds. > > > 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 > > > > > > 11:08:55 Maximum server connections 3 > > > 11:08:56 Reversion to version 9.2 Started > > > 11:08:56 Beginning process of reverting system to 9.2 ... > > > 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be > > > truncated from decimal value 4.000 to integer value 4. > > > Please check onconfig parameter value before reinitializing the Server. > > > > > > 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be > > > truncated from decimal value 2.000 to integer value 2. > > > Please check onconfig parameter value before reinitializing the Server. > > > > > > 11:08:58 Booting Language <spl> from module <> > > > 11:08:58 Loading Module <SPLNULL> > > > 11:08:58 On-Line Mode > > > 11:08:58 ON-Bar reversion test start: > > > 11:08:58 ON-Bar reversion test completed successfully. > > > 11:08:58 'onpload' reversion test start: > > > 11:08:59 'onpload' reversion test completed successfully. > > > 11:09:00 Reversion test for R-tree indexes started > > > 11:09:01 Reversion test for R-tree indexes completed successfully > > > 11:09:02 PAM reversion test completed successfully. > > > 11:09:06 Quiescent Mode > > > 11:09:10 Checking database trade for revertibility ... > > > 11:09:11 Database trade is revertible ... > > > 11:09:12 Checking database bo_repositoryo for revertibility ... > > > 11:09:13 Database bo_repositoryo is revertible ... > > > 11:09:14 Checking database bo_docagento for revertibility ... > > > 11:09:15 Database bo_docagento is revertible ... > > > 11:09:16 Checking database onpload for revertibility ... > > > 11:09:17 Database onpload is revertible ... > > > 11:09:18 Checking database startup for revertibility ... > > > 11:09:20 Database startup is revertible ... > > > 11:09:20 Checking database stores7 for revertibility ... > > > 11:09:21 Database stores7 is revertible ... > > > 11:09:22 Checking database dba for revertibility ... > > > 11:09:23 Database dba is revertible ... > > > 11:09:24 Checking database cats for revertibility ... > > > 11:09:26 Database cats is revertible ... > > > 11:09:26 Checking database live for revertibility ... > > > 11:09:30 Database live is revertible ... > > > 11:09:30 Checking database londis_syn for revertibility ... > > > 11:09:32 Database londis_syn is revertible ... > > > 11:09:32 Checking database londis_vw for revertibility ... > > > 11:09:35 Database londis_vw is revertible ... > > > 11:09:36 Checking database live_dummy for revertibility ... > > > 11:09:40 Database live_dummy is revertible ... > > > 11:09:41 On-Line Mode > > > 11:09:41 ON-Bar reversion start: > > > 11:09:41 WARNING:Target server version must have a certified Storage > > > Manager > > > installed after conversion/reversion and before bringing up > > > server. > > > 11:09:41 ON-Bar reversion completed successfully. > > > 11:09:42 ... reverting 'onpload' database. > > > 11:09:42 ... 'onpload' reversion completed successfully. > > > 11:09:42 PAM reversion completed successfully. > > > 11:09:46 ... dropping 'sysmaster' database > > > "crap.txt" 181 lines, 9064 characters > > > $ wc crap* > > > 181 1145 9064 crap.txt > > > $ cat crap.txt > > > 11:05:03 Maximum server connections 3 > > > 11:08:53 Shutdown Mode > > > 11:08:54 Quiescent Mode > > > 11:08:55 Checkpoint Completed: duration was 0 seconds. > > > 11:08:55 Checkpoint loguniq 112336, logpos 0x1018, timestamp: 761722097 > > > > > > 11:08:55 Maximum server connections 3 > > > 11:08:56 Reversion to version 9.2 Started > > > 11:08:56 Beginning process of reverting system to 9.2 ... > > > 11:08:57 ** WARNING: Value for config parameter LRU_MAX_DIRTY will be > > > truncated from decimal value 4.000 to integer value 4. > > > Please check onconfig parameter value before reinitializing the Server. > > > > > > 11:08:57 ** WARNING: Value for config parameter LRU_MIN_DIRTY will be > > > truncated from decimal value 2.000 to integer value 2. > > > Please check onconfig parameter value before reinitializing the Server. > > > > > > 11:08:58 Booting Language <spl> from module <> > > > 11:08:58 Loading Module <SPLNULL> > > > 11:08:58 On-Line Mode > > > 11:08:58 ON-Bar reversion test start: > > > 11:08:58 ON-Bar reversion test completed successfully. > > > 11:08:58 'onpload' reversion test start: > > > 11:08:59 'onpload' reversion test completed successfully. > > > 11:09:00 Reversion test for R-tree indexes started > > > 11:09:01 Reversion test for R-tree indexes completed successfully > > > 11:09:02 PAM reversion test completed successfully. > > > 11:09:06 Quiescent Mode > > > 11:09:10 Checking database trade for revertibility ... > > > 11:09:11 Database trade is revertible ... > > > 11:09:12 Checking database bo_repositoryo for revertibility ... > > > 11:09:13 Database bo_repositoryo is revertible ... > > > 11:09:14 Chcking database bo_docagento for revertibility ... > > > 11:09:15 Database bo_docagento is revertible ... > > > 11:09:16 Checking database onpload for revertibility ... > > > 11:09:17 Database onpload is revertible ... > > > 11:09:18 Checking database startup for revertibility ... > > > 11:09:20 Database startup is revertible ... > > > 11:09:20 Checking database stores7 for revertibility ... > > > 11:09:21 Database stores7 is revertible ... > > > 11:09:22 Checking database dba for revertibility ... > > > 11:09:23 Database dba is revertible ... > > > 11:09:24 Checking database cats for revertibility ... > > > 11:09:26 Database cats is revertible ... > > > 11:09:26 Checking database live for revertibility ... > > > 11:09:30 Database live is revertible ... > > > 11:09:30 Checking database londis_syn for revertibility ... > > > 11:09:32 Database londis_syn is revertible ... > > > 11:09:32 Checking database londis_vw for revertibility ... > > > 11:09:35 Database londis_vw is revertible ... > > > 11:09:36 Checking database live_dummy for revertibility ... > > > 11:09:40 Database live_dummy is revertible ... > > > 11:09:41 On-Line Mode > > > 11:09:41 ON-Bar reversion start: > > > 11:09:41 WARNING:Target server version must have a certified Storage > > > Manager > > > installed after conversion/reversion and before bringing up > > > server. > > > 11:09:41 ON-Bar reversion completed successfully. > > > 11:09:42 ... reverting 'onpload' database. > > > 11:09:42 ... 'onpload' reversion completed successfully. > > > 11:09:42 PAM reversion completed successfully. > > > 11:09:46 ... dropping 'sysmaster' database > > > 11:09:47 Quiescent Mode > > > 11:09:47 Revert system catalogs for 9.2 > > > 11:09:47 Starting reversion of database trade ... > > > 11:09:48 Database trade SUCCESSFULLY reverted ... > > > 11:09:49 Starting reversion of database bo_repositoryo ... > > > 11:09:50 Database bo_repositoryo SUCCESSFULLY reverted ... > > > 11:09:51 Starting reversion of database bo_docagento ... > > > 11:09:52 Database bo_docagento SUCCESSFULLY reverted ... > > > 11:09:53 Starting reversion of database onpload ... > > > 11:09:54 Database onpload SUCCESSFULLY reverted ... > > > 11:09:55 Starting reversion of database startup ... > > > 11:09:56 Database startup SUCCESSFULLY reverted ... > > > 11:09:57 Starting reversion of database stores7 ... > > > 11:09:58 Database stores7 SUCCESSFULLY reverted ... > > > 11:09:59 Starting reversion of database dba ... > > > 11:10:00 Database dba SUCCESSFULLY reverted ... > > > 11:10:00 (211) connection rejected - no calls allowed for sqlexec > > > 11:10:00 listener-thread: err = -27002: oserr = 0: errstr = : No > > > connections are allowed in Dynamic Server quiescent mode. > > > > > > 11:10:01 Starting reversion of database cats ... > > > 11:10:01 (212) connection rejected - no calls allowed for sqlexec > > > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > > > connections are allowed in Dynamic Server quiescent mode. > > > > > > 11:10:01 (213) connection rejected - no calls allowed for sqlexec > > > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > > > connections are allowed in Dynamic Server quiescent mode. > > > > > > 11:10:01 (214) connection rejected - no calls allowed for sqlexec > > > 11:10:01 listener-thread: err = -27002: oserr = 0: errstr = : No > > > connections are allowed in Dynamic Server quiescent mode. > > > > > > 11:10:02 (215) connection rejected - no calls allowed for sqlexec > > > 11:10:02 listener-thread: err = -27002: oserr = 0: errstr = : No > > > connections are allowed in Dynamic Server quiescent mode. > > > > > > 11:10:02 Database cats SUCCESSFULLY reverted ... > > > 11:10:03 Starting reversion of database live ... > > > 11:10:06 Database live SUCCESSFULLY reverted ... > > > 11:10:07 Starting reversion of database londis_syn ... > > > 11:10:08 Database londis_syn SUCCESSFULLY reverted ... > > > 11:10:09 Starting reversion of database londis_vw ... > > > 11:10:10 Database londis_vw SUCCESSFULLY reverted ... > > > 11:10:11 Starting reversion of database live_dummy ... > > > 11:10:15 Database live_dummy SUCCESSFULLY reverted ... > > > 11:10:18 Checkpoint Completed: duration was 1 seconds. > > > 11:10:18 Checkpoint loguniq 112336, logpos 0x28a93d4, timestamp: > > 761967468 > > > > > > 11:10:18 Maximum server connections 3 > > > 11:10:18 Reverting Partition Header Pages Started > > > 11:10:20 Reverting Partition Header Pages Succeeded > > > 11:10:20 Checkpoint Completed: duration was 0 seconds. > > > 11:10:20 Checkpoint loguniq 112336, logpos 0x28aa018, timestamp: > > 761979583 > > > > > > 11:10:20 Maximum server connections 3 > > > 11:10:20 Reversion complete. > > > Install INFORMIX-OnLine Version 9.2 before reinitializing OnLine. > > > 11:10:21 Reversion to version 9.2 Succeeded > > > 11:10:23 IBM Informix Dynamic Server Stopped. > > > > > > 11:58:38 Informix Dynamic Server 2000 Started. > > > 11:58:44 Segment locked: addr=0x39bbc000, size=1077215232 > > > > > > Wed Jan 7 11:58:46 2004 > > > > > > 11:58:46 Event alarms enabled. ALARMPROG = > > > '/opt/informix/9.21/etc/log_full.sh' > > > 11:58:46 Booting Language <c> from module <> > > > 11:58:46 Loading Module <CNULL> > > > 11:58:46 Booting Language <builtin> from module <> > > > 11:58:46 Loading Module <BUILTINNULL> > > > 11:59:05 Informix Dynamic Server 2000 Version 9.21.FC4 Software > > Serial > > > Number AAD#J130447 > > > 11:59:07 HPUX Version B.11.11 -> Using flag/select style KAIO > > > 11:59:07 HP KAIO concurrent requests changed from 1000 to 2300 > > > 11:59:10 Informix Dynamic Server 2000 Initialized -- Shared Memory > > > Initialized. > > > > > > 11:59:10 Physical Recovery Started at Page(2:38285). > > > 11:59:10 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > > > > > > 11:59:10 Logical Recovery Started. > > > 11:59:10 10 recovery worker threads will be started. > > > 11:59:10 Assert Failed: Dynamic Server 2000 must abort > > > 11:59:10 Informix Dynamic Server 2000 Version 9.21.FC4 > > > 11:59:10 Who: Session(14, informix@hamilton, 0, 2047781160) > > > Thread(209, fast_rec, c00000007a0c2028, 1) > > > File: rslog.c Line: 3202 > > > 11:59:10 Results: Dynamic Server 2000 must abort > > > 11:59:10 Action: Reinitialize shared memory > > > 11:59:10 stack trace for pid 17358 written to /var/tmp/af.4b9f48e > > > 11:59:10 See Also: /var/tmp/af.4b9f48e > > > 11:59:19 rslog.c, line 3202, thread 209, proc id 17358, Dynamic Server > > 2000 > > > must abort. > > > 11:59:19 PANIC: Attempting to bring system down > > > 12:05:11 Informix Dynamic Server 2000 Started. > > > 12:05:17 Segment locked: addr=0x39bbc000, size=1077215232 > > > > > > Wed Jan 7 12:05:19 2004 > > > > > > 12:05:19 Event alarms enabled. ALARMPROG = > > > '/opt/informix/9.21/etc/log_full.sh' > > > 12:05:19 Booting Language <c> from module <> > > > 12:05:19 Loading Module <CNULL> > > > 12:05:19 Booting Language <builtin> from module <> > > > 12:05:19 Loading Module <BUILTINNULL> > > > 12:05:38 Informix Dynamic Server 2000 Version 9.21.FC4 Software > > Serial > > > Number AAD#J130447 > > > 12:05:39 HPUX Version B.11.11 -> Using flag/select style KAIO > > > 12:05:39 HP KAIO concurrent requests changed from 1000 to 2300 > > > 12:05:42 Informix Dynamic Server 2000 Initialized -- Shared Memory > > > Initialized. > > > > > > 12:05:42 Physical Recovery Started at Page(2:38285). > > > 12:05:42 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored. > > > > > > 12:05:42 Logical Recovery Started. > > > 12:05:42 10 recovery worker threads will be started. > > > 12:05:42 Assert Failed: Dynamic Server 2000 must abort > > > 12:05:42 Informix Dynamic Server 2000 Version 9.21.FC4 > > > 12:05:42 Who: Session(14, informix@hamilton, 0, 2047781160) > > > Thread(209, fast_rec, c00000007a0c2028, 1) > > > File: rslog.c Line: 3202 > > > 12:05:42 Results: Dynamic Server 2000 must abort > > > 12:05:42 Action: Reinitialize shared memory > > > 12:05:42 stack trace for pid 17706 written to /var/tmp/af.4b9f615 > > > 12:05:42 See Also: /var/tmp/af.4b9f615 > > > 12:05:50 rslog.c, line 3202, thread 209, proc id 17706, Dynamic Server > > 2000 > > > must abort. > > > 12:05:50 PANIC: Attempting to bring system down > > > 11:36:35 IBM Informix Dynamic Server Started. > > > 11:36:41 Segment locked: addr=0xc000000039c49000, size=1080684544 > > > > > > > > > > > > |
|
04-19-2008, 07:52 PM
| |||
| |||
| Re: Reversion from IDS 9.40 to 9.21 fails "Madison Pruet" <mpruet@comcast.net> wrote in message news:wdjLb.475$I06.2334@attbi_s01... > There needs to be a reverted format style checkpoint at the end of the > reversion or the old version of the instance will have to try to process log > records from the 9.4 server. If any of the log records have changed their > format, then that would create a problem. > > Fundamentally - 9.4 knows about 9.21, but 9.21 knows nothing about 9.4. So, in your view, no viable workaround - even having an IBM engineer dial in and patch the logs - until mid-2004? cheers Neil |
|
04-19-2008, 07:52 PM
| |||
| |||
| Re: Reversion from IDS 9.40 to 9.21 fails We have a patch that we are currently testing. I'm fairly sure that tech support has a tool to force a checkpoint at a certain point which would eliminate the problem. Also, you could escalate the case for a patch. M.Pruet "Neil Truby" <neil.truby@ardenta.com> wrote in message news:btkf97$8gif1$1@ID-162943.news.uni-berlin.de... > > "Madison Pruet" <mpruet@comcast.net> wrote in message > news:wdjLb.475$I06.2334@attbi_s01... > > There needs to be a reverted format style checkpoint at the end of the > > reversion or the old version of the instance will have to try to process > log > > records from the 9.4 server. If any of the log records have changed their > > format, then that would create a problem. > > > > Fundamentally - 9.4 knows about 9.21, but 9.21 knows nothing about 9.4. > > So, in your view, no viable workaround - even having an IBM engineer dial in > and patch the logs - until mid-2004? > > cheers > Neil > > |
|
04-19-2008, 07:52 PM
| |||
| |||
| Re: Reversion from IDS 9.40 to 9.21 fails > Also, you could escalate the case for a patch. That would be brilliant. This is he client who is suffering seriously from the deferred B-tree cleaner bug (or feature) of 9.21, and who has been forced to abandon successive 9.30/9.40 upgrades due to known bugs encountered in testing. Would we escalate this request through the original Tech Support technician? cheers Neil "Madison Pruet" <mpruet@comcast.net> wrote in message news:JCjLb.789813$Fm2.764282@attbi_s04... > We have a patch that we are currently testing. I'm fairly sure that tech > support has a tool to force a checkpoint at a certain point which would > eliminate the problem. > > Also, you could escalate the case for a patch. > > M.Pruet > > > "Neil Truby" <neil.truby@ardenta.com> wrote in message > news:btkf97$8gif1$1@ID-162943.news.uni-berlin.de... > > > > "Madison Pruet" <mpruet@comcast.net> wrote in message > > news:wdjLb.475$I06.2334@attbi_s01... > > > There needs to be a reverted format style checkpoint at the end of the > > > reversion or the old version of the instance will have to try to process > > log > > > records from the 9.4 server. If any of the log records have changed > their > > > format, then that would create a problem. > > > > > > Fundamentally - 9.4 knows about 9.21, but 9.21 knows nothing about 9.4. > > > > So, in your view, no viable workaround - even having an IBM engineer dial > in > > and patch the logs - until mid-2004? > > > > cheers > > Neil > > > > > > |