08-30-2006 01:10 AM
"DBSPI-0001.3: DB-SPI cannot connect to database db_name, may be down; Oracle error [ORA-01013:_user_requested_cancel_of_current_opera
Is it the same 300 seconds as it says in the follwoing message?
"DBSPI10-24: Connect attempt to database 'db_name' timed out after 300 seconds. Please check database."
If so, where is the 300 seconds defined and can it be changed?
The monitor template triggering this uses the command:
"dbspicao -c DBSPI-Ora-05min-Favorites -m 1..."
08-30-2006 05:27 AM
DBSPI-0001 is an Oracle metric which is waiting a value from an external program. External program (dbspicao) is triggered by a Scheduled task template. There are a few Scheduled task templates to run dbspicao program at different times, with different metrics. One runs every 5 mins, another one runs hourly, daily etc.
DBSPI-0001 metric is by default included in 5-min template (as you already wrote) so "300 seconds" is defined in that policy.
If you want to change the interval to 1 hour, then move metric-1 to 1-hour template.
If you want to change the schedule for example to 2 mins, then create a new template (named DBSPI-Ora-02min-Favorites), then schedule it to every 2 minutes, and run "dbspicao -c DBSPI-Ora-02min-Favorites -m 1". You must also remove metric 1 from 5-min template.
DBSPI10-24 is produced by a DBSPI program itself, to inform an internal error. Like other internal errors, it is intercepted by a unique Open Message Interface template (i think it is named DBSPI-Messages)
08-30-2006 05:41 AM