Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Oracle Corporation (ORCL) -- Ignore unavailable to you. Want to Upgrade?

To: Lizzie Tudor who wrote (4733)	12/23/1997 6:45:00 AM
From: Robert E. Bruss	Read Replies (2) \| Respond to of 19080

I have to agree with Michael, Oracle occasionally releases premature products, some of these are shipping now. Sure in a future release everything will be cleaned up, but for now, our programmers consider them 'buggy'. ------------------- That's hardly unique in the pc software business. In fact, off hand I can't think of a single major mfr'r that introduced software that hasn't needed a patch before too long. Looking at my shelf, I don't believe there's a single box there that didn't require an "update" for some reason or other.

To: Lizzie Tudor who wrote (4733)	12/23/1997 9:11:00 AM
From: Michael Olin	Respond to of 19080

Michelle, I don't want to turn this thread into a tech support line but... There are several things to look at with SQL*Loader on the client. If you have already looked at these, just ignore me. If you are using replace (throw out the old data and use what you're loading), truncate the table first. This eliminates tons of rollback segment activity when the old records are deleted. Check the size of the array buffer being used. The default on clients is smaller than the default on servers. Bump up the array size. Also check the commit interval. For the number of records you're loading it needs to be a whole lot more than the default of 64. If you are doing replaces, consider presorting the records and using a direct path load. The first and third suggestions really shouldn't make that much of a difference if you are getting acceptable performance on the server. The array and commit parameters can make a big difference on the client side. There are a whole lot of sites on the web with technical tips, etc. regarding Oracle. We have links to a dozen or so on the New York Oracle Users Group site at nyoug.org -Michael