Version 2013

Oracle Database Manager Guide

Copyright © 2003-2015 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 trademarks,
trade names or service marks of Schlumberger and its licensors, or 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.
An asterisk (*) is used throughout this document to designate a mark of
Schlumberger.

Schlumberger Private - Customer Use

iv Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

Contents
1 Information Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Seabed Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

About Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Document Last Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Typestyle Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Alert Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Contacting Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Seabed Oracle Database Manager Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Who Uses Seabed Oracle Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
After Installation and Before You Begin Using Seabed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Starting Seabed Oracle Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Launching Seabed Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Connecting to Seabed Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Navigating Seabed Oracle Database Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Refreshing Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Menu Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Object Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Accessing Seabed Features from a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Configuring FlexNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Configuring ArcSDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Esri Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

4 Dictionary Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Navigation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Contents v
Schlumberger Private - Customer Use
 Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Object Tree Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Managing Data Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Viewing Available Data Dictionaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Creating a Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Updating a Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Deleting a Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

5 Project Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Navigation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Object Tree Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Project Management Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Recreating Spatial Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
SDE Reset Layer Extent Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Setting the Recommended CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Using Auto GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

6 Staging Area Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Navigation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Object Tree Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Staging Area Management Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Creating a Staging Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Freeing a Staging Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Deleting a Staging Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

7 Interface Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Navigation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Object Tree Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Managing Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Creating an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Deleting an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Recreating Spatial Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

vi Seabed Oracle Database Manager Guide v1.0 April 2014

Schlumberger Private - Customer Use

8 User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Registered Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Navigation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Object Tree Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Creating a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Deleting a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Changing the Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Changing Special Seabed Oracle Account Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Registering a Seabed User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Unregistering a Seabed User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Granting Project Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Granting Administrator Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Granting Authority to Create other Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Revoking Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Creating Project Access – Granting Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Deleting Project Access – Revoking Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Maximum Enabled Database Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

9 Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Seabed Storage Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Storage Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Storage Configuration Locking and Copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Navigation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Object Tree Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Managing Storage Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Creating a Storage Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Editing a Storage Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Copying a Storage Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Deleting a Storage Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

10 Reference Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Contents vii
Schlumberger Private - Customer Use
 Reference Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Reference Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Appendix A Coordinate System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Standards Organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Spatial Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Coordinate System Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Functional CRS Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Spatial Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Appendix B Match Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Managing Match Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C Oracle Tablespace Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Overview of Oracle Logical Database Storage Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Tablespace/Data File Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Automated File and Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Managing Disk Space Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
LOB Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Seabed Storage Configuration System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Reclaiming Unused Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Reclaiming Tablespace in Seabed DBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Partitioning Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7

Appendix D Standard Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-1

Seabed Accounts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Seabed Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-5
Account Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-14

Appendix E Useful Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

viii Seabed Oracle Database Manager Guide v1.0 April 2014

Schlumberger Private - Customer Use

 1 Information Resources

In This Chapter

Seabed Documentation ............................................................................... 1-2

About Schlumberger ............................................................................. 1-2
Document Last Updated........................................................................ 1-2
Online Documentation .......................................................................... 1-2
Typestyle Conventions .......................................................................... 1-2
Alert Statements .................................................................................. 1-2
Contacting Schlumberger ............................................................................ 1-3
Technical Support ................................................................................. 1-3

Information Resources 1-1

Schlumberger Private - Customer Use
Seabed Documentation

Seabed Documentation

About Schlumberger is the leading oilfield services provider, trusted to deliver superior
Schlumberger results and improved Exploration and Production (E&P) performance for oil and gas
companies around the world. In research and engineering facilities, and through
wellsite operations, Schlumberger develops products, services, and solutions that
optimize customer performance in a safe and environmentally sound manner.

Document Last April 2015

Updated

Online Seabed* documentation is provided as Adobe® Acrobat® PDF files on the

Documentation Schlumberger product CD.

You must have Adobe® Reader® installed to view the PDF files. You can download a
free version of Adobe Reader from the Adobe Web site at www.adobe.com.

Typestyle The following conventions are observed throughout this guide:

Conventions
• Bold text is used to designate file and folder names, dialog box titles, names of
buttons, icons, menus, and terms that are objects of a user selection.
• Italic text is used for word emphasis, defined terms, and manual titles.
• Monospace text (Courier) is used to show literal text as you would enter it, or
as it would appear onscreen.

Alert Statements The alerting statements are Notes, Cautions, and Warnings. These statements are
formatted in the following style:

• • • • • •
Note: Provides information that is incidental to the main text flow – or to an
important point or tip – provided in addition to the previous statement or
instruction.

• • • • • •
Caution: Advises of a machine or data error that could occur should the user fail
to take (or avoid) a specified action.

• • • • • •
Warning: Requires immediate action by the user to prevent actual loss of data;
indicates where an action is irreversible; or alerts that physical
damage to the machine or devices is possible.
1-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Contacting Schlumberger

Contacting Schlumberger

Technical Support Schlumberger has sales and support offices around the world. For information on
contacting Schlumberger, please refer to the information below.
For Technical Support for SIS software:
• Schlumberger Support Portal:
http://support.software.slb.com/Pages/Overview.aspx
• Customer Care Center e-mail: [email protected]
• Phone Support:
- SIS Support (main)
http://support.prod.software.slb.com/pages/SupportContacts.aspx

Information Resources 1-3

Schlumberger Private - Customer Use
Contacting Schlumberger

1-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 2 Overview

In This Chapter

Introduction ............................................................................................... 2-2

After Installation and Before You Begin Using Seabed ................................... 2-3
Starting Seabed Oracle Database Manager ................................................... 2-4
Navigating Seabed Oracle Database Manager ............................................... 2-6
Menu Options............................................................................................. 2-8
Object Tree ................................................................................................ 2-9

Overview 2-1
Schlumberger Private - Customer Use
Introduction

Introduction
This guide discusses the functionality of the Seabed Oracle Database Manager,
which is a graphical user interface (GUI) that enables your database administrator to
create and manage data dictionaries, projects, user accounts, security, storage,
reference data, match rules, and entitlements for the Seabed database.

Seabed Oracle Seabed Oracle Database Manager provides the following features:
Database Manager
• User administration
Features
• Project administration (includes Interface Administration and Staging Area
Administration)
• Data Dictionary administration
• Storage management
• Match rules
• Configuration (setting the FlexNet™ License Path and configuring ArcSDE™)

Who Uses Seabed The primary roles for Seabed Oracle Database Manager users are as follows:
Oracle Database
Table 2-1 Seabed Oracle Database Manager Users
Manager

Role Description
Seabed This role uses Seabed Oracle Database Manager to perform post-
Administrator installation tasks that are required before using Seabed for E&P
accounts. Managers of E&P accounts must use Seabed Oracle
Database Manager to perform administrative tasks on a database.
The Oracle DBA grants privileges to perform these tasks.
Oracle Many companies have one or more dedicated DBAs who create and
Database manage Oracle® databases and perform database diagnostic and
Administrator troubleshooting tasks. The DBA uses Seabed Oracle Database
(DBA) Manager to perform the administration tasks. The DBA needs an
understanding of Oracle terminology and concepts, and should be
familiar with the setup and configuration of Oracle databases.
Application The application developer primarily interacts with the Oracle
Developer Database Manager through the underlying API by integrating
portions of the administrative capabilities into application-specific
workflows. The application developer needs a basic understanding
of Oracle terminology, including how to invoke the API within the
programming language.

2-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 After Installation and Before You Begin Using Seabed

After Installation and Before You Begin Using Seabed

Before working with E&P data using Seabed, you must complete the following steps:
1. Start Seabed Oracle Database Manager (refer to “Starting Seabed Oracle
Database Manager” on page 2-4).
a. Log in using the SDS_SYS or SIS_ADMIN account.
b. (Recommended) Create personal Seabed administrative user account(s) to
use with Seabed Oracle Database Manager (refer to “Creating a User
Account” on page 8-4). Grant these users administrative access (refer to
“Granting Administrator Privileges” on page 8-10). You can then use any
personal administrative account to perform the remaining steps and ongoing
account maintenance.

• • • • • •
Note: You should not use the SDS_SYS or SIS_ADMIN accounts to administer
Seabed on an ongoing basis. These accounts should be used exclusively to
create individual user accounts for each administrator.

c. (Optional) If not already done, install and configure ArcSDE 10.0 (SP1) (refer
to “Configuring ArcSDE” on page 3-3).
d. If not already done, install and configure FlexNet 11.6 (refer to “Configuring
FlexNet” on page 3-2).
2. Create a data dictionary (refer to “Creating a Data Dictionary” on page 4-5).
3. (Optional) Create storage configurations. Although optional, these storage
configurations are recommended setups for large projects (refer to “Creating a
Storage Configuration” on page 9-8).
4. Create a project account (refer to “Creating a Project” on page 5-4).
5. Create a staging area (refer to “Creating a Staging Area” on page 6-3).
6. (Optional) Create an interface account (refer to “Creating an Interface” on page
7-3).
7. Create all required user accounts (see “Creating a User Account” on page 8-4).
8. Grant project or interface access (see “Granting Project Access” on page 8-10).

Overview 2-3
Schlumberger Private - Customer Use
Starting Seabed Oracle Database Manager

Starting Seabed Oracle Database Manager

You can start the Seabed Oracle Database Manager using either the Windows®
interface, or the Linux® command line interface. You can use the File menu to
connect or disconnect from the database server or exit the application.

Launching Seabed Use the following procedures to launch Seabed Oracle Database Manager in
Database Manager Windows and Linux operating systems.
In Windows:
Select Start > Programs > Schlumberger > Seabed > Seabed Oracle
Database Manager.
In Linux:
Run the following executable:
$SDS_HOME/bin/DBAdmin
(where $SDS_HOME is the SDS_HOME directory)

Connecting to Use the following steps to connect to a Seabed database.

Seabed Database

 To Connect to a Seabed Database

1 Launch Seabed Oracle Database Manager to display the login dialog box.

Fig. 2-1 Seabed Oracle Database Manager Login

• • • • • •
Note: To access a different Seabed database, refer to Step 7 below.
2 If you are logging into Seabed Oracle Database Manager for the first time,
specify the target Seabed database in the Database field using the following
format:
<DBServer host name or IP address>:<listener port number>/
<service name>
where, <service name> is the name of the oracle service that is running on the
‘server’. In the tnsnames.ora, this value will be represented as
SERVICE_NAME, for example,
2-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Starting Seabed Oracle Database Manager

VM2013 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ip-address)(PORT
= port))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = service-name)
3 If logging into a local installation, enter “localhost” for the host name. If you
are reconnecting to a Seabed database that has been accessed previously, click
the Search button next to the Database field and then select one of the
five most-recently accessed Seabed databases.
4 If personal user Administration accounts have been created in the target
Seabed database, after selecting or entering database information, click the
Search button next to the Login field and select the appropriate
administrator from the list.
If personal user Administration accounts have not been created, you will not be
able to access a list of such accounts, and you need to enter SDS_SYS or
SIS_ADMIN in the Login field. These accounts are not selectable because their
general use is discouraged.
5 Enter the Password for the Seabed administrative account.
6 Click OK to connect to the database server.

• • • • • •
Note: The entire login process might be disabled when Seabed Oracle Database
Manager is launched through another application.

7 If you are currently connected to a Seabed database, but want to switch to a

different Seabed database, first disconnect from the current Seabed database
(File > Disconnect), and then select File > Connect to access the login
dialog box. When logging back in, select a new database.
8 You can exit this application at any time by choosing File > Exit.

Overview 2-5
Schlumberger Private - Customer Use
Navigating Seabed Oracle Database Manager

Navigating Seabed Oracle Database Manager

To access the various types of operations in Seabed Oracle Database Manager, you
can use either the menu bar or the object tree. Either way, you must first focus the
view on the appropriate type of information.
You can focus on the following broad categories of operation types:
• Data Dictionaries and Projects
• Storage
• Users and Security

 To Focus the View

If you need to perform actions on data dictionaries and projects, for example, you
can focus the view using either of these two methods:
• From the Object Tree Header, select Dictionaries and Projects.

Fig. 2-2 Object Tree Header Selection

• From the menu bar, select View > Dictionaries and Projects.

Fig. 2-3 View Menu Options

Changing the focus using either of these methods changes the options
available in the object tree, as well as the options available on the Tools menu.

• • • • • •
Note: If Seabed Oracle Database Manager is launched from another application,
some of the View menu options and functionalities might be disabled.

2-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Navigating Seabed Oracle Database Manager

Refreshing Views The refresh command updates the object tree with the latest information in the
database. You can manually refresh the object tree to see any changes made by
other users.

 To Refresh the Data Dictionaries and Projects View

1 Navigate to the Data Dictionaries, Storage, or Users/Security node.
2 Right-click the particular object type node you want to refresh.

Fig. 2-4 Object Tree Pop-up Menu

3 Select Refresh.
Any change made to the object tree since the last refresh will display in the
object tree.

Overview 2-7
Schlumberger Private - Customer Use
Menu Options

Menu Options

Menu Functions Table 2-2 explains the Seabed Oracle Database Manager menu options.
Table 2-2 Seabed Oracle Database Manager Menu Options

Menu Item Menu Option

File • Connect (to database)
• Disconnect (from database)
• Exit (Seabed Oracle Database Manager)
Edit • Cut
• Copy
• Paste
View This menu focuses the Tools menu on certain operation types:
• Dictionaries and Projects
• Storage
• Users/Security
Tools The following Tools menu options are available with the
indicated View menu selections:
View > Dictionaries and Projects
• Create (Data Dictionary, Project, Interface, Staging)
• Delete (Data Dictionary, Project, Interface, Staging)
• Free Staging
• Set Recommended CRS
• Create Spatial Layers (if ArcSDE is installed and configured)
• Define Match Rules (available only through the View menu)

View > Storage

• Storage Configurations (Create, Copy, Edit, Delete)

View > Users/Security

• Create User
• Delete User
• Change Password
• Grant (privileges)
• Revoke (privileges)

The following Tools menu options are always available:

• ArcSDE Configuration
• FlexNet License
Help Provides information on your version of Seabed Oracle Database
Manager.

2-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Object Tree

Object Tree
The object tree contains nodes for account types and actual accounts.
For example, the Data Dictionaries node contains data dictionary accounts.
Individual data dictionaries contain projects and staging area accounts. Individual
project nodes contain Interface nodes, which contain auxiliary interfaces.

Nodes

Fig. 2-5 Object Tree Nodes

• • • • • •
Note: If the function you need is not displayed, confirm that you are on the
correct node. For example, you cannot create a project by right-clicking an
existing project node. You must right-click the Projects node in the
appropriate data dictionary.

If you believe you are on the correct node, but right-clicking does not
reveal a menu, repeat the right-click. The first attempt might have
“focused” you to this area of the window without selecting the node.

Account nodes are the actual accounts. For example, DD1 is an actual data
dictionary; PROJ01 and PROJ02 are actual projects. Each account inherits the
characteristics of the account type node. A grey circle in front of a node indicates
that the node is empty.
In general, right-click an account node to perform an action on that account, and
right-click an account type node to create an account of that type.

Overview 2-9
Schlumberger Private - Customer Use
Object Tree

Accessing Seabed Right-click a node to view available Seabed features for the node. For example, you
Features from a can right-click a project node (Fig. 2-6) to see the Seabed features available for that
Node node. If a menu item is disabled, that menu item (such as Create Spatial Layers) is
not available. Different types of nodes access different Seabed functionalities.

Seabed features
available from
pop-up menus

Fig. 2-6 Accessing Seabed Features from a Node

• • • • • •
Note: The Register and Unregister Users feature is available only through the
object tree.

2-10 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 3 Configuration

In This Chapter

Introduction ............................................................................................... 3-2

Configuring FlexNet .................................................................................... 3-2
Configuring ArcSDE .................................................................................... 3-3

Configuration 3-1
Schlumberger Private - Customer Use
Introduction

Introduction
You can use Seabed Oracle Database Manager to configure FlexNet licenses and
ArcSDE (to enable management of spatial geographical data).

Configuring FlexNet
Before you can configure FlexNet, a FlexNet 11.6-compatible license server must be
installed.

 To Configure FlexNet
1 From the Seabed Oracle Database Manager interface, select Tools > 
Options > FlexNet License.
2 On the FlexNet Configuration panel, enter the license path to the license
server or the group of license servers in use (refer to FlexNet documentation
for more information).
Enter the “port at” (hostname) server value for your FlexNet 11.6-compatible
license server, using the following format: <port#>@<IP_Address>

Fig. 3-1 FlexNet Configuration

• • • • • •
Note: The server name can be either the name (recommended) or the IP
address of the machine.

3-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Configuring ArcSDE

When entering a hostname, use the fully qualified hostname that uniquely identifies
the machine (for example, mymachine.mycompany.com). If a fully qualified
hostname is not entered, and the machine is not configured to append the DNS
suffixes used in your environment, attempts to connect to the license server will fail.

• • • • • •
Note: Be sure your license server path points to the latest valid Seabed license.

If you need to change licensing information after the initial configuration, perform
the following steps on the client utilities and the Seabed database.
Client Utilities
• In Linux, modify the LM_LICENSE_FILE setting in $SDS_HOME/.seabed,
source the .seabed file, and delete the FLEXlm registry file named .flexlmrc
in your home directory (CD <enter>).
• In Windows, modify the LM_LICENSE_FILE environment variable and if present,
delete the associated registry entries. Delete the registry entries for
*_LICENSE_FILE, where * might be LM, SLB, or LMGRD.SLB by selecting
HKEY_LOCAL_MACHINE > SOFTWARE > FLEXlm License Manager.
Seabed Database
• You must change licensing information in the Seabed Oracle Database Manager
(Tools > Options > FlexNet License). When you have changed license
information, you will need to restart your Oracle instance.

Configuring ArcSDE
If you plan to store spatial data using Seabed, you must install and configure the
ArcSDE server software, which is provided by Esri. This product is used to spatially
enable a relational database management system so that geographical information
and spatial data can be stored, queried, and manipulated via the database.
You can connect to the ArcSDE geodatabase using one of two methods: ArcSDE
service, or ArcSDE Direct Connect. With ArcSDE service, the service must be running
in order to enter or change configuration parameters. With ArcSDE Direct Connect, a
full Oracle client and ArcSDE client must be installed on each applicable client
machine.
Direct Connect offers the advantage of a direct connection to the database without
requiring a dedicated ArcSDE server.

• • • • • •
Note: If you intend to use Seabed to store spatial data, ArcSDE must be
configured before you create any projects. When ArcSDE is installed and
configured properly, it is enabled.
Regarding this note, the following limitations should be observerd:
• ArcSDE cannot be enabled or disabled after a project is created.
• If ArcSDE is enabled and a project exists, you cannot disable ArcSDE.

Configuration 3-3
Schlumberger Private - Customer Use
Configuring ArcSDE

• If ArcSDE is disabled and a project exists, you cannot enable ArcSDE.

• If projects are already created and you want to enable ArcSDE, you must delete
all projects before proceeding.

 To Configure ArcSDE
Before configuring ArcSDE, you must already have installed ArcSDE 10.0 (SP1) and
created an ArcSDE database account named SDE. The ArcSDE service must be
running in order to enter or change configuration parameters.
1 Select Tools > Options > ArcSDE Configuration from the menu.

Fig. 3-2 ArcSDE Configuration

3-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Configuring ArcSDE

2 Enter the following information to enable ArcSDE in Seabed:

Using ArcSDE Service Using Direct Connect

Server Enter the IP address or hostname of Enter the DBMS server

the ArcSDE server. For a hostname, name.
enter the fully qualified hostname that
uniquely identifies the machine (for
example, mymachine.mycompany.com).
If a fully qualified hostname is not
entered, and the machine is not
configured to append the DNS suffixes
used in your environment, attempts to
connect to the ArcSDE server will fail.

Port/ Enter the port number of SDE server Enter the Direct
Instance (e.g., 1212). Connect parameter
string. For information
about this string, refer
to the Esri website
(see “Esri Resources”
on page 3-6).

DirectConnect drivers are built as dynamically linked libraries (dlls) that execute in
the process space of the client application. The appropriate dlls must be installed on
the client application machines that will process spatial data.
The following dlls are needed in the Windows and Linux environments. Table 3-1
shows the necessary dlls for Oracle 10g client libraries.
Table 3-1 ArcSDE for Oracle 10g Client Libraries

(Windows) PATH variable (Linux) LD_LIBRARY_PATH variable

sdejavautil.dll (obtained through the libsdejavautil.so
Java SDK installation)
gsrvrora10g100.dll libgsrvrora10g100.so
sdeora10gsrvr100.dll libsdeora10gsrvr100.so

Configuration 3-5
Schlumberger Private - Customer Use
Configuring ArcSDE

Esri Resources For more information on ArcSDE, you can refer to the Esri ArcGIS Desktop online
help at the following URLs:
• Server 10 help
http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/
index.html#/Welcome_to_the_ArcGIS_Server_10_Help/
• Desktop 10 help
http://help.arcgis.com/en/arcgisdesktop/10.0/help/
Enter the following topic titles in the help search field to receive specific instructions
on these topics:
• Installing the ArcSDE Component
• Setting up ArcSDE Direct Connect
• ArcSDE Connection Syntax

3-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 4 Dictionary Administration

In This Chapter

Introduction ............................................................................................... 4-2

Navigation Methods .................................................................................... 4-3
Managing Data Dictionaries......................................................................... 4-4

Dictionary Administration 4-1

Schlumberger Private - Customer Use
Introduction

Introduction
The data dictionary contains the Seabed data model and associated reference data.
It is used to create projects, staging areas, and interfaces. Projects are
implementations of the Seabed data model that are used to store E&P data. Staging
areas are similar to projects, but they are used as temporary repositories for new
data while being validated for merger into a project. Interfaces are alternate ways of
looking at project data. For example, in an English-unit interface, data displays in
English-system units. Note that data must also be entered in accordance with the
type of unit system used.
Because of the relationships between data dictionaries, projects, staging areas, and
interfaces, it is highly recommended that you follow the Oracle full-database backup
procedure on a regular basis to ensure safekeeping of data. Only a full backup is
recommended, which takes data dictionaries, projects, and the Reef (formerly SIE)
account into consideration. For more information, refer to Oracle Corporation’s
documentation.

4-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Navigation Methods

Navigation Methods
To access data dictionary and project operations, you can use either the menu bar or
the object tree. Either way, you must first focus the view using one of the following
methods:
• From the object tree header, select Dictionaries and Projects.
• From the menu bar, select View > Dictionaries and Projects.

Menu Access With the view focused on Dictionaries and Projects (Fig. 4-1), you can select
Tools > Dictionaries and Projects to access the data dictionary functions.

Object Tree Access With the object tree focused on dictionaries and projects, you can double-click the
Data Dictionaries node to access data dictionary features as follows:
• Right-click the Data Dictionaries node to create a data dictionary, or to refresh
the object tree.
• If the Data Dictionaries node is closed (preceded by a plus sign), double-click it
to view a list of available data dictionaries.
• Right-click a specific data dictionary name to delete the data dictionary. Note that
all associated projects and staging areas must be deleted before you can delete a
data dictionary.
• Double-click a specific data dictionary name to view a list of projects and staging
areas associated with it.

Fig. 4-1 Object Tree Focused on Data Dictionaries and Projects

Dictionary Administration 4-3

Schlumberger Private - Customer Use
Managing Data Dictionaries

Managing Data Dictionaries

This section provides procedures that demonstrate the processes for viewing,
creating, and deleting data dictionaries.
After you have installed a new version of Seabed, the projects, data dictionaries,
staging areas, and interfaces from the previous Seabed version are still present in
the object tree display.

• • • • • •
Note: You cannot create a project using a data dictionary from the previous
Seabed version. At this point, you can delete any of the data dictionaries,
staging areas, and interfaces from the previous version.

To upgrade your existing projects to the new Seabed version, you will use the
separate Seabed Project Upgrade utility. For complete instructions and details,
refer to the Seabed Project Upgrade Guide.

• • • • • •
Note: When you create a data dictionary, Seabed applies a Construction status
to the data dictionary (for example, dd_1 [construction]). The construction
status is changed to Active if the account is successfully created. This
construction-to-active status principle applies when creating data
dictionaries, projects, staging areas, and interfaces.

You can create a project or staging area only under a data dictionary that
has Active status. Likewise, you can only create an interface under a
project with Active status.

When you delete a data dictionary, Seabed applies an interim
Destruction status to the data dictionary (for example, dd_2
[destruction]). If the delete process is successful, the account (and its
status) are removed from the database.

Viewing Available Typically, a database administrator or application developer views data dictionaries.
Data Dictionaries This procedure shows how to view all instances of data dictionaries available to your
database.

 To View Available Data Dictionaries

1 Focus the object tree on Dictionaries and Projects.
2 If the Data Dictionaries node is closed, double-click it to expand the tree and
display the available data dictionaries.

4-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Data Dictionaries

Creating a Data A Seabed data dictionary contains metadata defining the Seabed data model, as well
Dictionary as packages and procedures used in Seabed. A database administrator or
application developer will typically create a data dictionary.
A database might contain multiple Seabed data dictionaries. This occurs when you
upgrade Seabed to a newer version. Before upgrading, you will create a new version
of the data dictionary. During the upgrade process, you copy reference data from
the old data dictionary to the new data dictionary, and then upgrade project
structure to reflect the Seabed data model defined in the new data dictionary. For
more information, refer to the Seabed Project Upgrade Guide.
Before you begin, make sure of the following:
• You know the name to be used in creating the data dictionary.
• You know the password to be used in creating the data dictionary.
• You have sufficient space available in the SDS_TABLE tablespace to store an
additional data dictionary.

• • • • • •
Note: The following change is required (on the ProSource server) for proper
operation of Dictionary account creation and update processing in the
ProSource Seabed Database Manager. You may find this defined by default
in your Oracle installation but it is advised to check it and perform the
update as necessary. 
Edit $ORACLE_HOME/network/admin/sqlnet.ora and add EZCONNECT as:
NAMES.DIRECTORY_PATH= (TNSNAMES,EZCONNECT)

 To Create a Data Dictionary

1 Use one of the following methods to invoke the Create Data Dictionary
panel (Fig. 4-2) on the right side of the Oracle Database Manager:
• Select Tools > Dictionaries and Projects > Create > Data Dictionary.
• Right-click the Data Dictionaries node in the object tree and select
Create.

Dictionary Administration 4-5

Schlumberger Private - Customer Use
Managing Data Dictionaries

Fig. 4-2 Create Data Dictionary Panel

2 In the Dictionary field, enter a name for the data dictionary.

• • • • • •
Note: Database account names must meet the following criteria:
• Be between 1 and 25 characters in length
• Start with a letter
• Contain only letters, digits, and underscores
• Cannot intrude on a reserved name space (cannot begin with Seabed_
or SDS_ unless it also contains at least one digit)
• Cannot be in use by an existing database account
• Cannot be in use by an existing database object

3 Enter a Password.

4-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Data Dictionaries

• • • • • •
Note: The following characteristics are required for passwords:
• Between 1 and 30 characters in length
• No space character at start or end
• No single or double quotes (‘ or “)
• Any embedded spaces or “@” symbol must be in double quotes when
entered using Oracle applications and utilities.

4 In the Confirm Password field, re-enter the password.

The Default Tablespace field contains SDS_TABLE because data dictionaries
are required to be in that tablespace.
5 (Optional) From the Temporary Tablespace list, select a temporary
tablespace.

• • • • • •
Note: If you do not select a temporary tablespace, Seabed uses the one selected
during installation. If no temporary tablespace is selected during
installation, Oracle selects one for you.

6 From the Data Model Version list, select the Seabed data model. You cannot
create data dictionaries using old base data models or their extensions.

• • • • • •
Note: The property HideDataModelVersions can be set in SDS_HOME/DBAdmin/
properties/login.properties to exclude data model versions (extensions)
from being displayed. This property is a simple, comma-separated list,
such as the following:
HideDataModelVersions=My 2013.1A,My 2013.1B

• • • • • •
Note: For 2013.1, the base Seabed model is not displayed by default because all
Data Dictionaries must be created from the IM data model extension. The
IM data model extension will be merged into Seabed base model in the
future release. Also note that if all available data model names are
included in the property, the list will be ignored and all data model
versions will be displayed.

7 (Optional) Select the Auto GUID option if you want to generate a Globally
Unique Identifier (GUID) for each of the shared scope tables that are included
in the data dictionary.
If you select this option, it is recommended that you also use the Auto GUID
option when creating project records. This practice ensures that all entity tables
that comprise a project allow for the creation of records that can be uniquely
identified. For more information, refer to “Creating a Project” on page 5-4.

Dictionary Administration 4-7

Schlumberger Private - Customer Use
Managing Data Dictionaries

• • • • • •
Note: The process of creating the data dictionary takes longer with the Auto
GUID option selected than if you create a data dictionary without the Auto
GUID option.

8 (Optional) Enter a Description for the data dictionary.

9 Click Create to set up the data dictionary account information.
10 At the prompt to confirm the creation of the data dictionary, click Yes.
The new data dictionary displays under Data Dictionaries in the object tree.

Updating a Data Service Pack or hot fix patch releases may deliver updates to be applied to existing
Dictionary Seabed Data Dictionaries. This can be done as described below.

 To Update Data Dictionary

Use one of the following methods to invoke the Update Data Dictionary panel
(Fig. 4-2) on the right side of the Oracle Database Manager:
• Select Tools > Dictionaries and Projects > Update > Data
Dictionary.
• Select a Data Dictionary. Right-click and select Update.

Fig. 4-3 Update Data Dictionary Panel

• Select the Data Dictionary to be updated.

• Click Update.
• At the prompt, provide the password for the selected Data Dictionary.

4-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Data Dictionaries

Fig. 4-4 Data Dictionary Password dialog box

A confirmation message will be displayed upon completion of the update.

Deleting a Data A database administrator or an application developer deletes a data dictionary. This
Dictionary procedure shows you how to delete an instance of a data dictionary.

• • • • • •
Note: Before you can delete a data dictionary, you must first delete projects and
staging areas under the data dictionary.

 To Delete a Data Dictionary

1 Use one of the following methods to open the Delete Data Dictionary panel:
• Select Tools > Dictionaries and Projects > Delete > Data Dictionary.
• Right-click a specific data dictionary name in the object tree and select
Delete.
2 Click Delete to remove the data dictionary.
(Optional) To delete another data dictionary, select the appropriate data
dictionary name from the list and click Delete once again. You can delete one
data dictionary at a time using this method.
If, for any reason, you have selected several data dictionaries, you can click
Reset to return to the originally selected data dictionary, unless you already
deleted it.

Dictionary Administration 4-9

Schlumberger Private - Customer Use
Managing Data Dictionaries

4-10 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 5 Project Administration

In This Chapter

Introduction ............................................................................................... 5-2

Navigation Methods .................................................................................... 5-2
Project Management Procedures.................................................................. 5-3

Project Administration 5-1

Schlumberger Private - Customer Use
Introduction

Introduction
The project account holds E&P data organized in accordance with the Seabed data
model.

Navigation Methods
To access project operations, you can use either the menu bar or the object tree.
Either way, you must first focus the view using one of the following methods:
• From the object tree header, select Dictionaries and Projects.
• From the menu bar, select View > Dictionaries and Projects.

Menu Access With the view focused on dictionaries and projects (Fig. 5-1), you can select Tools
> Dictionaries and Projects to access the project functions.

Object Tree Access With the object tree focused on dictionaries and projects, you can expand the Data
Dictionaries node and individual data dictionaries to access project features using
one of the following options:
• Right-click the Projects node to create a project.
• Right-click a particular project to delete the project, re-create SDE layers, or set
recommended CRS.
• If a Projects node is closed, double-click it to view a list of available projects
under a given data dictionary.
• Double-click on a project to view a list of interfaces associated with the project.

Fig. 5-1 Object Tree Focused on Projects

5-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Project Management Procedures

Project Management Procedures

A project is created based on the Seabed data model contained in its parent data
dictionary. After a project is created, users must be granted access to the project to
view or manipulate data in the project. For more information, refer to “Creating
Project Access – Granting Interfaces” on page 8-12.

• • • • • •
Note: After you have installed a new version of Seabed, the projects, data
dictionaries, staging areas, and interfaces from the previous Seabed
version are still present in the object tree display. You cannot create a
project using a data dictionary from the previous Seabed version. At this
point, you can delete any of the data dictionaries, staging areas, and
interfaces from the previous version.

To upgrade your existing projects to the new Seabed version, you will use the
separate Seabed Project Upgrade utility. For complete instructions and details,
refer to the Seabed Project Upgrade Guide.
When creating a project, you can specify default and temporary tablespaces, and
you can select a storage configuration to specify data distribution in your system
environment. You must select a coordinate system for the stored data and choose a
vertical reference; if ArcSDE is installed, you must also create SDE layers. For more
information, refer to Chapter 9 “Storage Management.”
A newly created project receives a Construction status (for example, proj_1
[construction]). The construction status is changed to Active if the account is
successfully created. This construction-to-active status principle also applies when
creating data dictionaries, staging areas, and interfaces.
When you delete a project, Seabed applies an interim Destruction status to the
project account (for example, proj_2 [destruction]). If the delete process is
successful, the account (and its status) are removed from the database.

Audit History Log You can make audit history information available for a new project by selecting the
Audit History check box on the Create Project panel (refer to the procedure,“To
Create a Project” on page 5-5). This creates audit records for all insert, update, and
delete operations performed on the enabled entities. These records are written to
the SDS_AUDIT_TRAIL table found in the Data Dictionary account. Each record
contains the database user, key of the record, type of operation performed, and a
time stamp describing when the operation occurred.
You should note that the Audit History log can grow very large very quickly. If the
size of the log becomes an issue, you have several options:
• Delete the logs. Deleting the Audit History log has no effect on any functionality,
but the activity history information will be lost.
• If you want to preserve the activity history information, you can create a separate
tablespace to which you can archive the Audit History log on a scheduled basis.
• You can also archive by copying the log files to a separate, removable storage
medium, such as DVD or CD, and deleting the originals from the default log
location.

Project Administration 5-3

Schlumberger Private - Customer Use
Project Management Procedures

Audit history tracking is disabled by default. To make audit history available, you
must log in using the data dictionary account and then manually run the following
SQL*Plus statement:
update meta_entity
set audit_history=1
where entity in (‘<Entityname>’, ‘<Entityname>’);
where <entityname> is the name of the entity that you want to audit. For
example, to audit the Well and Borehole entities, you would specify(‘Well’,
‘Borehole’).
If you do not run this statement before creating a project, the Audit History check
box on the Create Project panel (Fig. 5-2) is disabled, but you can enable it later
by running this statement after the project is created.

Creating a Project The project creation process takes you through two interface panels, with optional
third and fourth panels: one where you can set recommended coordinate reference
systems and transformation methods with respect to the storage CRS, and one
where you can define spatial layers if you have installed ArcSDE.
For details on coordinate systems, refer to “Coordinate System Management” on
page A-1.
Before you begin, make sure you know the following:
• The name of the data dictionary to be used in creating the project
• The name of the project
• The password of the project
• Where to store the project’s permanent and temporary data; that is, the
tablespaces to be associated with the project. If storing permanent data using
multiple tablespaces, create a storage configuration before creating the project.
(For more information, refer to “Creating a Storage Configuration” on page 9-8.)
• The storage CRS for the project
• The vertical reference for the project
• The recommended CRS for the project, if any
• The spatial layer parameters for the project, if any
• The entities (if any) for which you wish to have an audit history available

• • • • • •
Note: If you will be working with spatial data, before you create the first Seabed
project, ArcSDE must be installed with an ArcSDE database account
named SDE. For more information, refer to the configuration procedures in
“After Installation and Before You Begin Using Seabed” on page 2-3. After
creating a project, you can change the configuration to point to a different
ArcSDE server, but you cannot delete the configuration. The Esri ArcSDE
server must be operational before you enter configuration information.

5-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Project Management Procedures

 To Create a Project
1 Use one of the following methods to invoke the Create Project panel:
• Select Tools > Dictionaries and Projects > Create > Project.
• Expand the appropriate Data Dictionary node, right-click the Projects
node, and select Create.

• • • • • •
Note: At this point, you receive a warning that you must configure ArcSDE
before creating the first project. If you want to use ArcSDE, install and
configure it before creating a project.

If a problem occurs with the ArcSDE layer during project creation, the
project is difficult to delete. You can manually delete this type of project
from the sds_sys.sds_accounts table and from the
sis_catalog.data_source_account, but it may still remain in Seabed 
Oracle Database Manager.

Fig. 5-2 Create Project Panel

• • • • • •
Note: If the Audit History check box is disabled as shown here, you can run a
SQL*Plus statement to activate it. For more information, refer to “Audit
History Log” on page 5-3.

Project Administration 5-5

Schlumberger Private - Customer Use
Project Management Procedures

2 On the Create Project panel, complete the following:

a. Select the Seabed Data Dictionary that contains the Seabed data model to
be used in constructing this project.
b. Enter the name of the Project.

• • • • • •
Note: Project names must meet the following criteria:
• Be between 1 and 25 characters in length
• Start with a letter
• Contain only letters, digits, and underscores
• Cannot intrude on a reserved name space (cannot begin with Seabed_
or SDS_ unless it also contains at least one digit)
• Cannot be in use by an existing database account
• Cannot be in use by an existing database object

c. Enter a Password and then re-enter the same password in the Confirm
Password field.

• • • • • •
Note: The following characteristics are required for passwords:
• Between 1 and 30 characters in length
• No space character at start or end
• No single or double quotes (‘ or “)
• Any embedded spaces or “@” symbol must be in double quotes when
entered using Oracle applications and utilities.

d. In the Default Tablespace field, select the tablespace to be used to store

project data that is not directed elsewhere through a storage configuration.

• • • • • •
Caution: If you do not select a default tablespace from the list, the default
tablespace selected during Seabed installation is used. If a default
tablespace was not specified during installation, then Oracle assigns
the SYSTEM tablespace as the default tablespace. However, the
SYSTEM tablespace does not provide optimum performance, so it is
recommended to select a default tablespace from this list.

e. (Optional) Select a Temporary Tablespace.

• • • • • •
Note: If you do not select a temporary tablespace, the one selected during
Seabed installation is used. If no temporary tablespace is selected during
installation, Oracle selects one for you.

5-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Project Management Procedures

f. (Optional) Select a Storage Configuration to be used to distribute your

project data across multiple tablespaces. Seabed provides three predefined
storage configurations: DEFAULT, RECOMMENDED (which allows for
partitioning of large object data to tablespaces of appropriate sizes based on
the size of the large objects), and PROSOURCERESULTS.

For more information, refer to Chapter 9 “Storage Management.”
g. (Optional) Select the Auto GUID option if you want to generate a Globally
Unique Identifier (GUID) for each table that is included in the project.

If you used the Auto GUID option when creating the data dictionary with
which the project will be associated, you should select it here as well for
project creation. This practice ensures that all entity tables that comprise a
project allow for the creation of records that can be uniquely identified. For
more information, refer to “Creating a Data Dictionary” on page 4-5.

• • • • • •
Note: Using the Auto GUID option will take longer when inserting data into the
project, but will ensure that the record will have a globally unique
identifier even if the application does not provide one.

h. (Optional) Enter a Description for the project.

i. (Optional) Select the Audit History check box to make audit history
available.
3 Click Next.

Project Administration 5-7

Schlumberger Private - Customer Use
Project Management Procedures

The Set Storage CRS panel (Fig. 5-3) opens so you can select a geodetic
coordinate reference system (CRS) as the Storage CRS using one of the three
techniques described in Step 4, Step 5, and Step 6.

Fig. 5-3 Set Storage CRS Panel

• • • • • •
Note: A geologist or a project domain expert determines the storage CRS and
recommended CRS codes.

The storage CRS is automatically considered a recommended CRS code.
You cannot explicitly set it as a recommended CRS code.

Only a geodetic CRS can be selected as the storage CRS, but a
recommended CRS can be geodetic or projected (non-geodetic).

4 Enter filter criteria in the following fields to find the appropriate CRS code.
If you know the CRS code, do the following:
a. In the CRS Attribute list, select Code.
b. Set the Operator list to equals (=).
c. In the Search String field, enter the CRS code.
d. Click Filter to pull the intended code to the CRS Filter Results list.

You can also produce a complete list of available CRS values by clicking Filter
with the Search String field empty.
5-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Project Management Procedures

5 To search for one or more values using wildcards, follow these steps:
a. Select a CRS Attribute from the list, defined as follows:

CRS Attribute Definition

Area_of_Use Region of CRS applicability
Code A standard abbreviation, mnemonic, or short code that
represents the reference value
Description A textual definition of the reference value
Name The name of the reference value
OpenGIS_Well_ Text string that specifies the projection parameters
Known_Text according to the OpenGIS standard
Original_Source The original source of this coordinate reference system. The
original source can be either of the following:
• EPSG – Many Esri Codes are attributed to EPSG.
• An extension of an out-of-the-box Esri coordinate
reference system; in this case, SOURCE is the group
making the addition and the ORIGINAL SOURCE is the
provider of the new coordinate reference system.
Source The person, company, or application that defined or
specified the data (content) for this instance and is
considered to be responsible for it. For example, POSC,
EPSG, API, ISO, etc.

