T.R | Title | User | Personal Name | Date | Lines |
---|
5042.1 | | HOTRDB::PMEAD | Paul, [email protected], 719-577-8032 | Tue Feb 18 1997 14:29 | 1 |
| Perhaps some images need to be installed?
|
5042.2 | | caotv1.ca.oracle.com::BZINN | [email protected] | Tue Feb 18 1997 15:25 | 9 |
| Well, all the 'normal' ones are installed.
The only difference between running and failing is the DCL line
$define lib$debug sys$share:pca$collector
Having them analyze pca$collector to see if it pulls in anything
unusual.
Will also try with SET WATCH to see if we can tell where its failing.
|
5042.3 | | DUCATI::LASTOVICA | Is it possible to be totally partial? | Tue Feb 18 1997 15:32 | 1 |
| are the PCA image(s) installed similarly to DEBUG*.EXE?
|
5042.4 | | NOVA::DICKSON | | Tue Feb 18 1997 16:01 | 2 |
| Doesn't PCA run the program under test in a sub-process? Does that
sub-process get its RDB environment set up?
|
5042.5 | | DUCATI::LASTOVICA | Is it possible to be totally partial? | Tue Feb 18 1997 16:05 | 5 |
| PCA run's in the process's context. Basically, when you use PCA,
it runs like the debugger would. You tell PCA to collect information
about whatever you want (I/Os, CPU time, PC sampling, whatever) and
it records the information into a data file. Later on, you analyze
the data file.
|
5042.6 | no luck | caotv1.ca.oracle.com::BZINN | [email protected] | Wed Feb 19 1997 10:43 | 8 |
| They still can't get this thing to run.
MV 6.1 is defined as the system default version.
Without PCA, everything runs fine.
Tried installing SQL$SHR61 and SQL$INT, just in case.
They're going to try to talk to a PCA specialist at Digital.
|