When I deploy the oracle_logmon configuration package that is present in the Nimsoft Archive, the logmon probe GUI no longer opens and it open the Raw Configure instead.
DX UIM 20.4.* / 23.4.*
The oralcle_logmon available at the Nimsoft Online Archive is simply a superpackge with configuration only that installs a logmon oracle monitoring profile and several watchers into your logmon target probe.
However, this package is End of Service as it was issued in 2003; although the profile in it can be still used as is, this is causing the issue because of packages mismatches.
We will retire or replace this package from the archive soon.
To resolve the issue you should NOT use the oracle_logmon package.
To Resolve the issue please:
1. First, Redeploy the same GA logmon version on top of the existing logmon probe that cannot be open. This will patch the issue. Check if the probe can be open now, and that you have your needed profile. Now you are ready to go as the GA probe has overwritten the EOS package and it will open now with the correct GUI.
2. never use again oracle_logmon but create a superpackage manually with the CFX below:
The procedure to create a simple probe configuration package is posted here: Create a simple DX UIM superpackage (broadcom.com)
oracle_logmon CFX:
<profiles>
<oracle alert log monitor>
active = no
scanfile = C:\Ora_816\ADMIN\POMAD\bdump\pomadALRT.LOG
scanmode = updates
interval =
<watchers>
<ORA-00600(internal)>
active = yes
match = /^ORA-0*600:? .*/
level = critical
expect = no
</ORA-00600(internal)>
<ORA-60(deadlocks)>
active = yes
match = /^ORA-0*60:? .*/
level = critical
expect = no
</ORA-60(deadlocks)>
<ORA-1578(block_Corruption)>
active = yes
match = /^ORA-0*1578:? .*/
level = critical
expect = no
</ORA-1578(block_Corruption)>
<ORA-18(max_session_exceeded)>
active = yes
match = /^ORA-0*18:? .*/
level = major
expect = no
</ORA-18(max_session_exceeded)>
<ORA-20(max_proc_exceeded)>
active = yes
match = /^ORA-0*20:? .*/
level = major
expect = no
</ORA-20(max_proc_exceeded)>
<ORA-034(commit_rollback_disable)>
active = yes
match = /^ORA-0*34:? .*/
level = major
expect = no
</ORA-034(commit_rollback_disable)>
<ORA-051(timeout)>
active = yes
match = /^ORA-0*51:? .*/
level = major
expect = no
</ORA-51(timeout)>
<ORA-55(max_dml_locks)>
active = yes
match = /^ORA-0*55:? .*/
level = major
expect = no
</ORA-55(max_dml_locks)>
<ORA-59(max_db_files)>
active = yes
match = /^ORA-0*59:? .*/
level = major
expect = no
</ORA-59(max_db_files)>
<ORA-206(disk_io_failure)>
active = yes
match = /^ORA-0*206:? .*/
level = critical
expect = no
</ORA-206(disk_io_failure)>
<ORA-601(cleanup lock conflict)>
active = yes
match = /^ORA-0*601:? .*/
level = critical
expect = no
</ORA-601(cleanup lock conflict)>
<ORA-602(internal programming exeption)>
active = yes
match = /^ORA-0*602:? .*/
level = critical
expect = no
</ORA-602(internal programming exeption)>
<ORA-603(server_session_terminate)>
active = yes
match = /^ORA-0*603:? .*/
level = critical
expect = no
</ORA-603(server_session_terminate)>
<ORA-604(recursive_sql_error)>
active = yes
match = /^ORA-0*604:? .*/
level = major
expect = no
</ORA-604(recursive_sql_error)>
<ORA-606(internal error code)>
active = yes
match = /^ORA-0*606:? .*/
level = critical
expect = no
</ORA-606(internal error code)>
<ORA-7445(core_dump)>
active = yes
match = /^ORA-0*7445:? .*/
level = critical
expect = no
</ORA-7445(core_dump)>
<ORA-1650(unable_extend_rollback)>
active = yes
match = /^ORA-0*1650:? .*/
level = minor
expect = no
</ORA-1650(unable_extend_rollback)>
<ORA-1652(unable_extend_tempseg)>
active = no
match = /^ORA-0*1652:? .*/
level = minor
expect = no
</ORA-1652(unable_extend_tempseg)>
<ORA-1555(snapshot_to_old)>
active = no
match = /^ORA-0*1555:? .*/
level = minor
expect = no
</ORA-1555(snapshot_to_old)>
<ORAX(all_ora_messages)>
active = no
match = ORA-*
level = warning
expect = no
</ORAX(all_ora_messages)>
</watchers>
</oracle alert log monitor>
</profiles>