Upgrade Programs in Needs Recovery (ugsql)

Roger,

Have you setup the CLASSPATH and MSJDBC environment variables on your system and restarted the system?
CLASSPATH should have a value of . or atleast have the period as the first part of the path if you have an additional value there.
MSJDBC should point to the location of your SQLJDBC driver. For instance D:\JDBC\
I'm using the sqljdbc4.jar file.
Also make sure you have #LAWGATENAME=msfdb2005 in your MICROSOFT file even if you are running SQL Server 2008.

Thanks,
This is Windows, so I don't think CLASSPATH needs to be set manually within the OS or the Lawson environment. 

The classpath recommendation comes from P.5 of the Enterprise Applications 9.0.1 Installation Guide Addendum Version 9.0.1 August 2011 edition.

The LAWGATE recommendation being commented out is just from how it is in my file. I think the key is LAWGATENAME being set to msfdb2005.
 
I am running Windows 2008 R2, SQL Server 2008, LUU, and was able to run the upgrade successfully.

Hope this helps!

No, just the dot is how I have it setup.

From: forums-lsf-s3-sys-admin@lawsonguru.com [mailto:forums-lsf-s3-sys-admin@lawsonguru.com]
Sent: Friday, February 17, 2012 12:33 PM
To: Roelofs, Thad
Subject: RE: Upgrade Programs in Needs Recovery (ugsql) [00009503:00018078]

[LawsonGuru.com Logo]<https://www.lawsonguru.com/>
S3 Systems Administration Forum Notification
A message was posted to a thread you are tracking.
RE: Upgrade Programs in Needs Recovery (ugsql)

Posted by: Roger French
02/17/2012 11:28 AM

I have CLASSPATH defined as a server environment variable just as a '.' (for current directory)
Does it need to include other things?

________________________________

To view the complete thread and reply via your browser, please visit:
https://www.lawsonguru.co...eeds-recovery-ugsql/

You were sent this email because you opted to receive email notifications when someone posted and/or responded to a message on this forum.
To unsubscribe to this thread please visit your user profile page and change your subscription options.

Thank you,
LawsonGuru.com

Thank you,
I checked all of that, checked the environment variables, rebooted, everything. It still does not work. Lawson doesn't know yet either.

The problem I guess resides in the UG99.sh where the ugsql is being called. I don't know if that is where the bug/issue resides. Could you share you're UG99.sh?

Thank you,
-R

Hi Roger,

I can send the UG99.sh script, but it should be the same as the one included in the latest download (February) of the DPP programs. I double checked the release notes of the DPPs (RelNotes-UNIX_NT_900-901.xls) and it looks like there was a correction made to the DPPs in January to address an issue with ugsql with MSF2008 parameter returning a database not found error. ugsql and the dbsql.jar file were updated.

I am also running LSF 9.0.1.9 so that may come into play.

Thanks, however, Lawson is saying that for our version of apps and environment, and OS, there isn't (yet??) a patch for the DPP programs and the issue we're having here.

There seemed to be an issue with not finding something called 'model' .. when we did a which model, it's not found. I don't know what if anything, the 'model' command has in all of this. 

They are checking with the altshell developer for additional clarification.

I remember having the same issue last year.  I had to add 2 additional environment variables called %LOGNAME% and %USERNAME%.

%LOGNAME% was equal to domain name\lawson and %USERNAME% was equal to lawson.

I also made sure that a . was the first thing in the classpath variable, and I also added the full file path to the lawsonrt.jar file.

I also created the MSJDBC variable as well.

I also ended up executing the sql commands that were in the joblog of the jobs that were in the job log files.

Also, I remember that the UG tables had old data in there that I ended up clearing out as well. 

Thanks we tried and confirmed all of the environment variables,  all of that already, rebooted, etc. and still the jobs won't run.

Well it turns out there is/was a bug in the UG99.sh for the version we have. We tried many many things but it turns out yes a bug which prevented all of the RunSQL update jobs from being submitted properly. There isn't a fix yet for it.

So we manually submitted the jobs as a workaround using the ugsql commands and that seemed to work.

Roger,

What versions are you on (OS, db, etc...) and what are you moving to?

Do you have the PT for the bug and is it opened under your company or some
other.

For those that are on a similar platform and version, it would be very
beneficial to know if/when this bug is addressed.

On Thu, Feb 23, 2012 at 6:39 AM, wrote:

> [image: LawsonGuru.com Logo] <https://www.lawsonguru.com/> S3 Systems
> Administration Forum Notification A message was posted to a thread you
> are tracking. *RE: Upgrade Programs in Needs Recovery (ugsql)* Posted
> by: *Roger French*
> 02/23/2012 06:38 AM Well it turns out there is/was a bug in the UG99.sh
> for the version we have. We tried many many things but it turns out yes a
> bug which prevented all of the RunSQL update jobs from being submitted
> properly. There isn't a fix yet for it.
>
> So we manually submitted the jobs as a workaround using the ugsql commands
> and that seemed to work.
> ------------------------------
>
> To view the complete thread and reply via your browser, please visit:
>
> https://www.lawsonguru.co...eeds-recovery-ugsql/
>
> You were sent this email because you opted to receive email notifications
> when someone posted and/or responded to a message on this forum.
> To unsubscribe to this thread please visit your user profile page and
> change your subscription options.
>
> Thank you,
> LawsonGuru.com
>

No, there isn't a PT, JT or anything yet as far as I know. We just kinda discovered it earlier this week.

Windows 2008R2
SQL2005
Using LUU, not MKSToolkit
Env: 9.0.1.8
Apps: 9.0.1.7
Moving from: 9.0.0.6 Env, 9.0.0.6 Apps