Oracle SDE List Tables 9.x

The Oracle SDE List Tables 9x monitoring point is designed to work together with the Oracle SDE Usage check to generate the information required for SDE Usage reporting. It is recommended that these two checks be placed together in a GeoMonitor Server because of the fact that both are needed to generate the data required to support SDE Usage reporting.

The Oracle SDE List Tables 9x check runs once a week based on a time stamp stored in the GeoMonitor database. The check creates a list of all of the SDE (version 9.x) geodabase feature datasets, feature classes and tables in an Oracle SDE instance. This list is used to identify geodatabase feature datasets, feature classes and that are unused for SDE Usage reporting. The Oracle SDE Usage check is generally run hourly and records what feature datasets, feature classes and tables are open. A more detailed description of the Oracle SDE Usage check is provided in the next section.

If you are not sure where your Usage information is being stored, you can consult the “About” dialog on the GeoSystems Monitor Charts UI.

This check needs an Oracle (32Bit) client that customer provides which is installed locally and configured to perform this check. Make sure that the ORACLE_HOME environment variable is set and that the system PATH is set to the folder where the Oracle (32Bit) client is located.

Note: If you are using Microsoft SQL Server / SQL Server Express, follow the instructions in Setting Up Microsoft SQL Server for SDE Usage Database

The parameters that are unique to the Oracle SDE List Tables 9x include:

Server Name	Domain name of SDE Server (or IP address)
Server Nm w/Listener	Server name, port and listener to connect to the Oracle DB *Example:* voracle10g:1521/vector (Must be identical for this check and Usage check)
userID	Oracle user ID with access to the Oracle Table *Note:* userID should be entered as encrypted information
userPW	Oracle user PW for access to the Oracle Table *Note:* userPW should be entered as encrypted information
Rpt-DSN:User:Pwd	Needed only if using RDBMS to store usage information – string must include YourODBC_ConnectionName:UserID:UserPW Note: Rpt-DSN:User:Pwd should be entered as encrypted information
Opt-User Schema	(Optional) Leave blank for Oracle SDE