DB2数据库SQL1366N错误处理
来源:互联网 发布:java单例模式使用场景 编辑:程序博客网 时间:2024/05/21 08:36
近日为了安全基线的检查,不停地在更新已上线系统的数据库参数设置,结果在更改了目录sqllib下的文件权限后,导致数据起停,连接等命令无法执行。
1、报错为:SQL1366N A Security plug-in "IBMOSauthclient" pfocessing error occurred on the client ,Reason code="3"。
2、研究发现:目录sqllib下security64(我的系统为64位的aix)的访问权限出现了问题。
3、解决办法:让实例用户具有访问和执行的权限。root用户登录,
chmod -R +rw /home/sjxt/sqllib/security64/plugin/IBM/client;
chmod +x /home/sjxt/sqllib/security64/plugin/IBM/client/IBMOsauthclient.a
结果上述问题解决后出现了:SQL0332N Character conversion from the source code page "1386" to the target code page "819" is not supported SQLSTATE=57017
针对这个现象的解决方法:db2set db2codepage=1386 ,
结果又出现了以下问题:DBI1306N The instance profile is not defined .
Explanation: The instance is not defined in the target machine registry.
User response: Specify an existing instance name or create the required instance.
针对这个问题,通过上网查找,发现有类似案例,现将访案例及处理方法贴如下:
APAR status
Closed as program error.
Error description
db2set throws the following error:$ db2set db2_workload=sapDBI1306N The instance profile is not defined.Explanation:The instance is not defined in the target machine registry.User response:Specify an existing instance name or create the requiredinstance.This problem can be caused by a dirty record in the DB2 globalregistry.You can list the content of the DB2 global registry with thiscommand: "<DB2DIR>/bin/db2greg -dump"If, for example, your instance is called "db2inst1" the outputwill contain a record like this:I,DB2,9.7.0.1,db2inst1,/home/db2inst1/sqllib,,1,0,/opt/IBM/v97,,The error from db2set is triggered because the InstallPathrecord (/opt/IBM/v97) is different than the path where your copyof DB2 is installed.
Local fix
Execute this command as root, where <DB2DIR> is the path whereyour DB2 copy is installed:<DB2DIR>/instance/db2iupdt <INSTANCE NAME>
Problem summary
***************************************************************** USERS AFFECTED: ** ALL ****************************************************************** PROBLEM DESCRIPTION: ** db2set throws the following error: ** ** ** ** $ db2set db2_workload=sap ** ** DBI1306N The instance profile is not defined. ** ** Explanation: ** ** The instance is not defined in the target machine registry. ** ** User response: ** ** Specify an existing instance name or create the required ** ** instance. ** ** ** ** ** ** This problem can be caused by a dirty record in the DB2 ** global ** registry. ** ** You can list the content of the DB2 global registry with ** this ** command: "<DB2DIR>/bin/db2greg -dump" ** ** If, for example, your instance is called "db2inst1" the ** output ** will contain a record like this: ** ** I,DB2,9.7.0.1,db2inst1,/home/db2inst1/sqllib,,1,0,/opt/IBM/v97* ** ** The error from db2set is triggered because the InstallPath ** ** record (/opt/IBM/v97) is different than the path where your ** copy ** of DB2 is installed. ** ** ** ** You can fix the issue by running db2iupdt against your ** instance: ** <DB2DIR>/instance/db2iupdt <INSTANCE NAME> ****************************************************************** RECOMMENDATION: ** You can fix the issue by running db2iupdt against your ** instance: ** <DB2DIR>/instance/db2iupdt <INSTANCE NAME> *****************************************************************
Problem conclusion
Problem was first fixed in Version 9.7 Fix Pack 2
具体链接见如下:http://www-01.ibm.com/support/docview.wss?uid=swg1IC67080
本人按这个案例成功解决了问题。
- DB2数据库SQL1366N错误处理
- 关于DB2数据库的ADM11003E和ADM0501C错误的处理
- DB2数据库碎片处理
- db2 备份恢复 错误处理
- DB2提示错误“数据库不一致”
- 使用DB2数据库,排序错误
- 如何处理创建DB2工具目录数据库的时候遇到的SQL1005N错误?
- [数据库][DB2]数据库对象授权处理
- db2 中出现SQL0449 错误处理
- DB2常用命令以及错误处理宝典
- DB2数据库 错误代码=错误说明
- jdbc连接db2数据库发生通信错误
- DB2数据库日期时间的处理
- 数据库8155错误处理
- FIBPlus:处理数据库错误
- DB2错误处理方案:SQL0973N,sqlstate=57011
- DB2存储过程的事务控制以及错误处理。
- 如何使用DB2条件处理器处理SQL错误
- FTP虚拟用户名模式
- Spark的广播变量和累加变量
- java--泛型擦除
- php 文件写入 文件最加内容
- vue界面传值(子父组件)
- DB2数据库SQL1366N错误处理
- Android自定义菊花进度条
- UIFont的lineHeight与pointSize
- spring框架详解(五)--AOP注解形式
- python创建数组
- O(1)快速乘
- LCD调试问题总结
- 9/15日JavaScript笔记
- kmp