Monitoring and Reporting for Siebel Remote

This chapter describes how to monitor operations and how to access reports for Siebel Remote. It includes the following topics:

Monitoring and Logging for Siebel Remote

This topic describes how to monitor the status of the remote client and operations on the Siebel Server for Siebel Remote. It includes the following information:

Naming Conventions for Log Files

This topic lists naming conventions for server components and their associated log files on the Siebel Server and the remote client.

Log Files on the Siebel Server

The Server Components That Siebel Remote Uses topic describes server components and the associated log files that Siebel Remote creates in the following folder:

On Windows, in the SIEBEL_ROOT\log folder on the Siebel Server. For example, C:\siebel\ses\siebsrvr\log.
On UNIX, in the /siebel/ses/siebsrvr/enterprises/enterprise_name/server_name/log folder on the Siebel Server.

These files include information that various server components create for SQL based events. The task Id is the identification number of the server task that created the log file. For example, TxnProc_7204.log.

For more information about:

Generating log files, see Configuring Traces for a Server Component.
An example log file, see Example Log File for Transaction Merger.
Other information sources, see Information Sources for Tracing.

Log Files on the Remote Client

Siebel Remote uses two naming conventions with log files on the remote client. The program log file names are Siebel.log or UpgWiz.log.

The name of the log file for the process or task is Syncthrd_123_456.log, where:

123 is the Id of the process.
456 is the Id of the task.

The location of the log file, such as the SyncThrd log file, is as follows:

If you set SIEBEL_LOG_DIR to SIEBEL_LOG_DIR=dir, then Siebel Remote creates the log file in the folder that the dir parameter specifies. Make sure this folder exists and permission to write a file in that location exists.
If no SIEBEL_LOG_DIR is specified, then Siebel Remote creates the log file in the SIEBEL_CLIENT_ROOT\log folder.

Automatic Notification of Critical Conditions

A critical condition might occur during processing on the Siebel Server that is related to the Transaction Router, Transaction Processor, or Transaction Merger. You can configure the Siebel Server so that if one of these conditions occurs, then the Siebel Server creates a notification alert and automatically sends an email message to you. The purpose of this notification alert is to reduce the amount of time that is required to detect and reply to these problematic conditions. The following conditions can create this notification message:

A server component fails to start.
A typical system failure occurs, such as the component failing or exiting abnormally.
The Siebel Server cannot write event logs because no more disk space is available on this server.
Siebel CRM reaches a critical throughput threshold for Siebel Remote during the Monitor Data Calculate Period, which is the number of transactions that occurs in a time period that you specify. This period can include the following items:
- Visible event transactions. Transactions that affect the amount of visible data and who can view that data, such as the addition of an Account.
- Position rule transactions. Visible event transactions that affect who can view specified data, such as assigning a user to an Account.
- Combined transaction types.
- Routing throughput of the Transaction Router.

To configure the email notification alert, you define the Monitor Data Calculate Period and other alert notification settings. For more information, see Siebel System Administration Guide.

Monitoring the Transaction Backlog

The Transaction Backlog view displays information about the number of Siebel Remote transactions that Siebel Remote backlogs. A backlog is a set of transactions that is waiting for the Transaction Router to route them. The Transaction Backlog view includes a count for each of the following items:

The number of backlogged transactions that exist in the Siebel Enterprise
The number of backlogged transactions that exist on a server, which includes users with waiting transactions that reside on the Siebel Server that you choose
The number of backlogged transactions that exist for a user on the Siebel Server. You can specify the user.

Backlog information is available for all Siebel Servers in the Siebel Enterprise, for an individual Siebel Server, or for an individual user.

For more information, see About the Siebel Enterprise and the Siebel Enterprise Server, and Troubleshooting a Large Transaction Backlog Problem.

To monitor the transaction backlog

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Monitor the combined transaction backlog for users in the Siebel Enterprise:
1. Navigate to the Administration - Siebel Remote screen, and then the Transaction Backlog view.
2. In the Enterprise form, click Calculate Backlog.
  The number of backlogged transactions displays. This number is the sum of the individual server backlogs.
