dbexport on RSS client

Anyone knows if dbexport on 11.50 RSS client is possible? Paul,

I don't know of any reason why it shouldn't work! You can always use my dbexport replacement utility myexport! Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) See you at the 2010 IIUG Informix Conference April 25-28, 2010 Overland Park (Kansas City), KS www.iiug.org/conf Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. 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, Apr 12, 2010 at 8:52 PM, Chin, Paul (TSG-OSDO) <pchin@hp.com> wrote: > Anyone knows if dbexport on 11.50 RSS client is possible? > > Paul, > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --0016368e319b55ed42048414bdfe

I'm pretty sure that we added support for dbexport as part of xC6 if st= op apply is set on the RSS node. = From: "Chin, Paul (TSG-OSDO)" <pchin@hp.com> = = To: ids@iiug.org = = Date: 04/12/2010 07:53 PM = = Subject: dbexport on RSS client [19649] = = Sent by: ids-bounces@iiug.org = = Anyone knows if dbexport on 11.50 RSS client is possible? Paul, ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

Did some testing on 11.50FC6. apparently dbexport is possible in RSS client by manipulating this two configuation parameters, STOP_APPLY and LOG_STAGING_DIR using the onmode -wf, -wm command -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Madison Pruet Sent: Tuesday, 13 April 2010 12:22 PM To: ids@iiug.org Subject: Re: dbexport on RSS client [19651] I'm pretty sure that we added support for dbexport as part of xC6 if st= op apply is set on the RSS node. = From: "Chin, Paul (TSG-OSDO)" <pchin@hp.com> = = To: ids@iiug.org = = Date: 04/12/2010 07:53 PM = = Subject: dbexport on RSS client [19649] = = Sent by: ids-bounces@iiug.org = = Anyone knows if dbexport on 11.50 RSS client is possible? Paul, ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. = ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

This function was enabled in 11.50.xC6. On the RSS turn on STOP_APPLY , onmode -wf STOP_APPLY=1 and set USELASTCOMMITTED=ALL using onmode -wf. Regards, -Ping ----- Original Message ---- From: "Chin, Paul (TSG-OSDO)" <pchin@hp.com> To: ids@iiug.org Sent: Mon, April 12, 2010 7:52:38 PM Subject: dbexport on RSS client [19649] Anyone knows if dbexport on 11.50 RSS client is possible? Paul, ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Works on a HDR secondary so it should - run on HDR secondary is a neat way to get an export with needing any locks. > Anyone knows if dbexport on 11.50 RSS client is possible? > > Paul, > > > Paul Watson Oninit www.oninit.com Advanced DataTools www.advancedatatools.com Tel: +1 913 674 0360 Cell: +1 913 387 7529 Failure is not as frightening as regret. If you want to improve, be content to be thought foolish and stupid. _____ avast! Antivirus <http://www.avast.com>; : Outbound message clean. Virus Database (VPS): 100413-0, 04/13/2010 Tested on: 4/13/2010 8:48:53 AM avast! - copyright (c) 1988-2010 ALWIL Software.

Paul Watson wrote: Works on a HDR secondary so it should - run on HDR secondary is a neat way to get an export with needing any locks. Response: There is a reason dbexport wants locks, and on HDR secondaries you can't enforce locks because of the interaction with recovery threads. So should you dbexport a database on a secondary, you should be aware that the tables you are exporting are very likely being modified out from under the export. So any referential constraints in your database could potential be invalid when you go to import it because the tables were changing while the export was occurring (ie you could be missing values in parent tables on foreign keys etc..). Just putting this out as a warning that dbexporting on a HDR secondary may not get you entirely what you expect, and so it could probably be argued that it should not be allowed to used dbexport on a secondary. Jacques Renaut IBM Informix Advanced Support APD Team

Jacques I'm aware of the limitations - it's just an easy way to get an export without taking the production system offline. Cheers Paul -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of JACQUES RENAUT Sent: Tuesday, April 13, 2010 9:37 AM To: ids@iiug.org Subject: Re: RE: dbexport on RSS client [19664] Paul Watson wrote: Works on a HDR secondary so it should - run on HDR secondary is a neat way to get an export with needing any locks. Response: There is a reason dbexport wants locks, and on HDR secondaries you can't enforce locks because of the interaction with recovery threads. So should you dbexport a database on a secondary, you should be aware that the tables you are exporting are very likely being modified out from under the export. So any referential constraints in your database could potential be invalid when you go to import it because the tables were changing while the export was occurring (ie you could be missing values in parent tables on foreign keys etc..). Just putting this out as a warning that dbexporting on a HDR secondary may not get you entirely what you expect, and so it could probably be argued that it should not be allowed to used dbexport on a secondary. Jacques Renaut IBM Informix Advanced Support APD Team **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. _____ avast! Antivirus <http://www.avast.com>; : Outbound message clean. Virus Database (VPS): 100413-0, 04/13/2010 Tested on: 4/13/2010 9:41:12 AM avast! - copyright (c) 1988-2010 ALWIL Software.

