Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Showing results for 
Search instead for 
Did you mean: 

HPUX Error:14: Bad address

ITRC Support
Occasional Contributor

HPUX Error:14: Bad address

Following Error message when trying to get extract from an oracle Database:

" Error message received from resource pulling data:
The following database error was encountered during extraction.
Function: OciChannelReader::ReadBatch
File: Native/Source/OciChannelReader.cpp
Line: 411
OCI Function: OCIStmtFetch
OCI Status Code: -1
Error Message: ORA-01115: IO error reading block from file 17 (block # 14696)
ORA-01110: data file 17 '/var/opt/vgdb02/u01/oracle/a3rcp3/a3rcp3_fulfill01.dbf'
ORA-07372: sfrfb: read error, unable to read requested block from database file.
HP-UX Error: 14: Bad address
Additional information: 14696
Error Code: 1115
Job Step with name "Fulfillment_Extract/BRU_Fulfillment Extract Group" failed because its child job step with name "Extraction: Fulfillment Extract" had OnErrorAction set to INHERIT and failed.

The job has been aborted because the JobStep with name
"Fulfillment_Extract/BRU_Fulfillment Extract Group" has failed. Although it had OnErrorAction set to AUTOREPEAT, it exceeded its maximum of 0 retries."

Any idea what could be wrong ?
Steven Sim Kok Leong
Honored Contributor

Re: HPUX Error:14: Bad address


This thread tells of a known bug in Oracle that causes this error:,,0xe7abee3e323bd5118fef0090279cd0f9,00.html

Hope this helps. Regards.

Steven Sim Kok Leong
Email: Homepage:
T G Manikandan
Honored Contributor

Re: HPUX Error:14: Bad address


The link of the bug for Oracle v7.

you must be using the latest version.