Project Administration 5-9

Schlumberger Private - Customer Use
Project Management Procedures

CRS Attribute Definition

Source_Version The version number assigned by the Source. For example, if
the Source is Esri, this will be the version number of the
software used to produce or modify the data.
Type Coordinate reference systems (CRS) can be classified as:
Geographic 3D – A Geographic 3D CRS has axes of
latitude, longitude, and ellipsoidal height, for example GPS.
Geographic 2D – A Geographic 2D CRS has axes of
latitude and longitude. This is the horizontal subset of a
geographic 3D CRS.
Projected – A Projected CRS is a Cartesian 2D system with
axes of easting and northing. The axes can be referred to as
E and N or X and Y, in any order. Projected coordinates
result from the conversion of geographic 2D coordinates
through a map projection.
Vertical – A Vertical CRS is a 1D system with axis of height,
elevation, or depth.
Compound – A Compound CRS is a geographic 2D or
projected CRS combined with vertical CRS. The horizontal
and vertical components are independent, unlike a
geographic 3D CRS.
Engineering – An Engineering CRS is a non-georeferenced
CRS in 1, 2, or 3 dimensions. An Engineering 2D CRS has
horizontal axes i and j, and an Engineering 1D CRS has a
vertical axis k. Engineering 2D CRSs include engineering site
grids and 3D seismic binning grids.

b. Select an Operator.

• • • • • •
Note: You can choose from the following operators to enter a string expression
in the Search String field:
• = (equal to)
• Like (similar to)
• Not Like (not similar to)

6 Click Filter. Matching CRS codes appear in the CRS Filter Results panel.
7 Scroll through the list and select a code to use as the storage CRS.
8 Click Set Storage CRS to select the highlighted CRS.
9 Select the Vertical Reference.

• • • • • •
Note: Refer to the Web Report for descriptions of vertical references.

10 Click Next to apply your selections and continue.

5-10 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Project Management Procedures

11 The Set Recommended CRS panel (Fig. 5-4) opens.

The set of all possible CRS options supported by Esri is too large for most
purposes. The Recommended CRS panel is intended for an administrator to
create a list of suggested coordinate reference systems to be seen by end
users. The choices should be made by someone knowledgeable in the geodesy
of the area covered by the Seabed project.
In particular, it must be possible to convert the Storage CRS defined previously
to each recommended coordinate system. If the recommended system is based
on a different datum or ellipsoid, a transform is required. If more than one
transform is supported by Esri, an extra step is required to specify the
transform method using the Transform list shown below.

This is the
method used
to transform
between
storage CRS
and
recommended
CRS.

Fig. 5-4 Set Recommended CRS Panel

• • • • • •
Note: For each recommended CRS, you must select a Transform value other than
“None” to complete datum transformation. However, if the recommended
CRS is a projected system based on the Storage CRS, then “None” is
acceptable, because no transform is needed.
The Data Dictionary, Project, Vertical Reference, and Storage CRS information
fields reflect the information you entered in the previous panel. If this
information is incorrect, click Back to make corrections.

Project Administration 5-11

Schlumberger Private - Customer Use
Project Management Procedures

12 If you do not have SDE installed, click Finish to create the project.
You are prompted to confirm creation of the project, then if successful, you are
notified of the new project, and the project is listed in the object tree.
13 If you have SDE installed, click Next to invoke the Create Spatial Layers
panel (Fig. 5-5).

Fig. 5-5 Create Spatial Layers Panel

a. (Optional) Set parameters, if necessary. The sample values in the following

table can be modified as needed:

• • • • • •
Note: Refer to the SDE documentation for information on setting parameters and
using an SDE Keyword.

Table 5-1 Sample Spatial Layer Parameter Values

Parameter Default Value Parameter Default Value

xyScale 1000000 mOffset -100000
xOffset -180 xyScale 1000000
yOffset -90 Grid0 10
zOffset -100000 Grid1 0
mScale 10000 Grid2 0

5-12 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Project Management Procedures

b. (Optional) Enter an SDE keyword, if necessary. If not specified, the

DEFAULTS keyword is used.

The SDE configuration keyword specifies storage parameters to use when
creating layers. These include parameters like tablespaces, extents, and so
forth, for the various database objects created as part of layer creation. Also,
the SDE keyword is used to specify other layer parameters, like spatial
storage type. Refer to SDE documentation for details about keywords.
c. Click Finish to create the project.

Deleting a Project Before you begin, make sure you have already deleted all interfaces based on the
project and freed any staging areas that are bound to the project.

• • • • • •
Note: Any database object associated with the project will be deleted, including
extension tables.
Any users assigned to the project will be unregistered from the project.
A project for which an associated staging area is locked cannot be deleted
until the lock is released.

 To Delete a Project
1 Use one of the following methods to access the Delete Project panel:
• Select Tools > Dictionaries and Projects > Delete > Project.
• Expand the appropriate data dictionary node and projects node, right-click
the specific project name, and select Delete.
2 Confirm or select the project name you want to delete from the list.
3 Click Delete to remove the project.
4 Click Yes to remove the project from the object tree.

• • • • • •
Note: During project creation, if a problem occurs with ArcSDE layer creation,
the project can be difficult to delete. You can manually delete this type of
project from the sds_sys.sds_accounts table and from the
sis_catalog.data_source_account, but it might still remain in Seabed
Oracle Database Manager.

Recreating Spatial After creating a project, you can change the spatial layers. If you do so, you will lose
Layers all existing spatial layer data. For more information, refer to Step 13 of the
procedure “Creating a Project.” Note that Back, Reset, and Finish become
Update and Reset. When the new spatial layers are created, existing project data
are not reflected in the new spatial layers. You should re-create spatial layers only
before loading data into the project.

Project Administration 5-13

Schlumberger Private - Customer Use
Project Management Procedures

SDE Reset Layer The SDE Reset Layer Extent utility is a command line utility that lets you update
Extent Utility spatial layer metadata for projects, such as the layer extent and spatial indexes. You
can run this utility on empty projects, as well as loaded projects that already contain
spatial data.
The executable for this utility (SdeResetLayerExtent.exe) is located in the
$SDS_HOME/bin directory in your Seabed installation and is run using the
Windows command prompt. This command line utility consists of the main
command followed by a series of arguments and required data values (shown as
variables).
This section describes the command line arguments you will use to run this utility.
The following conventions are used to demonstrate the use of this utility:
• [ ] = optional argument
• < > = data value variable
• ( ) = description

SdeResetLayerExtent
-admin_account <administrative user name>
-admin_password <administrative user password>
[-server <seabed database server name>]
(not needed if TNSALIAS is used as the instance value)
[-port <seabed database server port]
(not needed if TNSALIAS is used as the instance value)
-instance (value can be entered as any of the following values)
<seabed database server sid>
(If used, must also include server and port values)
<tnsalias for seabed database server>
<easy connect syntax>
-project_account <project name used to update spatial layer
metadata>
-project_password <project login password>
-xOffset
-yOffset
-xyScale
-zOffset
-zScale
-mOffset
-mScale
[-grid0]
[-grid1]
[-grid2]
[-log_file <log file name>]
[-log_level INFO/WARN/ERROR/VERBOSE/DEBUG]
(Each log level is progressively more detailed. INFO is the most basic and
DEBUG is the most detailed.)
For more information about how to define spatial indexes and spatial references,
refer to the Esri ArcSDE online help system:
http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/
index.html#/Welcome_to_the_ArcGIS_Server_10_Help/

5-14 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Project Management Procedures

Setting the After creating a project, you can set or change the recommended CRS. For more
Recommended CRS information, refer to Step 13 of the procedure “Creating a Project.”

Using Auto GUID The Auto GUID option (on the Create Project and Create Data Dictionary
panels) is used to automatically generate a globally unique identifier (GUID) when
creating data dictionaries and projects. For the data dictionary, all shared scope
tables are provided GUIDs, and for projects, all tables receive a GUID.
By creating a globally unique ID for both data dictionaries and projects, you can
uniquely identify any record on any table in a Seabed database.
Selecting or not selecting Auto GUID has the following effects:
When Auto GUID is on, the following SQL command will populate not only the UWI
column but also the GUID column.
INSERT WELL(UWI) VALUES (‘WELL1’);
In this scenario,
SELECT UWI, GUID FROM WELL;
will return something like:
• UWI = WELL1
• GUID = 8D35ADB9AB104BD5A2EDE0252EB5CEDD

When Auto GUID is off, the following SQL command will populate only the UWI
column.
INSERT WELL(UWI) VALUES (‘WELL1’);
The command
SELECT UWI, GUID FROM WELL;
will return something like the following:
• UWI = WELL1
• GUID = (blank)

If Auto GUID is on or off, the SQL command

INSERT WELL(UWI, GUID) VALUES (‘WELL1’, ‘MYGUID’);
will always populate the UWI and GUID columns with the values supplied.
SELECT UWI, GUID FROM WELL;
will return the following:
• UWI = WELL1
• GUID = MYGUID

Project Administration 5-15

Schlumberger Private - Customer Use
Project Management Procedures

5-16 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 6 Staging Area Administration

In This Chapter

Introduction ............................................................................................... 6-2

Navigation Methods .................................................................................... 6-2
Staging Area Management Procedures ......................................................... 6-3

Staging Area Administration 6-1

Schlumberger Private - Customer Use
Introduction

Introduction
In most cases, data is not loaded directly into a project (the exception is when using
the UKOOA Loader). Instead, temporary memory is allocated to a staging area that
is bound directly to a given project. After the new project data has been validated in
the staging area, the merge process can be run to load it into permanent storage.
When a project no longer needs a staging area, the staging area must be freed from
the project. Seabed requires one staging area for each concurrent loader process. If
three loader processes are running at the same time, you must have three staging
areas set up on your Seabed platform.

Navigation Methods
To access staging area operations, you can use either the menu bar or the object
tree. Either way, you must first focus the view using one of the following methods:
• From the object tree header, select Dictionaries and Projects.
• From the menu bar, select View > Dictionaries and Projects.

Menu Access With the view focused on Dictionaries and Projects (Fig. 6-1), you can select
Tools > Dictionaries and Projects to access the project functions.

Object Tree Access With the object tree focused on dictionaries and projects, you can expand the Data
Dictionaries node and individual data dictionaries to access staging area features
as follows:
• To create a staging area, right-click the Staging Areas node and select Create.
• If the Staging Areas node is closed, double-click it to view a list of available
staging areas for a given data dictionary.
• To free an occupied staging area, right-click the staging area name and select
Free Staging Area.
• To delete an unoccupied staging area, right-click the staging area name and
select Delete.

Fig. 6-1 Object Tree Focused on Staging Areas

6-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Staging Area Management Procedures

Staging Area Management Procedures

When creating a staging area, you can specify default permanent and temporary
tablespaces, and you can select a storage configuration to specify data distribution
in your system environment.
Seabed applies a Construction status to a newly created staging area (for
example, stag_1 [construction]). The construction status is changed to Active if the
account is successfully created. This construction-to-active status principle also
applies when creating data dictionaries, projects, and interfaces.
When you delete a staging area, Seabed applies an interim Destruction status to
the staging area (for example, stag_2 [destruction]). If the delete process is
successful, the account and its status are removed from the database.
For more information, refer to Chapter 9, “Storage Management.”

• • • • • •
Note: After you have installed a new version of Seabed, the projects, data
dictionaries, staging areas, and interfaces from the previous Seabed
version are still present in the object tree display. You can delete any of
these items as needed, but if you intend to upgrade projects to the latest
version, do not delete them. To upgrade your existing projects to the new
Seabed version, you will use the separate Seabed Project Upgrade
utility. For complete instructions and details, refer to the Seabed Project
Upgrade Guide.

Creating a Staging This procedure shows how to create a staging area. You must create a staging area
Area after you create a project; the two operations cannot happen concurrently.
Before you begin, make sure you know the following:
• Name of the data dictionary to be used in creating the staging area
• Intended name of the staging area
• Intended password for the staging area
• Where to store the staging area’s permanent and temporary data—that is, the
tablespaces to be associated with the staging area. If storing permanent data
using multiple tablespaces, create a storage configuration before creating the
staging area. (For more information, refer to “Create a Storage Configuration” on
page 9-6.)
• Storage configuration that will be used
• If ArcSDE is installed, the SDE project that will be used to clone the spatial layer
configuration

• • • • • •
Note: When a staging area is bound to a project, it will use the CRS of the
project during the data load.

Staging Area Administration 6-3

Schlumberger Private - Customer Use
Staging Area Management Procedures

• • • • • •
Note: If you will be working with spatial data, before you create the first Seabed
staging area, ArcSDE must be installed with an ArcSDE database account
named SDE. ArcSDE must be configured using the procedures described in
“After Installation and Before You Begin Using Seabed” on page 2-3. After
creating a staging area, you can change the configuration to point to a
different ArcSDE server, but you cannot delete the configuration. The Esri
ArcSDE server must be operational before you enter configuration
information.

 To Create a Staging Area

1 Use one of the following methods to access the Create Staging Area panel:
• Select Tools > Dictionaries and Projects > Create > Staging.
• Expand the appropriate data dictionary node, right-click the Staging Areas
node, and select Create.
The Create Staging Area panel opens (Fig. 6-2).
To use the various loaders (except UKOOA, which does not require a staging
area), at least one staging area must be available with the same layers and
under the same data dictionary as the project you are loading. If SDE is
disabled, this panel opens as shown here.

Fig. 6-2 Create Staging Area Panel (SDE Disabled)

6-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Staging Area Management Procedures

If SDE is enabled, the Create Staging Area panel opens (Fig. 6-3).

Added field for

SDE-enabled
Seabed
installations.

Fig. 6-3 Create Staging Area Panel (SDE Enabled)

2 Enter or select the following information:

a. In the Data Dictionary field, select the Seabed data dictionary containing
the Seabed data model to be used to create this staging area.
b. In the Staging Area field, enter the name of the staging area.

• • • • • •
Note: Database account names must meet the following criteria:
• Be between 1 and 25 characters in length
• Start with a letter
• Contain only letters, digits, and underscores
• Cannot intrude on a reserved name space (cannot begin with Seabed_
or SDS_ unless it also contains at least one digit)
• Cannot be in use by an existing database account
• Cannot be in use by an existing database object

Staging Area Administration 6-5

Schlumberger Private - Customer Use
Staging Area Management Procedures

c. Enter a Password that will be used to access the staging area, and then re-
enter the same password in the Confirm Password field.

• • • • • •
Note: The following characteristics are required for passwords:
• Between 1 and 30 characters in length
• No space character at start or end
• No single or double quotes (‘ or “)
• Any embedded spaces or “@” symbol must be in double quotes when
entered using Oracle applications and utilities.

d. In the Default Tablespace field, select the SDS_TABLE tablespace to be

used as the project’s default tablespace.

• • • • • •
Caution: If you do not select a default tablespace from the list, then the default
tablespace selected during Seabed installation is used. If a default
tablespace was not specified during installation, then Oracle assigns
the SYSTEM tablespace as the default tablespace. However, the
SYSTEM tablespace does not provide optimum performance, so it is
recommended to select a default tablespace from this list.

e. (Optional) From the Temporary Tablespace list, select a temporary

tablespace.

• • • • • •
Note: If you do not select a temporary tablespace, the one selected during
Seabed installation is used. If no temporary tablespace is selected during
installation, Oracle selects one for you.

f. (Optional: SDE-enabled only) From the Storage Configuration list, select a

storage configuration to be used to distribute your staging area data across
multiple tablespaces. Seabed provides three predefined storage
configurations: DEFAULT, RECOMMENDED (which allows for partitioning of
large object data to tablespaces of appropriate sizes based on the size of the
large objects), and PROSOURCERESULTS.

For more information, refer to Chapter 9, “Storage Management.”
g. (Optional: SDE-enabled only) From the SDE Project Template field, select
the project to be used as a template in the staging area for spatial layers if
ArcSDE is installed.
h. (Optional) Enter a Description for the staging area.
3 Click Create to create a staging area.
4 Click Yes to confirm the intent to create the staging area.
5 Click OK to acknowledge the staging area was created.
The new staging area appears under the data dictionary in the object tree.

6-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Staging Area Management Procedures

Freeing a Staging When a staging area is used during the loading process, Seabed automatically binds
Area a staging area to the project. When the loading process is complete, Seabed
automatically frees the staging area.
If an event causes the loading process to fail, the staging area might remain bound
to the project even when the loading process is cancelled. If this happens, the
staging area in the object tree receives a notation that the staging area is bound.
For example, Staging Area A (Project 1), where Project 1 is the project to which
the staging area is bound. In this case, you will manually free the staging area.

 To Free a Bound Staging Area

1 In the object tree, right-click the staging area and select Free Staging Area.
The Free Staging Area that is Bound to a Project panel opens.
2 Select the Bound Staging Area you want to free.
3 Click Free to free the staging area.

Deleting a Staging This procedure shows you how to delete and unregister a staging area.
Area

• • • • • •
Note: Each project must have at least one staging area to load data. Therefore,
the last staging area associated with a project should not be deleted.
However, if you delete the last staging area, you can re-create another.

A staging area that is bound to a project cannot be deleted until it is freed

from the project.

 To Delete a Staging Area

1 In the object tree, right-click the name of the subject staging area and select
Delete.
The Delete Free Staging Area panel opens.
2 Select the Free Staging Area you want to delete.
3 Click Delete.
4 Click Yes to delete the staging area.

Staging Area Administration 6-7

Schlumberger Private - Customer Use
Staging Area Management Procedures

6-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 7 Interface Administration

In This Chapter

Introduction ............................................................................................... 7-2

Navigation Methods .................................................................................... 7-2
Managing Interfaces ................................................................................... 7-3

Interface Administration 7-1

Schlumberger Private - Customer Use
Introduction

Introduction
Seabed allows applications and users to access data across multiple standard and
user-defined (auxiliary) interfaces. An interface is a tool that allows access to data in
a project. An interface consists of a set of views that mirror the set of tables in the
project. The views provide open access to data through SQL commands.
You can have multiple interfaces to the same project, which support different unit
systems as well as levels of security. A project contains a standard interface to the
project tables. The standard interface does not perform unit conversion. Other
project interfaces are auxiliary interfaces, which define behavior different from the
standard interface that is specific to a set of data for a project.

Navigation Methods
To access interface operations, you can use either the menu bar or the object tree.
Either way, you must first focus the view using one of the following methods:
• From the object tree header, select Dictionaries and Projects.
• From the menu bar, select View > Dictionaries and Projects.

Menu Access With the view focused on dictionaries and projects (Fig. 7-1), you can select Tools
> Dictionaries and Projects to access the interface functions.

Object Tree Access With the object tree focused on dictionaries and projects, you can access the
interface nodes by expanding the Data Dictionaries node, the individual data
dictionaries, and the projects created under specific dictionaries.
• To create an interface, right-click the Interfaces node in the appropriate project
folder and select Create.
• To view a list of available interfaces associated with a project, double-click the
Interfaces folder for the appropriate project.

Fig. 7-1 Object Tree Focused on Interfaces

7-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Interfaces

Managing Interfaces
The following procedures are available for managing interfaces:
• Creating an interface
• Deleting an interface
• Granting access to project interfaces (refer to “Creating Project Access – Granting
Interfaces” on page 8-12).
• Revoking access to project interfaces (refer to “Deleting Project Access –
Revoking Interfaces” on page 8-13).

• • • • • •
Caution: All accounts contained in the currently connected Seabed database are
listed in the left-hand object tree display by the Dictionaries and
Projects view. When you install a new version of Seabed on top of an
older version for upgrade purposes, you will see both old-version
accounts and current-version accounts in the object tree. The only
action supported on an old-version account is deletion.

• • • • • •
Note: If the project node has a status designation, such as Construction or
Destruction, you cannot access the interfaces created from the project
node.

Creating an This procedure shows how to create an interface. Multiple users can use the same
Interface interface at the same time. Access to an interface must be granted to a user before
the user can access and use the interface. Seabed is capable of generating multiple
interfaces for the same project. For more information about granting privileges, refer
to “Creating Project Access – Granting Interfaces” on page 8-12.

• • • • • •
Note: This procedure is optional because Seabed creates a standard interface at
the time a project is created. Auxiliary interfaces can be created at any
time after a project is created, and are used for particular data needs. For
example, a user can have different auxiliary interfaces to the same project
supporting different unit systems.

