Studio Petrel 2020-1 ReleaseNotes

Studio Petrel 2020
Version 2020.1
RELEASE NOTES
Making knowledge work

Schlumberger-Private
Copyright Notice
Copyright © 2020 Schlumberger. All rights reserved.
This work contains the confidential and proprietary trade secrets of Schlumberger and may not be copied or
stored in an information retrieval system, transferred, used, distributed, translated or retransmitted in any form or
by any means, electronic or mechanical, in whole or in part, without the express written permission of the
copyright owner.
Trademarks & Service Marks

Schlumberger, the Schlumberger logotype, and other words or symbols used to identify the products and
services described herein are either trademarks, trade names or service marks of Schlumberger and its
licensors, or are the property of their respective owners. These marks may not be copied, imitated or used, in
whole or in part, without the express prior written permission of Schlumberger. In addition, covers, page
headers, custom graphics, icons, and other design elements may be service marks, trademarks, and/or trade
dress of Schlumberger, and may not be copied, imitated, or used, in whole or in part, without the express prior
written permission of Schlumberger. Other company, product, and service names are the properties of their
respective owners.
Studio® is a mark of Schlumberger. Petrel® is a mark of Schlumberger.

An asterisk (*) is used throughout this document to designate other marks of Schlumberger.
Security Notice
The software described herein is configured to operate with at least the minimum specifications set out by
Schlumberger. You are advised that such minimum specifications are merely recommendations and not
intended to be limiting to configurations that may be used to operate the software. Similarly, you are advised that
the software should be operated in a secure environment whether such software is operated across a network,
on a single system and/or on a plurality of systems. It is up to you to configure and maintain your networks
and/or system(s) in a secure manner. If you have further questions as to recommendations regarding
recommended specifications or security, please feel free to contact your local Schlumberger representative.
Schlumberger-Private 2
Contents
Distribution and Licensing ...................................................................................................................... 5
Distribution ......................................................................................................................................... 5
Licensing ............................................................................................................................................ 5
System Requirements ............................................................................................................................ 6
Studio Manager Plug-in compatibility ................................................................................................. 6
Runtime for Studio System Requirements ......................................................................................... 6
Studio Database System Requirements ............................................................................................ 7
For Oracle Databases .................................................................................................................... 7
For Microsoft SQL Server Databases ............................................................................................ 7
Studio Manager System Requirements.............................................................................................. 8
Studio Server system requirements ................................................................................................... 9
What’s New in Brief .............................................................................................................................. 10
Ocean for Studio .......................................................................................................................... 10
Studio Database........................................................................................................................... 11
Studio Manager ............................................................................................................................ 11
Known Issues ....................................................................................................................................... 13
Studio Manager ............................................................................................................................ 13
Workaround: Spatial filter error on a copied Oracle Studio repository .......................................... 16
The Studio E&P environment empowers a level of usability and productivity that supports an E&P
organization’s quest to streamline and optimize its workflow across the asset lifecycle, while also
capturing vital knowledge to maximize personal and team productivity. It features a powerful set of
tools that allow geoscientists and engineers to access, review, and use information in the context of
their workflows, providing three key capabilities that increase productivity.
• Find Your Information
Studio provides a fast, powerful and intuitive way to search, identify and consume information in the
context of your project and workflows. Filter multiple information sources on any value of metadata,
display results in a variety of ways, and either consume the information directly into your working
environment or share your results with others. Find empowers a new level of data discovery, putting
the information you need right where you need it.
• Collaborate with Your Team
Studio promotes collaboration by enabling team members to promote those elements of their project
that are of relevance to the rest of the team or business. Capturing the status and quality of
interpretation as it is published to Studio ensures integrity and reliability for other team members both
now and into the future. Subscribing to notifications on data of interest, team members can receive
alerts on the work of others that is relevant to their current workflow.
• Manage Your Knowledge
Studio provides a proven, scalable database supported by industry standard technology (Oracle® and
Microsoft® SQL Server®). It is specifically designed to handle E&P project data as well as the
knowledge related to that data, all stored together in context. This allows users to obtain better
retention and reuse of the generated knowledge.
Distribution and Licensing
Distribution
The Studio Petrel 2020 release is available by download using the appropriate links on the
Software Integrated Solutions (SIS) Software Download Center. A user account is required for access
to the center. If you do not already have a user account, you can register to access the Software
Download Center at https://www.software.slb.com/support.
Licensing
To run Studio Petrel 2020, you need valid licenses. The licenses can be configured either locally on
your computer or on a central license server. Studio Petrel 2020 requires Schlumberger Licensing
2017 or 2020, which is distributed on the Petrel DVD. The new tool is backward compatible with all
previous release versions. Schlumberger Licensing 2020 is based on Flexera™ FlexNet Publisher® to
provide a secure licensing solution. As Schlumberger controls the licensing and hardware key
shipments, all license inquiries should be made to your SIS account manager.
System Requirements
Studio Petrel 2020.1 has minimum system requirements for installation and use. Before installing the
products, ensure that your system meets the requirements described here.
Studio Manager Plug-in compatibility

