本文主要介绍linux环境下的安装，使用Centos7.0

1. 确认安装环境

确认安装的操作系统版本，以及是否满足安装手册中提及的安装环境。此处使用Centos 7.0，使用 7 的时候可能会有问题。

2. License申请

需要知道本机的hostname，找我们申请license,需要5分钟就可以提供license。

3. 确认内核参数

3.1.LINUX的需要更改的内核参数值：

这些值将会在后续过程中修改

semmsl 10000 /proc/sys/kernel/sem

semmns 32000

semopm 10000

semmni 10000

shmall 2097152 /proc/sys/kernel/shmall

shmmax 物理内存的一半(byte) /proc/sys/kernel/shmmax

shmmni 4096 /proc/sys/kernel/shmmni

file-max 65536 /proc/sys/fs/file-max

ip_local_port_range 1024 ~ 65000 /proc/sys/net/ipv4/ip_local_port_rang

3.2更改内核参数

修改上面的值，首先查看当前系统的参数

# sysctl –a

kernel parameter 静态变更

# vi /etc/sysctl.conf

fs.file-max = 65536

kernel.sem = 10000 32000 10000 10000

kernel.shmmax = 1073741824

激活修改

# sysctl –p #进行动态激活

3.3 安装JDK

检测系统的JDK情况，如果JDK在1.5.17以上就不用安装了，否则需要安装JDK。

检测centos是否已经安装了jdk

查看版本是否安装如下：

产生如上信息说明已经安装了JDK，安装sun公司的jdk最好将openJDK卸载。

4. 手动安装K-DB

4.1 创建组合用户

创建KDB相关用户和组，并在 home 目录下添加 kdb用户目录

# groupadd dba

# useradd -d /home/kdb -g dba -p kdb -s /bin/bash kdb

4.2 配置参数文件在.bash_profile文件中

切换到kdb用户, 在kdb的家目录(/home/kdb)中修改下面文件

[root@localhost home]# su kdb

[kdb@localhost home]$ cd /home/kdb

[kdb@localhost ~]$

# 修改KDB用户的配置文件

[kdb@localhost~]$ vi .bash_profile

# .bash_profile

# Get the aliases and functions

if [ -f ~/.bashrc ]; then

. ~/.bashrc

fi

# User specific environment and startup programs

PATH=$PATH

export PATH

####### SET JAVA ENVIRONMENT ####

export JAVA_HOME=/usr/local/java/jdk1.8.0_144

export PATH=$JAVA_HOME/bin:$PATH

##############SET KDB###################

export KD_HOME=/home/kdb/kdb11

export KD_SID=kdb

export TB_HOME=/home/kdb/kdb11

export PATH=$PATH:$KD_HOME/bin:$KD_HOME/client/bin

export LD_LIBRARY_PATH=$KD_HOME/lib:$KD_HOME/client/lib

export KD_SQLPATH=/home/kdb/kdb11

####### KDB alias ########

alias kdhome='cd $KD_HOME'

alias kdbin='cd $KD_HOME/bin'

alias kdlog='cd $KD_HOME/instance/$KD_SID/log'

alias kdcfg='cd $KD_HOME/config'

alias kdcfgv='vi $KD_HOME/config/$KD_SID.tip'

alias kdcli='cd ${KD_HOME}/client/config'

alias kdcliv='vi ${KD_HOME}/client/config/kddsn.kdr'

alias kdi='cd ~/kdinary'

alias clean='kddown clean'

alias dba='kdsql sys/kdb'

alias tracef='tail -f $KD_HOME/instance/$KD_SID/log/tracelog/trace.log'

设置完成，将设置生效

[kdb@localhost~]$ source .bash_profile

4.3 开始安装数据库

CP 安装文件和license.xml 到安装的目录(kdb用户的.bash_profile中设置的KD_HOME)并更改权限

[kdb@localhost~]$ tar -xvf inspur-bin-kdb-linux64-91694-opt-tested.tar

kdb11/bin/alterdd.sh

kdb11/bin/kdprof

kdb11/client/win32/bin/kdodbc_driver_installer_11_32.exe

kdb11/client/win32/lib/EntLibContrib.Data.Inspur.dll

kdb11/client/bin/kderr

kdb11/client/bin/gw4db2_v9

kdb11/client/bin/kdMigrator2.zip

kdb11/scripts/pkg/pkg_dbms_alert.sql

kdb11/scripts/pkg/_pkg_dbms_metadata.tbw