Before you begin, make sure you know the following:

• Name of the project on which the interface is based
• Name of the interface
• Password for the interface
• Where to store the interface’s permanent and temporary data; that is to say, the
tablespaces to be associated with the interface. If storing permanent data using
multiple tablespaces, create a storage configuration before creating the interface.
For more information, refer to “Creating a Storage Configuration” on page 9-8.

Interface Administration 7-3

Schlumberger Private - Customer Use
Managing Interfaces

• Unit system to be used for the interface

• Whether you want to the interface to support “enterprise” entitlements, which
must be enabled before the interface is created. For more information, refer to
the note on page 7-6.

 To Create an Interface
1 Use one of the following methods to access the Create Interface panel:
a. Select Tools > Dictionaries and Projects > Create > Interface.
b. Expand the data dictionary node that contains the project for which you want
to create an interface. Right-click the Interfaces node, then select Create.

The Create Interface panel opens (Fig. 7-2).

Fig. 7-2 Create Interface Panel

7-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Interfaces

2 Enter or select the following information:

a. Select the Project to which this interface applies.
b. Enter the name of the Interface.

• • • • • •
Note: Database account names must meet the following criteria:
• Be between 1 and 25 characters in length
• Start with a letter
• Contain only letters, digits, and underscores
• Cannot intrude on a reserved name space (cannot begin with Seabed_
or SDS_ unless it also contains at least one digit)
• Cannot be in use by an existing database account
• Cannot be in use by an existing database object

The following restrictions pertain to interface names:

• An interface cannot be named “I1.”
• The character “-” is not allowed in an interface name.

c. Enter a Password and then re-enter the same password in the Confirm
Password field.

• • • • • •
Note: The following characteristics are required for passwords:
• Between 1 and 30 characters in length
• No space character at start or end
• No single or double quotes (‘ or “)
• Any embedded spaces or “@” symbol must be in double quotes when
entered using Oracle applications and utilities.

d. In the Default Tablespace field, select the tablespace to be used for the
interface. The SDS_TABLE tablespace is the default.

• • • • • •
Caution: If you do not select a default tablespace from the list, then the default
tablespace selected during Seabed installation is used. If a default
tablespace was not specified during installation, then Oracle assigns
the SYSTEM tablespace as the default tablespace. However, the
SYSTEM tablespace does not provide optimum performance, so it is
recommended that you select a default tablespace from this list.

Interface Administration 7-5

Schlumberger Private - Customer Use
Managing Interfaces

e. (Optional) Select a Temporary Tablespace.

• • • • • •
Note: If you do not select a temporary tablespace, the one selected during
Seabed installation is used. If no temporary tablespace is selected during
installation, Oracle selects one for you.

f. Select the Unit System type the interface will use.

• • • • • •
Note: If you need to create a new unit system, create a new <UnitSystem>
block in the XML file that EXACTLY matches the definition in the data
dictionary.

If you need to modify an existing unit system, modify the <UnitMapping>
section(s) in the XML file to EXACTLY match the definition(s) in the data
dictionary.

g. (Optional) Select the Entitled check box to enforce “enterprise” entitlements

through this interface.

• • • • • •
Note: An entitled interface enforces entitlements only on entities that are
explicitly enabled by an administrator before the interface is created. To
enable an entity, execute the <ddname>.SDS_DD_Admin.Entitle method
using SQL*Plus. For example, to enable entitlement enforcement on the
Well entity in the SDS_DD01 data dictionary, execute the following SQL
statement:

exec SDS_DD01.SDS_DD_Admin.Entitle (‘Well’, 1);

To turn off this setting for the Well entity, execute the following SQL
statement:

exec SDS_DD01.SDS_DD_Admin.Entitle (‘Well’, 0);

Note that these changes affect only the behavior of subsequently created
interfaces. Existing interfaces are not affected.

h. (Optional) Enter a Description for the project.

3 Click Create to create the interface.

You are prompted to confirm creation of the interface and you are notified
when the interface is created. The interface displays in the object tree beneath
the project.

Deleting an This procedure shows you how to delete an interface.

Interface

7-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Interfaces

 To Delete an Interface
1 In the data tree, right-click the subject interface and select Delete.
The Delete Interface panel opens.
2 From the Interface list, select the interface you want to delete.
3 Click Delete to remove the interface from the project tree.

Recreating Spatial After an interface is created, you can choose to recreate the spatial views for the
Views interface account. The spatial data resides in the project and will not be affected by
this operation.
The Recreate Spatial Views option is shown in the following figure.

Fig. 7-3 Recreate Spatial Views

Interface Administration 7-7

Schlumberger Private - Customer Use
Managing Interfaces

7-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 8 User Administration

In This Chapter

Introduction ............................................................................................... 8-2

Navigation Methods .................................................................................... 8-3
Managing Users ......................................................................................... 8-3

User Administration 8-1

Schlumberger Private - Customer Use
Introduction

Introduction
A Seabed administrative user can use Seabed Oracle Database Manager to perform
the following types of user administration tasks:
• Create/Delete database users
• Register/Unregister database users
• Grant/Revoke user privileges
• Change user passwords

In some environments, a Seabed administrative user will create both a new

database and Seabed users. In other environments, the database administrator will
create new database users, and the Seabed administrative user registers those
users with Seabed. Check with your database administrator if you are not sure
whether you should be creating new users.
You will initially access Seabed Oracle Database Manager as SIS_ADMIN. This
special administrative account gives the authority to create other administrative
accounts. Although it is possible to use SIS_ADMIN to administer Seabed, this
account should be used only to create individual user accounts with Administrator
privileges. SIS_ADMIN does not appear in lists of Seabed or database users and
cannot be granted access to projects through DBAdmin.

• • • • • •
Note: Overall user management for the ProSource system is handled through the
IM Administration Console. The information in this chapter is
supplementary or primarily to be used if directed to by the IM
Administration online help.

User Account Seabed user accounts provide access to Seabed database features, as needed. For
example, to load project data, a Seabed user might need to access two sets of data
through a standard interface and an auxiliary interface. The user account will
therefore need privileges to access project data through those interfaces.

Registered Users A registered user is entitled to access Seabed functionality. In an enterprise system
environment, some users have access to a Seabed database and some have access
to other database implementations. The Seabed Oracle Database Manager object
tree groups users by their registered or unregistered classification. User accounts
can be switched between registered and unregistered, as needed.

Privileges Privileges are granted when a user account is created, but they can be granted or
revoked at any time. The following types of privileges are available to Seabed users:
• Permit Project Access – Allows users access to the standard interface and/or
auxiliary interfaces of a project.
• Make User an Administrator – Provides access to administrator functions.

8-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Navigation Methods

• Make User an Administrator Who Can Create Other Administrators –

Allows access to administrator functions, including the ability to create other
administrator user accounts.

Users can have both administrator privileges and project access privileges. Seabed
users with administrator privileges can grant themselves project access, and if
granted the appropriate privilege, they can grant other users administrative rights.

Navigation Methods
To access user account information, you can use either the menu bar or the object
tree. Either way, you must first focus the view using one of the following methods:
• From the object tree header, select Users/Security.
• From the menu bar, select View > Users/Security.

Menu Access With the view focused on users and security (Fig. 8-1), you can select Tools >
Users/Security to access the user- and security-related functions (such as creating
and deleting accounts, changing passwords, and updating privileges).

Object Tree Access With the object tree focused on users and security, you can double-click the Users
node to access user account features as follows:
• Right-click the Registered Users node to create a user account.
• Right-click a registered user account to change the password, delete or unregister
the account, or grant/revoke user privileges.
• Right-click an unregistered user account to register the user in Seabed.

Fig. 8-1 Object Tree Focused on Users/Security

Managing Users
When responsible for managing Seabed user accounts, you will periodically perform
the following task types:
• Creating and deleting user accounts
• Changing passwords

User Administration 8-3

Schlumberger Private - Customer Use
Managing Users

• Registering and unregistering users

• Granting and revoking privileges
• Granting authority to create administrators

Creating a User After creating a user account, you need to register the account with Seabed and
Account grant project access or administrator privileges before that user can use Seabed.

 To Create a User Account

1 Use one of the following methods to invoke the Create User panel (Fig. 8-2)
to create a user account:
• Select Tools > Users/Security > Create User.
• Right-click the Registered Users node in the object tree and select Create.

Fig. 8-2 Create User Panel

2 Enter the new User.

• • • • • •
Note: The account names (USER, PROJECT, DATA DICTIONARY, etc) must not
match any Oracle reserved words. For example, you cannot create a user
account named "USER". For more information, please refer to Seabed
Data Model Naming Conventions guide.

8-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Users

3 Enter a Password.
4 Re-enter the password in the Confirm Password field to verify the password.
5 Select the Default Tablespace for the user.
User default tablespaces are typically different from account default
tablespaces. Seabed offers you a tablespace named USER to hold user
information.

• • • • • •
Caution: If you do not select a default tablespace from the list, then the default
tablespace selected during Seabed installation is used. If a default
tablespace was not specified during installation, then Oracle assigns
the SYSTEM tablespace as the default tablespace. However, the
SYSTEM tablespace does not provide optimum performance, so it is
recommended to select a default tablespace from this list.

6 Select the Temporary Tablespace name.

• • • • • •
Note: If you do not select a temporary tablespace, the one selected during
Seabed installation is used. If no temporary tablespace is selected during
installation, Oracle selects one for you.

7 Enter a description for the user account.

8 Click Create to save the new user account.
9 Click OK to acknowledge the new user account.
The account displays under Registered Users in the object tree.
If the user already exists, an error message displays, stating that the create
user process failed. In this case, the user likely exists in the Unregistered
Users list. If so, simply register the user (refer to “Registering a Seabed User”).
10 After the user account is created, you should grant privileges, as necessary.
Refer to the following for complete instructions:
• “Granting Project Access” on page 8-10
• “Granting Administrator Privileges” on page 8-10
• “Granting Authority to Create other Administrators” on page 8-11

Deleting a User The following instructions show how to delete a user account.
Account

 To Delete a User Account

1 Use one of the following methods to invoke the Delete Registered User
panel:
• Select Tools > Users/Security > Delete User.

User Administration 8-5

Schlumberger Private - Customer Use
Managing Users

• From the Registered Users list in the object tree, right-click the user
account to be deleted, and select Delete.

2 With the registered user selected, click Delete.

3 On the resulting dialog box, click Yes to delete the user.
The user account is dropped from the object tree.

8-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Users

Changing the Administrators can change the password of any registered user account, including
Password their own, but the passwords for the special Seabed accounts SDS_SYS,
SIS_ADMIN, and SIS_INFO cannot be changed. For more information, refer to
“Changing Special Seabed Oracle Account Passwords” on page 8-8.

 To Change the Password of your User Account

1 Use one of the following methods to open the Change Registered User’s
Password panel (Fig. 8-3):
• Select Tools > Users/Security > Change Password.
• From the Registered Users list in the object tree, right-click the user
account in question, and select Change Password.

Fig. 8-3 Change Password

2 Select the appropriate User from the list.

3 Enter the Admin Password you used to log into the Seabed Oracle Database
Manager.
4 Enter a New Password for the user.
5 Re-enter the password for confirmation.
6 Click Change to change the password.
A confirmation message displays, indicating that the change is made, and if
changing your own user account password, the message suggests you should
log out (File > Disconnect) and log in using the new password.
7 Click OK.

• • • • • •
Note: If you want to revert to the original password, you must repeat this
procedure in reverse (reassign the original password). The Reset button
does not “undo” the operation. It simply sets the panel to the base state.

• • • • • •
Note: Oracle password policies are set through Oracle user profiles. Default
profiles are delivered with the ProSource-Seabed system and can be
modified as required to meet user policy requirements. See “Manage Users
and Security” in the IM Administration online help for more information.

User Administration 8-7

Schlumberger Private - Customer Use
Managing Users

Changing Special Table 8-1 Password Change Commands

Seabed Oracle
Account Passwords Name Functionality/Password Information
SDS_SYS SDS_SYS is the master Seabed account that contains a directory of
all Seabed accounts. This account is granted extensive Oracle
privileges. Following installation, the DBA should change the
SDS_SYS account password if it is known by anyone who is not a
database administrator.
Notes:
• All passwords must adhere to Oracle password guidelines:
- Must begin with a character
- Must be fewer than 30 characters long
- Must not contain spaces or other special characters other than
the underscore (_) and dollar sign ($)
• Oracle passwords are not case-sensitive. (Refer to the Oracle
documentation for further information.)
Because SDS_SYS is also used internally within the Seabed
database, its password must not be changed other than through
the following SQL*Plus command:
1. Shut down the Seabed license daemon by running
exec sds_sys.sds_admin.LMSHUTDOWN

2. Change the password by running

exec sds_sys.sds_admin.LMCONNECT_password
('<new_password>')
SIS_ADMIN The SIS_ADMIN account is the administrative user account first
used to connect to Seabed Oracle Database Manager. During that
initial session, you should create accounts for designated
administrators and assign those accounts administrator privileges.
After other administrative accounts are created, the DBA should
change the SIS_ADMIN account password if it is known by anyone
who is not a database administrator.
Notes:
• Because SIS_ADMIN is also used internally within the IM
Framework, its password must not be changed other than
through the following SQL*Plus command:
exec sds_sys.sds_admin.sisadmin_password
('<new_password>')

• • • • • •
Note: You must be connected as SYS, SYSTEM, SDS_SYS, or SIS_ADMIN to
change either the SDS_SYS or SIS_ADMIN password. You must also be
sure all applications and users are logged out of the database before you
attempt to change the password.

8-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Users

Name Functionality/Password Information

SDS_INFO The SDS_INFO account is an internal Seabed account with access
only to database objects granted to Public. This account is created
automatically during Seabed installation with a default password
that must never be changed. If it is changed, Seabed E&P projects
and IM applications will not function.
To restore the Oracle SDS_INFO password, you must be connected
as SYS, SYSTEM, or SDS_SYS. You must also be sure all
applications and users are logged out of the database before you
attempt to change the password.

The following SQL*Plus command restores the password:
exec sds_sys.sds_admin.reset_password
('SDS_INFO', 'SDS_INFO');
This command appears to change the SDS_INFO account password
to SDS_INFO, but it actually restores the password to the value set
by Seabed during installation.
Note: The Seabed installation program does not require
information about the SDS_INFO account.

Registering a To upgrade a non-Seabed Oracle user to a user entitled to use Seabed, you must
Seabed User register the user with Seabed.

 To Register a Seabed User

1 From the Unregistered Users list in the object tree, right-click the user
account you want to register as a Seabed user, and select Register.
A dialog box prompts you to confirm that you wish to register this account.
2 Click Yes to register the user account as a Seabed user account.
3 Click OK to acknowledge the registration is complete.
The user account drops from the Unregistered Users list and appears under
Registered Users.

Unregistering a To remove an existing Seabed Oracle user from registered status, you must
Seabed User unregister the user.

 To Unregister a Seabed User

1 From the Registered Users list in the object tree, right-click the user account
you want to unregister as a Seabed user, and select Unregister.
A dialog box prompts you to confirm that you want to unregister this account.
2 Click Yes to unregister the user account as a Seabed user account.
3 Click OK to acknowledge the unregistration is complete.
The user account moves from Registered Users to Unregistered Users.

User Administration 8-9

Schlumberger Private - Customer Use
Managing Users

Granting Project When granting privileges to a user account, the Permit Project Access grant type
Access allows a user to access data through either the standard project interface or an
auxiliary interface.
A standard interface has the same name as the project, whereas an auxiliary
interface is named differently from the project. A user account must be granted
access to an interface of a project for the user to access project data.

 To Grant Project Access Privilege

1 From the Registered Users list in the object tree, right-click the user account
to which you want to grant privileges and select Grant.
2 On the Grant Privilege panel (Fig. 8-4), select Permit Project Access from
the Grant Type list.

Fig. 8-4 Permit Project Access Grant Type

3 Select a project or auxiliary project interface from the Project Name list.
4 Click Grant.
5 Click OK to acknowledge the privilege is granted.

Granting To provide permissions to use Seabed Oracle Database Manager and the ability to
Administrator create Seabed user accounts and change passwords, you must assign the
Privileges Administrator grant type.

 To Grant Administrator Privileges

1 From the Registered Users list in the object tree, right-click the user account
to which you want to grant privileges and select Grant.
2 On the Grant Privilege panel (Fig. 8-5), select Make User an
Administrator from the Grant Type list.

Fig. 8-5 Make User an Administrator Grant Type

3 Click Grant to assign the privilege to the user account.

8-10 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Users

4 Click OK to acknowledge the user now has Administrator privileges.

The notation “Is Admin” now appears below the User name (Fig. 8-6).

privilege
notation

Fig. 8-6 Is Admin Notation

Granting Authority To provide a user account with the authority to grant administrator privileges to
to Create other other accounts, you will assign the Administrator who can Create other
Administrators Administrators grant type.

 To Grant Authority to Create Administrators

1 From the Registered Users list in the object tree, right-click the user account
to which you want to grant privileges and select Grant.
2 On the Grant Privilege panel, select Make User an Administrator Who
Can Create Other Administrators from the Grant Type list.

Fig. 8-7 Make User an Admin Who Can Create Other Admins Grant Type

3 Click Grant to assign the privilege to the user account.

If the user was not already an administrator, a dialog box asks you to confirm
that the user should have Create other Administrators privileges.
4 Click Yes to confirm the intent to grant this privilege.
5 Click OK to acknowledge the user now has Create Administrator privileges.
The notation “Is Admin with Create Admin Authority” now displays below the
User name (Fig. 8-8).

privilege
notation

Fig. 8-8 Is Admin with Create Admin Authority Notation

User Administration 8-11

Schlumberger Private - Customer Use
Managing Users

Revoking As a Seabed administrator, you can revoke project privileges from any user. As a
Privileges Seabed administrator with privileges to create other administrators, you can also
revoke administrator privileges.

 To Revoke Privileges
1 From the Registered Users list in the object tree, right-click the user account
for which you want to revoke privileges, and select Revoke.
2 On the Revoke Privilege panel, select one of the following privileges to be
removed:
• Project Access
• Administrator Rights
• Ability to Create Other Administrators

3 If needed, select an interface from the Project Name list.

4 Click Revoke.
5 Click Yes to confirm the intent to revoke the privilege.
6 Click OK to acknowledge that the privilege has been revoked.
The privilege notation is removed from below the User name.

Creating Project Creating an interface is different from having the privilege to use an interface.
Access – Granting Hence, the phrase “creating project access” between a user and interface refers to
Interfaces granting the user the privilege to use the interface. At a highly secure site, the policy
might be to grant technical assistants the privilege to create projects, interfaces, and
users without giving them rights to grant an interface to a user. The new projects
contain no data until project access is created to the project. Users are unable to
view data until project access is created. Instead, this most critical aspect of
administration should be granted only to a highly trusted individual.
Before you begin, make sure you know the name of the interface and the name of
the user who will be receiving project access.

 To Create Project Access

1 From the Registered Users list in the object tree, right-click the user account
that is to receive project access and select Grant.
2 On the Grant Privilege panel, select the appropriate project from the Project
Name list.
When an administrator grants a user access to a project, the user will have read and
write access to all entities within a given project. Granting project access will also
give the user read access to the reference data in the data dictionary. However, the
user will not have insert, update, or delete permissions on any reference data,
because this is typically managed by a limited number of people.

8-12 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Users

There is no user interface to grant a user update access to the reference data in the
data dictionary. To grant update access, you must connect to the database directly
as an SDS_SYS or as a database administrator (SYS, SYSTEM, and so forth) using
any general SQL tool, and then run the following command(s):
Grant <dd_name>_Sys to <username>;
Where <dd_name> is the name of the data dictionary to which you intend to grant
update access, and <username> is the Seabed Oracle database user who will
access and change reference data in the named data dictionary.

Deleting Project This procedure describes how to delete project access.

Access – Revoking
Interfaces

 To Delete Project Access

1 From the Registered Users list in the object tree, right-click the user account
for which you want to revoke privileges and select Revoke.
2 On the Revoke Privilege panel, select the privilege type to revoke from the
Revoke Type list. Only privileges that have been granted appear in this list.
3 From the Project list, select the interface.
4 Click Revoke.
5 Click Yes to confirm the intent to revoke the privilege.
6 Click OK to acknowledge that the privilege has been revoked.
For more information, refer to “Revoking Privileges” on page 8-12.

