...
APPLY (without having to stop the APPLY process)
| Note |
|---|
Profiler can be enabled while APPLY is running but it will not collect all required performance statistics to diagnose the issue. Therefore it is not recommend to enable profiler on APPLY while it is running. |
Start the command console and type
No Format engine apply send memory_set PROFILER /home/oracle/..../prof_%S.%E engine apply send memory_set _THREADED_OCI YES- Wait for a few PLOG log switches.
- Zip and upload the resulting files to Dbvisit Support. The profiler files will be in the location specified by the full path given (/home/oracle/..../prof_%S.%E)
Turn off the profiling:
No Format engine apply send memory_set PROFILER OFF engine apply send memory_set _THREADED_OCI NO
APPLY (shutting down APPLY)
- Shutdown the APPLY process
- Edit the *-APPLY.ddc DDC file.
Add the following line to the DDC file (give full path name):
No Format memory_set PROFILER /home/oracle/..../prof_%S.%E memory_set _THREADED_OCI NO- Restart the APPLY process
- Wait for a few PLOG switches.
- Zip and upload the resulting file to Dbvisit Support. The profiler files will be in the location specified by the full path given (/home/oracle/..../prof_%S.%E)
Turn off the profiling with by removing the profiler command OR adding a comment in front of the line in the DDC file:
No Format # memory_set PROFILER /home/oracle/..../prof_%S.%E # memory_set _THREADED_OCI NOStop and restart the APPLY process
...