Reverting from 11.X -> 10.X using onmode -b does n
Michael upgraded from IDS 10.00.FC9 to 11.50.FC4 on AIX 5.3 and found 'onmode -b 10.00' aborting with "Reversion cancelled"; setting LOG_INDEX_BUILDS=0 didn't help. Art Kagel and John Miller pointed out the online.log already named the cause: several SPL/UDR routines and a trigger in one database used (directly or indirectly, e.g. after a recompile) features new to the 11.50 release, so the revertibility check failed. Ken Kwan added that procedures created or recreated under the newer version must be dropped first. Michael dropped the listed procedures/trigger and the reversion then completed smoothly; the objects can be recreated afterwards.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hello,
I am using Informix 10.00.FC9 and upgrading to 11.50.FC4 running AIX
5.3. I have noticed a fair amount of users are upgrading to 11.x and I
am very excited about V11 as well. But I am having a bit of a problem
in all of the environments when trying to revert back to V10 using the
onmode -b 10.00 command. I read online where I must useLOG_INDEX_BUILDS = 0 in my configuration file but it doesn't seem to
work. So I am reaching out to the INFORMIX world to see if anyone else
is having this problem because I am using very VLDB databases and
restores are really not an option in all test environments. Please advise.
16:04:55 Checkpoint Completed: duration was 1 seconds.
16:04:55 Mon Jul 13 - loguniq 36802, logpos 0x4ea7018, timestamp:
0xc715e8c5 Interval: 4289
16:04:55 Maximum server connections 0
16:04:55 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
blocked 0, Plog used 2, Llog used 1
16:04:55 On-Line Mode
16:04:56 SCHAPI: Started dbScheduler thread.
16:04:56 Booting Language <spl> from module <>
16:04:56 Loading Module <SPLNULL>
16:04:56 SCHAPI: Started 2 dbWorker threads.
16:05:32 SCHAPI: thread dbWorker2 task mon_config_startup(3-12)
shutting down
16:05:32 SCHAPI: thread dbScheduler task mon_checkpoint(0-217) shutting
down
16:05:32 SCHAPI: thread dbWorker1 task mon_sysenv(4-12) shutting down
16:05:34 Shutdown Mode
16:05:35 Quiescent Mode
16:05:36 Checkpoint Completed: duration was 0 seconds.
16:05:36 Mon Jul 13 - loguniq 36802, logpos 0x4ed8018, timestamp:
0xc715ef28 Interval: 4290
16:05:36 Maximum server connections 0
16:05:36 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
blocked 0, Plog used 15, Llog used 49
16:05:37 Reversion to version 10.00 Started
16:05:37 Reverting Partition Header Pages Started
16:05:41 Reverting Partition Header Pages Succeeded
16:05:41 Beginning process of reverting system to 10.00 ...
16:05:43 Conv/rev: Started check phase of reversion for component HA
16:05:44 On-Line Mode
16:05:45 Conv/rev: Finished check phase of reversion for component HA
16:05:45 Conv/rev: Started check phase of reversion for component SCHAPI
16:05:45 calling schapi_cvr1150_check_revertable
16:05:45 Conv/rev: Finished check phase of reversion for component SCHAPI
16:05:45 Conv/rev: Started check phase of reversion for component SECURE
16:05:45 Conv/rev: Finished check phase of reversion for component SECURE
16:05:45 Conv/rev: Started check phase of reversion for component RTREE
16:05:45 Conv/rev: Finished check phase of reversion for component RTREE
16:05:45 Conv/rev: Started check phase of reversion for component PLOAD
16:05:45 Conv/rev: Finished check phase of reversion for component PLOAD
16:05:45 Conv/rev: Started check phase of reversion for component BAR
16:05:45 Conv/rev: Finished check phase of reversion for component BAR
16:05:45 Conv/rev: Started check phase of reversion for component SMI
16:05:45 Conv/rev: Finished check phase of reversion for component SMI
16:05:45 Conv/rev: Started check phase of reversion for component SQL
16:05:46 Quiescent Mode
16:05:46 processing ace_test
16:05:46 Checking database ace_test for revertibility ...
16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
before attempting reversion"
16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
before attempting reversion"
16:05:49 "Database ace_test: Must drop spl/udr (iol_check_pin_exp)
before attempting reversion"
16:05:50 "Database ace_test: Must drop spl/udr (oe_upd_pin_exp) before
attempting reversion"
16:05:51 "Database ace_test: Must drop spl/udr (oe_upd_pin) before
attempting reversion"
16:05:52 "Database ace_test: Must drop spl/udr (f_company_by_emp)
before attempting reversion"
16:05:53 "Database ace_test: Must drop trigger (tr_ownere_update)
before attempting reversion"
16:05:54 Database ace_test is not revertible ...
16:05:55 processing dps_persist
16:05:55 Checking database dps_persist for revertibility ...
16:05:56 Database dps_persist is revertible ...
16:05:57 processing stores
16:05:57 Checking database stores for revertibility ...
16:05:59 Database stores is revertible ...
16:06:00 Conv/rev: Failed in check phase of reversion for component SQL
16:06:00 Conv/rev: Started check phase of reversion for component RSAM
16:06:00 Reverting Secondary Partition Header Pages Started
16:06:11 Reverting Secondary Partition Header Pages Succeeded
16:06:11 Conv/rev: Finished check phase of reversion for component RSAM
16:06:11 Reversion cancelled.
The online log is telling you why it won't revert:
16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
before attempting reversion"
16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
before attempting reversion"
16:05:49 "Database ace_test: Must drop spl/udr (iol_check_pin_exp)
before attempting reversion"
16:05:50 "Database ace_test: Must drop spl/udr (oe_upd_pin_exp) before
attempting reversion"
16:05:51 "Database ace_test: Must drop spl/udr (oe_upd_pin) before
attempting reversion"
16:05:52 "Database ace_test: Must drop spl/udr (f_company_by_emp)
before attempting reversion"
16:05:53 "Database ace_test: Must drop trigger (tr_ownere_update)
before attempting reversion"
16:05:54 Database ace_test is not revertible ...
So, just drop that handful of SPL or UDR routines and the reversion will
complete successfully. You can recreate them after the reversion.
Art
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do
those opinions reflect those of other individuals affiliated with any entity
with which I am affiliated nor those of the entities themselves.
On Mon, Jul 13, 2009 at 4:25 PM, Michael Wiggins <
michaelwiggins30@comcast.net> wrote:
> Hello,
>
> I am using Informix 10.00.FC9 and upgrading to 11.50.FC4 running AIX
> 5.3. I have noticed a fair amount of users are upgrading to 11.x and I
> am very excited about V11 as well. But I am having a bit of a problem
> in all of the environments when trying to revert back to V10 using the
> onmode -b 10.00 command. I read online where I must use> LOG_INDEX_BUILDS = 0 in my configuration file but it doesn't seem to
> work. So I am reaching out to the INFORMIX world to see if anyone else
> is having this problem because I am using very VLDB databases and
> restores are really not an option in all test environments. Please advise.
>
> 16:04:55 Checkpoint Completed: duration was 1 seconds.
>
> 16:04:55 Mon Jul 13 - loguniq 36802, logpos 0x4ea7018, timestamp:
> 0xc715e8c5 Interval: 4289
>
> 16:04:55 Maximum server connections 0
>
> 16:04:55 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
> blocked 0, Plog used 2, Llog used 1
>
> 16:04:55 On-Line Mode
>
> 16:04:56 SCHAPI: Started dbScheduler thread.
>
> 16:04:56 Booting Language <spl> from module <>
>
> 16:04:56 Loading Module <SPLNULL>
>
> 16:04:56 SCHAPI: Started 2 dbWorker threads.
>
> 16:05:32 SCHAPI: thread dbWorker2 task mon_config_startup(3-12)
> shutting down
>
> 16:05:32 SCHAPI: thread dbScheduler task mon_checkpoint(0-217) shutting
> down
>
> 16:05:32 SCHAPI: thread dbWorker1 task mon_sysenv(4-12) shutting down
>
> 16:05:34 Shutdown Mode
>
> 16:05:35 Quiescent Mode
>
> 16:05:36 Checkpoint Completed: duration was 0 seconds.
>
> 16:05:36 Mon Jul 13 - loguniq 36802, logpos 0x4ed8018, timestamp:
> 0xc715ef28 Interval: 4290
>
> 16:05:36 Maximum server connections 0
>
> 16:05:36 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
> blocked 0, Plog used 15, Llog used 49
>
> 16:05:37 Reversion to version 10.00 Started
>
> 16:05:37 Reverting Partition Header Pages Started
>
> 16:05:41 Reverting Partition Header Pages Succeeded
>
> 16:05:41 Beginning process of reverting system to 10.00 ...
>
> 16:05:43 Conv/rev: Started check phase of reversion for component HA
>
> 16:05:44 On-Line Mode
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component HA
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SCHAPI
>
> 16:05:45 calling schapi_cvr1150_check_revertable
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component SCHAPI
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SECURE
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component SECURE
>
> 16:05:45 Conv/rev: Started check phase of reversion for component RTREE
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component RTREE
>
> 16:05:45 Conv/rev: Started check phase of reversion for component PLOAD
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component PLOAD
>
> 16:05:45 Conv/rev: Started check phase of reversion for component BAR
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component BAR
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SMI
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component SMI
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SQL
>
> 16:05:46 Quiescent Mode
>
> 16:05:46 processing ace_test
>
> 16:05:46 Checking database ace_test for revertibility ...
>
> 16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
> before attempting reversion"
>
> 16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
> before attempting reversion"
>
> 16:05:49 "Database ace_test: Must drop spl/udr (iol_check_pin_exp)
> before attempting reversion"
>
> 16:05:50 "Database ace_test: Must drop spl/udr (oe_upd_pin_exp) before
> attempting reversion"
>
> 16:05:51 "Database ace_test: Must drop spl/udr (oe_upd_pin) before
> attempting reversion"
>
> 16:05:52 "Database ace_test: Must drop spl/udr (f_company_by_emp)
> before attempting reversion"
>
> 16:05:53 "Database ace_test: Must drop trigger (tr_ownere_update)
> before attempting reversion"
>
> 16:05:54 Database ace_test is not revertible ...
>
> 16:05:55 processing dps_persist
>
> 16:05:55 Checking database dps_persist for revertibility ...
>
> 16:05:56 Database dps_persist is revertible ...
>
> 16:05:57 processing stores
>
> 16:05:57 Checking database stores for revertibility ...
>
> 16:05:59 Database stores is revertible ...
>
> 16:06:00 Conv/rev: Failed in check phase of reversion for component SQL
> 16:06:00 Conv/rev: Started check phase of reversion for component RSAM
> 16:06:00 Reverting Secondary Partition Header Pages Started
>
> 16:06:11 Reverting Secondary Partition Header Pages Succeeded
>
> 16:06:11 Conv/rev: Finished check phase of reversion for component RSAM
>
> 16:06:11 Reversion cancelled.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001636c5b2f0383be4046e9de209
Michael:
The reversion check runs before IDS allows you to revert. If you utilize
new functionality, explicitly or implicitly, you must eliminated the use
of all new features before reverting. The reversion check is what
determines this. It has pointed out some stored procedures
or user defined routines which have taken advantage of new
features. You must drop these before the reversion will continue.
See the output below from your online.log.
16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
before attempting reversion"
16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
before attempting reversion"
16:05:49 "Database ace_test: Must drop spl/udr (iol_check_pin_exp)
before attempting reversion"
16:05:50 "Database ace_test: Must drop spl/udr (oe_upd_pin_exp) before
attempting reversion"
16:05:51 "Database ace_test: Must drop spl/udr (oe_upd_pin) before
attempting reversion"
16:05:52 "Database ace_test: Must drop spl/udr (f_company_by_emp)
before attempting reversion"
16:05:53 "Database ace_test: Must drop trigger (tr_ownere_update)
before attempting reversion"
16:05:54 Database ace_test is not revertible ..
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 07/13/2009 01:25:40 PM:
> [image removed]
>
> Reverting from 11.X -> 10.X using onmode -b do.... [16368]
>
> Michael Wiggins
>
> to:
>
> ids
>
> 07/13/2009 01:26 PM
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Please respond to ids>
>
> Hello,
>
> I am using Informix 10.00.FC9 and upgrading to 11.50.FC4 running AIX
> 5.3. I have noticed a fair amount of users are upgrading to 11.x and I
> am very excited about V11 as well. But I am having a bit of a problem
> in all of the environments when trying to revert back to V10 using the
> onmode -b 10.00 command. I read online where I must use> LOG_INDEX_BUILDS = 0 in my configuration file but it doesn't seem to
> work. So I am reaching out to the INFORMIX world to see if anyone else
> is having this problem because I am using very VLDB databases and
> restores are really not an option in all test environments. Please
advise.
>
> 16:04:55 Checkpoint Completed: duration was 1 seconds.
>
> 16:04:55 Mon Jul 13 - loguniq 36802, logpos 0x4ea7018, timestamp:
> 0xc715e8c5 Interval: 4289
>
> 16:04:55 Maximum server connections 0
>
> 16:04:55 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
> blocked 0, Plog used 2, Llog used 1
>
> 16:04:55 On-Line Mode
>
> 16:04:56 SCHAPI: Started dbScheduler thread.
>
> 16:04:56 Booting Language <spl> from module <>
>
> 16:04:56 Loading Module <SPLNULL>
>
> 16:04:56 SCHAPI: Started 2 dbWorker threads.
>
> 16:05:32 SCHAPI: thread dbWorker2 task mon_config_startup(3-12)
> shutting down
>
> 16:05:32 SCHAPI: thread dbScheduler task mon_checkpoint(0-217) shutting
> down
>
> 16:05:32 SCHAPI: thread dbWorker1 task mon_sysenv(4-12) shutting down
>
> 16:05:34 Shutdown Mode
>
> 16:05:35 Quiescent Mode
>
> 16:05:36 Checkpoint Completed: duration was 0 seconds.
>
> 16:05:36 Mon Jul 13 - loguniq 36802, logpos 0x4ed8018, timestamp:
> 0xc715ef28 Interval: 4290
>
> 16:05:36 Maximum server connections 0
>
> 16:05:36 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
> blocked 0, Plog used 15, Llog used 49
>
> 16:05:37 Reversion to version 10.00 Started
>
> 16:05:37 Reverting Partition Header Pages Started
>
> 16:05:41 Reverting Partition Header Pages Succeeded
>
> 16:05:41 Beginning process of reverting system to 10.00 ...
>
> 16:05:43 Conv/rev: Started check phase of reversion for component HA
>
> 16:05:44 On-Line Mode
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component HA
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SCHAPI
>
> 16:05:45 calling schapi_cvr1150_check_revertable
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component SCHAPI
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SECURE
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component SECURE
>
> 16:05:45 Conv/rev: Started check phase of reversion for component RTREE
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component RTREE
>
> 16:05:45 Conv/rev: Started check phase of reversion for component PLOAD
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component PLOAD
>
> 16:05:45 Conv/rev: Started check phase of reversion for component BAR
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component BAR
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SMI
>
> 16:05:45 Conv/rev: Finished check phase of reversion for component SMI
>
> 16:05:45 Conv/rev: Started check phase of reversion for component SQL
>
> 16:05:46 Quiescent Mode
>
> 16:05:46 processing ace_test
>
> 16:05:46 Checking database ace_test for revertibility ...
>
> 16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
> before attempting reversion"
>
> 16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
> before attempting reversion"
>
> 16:05:49 "Database ace_test: Must drop spl/udr (iol_check_pin_exp)
> before attempting reversion"
>
> 16:05:50 "Database ace_test: Must drop spl/udr (oe_upd_pin_exp) before
> attempting reversion"
>
> 16:05:51 "Database ace_test: Must drop spl/udr (oe_upd_pin) before
> attempting reversion"
>
> 16:05:52 "Database ace_test: Must drop spl/udr (f_company_by_emp)
> before attempting reversion"
>
> 16:05:53 "Database ace_test: Must drop trigger (tr_ownere_update)
> before attempting reversion"
>
> 16:05:54 Database ace_test is not revertible ...
>
> 16:05:55 processing dps_persist
>
> 16:05:55 Checking database dps_persist for revertibility ...
>
> 16:05:56 Database dps_persist is revertible ...
>
> 16:05:57 processing stores
>
> 16:05:57 Checking database stores for revertibility ...
>
> 16:05:59 Database stores is revertible ...
>
> 16:06:00 Conv/rev: Failed in check phase of reversion for component SQL
> 16:06:00 Conv/rev: Started check phase of reversion for component RSAM
> 16:06:00 Reverting Secondary Partition Header Pages Started
>
> 16:06:11 Reverting Secondary Partition Header Pages Succeeded
>
> 16:06:11 Conv/rev: Finished check phase of reversion for component RSAM
>
> 16:06:11 Reversion cancelled.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Ar, John,
I totally understand that, but my issue is that it works with 11.50.FC3
but then doesn't for FC4. I would like to do this the supported way
because we all know how IBM/Informix support will not support doing
unsupported solutions:
IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 47 days
11:22:58 -- 3829888 Kbytes
testaix01.icallinc.com:(/home/informix) $ onmode -b 10.00This will make all necessary modifications to disk structures
so that the IBM Informix Dynamic Server space will be compatible with
INFORMIX-OnLine Version 10.00
Do you wish to continue (y/n)? y
Beginning process of reverting system to 10.00 ...
Checking database ace_prod for revertibility ...
Database ace_prod is revertible ...
Checking database dps_persist for revertibility ...
Database dps_persist is revertible ...
Checking database stores for revertibility ...
Database stores is revertible ...
... dropping 'sysmaster' database
Starting reversion of database sysuser ...
Database sysuser SUCCESSFULLY reverted ...
Starting reversion of database ace_prod ...
Database ace_prod SUCCESSFULLY reverted ...
Starting reversion of database dps_persist ...
Database dps_persist SUCCESSFULLY reverted ...
Starting reversion of database stores ...
Database stores SUCCESSFULLY reverted ...
Reverting Partition Header Pages Started
Reverting Partition Header Pages Succeeded
Reversion complete.
Install INFORMIX-OnLine Version 10.00 before reinitializing OnLine.
> Michael:
>
> The reversion check runs before IDS allows you to revert. If you utilize
> new functionality, explicitly or implicitly, you must eliminated the use
> of all new features before reverting. The reversion check is what
> determines this. It has pointed out some stored procedures
> or user defined routines which have taken advantage of new
> features. You must drop these before the reversion will continue.
> See the output below from your online.log.
>
> 16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
> before attempting reversion"
>
> 16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
> before attempting reversion"
>
> 16:05:49 "Database ace_test: Must drop spl/udr (iol_check_pin_exp)
> before attempting reversion"
>
> 16:05:50 "Database ace_test: Must drop spl/udr (oe_upd_pin_exp) before
> attempting reversion"
>
> 16:05:51 "Database ace_test: Must drop spl/udr (oe_upd_pin) before
> attempting reversion"
>
> 16:05:52 "Database ace_test: Must drop spl/udr (f_company_by_emp)
> before attempting reversion"
>
> 16:05:53 "Database ace_test: Must drop trigger (tr_ownere_update)
> before attempting reversion"
>
> 16:05:54 Database ace_test is not revertible ..
>
> John F. Miller III
> STSM, Support Architect
> miller3@us.ibm.com
> 503-578-5645
> IBM Informix Dynamic Server (IDS)
>
> ids-bounces@iiug.org wrote on 07/13/2009 01:25:40 PM:
>
>
>> [image removed]
>>
>> Reverting from 11.X -> 10.X using onmode -b do.... [16368]
>>
>> Michael Wiggins
>>
>> to:
>>
>> ids
>>
>> 07/13/2009 01:26 PM
>>
>> Sent by:
>>
>> ids-bounces@iiug.org
>>
>> Please respond to ids>
>>
>> Hello,
>>
>> I am using Informix 10.00.FC9 and upgrading to 11.50.FC4 running AIX
>> 5.3. I have noticed a fair amount of users are upgrading to 11.x and I
>> am very excited about V11 as well. But I am having a bit of a problem
>> in all of the environments when trying to revert back to V10 using the
>> onmode -b 10.00 command. I read online where I must use>> LOG_INDEX_BUILDS = 0 in my configuration file but it doesn't seem to
>> work. So I am reaching out to the INFORMIX world to see if anyone else
>> is having this problem because I am using very VLDB databases and
>> restores are really not an option in all test environments. Please
>>
> advise.
>
>> 16:04:55 Checkpoint Completed: duration was 1 seconds.
>>
>> 16:04:55 Mon Jul 13 - loguniq 36802, logpos 0x4ea7018, timestamp:
>> 0xc715e8c5 Interval: 4289
>>
>> 16:04:55 Maximum server connections 0
>>
>> 16:04:55 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
>> blocked 0, Plog used 2, Llog used 1
>>
>> 16:04:55 On-Line Mode
>>
>> 16:04:56 SCHAPI: Started dbScheduler thread.
>>
>> 16:04:56 Booting Language <spl> from module <>
>>
>> 16:04:56 Loading Module <SPLNULL>
>>
>> 16:04:56 SCHAPI: Started 2 dbWorker threads.
>>
>> 16:05:32 SCHAPI: thread dbWorker2 task mon_config_startup(3-12)
>> shutting down
>>
>> 16:05:32 SCHAPI: thread dbScheduler task mon_checkpoint(0-217) shutting
>> down
>>
>> 16:05:32 SCHAPI: thread dbWorker1 task mon_sysenv(4-12) shutting down
>>
>> 16:05:34 Shutdown Mode
>>
>> 16:05:35 Quiescent Mode
>>
>> 16:05:36 Checkpoint Completed: duration was 0 seconds.
>>
>> 16:05:36 Mon Jul 13 - loguniq 36802, logpos 0x4ed8018, timestamp:
>> 0xc715ef28 Interval: 4290
>>
>> 16:05:36 Maximum server connections 0
>>
>> 16:05:36 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
>> blocked 0, Plog used 15, Llog used 49
>>
>> 16:05:37 Reversion to version 10.00 Started
>>
>> 16:05:37 Reverting Partition Header Pages Started
>>
>> 16:05:41 Reverting Partition Header Pages Succeeded
>>
>> 16:05:41 Beginning process of reverting system to 10.00 ...
>>
>> 16:05:43 Conv/rev: Started check phase of reversion for component HA
>>
>> 16:05:44 On-Line Mode
>>
>> 16:05:45 Conv/rev: Finished check phase of reversion for component HA
>>
>> 16:05:45 Conv/rev: Started check phase of reversion for component SCHAPI
>>
>> 16:05:45 calling schapi_cvr1150_check_revertable
>>
>> 16:05:45 Conv/rev: Finished check phase of reversion for component SCHAPI
>>
>
>
>> 16:05:45 Conv/rev: Started check phase of reversion for component SECURE
>>
>> 16:05:45 Conv/rev: Finished check phase of reversion for component SECURE
>>
>
>
>> 16:05:45 Conv/rev: Started check phase of reversion for component RTREE
>>
>> 16:05:45 Conv/rev: Finished check phase of reversion for component RTREE
>>
>> 16:05:45 Conv/rev: Started check phase of reversion for component PLOAD
>>
>> 16:05:45 Conv/rev: Finished check phase of reversion for component PLOAD
>>
>> 16:05:45 Conv/rev: Started check phase of reversion for component BAR
>>
>> 16:05:45 Conv/rev: Finished check phase of reversion for component BAR
>>
>> 16:05:45 Conv/rev: Started check phase of reversion for component SMI
>>
>> 16:05:45 Conv/rev: Finished check phase of reversion for component SMI
>>
>> 16:05:45 Conv/rev: Started check phase of reversion for component SQL
>>
>> 16:05:46 Quiescent Mode
>>
>> 16:05:46 processing ace_test
>>
>> 16:05:46 Checking database ace_test for revertibility ...
>>
>> 16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
>> before attempting reversion"
>>
>> 16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
>> before attempting reversion"
>>
>> 16:05
Michael:
It is not that it does not work for xC4. It is that at some point in time
while running
xC4, someone took advantage of a new feature which is only available in xC4
and
not in previous versions. While this might not have been by a direct
action, it can
be an indirect action.
Example: Someone ran update statistics on a table. That tables
was utilized in a stored procedure, which was later executed
by a users. That stored procedure is now out of date because
of the update stats, so it automatically re-compiles and
re-optimizes
itself which utilizes a new SQL feature to execute the queries
faster.
When doing any reversion it first check to make sure you are not using any
new
feature which are specific to the newer version (in your case xC5). The
reversion
founds some new feature that are specific to xC5. Before allowing you to
continue
you must manually remove the use of these new features. Once that is done
you
can re-run the reversion process using onmode -b.
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 07/14/2009 02:47:24 PM:
> [image removed]
>
> Re: Reverting from 11.X -> 10.X using onmode -.... [16400]
>
> Michael Wiggins
>
> to:
>
> ids
>
> 07/14/2009 02:48 PM
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Please respond to ids.
>
> Ar, John,
>
> I totally understand that, but my issue is that it works with 11.50.FC3
> but then doesn't for FC4. I would like to do this the supported way
> because we all know how IBM/Informix support will not support doing
> unsupported solutions:
>
> IBM Informix Dynamic Server Version 11.50.FC3 -- On-Line -- Up 47 days
> 11:22:58 -- 3829888 Kbytes
>
> testaix01.icallinc.com:(/home/informix) $ onmode -b 10.00> This will make all necessary modifications to disk structures
> so that the IBM Informix Dynamic Server space will be compatible with
> INFORMIX-OnLine Version 10.00
> Do you wish to continue (y/n)? y
> Beginning process of reverting system to 10.00 ...
> Checking database ace_prod for revertibility ...
> Database ace_prod is revertible ...
> Checking database dps_persist for revertibility ...
> Database dps_persist is revertible ...
> Checking database stores for revertibility ...
> Database stores is revertible ...
> .... dropping 'sysmaster' database
> Starting reversion of database sysuser ...
> Database sysuser SUCCESSFULLY reverted ...
> Starting reversion of database ace_prod ...
> Database ace_prod SUCCESSFULLY reverted ...
> Starting reversion of database dps_persist ...
> Database dps_persist SUCCESSFULLY reverted ...
> Starting reversion of database stores ...
> Database stores SUCCESSFULLY reverted ...
> Reverting Partition Header Pages Started
> Reverting Partition Header Pages Succeeded
> Reversion complete.
> Install INFORMIX-OnLine Version 10.00 before reinitializing OnLine.
>
> > Michael:
> >
> > The reversion check runs before IDS allows you to revert. If you
utilize
> > new functionality, explicitly or implicitly, you must eliminated the
use
> > of all new features before reverting. The reversion check is what
> > determines this. It has pointed out some stored procedures
> > or user defined routines which have taken advantage of new
> > features. You must drop these before the reversion will continue.
> > See the output below from your online.log.
> >
> > 16:05:47 "Database ace_test: Must drop spl/udr (oapi_rp_cc_and_pin)
> > before attempting reversion"
> >
> > 16:05:48 "Database ace_test: Must drop spl/udr (iol_update_rp_pin)
> > before attempting reversion"
> >
> > 16:05:49 "Database ace_test: Must drop spl/udr (iol_check_pin_exp)
> > before attempting reversion"
> >
> > 16:05:50 "Database ace_test: Must drop spl/udr (oe_upd_pin_exp) before
> > attempting reversion"
> >
> > 16:05:51 "Database ace_test: Must drop spl/udr (oe_upd_pin) before
> > attempting reversion"
> >
> > 16:05:52 "Database ace_test: Must drop spl/udr (f_company_by_emp)
> > before attempting reversion"
> >
> > 16:05:53 "Database ace_test: Must drop trigger (tr_ownere_update)
> > before attempting reversion"
> >
> > 16:05:54 Database ace_test is not revertible ..
> >
> > John F. Miller III
> > STSM, Support Architect
> > miller3@us.ibm.com
> > 503-578-5645
> > IBM Informix Dynamic Server (IDS)
> >
> > ids-bounces@iiug.org wrote on 07/13/2009 01:25:40 PM:
> >
> >
> >> [image removed]
> >>
> >> Reverting from 11.X -> 10.X using onmode -b do.... [16368]
> >>
> >> Michael Wiggins
> >>
> >> to:
> >>
> >> ids
> >>
> >> 07/13/2009 01:26 PM
> >>
> >> Sent by:
> >>
> >> ids-bounces@iiug.org
> >>
> >> Please respond to ids>
> >>
> >> Hello,
> >>
> >> I am using Informix 10.00.FC9 and upgrading to 11.50.FC4 running AIX
> >> 5.3. I have noticed a fair amount of users are upgrading to 11.x and I
> >> am very excited about V11 as well. But I am having a bit of a problem
> >> in all of the environments when trying to revert back to V10 using the
> >> onmode -b 10.00 command. I read online where I must use> >> LOG_INDEX_BUILDS = 0 in my configuration file but it doesn't seem to
> >> work. So I am reaching out to the INFORMIX world to see if anyone else
> >> is having this problem because I am using very VLDB databases and
> >> restores are really not an option in all test environments. Please
> >>
> > advise.
> >
> >> 16:04:55 Checkpoint Completed: duration was 1 seconds.
> >>
> >> 16:04:55 Mon Jul 13 - loguniq 36802, logpos 0x4ea7018, timestamp:
> >> 0xc715e8c5 Interval: 4289
> >>
> >> 16:04:55 Maximum server connections 0
> >>
> >> 16:04:55 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
> >> blocked 0, Plog used 2, Llog used 1
> >>
> >> 16:04:55 On-Line Mode
> >>
> >> 16:04:56 SCHAPI: Started dbScheduler thread.
> >>
> >> 16:04:56 Booting Language <spl> from module <>
> >>
> >> 16:04:56 Loading Module <SPLNULL>
> >>
> >> 16:04:56 SCHAPI: Started 2 dbWorker threads.
> >>
> >> 16:05:32 SCHAPI: thread dbWorker2 task mon_config_startup(3-12)
> >> shutting down
> >>
> >> 16:05:32 SCHAPI: thread dbScheduler task mon_checkpoint(0-217)
shutting
> >> down
> >>
> >> 16:05:32 SCHAPI: thread dbWorker1 task mon_sysenv(4-12) shutting down
> >>
> >> 16:05:34 Shutdown Mode
> >>
> >> 16:05:35 Quiescent Mode
> >>
> >> 16:05:36 Checkpoint Completed: duration was 0 seconds.
> >>
> >> 16:05:36 Mon Jul 13 - loguniq 36802, logpos 0x4ed8018, timestamp:
> >> 0xc715ef28 Interval: 4290
> >>
> >> 16:05:36 Maximum server connections 0
> >>
> >> 16:05:36 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns
> >> blocked 0, Plog used 15, Llog used 49
> >>
> >> 16:05:37 Reversion to version 10.00 Started
> >>
> >> 16:05:37 Reverting Partition Header Pages Started
> >>
> >> 16:05:41 Reverting
Hi Michael, Are those procedures/functions created(or re-created) after the conversion to 11.50.FC4? Why I'm asking is that all procedures/functions created in the new version need to be dropped before you can revert back to older version. This is the expected behavior. Regards, Ken
Yes, I dropped the procedures and the process went very smooth. Thanks for all the help. WIGG > Hi Michael, > > Are those procedures/functions created(or re-created) after the conversion to > 11.50.FC4? Why I'm asking is that all procedures/functions created in the new > version need to be dropped before you can revert back to older version. This > is the expected behavior. > > Regards, > Ken > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > >