Salesforce

The -trig parameter fails in combination with -cache at runtime

Printable View
« Go Back

Information

 
TitleThe -trig parameter fails in combination with -cache at runtime
URL NameThe-trig-parameter-fails-in-combination-with-cache-at-runtime
Article Number000155499
EnvironmentProduct: OpenEdge
Version: 11.x, 12.x
OS: All supported platforms
Question/Problem Description

When using the -cache parameter (to load a schema cache file) in combination with the -trig parameter (to define the db trigger location), it results in the message that the trigger is not found (293) when running a query against the database.
Using only the -trig parameter without -cache works fine.

Steps to Reproduce
Clarifying Information

When analyzing with Process Monitor, it checks for the trigger files in the following places:

  • Current working directory (start in)

  • DLC/

  • DLC/gui

  • DLC/bin

    But not in the folder defined with the -trig parameter

The documentation mentions that "If you are generating the local binary schema cache, do not connect to the database using Trigger Location (-trig) and Schema Cache File (-cache) together."
However, this is when generating the cache file. It doesn't mention runtime.

Error Message
Defect NumberOCTA-19138
Enhancement Number
Cause
When saving the cache file, the value for the trigger procedure is saved as is in the cache.
When specifying the -trig, the trigger procedure name is adjusted by adding the -trig value as a prefix, and keep that in the cache.
Thus when saving the cache file with the -trig parameter, the cache file ends up with the -trig value.
Hence it's not recommended to use the -trig parameter when saving the cache file.

However at runtime, because the schema is loaded from the cache file, the -trig value is ignored since the cache is already loaded.
Resolution
Fixed version(s): 11.7.6.0, OpenEdge 12.2, OpenEdge 12.3
Workaround
Notes
After the upgrade to 11.7.6, 12.2, 12.3 or later is performed several additional steps are needed:
  1. Regenerate the cache file with the upgraded client. (This will set a new flag when there's a relative path name for the trigger and has not been adjusted with -trig in the current session.) 
  2. Deploy the new cache file to users to replace their existing cache file.


If the above steps are not performed then existing cache files will continue to exhibit the faulty behavior.
Keyword Phrase
Last Modified Date11/29/2023 10:02 PM
Powered by