Maximum Enabled Oracle and Seabed make extensive use of database roles to manage the capabilities
Database Roles of user accounts. For example, Seabed uses database roles to control which projects
a user is allowed to access. Oracle has a limit to the number of roles that users can
have enabled at one time. This Oracle restriction limits the number of projects to
which a user is allowed access at a time. The exact number of projects to which a
user can be granted access varies depending upon what other roles the user has
been granted, but typically the limit is in the range of 65 to 70 projects.
For more information about setting Oracle parameters, refer to Appendix A of the
Seabed Installation Guide.

User Administration 8-13

Schlumberger Private - Customer Use
Managing Users

8-14 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 9 Storage Management

In This Chapter

Introduction ............................................................................................... 9-2

Navigation Methods .................................................................................... 9-7
Managing Storage Configurations ................................................................ 9-8

Storage Management 9-1

Schlumberger Private - Customer Use
Introduction

Introduction
A Seabed administrator can optimize the database configuration of Seabed projects
using Storage Configurations. Oracle DBAs typically optimize the database
configuration by spreading the input/output workload across several disks. Seabed
allows you to do this by defining storage configurations, which determine what
tablespaces will be used by the tables in a project. You specify which storage
configuration to use when you create a project.
A typical arrangement is to have many small projects share the same storage
configuration, and thus, share the same tablespaces. Large projects typically have
their own storage configuration definition, allowing for easier management of the
large project’s tablespaces.

Seabed Storage When you create a Seabed account, you specify a default tablespace and a
Configurations temporary tablespace. The temporary tablespace is used for activities such as
sorting query results. The default tablespace is used for all account storage not
directed elsewhere by a storage configuration. For projects and staging areas, where
most of your data is stored, you can define storage configurations to separate data
across multiple storage devices. Seabed provides three built-in storage
configurations—DEFAULT, RECOMMENDED, and PROSOURCERESULTS.
The DEFAULT storage configuration assigns all tables to the SDS_TABLE
tablespace, all indexes to SDS_INDEX, and all large object data (LOB) to SDS_LOB.
This default configuration can be used to create projects and staging areas. It can
also be used as the basis for creating your own storage configurations.
The RECOMMENDED storage configuration uses Oracle’s partitioning capability to
assign a tablespace based on the value of a controlling attribute column called the
RELATIVE_SIZE_INDICATOR. All tables in Seabed that have any sort of LOB (BLOB/
CLOB/NCLOB) columns have been added to this configuration as listed in Table 9-1
and Table 9-2. Each of these tables includes the RELATIVE_SIZE_INDICATOR
column.
The PROSOURCERESULTS storage configuration allows you to run workflows
related to ProSource Results projects. Workflows may fail if you select either the
DEFAULT or RECOMMENDED storage configuration option for ProSource Results
projects. The PROSOURCERESULTS storage configuration option stores all
Document and Document_Body_Part LOB data in the SDS_LARGE_LOB tablespace.
Table 9-1 Seabed Tables with BLOB columns

Table Name Parent Table Parent Package

Private_Blob Class 'Activity_Parameter' Package 'Activity'
Bulk_Array_Part Class 'Bulk_Array_Part' Package 'Bulk'
Record_Data Class 'Seismic_Record' Package 'Seismic'
Plot_Data Class 'Squash_Plot' Package 'Seismic'
Histogram_Data Class 'Dataset_Statistics' Package 'Seismic'
Document_Body Class 'Document' Package 'Utility'

9-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Introduction

Table Name Parent Table Parent Package

Document_Part Class 'Document_Body_Part' Package 'Utility'
Bulk_Array Class 'Bulk_Array' Package 'Bulk'

Table 9-2 Seabed Table with CLOB columns

Table Name Parent Table Parent Package

Remarks_CLOB Class 'Additional_Remarks' Package 'Utility'

For example, the BULK_ARRAY table has one BLOB column, BULK_DATA, which
would be partitioned into four different tablespaces based on the value of the
controlling attribute, as follows:
• If the RELATIVE_SIZE_INDICATOR value is ‘Small’, BLOB data from the
BULK_DATA column is stored in the SDS_SMALL_LOB tablespace.
• If the RELATIVE_SIZE_INDICATOR value is ‘Medium’, BLOB data from the
BULK_DATA column is stored in the SDS_MEDIUM_LOB tablespace.
• If the RELATIVE_SIZE_INDICATOR value is ‘Large’, BLOB data from the
BULK_DATA column is stored in the SDS_LARGE_LOB tablespace.
• If the RELATIVE_SIZE_INDICATOR value is NULL, BLOB data from the
BULK_DATA column is stored in the SDS_LOB tablespace.

• • • • • •
Note: Each of these tablespaces must be created before a storage configuration
can be used to allocate project or staging area data.

Any application that stores data in any of the tables specified in Table 9-1 can
indicate the relative size of the LOB column by setting the
RELATIVE_SIZE_INDICATOR column to one of these values (‘Small’, ‘Medium’, or
‘Large’). Your Oracle DBA can optimize the storage of this data by configuring the
tablespaces accordingly.

• • • • • •
Note: Keep in mind that with the above configuration, each partitioned LOB
column will add some pre-allocated space to the project size. For more
information on determining tablespace size allocations, refer to “Pre-
Installation Tasks” on page 3-4 of the Seabed Installation Guide for Oracle
Database.

Small non-E&P accounts (such as Seabed user accounts and data dictionaries) do
not experience significant benefit from distributing data. Therefore, Seabed does not
support the use of storage configurations with such accounts. Nor does Seabed
support the use of storage configurations with auxiliary interfaces, as they consist of
view definitions for data stored in project accounts.
Storage configurations should be used to improve performance in environments with
multiple storage devices (disk drives).

Storage Management 9-3

Schlumberger Private - Customer Use
Introduction

Storage configurations provide mapping for tables, indexes, and LOB data to
tablespaces at the data model, submodel, and individual entity level. Assignments at
the individual entity level supersede those at the submodel level, and those at the
submodel level supersede those at the model level. Entities and their related indexes
and LOBs that are not part of the data model, or not mapped by any storage
configuration assignment definition, are assigned to the default tablespace of the
account.
Tablespace assignment is by entity, submodel and model name; and by table, index
and LOB entity type. An individual entity can have its table mapped to one
tablespace, and its indexes mapped, either at the entity level or through submodel
or model inheritance, to a different tablespace.
For more information about creating tablespaces and configuration parameter
guidelines, refer to “Tablespaces” in Chapter 3 of the Seabed Installation Guide for
Oracle Database.

Considerations When creating a storage configuration for your system environment, consider the
size of your storage devices compared to the size and usage frequency of the tables
in your Seabed projects and staging areas. Normally, you will want to store large,
heavily used tables on different devices from where their indexes are located. When
possible, distribute your data across multiple storage access channels for better
performance. Refer to Oracle and third-party database tuning books for detailed
information and ideas.

9-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Introduction

Storage Storage configuration tables are generated when a project or staging area is created
Configuration using Seabed Oracle Database Manager.
Table

Fig. 9-1 Storage Configuration

• Data Dictionary and Storage Configuration lists contain the location and
name of the storage configuration assignment source, and the Save Changes As
field is the name under which any changes are stored within the same data
dictionary. When creating a new storage configuration, you can use the Storage
Configuration list to pre-fill the tablespace assignment table, make desired
changes, and save the configuration using the provided name. When editing in a
storage configuration, leave the Save Changes As field empty or enter the same
name as shown for Storage Configuration.
• Object lets you assign at the model level (Seabed/any/any), at the submodel
level (Seabed/submodel name/any), or at the individual entity/table level
(Seabed/submodel name/table name).
• Tablespace Assignment lets you map the object’s table(s), index(es), and
LOB(s) to existing database tablespaces.
• Clicking Add copies the selections in Object and Tablespace Assignment into
the Assignments section.
• Clicking Remove with a row selected in the Assignments section removes that
row from Assignments.

Storage Management 9-5

Schlumberger Private - Customer Use
Introduction

Storage Using Seabed Oracle Database Manager, you can create, edit, and delete storage
Configuration configurations. When you use a storage configuration, the configuration is locked.
Locking and Many projects or staging areas can use the same storage configuration at the same
Copying time. Therefore, the storage configuration remains locked until the last project or
staging area using it is dropped. After the storage configuration is unlocked, you can
change its mapping or delete it.
If you need to change the mapping of a storage configuration that is locked, you can
edit the storage configuration, make necessary changes, and save the changed
configuration using a different name.
You can also copy a storage configuration from one data dictionary to another data
dictionary within the same Seabed database, optionally changing the name in the
target data dictionary.
The Copy panel is similar to the Create/Edit panel shown in Fig. 9-1, except the
Object and Tablespace Assignment sections are missing, the Create button is
replaced with a Copy button, and underneath the Data Dictionary field is a
Target data dictionary list.

9-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Navigation Methods

Navigation Methods
To access storage configuration information, you can use either the menu bar or the
object tree. Either way, you must first focus the view using one of the following
methods:
• From the object tree header, select Storage.
• From the menu bar, select View > Storage.

Menu Access With the view focused on storage configuration (Fig. 9-2), you can select Tools >
Storage > Storage Configurations to access the storage configuration functions
(such as creating, copying, editing, and deleting configurations).

Object Tree Access With the object tree focused on Storage Configurations, you can access storage
configuration features from the object tree as follows:
• Right-click the Storage Configurations node to create a storage configuration.
• Right-click the DEFAULT configuration to copy or edit the configuration.
• Right-click any other configuration to copy, edit, or delete the configuration.

Fig. 9-2 Object Tree Focused on Storage Configuration

Storage Management 9-7

Schlumberger Private - Customer Use
Managing Storage Configurations

Managing Storage Configurations

This section describes how to create, copy, edit, and delete storage configurations.

• • • • • •
Caution: If you have performed a Seabed upgrade, you will see both old-version
data dictionaries and current-version data dictionaries in the Data
Dictionary lists on the various Storage Configuration panels. You must
select only a current-version data dictionary.

Creating a Storage As a Seabed administrator, you can use one of the provided storage configurations,
Configuration or you can create your own storage configuration based on the default. To use an
existing storage configuration in the current data dictionary, simply select it from the
Storage Configuration list. To use a storage configuration defined in another data
dictionary within the same database, copy it to the desired data dictionary.

 To Create a Storage Configuration

1 Use one of the following methods to open the Create Storage Configuration
panel (Fig. 9-3):
• Select Tools > Storage > Storage Configurations > Create.
• Right-click the Storage Configurations node in the object tree and select
Create.

Fig. 9-3 Create Storage Configuration Panel

2 If the correct data dictionary is not already selected, choose a data dictionary
from the Data Dictionary list.

9-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Managing Storage Configurations

3 (Optional) Select a storage configuration from the Storage Configuration list

to be used as the starting point for the new storage configuration.
4 Enter a name for the storage configuration in the Save Storage
Configuration As field.
5 Add, remove, and change tablespace assignments as follows:
a. In the Object section, select a combination of submodel and table objects.
b. In the Tablespace Assignment section, select tablespaces by object type.

• • • • • •
Note: Only the Seabed data model is supported, and only existing permanent
Oracle tablespaces can be assigned.
• To make an overall Seabed model level assignment, in the Object section,
select <any> Submodel and <any> Table.
• To make a submodel-level assignment, select a specific Submodel with
<any> Table.
• To make a table-level assignment, select a specific Submodel and a specific
Table within that submodel.

• • • • • •
Note: When making a specific table assignment, a tablespace can be assigned to
the table only for large objects when the table has a LOB. Tablespace
assignments to LOBs are always permitted at the submodel and model
levels because a future table in the submodel or model might receive LOB
data even if none is currently present.
6 Click Add to move your selections to the Assignments pane.
7 To replace an existing assignment definition, compose a new assignment for
the same object and click Add.
8 To delete an assignment, select the assignment in the Assignments section
and click Remove.

• • • • • •
Note: When defining a model level assignment, be sure to complete all three
tablespace assignment overrides (Table, Index, and LOB). With submodel
and table level overrides, you can choose any combination of these
tablespace assignment options.

9 Click Create to save the new storage configuration.

The new configuration is listed in the object tree.

Storage Management 9-9

Schlumberger Private - Customer Use
Managing Storage Configurations

Editing a Storage Editing a storage configuration is identical to creating one, except that the Save
Configuration Changes As field has the same name as the Storage Configuration list.

 To Edit a Storage Configuration

1 From the Storage Configurations node in the object tree, right-click a non-
default storage configuration, and select Edit from the menu.
2 Make changes as needed and click Update.

• • • • • •
Note: If you edit a storage configuration that is in use, the panel identifies the
configuration as “Locked” and you are required to enter a different name.

Copying a Storage The Create and Edit Storage Configuration panels let you copy storage
Configuration configurations within the same data dictionary. The Copy Storage Configuration
panel lets you copy storage configurations between data dictionaries in the same
database.

 To Copy a Storage Configuration

1 From the Storage Configurations node in the object tree, right-click any
storage configuration and select Copy from the menu.
2 Specify the Storage Configuration you want to copy.
3 Specify the Copy to Dictionary to which you are copying the configuration.
4 In the As Configuration field, specify the name of the configuration.
5 Click Copy.

Deleting a Storage Only unused (and thus unlocked) storage configurations can be deleted.
Configuration

 To Delete a Storage Configuration

1 From the Storage Configurations node in the object tree, right-click an
unused storage configuration, and select Delete from the menu.
The Delete Unused Storage Configuration panel opens with the subject
data dictionary and storage configuration selected in the lists.
2 With the appropriate data dictionary and storage configuration selected, click
Delete to remove the storage configuration from the object tree.
A confirmation dialog box opens.
3 Click Yes to confirm and OK to acknowledge the deletion.

9-10 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 10 Reference Data Management

In This Chapter

Introduction ..............................................................................................10-2
Reference Tables .......................................................................................10-3
Reference Catalogs....................................................................................10-4
Troubleshooting ........................................................................................10-5

Reference Data Management 10-1

Schlumberger Private - Customer Use
Introduction

Introduction
Seabed includes a set of tables that provide valid values for specific Seabed data
attributes. Seabed contains reference data that is pre-populated with industry-
standard values. Reference tables and reference catalogs reside in the data
dictionary. Seabed uses these tables to validate data, as when adding or updating
data records or when merging data from a staging area into a project.
For example, the Tank object references the following reference tables:
• R_Tank as Tank_Type
• R_Tank_End_Shape as First_Tank_End_Shape_Code and
Second_Tank_End_Shape_Code
• R_Orientation as Orientation_Code
• R_Tank_Cat as Tank_Cat

• • • • • •
Note: There is no Seabed tool (for example, DBAdmin) that maintains reference
data. Insertions, deletions, and updates should be done through your
favorite SQL tool.

• • • • • •
Note: By default, a user granted access to a project has the ability to read
reference data, but not to insert or update that data. Users who need to
insert or update reference data must be granted the <ddname> _Sys
database role (where <ddname> is the name of the data dictionary).

10-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Reference Tables

Reference Tables
A reference table contains a set of valid values for specific Seabed data attributes.
The naming convention for a reference table is R_ added as a prefix to the table
name, such as R_Tank. The structure of a reference table can be viewed through the
Web Report. If the reference table is used as a foreign key reference, the reference
table can be accessed through a link from the Values Domain/Measurement column
for the foreign key attribute in the Web Report. Generally, a reference table contains
at least the following properties:

Property Description
Code A standard abbreviation, mnemonic, or short code that
represents the reference value
Name The spelled-out name of the reference value
Description A textual description of the reference value
Source The person, company, or application that defined or
specified the data (content) for this instance, and is
considered to be responsible for it, such as POSC,
EPSG, API, and ISO
Active_Flag 1 = use without restriction
0 = avoid use
Update_Date Date of the most-recent modification to the entity. (This
field is optional and can be used as an audit variable.)
Update_User The name of the user responsible for the last
modification to this entity. (This field is optional and can
be used as an audit variable.)

The Code property is used as the primary key for the reference table. If there is a
requirement for a multi-column Primary Key, then a surrogate key (Ref_Id) is added.

Reference Data Management 10-3

Schlumberger Private - Customer Use
Reference Catalogs

Reference Catalogs
A reference catalog contains a set of valid values for specific Seabed data attributes,
and contains valid entries, such as catalog number, manufacturer, and weight, from
industry product catalogs. The naming convention for a reference table is R_<object
name>_Cat, such as R_Tank_Cat for the Tank catalog entries. The structure of a
reference catalog can be viewed through the Web Report. If the reference catalog is
used as a foreign key reference, the reference catalog can be accessed through a
link from the Values Domain/Measurement column for the object in the Web Report.
A reference catalog contains the same properties as a reference table and more,
depending on the characteristics of the catalog item. For example, the additional
R_Tank_Cat properties are as follows:

Property Description
Catalog_Number A catalog or part number for a facility
Cone_Height The height of the cone (for tanks with conical ends
only)
Conversion_Factor A number that can be used instead of height and
diameter values to determine tank volume for a vertical
tank with flat ends
(Conversion Factor) * (Tank Level) = Volume
Diameter The diameter of the tank
First_Tank_End A reference value that describes the shape of the first
_Shape_Code end of the tank—for example, round, flat, conical
Foreign Key to R_Tank_End_Shape
Height The height or length of the tank, depending on the
orientation of the tank. For vertical tanks, this value
represents the height of the tank; for horizontal tanks,
it represents the length of the tank.
Manufacturer Name of the business associate who manufactured the
item
Orientation_Code A value that describes the orientation of a tank, such as
whether it is horizontal or vertical
Ref_Id The surrogate identifier of an instance of reference data
Second_Tank_End_ A reference value that describes the shape of the
Shape_Code second end of the tank—for example, round, flat,
conical
Foreign Key to R_Tank_End_Shape
Storage_Capacity The storage capacity of the tank
Tank_Strapping_Table The identifier of the strapping table that is, by default,
used for this tank model
Tank_Type The type of tank, such as spherical, rectangular, or
cylindrical

10-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Troubleshooting

Troubleshooting
During the load process, if you receive an error message stating the foreign key is
violated, the merge process will fail because a value you are using in one of your
data attributes is not a valid value listed in the reference table. To correct this error,
open the Web Report and examine the reference table or reference catalog used to
validate the object to make sure you are using a correct value type.

Reference Data Management 10-5

Schlumberger Private - Customer Use
Troubleshooting

10-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 A Coordinate System Management

Introduction A Coordinate Reference System (CRS) is a set of mathematical rules for specifying
how coordinates are assigned to points.
A CRS provides the structure, or framework, that holds the complete definition of
the coordinate system. For example, longitude and latitude measurements cannot
be accurately determined without a coordinate reference system. Many coordinate
reference systems have well-known definitions provided by knowledge standards
organizations and agreed to by commercial software vendors. Others are customized
by companies and individuals at the project level. Currently, approximately 400
geographic CRSs and more than 2,000 projected coordinate systems are available
for use from the Esri ArcSDE projection engine. A large number of legacy or
proprietary CRSs are also available.
Seabed references well-known coordinate systems, lets you select the coordinate
system to use for stored data, and recommends a set of coordinate systems for
working with data in a project. Data that is encountered while loading using the
recommended coordinate systems is automatically transformed into data stored
using the storage coordinate system.
Seabed lets you define which CRS you want to use at the project level. Typically, a
geologist or a project domain expert determines the appropriate storage CRS and
recommended CRS codes.

Standards The CRS model is based on the following complimentary standards, which share a
Organizations common set of basic principles:
• OpenGIS Consortium (OGC) specification, transformation standard
• European Petroleum Survey Group (EPSG), content standard
• POSC Epicentre Model V3.0
• ISO Technical Committee 211

Spatial Data Spatial data needs an accurate coordinate reference system. Spatial data can be
misinterpreted if the data does not reference a well-defined CRS. The CRS locates
the reference data in two-dimensional or three-dimensional space. You need to
know the CRS when combining data from different sources.

Coordinate System Management A-1

Schlumberger Private - Customer Use
Potential Error A typical error when combining spatial data from two different sources is not
defining a coordinate system. The potential error when using a reference point
without a well-defined coordinate system is illustrated below (Fig. A-1).

Fig. A-1 Location Variation When Not Using CRS

Scenarios Seabed offers solutions to the following spatial data scenarios:

Scenario Description Seabed Solutions

Spatial data arrives Spatial data:
at the system, • Conforms to a supported CRS
typically using a
loading procedure or • Contains a description of a non-supported CRS
data entry procedure • Contains a description of a non-supported CRS that
agrees with a supported CRS
Spatial data can be Spatial data can be transformed to any required CRS to
transformed participate:
• As project data
• In a delivered product, such as being represented on a
monthly-production map
Examples:
• An application that gets data from multiple domains,
sources, processing histories, etc., into a common CRS
• Mapping and the use of position data in algorithms to
determine distances, areas, volumes, azimuths, etc.
You can query spatial Seabed reports the details of the CRS in use.
data

