Skip to main content

Search

Welcome to Tibero GTS!

Syntax error at line 76 occurs when running cepa_control

Document Type | Troubleshooting

Category | Monitoring/Inspection

Applicable Product Versions | 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS

Document Number | TMOTI005

 

Issue 

When running $TB_HOME/client/bin/cepa_control, the following syntax error at line 76 occurs. 

$ ps aux | grep tbepa
tibero 35259440  0.0  0.0 59604 59840      - A    10:52:42  0:00 tbepa 44 1 77

$ sh $TB_HOME/client/bin/cepa_control -d -p 35259440
$TB_HOME/client/bin/cepa_control[25]: syntax error at line 76 : `=~' unexpected
Note
When using the c external procedure, cepa_control is used to check the tbepa process that starts, for memory allocator dump and log level changes. 

 

 

Cause

The $TB_HOME/client/bin/cepa_control used for memory allocator dump and log level changes is a script written in bash shell syntax.
Therefore, if bash shell is not installed on the OS, the cepa_control script written in bash shell syntax will cause a syntax error and will not execute.
$ vi $TB_HOME/client/bin/cepa_control
  1 #!/bin/bash
  2 
  3 print_usage ()
  4 {
  5     echo ""
  6     echo "Usage: cepa_control [-h] [OPTION] "
  7     echo ""
  8     echo "  -h, --help          : show help"
  ...omitted

 

 

Solutions

Proceed after installing bash shell on the OS. 

Case 1. Using cepa_control

When using cepa_control, the option behavior and execution order of the $TB_HOME/client/bin/cepa_control script are as follows.
  1. -p {tbepa pid} : Creates 'tbepa_{tbepa pid}.ctl' in $TB_HOME/client/tbepa.
  2. -l [1~5] : Adds 'LOG_LVL=[1~5]' content to 'tbepa_{tbepa pid}.ctl'.
  3. -d : Adds 'DUMP_EPAALLOC=Y' content to 'tbepa_{tbepa pid}.ctl'.
  4. When 'kill -s SIGUSR1 {tbepa pid}' is executed, log level change and memory allocate dump are performed according to the contents written in 'tbepa_{tbepa pid}.ctl'.
 

Case 2. Not using cepa_control

You can manually create $TB_HOME/client/tbepa/tbepa_{tbepa pid}.ctl, write settings corresponding to options, and send SIGUSR1 signal to {tbepa pid} to achieve the same result without using cepa_control. 

$ touch $TB_HOME/client/tbepa/tbepa_35259440.ctl 

$ echo 'LOG_LVL=5' > $TB_HOME/client/tbepa/tbepa_35259440.ctl


$ echo 'DUMP_EPAALLOC=Y' >> $TB_HOME/client/tbepa/tbepa_35259440.ctl


$ cat $TB_HOME/client/tbepa/tbepa_35259440.ctl
  DUMP_EPAALLOC=Y
  LOG_LVL=5


$ kill -s SIGUSR1 35259440


$ ls -al $TB_HOME/client/tbepa
total 3
drwxr-xr-x 3 tibero dba 4096 May 9 17:09 .
drwxr-xr-x 9 tibero dba 4096 Feb 25 16:33 ..
-rw-r--r-- 1 tibero dba   82 May 9 17:09 tbepa.log_20250509170806_35259440.log
-rw-r--r-- 1 tibero dba   26 May 9 17:09 tbepa_35259440.ctl
drwxr-xr-x 2 tibero dba 4096 May 9 17:09 tracedump
*tbepa log is generated at log level 5


$ ls -al $TB_HOME/client/tbepa/tracedump
total 2
drwxr-xr-x 2 jin dba 4096 May 9 17:09 .
drwxr-xr-x 3 jin dba 4096 May 9 17:10 ..
-rw-r--r-- 1 jin dba 2033 May 9 17:09 epa_pga_35259440_20250509170931.dump
*tbepa memory allocator dump is generated
 

 

 

 

 

Related to