IBM DB2 Commands may fail with SQL1092N when executed from db2cmd.exe on Microsoft® Windows.
Why do DB2 commands like db2start or db2stop when executed from db2cmd.exe sometimes fail with SQL1092N ?
SQL1092N is received when the requested command or operation fails because the user ID does not have the authority to perform the requested command or operation.
This may be caused due to an User Access Control feature introduced by Microsoft® Windows in Windows 2008, Windows 2012, Windows Vista and Windows 7.
On Microsoft® Windows 2008, Windows 2012, Windows Vista, and Windows 7, by default, applications start with only standard user rights, even if the user is a local administrator.
To start an application with further privileges, you should use db2cmdadmin.exe instead of db2cmd.exe .
The DB2 installation process creates a shortcut called "Command window - Administrator" in 'Start Menu > Programs > IBM DB2 > DB2COPY* > Command Line Tools'. This shortcut calls db2cmdadmin.exe internally.
Alternatively you may want to disable User Access Control feature on Windows Operating system level or you may right click on db2cmd.exe and then select 'Run as Administrator' option to execute privileged commands like db2start or db2stop from db2cmd.exe itself.
More support for:
DB2 for Linux, UNIX and Windows
Programming Interface - CLP
Software version: 9.1, 9.5, 9.7, 9.8, 10.1, 10.5
Operating system(s): Windows
Software edition: Advanced Enterprise Server, Enterprise Server, Express, Express-C, Personal, Workgroup Server
Reference #: 1662159
Modified date: 23 January 2014
Translate this page: