Professional Documents
Culture Documents
Database Administration
User Manual
December 2012 v8.8
iii
Rock Solid Attributes is a trademark of RDSP I, L.P. Solid Attributes contains confidential,
proprietary, and trade secret information of RDSP I, L.P. This unpublished work by RDSP I, L.P. is
protected by the laws of the United States and other countries. Additionally, if publication occurs, the
following notice shall apply: Copyright RDSP I, L.P., All Rights reserved.
Baker Hughes JewelSuite is a trademark of Baker Hughes. JewelSuite contains confidential,
proprietary and trade secret information of Baker Hughes.
Microsoft is a registered trademark of Microsoft Corporation. Windows 2000, Windows XP, and
Windows XP x64, Windows Vista, Windows 7 operating systems, MS-DOS and SQL Server are
trademarks of Microsoft Corporation. Oracle Databases are registered trademarks of Oracle
Corporation. OpenWorks, SeisWorks, Interpret 2000 and Interpret 2003 are registered trademarks of
Landmark Graphics Corporation.
IHS Inc. incorporates BMC AppSight Black Box Technology in its software. BMC Software,
BMC Software logos and all other BMC Software product and service names are registered
trademarks or trademarks of BMC Software Inc. 2009 BMC Software, Inc. All rights reserved.
All other trademarks are the property of their respective holders.
2011 - 2012 IHS Inc.
All Rights Reserved Worldwide
Kingdom and this manual are both copyrighted and intended for use by a single user or a single
computer whose model is authorized by IHS Inc. You are entitled to electronically transcribe Kingdom
DVD to the hard disk of an authorized computer so long as Kingdom and related software packages
are operated on only one computer at a time. You are further entitled to electronically transcribe the
DVD to other DVD(s) for archival storage only. Physical duplication of the Kingdom software and
SENTINEL is expressly forbidden. No portion of Kingdom software may be incorporated into any
other program. No other usage or transcription in any form is allowed without the express written
permission of IHS Inc.
No portion of this manual may be reproduced, transmitted, transcribed or stored on any information
retrieval system, or translated into any foreign language or any computer language in any form and by
any means whatsoever without the express written permission of IHS Inc. This document contains
confidential information and trade secrets proprietary to IHS Inc.
Misuse Disclaimer
IHS Inc. makes no representation or warranties of any kind with respect to this manual or the Kingdom
software. Specifically, IHS Inc. disclaims any implied or any other claimed warranties of
merchantability or suitability for any particular purpose. IHS Inc. reserves the right to modify the
Kingdom software and any of the associated user documentation at any time.
Acknowledgments
IHS Inc. wishes to gratefully acknowledge the contributions of the many client software testers in
preparing the Kingdom software. The enthusiastic Beta testers, smoke testers, and IHS Inc.staff greatly
appreciate their invaluable feedback and contributions.
iv
Table of Contents
Database Considerations
Choosing a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Microsoft Access Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Advantages of Oracle and SQL Server as a Project Database . . . . . . . . . . . . 5
An Error Occurred Connecting to the Database . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Kingdom 8.8 v
Table of Contents
vi Kingdom 8.8
Import the Database Dump File into the Target Database . . . . . . . . . . . . . . . . 139
Kingdom 8.8 1
Kingdom 8.8 2
Database Considerations
Choosing a Database
Kingdom Software 64-bit applications allow you to benefit from the full power of 64-bit
computing and enjoy a significant increase in application performance:
increased memory capacity (many 64-bit workstations can have up to 128 GB of RAM)
increased addressable memory (8 Terabytes)
improved graphics capabilities
Kingdom 64-bit as well as most Kingdom Advanced modules require the scalability and
performance attributes provided by SQL and Oracle databases and require one of the
following:
SQL Serverrequires installation and configuration of a central server and a local client.
Two options are available:
- SQL Server (Single)creates a project specific database. With this configuration,
each project will have its own database in the selected SQL Server instance.
- SQL Server (Multiple)adds the project to an existing database that may contain
multiple Kingdom projects. The tables for each project have a unique number as a
prepend to the table name. See Microsoft SQL Server as the Project Database.
Kingdoms SQL Server Express
- Auto SSEis configured to be automatically portable. As long as all data is contained
in the project folder, when all authors are out of the project, the project can be copied
or moved without any tools or special operations.
- Manual SSEhas the original configuration introduced with Kingdom 8.2 and is
compatible with Kingdom versions 8.2 and later. Management of your Manual SSE
projects is done through the Manual SSE Management Tool available from the
Kingdom Start Page.
Oraclerequires installation and configuration of a central server and a local client. See
Oracle as the Project Database
Kingdom 8.8 3
Kingdom 64-bit is NOT compatible with an Access database. When you open an Access
project with Kingdom 64-bit, you will be required to migrate the Access database to one of the
databases listed above.
Related Topics
Note: Kingdom projects with SQL Server Express databases can be used with both 32-bit
and 64-bit versions of Kingdom.
Note: 32-bit software will generally run on a 64-bit computer, but 64-bit software will not
run on a 32-bit computer.
4 Kingdom 8.8
Even with Kingdom Core 32-bit users, Access has some inherent limitations which may make
it less desirable for use with large projects or in a large office:
Multiple users in a single project can affect Kingdom performance. More than five users
can make performance noticeably slower.
In a multi-user environment, Microsoft Access database updates may fail under a heavy
input/output load which could result in a loss of data.
Access has a 2 GB single database size limit.
Multiple Access projects may be more difficult to administer locally by a central database
administrator. If these databases are distributed, then backups may be more of a chore than
if a central database were used.
Many companies prefer to use the extra security measures they associate with an external
relational database management system (RDBMS) such as Oracle or SQL Server.
In theory, there is no database size limitation. Databases are actively sizeable to allow
project growth.
They provide an additional level of protection by requiring user authentication prior to
opening the project. A Kingdom project is assigned to an Oracle or SQL Server account
for which users must know the password. These accounts are not related to Kingdom
authorship or interpretation ownership, but to database table access only.
The Oracle instance can reside on any server, be it UNIX, Linux or Windows. Kingdom
requires the Oracle client for Windows be installed on the local PC, but the Oracle
database server can run anywhere.
Note: Kingdom 32-bit requires the Oracle 32-bit client and Kingdom 64-bit requires the
Oracle 64-bit client. Both clients can be installed on the workstation which will allow
both versions of Kingdom to connect to Kingdom Oracle projects.
Oracle and SQL Server use snapshot creation (making database edits pending), so the
administrator can do a backup without shutting down the database and asking users to exit
their instance of the project.
Kingdom 8.8 5
An Error Occurred Connecting to the Database
6 Kingdom 8.8
Microsoft SQL Server Express as
the Project Database
Decide which type of SQL Server Express to use for my Kingdom projects.
- See How is Auto SSE different from Manual SSE?
Ive just installed SQL Server Express and need help configuring the service.
- First select Local or Network.
- If you are in a network environment, you will need help from your domain
administrator. See Network ProjectNetwork Database Instance for instructions.
Update my Kingdom projects with Access databases to SQL Server Express.
- See Migrate Access Database to SQL Server Express
Kingdom 8.8 7
I cant connect to the database or start the service.
- Connecting to your SQL Server Express Database troubleshooting tips
- Unable to start the service
Im using the Manual option and need to make my project portable.
- Manual SQL Server Express (SSE) Management provides details on how to copy,
move, backup, restore, and delete your Kingdom projects.
8 Kingdom 8.8
How is Auto SSE different from Manual
SSE?
Kingdom versions 8.5 and later include an auto portability option for the SQL Server Express
database. Auto SSE is designed to minimize database management and differs from Manual
SSE in the following ways:
Places the database in the Kingdom project directory Places the database in the KingdomSuite
in a folder named ProjectDatabase. directory under Program Files (x86) on
the machine where the instance is
installed.
Automatically attaches the database when the first Does not automatically detach / attach
user opens the project
Automatically detaches the database when the last You must use the Manual SSE
user exits the project Management tool to detach (make
portable) or attach
After all users exit the project, you can copy / move After all users exit the project, you must
the project with Windows Explorer use the Manual SSE Management tool to
copy/move the project
Supports the following location combinations: Supports mixed mode location
combinations for your project folder and
- Local ProjectLocal Database Instance SSE instance. Your project on the network
- Network ProjectNetwork Database Instance can connect to a local instance and vice
versa.
Projects with the auto portability configuration have the same management simplicity as
Access projects. When the last author exits the project, the project folder can be moved or
copied with the database intact.
Note: Only data stored inside the project folder will be included in any move or copy. Data
stored outside of the project folder such as seismic files, author files, or tiff images of
your raster logs, will need to be copied separately.
Kingdom 8.8 9
How is Auto SSE different from Manual SSE?
Related Topics
Auto SSE and Backward Compatibilityprovides instructions if you want to open your Auto
SSE project in an earlier version of Kingdom.
Changing an Auto SSE Project back to Manual SSEchanging from auto to manual is done
through the Manual SQL Server Express Management tool.
Note: Projects changed back to the manual portability configuration are also compatible with
Kingdom version 8.5 SP2 and later.
1. Launch the tool from the Kingdom Start Page. Select Manage Manual SQL Server
Express Projects.
2. Select one of the Make Project Portable options.
3. Browse to the project *.tks file.
4. Click Start to Make a portable copy of the project or to make that project portable.
5. Click Yes in the message to continue with the Manual SSE configuration.
6. When the process is finished, the Summary Report will display project details.
The project is packaged in its current location into a folder called <project
name>_portable_<date yyyymmdd>_<time>.
The project now has the manual portability configuration and can be opened in Kingdom
versions 8.2 and later.
To open this project, use the Attach Portable Project option in the Manual SQL Server Express
Management tool.
10 Kingdom 8.8
2. Apply any of the options available in the management tool to change the project to
Manual SSE.
See Manage your Manual SSE Projects for detailed workflows.
Note: Converting or copying an Auto SSE project to a different instance using Kingdom
Data Management changes the project to Manual SSE.
Kingdom 8.8 11
How is Auto SSE different from Manual SSE?
Note: After migration, the Kingdom project folder remains in the same location with the
same name. The Access database is renamed and the <project name>.xml file is
created. This .xml file is the pointer to the project database in the Kingdom instance of
SQL Server Express.
Note: For best results when migrating your project data, make sure your computer is set to
English (United States) in the Control Panel > Region and Language options. After
the database has migrated, you can change the language back to your choice. However,
Kingdom requires that the decimal symbol be a period, and not a comma.
To migrate your Access database to SQL Server Express, select the Auto or Manual SQL
Server Express and Yes.
Migrate Access Project to Auto SSE
Migrate Access Project to Manual SSE
12 Kingdom 8.8
If your project and SQL Server Express instance are on different computers on the
network, you will need to select the instance on the network that has been configured as
the network instance. See Network ProjectNetwork Database Instance for details.
3. When the migration is complete, the Select Author dialog box opens, and your project is
ready to go in SQL Server Express.
3. When the migration is complete, the Select Author dialog box opens, and your project is
ready to go in SQL Server Express.
Kingdom 8.8 13
Connecting to your SQL Server Express Database
Related Topics:
14 Kingdom 8.8
After you enter the instance, the User Name and Password fields will disappear.
Click OK to continue.
If you receive an error message see Error Occurred Connecting to the Database
Kingdom 8.8 15
Connecting to your SQL Server Express Database
3. To start a service, right click beside the service in the Status column and select Start.
4. Now open the Access Kingdom project with Kingdom 64-bit and try the project migration
again.
Problem 2: One of the TCP/IP protocols is not enabled.
If the SQL Server Express instance you are migrating to is not local (on your computer),
the TCP/IP protocols on the remote database instance and on your local (client) machine
must be enabled. If the SQL Server Express instance is on your machine, this is not an
issue.
Solution 2A: On the computer where SQL Server Express is installed, open the SQL Server
Configuration Manager and Enable the TCP/IP protocol:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
16 Kingdom 8.8
Figure 1 Enable TCP/IP Protocol
2. Under SQL Server 2005 Network Configuration, select Protocols for SMTKINGDOM.
3. In the right panel, check if the TCP/IP protocol is Enabled. If it is Disabled as in the figure
above, right click Disabled and select Enable.
4. You will need to restart the database service.
a. In the same Configuration Manager, select SQL Server 2005 Services in the left
panel.
b. In the right panel right click SQL Server (SMTKINGDOM) and select Restart.
Solution 2B: Now return to the Kingdom workstation and Enable the TCP/IP Client Protocol
using the same procedure:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
2. Under SQL Native Client Configuration, select Client Protocols.
3. In the right panel, check if the TCP/IP protocol is Enabled. If it is Disabled, right click
Disabled and select Enable.
Warning: After you have completed parts A and B of the solution, open the Access Kingdom
project with Kingdom 64-bit and try the project migration again.
Kingdom 8.8 17
Connecting to your SQL Server Express Database
Kingdom projects are You are a single user or have Install SQL Server Express on the
on your workstation or a small work group. same computer as the Kingdom
on a colleagues project and use a Local Project
workstation. Local Database Instance
configuration.
Kingdom projects are The Kingdom project and Install SQL Server Express on a
on a shared resource on SQL Server Express network computer - not on your
the network instance are on different workstation.
machines.
This configuration requires a
Network ProjectNetwork
Database Instance solution.
Note: When using Auto SSE, projects on the network cannot connect to a local SSE
instance. Similarly, local projects cannot connect to an SSE instance on the network.
18 Kingdom 8.8
Managing your Manual SQL Server
Express Projects
With Manual SQL Server Express projects, like SQL Server and Oracle, the project database
is tied to the server on that computer. The database no longer resides in the project folder as it
does with Auto SSE projects or MS Access projects. Therefore, to copy, move, backup or
delete the project, you need to consider both the project folder and the database.
Note: If your projects have the auto portability configuration, you do not need to use this tool
unless you want to open your project with Kingdom 8.5 or earlier - or if you want to
convert your project from Auto SSE back to Manual SSE.
Warning: The Manual SQL Server Express Management tool manages only the SQL Server
Express database and the files in the Kingdom project folder. By default, Kingdom
files are saved in the project folder, but if files such as seismic data, author folders,
or raster logs have been saved in locations outside of the project folder, these files
will not be included in the action.
Before using Manual SQL Server Express Management to manage your project,
move all external files into the Kingdom project folder.
Kingdom 8.8 19
Managing your Manual SQL Server Express Projects
20 Kingdom 8.8
SQL Server Express Service
Configuration
Local
Projects Kingdom projects are on your workstation or on a colleagues
workstation.
Users You are a single user or have a small work group.
SQL Server Service Install SQL Server Express on the same computer as the
Kingdom projects. Accept Local as the configuration. Click OK
in the SQL Server Express Service Configuration dialog box to
exit.
Other users in a work group or network that have permissions to access this computer will
also be able to work in the Kingdom projects.
Kingdom 8.8 21
Network
Projects Kingdom projects are on a shared resource on the network.
Users The Kingdom projects and SQL Server Express instance may be
on different machines. Multiple users may connect to the same
SQL Server Express instance.
SQL Server Express Install SQL Server Express on a network computer - not on your
Service workstation.
You will need to get service credentials from your domain administrator before continuing.
See Unable to start the service for troubleshooting tips if you get an error message after trying
to start the service with the entered log on credentials.
You are in a network environment when your project and your SQL Server Express
(SMTKINGDOM) instance are both on your network - not on your workstation. This
configuration supports multiple projects on multiple computers connecting to a central SQL
Server Express instance.
See What is your Working Environment? for local and network criteria.
Your network administrator will need to do the following:
1. Create user (service account)
2. Add the Log on as a service right to the user account
3. Grant the service account Full Control privileges to Kingdom project directories
4. Add the service account user to the computer where the SQL Server Express instance is
installed and add to Administrator Group
5. Set the service account as the Log On account for the SQL Server (SMTKINGDOM)
service
Prerequisites:
22 Kingdom 8.8
Microsoft Administrative Tool Pack is installed on a machine in the domain or you have
access to the domain controller.
You have a domain administrator account or service account with permissions to create
users and modify the default domain policy to create the service account.
Create the user (service account)
1. On a Windows Domain Controller, open Administrative Tools and click Computer
Management.
2. Expand Your Domain.
3. Right click Users and select New User
4. Enter the user account information and click Next.
5. Enter a password and confirm the password.
6. Select Password never expires.
7. Click Create and then Close.
Add the service account to the group(s) that have Full Control access to the Kingdom project
directoriesorshare the Kingdom project directories to the user account and give Full
Control access. For the second option, see How do I share my project directories?
Add the service account to the group(s) that have Full Control access
1. On the Windows Domain Controller, select Start > Programs > Administrative Tools >
Active Directory Users and Computers.
2. Click Groups to display existing groups.
3. Right click the selected group and select Add to Group.
Kingdom 8.8 23
4. Click Add.
5. Make sure Service Accounts is displayed under Select this object type and that your
Domain is displayed under From this location.
6. Enter the name of the service account that you created and click Check Names.
7. When the account is returned, select OK and OK again.
Add the service account user to the computer where the SQL Server
Express instance is installed and add to Administrator Group
This step can be done by the domain administrator remotely or by any user that is an
administrator on the computer where SQL Server Express is installed.
Tip: You can use the same service account for other instances of SQL Server Express.
Set the service account as the Log On account for the SQL Server
(SMTKINGDOM) service
Note: This step can be done by the SQL Server Express Service Configuration tool installed
with the instance. The user installing the instance will only need the user name and
password of the service account.
You must be a local administrator on the computer to set the Log On account.
24 Kingdom 8.8
1. Log in to the network computer where SQL Server Express is installed.
2. Select Control Panel > Administrative Tools > Services
3. Right click the SQL Server (SMTKINGDOM) service and select Properties.
4. Select the Log On tab.
5. Select This account and click Browse.
6. In Select User, click Locations.
7. Expand Entire Directory and select the company domain (network) name. Click OK.
8. In Select User or Service Account enter the created service Active Directory user name
or display name and click Check Names. The service account should appear in the object
name box.
9. Click OK to return to the Log On tab.
10. Enter and confirm the service account domain password and click OK.
11. Click Yes in the 2 messages and OK again in the Log On tab.
12. You will need to restart the service. In the Services list, right click the SQL Server
(SMTKINGDOM) service and select Restart.
The SQL Server (SMTKINGDOM) service will now be able to access the database files
located in the Kingdom project folders.
The Kingdom project directories must be shared to the SQL Server (SMTKINGDOM) service
Log On account (service account).The Log On account must have Full Control permissions to
the project directories.
You must share your project folder on your computer to the Log On account for the SQL
Server (SMTKINGDOM) service and give this account Full Control permissions.
1. Contact your network administrator and request the name of the service account that was
created for the SQL Server (SMTKINGDOM) service.
2. Share your project folder to this service account and give it Full Control permissions.
a. Right click the project folder on your computer and select Properties.
b. Select the Sharing tab and click Share.
c. Enter the service account name and click Add. If a matching domain account is found,
the domain\service account name will appear in the list.
d. Under Permission level, click the down arrow and select Full Control. Click Share.
Your folder is now shared to the service account. Click Done to exit.
Kingdom 8.8 25
Windows Domain Controller
On Windows Server Systems, a domain controller (DC) is a server that responds to security
authentication requests (logging in, checking permissions, etc) within the Windows Server
domain. Windows 2000 and later versions introduced Active Directory.
26 Kingdom 8.8
Unable to start the service
There are a number of reasons why the service is unable to start. Microsoft returns 24 possible
reasons. However, the following are the most common:
Table 1
The user password is not Re-enter the password in the Server Configuration dialog box
valid and retry.
The user has not been If prompted that the user will be added to the local logon as a
granted local logon as a service group, click OK.
service rights
The domain user is not a Contact your domain administrator. See Network Project
member of a Group that has Network Database Instance for detailed steps.
logon as a service rights.
The user is not in the Add the service account user to the computer where the SQL
Administrator group on the Server Express instance is installed and add to Administrator
local machine Group
The user logged in to the You must be a member of the Administrator group on the
computer is not a local computer. Contact your domain administrator for assistance.
administrator
Kingdom 8.8 27
Unable to start the service
28 Kingdom 8.8
Manual SQL Server Express (SSE)
Management
Before using SQL Server Express Management to manage your project, move
all external files into the Kingdom project folder.
Note: If your projects have the auto portability configuration, you do not need to use this tool
unless you want to open your project with Kingdom 8.6 or earlier - or if you want to
convert your project from Auto SSE back to Manual SSE.
Note: Use the Manual SSE Management tool to accomplish the following.
Make a Project PortableSend or take your Manual SSE project to a computer not on
your network (home or to a colleague). You have two choices:
- Make the Original Project Portablemakes the project itself portable until restored.
Select the first option, Detach project database. The project database is moved into
the project directory in its original location. The project is inactive in this portable
form. You can then transfer the portable project to an external storage device and
Attach Portable Project in the new location.
- Make a Portable Copy of the Projectkeeps the original project active and makes a
portable copy of the entire project in a new folder. Select the second option, Copy
entire project. The portable project is inactive in this portable form.
Attach Portable ProjectMake your portable project active in the new location to
begin work. You have two choices:
Kingdom 8.8 29
- Attach the Project Database Onlyattaches the project database to the specified
instance and makes the Kingdom project active in its current location.
- Attach the Database and Copy the Project Filescopies the portable project file to the
specified location and then attaches the project database to the specified instance.
Make an Active CopyCopy the project to a location on your computer or network.
The new project will have its own database identical to the database in the original project.
Create a BackupMake a project copy to store. A copy of the project is packaged into a
portable folder to a location you specify. The original project remains active. You can
Restore a Backup as required.
Restore a BackupMake your project backup active and begin work.
Move Project Files OnlyRelocate the Kingdom project files without moving the
database. The moved project will remain active.
Delete an Entire Project Delete the database and project files of your Manual SQL
Server Express projects.
Note: You can also launch the Manual SSE Management tool from DBAdmin.
Select Start > Programs > The Kingdom Software 8.7.1 > DbAdmin
Select Database > SQL Server Express Management
30 Kingdom 8.8
3. Select the option. See Manage your Manual SSE Projects for a definition of each option or
click the link below for detailed instructions:
Make a Project Portable
Attach Portable Project
Make an Active Copy
Create a Backup
Restore a Backup
Move Project Files Only
Delete an Entire Project
4. Complete the Option Source / Destination / Instance Information
The option you select will determine the required source project, destination location, and
SQL Server Express instance information.
5. Determine if you want to use Validation mode for added data security.
Kingdom 8.8 31
Validation mode
Validation is a file by file comparison of the destination project with the source project.
This comparison is done after the selected action of the project database and project files
has been successfully completed. All validation issues detected during the selected
process will be listed in the Summary Report. Validation mode is not available for
database only operations (detach and attach database only) or for delete entire project.
Note: Validation mode will substantially increase the time required to complete the process
32 Kingdom 8.8
3. Select Make Project Portable and Detach project database.
4. Select the source project file (.TKS). Click Browse and navigate to the <project
name>.tks file of the project you want to send or move.
Note: You do not have a destination option as the project will packaged in its current
location. The contents of the database will be included in the project folder.
5. Click Start to begin the process. A status bar will display the progress.
6. When the process is finished, the Summary Report will display project details.
The project is packaged in its current location into a folder called <project
name>_portable_<date yyyymmdd>_<time>.
For example, for a project named BEG made portable on September 8, 2008 at 1:13 pm,
Kingdom 8.8 33
Table 1 Portable project files
7. Now using Windows, copy the portable project folder to an external storage device to
transport to the specified location.
Note: The destination computer must also have the SMTKINGDOM instance of SQL Server
Express installed before you can make the portable project active with Attach Portable
Project. SQL Server Express is available on the Kingdom Software DVD.
8. On the destination machine, use Windows to copy the portable project folder to the project
folder location.
9. Launch Kingdom and click Manage SQL Server Express Projects on the Start Page.
10. Now select Attach Portable Project to return the portable project to its original, active
state.
34 Kingdom 8.8
3. Select Make Project Portable and Copy entire project.
4. Select the source project file (.TKS). Click Browse and navigate to the <project
name>.tks file of the project for which you want to make a portable copy.
5. Select a portable project destination. Click Browse and navigate to the location where
you want to save the portable copy of the selected project.
6. Select a Validation mode.
7. Click Start to begin the process. A status bar will display the progress.
8. When the process is finished, the Summary Report will display project details.
The portable copy is saved to the specified location in a folder called <project
name>_portable_<date yyyymmdd>_<time>.
Kingdom 8.8 35
For example, for a project named BEG made portable on September 8, 2008 at 1:13 pm,
9. Now using Windows, copy the portable project folder to a storage device to transport to
the external location.
Note: The destination computer must also have the SMTKINGDOM instance of SQL Server
Express installed before you can make the portable project active with Attach Portable
Project. SQL Server Express is available on the Kingdom Software DVD.
10. On the destination machine, use Windows to copy the portable project folder to the project
folder location.
11. Launch the SQL Server Express Management Tool through DBAdmin.
12. Now select Attach Portable Project to return the portable project to its original, active
state.
36 Kingdom 8.8
Attach Portable Project
This option makes a portable project active. Use Attach a Portable Project if you want to
make the project active on a computer not connected to your network.
Note: The destination computer must also have the SMTKINGDOM instance of SQL Server
Express installed before you can make the portable project active. SQL Server Express
is available on the Kingdom Software DVD.
You have two choices when making your portable project active:
- Attach the Project Database Onlyattaches the project database to the specified
instance and makes the Kingdom project active in its current location. The portable
project folder is renamed to its original name, and the database pointer file (<project
name>.xml) is updated with the new SSE SMTKINGDOM instance information.
- Attach the Database and Copy the Project Filescopies the portable project file to the
specified location and then attaches the project database to the specified instance. The
copied portable project folder is renamed to its original name, and the database pointer
file (<project name>.xml) is updated with the new SSE SMTKINGDOM instance
information. The original portable project remains intact in the source location.
Kingdom 8.8 37
3. Select Attach Portable Project and Attach project database only.
4. Select the portable project file (.BAK). Click Browse and navigate to the <project
name>.tks.bak file in the portable project folder: <project name>_portable_<date
yyyymmdd>_<time>.
Note: You do not have a destination option for the project as the project will be activated and
attached to the database in its current location.
5. Select a SQL Server Express instance. Click the down arrow and select the
SMTKINDOM instance from the list. SMTKINGDOM instances are named
<computer_name>\SMTKINGDOM. If the instance you want is not on the list, enter the
information in the box.
6. Click Start to begin the process. A status bar will display the progress.
38 Kingdom 8.8
7. When the process is finished, the Summary Report will display project details.
Kingdom 8.8 39
Attach the Database and Copy the Project Files
This option copies the portable project file to the specified location and then attaches the
project database to the specified instance. The copied portable project folder is renamed to its
original name, and the database pointer file (<project name>.xml) is updated with the new
SSE SMTKINDOM instance information. The original portable project remains intact in the
source location.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
40 Kingdom 8.8
5. Select a project destination. Click Browse and navigate to the destination location for
the active project.
6. Select a SQL Server Express instance. Click the down arrow and select the
SMTKINDOM instance from the list. SMTKINGDOM instances are named
<computer_name>\SMTKINGDOM. If the instance you want is not on the list, enter the
information in the box.
7. Select a Validation mode.
8. Click Start to begin the process. A status bar will display the progress.
9. When the process is finished, the Summary Report will display project details.
When the attach is complete, the active project folder will be renamed to its original name
and the portable project folder will remain intact in its original location. The project is
connected to the specified SMTKINGDOM SQL Server Express instance and is ready for
production.
Kingdom 8.8 41
Make an Active Copy
Use Make an Active Copy to make an active copy of both the project and the database to a
location on your computer or network. The new project will have its own database identical to
the database in the original project. Note that the project and the database can reside on
different computers.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
42 Kingdom 8.8
5. Select a project destination. Click Browse and navigate to the project file location on the
network or your computer. Click OK.
6. Select a SQL Server Express instance. Click the down arrow and select the
SMTKINDOM instance from the list. SMTKINGDOM instances are named
<computer_name>\SMTKINGDOM. If the instance you want is not on the list, enter the
information in the box.
7. Select a Validation mode.
8. Click Start to begin the process. A status bar will display the progress.
Note: To Make an Active Copy both the Permissions and Security settings must be set to
Full Control for Everyone in the destination folder. If you get an error message, see
Windows File Sharing and Permissions for instructions on how to check or change
these settings.
9. When the process is finished, the Summary Report will display project details.
Kingdom 8.8 43
Create a Backup
Use Backup to make a non-active copy of the project for storage. The backup project folder
will include both the project files and a .BAK file of the database. The original project
remains active.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
44 Kingdom 8.8
6. Select a Validation mode.
7. Click Start to begin the process. A status bar will display the progress.
When the process is finished, the Summary Report will display project details.
The project.tks file will be appended with a .bak file extension. The backup project folder
name will be <project name>_Backup_<date yyyymmdd>_<time>.
For example, for a project named Golden_sse backed up on July 9, 2008 at 2:26 pm, the
backup project folder will be .
Kingdom 8.8 45
Restore a Backup
Use Restore a Backup to convert a project backup to an active state. This Restore tool will
only work on backups created by the SQL Server Express Management tool.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
46 Kingdom 8.8
6. Select a SQL Server Express instance. Click the down arrow and select the
SMTKINDOM instance from the list. SMTKINGDOM instances are named
<computer_name>\SMTKINGDOM. If the instance you want is not on the list, enter the
information in the box.
7. Select a Validation mode.
8. Click Start to begin the process. A status bar will display the progress.
Note: To Restore a Backup both the Permissions and Security settings must be set to Full
Control for Everyone in the destination folder. If you get an error message, see
Windows File Sharing and Permissions for instructions on how to check or change
these settings.
9. When the process is finished, the Summary Report will display project details.
When the restore is complete, the active project folder will be renamed to its original name
and the backup project folder will remain intact in its original location. The project is
connected to the specified SMTKINGDOM SQL Server Express instance and is ready for
production.
Kingdom 8.8 47
Move Project Files Only
Use Move to relocate the Kingdom project files without moving the database. The moved
project will remain active and will link to the original SQL Server Express database.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
48 Kingdom 8.8
6. Select a Validation mode.
7. Click Start to begin the process. A status bar will display the progress.
8. When the process is finished, the Summary Report will display source and destination
details.
Note: In some instances, the application is unable to delete one or more of the files in the
source folder. In this case, you will be prompted to use Windows to delete the
remaining SOURCE files. Deleting these source files will not affect the moved project
files.
Kingdom 8.8 49
Delete an Entire Project
The Delete option deletes the entire project, both the project files and the database. The Delete
command is irreversible, so delete with caution.
1. Launch Kingdom 32-bit or 64-bit.
2. Under Tools on the Kingdom Start Page click Manage SQL Server Express Projects.
50 Kingdom 8.8
6. In the warning message, click Yes if you are certain that you want to permanently delete
the project files and project database. A status bar will display the progress.
Warning: Often projects will have shared or linked seismic files. Before deleting the project,
ensure that there are no shared or linked files.
7. When the process is finished, the Summary Report will display project details.
Summary Report
Once the SQL Express Management action has been successfully completed, the Summary
Report dialog box opens as in the figure below:
The Summary Report displays the following details about the Source project and the
Destination project:
Project name
Project location
Database type
Database name
Note: If you selected Validation mode for the SQL Express Management action, and there
were validation issues, the issues will be listed in an additional panel.
Kingdom 8.8 51
Troubleshooting SQL Express Management
Prerequisite Issues
To successfully complete the SQL Server Express Management action, you will need to fix
the required prerequisite issues to continue.
The following tables lists the messages given and possible solutions.:
Message There was a problem connecting to the SQL Server Express Instance. Please
verify that the server is running.
Solution Start the SQL Server (SMTKINGDOM) service. Select Start > Settings >
Administrative Tools > SQL Server (SMTKINGDOM). In the Status
column, right click and select Start.
52 Kingdom 8.8
Message This utility only supports the SMTKINGDOM SQL Server Express instance.
Solution In the project folder, open the <project name>.xml file and check the database
instance. An SMTKINGDOMSQL Server Express instance will read as
follows:
<Connect_85>COMPUTER_NAME\SMTKINGDOM</Connect_85>.
The application did not detect \SMTKINGDOM as part of the instance name.
Message The source project is not using the SMTKINGDOM instance of SQL Server
Express for its database.
Solution Check that the project has been migrated to the SMTKINGDOM instance of
SSE from the Kingdom Software and retry.
Message The application has detected that here is not sufficient disk space available on
the destination directory. (Required space <>GB, available space <>GB). If
you know that there is sufficient disk space, you can ignore this warning and
continue.
Solution The SQL Management tool queries the Windows operating system for
available disk space. If you are running on a mixed platform, then the query
may not pick up available space on other operating systems such as Unix or
Linux. If you are sure there is enough space in the destination location, ignore
the message and continue with the operation.
Kingdom 8.8 53
Troubleshooting SQL Express Management
Message The destination SQL Server Express instance is remote from the portable
project. Do one of the following:
Move the source portable project folder to the SQL Server Express
instance machine OR
Share the source project folder to Everyone, and grant Everyone read
permissions.
Solution See Windows File Sharing and Permissions for instructions on how to set
sharing and permissions.
Message The SQL Express server on <destination computer name> is not running or
does not have the required SMTKINGDOM instance.
Solution The SMTKINGDOM instance of SQL Express must be installed from the
from the web download or from the SMTKingdom Software 8.6 DVD.
Message The portable project has been corrupted. Restore cannot continue.
Solution Necessary files or folders have been deleted, moved, or modified. The portable
project is no longer complete and valid.
All files have been successfully copied to the destination folder. The source
files are no longer required. However, the application is unable to delete one or
more of the files in the source folder. Please use Windows to delete remaining
SOURCE files.
Solution In some circumstances, after a Move, you may get this error message. You can
safely follow the directions in the message and delete the remaining source
files. The moved project files will not be affected.
54 Kingdom 8.8
Solution In some circumstances, after you make a project or project database portable,
you may get this error message. Kingdom was unable to delete the source
database, and/or was unable to rename the portable project folder. You can
safely follow the directions in the message.
You don not have full access rights on the source directory.
Warning Messages
Kingdom 8.8 55
Troubleshooting SQL Express Management
56 Kingdom 8.8
Windows File Sharing and Permissions
If you receive an error message regarding permissions, the first step is to make sure that
simple sharing on your computer has been disabled. For brief instructions, see the next section
Disable Simple File Sharing or Microsoft Help Topics.
In most cases, you only need Read/Write permissions specific to your user account, either
directly on a folder, if working locally, or on a network share if referencing a remote location.
In some cases, you must create a network share that has Read/Write permissions granted to
the Everyone group. In a few select cases with the copy operation, you must create a
network share that has Full Control permission granted to the Everyone group.
In all cases, the program will advise you of the specific permission and share requirements for
your specific case. For brief instructions, see the next section Changing Share and Permission
Settings on Destination Folder or Microsoft Help Topics.
Note: You may need to restart your computer for the changes in the sharing and permissions
to take effect.
Kingdom 8.8 57
Troubleshooting SQL Express Management
58 Kingdom 8.8
5. You can click Add and add your Windows user name to allow Full Control to you only, or
you can check Full Control to allow Full Control for Everyone.
6. After specifying the user name, and checking Full Control, select Apply as in the figure
below
Kingdom 8.8 59
Troubleshooting SQL Express Management
11. Enter the specific users name, or type Everyone and click Check Names.
60 Kingdom 8.8
If the entered user name is found in the selected Location, then the object name will
become underlined.
12. Click OK to return to the Security tab and check Full Control as Permissions for
Everyone or for the user name entered as in the figure below:
Note: You may need to restart your computer for the changes in the sharing and permissions
to take effect.
Kingdom 8.8 61
Troubleshooting SQL Express Management
62 Kingdom 8.8
Remote Local Local User Account 1. [Everyone or SQL Service Account] Read/
Write access to TKS project directory via a
Domain User network share.
Account
2. User Read/Write access to TKS project.
3. Sufficient free disk space in project directory for
database backup file.
1. [Everyone or SQL Service Account] Read/
Remote Remote Local User Account Write access to TKS project directory via a
network share.
Domain User
2. User Read/Write access to TKS project directory
Account
via a network share.
3. Sufficient free disk space in project directory for
database backup file.
Kingdom 8.8 63
Troubleshooting SQL Express Management
64 Kingdom 8.8
Microsoft SQL Server as the
Project Database
Note: The intent of this document is not to replace any documentation provided by the
Microsoft Corporation, but is provided only as an aid to the Kingdom user working in
a project that accesses a Microsoft SQL Server Database.
Kingdom 8.8 65
Installing and Configuring a SQL Server Database
Note: If you are installing SQL Server 2005, the Mixed Mode setting is specified in the
Authentication Mode dialog box.
66 Kingdom 8.8
You must select both the Database Engine Kingdom requires Mixed Mode Account Provisioning. With SQL
Services and the Management Tools. Other Server 2008 you must also specify a SQL Server administrator.
features are optional.
Note: The sa password will not be required by the Kingdom users as you will create a
different username and password for each database to hold a Kingdom project.
After installation, ensure that the SQL Server Management Studio (Management Tools) is
installed on the server machine. Select Start > Programs > Microsoft SQL Server [version].
You should see SQL Server Management Studio listed in your installed programs.
The SQL Server Management Studio does not have to be installed on each workstation. It
only needs to be installed on the machine with the SQL Server database.
In a network environment, multiple workstations can access the SQL Server database. The
required SQL Server client components on each Kingdom workstation are installed during the
Kingdom Software installation.
Kingdom 8.8 67
Installing and Configuring a SQL Server Database
68 Kingdom 8.8
Note: You can also login using SQL Server Authentication. Enter sa as the Login and the
password you created during the installation process.
Kingdom 8.8 69
Installing and Configuring a SQL Server Database
Note: SQL Server has numerous levels of server roles to define more granular levels of
access. Your database administrator may assign more restrictive server roles than
sysadmin as per your corporate policy.
70 Kingdom 8.8
Connect to the SQL Server Management Studio with a login that has sysadmin rights. Then
create a new Login account.
1. Expand the main Security node in the tree and right click on Logins.
2. Select New Login to open the LoginNew dialog box.
3. Select authentication type:
Windowssearch for or enter the domain login name. You could also enter an Active
Directory Group.
SQL Serverenter a login name/password and password policy information. Users
will need to enter this information when opening or creating a project.
4. Default database:
- For the SQL Server (Single) option, accept master as the default database.
- For the SQL Server (Multiple) option, change the default database to the database you
created for the multiple Kingdom projects.
5. Under Select a page in the upper left, select Server Roles.
6. In addition to public, select sysadmin.
7. Click OK to finish.
For other Windows users to access this project, the database administrator must add the other
users or groups as new logins. Repeat steps 1-7 above for each user or group.These users will
now be able to open and work in Kingdom project(s) in this SQL Server instance.
Authentication will come from active directory.
If the authentication type is SQL Server, additional users will need the entered user name and
password.
Note: If the user login does not have a sysadmin User Role, User Mapping and a change
from master as the default database to the selected database will be required. See
Microsoft documentation for more information.
When the user creates or migrates a Kingdom project using the single option, a database
named <projectname>_1 will be created in the selected instance.
When the user creates or migrates a Kingdom project using the multiple option, the project
tables will be added to the assigned database. All project tables will be prepended with a
unique identification number.
Kingdom 8.8 71
Installing and Configuring a SQL Server Database
On the computer where SQL Server is installed, open the SQL Server Configuration Manager
and Enable the TCP/IP protocol:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
Figure 2 Enable TCP/IP Protocol
2. Under SQL Server 2005 Network Configuration, select Protocols for <INSTANCE
NAME>.
3. In the right panel, check if the TCP/IP protocol is Enabled. If it is Disabled as in the figure
above, right click Disabled and select Enable.
4. You will need to restart the database service.
a. In the same Configuration Manager, select SQL Server 2005 Services in the left
panel.
b. In the right panel right click SQL Server (INSTANCE_NAME) and select Restart.
72 Kingdom 8.8
Enable TCP/IP Protocol on Client
Return to the Kingdom workstation and Enable the TCP/IP Client Protocol using the same
procedure:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
2. Under SQL Native Client Configuration, select Client Protocols.
3. In the right panel, check if the TCP/IP protocol is Enabled. If it is Disabled, right click
Disabled and select Enable.
Before you can create a Kingdom project, you must Create SQL Server Databases and Logins.
When you create a Kingdom project, the database schema will be automatically created.
1. Open Kingdom and choose Project > Create New Project or click the Create Project link
from the Kingdom Software Start Page.
2. In the Create New Project dialog box, navigate to the location where you want the
Kingdom project folder to reside, name the project and click Create.
3. Enter an author name for the project and click OK.
Note: Kingdom does not create a folder for the first author of a new project. All
interpretations for the first author are saved in the main project folder.
When creating a new project, make the first author an upper-level non-interpreter such
as company/group name. The creating author should not be a working author. Then
each new user can create an author name, which creates a subfolder in the project main
folder.
Kingdom 8.8 73
Installing and Configuring a SQL Server Database
SQL Server (Multiple)adds the project to an existing database that may contain
multiple Kingdom projects. The tables for each project have a unique number as a
prepend to the table name.
For both options, Logins can be created using Windows authentication or SQL Server
authentication.
Figure 3 Enter SQL Server Login Credentials
5. In the Microsoft SQL Server Configuration dialog box, enter the required information and
click OK.
SQL Server Connectthe host name of the machine running Microsoft SQL Server.
AuthenticationWindows or SQL Server. Only SQL Server authentication will
require a user name and password.
6. When you create a project in the designated SQL Server database, you will be asked if you
would like to create the T_PROJECT Table. You will only get a message with the first
project that the T_PROJECT Table is missing. Click Yes to create one and continue.
Note: Depending upon the speed of your Microsoft SQL Server database server and the
bandwidth of your network this process can take anywhere from a few seconds to
several minutes to create all the new tables and data.
When the project is ready, the Project Options dialog box opens.
7. Enter the required data and click OK to proceed.
74 Kingdom 8.8
Note: Click the Help button for information on the current dialog box.
8. The final step before your project is created is to specify the coordinate system of the new
project.
Click Yes and navigate to an existing project with the same coordinate system as the
project you are creating.
or
Click No to create the project with an undefined XY Projection Method. Once the project
opens, select Project > XY Projection Method and set your projection method.
With the creation of your first project, your SQL Server database is now ready to store your
Kingdom projects.
Kingdom 8.8 75
Connecting to your SQL Server Database
Note: You must know the SQL Server instance name, and your login credentials (user name
and password) before you can migrate your project database to SQL Server.
My SQL Server instance is not listedwhen creating a project, you cannot see your SQL
Server instance in the list of available instances.
Error occurred connecting to the databasea general error message when trying to create or
open a SQL Server project. This error could be caused by a number of reasons.
Troubleshooting tips are provided.
76 Kingdom 8.8
Problem 2: One of the TCP/IP protocols is not enabled.
If the SQL Server instance you are migrating to is not local (on your computer), the TCP/
IP protocols on the remote database instance and on your local (client) machine must be
enabled. If the SQL Server instance is on your machine, this is not an issue.
Solution 2A: On the computer where SQL Server is installed, open the SQL Server
Configuration Manager and Enable the TCP/IP protocol:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
Figure 4 Enable TCP/IP Protocol
2. Under SQL Server 2005 Network Configuration, select Protocols for <INSTANCE
NAME>.
3. In the right panel, check if the TCP/IP protocol is Enabled. If it is Disabled as in the figure
above, right click Disabled and select Enable.
4. You will need to restart the database service.
a. In the same Configuration Manager, select SQL Server 2005 Services in the left
panel.
b. In the right panel right click SQL Server (INSTANCE_NAME) and select Restart.
Solution 2B: Now return to the Kingdom workstation and Enable the TCP/IP Client Protocol
using the same procedure:
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager.
Kingdom 8.8 77
Connecting to your SQL Server Database
4. After you have completed parts A and B of the solution, open the Access Kingdom project
with Kingdom 64-bit and try the project migration again.
78 Kingdom 8.8
Oracle as the Project Database
Oracle Overview
Kingdom can utilize an Oracle database for storage of project data. This chapter explains only
the Oracle configuration pertaining to the Kingdom software which includes the following:
Configuring the Oracle Hoston the Windows, Solaris, or Linux machine designated as
the server.
Installing and Configuring the Oracle Clienton each interpreters workstation.
The section concludes with Connecting to your Oracle Databasea troubleshooting guide.
Oracle version 10g is used in this chapter for the example. The information provided in this
section is primarily for the Database Administrator (DBA) at your company. The client needs
to contact the DBA for the username and the Oracle instance.
Note: The intent of this document is not to replace any documentation provided by the
Oracle Corporation, but is provided only as an aid to the Kingdom user working in a
project that accesses an Oracle Database.
Note: Kingdom 32-bit requires the Oracle 32-bit client and Kingdom 64-bit requires the
Oracle 64-bit client.
If you are running Kingdom 32-bit on a 64-bit OS, you will need both clients installed
on your workstation.
Kingdom 8.8 79
Configuring the Oracle Host
Note: It is highly recommended that a tablespace and user be created for each Kingdom
project.
80 Kingdom 8.8
In our example, the Oracle instance created during the install was TRAINING.
After a successful login to the Oracle Enterprise Manager, you are ready to configure the
database for your Kingdom projects.
2. In the Oracle Enterprise Manager, select the Administration tab.
Figure 5 Select Tablespaces in Oracle Enterprise Manager
Kingdom 8.8 81
Configuring the Oracle Host
4. In the name box, type the Tablespace name. In our example, the name of the tablespace is
the name of the Kingdom project: SOONER.
Figure 6 Name Tablespace in Oracle Enterprise Manager
5. In the same window, scroll down to Datafiles and click Add on the far right.
82 Kingdom 8.8
6. In the Add Datafile window, enter a File Name for the datafile.
Figure 7 Name Datafile for Tablespace
7. In the File Directory box, search and select your file location or accept the default.
8. Enter a File Size for your Tablespace. Consult your database administrator for file size
requirements.
Note: Your Tablespace file size and Auto-Extend number will depend on the size of your
Kingdom projects. For large projects we recommend the following:
9. In the same window under Storage, check Automatically extend datafile when full.
Figure 8 Set Storage Autoextend Limits
Kingdom 8.8 83
Configuring the Oracle Host
10. Set the Increment to 100 MB (or any specified value) and accept the Unlimited
Maximum File Size.
11. Click Continue to complete the process of creating the tablespace.
12. Return to the Administration tab to create the Oracle users for Kingdom. In the Create
Tablespace dialog box, click the Database Instance: <Name> link at the top of the page.
84 Kingdom 8.8
2. In the Users dialog box, click on the far right.
c. Click the beside the Default Tablespace, select your tablespace from the list and
click Select.
d. Click the beside the Temporary Tablespace field, select TEMP or an alternate
temporary tablespace from the list and click Select.
Kingdom 8.8 85
Configuring the Oracle Host
Note: Use the same user name and password that you will use later when Kingdom creates a
new project in the Oracle database.
86 Kingdom 8.8
c. In the Modify System Privileges dialog box, use the scroll bar to locate, select and
move the following Available System Privileges to the Selected System Privileges
box:
CREATE TABLE
CREATE SESSION
CREATE VIEW
UNLIMITED TABLESPACE
d. Once the system privileges have been selected, click OK to return to the Create User
dialog box. The selected System Privileges will be displayed.
Kingdom 8.8 87
Configuring the Oracle Host
88 Kingdom 8.8
Installing and Configuring the Oracle
Client
The Oracle client is installed and configured on your workstation computer and includes the
following steps:
Install the Oracle Client
Create Oracle Service Name on Oracle Client
Set Oracle as the Kingdom Project Database
If you do not see your Oracle Service Name on the list, see Connecting to your Oracle
Database.
Note: If you are running Kingdom 32-bit on a 64-bit OS, you will need both clients installed
on your workstation.
In addition, if you are converting an Access Kingdom project to Oracle using the
database migration tool in the 64-bit version of Kingdom, you will need both Oracle
clients installed on your workstation.
This Oracle software may be installed before or after the Kingdom software, but both must be
installed for everything to work properly. Use the Oracle Universal Installer (OUI) to install
the client software.
Install the Oracle Client from the Oracle CD-ROM on the PC running Kingdom.
Kingdom 8.8 89
Installing and Configuring the Oracle Client
3. The Select Installation Type window appears. Click Administrator to install the
management console which will allow you to Configure the service names using the Net
Configuration Assistant unless directed otherwise by your network administrator.
4. In the Specify Home Details window accept the default or Browse to specify a location.
Click Next.
5. The Product-Specific Prerequisite Checks window appears verifying that your
environment has met all the installation and configuration requirements. The Status field
should state Succeeded. Click Next.
6. The Summary window will appear which displays all of your new installations you are
about to install and available space remaining. Click Install.
Installation may take several minutes.
7. In the End of Installation window click Exit.
Note: You can also manually add entries to the file tnsnames.ora located in the oracle
directory on the client machine. The default location is on your C drive:
C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN
90 Kingdom 8.8
All Programs > Oracle - OraClient10g_home1 > Configuration and Migration Tools > Net
Configuration Assistant
Note: The Net Configuration Assistant also opens automatically after installation of the
Oracle client.
2. On the Welcome page, select Local Net Service Name Configuration and click Next to
add the net service name to the tnsnames.ora file.
Note: To complete Net Service Configuration, you will need the host, service name, and port
number of the Oracle server. These were provided for the database during the server
install.
3. Select Add and Next to continue through the wizard entering the information about the
Oracle server:
a. Service Nameis the name of the Oracle database, not the computer name. Enter the
service name and click Next.
b. TCP Protocolis the standard Ethernet protocol used for client/database server
conversation over a network. Select TCP and click Next.
c. Host nameis the name of the computer where the host Oracle database is located.
Enter the host name.
d. Port numberaccept the standard port number or select Use another port number
(as provided for the database during the server install) and click Next.
Kingdom 8.8 91
Installing and Configuring the Oracle Client
c. In the Change Login dialog box, enter the Oracle user name and password established
in the Create Oracle Users for Kingdom Projects process (sooner/sooner) and click
OK.
d. If the test was successful, the following message will appear:
Figure 10 Connection Test to Oracle Database Successful
92 Kingdom 8.8
5. Click Next to continue.
6. Accept the default Net Service Name and click Next.
7. Would you like to configure another net service name? Click No and Next to complete
the net service name configuration.
8. Click Next and Finish in the final dialog box of the Wizard.
You should now be able to create your Kingdom project and Set Oracle as the Kingdom
Project Database. Alternatively, you can now convert an Access or SQL Server project to
Oracle. For project conversions see Kingdom Project Database Conversions.
To convert your existing project database to Oracle see Kingdom Project Database
Conversions.
Create a project in Kingdom using the Oracle database server to store project data.
1. Open Kingdom and choose the Project > Create New Project.
2. Create New Projectselect a location and enter a name for your Kingdom project and
click Create.
3. Select Project Database Typeselect the Oracle and click OK.
Kingdom 8.8 93
Installing and Configuring the Oracle Client
Note: If you are running Kingdom 64-bit, only the MS SQL Server and Oracle databases will
be available.
4. Enter User Name and Password in the Oracle Configuration dialog box (see the figure
below):
Project Path location of the Kingdom project.
Oracle Service Name the name you configured above using the Oracle Net
Configuration Asst.
UserName / Password must match the Oracle login credentials. See Create Oracle
Users for Kingdom Projects.
In our example, the Oracle Service Name is TRAINING. The User Name is sooner (the
name of the Kingdom project).
Note: If you do not see your Oracle Service Name in the list, see Connecting to your Oracle
Database for troubleshooting tips.
94 Kingdom 8.8
Connecting to your Oracle Database
The following section gives troubleshooting tips for a database migration to Oracle. These tips
also apply to problems opening an existing Oracle Kingdom project.
Kingdom requires Oracle users to have CREATE VIEW System Privileges. Your Oracle
DBA may need to add this privilege for each Oracle user before you can open or create
Kingdom projects with Oracle. See Create Oracle Users for Kingdom Projects.
You must know the Oracle instance name, and your login credentials (user name and
password) before you can migrate your project database to Oracle. Contact your database
administrator.
Kingdom 32-bit requires the Oracle 32-bit client and Kingdom 64-bit requires the Oracle
64-bit client. Both clients can be installed on the workstation which will allow both
versions of Kingdom to connect to Kingdom Oracle projects.
Note: If you are running Kingdom 32-bit on a 64-bit OS, you will need both clients installed
on your workstation.
In addition, if you are converting an Access Kingdom project to Oracle using the
database migration tool in the 64-bit version of Kingdom, you will need both Oracle
clients installed on your workstation.
Windows XP and Kingdom 32-bit users: Some versions of Oracle do not work with
applications installed in directories that contain parentheses. If you are using Oracle as
your Kingdom project database and you have installed Kingdom 32-bit on a Windows XP
64-bit operating system, the default installation directory has parentheses in the path:
C:\Program Files (x86)\KingdomSuite. You will need to do one of the following:
- Uninstall Kingdom 32-bit and reinstall to a folder without parentheses (e.g.
C:\KingdomSuite).
- Install a version of Oracle that does work with parentheses or install patch 5059238 for
Oracle client 10.2.0 32-bit.
Kingdom 8.8 95
Connecting to your Oracle Database
. If you cannot see your Oracle instance in the drop down list, the most common reason is
that you need to create the Oracle service name on your workstation using the Net
Configuration Assistant.
The Net Configuration Assistant creates the tnsnames file which contains the service
name, host, and port information. This file is in the Oracle home directory:
C:\oracle\product\10.2.0\client_64\NETWORK\ADMIN
Check network connectivity. If you recently moved the Oracle database server computer
or if you moved your workstation on the network, the Oracle database server and the
Windows PC may not be able to see each other on the network anymore.
- You can verify your Windows PC can communicate with the Oracle database server by
opening a command prompt on the Windows PC and typing ping OraTestServer.
Where OraTestServer is the host machine and where Oracle is running.
Ensure the Oracle server computer is on and that Oracle is running. Contact your database
administrator.
96 Kingdom 8.8
Kingdom Project Backups
Overview
This section includes the following topics:
What do I Backup?the Kingdom project includes 4 components. For a full backup, you
must include all components.
Backing up Kingdom Project Databasesa brief overview of backup procedures for SQL
Server, Oracle, and SQL Server Express databases.
Make a Single Project Manual Backup with DBAdminsteps for backing up a Kingdom
project with a SQL Server or Oracle database using Kingdoms Database Admin tool.
Kingdom 8.8 97
What do I Backup?
What do I Backup?
Every Kingdom project has four parts:
The project files by default, project files are saved in the project folder. For a
description of file types see The Kingdom Project Architecture.
The project databaseAccess databases and Auto SQL Server Express databases reside
inside the project folder. Oracle and SQL Server databases (including Manual SQL Server
Express databases) are external to the project folder. See Backing up Kingdom Project
Databases.
External data files some files can be stored outside of the project folder. If files such as
seismic data, author folders, or raster logs have been saved in locations outside of the
project folder, these files will not be backed up unless they are copied or moved into the
project folder. However, also note that external files that do not change often such as
seismic files can be backed up separately. See The Kingdom Project Architecture.
Custom color bar files stored in the <Kingdom installation directory>\Colorbars folder.
Custom color bars can be saved individually or placed in the same zip file.
Note: Do not save the colorbars that ship with the product. Save only colorbars you have
created or modified. Although user-customized color bars can be saved anywhere, by
default they are stored in Kingdom installation Colorbars directory.
98 Kingdom 8.8
Backing up Kingdom Project Databases
For MS Access-based projects, most well data and pointer files reside in the <project
name>70.mdb in the project directory. The <project name>70.mdb database file can be
backed up in the same file as the rest of the project.
Additional backup procedures are recommended if Oracle or SQL Server is the selected
database. In the event that all projects are stored in one Oracle database, all projects would be
rolled back if it became necessary to roll back the database. However, this creates the
possibility that the Oracle backups and the project folder backups could get out of sync if they
are not coordinated. If this were to happen, the result would be either orphaned database
records, or orphaned project files.
To keep the project file data and database data synchronized, you can use the Database Admin
tool to backup individual Oracle or SQL Server Kingdom projects.
First Make a Single Project Manual Backup with DBAdmin
Then Restore a Kingdom Project with DBAdmin
It is, however, a recommended practice to create a unique Oracle account or SQL Server
database to accommodate each Kingdom project. In that way, most standard external database
backup-restore procedures will treat each Kingdom project independently, and not rollback
multiple projects to restore a single project.
The database for Auto SQL Server Express projects are in the project folder. Both the
database tables and project files can be backed up by making a copy of the project folder.
For Manual SQL Server Express projects use the SQL Server Express Management tool in the
Database Admin utility. This tool will backup both database tables and project files into one
file.
You can access the tool from the Kingdom Start Page.
Under Tools, click Manage your Manual SSE Projects.
Kingdom 8.8 99
Backing up Kingdom Project Databases
Related Topic
1. To open DbAdmin from your desktop, select Start > Programs > The Kingdom
Software > DbAdmin [version].
Note: The version of DbAdmin, both the bit version and release version, must match the
version of Kingdom the project was last opened in.
3. In the Select a Project Manager dialog box, select the database type of the current project
and click OK.
Note: For Access projects, the database <project name>70.mdb file is located in the project
folder and has a size limit of 2 GB. To back up an Access project, you do not need to
use DBAdmin. Simply copy the project folder to the backup location. Be sure to
include any files that may reside outside of the project folder.
However, if space in the backup location is limited, you can create a backup using the
DBAdmin tool as enumerated below. The Access project backup without the original
database will be smaller than the original project.
4. For Oracle and SQL Server databases, enter the login credentials and click Next.
For SQL Server Express or Access projects, navigate to the <project name>.tks file of
the project you wish to back up and select.
5. When you are connected to the project database in DBAdmin, click the project that is to be
backed up.
Figure 11 Select Project to be Cloned in DbAdmin
Note: Database Admin Tool dump files are not equivalent to Oracle database dump files.
They are ASCII xml files unique to Kingdom.
Warning: Certain files may reside outside the project folder: seismic files, raster logs, author
folders, and culture files. For a complete backup, ensure that these external files
are in the project folder, or that their respective folders are also backed up.
Note: If your original project was Access, the backup folder will contain both the dump of
the database (export.dmp), and the original Access database (<project name>70.mdb).
If the size of the backup folder is an issue, you can remove the original access database
to an external location as the contents are contained in the export.dmp file.
If you have created a project backup of your Kingdom project with the Database Admin tool,
you can restore the project with the same tool.
You will:
1. Create a New Twin Project in the Target Database
2. Import the Database Dump into the Twin Projects Database.
Note: To restore SQL Server Express projects, use the SQL Server Express Management
tool. On the Kingdom Start Page click Manage your Manual SSE Projects.
- For Oracle and SQL Server projects, the project tables are created in the designated
Oracle or SQL Server instance, and the <project name>.xml file is created in the twin
project folder.
Note: The <project name>.xml file is the pointer file to the SQL Server or Oracle database.
This file contains the instance, username, password, and windows login information.
Access projects do not have an .xml file.
After the project tables are created, the Project Options dialog box opens.
9. Enter the same project options as the original project and click OK.
10. Click No to Do you want to use the coordinate system of an existing project? This
information is already recorded in the dumped database in the backup, and will be
retrieved once the project is converted.
11. Exit the Kingdom application.
12. Navigate to the twin project folder which is located within the original project folder.
- For Access projects, copy the <project name>70.mdb file up one level into the
original project directory.
- For SQL Server and Oracle projects, copy the <project name>.xml file up one level
into the original project directory.
The project database is now ready to be populated by the export.dmp file. For SQL Server and
Oracle projects, the <project name>.xml file is now in the project folder to point to the
database.
Start > Programs > The Kingdom Software [version] > DBAdmin
1. Run the DBAdmin tool again. From your desktop, select Start > Programs > The
Kingdom Software [version] > DBAdmin.
2. Select Database > Connect.
3. Select the Project Manager for the project (database type).
4. For SQL Server or Oracle, input the Service Name, User Name, and Password then click
OK.
For SQL Server Express and Access projects, browse to the tks file in the project folder
and click OK.
For Oracle or SQL Server, you may see more than one project in the left panel. Select the
new project that you just created from the project tree.
For Access and SQL Server Express projects there will be only one project in the left
panel.
Note: With some Oracle and SQL Server database configurations there may be multiple
Kingdom projects in the same database, with each project identified by a unique
prepend number. An easy to find a project in DBADMIN is to search by the projects
GUID number. The GUID can be found in the <project name>.xml file in the project
directory, and entered (including the enclosing brackets) in the window after clicking
Project > Find Project by GUID in DBADMIN.
5. Select Project > Import From File and click Yes to import the export.dmp file from the
project backup folder.
6. Click Yes in the replace project warning.
7. Navigate to the export.dmp file in the project backup folder, and click Open to begin the
import.
An import status dialog will be displayed.
The time needed to import will depend on the project size. The dbAdmin.exe main
window may not be displayed throughout the entire import process but will be displayed
again when the import is completed.
8. When the import is complete, exit the DBAdmin tool.
The project should be restored to an active state.
Note: The SQL Server Management Studio Express tool can be downloaded from the
Microsoft download Center. Click the link below and scroll to the bottom of the page:
Note: The backup file location must be a local drive on the database server. If necessary, the
files can be moved later. SQL Server and SQL Express both require you to use only
local drives as the location to: 1) install the software, 2) store database files and 3) save
database backup files. SAN drives also qualify as local drives.
6. In the Back Up Database dialog box you can click OK to carry out an immediate backup
of the Kingdom project database, or you can save the backup instructions to a file for later
execution.
To save the backup instructions to a file, click the down-arrow next to the Script button
and select Script Action to File (figure below).
Figure 15 Saving Backup Instructions
7. Select a location to save the structured query language (.sql) file and enter a File name:
Kingdom_Projects_Auto_Backups. (No default file name is provided).
8. Open the resulting file for edit. Right click the file and select Edit. The file will open in
Notepad.
9. To add additional databases to this script file in order to back up all databases, you can do
one of two things:
a. Repeat the above steps and select Script Action to Clipboard instead of Script Action
to File. Then paste (Ctrl+V) the backup instruction string into the .sql text file that is
open (figure below), or
b. Repeatedly copy and paste the initial line of instructions and edit the database name on
each line to match the remaining database names. There are three occurrences to edit
on each line of instructions.
Figure 16 Results of Pasting New Backup Instruction into .sql File
10. Save the final edited .sql backup script when completed.
11. When it is time to make a backup of your project databases, simply double-click the *.sql
backup script file, and the SQL Server Studio Management (or Management Express) tool
will open with the backup scripted steps ready to execute.
12. Click Execute in the Management Studio (figure below). The backups will be written to
the designated location: <database name>.bak.
Figure 17 Executing the Backup Script Manually
13. Copy the backup files out of the destination folder to a permanent location so they are not
overwritten later.
2. On the New Job dialog box, assign a job name and category (figure below).
Figure 19 Describing the Backup Job
3. Next, Select Steps under Select a page, and add the steps you previously scripted.
a. Click New at the bottom of the New Job dialog box.
b. Insert the steps contained in the .sql backup script you previously built. Click Open in
the New Job Step window (see figure below).
Figure 20 Preparing to Open the .sql Script to Insert Job Steps
c. Navigate to the location of the .sql script you built and click Open (see figure below).
Figure 21 Navigating to the .sql Script
The backup script steps contained in the .sql file will now appear as steps in your
scheduled backup job.
d. Enter a Step name and click OK (see figure below).
Figure 22 Backup Steps Now as Part of the Job
4. Now, under Select a page click Schedules on the Job Properties window and click the
New button to open the New Job Schedule window.
5. Select a backup time or frequency and start date and end date for your job, then click OK
to approve the scheduled job (see figure below).
Figure 23 Creating a Daily Backup Schedule
6. Add any other desire alerts or notifications and click OK to complete the scheduling.
7. Check the destination folder location of the backups after a scheduled job to assure that
backups are being properly executed.
8. Copy backups to a new location to prevent over-writing of backups if a longer history is
required. You can script this copy job to a .bat batch file and place it in the Windows
scheduler to make your job easier.
Summary
Kingdom database backups can be automated with the help of either SQL Server Management
Studio Express (downloaded from the Microsoft Download Center) or with SQL Server
Management Studio, purchased as part of full-featured SQL Server:
The sql script that is created with SQL Server Management Studio Express must be
executed manually.
The same sql script is used by SQL Servers Agent to schedule the backups for automated
after-hours execution.
Overview
Kingdom offers the user a choice the following databases: SQL Server SQL Server Express,
Oracle, and Access.
Kingdom 32-bit supports Microsoft Access as a database. Kingdom 64-bit does not. If your
projects are currently in Access but you would like to run Kingdom 64-bit, a database upgrade
to SQL Server Express, SQL Server, or Oracle is required.
You can convert your Kingdom project databases by the following methods:
Migrate Access Database to SQL Server Expressopen your Access project with
Kingdom 32-bit or 64-bit. You will be given the option to migrate (convert) your Access
database to SQL Server Express.
Migrate Access Database to SQL Server or Oracleopen your Access project with
Kingdom 32-bit or 64-bit. You will be given the option to migrate (convert) your Access
database to SQL Server or Oracle.
Convert Your SQL Server Express Project Back to Accessuse the Database Admin tool
for this database conversion.
Convert SQL Server or Oracle Database to Access with DBAdmin
Convert SQL Server Database to Oracle (or vice versa) with DBAdmin
Kingdom Data Managementa project and data management application with database
conversion, data transfer and other project and data management capabilities. Kingdom
Data Management requires a separate license.
Note: When using the Database Admin Tool to manage your Kingdom projects (export/
import database, delete), make sure that the Kingdom project is in the same version of
Kingdom as the DBAdmin tool.
For example, if you are launching DBAdmin from Kingdom 8.7, any projects being
managed should also be in Kingdom 8.7. If necessary, upgrade the project to the
version of DBAdmin before using the tool on that project.
Note: For troubleshooting tips see An Error Occurred Connecting to the Database.
When you open a Kingdom project with an Access database, you will be prompted to migrate
your project to SQL Server, SQL Server Express, or Oracle.
You can also open the Access Database Migration tool from the Kingdom Start Page.
Click the Migrate Access Project link under Tools and browse to the *.tks file of the Access
project:
If you are running the 32-bit version of Kingdom, you will be prompted to migrate your
project, but the database migration is optional.
If you are running the 64-bit version of Kingdom, you must migrate the project before you can
open it.
You must have the SQL Server or Oracle client installed on your computer. The SQL Server
client is installed with Kingdom. For Oracle client installation and configuration see Installing
and Configuring the Oracle Client.
See also Choosing a Database for a brief discussion of your options.
You must also know the database configuration information: database (instance) name, user
name, and password.
1. From the Kingdom Software Start Page select Project > Open Project.
2. Browse to the Access project.tks file and click Open.
The Migrate Project Database dialog box will open as in the figure above.
3. Select Microsoft SQL Server or Oracle and click Migrate. The Access database
contents will be imported into the specified database instance.
4. Click the down arrow and select the SQL Server or Oracle instance.
5. Click OK to import the project into the Oracle or SQL Server database and complete the
migration.
The Select Author dialog box opens, and your project is ready to go.
Note: The Kingdom project folder remains in the same location with the same name. The
Access database is renamed and the <project name>.xml file is created. This .xml file
is the pointer to the project database.
Note: Before beginning the conversion process, we recommend that you back up the original
project which includes the Kingdom project folder and the external database.
Backup your SQL Server Express projects with the SQL Server Express (SSE)
Management tool available from the Kingdom Start Page.
If you are a Kingdom 64-bit user, you have migrated your Kingdom project database to SQL
Server Express, you can convert it back to MS Access using either Kingdom Data
Management 32-bit or the Database Admin Tool included with your base feature of the
Kingdom software.
Once you have converted your project database back to Access, you will not be able to use
Kingdom 64-bit for this project as Microsoft does not support Access in a 64-bit application.
Instead, launch the 32-bit version of Kingdom and open the project.
Kingdom Data Managementis a project management application with a wide range of
project inventory and management tools which allows you to see and interact with the
contents of all your Kingdom projects simultaneously, making day to day project management
tasks such as converting databases infinitely easier. Kingdom Data Management requires a
separate license.
Database Admin Toolis included with the base Kingdom license. You will need to have
the 32-bit version of Kingdom installed to convert the database from SQL Server Express to
MS Access.
Note: MS Access has a database size limit of 2 GB. You will not be able to make the
conversion back to Access if the database is larger than 2GB.
Note: When using the Database Admin Tool to manage your Kingdom projects (export/
import database, delete), make sure that the Kingdom project is in the same version of
Kingdom as the DBAdmin tool.
For example, if you are launching DBAdmin from Kingdom 8.7.1, any projects being
managed should also be in Kingdom 8.7.1. If necessary, upgrade the project to the
version of DBAdmin before using the tool on that project.
Using the Database Admin Tool and Windows Explorer, the project conversion back to
Access involves the following steps:
1. Open the Database Admin Tool in the 32-bit version. From your desktop select Start >
Programs > The Kingdom Software (32-bit) > DbAdmin (32-bit).
2. In the Database Admin tool, select Database > Connect to open the Project Manager
dialog box.
3. Select Kingdoms SQL Server Express.
Note: If Microsoft Access is not displayed, you have launched DBAdmin (64-bit).
4. In the <Database Type> Configuration dialog box, select a SQL Server Express
instance: CompName\SMTKINGDOM.
Click OK and navigate to the <project name>.tks file in the project folder.
Once you have connected to your project in DBAdmin, the project path and name will
appear under Projects in the left panel as in the figure below.
5. In the Database Admin tool, select your project in the left panel and export the project
database as a *.dmp file to the project folder.
a. With the project path highlighted, select Project > Export to File.
Note: Database Admin Tool dump files are not equivalent to Oracle database dump files.
They are ASCII xml files unique to Kingdom.
7. Click No in the NULL out message to complete the export. DBAdmin will complete the
database export to the specified location, or the default location of the project folder.
a. In Windows Explorer, navigate to the project folder and locate the renamed Access
database file, or <project name>70sav.mdb.
b. Right click the <project name>70sav.mdb file, select Rename. Remove the sav from
the file name. The Database Admin Tool will now be able to connect to the Access
database.
2. In the Kingdom Software 32-bit Database Admin Tool, connect to the projects renamed
Access database.
a. In the Database Admin Tool main window, select Database > Connect and select
Microsoft Access as your database. Click OK.
Note: Only the 32-bit version of the Database Admin Tool will have the Access databases as
choices.
b. In the Open dialog box, navigate to the project folder, select the <project name>.tks
file and click OK. The project path and name will appear in the left panel of the
DBAdmin window.
3. Import the *.dmp file into the project. This will replace the old Access contents.
a. In the left panel, highlight the project.
b. In the Database Admin Tool main menu, select Project > Import from File.
c. In the warning box, click Yes to replace this project with the import data.
d. In the Windows Open dialog box, navigate to the export.dmp file in the project folder
and click Open.
The contents of the SQL Server Express database will replace the original contents of the
Access database.
Note: If your project was not originally created in Access, you will have an extra step: Create
a Twin Access Database if no Access Database Exists
Note: MS Access has a database size limit of 2 GB. You will not be able to make the
conversion back to Access if the database is larger than 2GB.
Before beginning the conversion process, we recommend that you back up the original project
which includes the Kingdom project folder and the external database.
Using the Database Admin Tool and Windows Explorer, the project conversion to Access
involves the following steps:
Step 1: Create a Database Dump of the Original Project:
Step 2: Create a Twin Access Database if no Access Database Exists
This step is only required if the project was created in Oracle, SQL Server, or SQL
Express. In this case, there would be no <project name>70sav.mdb file in the project
folder.
Step 3: Import the Database Dump File into the Target Access Database
1. Open the Database Admin Tool in the 32-bit version. From your desktop select Start >
The Kingdom Software (32-bit)>DbAdmin.
2. In the Database Admin tool, select Database > Connect to open the Project Manager
dialog box.
3. In the Select a Project Manager dialog box, select the database of your project.
4. In the <Database Type> Configuration dialog box, enter the Service Name, User Name,
and Password.
5. In the Database Admin tool, select your project in the left panel and select Project >
Export to File.
Depending on your database configuration, you may see more that one project listed.
Note: Database Admin Tool dump files are not equivalent to Oracle database dump files.
They are ASCII xml files unique to Kingdom.
This step is only required if your project was not originally created in Access. You will have
to create a dummy project in Access with the same <project name> and project options as
your source project.
If your project was originally created in Access and has a <project name>70sav.mbd file,
proceed to Import the Database Dump File into the Target Access Database.
1. In Kingdom 32-bit, select Project > Create New Project.
2. Navigate to the source Kingdom project folder. Create the new project inside the existing
project folder.
3. In the Create New Project dialog type the name of the project to be converted. This name
must be identical to the original name. After typing in the project name click Create.
4. Click Yes in the warning message.
5. In the Author Name dialog box, enter an author and click OK.
6. Select Access as your Project Database and click OK.
After the project tables are created, the Project Options dialog box opens.
7. Enter the same project options as the original project and click OK.
8. Click No to Do you want to use the coordinate system of an existing project? This
information is already recorded in the dumped Oracle or SQL Server database, and will be
retrieved once the project is converted.
Note: If you created a new Access database then you will not need to rename the file. Skip to
step 2.
a. In Windows Explorer, navigate to the project folder and locate the renamed Access
database file, or <project name>70sav.mdb.
b. Right click the <project name>70sav.mdb file, select Rename. Remove the sav from
the file name. The Database Admin Tool will now be able to connect to the Access
database.
2. In the Kingdom Software 32-bit Database Admin Tool, connect to the projects renamed
Access database.
a. In the Database Admin Tool main window, select Database > Connect and select
MS Access as your database. Click OK.
Note: Only the 32-bit version of the Database Admin Tool will have the Access databases as
choices.
b. In the Open dialog box, navigate to the project folder, select the <project name>.tks
file and click OK.
3. Import the *.dmp file into the project. This will replace the old Access contents.
a. In the left panel, highlight the project.
b. In the Database Admin Tool main menu, select Project > Import from File.
c. In the warning box, click Yes to replace this project with the import data.
d. In the Windows Open dialog box, navigate to the export.dmp file in the project folder
and click Open.
The contents of the SQL Server Express database will replace the original contents of the
Access database or populate the new Access database.
Note: MS Access has a database size limit of 2 GB. You will not be able to make the
conversion back to Access if the database is larger than 2GB.
Warning: Be very careful when you delete the twin Access project. Open the folder before
you delete to check the contents. There should be no author folders or
interpretation files in the project folder.
Note: For troubleshooting tips see An Error Occurred Connecting to the Database.
You can convert your Kingdom project database from SQL Server to Oracle or vice versa
using either Kingdom Data Management or the Database Admin Tool included with your base
feature of the Kingdom software.
Kingdom Data Managementis a project management application with a wide range of
project inventory and management tools which allows you to see and interact with the
contents of all your Kingdom projects simultaneously, making day to day project management
tasks such as converting databases infinitely easier. Kingdom Data Management requires a
separate license.
Database Admin Toolis included with the base Kingdom license.
Before beginning the conversion process, we recommend that you back up the original project
which includes the Kingdom project folder and the external database.
Using the Database Admin Tool and Windows Explorer, the project conversion involves the
following steps:
Step 1: Create a Database Dump of the Original Project:
Step 2: Create an Empty Target Database
Step 3: Import the Database Dump File into the Target Database
1. Open the Database Admin Tool. From your desktop select Start > The Kingdom
Software (32 or 64 bit) > DbAdmin.
2. In the Database Admin tool, select Database > Connect to open the Project Manager
dialog box.
3. In the Select a Project Manager dialog box, select the database of your project.
Note: Only the 32-bit version of the Database Admin Tool will have the Access databases as
choices.
4. In the <Database Type> Configuration dialog box, enter the Service Name, User Name,
and Password.
5. In the Database Admin tool, select your project in the left panel and select Project >
Export to File.
Note: Database Admin Tool dump files are not equivalent to Oracle database dump files.
They are ASCII xml files unique to Kingdom.
You will need to know the project options of your project to create the empty target database.
1. In Kingdom, select Project > Create New Project.
2. Navigate to the source Kingdom project folder. Create the new project inside the existing
project folder.
3. In the Create New Project dialog type the name of the project to be converted. This name
must be identical to the original name. After typing in the project name click Create.
4. Click Yes in the warning message.
5. In the Author Name dialog box, enter an author and click OK.
6. Select your target project database and click OK.
7. Enter the database name, user name and password and click OK.
After the project tables are created, the Project Options dialog box opens.
8. Enter the same project options as the original project and click OK.
9. Click No to Do you want to use the coordinate system of an existing project? This
information is already recorded in the dumped Oracle or SQL Server database, and will be
retrieved once the project is converted.
10. Exit The Kingdom application.
11. Now Browse to the new twin project folder which is located within the original project
folder and move or copy the new <project name>.xml file up one level into the original
project directory. Click Yes to replace the existing file.
The target database is now ready to be populated by the export.dmp file.
The next step is to import the *dmp file into the target database.
1. In the Database Admin Tool main window, select Database > Connect and select the
database that you created as your target database. Click OK.
Note: Only the 32-bit version of the Database Admin Tool will have the Access databases as
choice.
2. In the <Database Type> Configuration dialog box, enter the Service Name, User Name,
and Password.
3. In the Database Admin tool, select your project in the left panel. With the project path
highlighted, select Project > Import from File.
4. In the warning box, click Yes to replace this project with the import data.
5. In the Windows Open dialog box, navigate to the export.dmp file in the project folder and
click Open.
The contents of the exported (source) database will populate the new target database.
6. Now open the project in Kingdom to verify that the project converted successfully.
7. Once you have confirmed that the project converted successfully you can delete the empty
twin project folder within the main project folder.
Overview
Start > Programs > The Kingdom Software [version#] > DbAdmin
The Database Admin Tool can be used to examine and edit (if required) Kingdom project
database tables, copy and convert project databases, set the conditions and backup procedures
for archiving Kingdom project databases, and specify parameters for the Kingdom Data
Managements Data Transfer tool and OpenSpirit/Tunnel O connectivity.
Note: When using the Database Admin Tool to manage your Kingdom projects (export/
import database, delete), make sure that the Kingdom project is in the same version of
Kingdom as the DBAdmin tool.
For example, if you are launching DBAdmin from Kingdom 8.7.1, any projects being
managed should also be in Kingdom 8.7.1. If necessary, upgrade the project to the
version of DBAdmin before using the tool on that project.
On your desktop, click Start > Programs > The Kingdom Software 8.7.1 > DbAdmin to
launch the Database Admin Tool as seen in the figure below.
From the main menu bar in the Database Admin Tool window, choose Database > Connect
to open the Select a Project Manager dialog box.
The Select a Project Manager dialog box displays the various types of databases that are
valid project databases within Kingdom. Click a project manager icon to open the Open
dialog box, in which you can navigate to select a project.
For Oracle, SQL Server, and SQL Server Express databases the next step is to enter the
database login credentials. For Access databases, no login credentials are required. You will
browse to the Kingdom project folder and select the *.tks file.
Oracle Configuration
When an Oracle Project Manager is selected as the Project Manager, the Oracle
Configuration dialog box opens allowing you to specify the Oracle Service Name, User
Name and Password.
Oracle Service Namename assigned to the Oracle database when the client portion of
the Oracle components were installed on the local system.
User Nameuser name associated with the Oracle Instance when database tables were
created on the server system.
Passwordpassword associated with the Oracle Instance.
Note: This account will need administrative privileges if you intend to delete a project.
Backup and restore require only read/write access rights to the tables.
If a SQL Server project manager is selected as the Project Manager, the SQL Server
Configuration dialog box opens allowing you to specify the SQL Server name, User name
and Password.
Tip: This tool is also available from the Kingdom Start Page under Tools.
Once DbAdmin has connected to the specified database, the following menu items are added:
DBAdmin Project Menuprovides options to manage the individual project tables,
including create new project tables, edit project information, create author reports, and
import / export dump files for backup, copy and recovery.
Run a Script on Projects in DBAdminprovides options to create and run scripts on
selected projects or all projects.
Warning: Editing project information incorrectly will corrupt the project. Only edit if you are
sure the edits are valid.
Backup Tools
See also Backing up Kingdom Project Databases
Note: For Manual SQL Server Express projects, use the Manual SQL Server Express (SSE)
Management tool in the Database Admin utility. This tool will backup both database
tables and project files into one file.
Projects using the Auto SSE configuration can be backed up by copying the project
folder once all authors have exited the project. The detached database files are in the
project folder.
Backupallows you to select a Control File, activate an interactive backup and review
the report log at completion
Control Fileclick to open a standard Windows Open dialog box, in which you can
navigate to locate a *.ctl control file to use in your backup.
- Newclick to open a Save As dialog box, in which you can navigate to locate an
SMT Backup Control File (smtbackup.ctl) to use in the Save operation.
- Verifyclick to open a standard Windows Open dialog box, in which you can
navigate to locate a *.ctl control file to verify.
- Deleteclick to open a standard Windows Open dialog box, in which you can
navigate to locate a *.ctl control file to select and delete.
- Editclick to open a standard Windows Open dialog box, in which you can navigate
to locate a *.ctl control file to select and edit.
- Mergeclick to open a standard Windows Open dialog box, in which you can
navigate to locate and select *.ctl control files to merge.
Warning: Syntax errors can be introduced in the *.ctl file if the file is manually edited.
1. Select Backup Tools > Control File > New to open a browser window in which you can
specify and Save the directory folder and the output file name of the control file.
or
Select menu Backup Tool > Control File > Edit to open the file browser window.
2. Click the newly created control file, smtbackup.ctl, then click Open to open the
Database Admin Tool with smtbackup.ctl open as shown below.
3. Double-click GLOBAL in the Projects tree. The Modify Project Backup Info dialog
box opens and displays the GLOBAL parameters of the Control File (*.ctl).
The Modify Project Backup Info dialog box allows you to specify parameters that are used
in the back-up procedure.
Backup parameters are set at two levels:
GLOBALglobal settings are parameters that are general to all projects in the control
file. If the parameters have not been specifically altered in each local projects settings
then the GLOBAL settings is used during backup. An example of GLOBAL setting is
shown in the figure Control File Attributes in Database Admin Tool dialog box.
Projectlocal project settings can be made to tailor the settings for a particular project
within the backup control file. If no change is made at the project level, GLOBAL
settings are used during backup.
- A single-click will list the global attributes and their settings in the Control File
window.
- Double-click to open the Modify Project Backup Info dialog box with the selected
project displayed (in this case GLOBAL).
- GLOBAL should remain as the parameter specification in the TKS File: when
GLOBAL settings are being altered.
- Supply the correct path to the Kingdom project file when specifying the Project
Backup Parameters on an individual basis.
TKS Filedisplays the path to the Kingdom *.tks project file (in this case GLOBAL).
GLOBAL should remain as the parameter specification for TKS File when GLOBAL
settings are being altered.
Browseclick to open a standard Windows Open dialog box in which you can navigate
to locate the TKS file.
Want Backupwhen selected, specifies to include the project for backup. The
GLOBAL setting should always be checked (ON).
This box acts as an ON/OFF switch to control whether the project should be backed up or
not. This is useful if you want to selectively disable some projects, due to size or time
constraints, but keep their settings in the Control File (*.ctl) for back-up at a later date.
- Browseclick to open a standard Windows Open window in which you can navigate
to locate a file to overwrite or replace.
Export Filefile that will contain the backup of the database tables. The name can be
altered, the default is export-day-time-year.dmp
The output name supports four special tags %d, %h, %m, and %y
- Browseclick to open an Open window in which you can navigate to locate a file to
overwrite or replace.
Log Filethis file contains any system messages reported during the backup procedure.
The name can be altered, the default name is log--day-time-year.txt
The output name supports four special tags %d, %h, %m, and %y
- Browseclick to open an Open window in which you can navigate to locate a file to
overwrite or replace.
Backup Typethis field is used to specify the backup type. Currently only
RDBMS_Tables_Only is supported. Future options may include
RDBMS_And_Binary_Files as well as Seismic_Data.
Connectsupply the name of the Server System housing the project database. This
parameter is typically only used with Oracle and SQL Server databases.
If your project database is MS Access, the database should be located locally in the project
directory and have a file extension of .mdb. In this case this parameter is not necessary.
Userspecify the User name associated with the database when it was created. This
should be the same Password and User account supplied when you open the Kingdom
project. Typically only used when Oracle or SQL Server is the Project Manager of the
database.
Password
Specify the Password assigned when the database you wish to open. This should be the
same Password and User account supplied when you open the Kingdom project. Normally
used only when Oracle or SQL Server is the Project Manager of the database.
Frequencyspecify the number of days to check for a change in file dates before doing a
backup of the project database.
Parameter Specification:
Frequency can be specified in days or hours (i.e., 48 hours, 2 days).The Unit name must be
specified there is no default.
Type: Integer
Example
A frequency of 3 days means:
Back up the project if it has changed in the last three days; otherwise, (i.e. the
project has not been altered in 3 days) ignore this project.
Click OK to Modify the parameters and return to the DataBase Administration
Utility tool with the current.ctl file open in the Control File window.
Click Cancel to close the dialog box without saving any of your changes.
The Control file should still be open in the window from the previous step when we edited
GLOBAL and Project settings.
1. Select menu Backup Tool > Control File > Merge. This will display the Open Folder
dialog box.
2. Select the folder where projects to be backup are stored and click OK.
3. In the Project Report dialog box, select projects that are not required in the Projects list:.
to remove or add a single project from the list, hold down the <Ctrl> key and select a
single file from the list.
to remove or add multiple projects to the list, hold down the <Shift> key and select a
first and last file from the list.
4. Click Add.
5. Now the Project tree in the myControlFile.ctl window is populated.
All projects use parameters in the Global unless modified individually. To modify any
parameter for an individual project, double click the project from the Project tree and
modify it and close the dialog box.
6. Close the myControlFile.ctl window, and save it.
Where the <Path> is the complete path to the control file. For example E:\TestData\.
4. To verify projects that are scheduled for backup in the Control File, open the project
folder and check to see if the exported dump file exists in the folder.
Note: DBADMIN can also be executed from a batch file containing the following command:
C:\Program Files\KingdomSuite\TKSv#\dbadmin.exe /backup <mypath>
smtbackup.ctl
The batch file can be scheduled using the windows Scheduled Task utility to run at
scheduled times.
For data transfers to and from Kingdom projects using the OpenSpirit Data Connector and
Tunnel O or OpenSpirits CopySync (now available for Kingdom to Kingdom data transfer
through Kingdom Data Management), you must first specify some settings in DBAdmin.
These settings direct OpenSpirit to the required Kingdom files and directories.
Requirements
Note: The port number links to the specific OpenSpirit version/build installed on the server.
Workflow
The setup workflow for the OpenSpirit and Kingdom Data Server is as follows:
1. Install the OpenSpirit Client on your computer. See Installing OpenSpirit Components
in the Kingdom Software Installation Guide.
2. Install the Kingdom version that is compatible with OpenSpirit.
3. In the Database Admin Tool window, choose OpenKingdom from the main menu bar.
In the Database Admin Tool window, choose OpenKingdom > Set Installation Directory
to specify the installation directory for Kingdom. This operation lets the OpenSpirit software
know where Kingdom is installed.
If the Kingdom software is NOT installed in a default folder, you must enter the path to the
folder in the Folder Location text field, or Browse to the folder location.
In the Database Admin Tool window, choose OpenKingdom > Project Seismic File
Locator to specify the seismic file/data storage location for individual project(s), and where
the CopySync tool in OpenSpirit will place data.
The Project Seismic File Locator dialog box contains the following elements:
1. Select the Data Type
- Data Typealways SeismicDataFolder.
2. Select TKS Project for Seismic File Catalog
Note: The Root Folder list is a priority-ordered list. The first folder in the list has the highest
priority, which means seismic data for the project are stored in the folder that is first in
the list. If the specified maximum capacity (Set High Water Mark) of the folder is
reached, the remainder of the seismic data/files are stored in the second file folder, and
so on with succeeding file folders in the list.
6. Set High Water Markallows you to specify the percentage of the total storage capacity
of a folder that can be used to store the data. You can select a folder in the list, select the
high water mark, then click Update to keep your setting for this folder. The Update
button is associated with the folder name you highlighted in the folder list, which means
the High Water Mark for only the selected folder will be set to the percentage specified.
OKclick to create a SeismicDataFolderCollection.xml in a Config sub-folder under
the project specified in the Select TKS Project for Seismic File Catalog area.
Note: You can specify the seismic data/file location for a project only once. However, if you
have several projects for which you need to specify seismic data/file locations, you can
return to the Project Seismic File Locator dialog box and perform repeated
operations.
Note: The path displayed in Global Seismic File Catalog Path cannot be changed.
Note: The Root Folder list is a priority-ordered list. The first folder in the list has the highest
priority, which means that a project seismic file catalog is stored in the folder that is
first in the list. If the specified percentage of the total capacity (Set High Water
Mark) of the folder is reached, the remainder of the seismic file catalog is stored in the
second file folder, and so on with succeeding file folders in the list.
Set High Water Markallows you to specify the percentage of the total storage
capacity of a folder that can be used to store the data. You can select a folder in the list,
select the high water mark, then click Update to keep your setting for this folder. The
Update button is associated with the folder name you highlighted in the folder list, which
means the High Water Mark for only the selected folder will be set to the percentage
specified.
- OKclick to create a SeismicFile CatalogCollection.xml in a Config sub-folder
under the project specified in the Select TKS Project for Seismic File Catalog area.
Note: You can specify the seismic data/file location for a project only once. However, if you
have several projects for which you need to specify seismic data/file locations, you can
return to the Project Seismic File Locator dialog box and perform repeated
operations.