Top
ERROR: “ORA-01012: not logged on” messages reported in the mm.log in Metadata Manager (MM) 9.x – BPMBI
6910
post-template-default,single,single-post,postid-6910,single-format-standard,mkd-core-1.0,highrise child-ver-1.1.1,,mkd-smooth-page-transitions,mkd-ajax,mkd-grid-1300,mkd-blog-installed,mkd-header-standard,mkd-fixed-on-scroll,mkd-default-mobile-header,mkd-sticky-up-mobile-header,mkd-dropdown-slide-from-bottom,mkd-dark-header,mkd-full-width-wide-menu,mkd-header-standard-in-grid-shadow-disable,mkd-search-dropdown,mkd-side-menu-slide-from-right,wpb-js-composer js-comp-ver-5.2.1,vc_responsive

Blog

ERROR: “ORA-01012: not logged on” messages reported in the mm.log in Metadata Manager (MM) 9.x

Problem Description
In the mm.log, the following message is seen a number of times:
ORA-01012: not logged on
Because of this error, various operations/tasks do not complete or are hung.

Cause
This issue occurs when the JDBC connection from the MM Service to the MM Repository Database (on Oracle) is IDLE for a long time.

Solution
To resolve this issue, do the following:

  • Login to the MM Repository Database Server and execute the following queries:
    a) Find the Profile used by the MM Database user:

    SELECT USERNAME,PROFILE FROM DBA_USERS WHERE USERNAME='MM_Database_Username';

    b) Find the idle_time set for the profile in (a)

    select * from dba_profiles where resource_name='IDLE_TIME' and profile='Profile_from_a';
  • Set the IDLE_TIMEOUT to UNLIMITED, if this is not the current value.
  • Restart Database Server if required.
  • Restart the MM Service.
No Comments

Leave a Comment