Troubleshooting

This chapter describes how to troubleshoot some errors that may occur as a result of an incorrect installation properties file.

1. Overview

There are three ways to identify an error that may occur during Batch installation.

Open the ${OPENFRAME_HOME}/UninstallerData/log/install_batch.log file with a text editor.
Review the error logs information recorded during manual execution of the script after the Batch installation.
Check the server status logs information displayed during OpenFrame startup check.

For more information about installation properties file, refer to Creating an Installation Properties File.
For more information about error codes, refer to OpenFrame Error Message Reference Guide.

2. Error Type and Solution

This section describes the most frequently occurring errors during Batch installation as a result of an incorrect properties or license file and their solutions.

2.1. License File

If license files are not found or corrupted, or when the licenses have expired, the following errors may occur.

Problem Types
- No Tmax license file
  
  When running the batch_init.sh file, the following error occurs.
  (E) CFL2141 failed to read license file : /home/oframe/OpenFrame/core/license/license.dat [COM0900]
- Expired Tmax license file
  
  When running the batch_init.sh file, the following error occurs.
  (E) CFL2145 License is expired : [COM0906]
- Corrupted Tmax license file
  
  When running the batch_init.sh file, the following error occurs.
  (E) CFL2142 Corrupt license file : /home/oframe/OpenFrame/core/license/license.dat [COM0902]
- None or wrong Batch product license
  
  When starting OpenFrame, the corresponding module server cannot properly run. Also, when checking the server status by using tmadmin, the server is marked as NRDY.
  
  Execute tmadmin first and then the si command to check if the server is operating normally. For more information, refer to Verifying the Installation.
Solutions

If Batch product license files are not found or corrupted, you can identify the root causes by viewing the log file for the corresponding server process. For example, if the lictjes.dat file, a Batch license file, becomes corrupted, the obmjinit server does not operate properly. In this case, you can find the following error information in "obmjinit<execution_date>.err" log file under the ${OPENFRAME_HOME}/core/log/ulog directory.
```
>> U 2015-07-05 13:14:46 [NODE1:OBMJINIT:1134860:tlic.c:567]
(CHK0001) /home/oframe/OpenFrame/license/lictjes.dat file open fail: 2
>> E 2015-07-05 13:14:46 [NODE1:OBMJINIT:1134860:obmjinit.c:58]
(JES1040E) invalid license. contact the publisher.
(I) SVR3016 SVR obmjinit (13/45) tpsvrinit fail. [SVR0027]
```

2.2. Shared Memory

If shared memory key values are redundant, the following error may occur.

Problem Type: ALC0001E

When running tmboot after installing Batch, the server may not operate properly as the following error occurs.

[ALC0001E] cannot get DATASET_SHMKEY value from config subject 'ds' - rc=-22208
[JES2070E] dsalc initialization failed. rc=-22208.
[JES6001E] svrinit failed. rc=-22208.

Solutions

Modify the shared memory key value specified in the installation properties file and then retry the installation, or find the value in the TMAX config file under the ${OPEN FRAME_HOME}/core/config directory to modify the value and then manually apply the key.

The following example manually applies the TMAX shared memory key.
```
# vi $OPENFRAME_HOME/core/config/oframe.m
*DOMAIN
domain
SHMKEY = 38001
# $TMAXDIR/bin/pfmtcacheadmin -d
# $TMAXDIR/bin/pfmtcacheadmin -c

# vi $OPENFRAME_HOME/core/config/pfmtcache.cfg
* the configuration file of TCACHE
SHMKEY=39082
# $TMAXDIR/bin/cfl -i $TMAXDIR/config/oframe.m
```

2.3. Database

If the database connection information is incorrect, the following error may occur.

Problem type

When running the installer with incorrect ODBC connection information, the following error occurs during the installation.
```
[E] [COM0020E] ofcom_odbc: SQLConnect failed. State: IM002, Native Error: -2048, Message: [unixODBC] Data source was not found.
```
Solutions

If this error occurs when running the script, correct the ODBC connection information and then reinstall OpenFrame.