Studio Manager should be installed with the latest release date version from either Techlog or Petrel to
ensure the compatibility of plug-ins.
Runtime for Studio System Requirements

Recommended
Operating System Windows 10 Pro or Enterprise (64-bit) is required
Other Required Software
• Microsoft .NET Framework 4.7.2 or newer is required
• Microsoft Visual C++ Runtime 2010, 2012, 2013, and 2019†
†installed silently on a non-Windows Server machine
Studio Database System Requirements
For Oracle Databases
Recommended
Operating System Red Hat® Enterprise Linux® 7.5 (64-bit), CentOS 7.5 (Kwin Windowing
Manager)
Processor x64 processor (dual six-core) (x64 processor [dual quad-core] minimum)
Memory 64 GB or greater (32 GB minimum)
Oracle Database Enterprise Edition 18c (64-bit)
For Microsoft SQL Server Databases

Recommended
Operating System Windows Server 2016 (64-bit)
Processor x64 processor (dual quad-core) (x64 processor [quad-core] minimum)
Memory 64 GB (32 GB minimum)
SQL Server 2016 SP1 Standard Edition (64-bit)
Studio Manager System Requirements
Note: For machines performing indexing, you should consider adjusting the memory requirement,
depending on the total number of projects, the size of the projects, and the number of data items in the
projects to be indexed. Please contact your local Schlumberger Studio support representative if you
need further advice on system requirements.
Recommended
Operating System Windows 10 Pro or Enterprise (64-bit) is required,
Windows Server 2016 (database configuration for SQL Server only) †
Processor Dual quad/six-core processor (Quad-core processor minimum) (best with a
fast clock speed and high cache)
Memory 48 GB DDR3 SDRAM (16 GB minimum)
Display Quality of the viewing experience increases with size and number of monitors
Graphics NVIDIA® Quadro® P6000 (NVIDIA Quadro P4000 minimum)
Primary Storage • Fast rotational speed HDD (10K, 15K)
• SSD
Secondary storage Optional
• Microsoft .NET Framework 4.7.2 or newer is required
• Microsoft Visual C++ Runtime 2010, 2012, 2013, and 2019††
• Microsoft System CLR Types For Microsoft SQL Server 2016 SP1
Standard(64-bit)††
• Oracle Database 18c Client for Microsoft Windows x64
(64-bit) (installed with Administrator option) is required if installing the
Studio Database on an Oracle database. The ORACLE_HOME variable
needs to be set properly and the %ORACLE_HOME%\bin location
needs to be included in the PATH variable.
† All users who run Studio Manager on their workstations must have read/write permissions to the
%ProgramData% folder, usually C:\ProgramData (used by internal application components, in
addition to indexing) and should also have access to the registry.
†† installed silently on a non-Windows Server machine and with a prompt on a Windows Server
machine
Studio Server system requirements
Recommended
Operating system Windows Server 2016 Standard (64-bit)
Processor x64 processor (dual six-core) (x64 processor [dual quad core] minimum)
Memory 64 GB or greater (48 GB minimum)
Web server IIS 10 for Windows Server 2016
Disk space 50 GB
Other required software
Microsoft. NET® Framework 4.7.2 or higher.
The ORACLE_HOME variable needs to be set properly and the
$ORACLE_HOME/bin location needs to be included in the PATH variable.
Several Microsoft SQL Server client components are required for a
successful connection with the SQL Server database.
Download the latest version that supports SQL Server 2016 for you operating
system:
• Microsoft ODBC Driver for SQL Server
• Microsoft Command Line Utilities for SQL Server
Microsoft Visual C++ Runtime 2010, 2012, 2013, and 2019
(installed silently on a non-Windows Server machine).
Download the SQL Server packages from the following URL:
https://www.microsoft.com/en-us/download/details.aspx?id=54279
The following is a summary of the files that you need:
• ENU\x64\msodbcsql.msi
• ENU\x64\MsSqlCmdLnUtils.msi
Note: The folder used for the Studio Logs should be monitored periodically and cleaned of
obsolete log files.
What’s New in Brief
Below are short descriptions of new features in Studio Petrel 2020.1, grouped by product name.
Ocean for Studio

