Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved PB 19 tracing DB error

  1. Issue
0
Votes
Undo
  1. Kelly Amott
    Kelly Amott
  2. PowerBuilder
  3. Monday, 21 February 2022 20:44 PM UTC

I have a PowerBuilder 19 app I inherited that is producing primary key violations in the Oracle 19 DB. I have tried - 

1. Step debug but the structure of the application is so convoluted that it is incredibly tedious to step through from the start.

2. Inserting multiple breakpoints where it appears obvious that the breakpoint should be but nothing triggers. 

3. Profiling Trace View. This produced a pbp file that I can't read. I've tried just clicking on it and it brings up a window in PB along with an error - "Attempt to open DataWindow failed."

4. DB Trace tool. Still trying to figure this one out. Do I just replace (SQLCA) in my script with (SQLCA.DBMS = "TRACE ORA ORACLE")?

Opened the window from link is not on top
dw.Update() is no longer working and getting an er...
Responses (1)
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Monday, 21 February 2022 21:25 PM UTC
  2. PowerBuilder
  3. # 1

Hi, Kelly - 

A profile trace is a binary file. You can use one of the "Profiling xxxx View" tools on the "Tools" tab of the PB "New" dialog window to view the contents of a profile trace file:

As for the DB Trace, yes, set the DBMS property of the transaction object to begin with the keyword "TRACE", such as "TRACE ORA".

Good luck! John

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.