A-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

Scenario Description Seabed Solutions
Supported CRSs Seabed CRSs adhere to standards set by standards
match client needs organizations, such as EPSG and OpenGIS Consortium.
Support means that Seabed can represent the explicit
CRS and includes software to transform data conforming
to the CRS to use other standard CRSs.
Identify and match Matches are determined by examining the names and
the CRS of incoming parametric details of the CRS as it is described for the
spatial data incoming data.
Perform quality check Run quality check procedures on seismic reference data,
on spatial data petrophysical data, and geological data.
Support “spatial Spatial data keeps its processing history, and Seabed
forensic” when data allows you to query for the spatial data processing history
appears inconsistent to reconstruct the original data.
Support editing the Seabed allows you to augment CRS descriptions or
CRS of existing data replace one CRS with another without transforming or
reloading data.
Minimize Seabed does not perform transforms unless it is required.
transformations
Select a CRS A project expert or project domain expert selects a CRS
based on the following criteria:
• Cartographic properties, such as one exhibiting equal-
area properties as opposed to an equidistant or
conformal projection
• For area and extent of interest, such as a large area
leading to use of geographic coordinates versus a small
area or an area with identified areal trend for which a
projected system would be more appropriate
• Minimize costs of transformation, such as if data
routinely arrives and is delivered in the same regional
CRS
Select a CRS-to-CRS Seabed allows you to select a transformation method
transformation based on the following:
method • Accuracy of a transform method
• Geographic location
• Original survey method
• Data owner or client
• Regulatory fiat
• Availability of a supported method
• Matching precedent established in existing data
The result of establishing the criteria for selecting a
transformation is a set of defaults and preferences that
can be applied by a non-expert in the field.

Coordinate System Management A-3

Schlumberger Private - Customer Use
Coordinate System Coordinate systems can refer to geographic, projected (planar), or local coordinate
Types systems.

Geographic CRS A geographic CRS is a georeferenced coordinate system with axes of latitude,
longitude, and elevation. A geographic CRS is defined by a datum (reference point),
an angular unit of measure (such as degrees or grads), and a prime meridian. Depth
measurements require you to specifically state the coordinate system for the vertical
dimension.
A geographic CRS is illustrated below (Fig. A-2).

Fig. A-2 Example of Geographic CRS

Ellipsoidal height provides the vertical dimension in a three-dimensional (3D)

geographic CRS. The two-dimensional (2D) CRS is a simpler horizontal subset of a
geographic 3D CRS and is more readily used. Customized extensions to the
geographic CRS should be made in and referenced from the data dictionary.

Projected CRS A projected CRS is a flat 2D surface with axes of east and north or X and Y. A
projected CRS transforms latitude and longitude to X,Y coordinates, which converts
the CRS from 3D to 2D. Distortion occurs when converting coordinates from 3D to
2D. This distortion must be taken into consideration. A projected CRS consists of a
linear unit of measure such as meters or feet, a map projection, the specific
parameters used by the map projection, and a geographic coordinate system.
A projected CRS is illustrated below (Fig. A-3).

Fig. A-3 Example Projected CRS

Customized extensions to the projected CRS should be made in and referenced from
the data dictionary.

A-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

Local CRS The local CRS links to a projected or geographic coordinate system and lets you
define a specific reference for a specific situation. Local coordinate systems are
typically used for locating positions in a borehole. Typically, a local CRS is not reused
and is created during project scope assessment.
A local CRS can be a compound CRS or an engineering CRS, which are defined as
follows:
• A compound CRS is a georeferenced combination of two independent coordinate
systems, typically combining 2D geographic or projected CRS with a 1D vertical
reference system. Unlike the geographic 3D CRS, the horizontal and vertical
components of a compound CRS are independent.
• An engineering CRS is a non-georeferenced CRS in 1, 2, or 3 dimensions and is
typically a grid-based system for a local facility. An engineering 2D CRS has
horizontal axes i and j. An engineering 1D CRS has a vertical axis k. Engineering
2D CRSs include engineering site grids and 3D seismic binning grids.
An example lattice grid of a local coordinate system is illustrated below (Fig. A-4).

Fig. A-4 Example Local CRS

Functional CRS Functional CRS categories are general conventions that clarify, safeguard, and
Categories enhance the utility of using CRS. You can create a storage or recommended CRS
during project creation using Seabed Oracle Database Manager. For more
information, refer to “Creating a Project” on page 5-4.

Storage CRS The storage CRS is the coordinate system used to store project data and is the
default CRS for a project. The storage CRS determines the coordinate system that is
used as a reference for data stored in a project. The storage coordinate system is
set when you create a project, and after it is set, it cannot be changed. This
restriction ensures the integrity of the reference data in the project.

• • • • • •
Note: The storage CRS is stored in the PROJECT_DEFAULT storage table.

Coordinate System Management A-5

Schlumberger Private - Customer Use
Recommended CRS Define a list of recommended CRSs for a project to limit the number of CRS codes
that can be selected for a project. A geologist or project domain expert sets the
recommended CRSs based on the expected scope of a project. Recommended CRSs
can be changed as necessary. For more information on setting recommended CRSs,
refer to “Setting the Recommended CRS” on page 5-15.

• • • • • •
Note: The list of recommended CRSs is stored in the
Project_Recommended_CRS table.

The list of recommended CRSs can change over time. You can include CRSs from
alternate software packages, which are converted to internally recognized CRSs, as
well as different transformations that can be used at different times or under
different situations.

• • • • • •
Note: In Seabed, the list of recommended CRSs and CRS transformations applies
only to 2D coordinate systems that are part of the reference catalog.

Transformation Seabed can automatically transform stored data based on a storage CRS to working
data based on a recommended CRS, and vice versa.
Transformation changes the data because the target CRS is based on different data
than the source CRS. For example, land and marine seismic surveys are most
conveniently positioned by GPS satellite in the WGS 84 geographic CRS. However,
the national geodetic CRS used by a particular country might be an earlier CRS
created for a land-based system. Therefore, you may need to transform the WGS 84
data to the national geodetic CRS to avoid discrepancies in position. This type of
transformation is between source and target geographical CRSs with coordinates
expressed in geographical terms. This type of transformation is also known as a
datum shift.

Locations A location is a spatial object that consists of position, line, and area entities. The
position entity is a point referenced to a coordinate system, which is able to preserve
its original location. The line entity consists of line vertexes, which include a set of
position entities that define the line. The area entity consists of area vertexes, which
include position entities that define the area. Seabed uses the ArcSDE projection
engine to determine locations. The ArcSDE projection engine only uses positions to
define a shape, and line vertexes and area vertexes are controlled from positions.
The projection engine does not operate on or analyze lines or polygons.

• • • • • •
Note: Seabed implements the area entity as a list of area vertexes. The
Area_Vertex entity includes a natural key, which contains the Area_ID,
Polygon_Rank, Line_Rank, and Vertex_Rank attributes.

A-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 Locations are stored in Seabed as spatial objects with specific attributes of
established business entities. These spatial objects can have extensive context on
how the measurements are made and what the measurements mean. For example,
boreholes typically use spatial data for items located in a borehole, such as borehole
points, targets, deviation survey points, completion intervals, and bottomhole
locations. Each of these items has attributes that describe its location in the
borehole.

Spatial Data Seabed can store spatial objects, such as location, in the following formats:
Storage
• Relationally as a recognized business entity, such as Borehole_Point.MD
• As bulk data in a user-defined format
• As a spatial object with Position.Normal_Latitude and
Position.Normal_Longitude
Seabed also lets you preserve spatial data as a binary spatial representation of the
position using ArcSDE.

Seabed CRS Storage Seabed stores data about coordinate systems, including the special cases of local
Implementation and borehole coordinate systems, in the Coordinate_System entity, which includes
the following properties.
Table A-1 Properties of the Coordinate_System Entity

Property Description
Id System-generated ID, which the system generates
for all Seabed entities
Coordinate_System_Type Identifies one of the following types:
• Geodetic_System
• Projection_System
• Local_System
CRS • Refers to an external Code from
R_Coordinate_Ref_System
• Used primarily for projection and geodetic
coordinate systems
• Can be null for Local_System(s)
Name • Meaningful name for Coordinate_System
• Used primarily for references to SDE
Carto_Transform Transformation method to storage CRS

Seabed handles unknown coordinate systems by setting the Name to UNKNOWN

and setting the CRS to null. After the Coordinate_System has been identified, these
entries can be changed to the known values.
The Local_System entity is defined as a Sub_Type of the Coordinate_System and
has additional properties used to define translation and rotation, which are based on
the underlying coordinate system. The borehole Coordinate_Systems are defined as
local coordinate systems with respect to the field projection.

Coordinate System Management A-7

Schlumberger Private - Customer Use
 The original coordinates of point data are preserved so that normalized coordinates
can be recomputed as necessary using different algorithms or a corrected definition
for the original coordinate system. The following table describes the Seabed
attributes for Position.

Property Description
Original_X_Longitude X if projection; longitude if geodetic
Original_Y_Latitude Y if projection; latitude if geodetic
Cartographic_Reference_System

A-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 B Match Rule

Introduction During the data-loading process it is important to distinguish new data items from
existing data items. You will typically want to insert new items, and you might want
to update existing ones. The process of determining if an item already exists is
known as “matching.” It is one of the first steps in the data-merge process. Seabed
uses match rules to determine if an incoming data item is new or if it already exists.
After this distinction is determined, Seabed can perform different types of operations
based on the status. These are known as Merge Rules. The default merge rule is
UPSERT, where a match causes the data item to be updated and no match causes
the data item to be inserted.
Match rules are defined at the entity type level (for example, Well has a match rule
distinct from Borehole), and these rules are stored in the data dictionary. Match
rules consist of a combination of local attributes and references to other entities. As
part of the Seabed logical data model, all natural keys automatically become match
rules for that entity type. Seabed Oracle Database Manager allows an authorized
user to add, edit, and delete match rules to meet their specific matching
requirements.

Managing Match When you create a data dictionary, match rules are automatically created. These
Rules match rules represent any natural keys defined as part of the logical data model. If
an entity lacks a natural key, the entity will not have a match rule. For example, the
natural key for the Well entity is UWI, which is also a default match rule. Changes to
the match rules do not affect the definition of any natural keys.

• • • • • •
Caution: If you change the match rules for a dictionary that contains one or
more projects with data already loaded, the new match rules can
adversely affect the behavior of the merge operation.

Match Rule B-1

Schlumberger Private - Customer Use
Modifying Match Rules Use the following instructions to add, remove, or change a match rule.

 To Add, Remove, or Change a Match Rule

1 From the main menu, select Tools > Dictionaries and Projects > Define
Match Rule.
The Match Rule Definition panel opens (Fig. B-1).

• • • • • •
Note: You must access match rules from the main menu. You cannot access
match rules from the object tree.

Fig. B-1 Match Rule Definition Panel

2 Select a data dictionary from the Dictionary list.

The current match rules for the selected dictionary appear in the right list
boxes.
The Object List populates with objects available to specify in match rules.
3 Select an item from the Object List to define a match rule.

• • • • • •
Note: Only one match rule can be defined for an object at a time.

B-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 The Attributes and References lists refresh with attributes and references as
follows:
• Attributes – This pane consists of two lists. The list on the left displays
attributes for this entity available for match rules. The list on the right
displays attributes already defined as part of a match rule.
• References – This pane consists of two lists. The list on the left displays
references available for match rules. The list on the right displays references
already defined as part of a match rule.
4 To modify match rules, use the following keystrokes:
• Right arrow (>) – Add attributes and/or references to the match rule
• Double right arrow (>>) – Add all attributes and/or all references to the
match rule
• Left arrow (<) – Remove attributes and/or references from the match rule
• Double left arrow (<<) – Remove all attributes and/or references from the
match rule
5 Click Save to save the match rule definition for the selected object.
6 Repeat Step 3 through Step 5 as necessary to define match rules for objects
within a data dictionary.
7 Repeat Step 2 through Step 5 to define match rules for objects in a different
data dictionary.

• • • • • •
Warning: After you have defined your match rules, you must click the Generate
button to generate these rules. Until the match rules are generated,
they will not be used during the match-and-merge process.

Match Rule B-3

Schlumberger Private - Customer Use
B-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 C Oracle Tablespace Management

Introduction Oracle has a very powerful and flexible mechanism for managing its database files.
A properly trained Oracle Database Administrator (DBA) is the best resource for
optimizing the performance of an Oracle database, including the space used by the
data files.
This section provides information about how Seabed uses tablespaces so that DBAs
can make informed decisions about tablespace management in Seabed. This section
might also provide the non-Oracle DBA with the basic guidance needed to effectively
manage tablespaces.

Overview of Oracle Oracle divides its database storage into the following logical storage structures.
Logical Database
• A database is stored in one or more tablespaces.
Storage Structures
• A tablespace uses one or more data files to store the data on disk.
• A data file contains one or more data blocks.
• A data block is a fixed number of bytes in a data file.

Organization • A contiguous collection of data blocks form an extent.

• A set of extents allocated for a certain logical structure forms a segment.
• Each table is assigned a data segment.
• A segment and all its extents are stored in one tablespace.
• A segment can span multiple data files.
• An extent cannot span multiple data files. A single extent is wholly contained
in one data file.
• Many tables can share the same tablespace.
• Many database accounts can share the same tablespace.
• LOB columns can be stored in a tablespace that is separate from the other
columns in a table.
• A table can be partitioned to use multiple tablespaces based upon some well-
defined rule.

Expanding Storage • The database adds extents to a segment when the segment becomes full.
• Data blocks are allocated to the extent independently.
• The high water mark is the boundary between used and unused space in a
segment.

Oracle Tablespace Management C-1

Schlumberger Private - Customer Use
Tablespace/Data Tablespaces and data files have many associated properties. The most significant of
File Properties these properties are shown in the following table:
Table C-1 Tablespace Properties

Property Description
Tablespace Name The name used to identify the tablespace
Data files A list of data files used to store the data for the
tablespace
Extent Management Locally managed tablespaces use a bitmap in each data
file to keep track of free space. Dictionary-managed
tablespaces use an internal system table to keep track
of the free space. Locally managed tablespaces have
much better performance.

Autoallocated extents automatically vary in size
according to the tablespace needs. Uniform extents
have a fixed size.
Segment Space Automatically managed segments use a bitmap to
Management manage free space in the segment. Manually managed
segments use free lists for managing free space in the
segment.
Block Size Specifies the number of bytes that make up a data
block in the data file
File Size Type Small file tablespaces can be used on most file systems.
The data files in a small file tablespace are typically
limited to 32 GB per data file (varies by operating
system). Big file tablespaces can have only one data
file, which is typically limited to 32 TB. Big file
tablespaces typically require a 64-bit file system to
handle the large files.
Automatic If Autoextend is on, the data files are allowed to grow
Extension as needed. If Autoextend is off, the data files remain at
their fixed size.
Quota Different database accounts can be assigned quotas on
a tablespace to limit their tablespace usage.

Automated File and Oracle provides a logical volume manager that can be used in place of your normal
Storage operating system file structure to manage the disks used for your database. When
Management using Automated Storage Management (ASM), the Oracle database automatically
manages the disks and files needed for the tablespaces.

C-2 Seabed Oracle Database Manager Guide April 2014

Schlumberger Private - Customer Use

Managing Disk You can manage the disk space used by an Oracle database using several methods,
Space Usage including the following:
• Multiple tablespaces
- Use different tablespaces for different Seabed projects.
- Use different tablespaces for different tables in a single Seabed project.

• Multiple data files per tablespace

- Use multiple data files on multiple disks to allow for parallel access to the data
files.

• Different properties on tablespaces and data files to control size and usage
- A data file on one disk might be allowed to grow as needed, whereas another
data file on another disk may be fixed in size.

LOB Storage Large object columns present some special concerns regarding space management.
Management
• They can be stored in a different tablespace than the rest of the columns in a
table.
• They are typically large (sometimes many billions of bytes).
• Their data can vary widely in size in a single table. (Some rows might store a few
bytes, whereas other rows store many billions of bytes.)

Seabed typically stores LOB data in a separate tablespace (for example, SDS_LOB).
This allows the DBA to store this large data on a separate disk if needed.

Seabed Storage The Seabed Storage Configuration system allows Seabed administrators to assign
Configuration storage of project data to particular tablespaces.
System
Seabed has three preset storage configurations (RECOMMENDED, DEFAULT, and
PROSOURCERESULTS). The DEFAULT storage configuration stores the project’s table
data as follows:
Table C-2 DEFAULT Storage Configuration Tablespaces

Tablespace Usage
SDS_TABLE Used for Seabed system data, reference data, and
project data
SDS_INDEX Used for storing database indexes on table data
SDS_LOB Used to store large object column data

For more information about the RECOMMENDED and PROSOURCERESULTS storage

configurations, refer to Chapter 9 “Storage Management.”

Oracle Tablespace Management C-3

Schlumberger Private - Customer Use
 Many DBAs store the data files for these tablespaces on separate disks so that
queries can access the table and can index data in parallel.
If you have a project (PROJECT1) on which you expect to store a large amount of
data and you want to store it separately from the rest of the projects, you can create
a storage configuration called, for example, PROJECT1_STORAGE. For this
configuration, you can then specify that you will use the following tablespaces:
• PROJECT1_TABLE for table data
• PROJECT1_INDEX for index data
• PROJECT1_LOB for LOB data

When defining these tablespaces, you can specify that the data files will be stored
on different disks so that querying data from PROJECT1 is not slowed down by disk
I/O contention with other projects.
The Seabed Storage Configuration system allows control of the project’s tablespace
usage down to individual tables. In other words, you can specify that each table in a
project will be stored in a different tablespace (or any combination of tables and
tablespaces).

Reclaiming Unused When a tablespace is shared across multiple tables and/or multiple projects,
Tablespace reclaiming unused space can be difficult. The two main reasons for this are 1) the
high water mark for the tablespace, and 2) row movement within a table, across
tables, or across accounts.
In the diagram in Fig. C-1, the tablespace is shared across two accounts (A1 and A2)
and three tables (A1.T1, A1.T2, and A2.T1). Notice that when Row #2 in Table
A1.T1 is deleted, the total size of the tablespace and the amount of free space
above the high water mark remains unchanged. Deleting a row from a table does
not move the other rows.

Fig. C-1 Tablespace Components

C-4 Seabed Oracle Database Manager Guide April 2014

Schlumberger Private - Customer Use

Basic Space The following commands are typically used to reclaim unused space:
Reclamation
Commands • ALTER TABLESPACE RESIZE – This command can be used to shrink a
tablespace, but you cannot shrink it below the high water mark; therefore, the
free space created by deleting Row #2 will not be reclaimed.
• ALTER TABLE <tablename> SHRINK SPACE – If all the rows in the
tablespace are from the same table in the same account, and that table has ROW
MOVEMENT enabled, this command will move the rows in the table so as to move
the free space above the high water mark. But if there are other tables or
accounts between the subject table and the high water mark (as in Fig. C-1), this
command has no effect because the other tables and/or accounts will block the
free space from being moved to the free space above the high water mark.

Reclaiming Two other options are available given the scenario described in Fig. C-1. Each option
Tablespace in has benefits and drawbacks. Option 1 requires a good deal of preparation time and
Seabed DBs effort, but after being set up properly, it works very well. Option 2 involves much
less setup effort, but it requires a large amount of disk space and the time needed to
copy extremely large files to a temporary directory and back again.

 To Configure for Using the ALTER TABLE ... SHRINK SPACE Command
This example demonstrates how to resize the PROJECT1_BA_LOB.DBF data file
associated with the BULK_ARRAY_ table in a specific project called PROJECT1.
1 Create a tablespace called PROJECT1_BA_LOB for storing the LOB data in the
BULK_ARRAY_ table in project PROJECT1 in data file PROJECT1_BA_LOB.DBF.
2 Create a Seabed storage configuration that is used only for PROJECT1.
a. Create a storage configuration called PROJECT1_SC.
b. For Submodel = <any> and Table = <and>, set the tablespace assignments
as follows:
• Tables = “SDS_TABLE”
• Indexes = “SDS_INDEX”
• LOBs = “SDS_LOB”

c. For Submodel = “Bulk” and Table = “Bulk_Array,” set the tablespace

assignments as follows:
• Tables = “SDS_TABLE”
• Indexes = “SDS_INDEX”
• LOBs = “PROJECT1_BA_LOB”

