Summary
After performing the patching activity and reboot , UD 10.30 Production Server is not up and running. It displayed the "Data-Acquisition" error.
Question
After performing the patching activity and reboot , UD 10.30 Production Server is not up and running.
Answer
-We deleted CP24 and 23 from the data base and from the CP folder.
1. Stop uCMDB services
2. Detect the corrupted CP file in"\\hp\\ucmdb\\ucmdbserver\\content\\content_packs\\"
3. Remove the corrupted CP file from "content_pack" folder
4. Remove the CP record from database.
Here are the queries:
showing all CP in DB:
SELECT * FROM CONTENT_PACKS
removing a CPrecord from DB, where XX.XX.XXXX is a CP version:
DELETE FROM CONTENT_PACKS WHERE VERSION='-1.0.0'
5. Start uCMDB services. Observe the logs for reoccurring
-We deleted the Search folder, logs and jetty cache.
-Run this method from the JMX console:
rebuildModelDBSchemaAndViews
1.Go to jmx console
2.Login to JMX
3.Go to UCMDB:service=DAL services
4.Go to rebuildModelDBSchemaAndViews
CustomerID: 1
className: <leave empty>
skipIndexRebuild: False
skipColumnsUpdate: False
previewMode: false
5.Then click Invoke.
-Finally we deleted the tql.max.result.size.layout.retrieval line that was added on the C:\\hp\\UCMDB\\UCMDBServer\\conf\\settings.override.properties. Since the value added was smaller than the actual value amount of the tqls being sent.
-Finally we restarted the services and the were up and running as expected.
1. Stop uCMDB services
2. Detect the corrupted CP file in"\\hp\\ucmdb\\ucmdbserver\\content\\content_packs\\"
3. Remove the corrupted CP file from "content_pack" folder
4. Remove the CP record from database.
Here are the queries:
showing all CP in DB:
SELECT * FROM CONTENT_PACKS
removing a CPrecord from DB, where XX.XX.XXXX is a CP version:
DELETE FROM CONTENT_PACKS WHERE VERSION='-1.0.0'
5. Start uCMDB services. Observe the logs for reoccurring
-We deleted the Search folder, logs and jetty cache.
-Run this method from the JMX console:
rebuildModelDBSchemaAndViews
1.Go to jmx console
2.Login to JMX
3.Go to UCMDB:service=DAL services
4.Go to rebuildModelDBSchemaAndViews
CustomerID: 1
className: <leave empty>
skipIndexRebuild: False
skipColumnsUpdate: False
previewMode: false
5.Then click Invoke.
-Finally we deleted the tql.max.result.size.layout.retrieval line that was added on the C:\\hp\\UCMDB\\UCMDBServer\\conf\\settings.override.properties. Since the value added was smaller than the actual value amount of the tqls being sent.
-Finally we restarted the services and the were up and running as expected.