ORA-600 [3398] on Amdahl/UTS

ORA-600 [3398] on Amdahl/UTS

Post by Cynthia Mumfo » Fri, 01 Dec 1995 04:00:00



  Well, we converted our production Oracle6 (6.0.36) database to Oracle 7.1.3,
recompiled Pro*C apps (1300), tested for 4 days, and came up -- only to have
it fail within about 15 minutes with a disk buffer corruption error
(ORA-600 [3398]).  We (and Oracle support) cannot even get the database to
come back up so that we can trace the error. The trace files we do have contain
no file id/block id information.  Needless to say, we reverted
to Oracle6; it's a 12G database, but we had two copies of it available on
disk and going back was pretty easy.
  I've heard unofficially that data corruption errors were a problem in
the early 7.1 releases. Has anyone else had problems? If so, how
did you work around them? Unfortunately, 7.1.3. is the lastest version
available for our operating system (Amdahl UTS 2.1.5.). Our 7.1.3.
development system on Sun/Solaris has been running for a year or so,
and a 7.1.3. Amdahl/UTS read-only database has been up for 3 months. Any
hints or suggestions? Changing hardware/operating system platforms is not
an option; the Oracle V6 database on Amdahl/UTS was very stable. Please
reply via e-mail.

*********************************************************************
*           Cindy Mumford      (301) 622-0900 ext 304               *

*********************************************************************
--
*********************************************************************
*           Cindy Mumford      (301) 622-0900 ext 304               *

*********************************************************************

 
 
 

1. Oracle7 for Amdahl-IBM UTS

If anyone is even considering Oracle7 on a UTS 4.x system ---

_forget it_  

It don't work, and Oracle's supporting it in name only.  
If that's your OS, use another db vendor,
if you're married to Oracle, use another OS.

Marc

2. Help picking out equipment

3. ORA-600 [4097] - need help

4. Changing Focus in Win98

5. ORA-600 errors

6. Link error: IUMAgPString (One mode time)

7. Help:DCD Sometimes Lost

8. Have you ever had an ORA-600 [105] error when tracing?

9. ORA-600 Space Leak

10. ORA-600 Internal shared memory fragmentation - HELP!

11. Corrupt Primary Key index on table causing ORA-600 internal error