Create Object Links Cache actions
Create Object Links Cache actions create a tree of object dependency links for a specified RFC Destination. The tree of object links is stored in an object links cache database on the drive where the LiveCompare user data directory is stored. This database may be used by the following actions.
- Analyze Object Links
- Find Object Links
- Find Object Links (Read Only)
- Find Similar Objects
- Uses What
- Uses What (Read Only)
- Where Used
- Where Used (Read Only)
If an object links cache database has been generated for an RFC Destination it may provide these actions with a performance improvement, since the tree of object dependency links for the RFC Destination is already available to LiveCompare. The status of the object links cache database for an RFC Destination is shown in the RFC Destination’s OLC tab.
If the Create Object Links Cache action is run for an RFC Destination that does not already have an object links cache database, a new object links cache database will be created for the RFC Destination. The ‘Request Reset’ option in an RFC Destination’s OLC tab also causes a new an object links cache database to be created for the RFC Destination when the action is next run.
If the Create Object Links Cache action is run for an RFC Destination that already has an object links cache database, the object links cache database is updated with any new object dependency links found for the RFC Destination (typically, this is a much faster operation). Additionally, for any objects with code that need to be refreshed, SAP’s cross reference tables are rebuilt using a custom function.
The Create Object Links Cache action should be run before the Analyze Object Links, Find Object Links, Find Similar Objects, Uses What or Where Used actions are run against an RFC Destination for the first time. The action should also be run after any new transports or support packs have been imported into an SAP system. This ensures that any new transport objects are included in the RFC Destination’s cached tree of object links.
Action property | Description |
---|---|
Depth | An Integer parameter or dataset that specifies the maximum depth for the tree of links generated by the action. If this parameter is set to 0 and an object links cache needs to be generated, the action refreshes its cache of index tables for the RFC Destination, and does not generate any links. |
Hours to Run |
An Integer parameter or dataset that specifies the maximum number of hours for which the action will run. If this parameter is set to 0 and an object links cache needs to be generated, the action refreshes its cache of index tables for the RFC Destination, and does not generate any links If the Hours to Run setting elapses while the Create Object Links Cache action is generating index tables, the action finishes after the index tables have been generated. |
Result | A Table dataset that stores summary details for the Create Object Links Cache operation. |
RFC Destination | An RFC Destination parameter or dataset referring to the SAP system for which an object links cache database is to be generated. |
Source |
A Table parameter or dataset that contains performance history data. The table should include a NAME column which stores the name of each object, and a TYPE column which stores each object’s type. This property is normally set to the Application Statistics dataset returned by a Read Performance History Data action that is run for a Pipeline’s Usage System. |
Example
To examine the details for a Create Object Links Cache action, double-click the action node, or select ‘View Details’ from the node’s context menu. The Details screen displays the action’s start and end time, the type of update operation performed (either Create new OLC or Update existing OLC), and the time taken for the action to complete. In the case of an update, the Details screen also lists the number of recent objects, and the number of objects associated with a date.
The progress of a Create Object Links Cache action may be monitored by viewing the Details screen while the action is running. The following details are shown:
Item | Description |
---|---|
Started | The action’s start time. |
Update type | Indicates whether a full object links cache database is being created, or whether an incremental update of the object links cache database is being performed, or whether no update is required. |
Objects done | The number of objects processed so far. |
Elapsed time (seconds) | The time for which the Create Object Links cache action has been running. |
Total elapsed time hh:mm:ss | The time for which the Create Object Links Cache action has been running in hours, minutes and seconds. |
Press the F5 key periodically to update the display.
If a Create Object Links Cache action is interrupted (for example because its RFC Destination becomes unavailable) choose ‘Continue’ from the action’s context menu to restart it. Where possible, the Create Object Links Cache action will reuse results that have already been cached.
Object links cache locks
The Create Object Links Cache, Analyze Object Links, Find Object Links, Find Similar Objects, Uses What and Where Used actions place a lock on an RFC Destination’s object links cache database (if the last four actions are run with their Use Cache property set to true) . The actions cannot be run against the same RFC Destination while the lock is in place.
If one of the above actions fails to complete, it can cause the Object Links Cache action to remain locked. If an Object Links Cache is locked, the above actions check for the lock once every 100 seconds for a total of 999 times before they fail with an error. The number of times the lock is checked for can be set by creating the following DWORD registry entry on the LiveCompare server.
HKEY_LOCAL_MACHINE\SOFTWARE\Tricentis\LiveCompare\5.3\Settings\OlcLockRetries
If this entry is not set, 999 is used as the default, which means the above actions will check to see if an Object Links Cache lock has been released for approximately 27 days.
Find Object Links (Read Only) actions