要测试db2 cli是否可以执行相同的SQL语句（即独立于C#和独立于.net core），您可以复制并修改下面的脚本，方法是从凭据json文件（或您收到连接字符串详细信息的任何地方）复制主机名、用户名、口令和端口号。
如果您的连接未使用SSL/TLS加密，请修改脚本以从数据库和下面的dsn定义中删除Security=SSL参数，并使用正确的非SSL端口号。
如果您的密码包含了任何被您的linux shell认为是特殊的字符，在脚本中指定下面的密码变量时，请用反斜杠\转义每个这样的特殊字符。否则，您将得到SQL 30082 N reason“24”。
修改此文件后，使用chmod +x组合键修改该文件，然后运行它。

# !/bin/bash

# 

# populate db2dsdriver.cfg for Db2-on-cloud lite and verify db2cli connects and runs SQL statements.

# 

# Prereq: (1) an IBM Db2 CLI driver is already installed and on the PATH for current userid.

# Prereq: (2) the version of the CLI driver matches the version of the Db2-lite instance (per the UI dashboard)

# Prereq: (3) after you modify this file, remember to `chmod +x` this file before running it.

# 

# This script works with clidriver , with the Db2 runtime client, with the Db2 data server client (fat client).

# Can re-run this script, overwrites current matching entries in db2dsdriver.cfg (if exists) else creates that file.

# 

# For IBM Db2-on-cloud (lite plan ,  kostenlos ).

# Configure the db2dsdriver.cfg file for use with db2cli tool to connect to Db2-on-cloud from command-line bash.

# 

# You must modify the variable-values below by copying username, password, port, hostname from your credentials json file.

# And remember to escape ( precede with \) any and all special-character in password, otherwise connect will fail.

# 

# Note 1: this expects the Db2-on-cloud hostname to have SSL/TLS encrypted-connections to BLUDB which is the default

# for all IBM Db2-on-cloud hostnames ending with pattern *appdomain.cloud

# 

# Note 2: at clidriver version 11.5.6.0 , db2cli tool can return exit-code 0 even on failure, doh!

# 

# Note 3: to get your username and password, host and port-number , download the credentials json file and view it to see them.

# Then copy their values into the appropriate variables below before making this script executable and run it.

# 

set -u

typeset which=/usr/bin/which
typeset db2cli=$( ${which} db2cli )
        [[ -z ${db2cli:=""} ]] && print "\nERROR: please either  dot in a db2profile to allow db2cli to be on the PATH\nor edit your PATH environment variable to put the clidriver/bin directory on the PATH" && exit 1

typeset dbname=bludb   # default database-name for Db2-on-cloud lite plan shared databases.
typeset hostname="change me"
typeset ssl_port_number=32733  # from credentials json
typeset password="change me"  # remember to escape \ any special characters here, copy from credentials json file.
typeset username="change me"  # copy from credentials json file.
typeset dbalias=bludb # you can use whatever alias-name you like, 8 bytes long max
typeset input_sql_tmpfile=/tmp/db2cli_inputsql.sql

${db2cli} writecfg add -database ${dbname} -host ${hostname} -port ${ssl_port_number} -parameter Security=SSL
rc=$?
(( rc > 0 )) && print "\nERROR: failed to write the database to the config file\n" && exit 1

${db2cli} writecfg add -dsn ${dbalias} -database ${dbname} -host ${hostname} -port ${ssl_port_number} -parameter Security=SSL
rc=$?
(( rc > 0 )) && print "\nERROR: failed to write the dsn to the config file\n" && exit 1

${db2cli} validate -dsn ${dbalias} -connect -user ${username} -passwd ${password}
rc=$?
(( rc > 0 )) && print "\nERROR: failed to connect to the dsn with supplied credentials\n" && exit 1

# Verify that the db2cli tool can run some SQL statements by putting them into a file and passing the file to db2cli

# create an inputfile containing SQL statements ( make a temp file for this purpose)

# note that the default statement delimiter for db2cli is crlf (or lf on linux) not semicolon as with db2clp.

echo "values current timestamp" > ${input_sql_tmpfile}
echo "values current server" >> ${input_sql_tmpfile}
echo "values current user" >> ${input_sql_tmpfile}

${db2cli} execsql -execute -dsn ${dbalias} -user ${username} -passwd ${password} -inputsql ${input_sql_tmpfile}