SQL1092N "USER" does not have the authority to perform the requested operation

Installing DB2 on machine using a domain account could at times leave that particular domain account from having rights to perform actions like CREATE, UPDATE, etc., 

The reason being, if a user logs on to a domain account and tries to access a DB2 database, DB2 goes to a Domain Controller to enumerate groups (including the Administrator's group). You can change this behavior in either of two ways:

1. Set the registry variable DB2_GRP_LOOKUP = local and add the domain accounts (or global groups) to the local Administrators group.

DB2SET DB2_GRP_LOOKUP=LOCAL
DB2STOP
DB2START

2. Update the database manager configuration file to specify a new group. If you want that group enumerated on the local machine, then you must also set the DB2_GRP_LOOKUP registry variable.

By default in a Windows NT domain environment, only domain users that belong to the Administrators group at the Primary Domain Controller (PDC) have SYSADM authority on an instance. Since DB2 always performs authorization at the machine where the account is defined, adding a domain user to the local Administrators group on the server does not grant the domain user SYSADM authority to the group. So to do that, run the following commands

DB2 UPDATE DBM CFG USING SYSADM_GROUP <global_group> 
DB2STOP
DB2START

Note : global_group named DB2ADMNS would have got created on the local machine, had you chosen the option to enable administrative security while installing DB2. Use the same group, else use any of the global groups in your network.

You have tried the above mentioned steps and you still end up seeing the same error message, the following commands might help (it does most of the times)

Run the db2set like below, to see if the DB2_GRP_LOOKUP registry value is set properly. 

C:\IBM\SQLLIB\BIN>db2set -all

[e] DB2PATH=C:\IBM\SQLLIB

[i] DB2_USE_ALTERNATE_PAGE_CLEANING=ON

[i] DB2_INLIST_TO_NLJN=YES

[i] DB2_REDUCED_OPTIMIZATION=YES

[i] DB2INSTOWNER=MAGNETO

[i] DB2PORTRANGE=60000:60003

[i] DB2_GRP_LOOKUP=LOCAL
[i] DB2INSTPROF=C:\PROGRAMDATA\IBM\DB2\DB2COPY1
[i] DB2COMM=TCPIP
[g] DB2_EXTSECURITY=YES
[g] DB2_COMMON_APP_DATA_PATH=C:\ProgramData
[g] DB2SYSTEM=MAGNETO
[g] DB2PATH=C:\IBM\SQLLIB
[g] DB2INSTDEF=DB2
[g] DB2ADMINSERVER=DB2DAS00

Now append the value TOKENLOCAL to the DB2_GRP_LOOKUP registry entry like below. This works like magic most of the times.

DB2SET DB2_GRP_LOOKUP=LOCAL,TOKENLOCAL

DB2STOP

DB2START

The above steps should have helped you see through the error. If the error still persists, reboot the machine and retry all the steps. 

NullPointerException and Java

When I first started programming in Java, that was like few years ago, with the little background that I had of C the first thing I learnt was, Java does not have Pointers

Why doesn't it have Pointers?
Structures were removed and gone, and arrays and strings are objects, the need for pointers to these constructs goes away.

Why Structures were removed?
You don't need structures and unions when you have classes; you can achieve the same effect simply by declaring a class with the appropriate instance variables.

So now we have enough reasons as to why Java didn't have Pointers.

Having said that it makes me wonder why is there an exception called NullPointerException when there is no Pointer in Java. I am very sure the Java developers would have some reason to have named this the way it is today. May be they could have named it NullReferenceException. But obviously they didn't. The following are my guesses as to why it can still be called so

• Its not that Java does not have Pointers
• In fact every reference in Java is ideally a Pointer (except for primitive types)
• Its just that Java doesn't support Pointer arithmetic

Being an Engineer

Shift from a being a DEV guy, to becoming an ENGINEERING guy is something that not everyone would prefer to do. Why? For the simple reason, not many people understand what an ENGINEERING guy does. People see ENGINEERS as TESTERS, Black Box testers, and to them being a tester is being below their dignity level. For even, I thought so during my initial days of IT. I was too naive and I didn't know what role the testers played.

But after having treaded the road for about FOUR good years I stand in a position where I can see the point in needing/being a tester and there is nothing to be ashamed about it. But for testers, developers would be in soup, deep soup. I am not kidding. Assume a product/solution is being delivered without passing the QA(Quality Assurance). Of-cos, it was shipped after all the unit test cases developed by the developers passed and they were quite satisfied the product/solution is bug free. What the developers fail to do is to come up with use cases that are more likely the customers come up with. Putting it in simple terms they focus more than the positive scenarios and give a little attention to the negative scenarios. From the customers point of view, even something as trivial as a spelling mistake in the ack or error message is unacceptable and it would get escalated. When a bug is raised by the customer, the developer would be the one who will have to face the hot seat. I am sure, no developer would want himself to be placed there. Trust me, its not a pleasant experience being there.

This is where someone with a different perspective becomes necessary. The someone who can think beyond specifications of the application and try simulating real time scenarios. And this someone is ideally an ENGINEER/TESTER. Well, I am not going to discuss more about TESTER, because I am still not very sure as to what exactly his role would be. Now that I have been an ENGINEER for about an year, I can throw enough light on what it is like being one. First, an Engineer is not only a Tester. An Engineer should be aware of the technology being used in the product/solution that needs to be tested which a Tester can be least bothered about. Engineers primary responsibility is to break what the developer builds. What I call as "Breaking the Code". This means, an Engineer has to code to break the code. So being an engineer gives the exposure to both paradigms of software building, "cranking" and "breaking". An Engineer also tests the coverage of the code developed. Additionally an engineer should find ways in which the test execution environment can be automated. This means an Engineer gets exposed to build frameworks and automation tools. In short, being an Engineer involves more than just testing the product/solution.

Blat - A mailing utility

Often developers/testers come across scenarios where in they have to notify a team once a deployment or build is complete. There are many build management tools that provide us with such an option. There could be scenarios where in Maven or Ant is used for building purpose. In such scenarios emailing options should be considered through a third party tool. One such tool is "BLAT"

Blat is a Win32 command line utility that sends eMail using SMTP or post to usenet using NNTP. SMTP being the protocol that we use for email communication, Blat provides us with the option to send mails to the intended recipients.

Doing it the ANT way

Assuming your build process is setup using Ant and the last step that you want to do is to send an email. This is how to write an Ant target to achieve the same

  <target name="email-report">
         <exec dir="${basedir}"
          executable="${basedir}/../thirdparty/blat/blat.exe"
          os="Windows XP,Windows 2000,Windows 2003,Windows Server 2003,Windows Server 2008">
               <arg file="<location of the file you want to send as an attachment if any>"/>
               <arg line="-to <email address of the recipient>"/>
               <arg line="-f  <email address of the sender>"/>
               <arg line="-server <the SMTP server address>"/>
               <arg line="-i <email alias name>"/>
               <arg line="-s <'your subject within single quotes'>"/>
         </exec>

  </target>

Doing it the BAT way

Suppose if you have automated ur build process using batch script invoking specific goals or target and would like to also trigger mails from the batch, here is how you go about it.

<Location where blat is installed>\blat.exe "Attachment if any" -to "Recipient Email address" -f "Senders Email address" -i "Sender Email Alias" -s "Subject Line" -server "SMTP Server address"

This is a very simple email utility that not many of us know about. Happy mailing :)