3 Create the project PROJECT1 and use the storage configuration PROJECT1_SC.
Do not use this storage configuration for any other projects.
4 Log into the project and execute the following SQL command:
ALTER TABLE BULK_ARRAY_ ENABLE ROW MOVEMENT;
5 Use the project as normal.

Oracle Tablespace Management C-5

Schlumberger Private - Customer Use
 6 If you want to resize the data files for the LOB data in the BULK_ARRAY_ table
in the project, perform the following steps:
a. To consolidate the free space and move the high water mark, log in to the
project and execute the following SQL statement:

ALTER TABLE BULK_ARRAY_ MODIFY(BULK_DATA) (SHRINK
SPACE);
b. To estimate the location of the high water mark (minimum size of the data
file), log in as SYSTEM and execute the following query:

SELECT DE.TABLESPACE_NAME, DDF.FILE_NAME,
CEIL(MAX(DE.BLOCK_ID * DT.BLOCK_SIZE)/1048576) HWM
FROM DBA_EXTENTS DE,
DBA_TABLESPACES DT,
DBA_DATA_FILES DDF

WHERE DE.TABLESPACE_NAME = ‘PROJECT1_BA_LOB’
AND DE.TABLESPACE_NAME = DT.TABLESPACE_NAME
AND DE.FILE_ID = DDF.FILE_ID

GROUP BY DE.TABLESPACE_NAME, DDF.FILE_NAME
ORDER BY DE.TABLESPACE_NAME, DDF.FILE_NAME;
c. Now that you have the target high water mark, execute the following SQL
statement to resize the data file where <xxx> is the high water mark value:

ALTER DATABASE DATAFILE
‘C:\DATAFILES\PROJECT1_BA_LOB.DBF’ RESIZE <xxx>M;
If you get a message, “ORA-03297: file contains used data beyond requested
RESIZE value,” increase the <xxx> value and try again. (This is because the
query does not take into account any overhead used by the Oracle system.)

Copying Data to a New Another way to shrink the size of a data file is to use the Oracle Enterprise Manager
Tablespace to reorganize the tablespace. This process consists of the following steps:
1. Copy all the data from the original tablespace to a new tablespace.
2. Drop the original tablespace.
3. Rename the new tablespace back to the original name.

The advantage of this method is that you will need to do very little work before you
create the project. The disadvantage is that a great deal of data is moved, and you
temporarily need double the storage capacity to contain the two copies. Because the
tablespace might be shared by many tables and many projects, the amount of data
to be copied can far exceed the free space that will be reclaimed. Also, all project
tables that use the tablespace will be frozen while the data is being copied.

 To Reclaim Free Tablespace Using Oracle Enterprise Manager

1 Log in to Oracle Enterprise Manager using the SYSTEM account.
2 Click the Administration tab.
3 Click the Tablespaces link.
4 Select the SDS_LOB tablespace you want to reorganize.

C-6 Seabed Oracle Database Manager Guide April 2014

Schlumberger Private - Customer Use

 5 Select the Reorganize action.
6 Click Go.
7 Click Next. (You do not need to change the tablespace selected or set any
attributes.)
8 Using the default options, click Next.
9 Review any issues in the Impact Report. If everything looks correct, click Next.
10 Enter your Oracle username and password and click Next.
11 Review the script summary. Pay particular attention to the size of the data file
that is being created. If it is the same size as the current data file, you might
want to use the Save Full Script feature, then edit the file to make the data
file smaller. If the data file is set to autoextend, you can make the file as small
as you like because the file will grow as needed.
12 Execute the edited script or submit the job (as appropriate).

Partitioning ProSource Seabed supports high level partitioning, where you can set a partitioning
Tablespace scheme with different tablespaces for any of the TABLE, INDEX or LOB data.
The granular level of partitioning that involves splitting the table in two different
tablespaces based on a controlling attribute is supported only for entities that have a
LOB column.
You can use either of the two ways to partition table with LOB columns using
storage configuration:
Set the TABLE_tablespace for the Production_Header entity to SDS_LARGE
or
Create a new storage configuration with partitioning scheme and mappings. Create
the project using the newly created storage configuration.
After the table is created, run an alter table command on Production_Header table
to move the required partition to the SDS_LARGE tablespace.
Example:
ALTER TABLE PROJ.PRODUCTION_HEADER_
MOVE
PARTITION PART_2
NOLOGGING
NOCOMPRESS
TABLESPACE SDS_LARGE
PCTFREE 10
INITRANS 1
MAXTRANS 255
STORAGE (
BUFFER_POOL DEFAULT )

Oracle Tablespace Management C-7

Schlumberger Private - Customer Use
 • • • • • •
Note: Partitioning is an extra-cost Oracle option which is not included in Oracle
RTE licenses purchased from SIS. You need to contact Oracle directly to
purchase licenses for Partitioning.

C-8 Seabed Oracle Database Manager Guide April 2014

Schlumberger Private - Customer Use

 D Standard Accounts

Seabed Accounts This section describes the privileges provided with all standard Seabed accounts.
Overview This information will enable the Data Administrator or System Administrator to
evaluate potential security threats with respect to any of the standard accounts (for
example, threats due to improper granting of DBA privileges). Access to those
accounts can then be limited to selected privileged users in the organization.
Seabed uses three types of accounts: Fixed Accounts, Variable Accounts, and Third-
Party Accounts.
• Fixed accounts are the default accounts provided with standard Seabed
installations. These account names cannot be changed.
• Variable accounts vary according to the names provided at the time of account
creation (for example, DD1, Proj1). The names of variable accounts used
throughout this document are the names of the account types.
• Third-Party accounts are created by third-party software.

Fixed Accounts SDS_SYS

This account is used implicitly during the installation process. You do not need to log
in to this account on a routine basis. You must access this account only if a patch or
a problem work-around is provided by SIS Engineering or the InTouch team
resulting in content updates.
The following points should be taken into consideration with reference to the
SDS_SYS account:
• It is an “internal” or “root” account created during installation. This account has
many “bootstrap” procedures to create other accounts and perform administrative
functions, such as managing data dictionaries, projects, users, and project access.
• It should never be used for general data access.
• Passwords should be kept highly secure.
• Administrative privileges to modify SIS_CATALOG
• You can select and modify data in project and data dictionary accounts.

• It is typically assigned to the SDS_SYSTEM_PROFILE.

SIS_ADMIN
This is a type of “super admin” account and is created by default. This account
should be used to create additional administrative accounts for specific users (rather
than being used only as an admin account, since the real user will be anonymous).
This can be done through the IM Admin console and not by directly logging on to
the SIS_ADMIN account via SQL. 
You can select and modify data in project and dictionary accounts through this

Standard Accounts D-1

Schlumberger Private - Customer Use
 account. However, this only holds true for projects if you log in through SQL. Data
can only be loaded for those projects you can access.
The following points should be taken into consideration with reference to the
SIS_ADMIN account:
• It is the initial administrator account created during installation.
• It provides full administration privileges, as well as privileges to create other
administrators with the same or limited privileges.
• While it is possible to use SIS_ADMIN to administer Seabed, it is not
recommended. Instead, SIS_ADMIN should be used to create additional
administrative user accounts, which should then be used to administer Seabed.
• Only one Seabed SIS_ADMIN account is allowed in a database instance.
• Passwords should be kept highly secure.
• It can be used to create data dictionaries, projects, and users.
• Administrative privileges to modify SIS_CATALOG
• You can select and modify data in project accounts and data dictionary accounts.

• It is typically assigned to the SDS_ADMIN_USER_PROFILE.

• It is initially granted SDS_UPGRADE_ROLE to allow SIS_ADMIN to upgrade Data
Dictionaries and Projects. Once all accounts have been upgraded, this role can be
dropped from SIS_ADMIN to lower its privileges.
SIS_CATALOG
Only administrators can access the SIS_CATALOG account. However, there will be
very few occasions when you need to log in to this account, certainly not through
SQL. 
Certain actions such as creating Seabed data model extensions or adding PS meta
data, etc., will result in adding or modifying content in this account. This is handled
indirectly through other tools like the ProSource client, the IM Admin console,
Seabed Extensibility UI, etc.
The following points should be taken into consideration with reference to the
SIS_CATALOG account:
• It is a fixed account, created during Seabed installation where Grand Unified Meta
Model (GUMM) is stored.
• It is only for internal system usage. This account is not to be used by users
directly.
• It holds a collection of common metadata that represents one or more versions of
the Seabed logical data model, including various release versions and extended
data models. This metadata collection is used to generate and update the
database, data dictionaries, and services.
• Only one Seabed SIS_CATALOG account is allowed in a database instance.

• It is typically assigned to the SDS_SYSTEM_PROFILE.

SDS_INFO
This is an internal account that enables the software to gain basic information on
database content, such as lists of projects, etc. You do not need to log in to this
account on a routine basis.

D-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 The following points should be taken into consideration with reference to the
SDS_INFO account:
• It is a low-privilege account used to obtain basic information about the database.
• It is only for internal system usage. This account is not to be used by users
directly.
• Only one Seabed SDS_INFO account is allowed in a database instance.

• It is typically assigned to the SDS_SYSTEM_PROFILE.

Variable Accounts User

This is a type of account that can be granted access to projects by an administrator.
This is the most common type of Seabed account. Each person using Seabed should
log in using their own User account. The following points should be taken into
account with reference to the User account:
• It can be used to select reference tables, and select/write shared scope entities in
the data dictionary.
• It can be used to access views in projects.
• It can be used to execute some packages and procedures that exist in the data
dictionary.
• This type of account has read-only access to SIS_CATALOG.

• It is typically assigned to the SDS_NORMAL_USER_PROFILE.

Administrator
This is a type of User account that has privileges to create and manage other User
accounts. The following points should be taken into account with reference to the
Administrator account:
• It can be used to create project accounts.
• It can define Indexing service indexes, load matching, and chase rules.
• It can be used to access project data.
• It can be used to create User accounts, but cannot be used to create other
Administrator accounts.

• It is typically assigned to the SDS_ADMIN_USER_PROFILE.

Administrator who can create other Administrators
This type of account has the same privileges as an Administrator account, but it also
allows you to create other Administrator accounts (and additional Administrators
who can create other Administrator accounts).
• It is typically assigned to the SDS_ADMIN_USER_PROFILE.
Data Dictionary
• It contains Meta tables that contain data used to generate projects, staging areas,
and interfaces.
• It contains one version of the Seabed data model.
• It contains reference tables and some common entities shared by all projects
created from that data dictionary.

Standard Accounts D-3

Schlumberger Private - Customer Use
 • The data dictionary contains:
- Metadata – Describes the data model used by project accounts
- Reference data – For example, Units and Enumerations
- Shared data – Exploration and Production data shared between projects

• It contains all the reference table catalogs used for the following:
- Units
- Measurements
- Value Domains
- Enumerations of other reference values for validation

• This type of account has SELECT access to SIS_CATALOG.

• It is typically assigned to the SDS_SYSTEM_PROFILE.

Project
This type of account is an organized collection of Exploration and Production (E&P)
related data contained in the Seabed repository.The following points should be taken
into account with reference to the Project account:
• It serves as the main data store for E&P data.
• Standard Interface is implemented by Project account views.
• All measurements are stored in ‘Storage’ Units.
• Users should not log in with this database account, but instead, should log in
using the User account that has been granted access to the repository.
• This account type has SELECT access to SIS_CATALOG.

• It is typically assigned to the SDS_PROJECT_PROFILE.

Staging
This type of account is a mirror of the Project account that can be used by the
loaders to stage data before it is loaded into the project.
• Users are not granted access to staging accounts. When a staging area is bound
to a project, appropriate privileges are granted to load data into the staging
account, and once the data is loaded, the privileges are revoked.
• This type of account has SELECT access to SIS_CATALOG.

• It is typically assigned to the SDS_PROJECT_PROFILE.

Interface
This type of account is a set of views that are used to access project data.
• It is an “Auxiliary Interface” is implemented by the views in an Interface account,
which allows users to view data with different services, such as unit conversion.
• Users should not login using this database account, but should instead login using
the USER account that has been given access to “Auxiliary Interface”.
• It can be used for SELECT/WRITE access to project data.
• It can be used for SELECT access to SIS_CATALOG.

D-4 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 • It is typically assigned to the SDS_PROJECT_PROFILE.

Third Party Accounts In addition to the above accounts, the SDE account that comes along with installing
ArcSDE is also listed. ArcSDE is a third-party software application used to manage
spatial information in Seabed projects.

Seabed Roles Managing and controlling privileges is made easier by using Roles, which are named
groups of related privileges that are granted to users or other roles. Both roles and
direct system and object privileges may be assigned to different Seabed accounts.
This section covers the roles used in Seabed.

SIS_CATALOG_ADMIN Object Privileges

• CRUD operations on SIS_CATALOG
• EXECUTE for the following packages in SIS_CATALOG:
- SDS_Extend
- DP_Metadata_Import

SIS_CATALOG_READ Object Privileges

• READ SIS_CATALOG tables

<DD>_ADM Object Privileges

• CRUD operations on SDS* tables (tables for which the name starts with “SDS”)
- SDS_CHASE
- SDS_CHASE_DEPEND
- SDS_CHASE_ENTITY
- SDS_CHASE_IGNORE
- SDS_CHASE_INCLUDE
- SDS_CHASE_INPUT
- SDS_CHASE_MAP
- SDS_CHASE_PICK
- SDS_CHASE_RANK
- SDS_CHASE_RULE
- SDS_INDEX_ATTRIBUTE
- SDS_INDEX_ENTITY
- SDS_INDEX_FUNCTION
- SDS_INDEX_NAMESPACE
- SDS_INDEX_PATHEVAL
- SDS_INDEX_RULE
- SDS_INDEX_STATUS
- SDS_INDXSERVICE_ATTR

Standard Accounts D-5

Schlumberger Private - Customer Use
 - SDS_INDXSERVICE_ENTITY
- SDS_MATCH_ATTRIBUTE
- SDS_MATCH_RULE
- SDS_VIOLATION

• CRUD operations on the following reference tables in the data dictionary:

- R_CARTO_TRANSFORM
- R_COORDINATE_REF_SYSTEM
- R_CSMAP

• EXECUTE for the following packages in the data dictionary:

- SDS_Meta
- SDS_Merge
- SDS_Index
- SDS_Spatial
- SDS_Chase
- SDS_Storage
- SDS_DD_Admin
- SDS_Name
- CALC_Well_Point

• SELECT privilege on SDS_ID_SEQ

• SELECT privilege on the following SDS tables:
- SDS_Storage_Configuration
- SDS_Storage_Mapping
- SDS_Storage_Part_Mapping
- SDS_Storage_Part_Scheme

• SELECT the following reference tables in the data dictionary:

- R_UNIT_SYSTEM
- R_VERTICAL_REFERENCE
- R_VALUE_DOMAIN

• SELECT data dictionary Meta tables

<DD>_USER Object Privileges

• CRUD operations on Shared Scope entities in the data dictionary
• EXECUTE privileges on the following packages in the data dictionary:
- Disable_DD_Constraints
- Enable_DD_Constraints
- SDS_Index

D-6 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 - SDS_Spatial
- CALC_Well_Point

• SELECT Reference tables in the data dictionary

• SELECT Meta tables in the data dictionary
• CRUD operations on the following SDS* tables:
- SDS_MERGE_LIST
- SDS_MERGE_LOCK
- SDS_MERGE_OPERATION
- SDS_INDEX_PATHEVAL

• SELECT privilege on remaining SDS* tables.

<DD>_SYS Object Privileges

• INSERT, UPDATE and DELETE on Reference tables in the data dictionary
• INSERT, UPDATE and DELETE on the following BULK* tables:
- BULK_CAT
- BULK_DIMENSION_CAT
- BULK_PROPERTY_CAT

<PROJECT>_ADM Object Privileges

• CRUD operations on Event Service tables
• CRUD operations on the following SDS* tables:
- SDS_Indexservice_Rule
- SDS_Move
- SDS_MoveExt

• EXECUTE privileges on the following SDS* packages:

- SDS_CHASE_GEN
- SDS_CHASE_MANAGER
- SDS_CHASE_GET_WORKFLOW
- SDS_INDEXSERVICE_GEN

• SELECT privileges on a few project tables

<PROJECT>_IUSR Not used

<PROJECT>_SYS Not used

<PROJECT>_TAB Object Privileges

CRUD operations on project tables that store E&P data

<PROJECT>_USER Object Privileges

• Same privileges as <DD>_USER

Standard Accounts D-7

Schlumberger Private - Customer Use
 • CRUD operations on SDS_COUNTER
• CRUD operations on project views that contain E&P data
• CRUD operations on _REF views
• CRUD operations on the following tables:
- ASSOC_
- Data_Event_
- SDS_IndexService_Rule
- SDS_Merge_State
- SDS_Move
- SDS_MoveExt
- Session_Event
- Session_Interest
- User_Event
- User_Interest

• EXECUTE privileges on the following subprograms:

- DISABLE_CONSTRAINT
- ENABLE_CONSTRAINT
- SDS_CHASE_GET_WORKFLOW
- SDS_CHASE_MANAGER
- SDS_MERGE_MERGE

- GET_TRUE_ZONE_THICKNESS
- PS_WELL_LOG_DATA_DELETE
• SELECT privileges on the following sequences in the data dictionary:
- SDS_ID_SEQ
- SDS_ESPG_SEQ

<USER> Privileges
• SIS_CATALOG_READ – User receives this role by default.
• <PROJECT>_USER – User receives this role when assigned to a project.

<STAGING>_ADM Privileges
• SELECT privilege on the following staging tables:
- AZIMUTH_REFERENCE
- COORDINATE_SYSTEM
- PROJECT_RECOMMENDED_CRS
- PROJECT_RECOMMENDED_XFORM

<STAGING>_USER Privileges

D-8 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 • CRUD operations on staging tables that store E&P data
• CRUD operations on the following staging tables:
- ASSOC_
- SDS_CYCLE_LINK
- SDS_DUPL
- SDS_ENTITY_DEPENDENCY
- SDS_FILTER_LIST
- SDS_ID_MAPPING
- SDS_MERGE_LIST
- SDS_VISITED_ENTITY

- SDS_MATCH
• EXECUTE privilege on the following subprograms:
- SDS_MERGE_BUILD_DOV_Tables
- SDS_MERGE_DROP_DOV_Tables
- GRANT_PRIVILEGES
- REVOKE_PRIVILEGES
- SDS_MERGE_COMP_STATS
- SDS_MERGE_DELETE_STATS

- GET_TRUE_ZONE_THICKNESS
- PS_WELL_LOG_DATA_DELETE
• SELECT privilege on the following sequences:
- SDS_EPSG_SEQ
- SDS_ID_SEQ

• SELECT privilege on the following staging tables:

- ACCOUNT_INFO
- SDS_MATCH_ATTRIBUTE
- SDS_MATCH_RULE

SDS_ Object Privileges

ADMINISTRATOR
• CRUD operations on Event Service tables and the following reference tables in the
data dictionary:
- R_CARTO_TRANSFORM
- R_COORDINATE_REF_SYSTEM
- R_CSMAP

• CRUD operations on SDS* tables and views (name starts with “SDS”)
- SDS_CHASE_DEPEND
- SDS_CHASE_ENTITY

Standard Accounts D-9

Schlumberger Private - Customer Use
 - SDS_CHASE_IGNORE
- SDS_CHASE_INCLUDE
- SDS_CHASE_INPUT
- SDS_CHASE_MAP
- SDS_CHASE_PICK
- SDS_CHASE_RANK
- SDS_CHASE_RULE
- SDS_INDEX_ATTRIBUTE
- SDS_INDEX_ENTITY
- SDS_INDEX_FUNCTION
- SDS_INDEX_NAMESPACE
- SDS_INDEX_PATHEVAL
- SDS_INDEX_RULE
- SDS_INDEX_STATUS
- SDS_INDXSERVICE_ATTR
- SDS_INDXSERVICE_ENTITY
- SDS_INDXSERVICE_LINK
- SDS_INDXSERVICE_RULE
- SDS_MATCH_ATTRIBUTE
- SDS_MOVE
- SDS_MOVEEXT
- SDS_MATCH_RULE
- SDS_VIOLATION

• CRUD operations on the following reference tables in the data dictionary:

- R_CARTO_TRANSFORM
- R_COORDINATE_REF_SYSTEM
- R_CSMAP

• EXECUTE privileges on SDS_GUMM package in SIS_CATALOG

• EXECUTE privileges on the following SDS* subprograms:
- SDS_CHASE_GEN
- SDS_CHASE_MANAGER
- SDS_CHASE_GET_WORKFLOW
- SDS_INDEXSERVICE_GEN

