Oracle Linux64 libst_shapelib.so file size: ArcGISPro 3.0 to ArcGISPro 3.1

979
9
Jump to solution
05-10-2023 06:27 AM
JamesMorrison1
Occasional Contributor

Hello Everyone

I have been making tests in Oracle 19.16 using the Linux library downloaded last year and it was 11MB in size. Now I want to test with the newer version. I see the Linux file size is now  42MB. See info below and the enclosed image.

ArcGISPro_30_ST_Geometry_Oracle_182271   June 2022

IBM      16MB
Linux    11MB
Sun      26MB
Win      41MB

ArcGISPro_31_ST_Geometry_Oracle_185049   Feb 2023

IBM      16MB
Linux    42MB
Sun      27MB
Win      42MB

As you can see the Linux one seems to have changed 11MB – 42MB; whereas the others have not changed greatly.

Question 1 - if correct is there a reason for this file size increase in Linux?
Question 2 - when fellow Linux users download the libst_shapelib.so library what file size do you see?

Slightly confused. Help appreciated.

0 Kudos
1 Solution

Accepted Solutions
MarceloMarques
Esri Regular Contributor

It seems there were more changes to the Linux st_geometry  library, more code changes that were necessary for this platform specifically, then when the new version was compiled, the new file got bigger than the previous one.

| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov

View solution in original post

9 Replies
ChrisUnderwood
Esri Contributor

If you are worried that your file might have been corrupted during the download, you can use a Checksum to verify the file you have received is the same as Esri's original copy of the file.

https://support.esri.com/en-us/knowledge-base/how-to-verify-an-esri-download-using-the-checksum-0000...

(see section How to calculate the Checksum of a file (Linux))

JamesMorrison1
Occasional Contributor

Hi Chris

Thanks for the tip.

It seems the files we downloaded are correct. 
So can you explain the difference in file size for the Linux version?

0 Kudos
ChrisUnderwood
Esri Contributor

Always calculate your Checksum on the file exactly as downloaded, ie the .ZIP itself before extraction.

0 Kudos
JamesMorrison1
Occasional Contributor

Hi Chris

Thanks for the tip.

It seems the files we downloaded are correct. 
So can you explain the difference in file size for the Linux version?

0 Kudos
MarceloMarques
Esri Regular Contributor

At each release of ArcGIS Pro there will be a new version of the st_geometry library for each platform, Windows and Linux, and code changes can be introduced therefore the size of the st_geometry library file can change. I hope this clarifies.

| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov
JamesMorrison1
Occasional Contributor

Hi Marcelo. Thank you for the feedback. I assumed there would be some difference between ARcGIS Pro versions.  

However my question was directed at the Linux version: 11MB to 42MB. 

whereas the other flavours windows, sun etc only changed by 1MB or so. 

To me this seems a major update and if my size figures are correct I was querying why. 

 

0 Kudos
MarceloMarques
Esri Regular Contributor

It seems there were more changes to the Linux st_geometry  library, more code changes that were necessary for this platform specifically, then when the new version was compiled, the new file got bigger than the previous one.

| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov
JamesMorrison1
Occasional Contributor

Perfect thanks Marcelo. Appreciated. 

0 Kudos
VinceAngelo
Esri Esteemed Contributor

It seems likely (just based on 30+ years of Linux development, not with any direct knowledge)  that supporting DLLs changed (or were scheduled to change), and had to be folded into the release DLL to prevent an awkward package dependency chain.  It happens.

-  V