Wanna change network settings to work at different locations?

People working with laptops might have to swap the network settings depending on the location they work at. Normal usage being at Home and at Work. At work places these settings are normally defined by the DHCP and at home its a STATIC source most of times.

I have come up with a batch script using which you can switch between these network settings without having to change them manually whenever your work location changes. All that has to be done to copy the below script into a file and name it *.bat and just double click it. You might have to key in your work location as an arg when you run this.

Don't forget to define the following variables varip, varsm, vargw, vardns1 and  vardns2 with your network specific entries. (Your service provider must have provided you with these entries)

 ******** COPY THE SOURCE BELOW ********

@ECHO OFF

ECHO Change network setting for (Home/Work)?

set/p "cho=>"

if %cho%==Home goto HOME
if %cho%==HOME goto HOME
if %cho%==Work goto WORK
if %cho%==WORK goto WORK

:HOME
set varip=

set varsm=

set vargw=

set vardns1=

set vardns2=

REM ***** You don’t need to change anything below this line! ******

ECHO Setting IP Address and Subnet Mask

netsh int ip set address name = "Local Area Connection" source = static addr = %varip% mask = %varsm%

ECHO Setting Gateway

netsh int ip set address name = "Local Area Connection" gateway = %vargw% gwmetric = 1

ECHO Setting Primary DNS

netsh int ip set dns name = "Local Area Connection" source = static addr = %vardns1%

ECHO Setting Secondary DNS

netsh int ip add dns name = "Local Area Connection" addr = %vardns2%

GOTO DISPLAY

:WORK

ECHO Setting IP Address

netsh int ip set address name = "Local Area Connection" source = dhcp

ECHO Setting DNS

