Professional Documents
Culture Documents
Copying A Siebel Sample DB To A Server DB
Copying A Siebel Sample DB To A Server DB
Sample DB to a
Server DB
Copying a Siebel Sample DB to a Server DB
Table of contents
2. Introduction..................................................................................................................................................................... 3
3. Requirements .................................................................................................................................................................. 4
5. Further Considerations.................................................................................................................................................. 10
7. References ..................................................................................................................................................................... 12
1. Document History
1.x
2. Introduction
A lot of Siebel proposals are backed up by a sample application. Most of the time it is developed on a local or
sample database on a laptop. Sometimes the question is raised if it is possible to put this sample application on a
server, so we can host it for a client, or for other reasons. Migrating all the data and configuration by hand can be a
tedious task.
There is no official Siebel supported way, but it is possible. It is recommended to only do this for so called
sandbox environments and should never replace a dev2prod! Never touch DEV, TEST or PROD environments
with the tools mentioned in this document.
We also have to warn that we haven’t tested the full functionality of a Siebel server after copying a Sample
database to it. So far we have tested if it was possible to connect to the server with the web client and change data.
A fuller overview of functionalities that do or don’t work might come in later revisions of this document.
3. Requirements
This document will only show you how to copy the sample database to a server database. This document will not
show you how to install a Siebel Server or Client.
The actual sample database that needs to be copied can be copied over to the server in the appropriate client
directory.
If you have installed a client and sample database on the server, it will have created the ODBC connection to the
sample client database.
You can check the name of the ODBC in the DataSources (ODBC) program.
Click Start -> Programs -> Administrative Tools -> Data Sources (ODBC).
Now you can note the name of the ODBC to the client sample database.
If you don’t see something like “SEAW Samp Db C:/sea752/client” you probably aren’t the user under which the
client sample database has been installed. Please login with the user that has the client sample database installed.
Open the command prompt and change the directory to the one on your server.
You can bypass this step, but than you have to add the path in front of “dataexp”.
If you execute “dataexp” without parameters, you will get the help file.
The /U parameter is for the username. It is recommended to use SADMIN for this task,
The /P parameter is the password for the user specified with /U.
The /C parameter should contain the name of the ODBC to the client sample database. We used quotes as there
were spaces in the name.
The /D parameter is the name of the Siebel table owner.
The /F parameter specifies the name and path of the export file. This file will be later used with DataImp.
The /K parameter allows use of wildcards for selecting the tables.
If you have correctly filled everything, you will be presented with a prompt that asks you the name of the table to
be exported.
Here we fill in the wildcard “%” and this will export all tables. Remember we enabled wildcards with the /K
parameter.
After a while all data will be exported to the file specified with the /F parameter.
If you have installed the Siebel application server on the server, it will have created the ODBC connection to the
server database.
You can check the name of the ODBC in the DataSources (ODBC) program. (See 4.1)
Click on the “System DSN” tab to see the name of the ODBC to the server database.
In this case it is “Siebsrvr_CRMESSAMP”. Now we have enough information to import the sample data.
Open the command prompt and change the directory to the one on your server.
You can bypass this step, but than you have to add the path in front of “dataexp”.
If you execute “dataimp” without parameters, you will get the help file.
The /U parameter is for the username. It is recommended to use SADMIN for this task,
The /P parameter is the password for the user specified with /U.
The /C parameter should contain the name of the ODBC to the server database. If there are spaces in the name, use
quotes.
The /D parameter is the name of the Siebel table owner.
The /F parameter specifies the name and path of the import file. This should be the same name as used with
DataExp.
The /H parameter controls the way to handle errors. Default it will “Abort”. We used “Log”, but we ended up with
a log file of almost 500MB! Perhaps it is better to use “Count”.
For performance reasons you might want to experiment with the /X and /N parameters.
In our case the import took considerable longer than the export.
You might want to copy the filesystem of the sample database to the filesystem of the server database. We haven’t
tested it, so we can’t tell if it works.
The users are not automatically created. Talk to your DBA or refer to the documentation of your database.
SADMIN should be available, so there is no immediate need for creating users.
5. Further Considerations
Some data in the sample database is duplicate with a vanilla server install. For instance, a vanilla install already
has some responsibilities defined. If the process wants to import this duplicate data, an error is observed caused by
a unique index violation.
This is correct behaviour, as we only want the extra information stored in the database.
However, there seems to be an exception to this. All tools related data is being imported. Although we are pretty
sure that this is duplicate data, somehow there are no unique index violations. This might be caused by the
difference in ROW_ID or Name for the Repository itself. This means that it is not recommended to use this
environment to develop a new SRF. Further investigation is needed for a full resolution.
If you still need this environment also as a playground to test new things in Tools, there are four ways to consider.
First you can have DataImp empty all tables before importing the data with the /T parameter. But we can’t tell you
if this would delete too much.
Second way is exporting the repository before you import the data. After the import, rename the repository and
import the repository from before the import. But we don’t know if the newly imported tools data is affected by the
rename of the repository and will no longer be causing any problems.
Third way would be to explore the use of an input file. Suspicion is that you can control what tables are affected by
putting them in a text file. As DataImp and DataExp are not supported by Siebel, there is little information
available on this.
You can look at the file “seed.inp” in dbsrvr/enu for an example.
The fourth way would be to check if you can do an exprep on a sample or local database and import the resulting
file into the server.
6. Useful Links
7. References
[1]
[2]
[3]
[4]
[5]
[6]
[7]