Jake,
I have heard horror stories from both Sun *and* Tru64 customers (we were
Sequent, and moved to Sun), but your CIO is probably right in moving out
since support (people, skills, patch and product/application availability)
for Tru64 is slowly vanishing. As well maintenance costs are higher
We moved from a T64 (ES40 4
CPU) to a Sun (68002 blades 8 CPU) recently. There were no problems with
the export/import of the 1/2 TB database.
One big thing was that the
max block size on Sun for 8174 is 16K. We had used 32K on T64. So we had to
rethink our multi_block_read_counts, etc.
recipients of list ORACLE-L [EMAIL PROTECTED]
cc:
Subject:RE: Oracle on Sun vs Tru64
Jake,
I have heard horror stories from both Sun *and* Tru64 customers (we were
Sequent, and moved to Sun), but your CIO is probably right in moving out
since support (people, skills, patch
Babu - I created a 32K block size database on Solaris. What is the issue?
Jake - We are doing the same. Nothing big to report. In our case we saw this
coming so we hadn't put any resources in the T64 in several years. The new
Solaris system has newer technology, so it really screams. I had asked
Dennis
I dont have the MEtalink note that says this but here is a clip from one of
the forums
begin quote
Jonathan has given good advice.
Also, on Solaris, Oracle db_block_size is limited to 16K.
There are some other unix platforms that you can use 32K, but not Solaris.
Regards
Tom Villane
Babu - This was 64-bit Solaris, 64-bit Oracle 9.2.0.1. If a catastrophe
looms I would be interested in knowing. ;-)
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Wednesday, October 15, 2003 5:14 PM
To: Multiple recipients of list ORACLE-L
Dennis
I
According to the 9.2 admin guide for Solaris the limits on db block size
are...
Parameter Default Value Range of Values
DB_BLOCK_SIZE 20482048 to 16384 (Linux, Solaris
32-bit)
2048 to 32768 (AIX, HP,
Tru64,
