UPDATEDB ERROR WHEN RUNNNG MAXIMO 7.5 WITH SQL SERVER

Abstract

While upgrading Maximo from 7.1 to 7.5 by running updatedb on SQL Server, you could encounter an error on script V7500_224 .

Content

While upgrading Maximo from 7.1 to 7.5 ( eg: MBS 7.1.1.10 to MBS 7.5.0.3 ) by running updatedb on SQL Server, you could encounter an error on script V7500_224 .
The updatedb process ends without errors, however the following errors are shown on the updatedb console.

-----------------------------------------------------------------------------------------------------------------------------------------------------------
com.microsoft.sqlserver.jdbc.SQLServerException: The multi-part identifier "wocalcvaluesseq.nextval" could not be bound.
at com.microsoft.sqlserver.jdbc.SQLServerException. makeFromDatabaseError(SQLServerException.java:196)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextRes (SQLServerStatement.java:1454)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:786)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmdoExecute(SQLServerStatement.java:685)
at
|
|

com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:658)
at psdi.script.en.V7500_224.updateWOValues(UnknownSource)
at psdi.script.en.V7500_224.findTotals(Unknown Source)
at psdi.script.en.V7500_224.process(Unknown Source)
at psdi.script.AutoUpgradeTemplate.(Unknown
Source)
at psdi.script.en.V7500_224.(Unknown Source)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
------------------------------------------------------------------------------------------------------------------------------------------------------------



This has been identified as a product defect and is being fixed in APAR IV36359

ADMA5014E: The installation of application MAXIMO failed

Problem(Abstract)

Deployment fails for maximo.ear file in WebSphere.

Symptom

After uninstalling and reinstalling the Maximo application, the WebSphere Integrated Solutions Console displays the following:

Installing...
If there are enterprise beans in the application, the EJB deployment
process can take several minutes. Do not save the configuration until
the process completes.

Check the SystemOut.log on the deployment manager or server where the
application is deployed for specific information about the EJB
deployment process as it occurs.

ADMA5016I: Installation of MAXIMO started.

A composition unit with name MAXIMO already exists. Select a different application name.

ADMA5011I: The cleanup of the temp directory for application MAXIMO is complete.

ADMA5014E: The installation of application MAXIMO failed.

The installation of application MAXIMO failed.

Cause

Occasionally after uninstalling the MAXIMO application, the directory at /config/cells//applications director will still contain the MAXIMO.ear directory.

By default , this directory is located at C:\Program
Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\config\cells\ctgCell01\applications\MAXIMO.ear.

For another possible cause of this error, see the link below .

Resolving the problem

Delete the /config/cells//applications/MAXIMO.ear directory.

Redeploy the MAXIMO ear file.

SCCD 7.5 install failing with error CTGIN0005E

Problem(Abstract)

Installing Smart Cloud Control Desk 7.5 fails with the error CTGIN0005E The deployment of D:\IBM\SMP\pmp\DIS_CMS_Tpae_Config_7.5.0.0.zip failed. The error text is CTGIN0143E: An

action error ocurred during the processing of a deployment operation. Action identifier: "Patch_webXML".

Symptom

The deployment of D:\IBM\SMP\pmp\DIS_CMS_Tpae_Config_7.5.0.0.zip failed. The error text is CTGIN0143E: An
action error ocurred during the processing of a deployment operation. Action identifier: "Patch_webXML".
This will be shown in the solutioninstaller logs as:
IBM\SMP\ant\bin\ant' is not recognized as an internal or external command,
operable program or batch file.

Cause

This is caused by the installer not being able to call the ant.bat file due to the PATHEXT system variable not being set correctly.

Diagnosing the problem

In command prompt run the command:
set PATHEXT
This will display what your path extension system variable is currently set to. If it is missing .bat and .cmd you will need to add them.

Resolving the problem

In Windows navigate to your Environment variables.
In Windows Server 2008, Right-click Computer and go to properties. Then Advanced System Settings. Then Environment variables.
Pre-Windows Server 2008, Right-click
In this menu you can see your system variables. Under system variables find PATHEXT. Edit this and add .BAT;.CMD with each new entry being separated by a semi-colon. Ensure that .BAT is before .CMD in the list from left to right.

After adding this to your Path Extention variable, you can re-run taskrunner CONTINUE STOPONERROR.

Forgot password and cannot access WebSphere Application Server administrative console

Problem(Abstract)

Forgot the password and cannot access WebSphere Application Server administrative console.

Cause

After enabling WebSphere Application Server with security, the administrator forgot the user id and password and could no longer access the server.

Resolving the problem

WARNING: Please use this as the last resort and make sure the server is not in the middle of processing any transactions.

There are 2 possible methods for disabling security:

By way of wsadmin command:

1. /bin/> wsadmin -conntype NONE
2. wsadmin> securityoff
3. wsadmin> exit
4. Restart the servers.
5. Enable the security from administrative console.
6. Restart the servers.

By way of manual edit of security.xml file, which is typically located in /config/cells /:

1. Create a copy for security.xml file, in case you need to roll back.
2. Disable the security from the security.xml file (change the very first occurrence of... enabled="true" to enabled="false")
3. Restart the servers.
4. Enable the security from administrative console.
5. Restart the servers.

For additional information regarding enabling administrative security, please refer to this link:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tsec_csec2.html

Backing up and restoring the Deployment Engine database

Question

How do I backup and restore the deployment engine found on my product's middleware servers and administrative system?

Answer

These instructions are for manually backing up and restoring the Deployment Engine
database to the state it was before installing middleware on middleware servers or
process managers on the administrative workstation.
In past releases, the deployment engine was automatically backed up during installation. This is no longer the case. In the latest releases of ISM products, deployment engine backups and restoration are the responsibility of the user.
You should back up the Deployment Engine database of the system before and
after applying any updates to an existing deployment. Having backups allows you
to recover from partial installation attempts where middleware or process manager
components were partially installed.
This procedure is not dependant on the state of the application server. The application server can either in a started or stopped state.
To backup the Deployment Engine database, complete the following steps:
1. Set up the environment using the following command:
Windows c:\Program Files\IBM\Common\acsi\setenv.cmd
UNIX cd /var/ibm/common/acsi ./setenv.sh
2. Run the command to backup the Deployment Engine registry:
Windows c:\Program Files\IBM\Common\acsi\bin\backupdb.cmd

UNIX cd /usr/ibm/common/acsi/bin ./backupdb.sh

Use a meaningful name for to reflect the fact that it contains the state of the registry after your installation of the product. For example, DEBackupAfterJune12Install.
If you have a backup of the Deployment Engine database, you can use the
following command to restore it:
Windows
c:\Program Files\IBM\Common\acsi\bin\restoredb

UNIX
cd /usr/ibm/common/acsi/bin
./restoredb.sh

where is the file containing the Deployment Engine backup
you made.

SmartCloud Control Desk version 7.5 Upgrade Guide.

https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=e25892f0-20f7-46ff-bbe9-c7c03fb3036f#fullpageWidgetId=Wb33da0c91d92_4cec_a8a7_57df877f617b&file=9ff971b9-237a-4713-a944-c1e322efff78

Upgrade Service Request Manager 7.1 to 7.2.1

http://pic.dhe.ibm.com/infocenter/tivihelp/v32r1/index.jsp?topic=%2Fcom.ibm.srm.doc_721%2Fupgrade%2Fc_upgrade_71to7201.html