1. Remote and Replication Manager Administration Guide
  2. Backing Up and Recovering the Siebel Enterprise Server

Backing Up and Recovering the Siebel Enterprise Server

To back up the entire Siebel database or user schema, you can use an RDBMS tool that a third-party supplier provides. You must take some precautions, such as not backing up the docking folders. After moving the Oracle database to a new machine, follow the solution outlined below.

The Oracle Database Administrator (DBA) might decide to move the Oracle database from machine A to machine B for several reasons.
  • If this is a planned move, then the instructions in this topic should be tested in a test environment first and a backup should be taken before a production move.
  • If this is an unplanned move, for example, for disaster recovery of the Oracle database, follow the same steps.

The Siebel Administrator and Oracle DBA have two options for pointing the Siebel Server(s) and dedicated clients to the new database.

  • Option 1: Only update the SQL*net TNS alias
  • Option 2: Create a new TNS alias

Option 1: Only update the SQL*net TNS alias

If the TNS alias name doesn't need to be changed, then only the connection details -- most likely the HOST and SERVICE_NAME (or SID) -- need to be updated. The following tnsnames.ora file is for information only. Oracle recommends that changes to the tnsnames.ora be made using the Oracle-supplied Net Manager Tool. Note that the DBA can provide the new settings.

Change:

SiebelDB.SIEBEL.COM = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = machineA)(PORT = 1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = SiebelDB) ) )

to: 

SiebelDB.SIEBEL.COM = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = machineB)(PORT = 1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = NewSiebelDB) ) )

Option 2: Create a new TNS alias

If a new TNS alias needs to be created, then you must do the steps outlined here.

  1. Create the new TNS alias using the Oracle-supplied Net Manager Tool.
  2. Change the appropriate Configuration (CFG) file to reference the new TNS alias created in the above step.
  3. In the [ServerDataSrc] section, change the value of the ConnectString parameter to the new TNS alias.

    Make this change for all the dedicated client CFG files and all the CFG files in the SiebSrvr\bin directory (version 6.x) or SiebSrvr\bin\<lang> (version 7.x).

  4. Change the Siebel Servers ODBC Data Source Name (DSN). Change the Server Name entry to use the new TNS alias using the ODBC Data Source Administrator on the machine where the Siebel Server is installed. The System DSN is in the format of SiebSrvr_<EnterpriseName>.
  5. Change the ODBC Data Source Name (DSN) for any dedicated clients.
  6. Change the Server Name entry to use the new TNS alias using the ODBC Data Source Administrator on the machine where the dedicated client is installed. The User DSN is in the format of SEAW <InstallationDirectory>. The Siebel Server will need to be stopped and restarted for this change to take effect.
  7. For Siebel 7.x and above, update the gateway configuration information. By default the Object Managers no longer read the CFG files for the database connect string (see the OM parameter, OM - Read Configuration From Server Component Parameters). Therefore, the gateway configuration for that enterprise must updated to reflect the new TNS alias. The commands to use are below, but first, Siebel administrators must back up the Siebns.dat, either manually by copying the file or using the SRVRMGR backup nameserver command, for example: SRVRMGR> backup nameserver SRVRMGR> change parameter DSConnectString=<new TNS alias> for named subsystem ServerDataSrc.
Change the ODBC Data Source Name using the client GUI:
  1. Navigate to View > Site Map > Server Administration > Enterprise Configuration. (version 7.x) or View> Site Map > Administration – Server Configuration > Enterprises (version 8.x).
  2. Select the Enterprise Profile Configuration tab (version 7.x) or Profile Configuration tab (version 8.x).
  3. Select ServerDataSrc in the top list applet.
  4. In the lower applet, find the DSConnectString and change its value to the new TNS alias.

    The Siebel server will need to be stopped and restarted for this change to take effect.

Note: The TNS alias is listed in the Siebns.dat twice. DSConnectString, which is used to connect to the database and is modified as above DatabaseConnStr (which is only used during the installation process to create the ODBC data sources). Users can't change this value directly using SRVRMGR or the GUI, but they can modify the ODBC DSN (see previous steps).