• EXECUTE privilege on the following SDS_SYS type objects:

- SDS_DBOBJECTLIST
- T_VARCHAR2_TAB
D-10 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

• EXECUTE for the following packages in the data dictionary:
- SDS_Meta
- SDS_Merge
- SDS_Index
- SDS_Spatial
- SDS_Chase
- SDS_Storage
- SDS_DD_Admin
- SDS_Name
- CALC_Well_Point

• SELECT data dictionary Meta tables

• SELECT the following reference tables in the data dictionary:
- R_UNIT_SYSTEM
- R_VALUE_DOMAIN
- R_VERTICAL_REFERENCE

• SELECT privileges on the following project views:

- AZIMUTH_REFERENCE
- COORDINATE_SYSTEM
- PROJECT_RECOMMENDED_CRS
- PROJECT_RECOMMENDED_XFORM

• SELECT privilege on the following SDS tables:

- SDS_Storage_Configuration
- SDS_Storage_Mapping
- SDS_Storage_Part_Mapping
- SDS_Storage_Part_Scheme

• SELECT privilege on SDS_ID_SEQ sequence in the data dictionary

• SELECT privileges on the following SYS views:
- DBA_CONSTRAINTS
- DBA_CONS_COLUMNS
- DBA_DATA_FILES
- DBA_OBJECTS
- DBA_ROLE_PRIVS
- DBA_SEGMENTS
- DBA_SOURCE
- DBA_TABLESPACES
- DBA_TAB_COLUMNS

Standard Accounts D-11

Schlumberger Private - Customer Use
 - DBA_TRIGGERS
- DBA_USERS
- DBA_VIEWS
- V_$INSTANCE
- V_$LOCK
- V_$LOCKED_OBJECT
- V_$SESSION
- V_$SQLTEXT

System Privileges
• CREATE ANY VIEW
• CREATE ANY DATABASE LINK
• CREATE JOB
• DROP ANY VIEW
• GRANT ANY OBJECT PRIVILEGE

Roles
• SDS_DATAPUMP_DIR_ROLE – Select/Write on DATA_PUMP_DIR directory which
is used by Oracle Import and Export Utility
• SIS_CATALOG_ADMIN

SDS_ADMIN_DATA Object Privileges

• CRUD operations on Shared Scope entities in the data dictionary
• CRUD operations on project views that contain E&P data
• EXECUTE privileges on the following packages and subprograms in the data
dictionary:
- Disable_DD_Constraints
- Enable_DD_Constraints
- SDS_Index
- SDS_Spatial
- CALC_Well_Point

- PS_USER_UTILITIES
• SELECT Reference tables in the data dictionary
• SELECT Meta tables in the data dictionary

• EXECUTE privileges on the following packages and subprograms in projects:

- SDS_CHASE_GET_WORKFLOW
- PS_WELL_LOG_DATA_DELETE
- GET_TRUE_ZONE_THICKNESS
- DISABLE_CONSTRAINT

D-12 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 - ENABLE_CONSTRAINT
- SDS_CHASE_MANAGER
- SDS_MERGE_MERGE

SDS_ADMIN_ALL Roles
• SDS_ADMINISTRATOR
• SDS_ADMIN_DATA
• SIS_CATALOG_ADMIN

SDS_UPGRADE_ROLE System Privileges

• ALTER ANY INDEX
• ALTER ANY PROCEDURE
• ALTER ANY ROLE
• ALTER ANY SEQUENCE
• ALTER ANY TABLE
• ALTER ANY TRIGGER
• ALTER SESSION
• ALTER USER
• COMMENT ANY TABLE
• CREATE ANY INDEX
• CREATE ANY PROCEDURE
• CREATE ANY SEQUENCE
• CREATE ANY SYNONYM
• CREATE ANY TABLE
• CREATE ANY TRIGGER
• CREATE ANY TYPE
• CREATE ANY VIEW
• CREATE ROLE
• CREATE SESSION
• DELETE ANY TABLE
• DROP ANY INDEX
• DROP ANY PROCEDURE
• DROP ANY ROLE
• DROP ANY SEQUENCE
• DROP ANY SYNONYM
• DROP ANY TABLE
• DROP ANY TRIGGER
• DROP ANY TYPE

Standard Accounts D-13

Schlumberger Private - Customer Use
 • DROP ANY VIEW
• EXECUTE ANY PROCEDURE
• GRANT ANY OBJECT PRIVILEGE
• GRANT ANY ROLE
• INSERT ANY TABLE
• SELECT ANY DICTIONARY
• SELECT ANY SEQUENCE
• SELECT ANY TABLE
• UPDATE ANY TABLE

Account Privileges

SDS_SYS Java Privileges

• SYS:java.io.FilePermission – EXECUTE, READ, WRITE on all files in the
system.
• SYS:java.lang.RuntimePermission
- readFileDescriptor – Allows code to read the file associated with the
descriptor.
- writeFileDescriptor – Allows code to write to the file associated with the
descriptor.

System Privileges
• ALTER ANY TRIGGER
• ALTER SESSION
• ALTER USER
• CREATE ANY DIRECTORY
• CREATE ANY LIBRARY
• CREATE ANY SYNONYM
• CREATE ANY TRIGGER
• CREATE INDEXTYPE
• CREATE OPERATOR
• CREATE PROCEDURE
• CREATE PUBLIC SYNONYM
• CREATE ROLE
• CREATE SEQUENCE
• CREATE SESSION
• CREATE SYNONYM
• CREATE TABLE

D-14 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

• CREATE TRIGGER
• CREATE TYPE
• CREATE USER
• CREATE VIEW
• DROP ANY DIRECTORY
• DROP ANY LIBRARY
• DROP ANY ROLE
• DROP ANY SYNONYM
• DROP ANY TRIGGER
• DROP PUBLIC SYNONYM
• DROP USER
• GRANT ANY ROLE
• SELECT ANY TABLE
• UNLIMITED TABLESPACE

Object Privileges
• CRUD operations on some SDS* tables in the data dictionary.
• CRUD operations on some tables in the repository and SIS_CATALOG.
• CRUD operations on the following entities:
- AZIMUTH_REFERENCE
- COORDINATE_SYSTEM
- DBX_REPOSITORY
- PROJECT_DEFAULT_
- PROJECT_RECOMMENDED_CRS
- PROJECT_RECOMMENDED_XFORM
- SDS_INDEX_PATHEVAL
- SDS_MATCH_ATTRIBUTE
- SDS_MATCH_RULE
- SDS_STORAGE_CONFIGURATION
- SDS_STORAGE_MAPPING
- SDS_STORAGE_PART_MAPPING
- SDS_STORAGE_PART_SCHEME
- SDS_VIOLATION
- APPL_USER_MEMBERSHIP
- ENTITLEMENT_DETAIL
- MODEL_VERSION

• EXECUTE privileges on the following SYS packages:

Standard Accounts D-15

Schlumberger Private - Customer Use
 - DBMS_LOCK
- DBMS_PIPE
- DBMS_CRYPTO

• EXECUTE privileges on the packages and subprograms in SIS_CATALOG, data

dictionary, and project.
- CALC_WELL_POINT
- GRANT_PRIVS
- SDS_ADMIN_CLEAR_STAGING
- SDS_AUDIT
- SDS_DD_ADMIN
- SDS_MERGE
- SDS_SPATIAL
- SDS_STORAGE
- SDS_GUMM

• READ privileges on the following SYS tables:

- DBA_CONSTRAINTS
- DBA_SEQUENCES
- DBA_SYNONYMS
- DBA_TABLES
- DBA_OBJECTS
- DBA_ROLES
- DBA_ROLE_PRIVS
- DBA_SOURCE
- DBA_TABLESPACES
- DBA_TAB_COLUMNS
- DBA_TAB_PRIVS
- DBA_TRIGGERS
- DBA_USERS
- DBA_VIEWS
- DBA_PROFILES
- V_$INSTANCE
- V_$MYSTAT
- V_$SESSION

- V_$LOCK
• READ privileges on Meta tables in data dictionary.
• READ privileges on some reference tables in data dictionary.

D-16 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 - R_CARTO_TRANSFORM
- R_COORDINATE_REF_SYSTEM
- R_CSMAP
- R_UNIT_SYSTEM
- R_VERTICAL_REFERENCE

• SELECT privileges on some SDS* tables.

• UPDATE, SELECT on SDS_MERGE_LOCK table

Roles
• SIS_CATALOG_ADMIN
• SDS_ADMINISTRATOR

SIS_ADMIN System Privileges

• ALTER SESSION
• CREATE SESSION

Object Privileges
• SELECT privilege on V_$INSTANCE

Roles
• SDS_ADMIN_ALL
• SDS_UPGRADE_ROLE

SIS_CATALOG System Privileges

- ALTER SESSION
- CREATE INDEXTYPE
- CREATE OPERATOR
- CREATE PROCEDURE
- CREATE ROLE
- CREATE SEQUENCE
- CREATE SESSION
- CREATE SYNONYM
- CREATE TABLE
- CREATE TRIGGER
- CREATE TYPE
- CREATE VIEW
- UNLIMITED TABLESPACE

• EXECUTE privileges on SDS_CONTEXT package

Standard Accounts D-17

Schlumberger Private - Customer Use
 Object Privileges
• SELECT privileges on the following SYS views:
- DBA_OBJECTS
- DBA_SOURCE
- DBA_TAB_COLUMNS
- DBA_TRIGGERS
- DBA_USERS
- DBA_VIEWS

SDS_INFO System Privileges

• ALTER SESSION
• CREATE SESSION

User System Privileges

• ALTER SESSION
• CREATE SEQUENCE
• CREATE SESSION
• CREATE SYNONYM
• CREATE TABLE
• CREATE VIEW

Roles
• SIS_CATALOG_READ
• <PROJECT>_USER – Assigned to users given access to a specific named project.

Administrator System Privileges

• CREATE SEQUENCE
• ALTER SESSION
• CREATE TABLE
• CREATE VIEW
• CREATE SESSION
• CREATE SYNONYM

Roles
• SDS_ADMINISTRATOR
• SIS_CATALOG_READ

D-18 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

Administrator who can This account has the same privileges and roles as an Administrator account, but it
create other also allows the creation of other Administrator accounts.
Administrators

Data Dictionary System Privileges

• ALTER SESSION
• CREATE INDEXTYPE
• CREATE JOB
• CREATE OPERATOR
• CREATE PROCEDURE
• CREATE ROLE
• CREATE SEQUENCE
• CREATE SESSION
• CREATE SYNONYM
• CREATE TABLE
• CREATE TRIGGER
• CREATE TYPE
• CREATE VIEW

Object Privileges
• CRUD operations on data dictionary tables
• CRUD operations on the following <PROJECT>/<STAGING> entities:
- AZIMUTH_REFERENCE
- COORDINATE_SYSTEM
- PROJECT_DEFAULT_
- PROJECT_RECOMMENDED_CRS
- PROJECT_RECOMMENDED_XFORM
- SDE_LAYER_PARAMETER

• EXECUTE privilege on the following packages:

- SDS_CONTEXT
- SDS_GUMM
- SDS_EXTEND
- REPORTCHARTMUTATINGPKG
- DP_METADATA_IMPORT
- SDS_AUDIT

• SELECT privilege on the following <PROJECT>/<STAGING> entity:

- PROJECT_DEFAULT

• REFERENCES privilege on SDS_ACCOUNT

Standard Accounts D-19

Schlumberger Private - Customer Use
 • SELECT privilege on DBA_USERS

Roles
• SIS_CATALOG_READ

Project System Privileges

• ALTER SESSION
• CREATE INDEXTYPE
• CREATE OPERATOR
• CREATE PROCEDURE
• CREATE ROLE
• CREATE SEQUENCE
• CREATE SESSION
• CREATE SYNONYM
• CREATE TABLE
• CREATE TRIGGER
• CREATE TYPE
• CREATE VIEW
• UNLIMITED TABLESPACE

Object Privileges
• CRUD operations on E&P data views in the Interface
• CRUD operations on shared scope entities in the data dictionary
• CRUD operations on Indexing Service tables in the data dictionary
• EXECUTE privilege on the following:
- CALC_WELL_POINT
- DISABLE_DD_CONSTRAINTS
- ENABLE_DD_CONSTRAINTS
- PROCESS_CONSTRAINTS
- PROCESS_MERGE_CONSTRAINTS
- PS_USER_UTILITIES
- SDS_CHASE
- SDS_CONFIG
- SDS_CONTEXT
- SDS_DD_ADMIN
- SDS_GEN
- SDS_GRANT_DD_OBJ
- SDS_INDEX
- SDS_LOG
D-20 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 - SDS_MERGE
- SDS_MERGE_CLEAR_STAGING
- SDS_MERGE_FREE_MERGELOCK
- SDS_MERGE_FREE_STAGING
- SDS_MERGE_GET_MERGELOCK
- SDS_MERGE_GET_STAGING
- SDS_META
- SDS_META_GUMM
- SDS_NAME
- SDS_PROJ
- SDS_SPATIAL
- SDS_STORAGE
- SDS_SYN_INT
- SDS_UTL
- SEABED_DATA_OBJECT
- SEABED_LICENSE
- SEABED_META
- SEABED_OVERRIDE
• SELECT, REFERENCES privilege on certain SDS* tables and Reference tables
• SELECT privilege on metadata in the data dictionary
• SELECT privilege on DBA_USERS
• SELECT privilege on the following sequences:
- SDS_ID_SEQ
- SDS_EPSG_SEQ
Roles
• SIS_CATALOG_READ

Staging System Privileges

• ALTER SESSION
• CREATE INDEXTYPE
• CREATE OPERATOR
• CREATE PROCEDURE
• CREATE ROLE
• CREATE SEQUENCE
• CREATE SESSION
• CREATE SYNONYM
• CREATE TABLE

Standard Accounts D-21

Schlumberger Private - Customer Use
 • CREATE TRIGGER
• CREATE TYPE
• CREATE VIEW
• UNLIMITED TABLESPACE

Object Privileges
• CRUD operations privilege on shared scope entities in the data dictionary
• CRUD operations on Indexing Service tables in the data dictionary
• CRUD operations on E&P data views in the Interface
• EXECUTE privilege on the following subprograms:
- CALC_WELL_POINT
- DISABLE_DD_CONSTRAINTS
- ENABLE_DD_CONSTRAINTS
- PROCESS_CONSTRAINTS
- PROCESS_MERGE_CONSTRAINTS
- PS_USER_UTILITIES
- SDS_CHASE
- SDS_CONFIG
- SDS_CONTEXT
- SDS_DD_ADMIN
- SDS_GEN
- SDS_GRANT_DD_OBJ
- SDS_INDEX
- SDS_MERGE
- SDS_MERGE_CLEAR_STAGING
- SDS_MERGE_FREE_MERGELOCK
- SDS_MERGE_FREE_STAGING
- SDS_MERGE_GET_MERGELOCK
- SDS_MERGE_GET_STAGING
- SDS_META
- SDS_META_GUMM
- SDS_NAME
- SDS_PROJ
- SDS_SPATIAL
- SDS_STORAGE
- SDS_SYN_INT
- SDS_UTL

D-22 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 - SEABED_DATA_OBJECT
- SEABED_LICENSE
- SEABED_META
- SEABED_OVERRIDE

• SELECT privilege on the following SYS table:

- DBA_USERS

• SELECT, REFERENCES privilege on certain SDS* tables and Reference tables

• SELECT privilege on metadata in the data dictionary
• SELECT privilege on the following sequences:
- SDS_ID_SEQ
- SDS_EPSG_SEQ

Roles
• SIS_CATALOG_READ

Interface System Privileges

• ALTER SESSION
• CREATE INDEXTYPE
• CREATE OPERATOR
• CREATE PROCEDURE
• CREATE ROLE
• CREATE SEQUENCE
• CREATE SESSION
• CREATE SYNONYM
• CREATE TABLE
• CREATE TRIGGER
• CREATE TYPE
• CREATE VIEW

Object Privileges
• CRUD operations on E&P data tables in the project
• CRUD operations on Entitlement tables
• CRUD operations on Shared scope entities
• CRUD operations on the following entities:
- SDS_INDEX_RULE
- SDS_MERGE_STATE
- SDS_INDEX_NAMESPACE
- SDS_MOVE_

Standard Accounts D-23

Schlumberger Private - Customer Use
 - SDS_INDXSERVICE_ENTITY
- SDS_MOVEEXT_
- SDS_MOVE
- SDS_INDEX_ENTITY
- SDS_COUNTER_
- SDS_MOVEEXT
- SDS_INDXSERVICE_LINK
- SDS_INDEX_PATHEVAL
- SDS_INDEX_ATTRIBUTE
- SDS_INDXSERVICE_ATTR
- SDS_INDEX_STATUS
- SDS_INDXSERVICE_RULE
- SDS_INDEX_FUNCTION

• EXECUTE privilege on the following subprograms:

- SDS_CONTEXT
- SDS_MERGE_GET_MERGELOCK
- SDS_CONFIG
- SEABED_META
- SDS_META
- DISABLE_DD_CONSTRAINTS
- ENABLE_DD_CONSTRAINTS
- SDS_GRANT_DD_OBJ
- SEABED_OVERRIDE
- SEABED_LICENSE
- SEABED_DATA_OBJECT
- PROCESS_MERGE_CONSTRAINTS
- PS_USER_UTILITIES
- PS_WELL_LOG_DATA_DELETE
- GET_TRUE_ZONE_THICKNESS
- SDS_MERGE_FREE_STAGING
- SDS_MERGE
- SDS_MERGE_CLEAR_STAGING
- SDS_MERGE_GET_STAGING
- SDS_MERGE_FREE_MERGELOCK
- PROCESS_CONSTRAINTS
- SDS_INDEX

D-24 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 - SDS_SPATIAL
- SDS_CHASE
- SDS_UTL
- SDS_STORAGE
- SDS_SYN_INT
- SDS_PROJ
- SDS_GEN
- SDS_DD_ADMIN
- SDS_NAME
- SDS_META_GUMM
- CALC_WELL_POINT
- DISABLE_CONSTRAINT
- ENABLE_CONSTRAINT
- SDS_MERGE_MERGE
- SDS_CHASE_GEN
- SDS_CHASE_MANAGER
- SDS_INDEXSERVICE_GEN

• SELECT privilege on DBA_USERS

• SELECT, REFERENCES privileges on other SDS* tables and Reference tables
• SELECT, REFERENCES privileges on Meta entities
• SELECT privilege on the following sequences:
- SDS_ID_SEQ
- SDS_EPSG_SEQ

Roles
• <PROJECT>_TAB
• SIS_CATALOG_READ

SDE SDE account is created by ArcSDE upon installation. It is used for ArcSDE
administrative purposes.
System Privileges
• CREATE SESSION
• ADMINISTER DATABASE TRIGGER
• CREATE TYPE
• CREATE PROCEDURE
• DROP PUBLIC SYNONYM
• CREATE SEQUENCE
• CREATE PUBLIC SYNONYM

Standard Accounts D-25

Schlumberger Private - Customer Use
 • CREATE TABLE
• CREATE OPERATOR
• CREATE INDEXTYPE
• CREATE VIEW
• CREATE LIBRARY
• CREATE TRIGGER
• UNLIMITED TABLESPACE

Object Privileges
• SELECT privilege on certain DOVs, views, and tables in the repository
- AREA
- BOREHOLE_SUMMARY_DOV
- DEVIATION_SURVEY_PROC_DOV
- LEASE_DOV
- LINE
- MARKER_DOV
- MULTIPOINT
- POSITION
- SEISMIC_LINE_DOV
- SEISMIC_SURVEY_3D_DOV
- WELL_SUMMARY_DOV

Roles
• CONNECT
• RESOURCE

D-26 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use

 E Useful Procedures

Procedure Comments

SDS_ADMIN.Reset_Password (pUser, • Resets the password for the user. E.g. execute
pNewPassword,pOldPassword) SDS_ADMIN.Reset_Password (‘U1’,’SeabedU1’,’seabed’)
• Changes the password for the user U1, to ‘SeabedU1’.

SDS_ADMIN.Free_Staging (p_Staging) • Frees the staging. E.g. execute SDS_ADMIN.Free_Staging

(‘Stage1’)
• Frees ‘Stage1’.

SDS_PROJ.db_cleanup • Deletes all data in the project executed in. User must login to
the project.
• Deletes all project data.

Useful Procedures E-1

Schlumberger Private - Customer Use

E-2 Seabed Oracle Database Manager Guide April 2015

Schlumberger Private - Customer Use