I’ve loaded Oracle 11GR2 on a Windows 7 Ulitmate machine. The machine has
8 G memory, so I thought I would give Oracle 3.6G of it. After loading the 32
bit client and TOAD 11, queries are coming up with a memory error. I looked and
Oracle is taking up the 3.6G. My thinking is that it is holding onto it somehow
and not giving TOAD anything to work with.
If this is the problem, is there anyway in TOAD to change the memory in Oracle,
or, would it just be better to unload everything and start all over again?
Actually, I was doing it with TOAD import rather than CTL creation
Once I used the CTL creation, it loaded the 16 million records extremely fast with no issues.
hmmmm.
We’ll see.
64-bit would not have solved your issue – i.e. it’s not some magic
silver bullet. When you want to bulk load data you should be using the right
method – e.g. sql loader, external tables, or some third party bulk load
or etl tool. A 64-bit toad would have only allowed you to try a brute force
solution longer before having the same issues. When you need to dig a swimming
pool a back hoe is always preferable to a shovel – no matter how big or
nice the shovel. Manual or brute force only works to a point – 64-bits
won’t fix that ….