Ricardo Strausz
2005-08-25 16:00:59 UTC
Hola a ***@s!
I am facing the following problem:
I have to move a database from one machine to other ---to be precise,
from Sybase 11.5 on Win NT, to Sybase 12 on OSX.
Since the versions are not compatible, it is not possible via
standard backup.
After trying some suggestions on the bible (aka PWO), with out
success, I decided to implement an app to do it ---the database is huge!
The basic idea behind the algorithm, is to traverse all entities in
the source-model and, for each one, traverse its data to create new
eos and insert them into the sink-model.
The problem: it is running out of memory!
I already gave the JVM 1024Mb but it looks that it will run out of
memory sooner or later, no mater how many memory I assign to it...
It cross to my mind that there should be a standard way to free the
used memory, say whenever a new entity is going to be traversed.
What is better?
1. re-faulting.
2. using a new editing context for each entity.
3. creating a new store coordinator (for each entity)
How to force to run the garbage-collector after releasing an store
coordinator?
is it necessary?
In five words: how to free system resources?
HELP!
--
Ricardo Strausz
***@mac.com
Business Applied C Objects
http://homepage.mac.com/strausz/baco
+5255 5437 8205
I am facing the following problem:
I have to move a database from one machine to other ---to be precise,
from Sybase 11.5 on Win NT, to Sybase 12 on OSX.
Since the versions are not compatible, it is not possible via
standard backup.
After trying some suggestions on the bible (aka PWO), with out
success, I decided to implement an app to do it ---the database is huge!
The basic idea behind the algorithm, is to traverse all entities in
the source-model and, for each one, traverse its data to create new
eos and insert them into the sink-model.
The problem: it is running out of memory!
I already gave the JVM 1024Mb but it looks that it will run out of
memory sooner or later, no mater how many memory I assign to it...
It cross to my mind that there should be a standard way to free the
used memory, say whenever a new entity is going to be traversed.
What is better?
1. re-faulting.
2. using a new editing context for each entity.
3. creating a new store coordinator (for each entity)
How to force to run the garbage-collector after releasing an store
coordinator?
is it necessary?
In five words: how to free system resources?
HELP!
--
Ricardo Strausz
***@mac.com
Business Applied C Objects
http://homepage.mac.com/strausz/baco
+5255 5437 8205