The person doing this configuration must also have access to all
DBMSs used by LANDesk,
and they must have security permissions to create database links
and perform configuration steps at a DBMS server level.
Oracle rolling to Oracle
Configure the Oracle database
The TNSNames.ora file on the database server in which your
rollup database exists must contain an entry for your core server
database.
For an Oracle database, within the Enterprise Manager
Console, log in to your database. Expand Distributed.
From the Database Links item's shortcut menu,
click Create.
In the Name field, enter a name for your
database link.
Note: If the AR database is using Oracle9i, the link name can be
any name that is not already in use or reserved. The installation
will prompt you for this information.
Choose Fixed User and enter the username and
password for the core server's database.
In the Service Name field, enter the
TNSNames.ora (i.e., Net Alias) entry that refers to your core
server database.
Click Create.
Double-click your newly-created link and click
Test. You should get a message that says your link is
active. You can also test your link by logging into the rollup
database and issuing the following command:
Select count(*) from computer@linkname;
If the return is a count of devices in the core server's production
database, then the link is configured properly.
SQL Server rolling to SQL Server
Configure the SQL Server database
Creating links with SQL
Open SQL Server Management Studio.
Expand your server and expand Server
Objects.
From the Linked Servers item's shortcut menu,
click New Linked Server.
On the General page, do steps 5-11:
Linked Server: enter a unique name for this
database link (for example, LDMS core server1 Link).
Choose Other data source.
Select Microsoft OLE DB Provider for SQL
Server.
Product name: Enter LDMS.
Data source: enter the name of the database
server containing the core database.
Provider string: enter the provider string.
For instance:
SQL Server
provider=SQLOLEDB.1;user id=<User for the core server’s
database> ** The user id portion of the provider string is required on the
connection string to another SQL Server database. **
Catalog: enter the physical name of your core
server’s database (for example, lddb).
On the Security page, select Be made using
this security context and enter the username and password for
the core server’s database, then click OK.
Click New Query and issue the following
command:
Select count(*) from [Link name].[database name].[table-owner
name].Computer
Using the values above, this query would appear as:
Select count(*) from [LDMS Core Server1
Link].[lddb].[dbo].Computer
If the correct count comes back, your link is set up
correctly.