1,126
edits
Difference between revisions of "Troubleshooting Content Manager OnDemand"
Troubleshooting Content Manager OnDemand (view source)
Revision as of 14:16, 29 January 2016
, 14:16, 29 January 2016Added examples of how to view the db2 diag log.
(Initial Edit.) |
(Added examples of how to view the db2 diag log.) |
||
| Line 35: | Line 35: | ||
IBM DB2 is provided by default as a 'limited use' license with Content Manager OnDemand at no cost, and as such, is the most popular database for CMOD. DB2 has a concept call 'instances', which is like a complete installation of DB2 that is unique and managed at the user account level. If users Bob and Alice both have accounts on a single server, they can each have their own instance, and that instance is complete and wholly functional and independent for each of them. To facilitate this user-level instance, DB2 creates a directory called 'sqllib' inside the user's home directory (in our example, Alice would have /home/alice/sqllib, and Bob would have /home/bob/sqllib). Inside the sqllib directory is the 'db2dump' subdirectory, which contains a file called 'db2diag.log'. It contains the majority of the diagnostic information for DB2. | IBM DB2 is provided by default as a 'limited use' license with Content Manager OnDemand at no cost, and as such, is the most popular database for CMOD. DB2 has a concept call 'instances', which is like a complete installation of DB2 that is unique and managed at the user account level. If users Bob and Alice both have accounts on a single server, they can each have their own instance, and that instance is complete and wholly functional and independent for each of them. To facilitate this user-level instance, DB2 creates a directory called 'sqllib' inside the user's home directory (in our example, Alice would have /home/alice/sqllib, and Bob would have /home/bob/sqllib). Inside the sqllib directory is the 'db2dump' subdirectory, which contains a file called 'db2diag.log'. It contains the majority of the diagnostic information for DB2. | ||
Log in as the database instance owner, then run these commands: | |||
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. | |||
Alternately, you can see the last 500 lines of the log with tail: | |||
tail -n 500 ~/sqllib/db2dump/db2diag.log # Show the last 500 lines -- may be different on different Operating Systems! | |||
Or of you want to monitor messages as they're written into the database: | |||
tail -f ~/sqllib/db2dump/db2diag.log # Prints new messages as they're added to the log file. | |||
In order to exit from the tail command, press Control-C. | |||
== Tivoli Storage Manager == | == Tivoli Storage Manager == | ||