SAP MDM Books:SAP NetWeaver MDM 7.1 for Functional Consultants

SAP NetWeaver MDM 7.1 for Functional Consultants

SAP MDM Books : Enterprise Master Data Management using SAP Netweaver MDM

Enterprise Master Data Management using SAP Netweaver MDM

SAP MDM Books :Enterprise Data Management with SAP NetWeaver MDM

Enterprise Data Management with SAP NetWeaver MDM

SAP MDM Books: Effective Master Data Management with SAP NetWeaver MDM

Effective Master Data Management with SAP NetWeaver MDM

CLIX ERRORS

Common CLIX errors are listed in Table 112.

Table 112. Common CLIX Errors

388
MDM Console

Number Message Explanation / Probable Cause 0x83000002 WinSock error on connect MDM Server is not running. The CLIX Client could not connect. 0x80020002 Error opening file File specified does not exist, or argument not in quotes. 0x80010004 Already exists Target file or repository already exists (use –FORCE option to override). 0x8001000d Directory already exists Target file same as an existing directory. 0x80020002 Error opening file Source Archive File not found; mistyped or lacking full path or needing quotes. 0xFFAB4010 The repository is invalid Source Repository was mistyped, not in quotes, or not mounted on MDM Server. 0x8402000B Repository already exists Target repository cannot be overwritten unless –FORCE option is added.

DBMS Settings

DBMS Settings

The applicable brands for each DBMS setting are listed in Table 113.

Table 113. DBMS Settings and Brands

NOTE ►► See “DBMS Settings” on page 234 for more information on

the DBMS settings.

DBMS COMMANDS

CLIX dbGetDBMSSetting MDMHostSpec DBMSHostSpec [-D]

Display all the DBMS settings for that DBMS instance. These vary

according to DBMS brand. See below for a table of settingNames that

you are likely to encounter.

MDM Console
387

Part 14: CLIX Command Line Interface

CLIX dbInitialize MDMHostSpec DBMSHostSpec [-D]

Initialize a DBMS for use with an MDM Server. This is the first thing you

should do with a DBMS instance that you wish to use for the storage of

MDM repositories.

CLIX dbList MDMHostSpec DBMSHostSpec [-D]

Display a list of repositories that are stored on the DBMS instance.

Mountable repositories are listed first, then unavailable (unmountable)

repositories.

CLIX dbChangePass MDMHostSpec DBMSHostSpec newPassword [-D]

Change the DBMS password for access to all repositories on a

particular DBMS server. Valid only for Oracle; passwords for other

brands should be changed with the applicable DBMS tools.

CLIX dbSetDBMSSetting MDMHostSpec DBMSHostSpec

settingName=value [-D]

Modify one of the DBMS settings for the DBMS instance listed from the

dbGetDBMSSetting command. The settingName must be entered

exactly.

REPOSITORY COPYING COMMANDS

CLIX cpyArchive MDMHostSpec RepositorySpec [-A filename]

[-S segSize] [-F] [-N] [-O] [-D] [-XS] [-XSOVT]

Saves an MDM repository to an .a2a archive file. Use –A to specify the

filename rather than accept the MDM Server generated filename. Use –

S to split the file into smaller segments; segment size is suffixed with ‘K’,

‘M’, or ‘G’ to specify kilo-, mega-, or gigabytes respectively. Use the –F

flag to force the overwriting of an existing .a2a archive file. Use the –XS

flag to create a schema-only archive. Use the –XOVT flag to exclude

originals (O), variants (V) and thumbnails (T) from the archive (any

combination of O, V, and T is permitted, such as –XV to exclude only

variants).

Normally CLIX will wait until the MDM Server completes the archive

operation; use the –N flag to return immediately, leaving the archive

activity to run in the background. If you do so, you can check the status

later with the mdsInfo command.

386
MDM Console

CLIX Commands

CLIX cpyDuplicate MDMHostSpec sourceRepositorySpec

