Monday, May 2, 2011

Some simple stuff

 These tips will help you get that extra data to help with self-troubleshooting:


WebLogic Installer in debug mode:

There are times when a webLogic installer fails in the middle and you do not have a clue what is going wrong (except for a single fat error message). Consider starting the installer with extra bit of logging enabled. Here is the syntax and applicable logging level flags (holds true for 11g as well):

      <installer_name> [-mode={console|gui|silent}] [-silent_xml=<file_name>] [-log=<file_name>] [-log_priority={debug|info|warn|error|fatal}]

       e.g., wls1032.exe -mode=console -log install.log -log_priority=debug

Applying patch with debug logging level:

Enable debug logging when applying the patch to get more insight into what is happening:

       bsu.sh [-log=<file_name>] [-log_priority={trace|debug|info|warn|error|fatal}]


Checking the Debug scope (of available debug flags in WebLogic):

       java weblogic.diagnostics.debug.DebugScopeViewer

No comments:

Post a Comment