Paul, Let me suggest the following technique. 1) demote the HDR secondary to an RSS node --- This can be done online 2) set stop apply on the RSS node -- This can also be done online. Whi= le in this mode, we will stage the logs and can recover from them in the c= ase of a primary failure... 3) perform dbexport 4) turn off stop apply on the RSS node so it can replay the staged logs= 5) once the secondary is fairly caught up - promote the RSS node back t= o an HDR secondary All of these steps can be performed online and since we are staging the= logs rather than blocking the log transfer, we are still protected from= a primary failure. The dbexport will be using last committed read isolation - and thus wil= l be consistent. This technique will allow the export to be performed witho= ut impacting the primary and also will result in a consistent export. M.P. = From: "Paul Watson" <paul@oninit.com> = = To: ids@iiug.org = = Date: 04/13/2010 09:42 AM = = Subject: RE: RE: dbexport on RSS client [19665] = = Sent by: ids-bounces@iiug.org = = Jacques I'm aware of the limitations - it's just an easy way to get an export without taking the production system offline. Cheers Paul -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of JACQUES RENAUT Sent: Tuesday, April 13, 2010 9:37 AM To: ids@iiug.org Subject: Re: RE: dbexport on RSS client [19664] Paul Watson wrote: Works on a HDR secondary so it should - run on HDR secondary is a neat = way to get an export with needing any locks. Response: There is a reason dbexport wants locks, and on HDR secondaries you can'= t enforce locks because of the interaction with recovery threads. So shou= ld you dbexport a database on a secondary, you should be aware that the tables= you are exporting are very likely being modified out from under the export.= So any referential constraints in your database could potential be invalid whe= n you go to import it because the tables were changing while the export was occurring (ie you could be missing values in parent tables on foreign k= eys etc..). Just putting this out as a warning that dbexporting on a HDR secondary may not get you entirely what you expect, and so it could probably be argued that it should not be allowed to used dbexport on a secondary. Jacques Renaut IBM Informix Advanced Support APD Team ***********************************************************************= ***** *** Forum Note: Use "Reply" to post a response in the discussion forum. _____ avast! Antivirus <http://www.avast.com>; : Outbound message clean. Virus Database (VPS): 100413-0, 04/13/2010 Tested on: 4/13/2010 9:41:12 AM avast! - copyright (c) 1988-2010 ALWIL Software. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

Yep - works perfectly unless you are on V7, 9 or 10 :) -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Madison Pruet Sent: Tuesday, April 13, 2010 10:22 AM To: ids@iiug.org Subject: RE: RE: dbexport on RSS client [19667] Paul, Let me suggest the following technique. 1) demote the HDR secondary to an RSS node --- This can be done online 2) set stop apply on the RSS node -- This can also be done online. Whi= le in this mode, we will stage the logs and can recover from them in the c= ase of a primary failure... 3) perform dbexport 4) turn off stop apply on the RSS node so it can replay the staged logs= 5) once the secondary is fairly caught up - promote the RSS node back t= o an HDR secondary All of these steps can be performed online and since we are staging the= logs rather than blocking the log transfer, we are still protected from= a primary failure. The dbexport will be using last committed read isolation - and thus wil= l be consistent. This technique will allow the export to be performed witho= ut impacting the primary and also will result in a consistent export. M.P. = From: "Paul Watson" <paul@oninit.com> = = To: ids@iiug.org = = Date: 04/13/2010 09:42 AM = = Subject: RE: RE: dbexport on RSS client [19665] = = Sent by: ids-bounces@iiug.org = = Jacques I'm aware of the limitations - it's just an easy way to get an export without taking the production system offline. Cheers Paul -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of JACQUES RENAUT Sent: Tuesday, April 13, 2010 9:37 AM To: ids@iiug.org Subject: Re: RE: dbexport on RSS client [19664] Paul Watson wrote: Works on a HDR secondary so it should - run on HDR secondary is a neat = way to get an export with needing any locks. Response: There is a reason dbexport wants locks, and on HDR secondaries you can'= t enforce locks because of the interaction with recovery threads. So shou= ld you dbexport a database on a secondary, you should be aware that the tables= you are exporting are very likely being modified out from under the export.= So any referential constraints in your database could potential be invalid whe= n you go to import it because the tables were changing while the export was occurring (ie you could be missing values in parent tables on foreign k= eys etc..). Just putting this out as a warning that dbexporting on a HDR secondary may not get you entirely what you expect, and so it could probably be argued that it should not be allowed to used dbexport on a secondary. Jacques Renaut IBM Informix Advanced Support APD Team ***********************************************************************= ***** *** Forum Note: Use "Reply" to post a response in the discussion forum. _____ avast! Antivirus <http://www.avast.com>; : Outbound message clean. Virus Database (VPS): 100413-0, 04/13/2010 Tested on: 4/13/2010 9:41:12 AM avast! - copyright (c) 1988-2010 ALWIL Software. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. = **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum. _____ avast! Antivirus <http://www.avast.com>; : Outbound message clean. Virus Database (VPS): 100413-0, 04/13/2010 Tested on: 4/13/2010 10:26:18 AM avast! - copyright (c) 1988-2010 ALWIL Software.