kdb11/scripts/pkg/func_xmlidx.sql

kdb11/license/oss_licenses/Apache_v2.txt

kdb11/nls/zoneinfo/timezone_be.dat

kdb11/nls/zoneinfo/timezone_le.dat

4.4 生成参数文件及监听文件

首先即切换到KDB的安装目录

[kdb@localhost~]$ cd $KD_HOME/config

接着执行如下命令

[kdb@localhostconfig]$ ./gen_tip.sh

Using KD_SID "kdb"

/home/kdb/kdb11/config/kdb.tip generated

/home/kdb/kdb11/config/psm_commands generated

/home/kdb/kdb11/client/config/kddsn.tbr generated.

Running client/config/gen_esql_cfg.sh

Done.

如果继续默认安装，则数据文件就会被安装在KD_HOME下的database目录下面，这里我们增加一个参数使数据文件日志控制文件都安装在这个目录下，便于修护。

[kdb@localhost~]$ pwd

/home/kdb

[kdb@localhostinspur]$ mkdir kddata

[kdb@localhost~]$ cp license.xml $KD_HOME/license/

[kdb@localhost~]$ cd $KD_HOME/config

[kdb@localhostconfig]$ vi kdb.tip

DB_NAME=kdb

LISTENER_PORT=8629

# 修改部分

CONTROL_FILES="/home/kdb/kddata/c1.ctl"

#CERTIFICATE_FILE="/home/kdb/inspur/config/svr_wallet/kdb.crt"

#PRIVKEY_FILE="/home/kdb/inspur/config/svr_wallet/kdb.key"

#WALLET_FILE="/home/kdb/inspur/config/svr_wallet/WALLET"

MAX_SESSION_COUNT=20

TOTAL_SHM_SIZE=512M

MEMORY_TARGET=1G

# 添加部分

DB_CREATE_FILE_DEST="/home/kdb/kddata"

4.5 启动数据库到nomount阶段

[kdb@localhostconfig]$ kdboot nomount

Listener port = 8629

Inspur K-DB 1 SP1

Inspur K-DB instance started up (NOMOUNT mode).

在运行的过程中可能会遇到如下错误提示

kdsvr: error while loading shared libraries: libkdclnt.so: cannot open shared object file: No such file or directory

这有可能是因为在root与kdb来回切换的过程中 `bash_profile` 失效，这是可以重新让文件生效基本上就可以解决

source ~/.bash_profile

4.6 建库

按照上述的方式启动之后，就需要连接 kdb 进行数据库创建

[kdb@localhostconfig]$ kdsql sys/kdb

kdSQL 1 SP1

Connected to Inspur K-DB.

接下来在 SQL 命令下进行数据的创建

SQL>

create database "kdb" --数据库名

user sys identified by kdb --sys的密码

maxinstances 8

maxdatafiles 1024

character set UTF8

NATIONAL CHARACTER SET UTF16

logfile group 1 ('redo11.log')

size 1024M,

group 2 ('redo21.log')

size 1024M,

group 3 ('redo31.log')

size 1024M

maxloggroups 255

maxlogmembers 8

archivelog

datafile 'system01.dtf'

size 1024M

DEFAULT TABLESPACE USR

datafile 'usr01.dtf'

size 1024M

DEFAULT TEMPORARY TABLESPACE TEMP

tempfile 'temp01.dtf' size 4096M

extent management local autoallocate

undo tablespace UNDO0

datafile 'undo00.dtf'

size 4096M

extent management local autoallocate;

在常见的过程中可能会遇到 `c1.ctl` 无法创建的问题

TBR-1001: Unable to create file /home/kdb/kddata/c1.ctl.

这个可能是因为，在第一次创建的时候没有成功，但是 `c1.ctl` 已经存在的，因此只需要将之前的文件删除即可。

4.7 启动数据库到OPEN阶段

退出SQL名利机界面

SQL> exit

Disconnected.

正常启动kdb

[kdb@localhostconfig]$ kdboot

Listener port = 8629

Inspur K-DB 1 SP1

Inspur K-DB instance started up (NORMAL mode).

4.8 执行system.sh脚本生成数据库所需要的数据字典

切换到脚本目录，然后运行 `system.sh` 脚本

[kdb@localhostconfig]$ cd $ KD_HOME/scripts

[kdb@localhostscripts]$ ./system.sh

Enter SYS password:

kdb # 此密码一定要和创建数据库时的密码一样

Enter SYSCAT password:

syscat # 此处的密码一定要输入syscat

