Skip to main content

Search

Welcome to Tibero GTS!

Occurrence of APM/TPR STOP Phenomenon

Document Type | Troubleshooting

Category | Utility 

Applicable Product Version | 5SP1FS06, 6FS06

Document Number | TUTTS004

 

Issue

An issue has occurred where APM (Automatic Performance Monitoring)/TPR (Tibero Performance Repository) Snapshots are not being collected.
 

Reproduction Scenario

1. Create the Views referenced by APM/TPR in the Tibero account.
SQL> create view tibero.v$session as select * from sys.v$session;

2. Restart APM/TPR.
SQL> @$TB_HOME/scripts/apm_stop.sql   โ€“ Stop APM


sys.log
02/14 14:32:53.046391 [DDL][0] 32 ddl_fram:204 Executing DDL: ALTER SYSTEM SET AUTOMATIC_PERFORMANCE_MONITORING=N
02/14 14:32:53.047480 [DDL][0] 32 ddl_fram:226 DDL execution succeeded


SQL> @$TB_HOME/scripts/apm_start.sql  โ€“ Start APM



sys.log
02/14 14:33:30.508828 [DDL][0] 32 ddl_fram:204 Executing DDL: ALTER SYSTEM SET AUTOMATIC_PERFORMANCE_MONITORING=Y
02/14 14:33:30.509057 [APM][0] 01 tbsvr_ct:2350 APM begins
02/14 14:33:30.509079 [DDL][0] 32 ddl_fram:226 DDL execution succeeded
โ€ฆ
02/14 14:33:42.653494 [APM][0] 22 tbsvr_ap:164 APM failed to init. System views are not created . retry_cnt:10
02/14 14:33:42.653592 [APM][0] 01 tbsvr_ct:2366 APM stops
02/14 14:33:42.653609 [FRM][0] 01 tbsvr_si:714 SEND SESS_KILL SIGNAL to 22
02/14 14:33:42.653658 [FRM][0] 22 tbsvr_si:1856 GET SESS_KILL SIGNAL (tid=22, thr_status=4, sess_status=3)
02/14 14:33:42.653695 [FRM][0] 22 tbsvr_er:081 THROW. ec=ERROR_SESS_KILLED(-12001) [ Session has been closed.   ] (csr_id:4294967295) [sem.c:663:tb_sem_wait_internal]
02/14 14:33:42.653729 [FRM][0] 22 tbsvr_er:081 THROW. ec=ERROR_SESS_KILLED(-12001) [ Session has been closed.   ] (csr_id:4294967295) [bitqueue.c:268:bitq_read_internal]

3. Check the status of APM/TPR.
SQL> @$TB_HOME/scripts/apm_check_status.sql
   APM_ENABLE: NO
   PSM completed.
   File finished.

 

Cause

If the objects (Views) referenced by APM/TPR exist under users other than the SYS account, an error occurs during the process of checking whether the Views are created, causing APM/TPR to stop.
 
List of Referenced OBJECTS (Views)
  • V$SYSTEM_EVENT
  • V$LATCH
  • V$SQLSTATS_PLAN_HASH
  • V$LIBRARYCACHE
  • V$ALL_FILESTAT
  • V$OSSTAT2
  • V$PGASTAT
  • V$SGASTAT
  • V$PROCESS
  • V$UNDOSTAT
  • V$SQL_PLAN_STATISTICS
  • V$SQL_WORKAREA_HISTOGRAM
  • V$SESSION
  • V$SEGMENT_STATISTICS
  • V$TEMPSEG_OP_USAGE
 
 

Solutions

Apply the 175508a patch, which has been modified to allow APM/TPR to function normally even if the Views referenced by TPR/APM are created under accounts other than SYS.
Caution
Apply the patch through technical support provided by Tmax Tibero.

Note
After deleting the APM/TPR referenced Views created outside the SYS account and restarting APM/TPR, normal use is possible.
If you avoid using Views with the same names thereafter, this issue can be permanently circumvented.

(1) Drop Views referenced by APM/TPR created outside the SYS account
select owner,object_name 
from dba_objects 
where owner not in ('SYS','PUBLIC') 
and object_name in ('V$SYSTEM_EVENT', 'V$LATCH', 'V$SQLSTATS_PLAN_HASH', 'V$LIBRARYCACHE', 'V$ALL_FILESTAT', 'V$OSSTAT2', 'V$PGASTAT', 'V$SGASTAT', 
                'V$PROCESS', 'V$UNDOSTAT', 'V$SQL_PLAN_STATISTICS','V$SQL_WORKAREA_HISTOGRAM', 'V$SESSION', 'V$SEGMENT_STATISTICS', 'V$TEMPSEG_OP_USAGE');

(2) @$TB_HOME/scripts/apm_start.sql

 

 

 

Related to