APAR status
Closed as program error.
Error description
Maximo 75 Problem description In the Assets and Locations application on the "Relationships" tab relationships can be created from Assets to Locations or Assets. Whenever a relationship is created from an Asset to a Location the AssetTopoCache crontask fails. A "cannot insert null into TargetAsset" error occurs. Steps to Replicate: 1. create 2 new assets, asset 1 and asset 2. For Asset 1 associate it to a location that currently has no asset tied to it. 2. Move to the Relationships tab and press new row set up as follows Source Asset: this value defaults for us Relationships: Use Includes Target Asset: use the 2nd asset created in step. Once that is done save the asset and now move to the Crontask application. Bring up the AssetTopoCachecron and set it to run every 10 minutes, reload the cron. Wait for the cron to run and we should the error of 29 Mar 2012 14:53:32:528 [ERROR] [MXServer] [CID-InitAssetTopoBVCache-32322] ORA -01400: cannot insert NULL into ("MAXIMO"."ASSETTOPOCACHE"."TARGETASSETNUM") java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("MAXIMO"."ASSETTOPOCACHE"."TARGETASSETNUM")
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: ALL * **************************************************************** * PROBLEM DESCRIPTION: Maximo 75 * * * * Problem description * * * * In the Assets and Locations application * * on the "Relationships" * * * * tab relationships can be created from * * Assets to Locations or * * * * Assets. * * * * Whenever a relationship is created from * * an Asset to a Location * * * * the AssetTopoCache crontask fails. A * * "cannot insert null into * * * * TargetAsset" * * * * error occurs. * * * * Steps to Replicate: * * * * 1. create 2 new assets, asset 1 and * * asset 2. For Asset 1 * * * * associate it to a location that * * currently has no asset tied to * * * * it. * * * * 2. Move to the Relationships tab and * * press new row set up as * * * * follows * * * * Source Asset: this value defaults for * * us * * * * Relationships: Use Includes * * * * Target Asset: use the 2nd asset created * * in step. * * * * Once that is done save the asset and * * now move to the Crontask * * * * application. * * * * Bring up the AssetTopoCachecron and set * * it to run every 10 * * * * minutes, * * * * reload the cron. * * * * Wait for the cron to run and we should * * the error of * * * * 29 Mar 2012 14:53:32:528 ERROR * * MXServer * * * * CID-InitAssetTopoBVCache-32322 ORA * * * * -01400: cannot insert NULL into * * * * ("MAXIMO"."ASSETTOPOCACHE"."TARGETASSET * * NUM") * * * * java.sql.SQLIntegrityConstraintViolatio * * nException: ORA-01400: * * * * cannot * * * * insert NULL * * * * into * * ("MAXIMO"."ASSETTOPOCACHE"."TARGETASSET * * NUM") * * * * LOCAL FIX: * * * * N/A * * * **************************************************************** * RECOMMENDATION: * * * * * * * **************************************************************** BMXAA4210E - DATABASE ERROR NUMBER 1400 HAS OCCURRED. INVALID SQL QUERIES ARE LOGGED.
Problem conclusion
Not reproducible on a latest build of Maximo Release 7.5.0.3
Temporary fix
Comments
APAR Information
APAR number
IV19093
Reported component name
ASSETS
Reported component ID
5724R46AS
Reported release
711
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-04-09
Closed date
2012-04-16
Last modified date
2012-04-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
MAXIMO
Fix information
Fixed component name
ASSETS
Fixed component ID
5724R46AS
Applicable component levels
R711 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"711","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
09 April 2023