Page History
...
- Open the PeopleSoft configuration file:
psappsrv.cfg
(usually underPT%version%/appserv/%domainName%
). If EnableDBMonitoring=1, proceed to step 6. Otherwise, proceed to step 2. - Disconnect all PeopleSoft users.
- Shut down all PeopleSoft servers.
- Edit the DB Monitoring parameter to be TRUE:
EnableDBMonitoring=1
- Restart the PeopleSoft application servers.
- Using SQL Query Analyzer, connect to the database holding the PeopleSoft tables. Verify that you are connecting with a user that is a member of the db_owner database role in the database.
- Execute the following batch:
if exists (select name from sysobjects where name = 'precise_psprcsrqst_register' and type = 'TR')
drop trigger precise_psprcsrqst_register go
if exists (select name from sysobjects where name = 'VERITAS_psprcsrqst_register' and type = 'TR')
drop trigger VERITAS_psprcsrqst_register go
if exists (select name from sysobjects where name = 'Symantec_psprcsrqst_register' and type = 'TR')
drop trigger Symantec_psprcsrqst_register go
create trigger precise_psprcsrqst_register on PSPRCSRQST for update as
declare @oprid char(30), @prcsinstance int, @old_status int, @new_status int, @info binary(50)
select @old_status = RUNSTATUS from deleted select @new_status = RUNSTATUS from inserted if (@new_status <> 7) or (@old_status = 7) return
select @oprid = OPRID, @prcsinstance = PRCSINSTANCE from inserted
set @info = convert(binary(50), rtrim(@oprid) + ',' + convert(varchar(20), @prcsinstance))
set context_info @info go
Precise. Performance intelligence from click to storage. Learn more > >
IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal