Description

This page troubleshoots performance issues you may face during a PL/SQL extraction.

Observed in CAST AIP
Release
Yes/No
8.3.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
CSS(tick)
Step by Step Scenario
 Run the DB extractor
Action Plan
  1. Open the extractor log file
  2. Check globally if the extraction rate is low : If they are lower than 1000 rows/s, this is a bad performance. You can focus on the Extracting: Oracle Tables... as below screenshot :
  3. If the rate are low :
    1. Either this is due to network issue, the bandwidth is very thin. The extraction must be done closely to the Oracle Server, or in the Oracle Server.
    2. Or / And this is due to Oracle performances.
    3. To check these two informations, you can use the stand alone extractor, in Expert mode, with the export format set to test_sql as below screenshot :
    4. Run the extraction in this mode. This mode will extract only the number of rows per queries, that means, for each queries, it send only one octet:
      1. If the rate is low, this is an Oracle Server performance
      2. If the rate is high, this is a network issue, the bandwidth is very thin.
  4. If in the extractor log file, the last line of the extraction is :

    Extracting: Oracle All Columns Of Tables...

    This means that the extractor is extracting the column of tables. Included in the columns are the comments. We usualy may face performance issue at this step. To solve this, you must use the standalone CAST DB Extractor from the CAST AIP 8.2.9 from where we can prevent the comments to be extracted.

Impact on Analysis Results and Dashboard

Impact of the error : Extraction is not complete
Impact of solution : No impact and extraction gets completed successfully.

Notes/comments
 Ticket # 2844
Related Pages