- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Oracle 8.1.6 crash
Operating System - HP-UX
1753884
Members
7502
Online
108809
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
Discussions
Discussions
Forums
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
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
тАО04-10-2002 05:39 AM
тАО04-10-2002 05:39 AM
Oracle 8.1.6 crash
I am running HPUX 11 with Oracle 8.1.6. $GB memory with a 1GB SGA.
Oracle crashed with a segmentation violation. The Oracle error was ORA-07445. Oracle said that the online redo logs got corrupted due to a memory corruption. They do not know what triggers this. This problem is very random and Oracle suggests going to a newer release although they have not found what is causing the problem.
Has anyone experienced a similar problem.
Oracle crashed with a segmentation violation. The Oracle error was ORA-07445. Oracle said that the online redo logs got corrupted due to a memory corruption. They do not know what triggers this. This problem is very random and Oracle suggests going to a newer release although they have not found what is causing the problem.
Has anyone experienced a similar problem.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2002 05:53 AM
тАО04-10-2002 05:53 AM
Re: Oracle 8.1.6 crash
Hello,
several reasons for this. I would check oracle website. Even SAP-OSS has some 20 hits for various reasons for this, depending on diffrent sources.
Some are related to oracle parameters
timed_statistics
star_transformation_enabled
sql_trace
Others are OP-Sys-dependend like
PHSS_16849 core 64bit HPUX Oracle Note 73835.1 for Oracle 64-Bit on HP-UX 11.0
PHSS_16849 : s700_800 11.0 LIBCL patch should be exchanged by a superseeded one
Do not know if this helps
Volker
several reasons for this. I would check oracle website. Even SAP-OSS has some 20 hits for various reasons for this, depending on diffrent sources.
Some are related to oracle parameters
timed_statistics
star_transformation_enabled
sql_trace
Others are OP-Sys-dependend like
PHSS_16849 core 64bit HPUX Oracle Note 73835.1 for Oracle 64-Bit on HP-UX 11.0
PHSS_16849 : s700_800 11.0 LIBCL patch should be exchanged by a superseeded one
Do not know if this helps
Volker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2002 04:40 PM
тАО04-10-2002 04:40 PM
Re: Oracle 8.1.6 crash
Hi Marc,
I'm always leary when vendors or developers start blaming "memory corruption" on HP-UX systems. If memory truly erred out there WILL be an entry in the syslog or the STM log. Lord knows, for the $ of HP ECC memory, it better let me know. So unless there is actually an entry, I'd turn the argument back on them, ESPECIALLY when they start the "new release" spiel. Seems awfully self-serving don't you think?
If that CAN be ruled out, AS WELL AS, faulty code - then a misconfigured kernel param would be the next likely culprit.
Rgds,
Jeff
I'm always leary when vendors or developers start blaming "memory corruption" on HP-UX systems. If memory truly erred out there WILL be an entry in the syslog or the STM log. Lord knows, for the $ of HP ECC memory, it better let me know. So unless there is actually an entry, I'd turn the argument back on them, ESPECIALLY when they start the "new release" spiel. Seems awfully self-serving don't you think?
If that CAN be ruled out, AS WELL AS, faulty code - then a misconfigured kernel param would be the next likely culprit.
Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP