Error during upgrade geodatabase ArcSDE 9.2/Oracle 10 R2

10-10-2015 07:30 AM
New Contributor

I have an old ArcSDE 9.2 geodatabase built on Oracle 10g R2 with multiple geodatabases in users schemas and try to upgrade to ArcSDE 9.3.1.

I successfully upgraded the master SDE schema using the command:

sdesetup -o upgrade -d ORACLE10G -u sde -p **@ORCL -i 5151:sde

Then when I try to upgrade the geodatabase in schema named 'John' using the command

sdesetup -o upgrade -d ORACLE10G -u john -p **@ORCL -i 5151:john

I receive the following error:

[Wed Oct 07 14:21:53 2015] ST_Geometry Schema Owner: (SDE) Type Release: 1007

[Wed Oct 07 14:21:53 2015] Instance initialized for ((john)) . . .

[Wed Oct 07 14:21:53 2015] ArcSde is already at an acceptable release:


[Wed Oct 07 14:21:53 2015] S_insert_update_server_config_table():

     Error insert data to server_config table.

[Wed Oct 07 14:21:53 2015] Error inserting following data into Server Config table:

    Property name: CONNECTIONS

    Numeric property value : 64

[Wed Oct 07 14:21:53 2015] ERROR in upgrading server_config table.

Error: -51

[Wed Oct 07 14:21:53 2015] DBMS error code: 6550

ORA-06550: Line 1 , Column 26 :

PLS-00201: identifier 'JOHN.SVR_CONFIG_UTIL' must be declared

ORA-06550: Line 1 , Column 26 :

PL/SQL: Statement ignored

ORA-06550: Line 1 , Column 132 :

PLS-00201: identifier 'JOHN.SDE_UTIL' must be declared

ORA-06550: Line 1 , Column 119 :

PL/SQL: Statement ignored

[Wed Oct 07 14:21:53 2015]

    Property name C failed to load,

[Wed Oct 07 14:21:53 2015]  with Property value: 64

[Wed Oct 07 14:21:53 2015] SDE release upgrade not completed(-1).

[Wed Oct 07 14:21:53 2015] ERROR installing/upgrading ArcSDE, Error = -1


    server_config table exist in SDE schema and has property CONNECTIONS = 48

    There is SDE.SVR_CONFIG_UTIL and SDE.SDE_UTIL packages in SDE schema but not in John one.

Am I doing something wrong?

Tags (3)
0 Kudos
1 Reply
New Contributor III

Hi Rami,

I am doing the same thing. When you do the SDE upgrade it also upgrades all the schemas in the same database. That is why the SDE schema has to have all the 'ANY' permissions. You only have to do new upgrades for separate databases.

The upgrade reports that John is already in an acceptable release because it was upgraded by the SDE one.

0 Kudos