IV69036: LOGIN TO PROVISO DATABASE TAKING TIME.

1.4.0.0-TIV-TNPM_ORA-IF0030

APAR status

• Closed as program error.

Error description

• Simple login to proviso database is taking too much time(7-8
  sec).
  
  During the investigation we came to know that an additional
  parameter has been added to the register procedure. This
  parameter is a boolean with a default of TRUE which is used to
  denote whether we should check to see whether there are orphaned
  pipes to be cleaned up.
  The default is to behave as older versions do which is to
  execute the SQL and perform any required cleanup on the first
  call to register following the package instantiation.
  Where this overhead is too expensive application developers can
  now pass FALSE into dbms_alert.register's new parameter to avoid
  the SQL being executed
  
  Following is the function which is affecting.
  
  Procedure LocalRegisterForAlert Is
        Pragma Autonomous_Transaction;
     Begin
        -- an AT is used because Register performs DML
        vcLogAlertName := GetLogAlertName();
        Dbms_Alert.Register( vcLogAlertName );
        Commit;
     End LocalRegisterForAlert;
  
  
  And we need to change it from
  
  Dbms_Alert.Register( vcLogAlertName )
  
  To
  
  Dbms_Alert.Register( vcLogAlertName, FALSE )
  

Local fix

• N/A
  

Problem summary

• The issue raised in this APAR regarding the Login Time for TNPM
  has been addressed in the following Interim Fix:
  1.4.0.0-TIV-TNPM_ORA-IF0030
  

Problem conclusion

• 1.4.0.0-TIV-TNPM_ORA-IF0030
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  NC/PROVISO DATA

• Fixed component ID

  5724P59DM

Applicable component levels

• R140 PSY

     UP