Monitor the transaction backlog for a Siebel Server:
1. Navigate to the Administration - Siebel Remote screen, and then the Transaction Backlog view.
2. In the Servers list, choose the Siebel Server you must monitor, and then click Calculate Server Backlog.
Monitor the transaction backlog for a user:
1. Navigate to the Administration - Siebel Remote screen, and then the Transaction Backlog view.
2. In the Users list, query the User ID field for the user ID of the user you must monitor, and then click Calculate Mobile Client Backlog.
  To determine the count of backlogged transactions for a user, Siebel Remote calculates the pending transactions that are not yet routed. This might include transactions that are visible to the chosen user but are not routed to that user.

Monitoring Various Transaction Logs

This topic describes how to use the Administration - Siebel Remote views to monitor transaction logs. It includes the following information:

Monitoring Transaction Logs

This topic describes how to monitor transaction logs.

To monitor transaction logs

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Transaction Log view.
The Transaction Log list displays information about each transaction.

Examine fields in the Transaction Log list using information from the following table.

Field	Description
Node Number	ID of the node that created the transaction.
Operation	Type of transaction completed, indicated with a letter. For example, Insert (I), update (U), delete (D), and so on. For more information, see the table in the topic Operation Types for the Operation Field of the Transaction Log List.
Item	Table name of the transaction.
File Flag	Flag to indicate if the transaction is on a file attachment related table.
Transaction ID	Sequence number of the transaction.
Transaction Row ID	ROW_ID of the transaction.
Transaction Updated	Timestamp of when Siebel Remote last updated the transaction.

Examine fields in the Detail form, using information from the following table.

Field	Description
Transaction Updated by	ROW_ID of the user who last updated the transaction.
Transaction Conflict ID	ID of the conflict for the base table record.
Transaction Mod ID	Version number of the base table record.
Visibility Level	Visibility event level for the transaction: Enterprise (E), or Limited (L).
Visibility Event	Indicates if the transaction is a visibility event.
Related Visibility Event	Indicates if the transaction is a related visibility event.
Dock Object Code	Dock object code of the transaction instance.
Primary Table Row ID	ROW_ID of the Primary table for the instance of the dock object.
Length (Long Log data)	Real length of the long column of the transaction data.
Log Data 1, 2, 3, 4, long	These fields hold transaction data.

Monitoring Transaction Logs by Operation

This topic describes how to monitor transaction logs by operation.

To monitor transaction logs by operation

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.

Navigate to the Administration - Siebel Remote screen, and then the Transaction Log By Operation view.

The fields in the Transaction Log By Operation view display information about the number of transactions for each operation, as described in the following table.

Field	Description
Operation	Type of the operation.
Number of transactions	Total number of transaction for the operation type.

Monitoring Transaction Logs by Node

This topic describes how to monitor transaction logs by node.

To monitor transaction logs by node

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.

Navigate to the Administration - Siebel Remote screen, and then the Transaction Log By Node view.

The fields in the Transaction Log By Node view display the number of transactions for each node, as described in the following table.

Field	Description
Node Name	remote client node name.
Number of transactions	Total number of transactions for the operation type.

A node is a remote client or a regional server. This view only displays transactions from users and regional nodes. It does not include transactions that a person creates who is not a user who connects directly to the Siebel Server.

Monitoring Transaction Logs by Table

This topic describes how to monitor transaction logs by table.

To monitor transaction logs by table

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.

Navigate to the Administration - Siebel Remote screen, and then the Transaction Log By Table view.

The fields of the Transaction Log By Table view displays the number of transactions for each table in the server database, as described in the following table.

Field	Description
Item	Table name.
Number of transactions	Total number of transactions for the operation type.

Support for Fields That Include the CLOB Data Type

Siebel Remote supports synchronization for database fields that include the CLOB data type. A CLOB field can typically store up to 128K characters. CLOB can increase the maximum transaction size that Siebel Remote can log. The S_DOCK_TXN_LOG table uses a special CLOB field that can store up to 2.25MB of data. A database table can contain up to three CLOB fields. For more information, see Modifying the S_DOCK_TXN_LOG Table.