targetRepositorySpec Credentials [-Pn] [-F] [-N] [-O]

[-D]

Duplicate a mounted MDM repository to a new repository. You can

overwrite an existing target repository by using the –F flag. Use the –N

flag to perform the operation asynchronously. Use the –P2 or –P4 flags

to specify 2 or 4 storage partitions rather than the default of 1.

CLIX cpyInfo MDMHostSpec [-D]

Whenever a cpyArchive command completes, the MDM Server

surveys and analyses every .a2a file in the MDM Server archive

directory. This command lists the contents of that report file.

CLIX cpyListArchives MDMHostSpec [-D]

Returns a list of the files in the MDM Server archive directory. You can

then choose one of these as the filename for the repUnarchive

command.

CLIX cpySlave MDMHostSpec sourceRepositorySpec

slaveRepositorySpec Credentials [-Pn] [-F] [-N] [-O]

[-D]

Duplicate a mounted MDM repository to a new repository and modify

the new repository to be a slave repository. You can overwrite an

existing target repository by using the –F flag. Use the –N flag to

perform the operation asynchronously. Use the –P2 or –P4 flags to

specify 2 or 4 storage partitions rather than the default of 1.

CLIX cpyUnarchive MDMHostSpec RepositorySpec filename [-Pn]

[-F] [-N] [-O] [-D]

Creates an MDM repository from an .a2a archive file specified by

filename. Use the –F flag to force the overwriting of an existing

repository by the same name on the same DBMS instance. Use the –N

flag if you wish to perform the processing in the background rather than

have CLIX wait until the operation finishes. Use the –P2 or –P4 flags to

specify 2 or 4 storage partitions rather than the default of 1.

Activity Monitoring Commands

You can monitor the activities currently being processed for a specific

repository on an MDM Server by using the repMonitor command.

This command works exactly like the mdsMonitor command, except

that the information it outputs is limited to the specified repository (see

“MDS Activity Monitoring Command” on page 381 for a complete

description of the information output by the repMonitor command ).

Otherwise, you can use the repIsAvailable command to find out if

certain long-running activities are running on a specified MDM

repository. This command checks whether the repository is busy with

any of the following operations:

•

•

•

•

•

•

•

Archive repository

Copy/Duplicate repository

Create Slave repository

Import records

Check In records

Check Out records

Roll Back records

If any of the above activities are running on the repository, the

command output will be busy. Otherwise, the output is available.

Master/Slave Commands

You can use the repShare command to make a slave repository

“shareable” so that multiple MDM Servers can load it. Conversely, you

must use the repExclusive command to return the slave to an

unshared state before synchronizing it, so that a single MDM Server can

issue the synchronization command.

An alternate method is to leave the slave shared and loaded, then:

1.

2.

3.

4.

Create a new slave from the Master.

Make that new slave “shareable.”

Load the new slave without ports in the background using the

repPreload command on each MDM Server that acts as a host.

After each host completes the background load, use the repSwap

command to swap the new slave for the old on the same port.

REPOSITORY CONTROL COMMANDS

CLIX repCancelUnload MDMHostSpec RepositorySpec [-D]

Cancels a repository’s pending Unload command.

CLIX repCheck MDMHostSpec RepositorySpec Credentials [-O]

[-E1 | -E2] [-N] [-D]

Verifies an MDM repository, but makes no repairs. It returns an error if

any fatal errors exist. If –E1 or –E2 is provided, an error is returned if

there are any non-fatal errors or warnings, respectively.

382
MDM Console

CLIX Commands

CLIX repCreate MDMHostSpec RepositorySpec port [-Pn] [-F] [-D]

Creates and mounts an MDM repository. The port must be in the range

2000-9999. Use the –P2 or –P4 flags to specify 2 or 4 storage partitions

rather than the default of 1. The –F flag will force the new repository

over an existing one.

CLIX repDelete MDMHostSpec RepositorySpec [-D]

Deletes an MDM repository.

