Home > Archive > Clipper > June 2004 > Migration Clipper/ADS to Mediator/Oracle
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Migration Clipper/ADS to Mediator/Oracle
|
|
|
| Hi everyone,
I'm very interested to hear whether someone has already some experience
with a migration of Clipper/ADS tables to Mediator/Oracle.
The DBF/ADS tables I have to migrate are bigger than 2GB in size,
therefore only experience with this scenario is what I'm looking for
(The Mediator utility DAT2MED executes Commit/Begin transactions
commands which producing a RT error when DBFNTXAX is linked in).
Hopefully someone can share some thoughts.
TIA
Fred
| |
| Joe Wright 2004-06-05, 3:55 pm |
| dbyy wrote:
> Hi everyone,
>
> I'm very interested to hear whether someone has already some experience
> with a migration of Clipper/ADS tables to Mediator/Oracle.
> The DBF/ADS tables I have to migrate are bigger than 2GB in size,
> therefore only experience with this scenario is what I'm looking for
> (The Mediator utility DAT2MED executes Commit/Begin transactions
> commands which producing a RT error when DBFNTXAX is linked in).
>
> Hopefully someone can share some thoughts.
>
> TIA
>
> Fred
I routinely 'unload' Informix tables to text and then 'load' up .dbf
structures with the text. And vice versa. No indexing involved.
Please explain in what environment you are able to create and
maintain Clipper .dbf files bigger than 2 Gigabytes.
--
Joe Wright mailto:joewwright@comcast.net
"Everything should be made as simple as possible, but not simpler."
--- Albert Einstein ---
| |
|
| Joe Wright wrote:
> dbyy wrote:
>
>
>
> I routinely 'unload' Informix tables to text and then 'load' up .dbf
> structures with the text. And vice versa. No indexing involved.
>
> Please explain in what environment you are able to create and maintain
> Clipper .dbf files bigger than 2 Gigabytes.
>
Hi Joe,
as I mentioned in my first posting. We're using (Clipper) DBF tables
with ADS (AdvantageDatabaseSystem). (max size on ADS for DBF's: 4GB)
Environemnt: W2K server and W2K/Win98 workstations, TCP/IP and
ADS Vers 5.7.
HTH
Fred
| |
| Andreas Moroder 2004-06-06, 3:55 am |
| dbyy schrieb:
> Hi everyone,
>
> I'm very interested to hear whether someone has already some experience
> with a migration of Clipper/ADS tables to Mediator/Oracle.
> The DBF/ADS tables I have to migrate are bigger than 2GB in size,
> therefore only experience with this scenario is what I'm looking for
> (The Mediator utility DAT2MED executes Commit/Begin transactions
> commands which producing a RT error when DBFNTXAX is linked in).
>
> Hopefully someone can share some thoughts.
>
> TIA
>
> Fred
Hello Fred,
we have a application with Advantage and mediator and it works very
well. If you get a runtime error it may depend on the fact that
advantage and mediator have certain macros that have the same name but
that translate to different functions. The compiler does simply
translate using the first header file.
The only way to solve this problem is to search the sources for this
macros a change it with the appropriate med or ads fuction calls.
Bye
Andreas
| |
|
| Andreas Moroder wrote:
> dbyy schrieb:
>
>
> Hello Fred,
>
> we have a application with Advantage and mediator and it works very
> well. If you get a runtime error it may depend on the fact that
> advantage and mediator have certain macros that have the same name but
> that translate to different functions. The compiler does simply
> translate using the first header file.
> The only way to solve this problem is to search the sources for this
> macros a change it with the appropriate med or ads fuction calls.
>
> Bye
> Andreas
>
>
hi Andres,
Thanks for your input.
I checked the include files for ADS and Mediator.
And you're right. Same command, different translation into ADS
/Mediator function calls.
Now it's easy to create a workaround.
Thanks again for help.
And beside that, how is your experience with the migration from ADS to
Mediator?
We have to migrate several bigger apps - one with over 50 modules.
Would be nice if you would have any suggestions. Roadblocks, tricky
things etc.
If you like, contact me at dbyy^at^canada^dot^com@neverland.com (use
part b4 @).
Thanks
Fred
| |
| Andreas Moroder 2004-06-06, 3:55 pm |
| > Thanks for your input.
> I checked the include files for ADS and Mediator.
> And you're right. Same command, different translation into ADS
> /Mediator function calls.
> Now it's easy to create a workaround.
>
> Thanks again for help.
>
> And beside that, how is your experience with the migration from ADS to
> Mediator?
> We have to migrate several bigger apps - one with over 50 modules.
>
> Would be nice if you would have any suggestions. Roadblocks, tricky
> things etc.
>
> If you like, contact me at dbyy^at^canada^dot^com@neverland.com (use
> part b4 @).
>
> Thanks
> Fred
>
Hello Fred,
we use mediator since last autunmn, but mostly using medsql and not
using medntx or medidx. With medsql we had no big problems execpt at the
begining to find the right link order with blinker.
Two w s ago we started with a first test migration using medntx and it
was there that I discovered the macro problems. I replaced the SET SCOPE
TO with a function call. In this function I check the driver type and
then call the appropriate mediator or ads functions.
Here I disovered a bug of our mediator version ( 3.x, I can't tell you
the exact version, because I am at home now ). If you uset the
MedSetScpe() function on a clipper index that was translated to a real
oracle index ( not with field in table ) by dbf2med, than the scope does
NOT work. This is the case if the index is made of only one field
without functions.
Another problem is also the slow speed when loading the data to oracle
via dat2med. May be I should also try to link dat2med with axs.
Bye
Andreas
P.S. How many dot com does you address have ?
| |
|
| Andreas Moroder wrote:
> Hello Fred,
>
> we use mediator since last autunmn, but mostly using medsql and not
> using medntx or medidx. With medsql we had no big problems execpt at the
> begining to find the right link order with blinker.
>
> Two ws ago we started with a first test migration using medntx and it
> was there that I discovered the macro problems. I replaced the SET SCOPE
> TO with a function call. In this function I check the driver type and
> then call the appropriate mediator or ads functions.
>
> Here I disovered a bug of our mediator version ( 3.x, I can't tell you
> the exact version, because I am at home now ). If you uset the
> MedSetScpe() function on a clipper index that was translated to a real
> oracle index ( not with field in table ) by dbf2med, than the scope does
> NOT work. This is the case if the index is made of only one field
> without functions.
>
> Another problem is also the slow speed when loading the data to oracle
> via dat2med. May be I should also try to link dat2med with axs.
>
> Bye
> Andreas
>
> P.S. How many dot com does you address have ?
Hi Andres
right now we converting dbf tables (total 13GB) to Oracle using
DBF2MED. NTX2MEd and DAT2MED (modified with DBFNXTAX RDD).
Everything so far looks fine but we're not in the stage that we're using
the Oracle tables in 'real-life' apps.
We working at the moment on some issues to be able to access Oracle
tables with Clipper <and> with DELPHI5.
Would be nice to have a TComponent with the fucntionality of the
Mediator RDD.
Thats for now.
Cheers
Fred
| |
|
| if you are using oracle 8i there is a utility oracle migration assistant
for ms access. So, first of all you should open your clipper table/dbf
file in ms access and save as ms acess mdb file. then you can covert the
entire table into oracle table.
take care of data type and size/length and other properties while
migrating the data from ms access to oracle
regards
pgv
| |
| Andreas Moroder 2004-06-08, 3:55 pm |
| pgv schrieb:
> if you are using oracle 8i there is a utility oracle migration assistant
> for ms access. So, first of all you should open your clipper table/dbf
> file in ms access and save as ms acess mdb file. then you can covert the
> entire table into oracle table.
>
> take care of data type and size/length and other properties while
> migrating the data from ms access to oracle
>
> regards
> pgv
>
No,
mediator ads his own field to your tables so yo can NOT do this, if you
want to continue using the clipper logic to access records etc.
Bye
Andreas
| |
|
| Andreas Moroder wrote:
> pgv schrieb:
>
> No,
> mediator ads his own field to your tables so yo can NOT do this, if you
> want to continue using the clipper logic to access records etc.
>
> Bye
> Andreas
I agree,
There is no way to go via access from ADS/DBF to Oracle.
btw. I modified the load utility and now it's processing ADS DBF to
load the to Oracle.
Thanks to anybody who tried to help.
cheers
Fred
| |
|
| Hi,
Uzytkownik "dbyy" <dbyy@nirvana.com> napisal w wiadomosci
news:6o5xc.9421$8k4.312554@news20.bellglobal.com...
>
> We working at the moment on some issues to be able to access Oracle
> tables with Clipper <and> with DELPHI5.
> Would be nice to have a TComponent with the fucntionality of the
> Mediator RDD.
Have good news for you.
OTC has already developped the secure and efficient way of accessing
Mediator from Delphi. At this stage it consists of over 250 Delphi functions
giving you direct access to Mediator and DBF tables from Delphi level.
If you are familiar with Clipper you are also familiar with this new xBApi
interface.
The functions available are directly modeled on Clipper and Mediator
functions.
Visual components based on this interface will follow soon.
Regards,
Jacek Potempa
OTC Mediator & Terminal info: www.otc.pl
| |
| Martin \(Please note spammers email address used\) 2004-06-16, 8:55 am |
| Why are you doing this - just curious?
|
|
|
|
|