Supported Environments – Petrosys PRO

Supported environments for Desktop Petrosys PRO

Petrosys supports a wide range of computing environments. Mapping with Petrosys PRO is a natural way to bring together facts and ideas from a range of disciplines and data sources.

Petrosys PRO’s direct interfaces to many of the specialised applications used by EP professionals ensure that EP teams have better communication more quickly and with lower support and learning overheads than with older or more generic mapping systems.

Petrosys PRO Operating Systems Support

Petrosys PRO supports the following operating systems configurations:

Notes

1. Petrosys PRO is officially designed to operate on Red Hat Enterprise Linux. While we ensure compatibility with official RHEL versions, we also acknowledge that our product can function on alternative versions such as OracleLinux, AlmaxLinux, and RockyLinux. However, please note that the compatibility of these alternate versions may vary over time. Therefore, it is the responsibility of the individual installing the product to verify its compatibility with their specific system
2. Starting from the PRO 2024.1 version, Petrosys has limited its support for RHEL7 due to it reaching its “End of life” on June 30,2024. The RHEL7 version can be obtained only upon request by contacting us at support@petrosys.com.au. We fully support RHEL8. The RHEL8 installer is compatible with RHEL9 from 2024.1.

Petrosys Applications Connectivity

Petrosys supports an ever increasing set of import / export interfaces and direct connections to a wide range of EP packages.

Currently Petrosys supports links to the following third-party applications:

20232023.1.3No

Notes

1. Petrosys running under Microsoft Windows requires a Petrosys ‘SSH’ communication protocol to be configured to access some OpenWorks/SeisWorks data on a Linux server . From version 17.7, Petrosys is able to natively access Openworks R5000.8+ on Windows.
2. Petrosys recommends Oracle Database Server 18c (12.2.0.2) or higher. When running on Redhat Enterprise Linux or above you must ensure that all of Oracle’s system library dependencies are installed, particularly nss-pam-ldapd.
3. For Oracle Server version 11.2.0.2, or higher, Petrosys recommends clients consider some known hardware compatibility issues on certain Oracle brand hardware due to a serious bug introduced by Oracle in 11.2.0.2 that breaks Spatial functionality. Refer Oracle Bug 11686843.
4. For Oracle Server version 12.1.0.1 Petrosys requires patch set 18470311 & 18328186, or use version 12.1.0.2 or above. Note that as always new versions of Oracle should be tested in non-production environments to verify functionality before being rolled out to production servers.
5. If the Auto SQL Server Express option in IHS Kingdom V8.5sp2 and higher is used for a project, it is only possible to connect to it while the project is open in IHS Kingdom.
6. ‘Paradigm with Epos 4 Data Management’ was last supported in Petrosys version 17.5sp4 , ‘Paradigm 2011 to 2011.2 with Epos 4.1 Data Management’ were last supported in Petrosys version 17.7sp6.
7. DUG Insight version 4.5 has not been tested explicitly. However, it is expected to work at the same level as version 4.
8. Paradigm versions older than 15.5 are not supported on Windows 10 or at all from Petrosys PRO 2017.1
9. ArcSDE server connection compatibility can be quite complex due to the wide variety of underlying database vendors and versions. Please check with Petrosys support before upgrading your ArcSDE version or database versions.
10. Using Oracle 12 and later wallets is supported from version 17.8sp5 and later.
11. For GeoGraphix, a 64bit ODBC driver for Sybase is required and it is only possible to connect to a project while it is open in GeoGraphix.
12. ArcGIS Pro Add-In is not supported using dongle licensing. Contact support.
13. Paradigm versions 17,18,19 are not supported running Redhat Enterprise Linux 8 or above

See more on Hardware Requirements and the Connectivity Matrix