Monitoring the Status of the Siebel Server

To monitor Siebel Server tasks that are running or that have completed, you can use the Server Manager to view the task state values and statistics. Each state value contains information about the current operation of a server task or the server component where the task is running. The Siebel Server records statistics at the task level for server tasks. When the task finishes, task statistics roll up to the component and server levels.

To monitor the status of the Siebel Server

Use the Server Manager to view the state values and statistics for server components and server tasks.
For more information, see Siebel System Monitoring and Diagnostics Guide.

Configuring Traces for a Server Component

Siebel Remote includes tracing capability for Remote and Replication Manager server components that improves system diagnostics. Trace files track SQL statements that a server component sends. They include some information about the task or function that is in progress.

Configuring Traces for a Server Component by Using an Administrative Screen

This topic describes how to set tracing for a server component by using an administrative screen.

To configure traces for a server component by using an administrative screen

Locate the record for the server component you must trace.
For more information, see Server Components That You Can Use with Tracing and Locating the Record for a Server Component.
In the Events list, choose the Event Type you must trace.
To help determine the Event Type to choose, you can use the Description field. For more information, see Using Event Logging with Server Components.
Set the value in the Log Level field to 4.
The log file for the server component you choose in Step 2 will contain the tracing information.

Configuring Traces for a Server Component by Using a Command Line

This topic describes how to set tracing for a server component by using the command line.

To configure traces for a server component by using a command line

From the Server Manager command line, enter the following command:
```
srvrmgr: change evtloglvl event_type = 4 for server_component_name
```
where:
- event_type is the type of event that the Siebel Server traces
- server_component_name is the name of the server component that the Siebel Server traces
For more information, see Opening the Command Line Interface for Server Manager.

How the Siebel Server Traces a Lock

A lock is a handle that a server component uses to identify the server component that can access an object, such as a DX file that resides in the folder of the Transaction Processor. A lock on the tracing feature displays the reason why the lock is set or released for the server component. A lock in the trace file provides information than you can use to troubleshoot a problem to reduce the contention between critical server components for Remote and Replication Manager.

For example, assume there is a problem with the Transaction Processor. It might be locking an object, such as a DX file that resides in the docking folder but not releasing it. If you set the Log Level to 4 or 5, then the Siebel Server logs information about the lock in the Transaction Processor log file. This functionality applies to the Remote and Replication Manager server components on the headquarters or regional nodes. It is not available to the user. For more information, see Overview of Siebel Replication Manager.

Tracing and logging of locks for server components includes the following objects on the Siebel Server:

Dobjinst.dbf
DX files
Inbox
Outbox
Visdata.dbf

To enable the tracing for these locks, you can use the predefined Siebel event tracing features. The trace level of the server component controls logging. It is not necessary to restart the Siebel Server. For help with reducing contention, see Getting Help from Oracle.

For more information, see Naming Conventions for Log Files.

Server Components That You Can Use with Tracing

You can use the following server components with tracing:

Database Extract
Generate New Database
Parallel Database Extract
Transaction Merger
Transaction Processor
Transaction Router
Replication Agent
Synchronization Manager

For more information, see Server Component Parameters.

Using Event Logging with Server Components

Event logs provide helpful information for diagnosing problems. For example, to log information for the Database Extract server component, you can enter the following command in the Server Manager command line interface:

change evtloglvl GenericLog=5, Trace=5, SQL=5, EVENT_GENERIC_PROFILE=5 for comp dbxtract

start task for comp dbxtract server server_name with Client=client_name, SQLFlags=2, TraceFlags=7

Information Sources for Tracing

The following table describes sources that you can access to get more information about tracing.

Table More Information Sources for Tracing