Feature Short Description
Supports mismatch between The Studio SDK now supports a mismatch between a CRS of a
wellbore CRS and trajectory wellbore and a CRS of the trajectories of the wellbore. In other
CRS words, the Studio SDK allows creating a trajectory with trajectory
CRS different from the CRS of its parent wellbore. The trajectory
records are calculated accordingly for the mismatch scenario. This
feature is implemented for all trajectory data types except for
AutomaticPlanTrajectory and PlannedTrajectory.
A consistency rule was enforced in the past.
Add LINQ enabled property The LINQ enabled property IsTimeLog is now available for the
IsTimeLog log data types:
• WellLog
• TimeStepWellLog
• BoreholeSeismogram
New IsEmpty() API for collection The IsEmpty() method is now available for collection data types
data types to determine if there are any children within. It detects not only the
SDK supported data types such as Polygons, but also the data
types not yet supported by the SDK such as Geopolygons.
This feature is implemented for the following data types:
• Collection
• InterpretationCollection
• SeismicCollection
• SurveyCollection
• BoreholeCollection
• MarkerCollection
• TargetCollection
Enable SRD support for seismic The Studio SDK now supports read-only access to SRD data
logs (SrdReference and SrdShiftInfo) of seismic logs
(BoreholeSeismogram).
Supports importing SEG-Y files The Studio SDK now supports imports of SEG-Y files of Rev1
(seismic 2D data) with fractional format with fractional SP numbers (using the
SP numbers ISegyFormat.ImportSeismic2D API). The SP numbers
are extracted correctly with no truncation.
Upgrade ZgyEngine to use latest The ZgyEngine is upgraded to utilize latest version of Salmon
Salmon library library (same as Petrel). This allows the Studio SDK to take
advantage of performance improvements in Salmon.
Comments of Completion data The Studio SDK now saves Comments of Completion data types
types are saved correctly (CasingString, TubingString, Perforation,
Squeeze) correctly, and they display properly when sent to
Petrel.
FindTemplateByType works as The ITemplateService.FindTemplateByType API now
expected. returns correct values when a non-existent template type is
provided as input.
Correct Ocean license is The correct Ocean Framework license feature is checked out for all
checked out for all scenarios development scenarios including running Petrel, Studio Manager,
and standalone programs developed using the Studio SDK.
Studio Database
Database Upgrade The upgrade procedure for Studio Database supporting Petrel is
valid only from version 2018.x or 2019.x to 2020. If you have
previous versions of Studio Database, you must upgrade/update to
2018 / 2019 before upgrading to 2020.
Refresh tasks There are no refresh tasks.
Studio Manager
Data Footprint improvement The following data types are now supported in the Studio database to
enhance user workflow collaboration:
• Editable triangle mesh (Geophysics)
• Triangle mesh (Structural Framework)
• Corridor x-section (Geological Interpretation) polyline can be
transferred and stored in Studio, in the Data table Shape tab
under corridor X-section tab.
Seismic logs SRD info Seismic logs upgraded from Studio manager 2017 through 2018/2019
to 2020 shows blank SRD record but on transfer from Petrel to Studio
repository will have the SRD info updated
Global well logs data merge Newly merged global well log in the Global data app, now correctly
reassign source to target well log and updates the path attribute in the
Data table. Well logs merged in prior releases are not affected.
Find indexing configuration An option is available to Import existing data environment in the
upgrade Studio manager Shared indexing configuration settings dialog. This
removes manual editing of configuration files before upgrade.
Find filter based on relative Geoscientists can now search for objects based on the relative size of
object extent the extent of the object. This can be useful for workflows such as:
• finding surface objects which are relevant for the project area
(For example, filtering out objects which cover a large area.)
• finding objects of a specific size
• QA control: finding large or small objects, or to see if the size
of the objects in a search result varies (by looking at the
histogram)
• finding objects of roughly the same size
The filter is located under the geometry group and have a slider with
histogram display of the relative object size. The numeric value in the
filter is only a relative value, but it is roughly the length of the diagonal
across the extent in kilometers.
Securely store and prompt: It is now possible to add items which require basic authentication
user basic authentication (username and password) to a custom webmap gallery config file
details without having to put the actual username and password in the
configuration file. If the item is a ESRI portal, the user is prompted for
their username and password when the webmap gallery dialog is
opened. If the item is a specific map service, the user is prompted
when adding that service to the project.
Point well data merge An Admin, Super Admin, Repository Admin, or Petrel super user can
now merge point well from different well entries in the Global Data
App. Two or more source entries can be selected and merged into a
target.
2D line shape storage 2D lines saved with Studio Manager 2020 are now stored as a
multiLineString (and not in a GeometryCollectionWrapper). That
means they can now be mapped properly in tools such as ArcGIS
server.
WITSML Connector – Grid You can now stream well trajectories in Grid North azimuth reference.
North support for surveys The azimuth reference is automatically detected from the source but
can be selected by the user. If the azimuth reference source is
unknown, it defaults to True North.
Note: When streaming trajectories referenced in Grid North, the
borehole CRS of the Studio well must match the CRS of the source
WITSML trajectory. There is no support for trajectories referenced in
Magnetic North.
Known Issues
The following content summarizes known issues and limitations in Studio Petrel 2020.X, grouped by
product name.
Studio Manager
Affected Feature Issue or Limitation
Velocity model folders with Velocity models generated in different projects create different GUID
different GUIDs folders. When transferring these models to managed projects, the
Studio transfer tool recognizes them as different GUIDs and will try
to duplicate the folder which can lead to data mismatch.
Workaround: Select only the velocity models folder and transfer
from the managed project, then send any velocity models from the
project without generating duplicate folders.
Studio Manager Plug-in Studio Manager should be installed with the latest release date
compatibility version from either Techlog or Petrel to ensure the compatibility of
plug-ins.
Scheduled backups on Oracle In cases where Oracle client tools are not installed on the same
machine as the scheduled backup service, the first scheduled
backup will successfully complete but the next may fail.
Workaround: If this error is observed, you should install the Oracle
client tools and restart the scheduled backup service.
Generate repository statistics The Generate repository statistics check box in the Filter option
of Data source properties dialog box in Index Schedules app
does not persist after changing the connection to a new repository.
Workaround: If you click the Refresh data environments, the
check box is updated.
Data Table filter and sorting not The following columns do not support filtering and sorting in the Data
supported on some columns Table:
• SRD (m.m/s)
• SRD velocity(m/s)
• Time Shift (ms)
Switching Repositories An intermittent issue occurs where an error is thrown related to ‘User
Attributes application error...’ when switching connections within a
session or when launching Studio Manager when the previous
session left the User Attributes app open. Either close the user
attributes dialog or refresh to resolve the issue.
Command-line Backup Backing up a repository using the command-line backup utility does
not backup the managed projects. To ensure that after restoring a
Repository the full integrity of the repository is maintained and the
data in managed projects is available to users as part of the
repository, it is necessary to perform the following steps:
1. Compress the associated managed projects files for the
repository, which is being backed up in zip format (zipx or
other zip formats will not work) to create a single zip file
named ManagedProjects.Zip.
2. Place ManagedProjects.Zip into the backup folder
specified as the target folder for backup files.
3. Restore the repository, using the command line utility as
normal.
See the Studio Manager online Help for more information.
Editing User-defined Attributes When editing a user-defined well or well top attributes using the data
table, you will not receive a warning if an invalid data type is entered
for a specific field. (For example, entering a string value in a discrete
attribute field.) However, if an invalid data type is entered, you will
not be able to edit any other fields or save your changes until the
invalid entry is removed or changed to the valid data type.
Pinned Column Locations When a user-defined well or well top attribute column is pinned to a
given location within the data table, the pinned column location is not
maintained when adding additional columns to the table.
Region and Language settings When running Studio Manager plug-ins with Region and Language
settings on a laptop/desktop set to Norwegian or a different
language other than English United States format can cause
problems for the user.
User-defined Attributes When visualizing user-defined well or well top attributes within the
data table app, you will receive a warning if duplicate attributes exist.
However, if a user-defined attribute has the same name as an
existing system created attribute, you will not receive this warning.
Carefully QC the attribute data, as only one of the duplicate named
attributes will be displayed in the data table. This behavior is also
seen in the repository data table within Petrel.
Managed Project Upgrade Managed projects are not automatically upgraded with the
(Petrel) repository. The managed projects need to be upgraded using the
Managed Projects app to upgrade the project and enable the
transfer of managed objects in 2020.
Silent Uninstall Fails when When silently uninstalling Studio Manager, the indexing service must
Indexing Service is Running be stopped before the uninstall begins. If not, the silent uninstall will
fail because the indexing service is still running, and no error
message is displayed.
WITSML Connector The WITSML connector service must be manually installed, either
locally or on a server.
The Slb.Scc.Studio.WitsmlConnector.ServiceInstaller.msi
should be run from the installation directory:
C:\Program Files\Schlumberger\Studio Manager
2020\Plugins\WITSMLConnector
Note: Studio Database credentials should be entered in the app
settings.
Transfer of seismic logs SRD definitions for seismogram logs are not populated during
sampled in depth from Petrel to upgrade to 2020. They will assume the SRD of the receiving project
Studio and can be subsequently reassigned. When sent back to Studio the
SRD information will be correctly retained.
Corrupt path value for well data Using UWI as the well identifier in Petrel will result in the UWI being
when UWI is used for transfer used in the path when the well is transferred to Studio. If the name
and well is renamed of the well is subsequently updated in Studio, the path will be
updated incorrectly for all child data belonging to the well.
Workaround: Avoid updating well name in Studio manager when
the UWI is the primary identifier, or use the well name as the
identifier in Petrel before transferring it to Studio.
Inconsistent behavior in column You can encounter a different behavior when filtering on user-
filtering in user defined defined attributes in the Data Table on Oracle and SQL repositories.
attributes in the Data Table The percentage (%) acts as a multiple character wildcard and the
asterisk (*) is treated as literal character.
Underscore (_) cannot be treated as a literal character on SQL but
Oracle can use a backslash (\_) to treat an underscore as a literal
character.
Updating merged point well data When the attribute data from a source point well data is merged into
attribute a target, the source is deleted and the link between the source point
well data attribute and the target is lost. Any updates made against
the source point well data attributes are not preserved in Studio. It is
important to delete the source point well data in a Petrel project
before you transfer from Studio.
Accessing data from OneDrive: When the Spreadsheet loader is accessing a file to load from a
OneDrive shared drive, it can cause Studio manager to hang. It is
important to avoid accessing files from OneDrive while running the
Spreadsheet loader plug-in.
Spreadsheet Loader - user User-defined well attributes values loaded with the Spreadsheet
defined well attributes Loader are assumed to be in SI unit in the source file. This can lead
to data being converted during the import process. It is
recommended to manually convert user-defined well attributes to SI
units.
Spreadsheet Loader Upon loading a spreadsheet after the install, the default CRS is
copied from the repository storage CRS. This will cause errors if the
repository CRS is geographic and should be changed to Projected
CRS prior to executing a load.
Spatial filter error on a copied Repository filters with spatial conditions applied on a copy or
Oracle Studio repository restored Oracle repository display inconsistent results compared
with the original repository. The workaround during repository
backup is to record and restore USER_SDO_GEOM_METADATA
information in the copied repository from backup xml records. This
uses a locator system view USER_SDO_GEOM_METADATA that is
unique to each user. It contains spatial definitions for six tables
which is not captured in backup as it is not part of the repository
schema.
Reinsert the entries into the new schema and create the missing
indexes using the following workaround.
Workaround: Spatial filter error on a copied Oracle Studio repository
1. Execute the following select statement to see the data.
SELECT * FROM USER_SDO_GEOM_METADATA;
TABLE_NAME, COLUMN_NAME, DIMINFO,

