装置Linux下DB2的装置效果SQLSTATE57019装置
装置 目次 效果 空间 内存 过程 大年夜 系统 篇文章 号令 序列号 差错 属性 异常 当时 发生 版本 站点 文件 方法 网上
LinuxXia∴DB2De∴Zhuang∴Zhi∴Xiao∴Guo∴SQLSTATE57019因为该版本没法篡改装置目次!默许装置正在/opt下!空间给/目次!或者许特地为/opt分派空间
装置过程无任何异常!可是装置结束后!施行db2start出错
2.查找辅佐db2 SQL1220N发觉能够是共享内存设置少了有以下倡议
On Linux 32-bit! increase the kernel parameter shmmax to 256 MB. On Linux 64-bit! increase the kernel parameter shmmax to 1GB.
用ipcs -l号令看了壹下系统建设
------ Shared Memory Limits --------
max number of segments = 4096
max seg size = 3939665
max total shared memory = 4G
min seg size = 1
系统有4G的最大年夜共享内存
db2licm -l 检查!db2序列号为永久的!不过期
这个改正了以后还是没法发动
网上搜寻IBM站点有这么壹篇文章提到了这个效果的处理方法
Problem
This technote provides troubleshooting methods for when you attempt to start an instance and encounter the following error: SQL1220N The database manager shared memory set cannot be allocated.
Cause
One possibility is that during the creation of the instance the file sqllib/.ftok was not created.
DB2 was unable to allocate its shared memory set.
Solution
A quick work-around is to use the executable db2ftok to create a new seed file sqllib/.ftok. The .ftok file is generated based on the current time and other information. When starting the instance! DB2 reads the .ftok file and creates a standard interprocess communication key which is later supplied to other subroutines for memory allocation.
After the .ftok file has been created! issue the db2start command again.
Please note that in order to determine the reason why the .ftok file was absent in your particular environment! contact DB2 UDB Support and submit a problem record.
依照其说明!施行db2ftok!再db2start!Ok
效果回忆效果处理以后!回过甚来剖析!能够是/opt空间属性有效果!招致装置过程当中不克不及发生.ftok文件!因为装置完成后!施行 db2start!提醒无权施行!当时改正了目次属主为db2inst1就可以够施行了!然后就出现了下面的差错
因为该版本没法篡改装置目次!默许装置正在/opt下!空间给/目次!或者许特地为/opt分派空间 装置过程无任何异
飞扬黑客网 http://www.gdwkb.cn
LinuxXia∴DB2De∴Zhuang∴Zhi∴Xiao∴Guo∴SQLSTATE57019因为该版本没法篡改装置目次!默许装置正在/opt下!空间给/目次!或者许特地为/opt分派空间
装置过程无任何异常!可是装置结束后!施行db2start出错
2.查找辅佐db2 SQL1220N发觉能够是共享内存设置少了有以下倡议
On Linux 32-bit! increase the kernel parameter shmmax to 256 MB. On Linux 64-bit! increase the kernel parameter shmmax to 1GB.
用ipcs -l号令看了壹下系统建设
------ Shared Memory Limits --------
max number of segments = 4096
max seg size = 3939665
max total shared memory = 4G
min seg size = 1
系统有4G的最大年夜共享内存
db2licm -l 检查!db2序列号为永久的!不过期
这个改正了以后还是没法发动
网上搜寻IBM站点有这么壹篇文章提到了这个效果的处理方法
Problem
This technote provides troubleshooting methods for when you attempt to start an instance and encounter the following error: SQL1220N The database manager shared memory set cannot be allocated.
Cause
One possibility is that during the creation of the instance the file sqllib/.ftok was not created.
DB2 was unable to allocate its shared memory set.
Solution
A quick work-around is to use the executable db2ftok to create a new seed file sqllib/.ftok. The .ftok file is generated based on the current time and other information. When starting the instance! DB2 reads the .ftok file and creates a standard interprocess communication key which is later supplied to other subroutines for memory allocation.
After the .ftok file has been created! issue the db2start command again.
Please note that in order to determine the reason why the .ftok file was absent in your particular environment! contact DB2 UDB Support and submit a problem record.
依照其说明!施行db2ftok!再db2start!Ok
效果回忆效果处理以后!回过甚来剖析!能够是/opt空间属性有效果!招致装置过程当中不克不及发生.ftok文件!因为装置完成后!施行 db2start!提醒无权施行!当时改正了目次属主为db2inst1就可以够施行了!然后就出现了下面的差错
因为该版本没法篡改装置目次!默许装置正在/opt下!空间给/目次!或者许特地为/opt分派空间 装置过程无任何异
飞扬黑客网 http://www.gdwkb.cn
