Escape from boredom

Trying to update the nodeagent service following the guideline found at IBM Knowledge Center failed, complaining about the value of the -username was not known.

Unrecognized parameters encountered on the command line: 'wasadmin '

It turned out that I had a slash at the end of the folder name for the washome, which then acted as an escape char for the double qoute

-washome "D:\WebSphere\AppServer\"

Changed to

-washome "D:\WebSphere\AppServer"

and all was fine.

Not first day working after summer holiday, but first day at the office, giving it a fresh start, did wash my water bottle and even the whiteboard – very old doodles meaning nothing – better having a white whiteboard.

Its a book, but work related, not leisure at all. Read it to get a grasp of IBM WebSphere Liberty.

Just noticed my email recycle bin

Trying to access http://www.dagbladet.no/ just now it responded with Error Bad Gateway 502. Whatever reason for the error, I found the custom error page really nice

Sending common_select_deployitenvironment.bat
Transmitting file data .
Committed revision 666.

Better hurry up and commit yet another change.

Did test the iPhones voice recognition, but after way to many attempts my voice was not recogniced. Why it insist on Elin being green beats me

We are in the process of migrating our IBM Filenet 5.1 environment to 5.2. During migration of the process engine, while running the script rmove.bat the script failed while migrating the table with most data. The error was:
Creating Table PE_DB.VWLOG3_911
Exception occurred while executing SQL statement.
Exception = java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

We did not entierly believe that this was the root cause, but more suspected a timeout. After some investigation, one of our developers took a closer look into the .jar file used (regmove.jar). There he found out the following

The utility tries to create a temp table as a copy of all rows in the log. That probably fails due to out of space for extending the segments.
Then it tries to drop the temp table and fails here.

static final int DB_ORACLE = 4;

     if (srcDb.type == 4)
      {
        SQLHelper.execSQLStmt(srcDb.connection, "create table " + tmpTbl + " as " + "(select * from " + srcDb.schema + "." + sourceTableName + ")");

        srcRs = srcStmt.executeQuery("select * from " + tmpTbl);
      }
      else
      {
        srcRs = srcStmt.executeQuery("select * from " + srcDb.schema + "." + sourceTableName);
      }

      copyRows(srcDb, destDb, table, sourceTableName, destinationTableName, srcRs, batchSize);

      JDBCHelper.closeDBObject(srcStmt);
      JDBCHelper.closeDBObject(srcRs);
      JDBCHelper.closeDBObject(destStmt);
      if (srcDb.type == 4)
      {
        SQLHelper.dropTable(srcDb, tmpTbl);
      }

… This was also confirmed by the DBA. So he then increased the available space for the schema. We then had to drop all tables in the new schema and rerun the script, now with success. Or actually, it did fail yet another time, but this time the developers of the script had managed to provide the correct error message

*** Creating indices in destination region
Exception occurred while executing SQL statement.
Exception = java.sql.SQLException: ORA-01652: unable to extend temp segment by 1
28 in tablespace PE_DB_TS

Since Google did not return any hits for the error we had on one of our servers I add it here for future references. The error logged in SystemOut.log was

ContainerHelp E   WSVR0501E: Error creating component com.ibm.ws.runtime.component.CompositionUnitMgrImpl@593e2ce7
com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.RuntimeError: java.lang.RuntimeException: java.lang.VerifyError: JVMVRFY024 arguments are not type compatible; class="com"/ibm/ws/webcontainer/srt/SRTRequestContext...

The solution was to clear the WebSphere class caches as described in this IBM technote http://www-01.ibm.com/support/docview.wss?uid=swg21607887

First one up this morning, nothing else to do than enjoying myself with a bit of Powershell-scripting. Got stuck for a while, my script did not run due to the error “Bad numeric constant error”. Turned out that I had a variable starting with a number…which apperantly is bad. Removed the number and voila, all fine.