SRID
========================================================================================================
===============================================================================
AREA_, SHAPE, ((X, -1000000, 1000000, 5E-5), (Y, -1000000, 1000000, 5E-5), (Z, -1000000,
1000000, 5E-5), (M, -1000000, 1000000, 5E-5)), NULL
BLOCKED_OBJ_MATCH_PARAM_, GEOMETRY_VALUE, ((X, -1000000, 1000000, 5E-5), (Y, -1000000, 1000000, 5E-5), (Z,
-1000000, 1000000, 5E-5), (M, -1000000, 1000000, 5E-5)), NULL
DBX_OBJECT_, SHAPE, ((X, -1000000, 1000000, 5E-5), (Y, -1000000, 1000000, 5E-5), (Z, -1000000,
1000000, 5E-5), (M, -1000000, 1000000, 5E-5)), NULL
LINE_, SHAPE, ((X, -1000000, 1000000, 5E-5), (Y, -1000000, 1000000, 5E-5), (Z, -1000000,
1000000, 5E-5), (M, -1000000, 1000000, 5E-5)), NULL
MULTIPOINT_, SHAPE, ((X, -1000000, 1000000, 5E-5), (Y, -1000000, 1000000, 5E-5), (Z, -1000000,
1000000, 5E-5), (M, -1000000, 1000000, 5E-5)), NULL
POSITION_, SHAPE, ((X, -1000000, 1000000, 5E-5), (Y, -1000000, 1000000, 5E-5), (Z, -1000000,
1000000, 5E-5), (M, -1000000, 1000000, 5E-5)), NULL
2. In the duplicated schema, insert the layers into the USER_SDO_GEOM_METADATA view.
Ensure that you are entering the table and column names in upper case as Oracle is case sensitive.
Match up the syntax as below from the data from the original schema.
INSERT into USER_SDO_GEOM_METADATA

