- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Fatal Oracle error
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО09-13-2004 04:14 AM
тАО09-13-2004 04:14 AM
Fatal Oracle error
Oracle alert file noticed about a very important error reported on a trc file (attached).
Any idea about the error and how to fix it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 04:28 AM
тАО09-13-2004 04:28 AM
Re: Fatal Oracle error
Have you access to metalink? Can you open a tar?
This may be the best avenue to pursue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 04:28 AM
тАО09-13-2004 04:28 AM
Re: Fatal Oracle error
disk_async_io=?
Set it to FALSE
disk_async_io=FALSE
If you want to use "async" you'll need to create the /dev/async file...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 07:25 AM
тАО09-13-2004 07:25 AM
Re: Fatal Oracle error
Doc ID: Note:41472.1
Subject: ORA-600 [17034] "pin not valid"
Type: REFERENCE
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 17-NOV-1997
Last Revision Date: 06-SEP-2004
Note: For additional ORA-600 related information please read [NOTE:146580.1]
PURPOSE:
This article discusses the internal error "ORA-600 [17034]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.
ERROR:
ORA-600 [17034] [a] [b]
VERSIONS:
versions 7.0 to 9.2
DESCRIPTION:
When trying to unpin heaps belonging to an object we find that
the pin is not valid. This activity typically occurs when closing
cursors.
ARGUMENTS:
Arg [a] Address of the pointer to the pin
Arg [b] Pin Count
FUNCTIONALITY:
GENERIC LAYER
IMPACT:
PROCESS FAILURE
NON CORRUPTIVE - No underlying data corruption.
SUGGESTIONS:
Known Issues:
Bug# 1818676 See Note 1818676.8
Sessions exceeding PROFILE resource limits may raise OERI:17034 / OERI:17281
Fixed: 8.1.7.3, 9.0.1.2, 9.2.0.1
Bug# 1096056 See Note 1096056.8
OERI:17034 / spin after UPDATE with TRIGGER and column value too large
Fixed: 8.1.7.0
Bug# 674565 See Note 674565.8
OERI:17034 releasing a pin on a trigger in kglunp()
Fixed: 8.0.4.3, 8.0.6.2, 8.1.6.3, 8.1.7.0
Bug# 614799 See Note 614799.8
OERI:17034 possible in EXCEPTION from TRIGGER when AUDITING
Fixed: 8.0.4.2, 8.0.5.1, 8.1.5.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 07:35 AM
тАО09-13-2004 07:35 AM
Re: Fatal Oracle error
ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
CAUSE: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:
timeouts
file corruption
failed data checks in memory
hardware, memory, or I/O errors
incorrectly restored files
The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.
ACTION: Report this error to Oracle Support Services after gathering the following information:
events that led up to the error
the operations that were attempted that led to the error
the conditions of the operating system and databases at the time of the error
any unusual circumstances that occurred before receiving the ORA-00600 message
contents of any trace files generated by the error
the relevant portions of the Alter files
Regards,
Hamdy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 05:12 PM
тАО09-13-2004 05:12 PM
Re: Fatal Oracle error
since we have little information, it can be either of these cases:
a. Related to triggers or plsql and occurring when raising an EXCEPTION from TRIGGER when AUDITING
b. Related to Triggers occurring when a pin on a trigger is being released.
c. Occurring while attempting to update a table with an invalid value (value too large for column) if the table has UPDATE TRIGGER defined. The server process may spin (appearing to hang) on disconnect.
You must contact Oracle support for more systematic help.
regards
Yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 08:54 PM
тАО09-13-2004 08:54 PM
Re: Fatal Oracle error
What├В┬┤s /dev/async purpose?
Thanks everybo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 09:17 PM
тАО09-13-2004 09:17 PM
Re: Fatal Oracle error
Async IO is a most efficient form of IO available but it works better on Oracle 8i that on Oracle 8.
Try this:
- shutdown the database
- set disk_async_io=FALSE in init
- startup the database
Regards,
Eric Antunes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 10:07 PM
тАО09-13-2004 10:07 PM
Re: Fatal Oracle error
It seems they have a workaround for your issue (see Metalink Note 60692.1: http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=60692.1):
It is possible to workaround the problem by the following means;
If the "/dev/async" device does not exists, then create it.
As the root user:
/sbin/mknod /dev/async c 101 0x0
/usr/bin/chown oracle:dba /dev/async
/usr/bin/chmod 000 /dev/async
The permissions on /dev/async of 000 ensure that it is not possible to use the async driver unintentionally.
As the oracle user, modify the "init.ora" file so that the parameters:
disk_asynch_io = false
tape_asynch_io = false
Hope this will solve your problem...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2004 10:19 PM
тАО09-13-2004 10:19 PM