netsh int ip set dns name = "Local Area Connection" source = dhcp

GOTO DISPLAY

:DISPLAY

ECHO Here are the new settings for %computername%:

netsh int ip show config

pause.

Code Coverage with Maven 1.x / Cobertura

Many a times developers tend to compromise on testing every line and branch of code they crank. It becomes important that source files do not become cluttered with source lines that never gets invoked during the runtime.There goes a saying "Uncovered Code = Undiscovered Defects"

Of the three coverage tools I have used, JCoverage, Clover and Cobertura, I feel cobertura makes things simpler just for the fact it can be integrated with Ant and Maven without much of effort to generate coverage reports. In this post I shall explain how to generate a coverage report using Cobertura and Maven 1.x for a simple source file with three basic operations like add, subtract and delete.

1. Create a source file with the basic operations you need

public class Operator {
   
    public Integer add(int a, int b) {
        Integer sum = null;
        sum = a + b;
        return sum;
    }
   
    public Integer subtract(int a, int b) {
        Integer diff = null;
        diff = a - b;
        return diff;
    }
   
    public Double divide(double a, double b) {
        Double quotient = null;
        quotient = a / b;
        return quotient;
    }
}

 2. Export the source file you just created as a JAR(Java Archive) so that it can be used as a dependency while running the test class. Don't forget to place this archive into your maven repository. (For this example I have placed this jar under the artifactId sample-cobertura)

3. Create a test class to test the operations. I used JUnit 3.8.1 to create the test class as shown below

public class OperatorTest extends TestCase {

    private static Operator operator = null;
    public static Test suite() {
        final TestSuite suite = new TestSuite(OperatorTest.class);
        TestSetup wrapper = new TestSetup(suite) {
            protected void setUp() {
                oneTimeSetUp();
            }
        };

        return wrapper;
    }
   
    protected static void oneTimeSetUp() {
        operator = new Operator();
    }
   
    public void testAdd() {
        assertEquals(new Integer(5), operator.add(3, 2));
    }
   
    public void testSubtract() {
        assertEquals(new Integer(1), operator.subtract(3, 2));
    }
   
    public void testDivide() {
        assertEquals(new Double(2.0), operator.divide(6.0, 3.0));
    }
}

 4. Next would be to get the test class running with maven. For this example I used Maven 1.0.2 and installed maven-cobertura-plugin-1.4. For those familiar with Maven the site goal would also ensure running the tests in addition to generating the site reports. So I had only one goal in pom.xml to invoke the site command. Something like

    <goal name="maven-test-operator" prereqs="somegoal">
        <attainGoal name="site"/>
    </goal>

 5. Next step would be to create the project.xml without which you cannot run a maven project. In the project.xml specify the dependencies that your test class needs in order to run successfully. In this case junit.3.8.1 and the JAR created in Step 2 are the dependencies

    <dependencies>
 
        <dependency>
            <groupId>sample-cobertura</groupId>
            <artifactId>operator</artifactId>
            <type>jar</type>
            <jar>operator.jar</jar>
        </dependency>
       
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>3.8.1</version>
        </dependency>
       
    </dependencies>

6. Now having defined the dependencies the next step would be to configure the <build> element in the project.xml. Don't forget to mention the source directory of the class for which you need the coverage reports. Your build element should look something like shown below

    <build>
        <sourceDirectory>${source.dir}/src/java</sourceDirectory>
        <unitTestSourceDirectory>src/test/java</unitTestSourceDirectory>
        <unitTest>
            <includes>
                <include>**/*Test.java</include>
            </includes>
            <resources>
                <resource>
                    <directory>${basedir}/src/test/java</directory>
                    <filtering>false</filtering>
                </resource>
            </resources>
        </unitTest>
    </build>

 7. The last step would be to add the <reports> tag in the project.xml

    <reports>
        <report>maven-junit-report-plugin</report>
        <report>maven-cobertura-plugin</report>
    </reports>

 8. We are ready to run the project. Navigate to your test root folder where you have the pom.xml and the project.xml and run the command maven maven-test-cobertura. Below shown the the folder structure I used and the pom.xml and project.xml were at the operator-test level

operator_test
├───bin
├───src
│   └───test
│       └───java
│           └───com
│               └───cobertura
│                   └───test

9. Sit back and relax, Maven will run the test class and generate the coverage report if everything goes on well. :) This is how the coverage report will look. As desired we have 100% coverage. The reports can be found inside the target directory that gets created

PS: This post assumes people to have a basic understanding of Maven. Those new to Maven might consider going through this link to get to know what Maven is all about. http://maven.apache.org/