VALUES (
'AREA_',
'SHAPE',
SDO_DIM_ARRAY(
SDO_DIM_ELEMENT('X', -1000000, 1000000, 5E-5),
SDO_DIM_ELEMENT('Y', -1000000, 1000000, 5E-5),
SDO_DIM_ELEMENT('Z', -1000000, 1000000, 5E-5),
SDO_DIM_ELEMENT('M', -1000000, 1000000, 5E-5)
),
NULL
);

VALUES (
'BLOCKED_OBJ_MATCH_PARAM_',
'GEOMETRY_VALUE',
SDO_DIM_ARRAY(
),
NULL
);

VALUES (
'DBX_OBJECT_',
'SHAPE',
SDO_DIM_ARRAY(
),
NULL
);

VALUES (
'LINE_',
'SHAPE',
SDO_DIM_ARRAY(
),
NULL
);

VALUES (
'MULTIPOINT_',
'SHAPE',
SDO_DIM_ARRAY(
),
NULL
);

VALUES (
'POSITION_',
'SHAPE',
SDO_DIM_ARRAY(
),
NULL
);
3. In the duplicated schema still, create the missing indexes that will have failed to import due
to the missing layers.
CREATE INDEX BLOCKED_OBJ_MATCH_PARAM__SI01 ON BLOCKED_OBJ_MATCH_PARAM_