Source	Description
Siebel System Monitoring and Diagnostics Guide	Describes event logging for server components that Siebel Remote uses.
477897.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 2116.	Describes how to increase tracing for the Siebel object manager.
477162.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 1964.	Describes how to trace navigation and actions of an application user.
477003.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 1894.	Describes how to do SQL based event logging with server components that Siebel Remote uses.
477585.1 (Article ID) on My Oracle Support. This document was previously published as Technical Note 499.	Describes transaction gaps, their causes, and recommendations on how to minimize their impact.
477144.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 1930.	Describes how to trace the Transaction Processor server component and read the corresponding log file.
477002.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 1895.	Describes how to trace the Transaction Router server component and read the corresponding log file.
477138.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 1944.	Describes how to trace the Transaction Merger server component and read the corresponding log file.
477125.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 1943.	Describes how to trace the Database Extract server component and read the corresponding log file.
477132.1 (Article ID) on My Oracle Support. This document was previously published as FAQ 1941.	Describes how to trace the Replication Agent server component and read the corresponding log file.

Configuring Logs on the Remote Client

This topic describes how to set the parameters that control logging on the remote client. It includes the following information:

Temporarily Setting Event Levels

To modify the type of information that Siebel Remote collects, you can temporarily modify the SIEBEL_LOG_EVENTS environment variable.

To temporarily set event levels

Open a DOS window on the remote client computer.
Navigate to the SIEBEL_CLIENT_ROOT\bin folder.
Enter the following command:
```
set SIEBEL_LOG_EVENTS=event_level
```
For more information, see Setting the Event Level.
From the same DOS window you opened in Step 1, log in to the remote client.
For example, enter the following command:
```
siebel /u username /p password /c cfg /d local
```
where:
- username is the name of the user
- password is the password assigned to the user
- cfg is the name and path to the configuration file
- local specifies the local database
For more information, see Locating the Siebel Application Configuration File.

Setting the Event Level

The value for the event level can be between 0 and 5. A higher level collects more detailed information and uses more disk space. If you use the default value of 1, then Siebel Remote collects the minimum amount of information in the trace file. To troubleshoot a problem, you can set the event level to 3 or higher. If you set the event level to a higher value, then make sure sufficient disk space is available.

Using Siebel Audit Trail with Siebel Remote

If your Siebel implementation includes Siebel Audit Trail, then you can view audit trail records for successfully synchronized remote client transactions and other audit trail records, provided that your computer is connected to the headquarters database or to a regional node that includes Siebel Audit Trail.

The headquarters database must audit all of the fields that regional nodes audit. A regional node is not required to audit all of the fields that the headquarters database audits.

If the following requirements are met, then the user who is using the remote client can view audit trail records while using the local database:

Siebel Audit Trail must be functioning correctly on the Siebel Server that Siebel Remote uses to synchronize the remote client.
The remote client must use a local Siebel runtime repository that was published while Siebel Audit Trail is enabled for the correct business components.
To view the audit trail for an audited record, the user must possess visibility to this record.

For more information, see Overview of Siebel Replication Manager and Siebel Applications Administration Guide.

To use Siebel Audit Trail with Siebel Remote

Start a remote client that connects to the headquarters database or a regional node where Siebel Audit Trail is implemented.
Do not use a remote client that connects to the local database of a remote client.
Navigate to the Audit Trail screen, and then the Audit Trail Items view.
Alternatively, you can choose a screen for a business component that uses auditing. For example, you can navigate to the Assets screen, click an asset, and then choose the Audit Trail link.

Use a typical query to locate the record you must modify.

The fields of the Audit Trail Items list display information about the transaction, as described in the following table.

Field	Description
Source	A value of Sync indicates an audit trail record that Siebel Remote created as the result of a transaction that it successfully synchronized.
Date	Displays the date and time that the original transaction occurred on the remote client.
Synchronization Date	Displays the date and time that Siebel Remote synchronized the transaction to the current server.

Viewing Reports

This topic describes how to view reports. It includes the following information:

Viewing Reports for Synchronization Sessions

Oracle provides a number of online reports that display information about Siebel Remote and Replication Manager components and system status. These reports allow you to do the following:

Get information about the Siebel Remote server components and users.
Monitor and manage deployment of Siebel Remote and Replication Manager.
Improve support.
Reduce administrative overhead.

