Re: V7.0 -> V7.1 any problems?

In article <3m3rjo$cso_at_CUBoulder.Colorado.EDU>, zhouf_at_rastro.Colorado.EDU (ZHOU FENGQUING) wrote:
>
> In article <3m1537$a05_at_blackice.winternet.com>,
> Carl Hoang <choang_at_winternet.com> wrote:
> >The process was not bad at all. No changes for the programs and
> >tables.
>
> How about for Solaris 2.3?
>
> I have a bad week to try upgrade from 7.0.16 to 7.1.4
> The problem is: connecttion from clients to server will get
> ORA-12500 error. The server is on Solaris 2.3 of course, but my clients
> may be Windows, OS/2 and Mac.
>
> Now my databse system is alomst useless since no client can connect
> to the server. I call ORACLE support everyday, but I get no call back.
>
> I would say that Oracle support could not be better. :-)
>
>
> >
> >okhuijsen_at_twice.nl (Stephan Okhuijsen) wrote:
> >
> >>We need to upgrade our version 7.0.16 RDBMS to version 7.1.4
> >>It's on a ICL DRS6000 with a sparc. Unix V 7.2
> >>Can this be done without any trouble, or are there certain things wich could
> >>go wrong.
> >>Comment and suggestions needed!
 

> >>Thanks
> >>Stephan
> >
> >

We ran into some oddities when we followed the migration path documented in the readme. If database size permits it, would recommend importing and exporting the database instead of trying to alter the existing data dictionary via the recommened sql scripts. We did not import/export our databases and kept running into oddities, no show stoppers, just headaches like having to regrant privileges and recreate roles. Once we imported/exported the problems ceased and 7.1.3 has been fine .
Steve Hoffman Consulting at Apple Computer Received on Thu Apr 13 1995 - 00:00:00 CEST