Upgraded my production instance of CA Service Catalog to 17.3.0.18 from 17.3.0.15, but cannot access the application when I try to navigate to it.
I checked the logs and found the following error in the seeddata.log file:
"2XX/XX/XX 06.54.43.797 ERROR Exception while communicating with the database:The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "XFK02usm_request_status". The conflict occurred in database "mdb", table "dbo.usm_subscription_detail", column 'id'.
com.microsoft.sqlserver.jdbc.SQLServerException: The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "XFK02usm_request_status". The conflict occurred in database "mdb", table "dbo.usm_subscription_detail", column 'id'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:217) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1635) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:426) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:372) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:6276) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1794) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:184) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:159) ~[sqljdbc.jar:?]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:315) ~[sqljdbc.jar:?]
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) ~[commons-dbcp.jar:2.1.1]
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:98) ~[commons-dbcp.jar:2.1.1]
at com.ca.usm.datasource.DBJDBC.update(DBJDBC.java:1239) ~[common.core.jar:17.3.0.1.100]
at com.ca.usm.datasource.DBSource.executeUpdate(DBSource.java:1584) ~[common.core.jar:17.3.0.1.100]
at com.ca.usm.datasource.DBSource.executeUpdate(DBSource.java:1560) ~[common.core.jar:17.3.0.1.100]
at com.ca.usm.util.seeddata.SeedDataImporter.enableFkAndTriggers(SeedDataImporter.java:351) ~[common.core.jar:17.3.0.1.100]
at com.ca.usm.util.seeddata.SeedDataImporter.importSeeddata(SeedDataImporter.java:626) [common.core.jar:17.3.0.1.100]
at com.ca.usm.util.seeddata.SeedDataImporter.main(SeedDataImporter.java:595) [common.core.jar:17.3.0.1.100]"
I tried re-running the seeddata utility using instructions I had received before, but I continue to receive an error about this particular table. When I check the usm_request_status table, I find there are more than 300,000 records with null in the subscription_detail_id field, including several entries dated from when I ran the installer this morning.
Release : 17.3
CA Service Catalog
select jar file missing from the Catalog install.
Examine the USM_HOME/view/webapps/WEB-INF/lib and compare with a working environment for any missing content