CLIX repExclusive MDMHostSpec RepositorySpec Credentials

[-O] [-D]

Configures a single MDM repository instance for exclusive use so that

only a single MDM host can distribute and share its data. This is

permitted if the repository is idle (not loaded by any MDM Server) or

already loaded only the by the MDM Server specified by the

MDMHostSpec parameter.

CLIX repFieldsRecalc MDMHostSpec RepositorySpec port [-D]

Refreshes all calculated fields on an MDM repository.

CLIX repGetChangeCounter MDMHostSpec RepositorySpec

Credentials [-D]

Reports the change counter for an MDM repository.

CLIX repGetMasterChangeCounter MDMHostSpec RepositorySpec

port [-D]

Reports the change counter of the specified slave repository’s master

repository.

CLIX repGetMasterInfo MDMHostSpec RepositorySpec port [-D]

Reports the name, DBMS instance name and type, and MDM Server of

the specified slave repository’s master repository.

CLIX repIsAvailable MDMHostSpec RepositorySpec [-T –

TIMELOOP LoopSecs] [-W] [-D]

Checks whether the repository is busy with certain long-running

operations.

CLIX repLoad MDMHostSpec RepositorySpec Credentials [-R]

[-D] [-En] [-W]

Loads a mounted MDM repository. Adding the –R flag forces indices

and accelerators to be rebuilt. With either –E1 or –E2, an error is

returned if the repository is already running/loaded.

MDM Console
383

Part 14: CLIX Command Line Interface

CLIX repMonitor MDMHostSpec RepositorySpec [-D] [-W] [-T

seconds]

Displays information about the current and queued activities on the

MDM Server for the specified MDM repository.

CLIX repMount MDMHostSpec RepositorySpec port [-D]

Mounts an MDM repository. The port must be in the range 2000-9999.

CLIX repNormalize MDMHostSpec RepositorySpec Credentials [-D]

Turns a master or slave repository into a normal repository, permanently

severing any prior master/slave relationship.

CLIX repPreload MDMHostSpec RepositorySpec Credentials [-R]

[-D] [-N]

Loads a mounted MDM repository without opening the communication

port access to it. Intended for use with the catSwap command. The –R

flag forces indices and accelerators to be rebuilt.

CLIX repRepair MDMHostSpec RepositorySpec Credentials [-O]

[-E1 | -E2] [-N] [-D]

Verifies and repairs an MDM repository. It returns an error if any fatal

errors remain. If –E1 or –E2 is provided, an error is returned if there are

any non-fatal errors or warnings remaining, respectively.

CLIX repShare MDMHostSpec RepositorySpec Credentials [-O][-D]

Configures a single MDM repository instance as being shared so that

multiple MDM hosts can distribute its data. This is permitted if the

repository is idle (not loaded by any MDM Server) or already loaded

only by the MDM Server specified by the MDMHostSpec parameter. It is

not permitted if any data altering operation (such as Verify-Repair) is in

progress.

CLIX repSwap MDMHostSpec stoppingRepositorySpec

swapinRepositorySpec [-D] [-W]

Stops a running MDM repository and starts another. If the swap-in

repository has been “preloaded” then this allows it to quickly assume the

stopping repository’s ports. If the second repository has not been

preloaded, this command is equivalent to repLoad and repUnload

commands in combination.

CLIX repSynchronize MDMHostSpec slaveRepositorySpec

Credentials [-D]

Synchronizes a slave repository to its master. An MDM repository that is

shared cannot be synchronized.

384
MDM Console

CLIX Commands

CLIX repTruncateMCL MDMHostSpec RepositorySpec Credentials

[-D]

Truncates a master repository’s Master Change Log. Slave repositories

which are not synchronized with the master repository prior to truncation

will not be able to synchronize afterwards.

CLIX repUnload MDMHostSpec RepositorySpec Credentials [-D]

Unloads a loaded MDM repository.

CLIX repUnlock MDMHostSpec RepositorySpec Credentials