(GEOMETRY_VALUE)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
NOPARALLEL;
CREATE INDEX POSITION__SI01 ON POSITION_

(SHAPE)
NOPARALLEL;
CREATE INDEX LINE__SI01 ON LINE_

(SHAPE)
NOPARALLEL;
CREATE INDEX DBX_OBJECT__SI01 ON DBX_OBJECT_

(SHAPE)
NOPARALLEL;
CREATE INDEX AREA__SI01 ON AREA_

(SHAPE)
NOPARALLEL;
CREATE INDEX MULTIPOINT__SI01 ON MULTIPOINT_

(SHAPE)
NOPARALLEL;
4. Recompile all invalid objects in the schema.
EXEC DBMS_UTILITY.compile_schema(schema => 'REPO');

Studio Petrel 2020-1 ReleaseNotes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Studio Petrel 2020-1 ReleaseNotes

Uploaded by

Copyright:

Available Formats

Studio Petrel 2020

Making knowledge work

Trademarks & Service Marks

Studio® is a mark of Schlumberger. Petrel® is a mark of Schlumberger.

• Find Your Information

• Collaborate with Your Team

• Manage Your Knowledge

Studio Manager Plug-in compatibility

Runtime for Studio System Requirements

For Microsoft SQL Server Databases

Ocean for Studio

Workaround: Spatial filter error on a copied Oracle Studio repository

1. Execute the following select statement to see the data.

SELECT * FROM USER_SDO_GEOM_METADATA;

TABLE_NAME, COLUMN_NAME, DIMINFO,

INSERT into USER_SDO_GEOM_METADATA

INSERT into USER_SDO_GEOM_METADATA

INSERT into USER_SDO_GEOM_METADATA

INSERT into USER_SDO_GEOM_METADATA

INSERT into USER_SDO_GEOM_METADATA

INSERT into USER_SDO_GEOM_METADATA

CREATE INDEX BLOCKED_OBJ_MATCH_PARAM__SI01 ON BLOCKED_OBJ_MATCH_PARAM_

CREATE INDEX POSITION__SI01 ON POSITION_

CREATE INDEX LINE__SI01 ON LINE_

CREATE INDEX DBX_OBJECT__SI01 ON DBX_OBJECT_

CREATE INDEX AREA__SI01 ON AREA_

CREATE INDEX MULTIPOINT__SI01 ON MULTIPOINT_

4. Recompile all invalid objects in the schema.

EXEC DBMS_UTILITY.compile_schema(schema => 'REPO');

You might also like