Siebel Life Sciences Guide > Importing Data into Life Sciences > Extracting Data for Mobile Users >

Performing a Data Extraction

Use the following procedure to preform a data extraction.

To perform the data extraction

1. In the siebel_server\BIN directory, run the Syndexp.exe executable file.

   Use the command line arguments listed in Table 24 to define multiple variables that are specific to the user environment. For example:

   syndexp /U sadmin /P <password> /D phdemo /E "Rule One" /C siebsrvr_siebel

   NOTE:  Interruption of the extraction process at any point causes the system to fail and necessitates restarting the data extraction from the beginning.

2. If an interruption occurs, you must go into the Pharma Node Attachment Administration view (navigate to the Syndicated Data Files view) and delete the previously generated data files. You also must go into each node and delete the latest file that was created in the previous run.

   After the program executes the Syndicated Data Loading (SDL) process, it displays the name of the user whose data is being extracted. This process continues until it has completed the extraction process for each user defined in the Syndicated Data Export Rules.

3. After you successfully complete the extraction process, you can create a batch file for use with subsequent extractions.

   The extracted files are output in a compressed form to minimize file transfer time. Files are transferred using Siebel Remote, which is described in Siebel Remote and Replication Manager Administration Guide. After mobile users receive their extracted files, they must import the data into their local databases.

Full and Partial Data Extracts

Because syndicated data loading does not use EIM to maintain synchronization between the server and the remote databases, you must force a resynchronization step at the end of each direct load. Force resynchronization either by re-extracting an entirely new remote database for each mobile user or by performing a partial extract that includes only the refreshed syndicated data. A new, full database extract creates a database snapshot file for a given mobile user. A partial extract contains only S_SYND_DATA table data.

Some users receive syndicated data updates once a week, while some might receive syndicated data updates monthly or quarterly. Therefore, partial extract is preferred.

Possible Data Loss

Sometimes remote users connect to Siebel Server using unstable dial-up connections that prevent the data file from being transferred correctly, so that the data file does not reach the remote server. Siebel Server does not verify that the data file reached its destination successfully. At the end of the transfer step, Siebel Server removes the data file from the server.

In the case in which a data file is lost and removed from the server, you must extract a new data file for users.

CAUTION:  The loss of data or files can occur without warning. You might not be able to automatically determine the success or failure of a particular transfer. As a result, sales representatives might be using incorrect data for up to several months without realizing it.