This topic describes views you can access that provide information about the remote status.

Viewing the Remote Status View

The Remote Status view displays information about database updates that the Merger Friendly Notification system preference determines. This view includes the following applets:

Session Summary. Displays synchronizations that occurred since Siebel Remote initialized the last local database.
Session Actions. Displays information of the major actions of the synchronization session. There are typically five major actions.
Session Actions Details. Displays details depending on the activities of the synchronization session.

Siebel Remote archives synchronization details on the local database. It does not store them on the server database:

On the local computer, Siebel Remote displays details of the previous synchronization in the Remote Status view of the User Preferences screen.
On the Siebel Server, Siebel Remote stores details only for the latest synchronization. It displays these details in views in the Administration - Siebel Remote screen.

For more details about system preferences that affect the way Siebel Remote manages database modifications, see Process of Configuring System Preferences for the Siebel Server.

To view the remote status view

In the remote client, navigate to the User Preferences screen, and then the Remote Status view.

Examine fields in the report, using descriptions from the following table.

Applet	Field	Description
Session Summary	Session Date	Timestamp of the beginning of the synchronization.
	Session Status	Result of the synchronization.
	Session Result Summary	Key summary information of the synchronization.
Session Actions	Item Name	Name of major action.
Session Actions	Results Summary	Summary result of the action.
Session Actions Details	Item Type	Type of object, such as Account or Opportunity.
	Item Name	The name of the field.
	Action	The kind of conflict or action.
	Updated By	Self-explanatory.
	Date Updated	Self-explanatory.
	Item Details	Detailed information that describes the work that Siebel Remote completed.

Viewing the Current Siebel Remote Session Report

The Current Siebel Remote Session report provides the following kinds of information about the chosen session:

List of actions completed during the session, such as connecting to server, sending database modifications, retrieving database modifications, or retrieving requested files.
Description of each action completed, including quantities of transactions, operations, and files involved.
Details for action items, where applicable.

This report is available only for the remote client.

To view the Current Siebel Remote Session report

In the remote client, navigate to the User Preferences screen, and then the Remote Status view.
In the Session Summary list, query the Session Date field for the session that you must view.
Click the Reports button.
Choose Current Siebel Remote Session.
Wait for the report to display, and then examine the results.

Viewing Administrative Status Reports

Several predefined administrative status reports are available from various views in the Administration - Siebel Remote screen. The reports provide the following types of information:

Synchronization frequency
Transaction backlog
Transaction Processor usage
Mobile users usage

These reports are accessible only to you except for the Client Status report. If the user responsibility includes the Client Status view, then the Client Status report is available to the remote client. For more information, see Siebel Applications Administration Guide.

To view administrative status reports

In the remote client, navigate to the Administration - Siebel Remote screen.
For example, you might require reports from the Synchronization Sessions view.
Choose the view tab that contains the report you must view.
For example, to view a report for synchronization sessions, choose the Synchronization Sessions view tab. For a list of views to choose, see Predefined Administrative Reports.
Click the Reports button, and then choose the required report.
Wait for the report to display, and then examine the results.

Viewing Reports on the Remote Client

This topic describes views you can use in the Administration - Siebel Remote screen to monitor the status and progress of remote clients. It includes the following information:

Using the Client Status View

The Client Status view displays the current status of remote clients, including the following information:

The last time each remote client synchronized
The product versions of each remote client
The last time Siebel Remote extracted and initialized each remote client
The amount of free disk space, in bytes

Siebel Remote updates the data in this screen at the start and end of each synchronization. It does not update this data in the following situations:

During an initialization
If the Free Disk (Bytes) field is reset to zero during a database extract.

After applying modifications to the local database if these modifications are applied after data transfers are complete

In these situations, because the work occurs after the remote client disconnects from the Siebel Server, Siebel Remote does not update data in the status screen until the next synchronization. To help avoid running out of disk space on the local computer, the user can examine this information during this next synchronization.

