Patch for WLS 10.0 ORA-00001 Error Messages in Logs

While the message does not impact functionality, if you have to read the logs it becomes tedious to scroll past the following over and over:

<BEA-403302> <An unexpected SQL exception occured java.sql.SQLException: ORA-00001:
unique constraint (PORTAL.PK_LEASE) violated.
java.sql.SQLException: ORA-00001: unique constraint (PORTAL.PK_LEASE) violated
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)

Not to mention how the fun of having every person who hasn’t looked at your application before reporting it as a problem or insisting it is the root of a bug you are chasing (it isn’t).

If you have a support account, you can surpress this with the following WLP 10.2 patch:

VZGR | 9AS6D7D9

If you found this interesting, please share.

© Scott S. Nelson

Next Step: Using MySQL on Vista

Once I got MySQL running on Vista, I then needed to manage it. While I ran MySQL from the command line eight years ago, that was, well, eight years ago. I remembered enough to get the server started, set up the root user, and find the databases that are pre-configured. This was enough to get my local version of WordPress running.

To do more interesting things for the casual user, the best tool I ever found is the one made by DBTools. I started using it with version 1.02, and find 3.2.4 just as delightfully simple and feature-rich as my first foray into getting fast results with very little ramp-up back in 2001.

I’m also notoriously cheap, and DBTools has a free version for personal use. Price aside, it is still my preferred tool for basic interaction with MySQL.

If you found this interesting, please share.

© Scott S. Nelson

WebLogic Workshop 10.2 Debugging

On a very long, large project where there are multiple portals I will create separate worskpaces for the different portals. Especially when developing shared libraries, to save time in unit testing and debugging. Once in a while, I would get this annoying message about the WebLogic Server not starting within the timeout period. The server does eventually start, but you can’t debug without restarting.

Later in the project I had to run all of the portals in Workshop at once. Being able to debug become the norm, which is really annoying when trying to find bugs in code you have never seen before. I did some digging and found that the timout period was made configurable in an older version of Workshop. Originally, there were several versions of Workshop. Some were versions for specific products, like WebLogic Portal. Then they combined them in all into one. Unfortunately, the ability to configure the timeout was only in the WLP version and did not make it into Workspace Studio (the actual new name for Workshop that no one seems to use).

Long story short (yeah, I know, too late), I got the feature ported forward to 10.2. It is patch WW5U | F21UMQIN. Once the patch is installed, edit workshop.ini and add the following:

-Dweblogic.deployment.timeout=3600000
-Dweblogic.startserver.timeout=3600000
-Dweblogic.stopserver.timeout=3600000

3600000 is number of milliseconds, and is the maximum setting.  You can set it for whatever you want less than that, but why would you?

If you found this interesting, please share.

© Scott S. Nelson

Installing MySQL on Vista Part 3

Mission accomplished.As noted in part 2, changing the path where tables are stored causes a failure. This is probably a Vista permission thing, which I will dig into deeper when I start building stuff on my machine where backing up the files is important again (it isn’t, usually).

The only other comment on the great instructions from thesitewizard.com is in the Modifying Your PHP Configuration to Allow Your PHP Scripts to Use MySQL section, he leaves out the tip found in many PHP fourms of placing the php.ini file in the windows directory. For some reason I remebered doing this from my installation a year ago and didn’t spend hours trying to find the fix I failed to blog or bookmark at that time.

If you found this interesting, please share.

© Scott S. Nelson

Installing MySQL on Vista Part 2

So, as usual, I had to select options other than the defaults, even though legitimate options. Deviating from one of the below prevented getting the basics working:

6. The next screen in the dialog box lets you select the drive where your database is to be stored. If you have no particular preference, leave it at the default and click “Next” (I have always used a custom path to simplify my backups).

If you found this interesting, please share.

© Scott S. Nelson