How to Perform sqlite3 Operations against the DAP pendingRequests.db Database
(Doc ID 2075422.1)
Last updated on MARCH 15, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (NCC), Data Access Pack (DAP) has the ability to store failed requests (to try again later) in either internal memory or an sqlite3 database based on the following configuration in the DAP section of the eserv.config file:
pendingQueueInMemory - Sets whether or not to boost performance by holding the queue of pending DAP requests in non-persistent memory. true|false - defaults to false
pendingFilename - Location in which to store pending requests in the event that re-delivery is required. Any path/filename combination - defaults to /IN/service_packages/DAP/tmp/pendingRequests.db
Assuming the aforementioned configuration options are left as default, then the failed requests will be stored in an sqlite3 database file on disk.
This article will cover what operations can be run against the SQLite database file, how to run them based on what version of NCC is installed, and precautions around running these operations.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Calling sqlite3 Against the pendingRequest.db Database|
|Querying Outstanding Requests|
|Recovering Disk Space by Shrinking pendingRequest.db|
|Validating the Integrity of the pendingRequests.db Database|