To use the Client Status view

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Client Status view.
In the Mobile Clients/Replication Servers list, choose the remote client that you must monitor.
Examine the Siebel Remote Client Status form that displays details for the remote client that is currently chosen in the Mobile Clients/Replication Servers list.
For more information, see the table in Fields in the Siebel Remote Client Status Form.

Using the Client Status View with Siebel Anywhere

The Product Version field describes the Siebel Anywhere Upgrade kit that the user applied. This information is typically one session behind the current state of the upgrade. When you are using Siebel Anywhere, Siebel CRM does not update the Product Version field with the version information until after the upgrade finishes, and then after the user finishes the next synchronization.

Using the Client Status Diagnostics View

The Client Status Diagnostics view provides data routing information about the processors, remote clients, and regional nodes.

To use the Client Status Diagnostics view

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Client Diagnostics view.
Examine information in the Client form and the detailed form for the remote client.
For more information, see the table in Fields in the Siebel Remote Client Diagnostics Form.

Using the Synchronization Sessions View

The Synchronization Sessions view displays information about every user and the synchronization session for each user for a period of time. A systems administrator is the only person who can access this view.

To use the Synchronization Sessions view

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Synchronization Sessions view.
In the Synchronization Period form, choose the time frame for the period of time you must investigate.
In the Mobile Users list, choose the remote client that you must examine.
In the Synchronization Sessions list, run a query by entering values in the fields.
Examine details that Siebel Remote displays the Synchronization Sessions list.
For more information, see the table in Fields in the Synchronization Sessions List.

Using the Upload Statistics View

To configure Siebel Remote to save transactions on the Siebel Server after the remote client synchronizes, you can use the Upload Statistics view. You can use this view to verify the last set of transactions that Siebel Remote sent from the remote client to the server, and the last transaction that it applied to the server. The Upload Statistics view displays information about transactions and file attachments that Siebel Remote creates, receives, or applies in the following ways:

Created on each remote client
Received on the Siebel Server
Applied to the Siebel Server

To use the Upload Statistics view

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Upload Statistics view.
In the Mobile Clients/Replication Servers list, choose the remote client that you must monitor.
Examine the Siebel Remote Upload Statistics form that displays details for the remote client that is currently chosen in the Mobile Clients/Replication Servers list.
For more information, see the table in Fields in the Siebel Remote Upload Statistics Form.

Using the Download Statistics View

The Download Statistics view displays information about transactions and file attachments that are created, received, or applied in the following ways:

Created on the Siebel Server
Received on the remote client
Applied to the remote client

To use the Download Statistics view

Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Siebel Remote screen, and then the Download Statistics view.
In the Mobile Clients/Replication Servers list, choose the remote client that you must monitor.
Examine the Siebel Remote Download Statistics form that displays details for the remote client that is currently chosen in the Mobile Clients/Replication Servers list.
For more information, see the table in Fields in the Siebel Remote Download Statistics Form.

Displaying Local Time in the User Preferences Screen

If UTC is enabled, then some fields in the User Preferences screen use the GMT (Greenwich Mean Time) time zone to display time. Local time is the current time according to the local time zone on the remote client computer. To display local time in these fields, you must use Siebel Tools to modify the type property for each field, and then republish the Siebel runtime repository.

The following table describes the fields that display time in GMT if UTC is enabled.

Table Fields in the User Preferences View That Use GMT If UTC is Enabled

View	Display Name of Field	Business Component	Business Component Field
Mobile User Summary View	Time of Last Sync Session	Sync Client Status Local	C.Sess.When
Dock Session Log	Session Date	Session Log	Created

To display local time in the user preferences screen

Log in to Siebel Tools.
In the Object Explorer, click the Business Component object type.
In the Business Components list, query the Name property for the following value:
Sync Client Status Local
In the Object Explorer, expand the Business Component object type, and then choose Field.
In the Fields list, query the Name field for the following value:
C.Sess.When
Set the Type property to DTYPE_UTCDATETIME.
Repeat Step 3 through Step 6 for the Created field of the Session Log business component.
Compile your modifications, and then test them in a development environment.
Upgrade your Remote implementation.
For more information, see Upgrading a Regional Node.