Re: Restores
Posted in 2010
Topics: Installation, Setup & Upgrades, Migration, Import/Export & Data Conversion
In this case, where a downgrade is needed, isn't exists a workaround from IBM support ?
The client always need to export/import all databases?
Technical speaking , is WG already impose a hard limitation of resources like partitioning ? what can be one reason to limit this restore...
Neil, a suggestion to workaround... export all data in "binary" mode ("no conversion" for HPL or "informix" for external tables) and use it to reimport in your test/development environment or test if the onunload/onload works , this way you don't need to recreate your indexes they are exported/imported together with all data.
--- Em qua, 24/3/10, Art Kagel <art.kagel@gmail.com> escreveu:
De: Art Kagel <art.kagel@gmail.com>
Assunto: Re: Restores
Para: "Neil Truby" <neil.truby@ardenta.com>
Cc: informix-list@iiug.org
Data: Quarta-feira, 24 de Março de 2010, 0:41
Granted and accepted.
As far as the semantics, when hard core developers (I still count myself in there) talk about the 'code base' we refer to the source code files. If two executable entities are compiled from the same source files, they have the same code base.
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 Tue, Mar 23, 2010 at 11:18 PM, Neil Truby <neil.truby@ardenta.com> wrote:
"Art Kagel" <art.kagel@gmail.com> wrote in message
news:mailman.46.1269395389.1071.informix-list@iiug.org...
>> You've never heard of #DEFINE and #if DEFINED()? Same code, different
>> compiles. That's how the resoruce limitations are implemented as well as
>> the version checks.
Maybe we're just arguing semantics?
You have to download different software for WGE then for EE (I know, I've
just wasted half an hour downloading and installing EE just so I can do the
restore ;-)).
Depending upon which you've download they do different things, like put out
resource restriction messages, and in fact actually apply the restrictions.
Since there's nothing on my (or your syste,) which the oninit program can
query to decide whether you are an EE or WGE customer, the code *must* be
different, even if very supericially, surely ...?!
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
-----Anexo incorporado-----
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
"Cesar Inacio Martins" <cesar_inacio_martins@yahoo.com.br> wrote in message
news:mailman.50.1269429864.1071.informix-list@iiug.org...
>> In this case, where a downgrade is needed, isn't exists a workaround from
>> IBM support ?
The client always need to export/import all databases?
Technical speaking , is WG already impose a hard limitation of resources
like partitioning ? what can be one reason to limit this restore...
>> Neil, a suggestion to workaround... export all data in "binary" mode ("no
>> conversion" for HPL or "informix" for external tables) and use it to
>> reimport in your test/development environment or test if the
>> onunload/onload works , this way you don't need to recreate your indexes
>> they are exported/imported together with all data.
Hi Cesar
Thanks for the suggestion.
There is indeed the possibility to do ASCII transfers for modest data
volumes.
The larger the db though the more attractive the archive/restore option
In this case I am investigating a performance issue that may be a function
of how the data physically exists on disk, so an archive/restore is the only
option.
regards
I don't know if the onunload/onload have the same version limitation of ontape, did you tested it?
AFAIK they works in a similar way from ontape, dumping the used pages and the structure of the table/indexes... what is very fast, just like the ontape.
And with it , you can specify to export the database in single command to unique file...
Just remember, the destination must have the same dbspaces configuration... and if your company buy the workgroup before feb/2009 tables use partitioning , you will violate a license limitation on the WG (don't permits pa
--- Em qua, 24/3/10, Neil Truby <neil.truby@ardenta.com> escreveu:
De: Neil Truby <neil.truby@ardenta.com>
Assunto: Re: Restores
Para: informix-list@iiug.org
Data: Quarta-feira, 24 de Março de 2010, 9:27
"Cesar Inacio Martins" <cesar_inacio_martins@yahoo.com.br> wrote in message
news:mailman.50.1269429864.1071.informix-list@iiug.org...
>> In this case, where a downgrade is needed, isn't exists a workaround from
>> IBM support ?
The client always need to export/import all databases?
Technical speaking , is WG already impose a hard limitation of resources
like partitioning ? what can be one reason to limit this restore...
>> Neil, a suggestion to workaround... export all data in "binary" mode ("no
>> conversion" for HPL or "informix" for external tables) and use it to
>> reimport in your test/development environment or test if the
>> onunload/onload works , this way you don't need to recreate your indexes
>> they are exported/imported together with all data.
Hi Cesar
Thanks for the suggestion.
There is indeed the possibility to do ASCII transfers for modest data
volumes.
The larger the db though the more attractive the archive/restore option
In this case I am investigating a performance issue that may be a function
of how the data physically exists on disk, so an archive/restore is the only
option.
regards
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com