Upgrade ArcSDE from 9.1SP3 to ArcSDE 92Sp6 failed without detailed log info.

[sandrawang]

Hi,
I am working on a migration project that move a old Oracle SDE database from Sun solaris database/SDE into new Linux enviorment .
Here's the situation:
Old database: Oracle 9.2.0.7 (32 bit) in Solrais (SunOs 5.9 Generic_122300-08).
Old SDE : 9.1SP3 (32 bit) in same amchine with Oracle adtabase.

New enviorment:

Oracle database 9.2.0.8 64bit Linux (Linux version 2.6.9-67.ELlargesmp, Red Hat 3.4.6-8)

ArcSDE 92Sp6 32 bit (Linux version 2.6.9-78.ELsmp, Red Hat 3.4.6-10).

After I set up database (using export/import ) and I tried to run :
sdesetup -o install -d ORACLE9I -u sde -p xxxxx

I got memory fault error.
================================

hlin185{sde} $  sdesetup -o install -d ORACLE9I -u sde -p xxxx

ESRI ArcSDE Server Setup Utility Mon Oct  4 10:56:36 2010
----------------------------------------------------------------
Install or update ArcSDE schema objects: Are you sure? (Y/N): Y
Creating ArcSde schema.....
Memory fault
=======================================================

Here's the sde_setup.log error:
==[Mon Oct  4 10:21:37 2010]
ST_Geometry Schema Owner: () Type Release: 0
[Mon Oct  4 10:21:37 2010] Instance initialized for ((sde)) . . .

[Mon Oct  4 10:53:11 2010]
ST_Geometry Schema Owner: () Type Release: 0
[Mon Oct  4 10:53:11 2010] Instance initialized for ((sde)) . . .

[Mon Oct  4 10:56:38 2010]
ST_Geometry Schema Owner: () Type Release: 0
[Mon Oct  4 10:56:38 2010] Instance initialized for ((sde)) . . .
==========================================================

Doesn't content any error that I tried to look for.


However, the I did test and drop the SDE schema and let the SDESETUP to create the SDE schema
and it works. Looks like something really doesn't been liked in my old SDE schema. But I just don't know why and how to fix it.

Anybody has any idea ?

I really appreacite your help.

Many Thanks in advance.

Sandra Wang
Chevron
832-854-6097

[VinceAngelo]

No SP3 was ever released for 9.1. Is your old ArcSDE "9.1sp2 General Update 3"?

Upgrading to 9.2sp6 on 9iR2 at this late date is setting yourself up for an imminent
upgrade, since 9.2 is in mature status and 9iR2 isn't supported by Oracle. Heck, as
of July, 10gR2 isn't supported either (you'd need ArcSDE 9.3.1 to support 11gR1).

It's likely that the lack of logs indicates ArcSDE didn't really even start before the
OS fataled the application (which in turn indicates an improper application
configuration). What is the version of your Oracle 32-bit client install (required
for 32-bit ArcSDE).

If you imported all the users (including SDE) with exp/imp, then you certainly don't
want the '-o install' option -- use '-o upgrade' instead (after you make sure that
SDE has the required permissions). You might be better served by dropping the SDE
user, working on installing 9.2sp6 cleanly, then imp-ing SDE again to do an upgrade.

- V

[sandrawang]

Thanks for the reply.
Despite of the upgrade situation we had and oracle version we had which is desupported in old server due to the big company's historyic reason. right now, we just tried to move to th new server to free up license as well as decommissioned server.

Answer your question:
1. First about the old server's SDE version:
I just take over this DB/SDE and from the installation log of software, I did see it show 9.1Sp3. check with SDE.version table, it also shows release is 91003 (desc: Oracle9i  Build 1382 Wed Apr 19 15:01:47 PDT 2006), I am not sure is that means 91Sp2 or 91Sp3.

however, despite of the old version, I am totally move to a new enviorment and I tried to using sdesetup -o upgrade already, it shows the same error.

2. If I drop the SDE schema, and let sdesetup to recreate SDE meata data, it will work and I was able to bring up the SDE.
the reason I import the whole database (inculind SDE schema), because I don't want to re-export layer and re-import each of them so I can bring up datbaase and SDE without second work to do. I did this in past for my other databases/SDE, it all works fine .

Thanks for your help.

Sandra

[sandrawang]

I fingered out the installation directory name is misleading and it actully is SDE9.1Sp2 general updates 3. Thanks for help me to find out this.

[VinceAngelo]

There is no direct correspondence between the release number and service pack. Releases
are usually incremented during development, so that sometimes "Final" will be as high as
xy003 or xy004. I always name my install directories with the release version and service
pack so I can keep things straight (I usually have two or three *dozen* SDEHOMEs in my
ESRI directory, so using a naming convention is not optional). You can use the service pack
finder on Windows hosts to determine the actual product version.

I suggested that you drop the SDE user to simplify your problem. No install should ever
receive a "memory fault", so not having to work with an upgrade can sometimes isolate
the actual problem.

At this point you'd probably be better off contacting Tech Support to walk you through the
trouble-shooting process.

- V

[sandrawang]

Thanks for the suggestion again. That's my Plan B as well.

We finally solved this issue by using the Oracle 10g client (instead of Oracle 9i) also using SDE software of SDE92SP6 for Oracle 10g (instead of SDE92SP6 for Oracle 9i). At the begining I thought that ESRI's software SDE version for Oracle that always meant Oracle database version , For example: SDE92 for Oracle 9i means for Oracle 9i database not the Oracle client were be using.  But I got impression that seems actully mean oracle client in my case, That is : Oracle database itself is 9iR2 but in seperate machine with ArcSDE server.  I also use the sdesetup -o upgrade -d ORACLE10G -u sde -p xxxx and able to upgrade the SDE schema sucesfully also brougt up the SDE services.


Sandra

[VinceAngelo]

You really ought to use the same client as the server (Oracle 9.2.0.8 32-bit client with ArcSDE
for Oracle 9i 9.2sp6 to connect to a 9.2.0.8 server).  If you were using an early/buggy
Oracle 9.2 client (not one patched to 9.2.0.8), that would explain the memory error.

- V