Hello Everyone Perhaps some one can help? We upgraded Oracle 19c eGDB from 11.1 to 11.4 using ArcGIS Pro 3.4 Reviewing the sde_setup.log TEST instance [17:11:48.176] SQL Stmt: [17:26:48.366] SQL Stmt: [17:41:48.510] SQL Stmt: [17:41:48.755] SQL Stmt: [17:56:48.895] SQL Stmt: [18:11:49.038] SQL Stmt: On a copy of our TEST instance for practice: [13:13:53.000] SQL Stmt: [13:13:53.214] SQL Stmt: [13:13:53.424] SQL Stmt: [13:13:53.633] SQL Stmt: [13:13:53.843] SQL Stmt: [13:13:54.054] SQL Stmt: So same amount of data just on separate Servers. Any idea why on our Test Instance it was taking 15 minutes to process each statement? Compared to the copy I made. I realise this may be hard to answer as our architecture is unknown or at least a good place to start looking. As next would be our Production instances. Thank you.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle 19c / ArcGIS Pro 3.4: upgrade sde_setup.log

JamesMorrison1

Hello Everyone

Perhaps some one can help?

We upgraded Oracle 19c eGDB from 11.1 to 11.4 using ArcGIS Pro 3.4

Reviewing the sde_setup.log

TEST instance

[17:11:48.176] SQL Stmt: <ALTER TYPE SDE.st_geometry drop constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,semiMajorAxis number,semiMinorAxis number,angle number,numpts number,srid number)Return self AS result deterministic cascade >
[17:26:48.366] SQL Stmt: <ALTER TYPE SDE.st_geometry drop constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,radius number,numpts number,srid number)Return self AS result deterministic cascade >
[17:41:48.510] SQL Stmt: <ALTER TYPE SDE.st_geometry drop constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,startAngle number,endAngle number,outerRadius number,innerRadius number,numpts number,srid number)Return self AS result deterministic cascade >
[17:41:48.755] SQL Stmt: <ALTER TYPE SDE.st_geometry add constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,semiMajorAxis number,semiMinorAxis number,angle number,numpts number,srid integer)Return self AS result deterministic cascade >
[17:56:48.895] SQL Stmt: <ALTER TYPE SDE.st_geometry add constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,radius number,numpts number,srid integer)Return self AS result deterministic cascade >
[18:11:49.038] SQL Stmt: <ALTER TYPE SDE.st_geometry add constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,startAngle number,endAngle number,outerRadius number,innerRadius number,numpts number,srid integer)Return self AS result deterministic cascade >

On a copy of our TEST instance for practice:

[13:13:53.000] SQL Stmt: <ALTER TYPE SDE.st_geometry drop constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,semiMajorAxis number,semiMinorAxis number,angle number,numpts number,srid number)Return self AS result deterministic cascade >
[13:13:53.214] SQL Stmt: <ALTER TYPE SDE.st_geometry drop constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,radius number,numpts number,srid number)Return self AS result deterministic cascade >
[13:13:53.424] SQL Stmt: <ALTER TYPE SDE.st_geometry drop constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,startAngle number,endAngle number,outerRadius number,innerRadius number,numpts number,srid number)Return self AS result deterministic cascade >
[13:13:53.633] SQL Stmt: <ALTER TYPE SDE.st_geometry add constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,semiMajorAxis number,semiMinorAxis number,angle number,numpts number,srid integer)Return self AS result deterministic cascade >
[13:13:53.843] SQL Stmt: <ALTER TYPE SDE.st_geometry add constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,radius number,numpts number,srid integer)Return self AS result deterministic cascade >
[13:13:54.054] SQL Stmt: <ALTER TYPE SDE.st_geometry add constructor function st_geometry (center_x number,center_y number,center_z number,center_m number,startAngle number,endAngle number,outerRadius number,innerRadius number,numpts number,srid integer)Return self AS result deterministic cascade >

So same amount of data just on separate Servers.

Any idea why on our Test Instance it was taking 15 minutes to process each statement? Compared to the copy I made.

I realise this may be hard to answer as our architecture is unknown or at least a good place to start looking. As next would be our Production instances.

Thank you.

Najděte více příspěvků označených jako

Enterprise geodatabase

Databases

Geodatabase Administration

Accepted answers

VinceAngelo

It's been decades since my last Oracle upgrade, but sometimes they run long, and it's hard to predict, with side-by-side systems that ought to be identical, which one will be the slow child.

- V

All comments

VinceAngelo

The undefined environment makes identifying a cause challenging. Is the database on-prem on in the cloud? Is the workstation on-prem or in the cloud? If in the cloud, is it in the same neighborhood (subnet)? A full architecture diagram of both execution environments could be useful.

- V

JamesMorrison1

Hello Vince

Yes I realised my posting my lacking in detail. Sorry.

No cloud.

ArcGIS Pro Windows - Work's Enclosed Network - Oracle on Linux. No difference between either instances.

Probably asking how long is a piece of string but all the upgrades I have made over the years were less than 10 minutes. Is this the general picture for most users too?

VinceAngelo

It's been decades since my last Oracle upgrade, but sometimes they run long, and it's hard to predict, with side-by-side systems that ought to be identical, which one will be the slow child.

- V

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Všechny komunity
Nedávné příspěvky
Sledovaný obsah
Pomoc komunity

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.