[-M[LMCRNPOADS] [-E] [-D]

Unlocks (appropriates) all activities on an MDM repository. Use the –E

flag to unlock the repository for all MDM Servers. The –M flag followed

by one or more qualifier letters unlocks only the corresponding activities:

L=Load; M=Modify; C=Check; R=Repair; N=New; P=Update;, A=Archive;

D=Duplicate; S=Create Slave.

CLIX repUnmount MDMHostSpec RepositorySpec [-D]

Unmounts a stopped MDM repository.

CLIX repUpdate MDMHostSpec RepositorySpec [-O] [-N] [-D]

Updates a mounted MDM repository

MDS Activity Monitoring Command

The mdsMonitor command outputs information regarding the MDM

activities that are currently being processed by an MDM Server. This

information spans all repositories loaded on the specified MDM Server.

The information displayed by the mdsMonitor command is formatted in

rows and columns, as shown in Figure 111.

S
Locks
Elapsed

ThrId t Username Protocol Command
Data Synch Time,ms Connection Repository

==============================================================================

2160 R Admin
MDSAdmin VerifyRep
SS
--
7440 MDM Console XYZ_BP

2622 W ATran

6507 R

CatMgr

Itsam

ImportRecords

GetActivityIn

- X* - -

-- --

5234 MDM Data Ma XYZ_BP

0

Figure 111. Output from the mdsMonitor command

Each row of output data represents a single command being processed

by the MDM Server. Each column contains information about the

current state of that command, as described in Table 111.

Table 111. mdsMonitor Columns

1

Only displayed when –W flag is added to the mdsMonitor command.

MDM Console
381

Column Description ThrId Thread number of the MDS activity processing the command St The current state of the command: W -- Waiting for a lock R -- Running Username The MDM user that issued the command Protocol The MDM internal protocol used to access the MDM Server Command The command or MDM Server method currently being processed. Locks Lock information is displayed in the format AB CD, where: A describes the state of the MDM Server data lock. B describes the state of the MDM Repository data lock. C describes the state of the MDM Server synch lock. D describes the state of the MDM Repository synch lock. The possible states for a lock are: -- No lock requested - -- Share lock requested S* -- Share lock acquired S -- eXclusive lock requested X* -- eXclusive lock acquired X Elapsed Time Elapsed time in MS since the activity started. Connection The MDM client application which triggered the command request. Repository The MDM repository for which the command was requested 1 Remote Host If the command was triggered by an MDM client application, the name of the machine on which the MDM client application is running.

Part 14: CLIX Command Line Interface

With mdsMonitor you can quickly view the activities on an MDM

Server and identify any performance bottlenecks in your system.

Figure 111, for example, shows that the user “Admin” issued a

VerifyRep command for the repository XYZ_BP. The VerifyRep

command acquired shared server and repository data locks, and the

operation has been running for 7440 milliseconds.

It also shows that user “ATran” launched an ImportRecords operation

on the same repository, and that this operation has been waiting 5234

milliseconds for an exclusive data lock before it can begin.

TIP ►► The standard output of the mdsMonitor command is limited

to a width of 80 characters. If you issue the command with the [–W]

flag, the output is expanded to a width of 120 characters. With the

wider output, MDM adds the Remote Host column and relaxes the

cutoff limit for displaying name data in a column.

NOTE ►► mdsMonitor output is provided as a “snapshot” but can

be refreshed every certain number of seconds if the command is

issued with the [-T seconds] flag. Some commands may be

requested, executed, and completed within this interval and so will not

appear in the output.

NOTE ►► Only information regarding data locks and synchronization

locks is displayed in the Locks column. Information about locks used

by other MDM activities is not currently shown.

NOTE ►► The mdsMonitor command is itself reported as the

GetActivityIn command in the mdsMonitor output.

NOTE ►► mdsMonitor output changed from MDM 7.1 to MDM 7.1

SP2 to make it more readable. This section describes the updated

format.