Discoverer Import Checklist and Configuration

The Blitz Report Discoverer import heavily relies on execution statistics stored in the database table `EUL5_QPP_STATS` . To ensure this table is populated, users must properly exit Discoverer Desktop or Plus using the File > Exit menu (not just closing the window) , . For Discoverer Plus and Viewer users, specific settings must be verified in the server configuration file (`pref.txt`) , .

You need to verify two critical profile settings, typically found in the `[Database]` section or the registry key path `HKEY_CURRENT_USER > Software > Oracle > Discoverer 11 > Database` . The keys `QPPEnable` and `QPPCreateNewStats` must both have their values set to ‘1’ . Additionally, within Discoverer Admin, you must enable ‘Collect Query Statistics’ for all users whose statistics you want to track .

If you are not seeing current worksheet SQLs or execution history, it indicates a failure in the mechanism that updates the `AMS_DISCOVERER_SQL` table . This table is updated when a worksheet is saved, triggered by a Discoverer database trigger called `eul_trigger$post_save_document` . If this trigger does not exist or fails to call the underlying PL/SQL function (`AMS_DISCOVERER_PVT.EUL_TRIGGER$POST_SAVE_DOCUMENT`), the SQLs won’t be available for import .

Yes, for better import performance, it is recommended to create an index on `eul5_documents.doc_name` . The suggested index creation statement is: `create index .xxeul5_documents_n1 on .eul5_documents (doc_name) tablespace apps_ts_tx_idx;` .