Creating the role DBA...

Create default system users & roles?(Y/N):

y

Creating system users & roles...

Creating virtual tables(1)...

Creating virtual tables(2)...

Granting public access to _VT_DUAL...

Creating the system generated sequences...

Creating internal dynamic performance views...

Creating outline table...

Creating system tables related to dbms_job...

Creating system tables related to dbms_lock...

Creating system packages:

Running /home/kdb/kdb11/scripts/pkg/pkg_standard.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_standard_extension.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_seaf.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_debug_jdwp.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_expression.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_xmlgen.sql...

Creating packages for sql:

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_types.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_sql.sql...

Creating packages for verification:

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_verify.sql...

Creating public synonyms for system packages...

Creating auxiliary tables used in static views...

Create system tables related to profile?(Y/N):

y

Creating system tables related to profile...

Creating static views...

Creating static view descriptions...

Creating system tables related to statistics...

Creating packages for statistics:

Running /home/kdb/kdb11/scripts/pkg/pkg_sys_util.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_stats_internal.sql...

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_stats.sql...

Register dbms_stats job to Job Scheduler?(Y/N):

y

Registering dbms_stats job to Job Scheduler...

Creating packages for log errors:

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_errlog.sql...

Creating packages for mview:

Running /home/kdb/kdb11/scripts/rewrite_table.sql...

Creating packages for text:

Running /home/kdb/kdb11/scripts/pkg/pkg_text.sql...

Creating remaining public synonyms for system packages...

Running /home/kdb/kdb11/scripts/iparam_desc_gen.sql...

Running /home/kdb/kdb11/scripts/trace_event_desc_gen.sql...

Creating dynamic performance views...

Creating dynamic performance view descriptions...

Check APM status..

Stop APM

Create APM tables?(Y/N):

y

Dropping tables used in APM...

Creating auxiliary tables used in APM...

Replenish APM Tables if Updates Exist

Creating internal system tables...

Creating packages for sph:

Running /home/kdb/kdb11/scripts/pkg/pkg_dbms_sph.sql...

Done.

For details, check /home/kdb/kdb11/instance/kdb/log/system_init.log.

检查是否启动

[kdb@kdbdomain scripts]$ ps -ef |grep kdsvr

kdb 1755 1 0 00:04 pts/0 00:00:00 kdsvr -t NORMAL -SVR_SID kdb

kdb 1757 1755 0 00:04 pts/0 00:00:00 kdsvr_TBMP -t NORMAL -SVR_SID kdb

kdb 1758 1755 6 00:04 pts/0 00:00:14 kdsvr_WP000 -t NORMAL -SVR_SID kdb

kdb 1759 1755 0 00:04 pts/0 00:00:00 kdsvr_WP001 -t NORMAL -SVR_SID kdb

kdb 1760 1755 0 00:04 pts/0 00:00:00 kdsvr_AGNT -t NORMAL -SVR_SID kdb

kdb 1761 1755 0 00:04 pts/0 00:00:00 kdsvr_DBWR -t NORMAL -SVR_SID kdb

kdb 1762 1755 0 00:04 pts/0 00:00:00 kdsvr_RECO -t NORMAL -SVR_SID kdb

kdb 2764 1471 0 00:08 pts/0 00:00:00 grep kdsvr

检查数据库是否正常

[kdb@kdbdomain scripts]$ kdsql sys/kdb

SQL> ls

HS$_FDS_CLASS_DATE_UK1 INDEX

HS$_FDS_CLASS_PK INDEX

HS$_FDS_CLASS_UK1 INDEX

HS$_FDS_INST_PK INDEX

...

_SYS_CONTEXT TABLE

_TPR_ACTIVE_SESSION_HISTORY TABLE

_TPR_BASELINE TABLE

_TPR_FILESTAT TABLE

_TPR_FILESTAT_SAVE TABLE

...

_SCHEDULER_CHAIN_STEPS_INTERNAL VIEW

_SCHEDULER_OBJECTS_INTERNAL VIEW

_SCHEDULER_RULE_CTX_INTERNAL VIEW

_SCHEDULER_STEP_CTX_INTERNAL VIEW

看到以上信息说明数据库创建成功。

注意：如果有信息，则说明执行成功；如果没有，则不成功，重新执行sytem.sh即可，其中安装可以查看system_init.log。平时的数据库运维只要查看下面的日志。

[kdb@localhos]$tail -f $KD_HOME/instance/$KD_SID/log/tracelog/trace.log