1,126
edits
Difference between revisions of "Troubleshooting Content Manager OnDemand"
Jump to navigation
Jump to search
Troubleshooting Content Manager OnDemand (view source)
Revision as of 16:34, 16 March 2018
, 16:34, 16 March 2018→IBM DB2
| Line 63: | Line 63: | ||
cd sqllib/db2dump # Change into the directory where log files are kept. | cd sqllib/db2dump # Change into the directory where log files are kept. | ||
more db2diag.log # View the contents of the DB2 Diagnostic Log a page at a time. | more db2diag.log # View the contents of the DB2 Diagnostic Log a page at a time. | ||
If you can't find the db2diag.log, or the data in it is old, your organizations Database Administrator may have moved the diagnostic data files. You can find the new path with the following command: | |||
$ db2 "get dbm cfg" |grep DIAGPATH | |||
Diagnostic data directory path (DIAGPATH) = /db2/db2dump/ | |||
Alternate diagnostic data directory path (ALT_DIAGPATH) = | |||
Alternately, you can see the last 500 lines of the log with tail: | Alternately, you can see the last 500 lines of the log with tail: | ||