Troubleshooting
Problem
How to resolve 'SQL1042C' with EPERM (1) "Not owner" on 'db2start'
Symptom
1. 'db2start' fails on command line.
$ db2start
06/25/2016 14:41:33 0 0 SQL1042C An unexpected system error occurred.
SQL1032N No start database manager command was issued. SQLSTATE=57019
2. There is following pattern error on db2diag.log.
FUNCTION: DB2 UDB, oper system services, sqloWatchDogSetup, probe:35
MESSAGE : ZRC=0x83000001=-2097151999
CALLED : OS, -, initgroups
OSERR : EPERM (1) "Not owner"
....
Cause
'db2sysc' file does not have SUID permission.
Diagnosing The Problem
Check file permission of 'db2sysc'.
Go to "{DB2 instance directory}/sqllib/adm" and run 'ls -l db2sysc'.
Good case :
$ ls -l db2sysc
-r-sr-s--- 1 root db2iadm 360386 Jun 09 2015 db2sysc
Bad case :
-r-xr-xr-x 1 root db2iadm1 334823 Feb 19 23:25 db2sysc
or
-r-xr-x--- 1 root db2iadm 360386 Jun 09 2015 db2sysc
Resolving The Problem
1. update DB2 instance.
(By 'root' user)
{DB2 installation directory}/instance/db2iupdt <db2 instance name>
2. In a urgent case that db2iupdt can't be done right away,
change the permission with 'root' user manually.
For example,
1. This has problem
-r-xr-x--- 1 root db2iadm 360386 Jun 09 2015 db2sysc
2. Add SUID permission
chmod u+s db2sysc
chmod g+s db2sysc
3. Fixed permission.
$ ls -l db2sysc
-r-sr-s--- 1 root db2iadm 360386 Jun 09 2015 db2sysc
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21986081