Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: AIX 4.3.3 , Oracle 7.3.4 coredumps at startup

Re: AIX 4.3.3 , Oracle 7.3.4 coredumps at startup

From: Sybrand Bakker <gooiditweg_at_sybrandb.nospam.demon.nl>
Date: Fri, 07 Nov 2003 06:16:18 +0100
Message-ID: <phamqv0riefnk5v4imf1psp78fock05ktq@4ax.com>


On Thu, 06 Nov 2003 20:08:44 -0600, lost in dbspace <nospam_at_nospam.yup> wrote:

>I need to move an Oracle 7.3.4 database and application from an old
>AIX 4.2.1 J40 machine to a newer p660 box that is running 4.3.3 of
>AIX. I cannot port the database to Oracle 8 or later since the app
>progs are closed-source (was written in cobol), the vendor is not
>around anymore, and they used variable names imbedded in the sql of
>the apps that are now reserved words in Oracle 8 and later. I
>installed the Oracle 7.3.4 from cdrom onto the new machine, did a
>clone-style copy of the database filles over but the instant you run
>svrmgrl and try to do a "startup nomount" to get ready to create new
>controlfiles, Oracle 7.3.4 instantly coredumps. Even when trying to
>build the default demo ORCL database during 7.3.4 installation, it too
>coredumps instantly when it tries to start the Oracle engine for the
>first time. A hand-built, fresh, empty database instance will not
>start either.
>
>The new machine already has Oracle 8.1.7 running on it, installed in
>another filesystem, and I'm using the proper /etc/pw-syscall version 3
>with support for both 32 and 64 bits. The AIX 4.3.3 is at ML9, and I
>have bos.rte.aio at version 4.3.3.75.
>
>Will Oracle 7.3.4 compiled for AIX 4.1/4.2 just simply not run on this
>new machine? The old machine had 7.3.4 and 8.0.5 running concurrently
>with no problems for a long time, but it's out of disk space now and I
>really need to get the database and apps onto the newer box since it
>has boatloats of disk space, ram, and cpu horsepower to spare.
>
>
>Any ideas?

The operative keyword here (can be verified from Metalink) probably is 'hasn't been certified against 4.3.3'. Remember 7.3.4 was around for several years when 4.3.3 was released and Oracle usually doesn't certify for newer releases on an O/S

--
Sybrand Bakker, Senior Oracle DBA
Received on Thu Nov 06 2003 - 23:16:18 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US