DMW/LSH: How To Enable/Disable/Truncate Debug via PL/SQL, And Find In CDR_EXE_DEBUG The Testcase Log Entries
(Doc ID 2213775.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Data Hub - Version 2.2.1 and laterOracle Life Sciences Data Management Workbench - Version 2.4.3 and later
Information in this document applies to any platform.
Goal
LSH Debug (LSH:ENABLE_DEBUGGING profile) is available after DMW/LSH 2.4.3. It was back ported to 2.2.1 version, too.
This document explains how to Enable/Disable/Truncate Debug via PL/SQL code. Additionally, it shares some tips to query CDR_EXE_DEBUG table and collect correctly the log entries for each testcase. When LSH Debug is enabled, it saves all executions logs in CDR_EXE_DEBUG Table. After several runs, it is hard to figure out which rows are related to which testcase. Here you will find some ideas.
IMPORTANT: In LSW 2.4.3.X, the CDR schema is owner of table CDR_EXE_DEBUG. Then, in this KM Doc, all queries are executed as CDR.CDR_EXE_DEBUG due you login as APPS schema. In earlier LSH versions, like 2.2.1.X, the owner was APPS schema and then, in 2.2.1.X, you run the queries just as CDR_EXE_DEBUG.
Login as APPS and check to whom the table belongs in your instance to see if you should run the queries as CDR_EXE_DEBUG instead of CDR.CDR_EXE_DEBUG.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Steps to consider to enable/disable debug |
| Enable LSH Debug via PL/SQL |
| Find Testcase Logs When Few Rows Are In Debug Table. Optionally, Truncate It |
| How To Disable Debug And, Optionally, Truncate CDR_EXE_DEBUG Table |
| Extra Tips To Find Testcase Logs When Too Many Rows Exist In Debug Table, Or Several Testcases Are Run In The Same Debug Session |
| References |