|
IBM Lotus Domino 6. 5 for Linux on zSeries Implementation Authors: Ebbers M. Published year: 2003 Pages: 78-81/162 |
| < Day Day Up > |
Problem: We discovered that the translog was placed in the wrong directory.
Cause: The default value of /translog caused it to be placed in the root, because of the leading slash.
Solution: Any directory that is to be placed inside another one must be specified without the slash (/), for example: translog, not /translog. Or the full path must be specified, for example: /notesdata/translog.
| < Day Day Up > |
| < Day Day Up > |
Problem: We received the following error messages (not all at once).
Server Error: Realtime Service cannot connect to external system SQL1013N The database alias name or database name "DB2DB" could not be found. SQLSTATE=42705 SQL1032N No start database manager command was issued. SQLSTATE=57019
Cause : DB2 might not be started.
Solution: Here is how to start the DB2 database manager. It assumes that you have a sample DB2 database named "sample".
Login onto your Linux guest with your DB2 user ID, such as db2inst1. If you are already logged in, issue the switch user command: su - db2inst1
Issue the command: db2start
Issue the command start dbm to start the database manager.
To see the database named sample, issue: connect to sample
To see if all the DB2 processes are running, type: ps-ef grep DB2
| < Day Day Up > |
| < Day Day Up > |
Problem: You cannot get your DECS or DCR session to connect to a database.
Cause: DECS must be running in order to communicate to DB2 with it, or with DCRs.
Solution:
You can include DECS in the list of started Domino processes in notes.ini, as follows :
ServerTasks=.....,DECS,...
If you want to start DECS manually from the Domino console, issue: load decs
To test for connectivity to DB2, complete the following steps:
Run the test program DCTEST, located in the Domino program directory. On our platform, the program directory was located in /opt/lotus/notes/latest/zlinux, the default directory. This test should be conducted using the Domino user /account ID.
Select DB2 from the program menu.
Enter the data source, user name , and password when the program prompts for them.
Choose (Y/N) whether you want detailed driver information.
You can produce a printed report for diagnostic purposes. When asked, you can choose to output to a file (Y) or not (N). If you do not choose output to a file, the results appear on your monitor.
If you chose file output, supply a name for the file, then press Enter. The program then attempts to connect to the DB2 data source.
You can retry a connection by entering: Y when prompted for another data source.
| < Day Day Up > |
| < Day Day Up > |
Problem: We were able to seemingly crash the Domino server (actually, it was locked up) by accessing LotusScript functions that did look-ups external to the server itself, but with the server's address incorrectly specified in the server doc in the NAB.
Cause: The server setup routine placed the vmlinuxa into the server doc by default. vmlinuxa was not in the DNS, and either the LotusScript interpreter or some API call could not resolve that name to the numeric IP address. This caused the server to lock up.
Solution: When we changed the entry in the server doc from vmlinuxa.itso.company.com to the numeric IP address, everything functioned properly.
| < Day Day Up > |
|
IBM Lotus Domino 6. 5 for Linux on zSeries Implementation Authors: Ebbers M. Published year: 2003 Pages: 78-81/162 |