Syntax for pcm_compute_stats
| OS | Command |
|---|---|
| Windows | pcm_compute_stats.pl dbname@ODBC_DSN -xyadminpwd xyadmin_pwd -pdmpwd db_passwd |
| Linux | pcm_compute_stats.pl dbname@SID -xyadminpwd xyadmin_pwd -pdmpwd db_passwd |
| Switch | Description |
|---|---|
Windows: dbname@ODBC_DSN —or— Linux: dbname@SID | Required: dbname. The name of the Contenta database. |
Optional: ODBC_DSN (Windows) The ODBC data source name. If not specified, the default is used—as defined in the registry for XYV_PDM_ODBC_DSN | |
Optional: SID (Linux) The system identifier. If not specified, the default is used—as defined in the registry for XYV_PDM_DATABASE_SID | |
-xyadminpwd xyadmin_pwd | xyadmin_pwd is the password for the Contenta xyadmin user if not the default password (see Modifying Contenta User Passwords). Default: manager |
| -pdmpwd db_passwd | db_passwd is the Contenta database password if not the default database password (see Modifying Contenta User Passwords). |
There is no visible output (stdout) when you execute this program unless it fails, then the reason for the failure is reported.
Example
pcm_compute_stats.pl:database cetrain/db_passwd@trng is in use by another user
On Linux systems, you can schedule execution of the program in a CRON job at a time when there are no users on the system. It is recommended that:
- you estimate the time that is needed to complete the process then schedule program execution appropriate to a time when no users need access to Contenta. (Refer to your Oracle documentation to estimate the time needed.)
- prior to execution of pcm_update_stats.pl you schedule execution of pcmsessions with the -clear switch for the Contenta database (Oracle user) for which you want to analyze and compute statistics. This will ensure if there are stale sessions, that the pcm_compute_stats.pl program will execute without failure. See the Contenta Sessions Command for information about pcmsessions.
- you pipe the standard output (stdout) from the program to a log file so you can be certain that it was successfully executed. If successful, the log file is empty.