HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Ozone Database fault
HPE EVA Storage
1826061
Members
3990
Online
109690
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2007 08:46 PM
08-27-2007 08:46 PM
Ozone Database fault
Hi,
Since moving a server from a DL380G2 to a BL460 using the Proliant Migration utility we have been having this problem.
Caught during
createObject("com.compaq.svctools.desta.services.database.persistent.ozo
ne.DefaultOzonePersistent",0,00000013|00000001|00000027,"null"):
org.ozoneDB.OzoneInternalExc: java.lang.IllegalStateException: Unable to
add id -1 to cluster 80126
CallStack:
org.ozoneDB.ExternalDatabase.createObject(Unknown Source)
org.ozoneDB.AbstractDatabase.createObject(Unknown Source)
org.ozoneDB.AbstractDatabase.createObject(Unknown Source)
com.compaq.svctools.desta.services.database.server.ozone.AbstractOzoneSe
rver.createPersistent(AbstractOzoneServer.java:175)
com.compaq.svctools.anaknowledge.RDBSystemFunctions.persist(RDBSystemFun
ctions.java:1149)
com.compaq.svctools.anaknowledge.JDOMElementSystemFunctions.fsCreateTabl
eFromElements(JDOMElementSystemFunctions.java:464)
com.compaq.svctools.anaknowledge.JDOMElementSystemFunctions.fsCreateMerg
edTable(JDOMElementSystemFunctions.java:578)
com.compaq.svctools.anaknowledge.Storage_HSV_PSA.HSV_Decompose_Construct
_PSA_Table(Storage_HSV_PSA.java:6643)
com.compaq.svctools.anaknowledge.Storage_HSV_PSA.inference(Storage_HSV_P
SA.java:8880)
com.compaq.svctools.ca.services.analysis.knowledge.AnalysisKnowledge.inf
erence(AnalysisKnowledge.java:179)
com.compaq.svctools.ca.services.analysis.engine.CAAnalyzer.analyzeData(C
AAnalyzer.java:242)
com.compaq.svctools.ca.services.analysis.engine.CAAnalyzer.analyzeData(C
AAnalyzer.java:181)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeEve
ntData(AnaEngineAuto.java:408)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeEve
nt(AnaEngineAuto.java:332)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeEve
ntList(AnaEngineAuto.java:247)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeDir
(AnaEngineAuto.java:177)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.run(AnaEng
ineAuto.java:605)
Recommended Action:
Reset the Ozone database.
How do I reset the Ozone Database, also is this an action I should be undertaking?
Thanks
Dwain
Since moving a server from a DL380G2 to a BL460 using the Proliant Migration utility we have been having this problem.
Caught during
createObject("com.compaq.svctools.desta.services.database.persistent.ozo
ne.DefaultOzonePersistent",0,00000013|00000001|00000027,"null"):
org.ozoneDB.OzoneInternalExc: java.lang.IllegalStateException: Unable to
add id -1 to cluster 80126
CallStack:
org.ozoneDB.ExternalDatabase.createObject(Unknown Source)
org.ozoneDB.AbstractDatabase.createObject(Unknown Source)
org.ozoneDB.AbstractDatabase.createObject(Unknown Source)
com.compaq.svctools.desta.services.database.server.ozone.AbstractOzoneSe
rver.createPersistent(AbstractOzoneServer.java:175)
com.compaq.svctools.anaknowledge.RDBSystemFunctions.persist(RDBSystemFun
ctions.java:1149)
com.compaq.svctools.anaknowledge.JDOMElementSystemFunctions.fsCreateTabl
eFromElements(JDOMElementSystemFunctions.java:464)
com.compaq.svctools.anaknowledge.JDOMElementSystemFunctions.fsCreateMerg
edTable(JDOMElementSystemFunctions.java:578)
com.compaq.svctools.anaknowledge.Storage_HSV_PSA.HSV_Decompose_Construct
_PSA_Table(Storage_HSV_PSA.java:6643)
com.compaq.svctools.anaknowledge.Storage_HSV_PSA.inference(Storage_HSV_P
SA.java:8880)
com.compaq.svctools.ca.services.analysis.knowledge.AnalysisKnowledge.inf
erence(AnalysisKnowledge.java:179)
com.compaq.svctools.ca.services.analysis.engine.CAAnalyzer.analyzeData(C
AAnalyzer.java:242)
com.compaq.svctools.ca.services.analysis.engine.CAAnalyzer.analyzeData(C
AAnalyzer.java:181)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeEve
ntData(AnaEngineAuto.java:408)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeEve
nt(AnaEngineAuto.java:332)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeEve
ntList(AnaEngineAuto.java:247)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.analyzeDir
(AnaEngineAuto.java:177)
com.compaq.svctools.ca.services.analysis.engine.AnaEngineAuto.run(AnaEng
ineAuto.java:605)
Recommended Action:
Reset the Ozone database.
How do I reset the Ozone Database, also is this an action I should be undertaking?
Thanks
Dwain
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2007 09:10 PM
08-27-2007 09:10 PM
Re: Ozone Database fault
There is an Install document in the OZONE root directory.
Check this document
Check this document
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2007 10:49 PM
09-17-2007 10:49 PM
Re: Ozone Database fault
We had this problem and this is the response from HP:
This is in ref to the case # 1216921930 for which we have received an alert for the Webes issue "
Error Code: Ozone ".
Kindly follow the below instructions for this issue and revert back for any clarifications.
************************************************************************
********************************8
The Ozone database is the WEBES automatic analysis database.
This problem has occurred in previous versions of WEBES, however there was no healthcheck mechanism to detect problems with the database. One of the symptoms of this issue was that old callouts were resubmitted intermittently.
The recommended way of resetting the database on Windows platforms is as
follows:-
Stop the DESTA process
C:\> net stop desta_service
Issue the following DESTA command
C:\> desta exec com.compaq.svctools.ca.services.database.resetAll
Restart the DESTA process
C:\> net start desta_service
You can safely ignore any INFO messages that appear during resting the database.
Be aware that these commands completely reset the Auto analysis (ozone) database & cause WEBES to analyze the whole Windows Application Event log again, which will result in WEBES Emails & calls logged via ISEE for any events that are still in the event log. To avoid this clear all the events in Application Event log before restarting the DESTA process.
This is in ref to the case # 1216921930 for which we have received an alert for the Webes issue "
Error Code: Ozone ".
Kindly follow the below instructions for this issue and revert back for any clarifications.
************************************************************************
********************************8
The Ozone database is the WEBES automatic analysis database.
This problem has occurred in previous versions of WEBES, however there was no healthcheck mechanism to detect problems with the database. One of the symptoms of this issue was that old callouts were resubmitted intermittently.
The recommended way of resetting the database on Windows platforms is as
follows:-
Stop the DESTA process
C:\> net stop desta_service
Issue the following DESTA command
C:\> desta exec com.compaq.svctools.ca.services.database.resetAll
Restart the DESTA process
C:\> net start desta_service
You can safely ignore any INFO messages that appear during resting the database.
Be aware that these commands completely reset the Auto analysis (ozone) database & cause WEBES to analyze the whole Windows Application Event log again, which will result in WEBES Emails & calls logged via ISEE for any events that are still in the event log. To avoid this clear all the events in Application Event log before restarting the DESTA process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2007 01:28 AM
10-16-2007 01:28 AM
Re: Ozone Database fault
Here's some info we got from our HP Remote Support Advocate:
http://h41302.www4.hp.com/km/saw/print.do?docId=mmr_na-140871-4
Title: HP Web Based Enterprise Services 4.5-x -Ozone Database Corruption Failure Notifications How to Reset the Database?
Object Name: mmr_na-140871-4
Document Type: Support Information
Original owner: Storage EVA
Disclosure level: For HP and Customer Verbal Use
Version state: published
Issue
WEBES 4.5 and 4.5.1 have an issue where it will periodically send the customer email messages about Ozone database corruption failures. This happens whenever the analysis database within WEBES becomes unusable or damaged. When this happens WEBES will send notification of the failure to the customerâ s distribution list. The mail message says to reset the database. But it does not explain how. The specific commands are documented in the WEBES User guide.
Solution
Once the Ozone database corruption failures occur, it is best to issue the following series of commands. These commands are specific to the Windows EVA environment. They would need to be syntactically modified for the operating system being affected if not Windows.
â ¢ Stop the Desta service with the command DOS>net stop desta_service
â ¢ Stop the Wccproxy service with the command DOS>net stop wccproxy
â ¢ Run the command
C:\program files\hewlett-packard\svctools\common\share\WebesJavaKill.exe
â ¢ Disable fps creation. From the command line enter: DOS>wccproxy fpsoff
â ¢ Reset the automatic analysis database by entering the command:
DOS>desta exec com.compaq.svctools.ca.services.database.resetAll
â ¢ Save and clear the Windows application event file.
â ¢ Use Task Manager to verify all WCCproxy, WCCAgents, and CAAgents processes are stopped. If they are not a reboot is recommended.
â ¢ Restart Desta service with the command DOS>net start desta_service This will automatically restart the Wccproxy service
© Copyright 2007 Hewlett-Packard Development Company, L.P.
http://h41302.www4.hp.com/km/saw/print.do?docId=mmr_na-140871-4
Title: HP Web Based Enterprise Services 4.5-x -Ozone Database Corruption Failure Notifications How to Reset the Database?
Object Name: mmr_na-140871-4
Document Type: Support Information
Original owner: Storage EVA
Disclosure level: For HP and Customer Verbal Use
Version state: published
Issue
WEBES 4.5 and 4.5.1 have an issue where it will periodically send the customer email messages about Ozone database corruption failures. This happens whenever the analysis database within WEBES becomes unusable or damaged. When this happens WEBES will send notification of the failure to the customerâ s distribution list. The mail message says to reset the database. But it does not explain how. The specific commands are documented in the WEBES User guide.
Solution
Once the Ozone database corruption failures occur, it is best to issue the following series of commands. These commands are specific to the Windows EVA environment. They would need to be syntactically modified for the operating system being affected if not Windows.
â ¢ Stop the Desta service with the command DOS>net stop desta_service
â ¢ Stop the Wccproxy service with the command DOS>net stop wccproxy
â ¢ Run the command
C:\program files\hewlett-packard\svctools\common\share\WebesJavaKill.exe
â ¢ Disable fps creation. From the command line enter: DOS>wccproxy fpsoff
â ¢ Reset the automatic analysis database by entering the command:
DOS>desta exec com.compaq.svctools.ca.services.database.resetAll
â ¢ Save and clear the Windows application event file.
â ¢ Use Task Manager to verify all WCCproxy, WCCAgents, and CAAgents processes are stopped. If they are not a reboot is recommended.
â ¢ Restart Desta service with the command DOS>net start desta_service This will automatically restart the Wccproxy service
© Copyright 2007 Hewlett-Packard Development Company, L.P.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP