Floating point exception

Posted in 2006

MICHAEL CLARK — Fri, 17 Nov 2006 19:52:51 — source: IIUG Forums & Mailing Lists

ontape -rFloating point exception. and no restore occurs I'm posting this in case anyone else gets such an error when trying to restore via ontape. It's a cryptic message. This occurred to me when transferring an IDS database from one server to another via ontape. The error occurred because the block size of the tape drive on the server where ontape was made did not match the block size of the drive where the restore was being made. mt -f /dev/st? status showed server A 1024 server B 0 server A where ontape was made server B where restore was desired. I was under the impression that a block size of 0 meant the tape device would read the tape and adjust accordingly. That's not the case. Setting the tape block size via mt on server B to match server A, the restore proceeds fine.

↪ replying to MICHAEL CLARK

Paul Watson — Fri, 17 Nov 2006 19:55:28 — source: IIUG Forums & Mailing Lists

IDS version and OS would help Paul Watson Tel: +44 1414161772 Mob: +44 7818003457 Web: www.oninit.com GO FURTHER with DB2 GET THERE FASTER with Informix. Attend IDUG 2007 San Jose, North America May 6-10, 2007 Visit http://www.iiug.org/conf for more information. > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On > Behalf Of MICHAEL CLARK > Sent: 17 November 2006 13:53 > To: ids@iiug.org > Subject: Floating point exception [7826] > > > ontape -r> Floating point exception. > > and no restore occurs > > I'm posting this in case anyone else gets such an error when > trying to restore via ontape. It's a cryptic message. This > occurred to me when transferring an IDS database from one > server to another via ontape. The error occurred because the > block size of the tape drive on the server where ontape was > made did not match the block size of the drive where the > restore was being made. > > mt -f /dev/st? status showed > server A 1024 server B 0 > > server A where ontape was made > server B where restore was desired. > > I was under the impression that a block size of 0 meant the > tape device would read the tape and adjust accordingly. > That's not the case. Setting the tape block size via mt on > server B to match server A, the restore proceeds fine. > > > ************************************************************** > ***************** > Forum Note: Use "Reply" to post a response in the > discussion forum.

↪ replying to MICHAEL CLARK

MICHAEL CLARK — Fri, 17 Nov 2006 20:01:38 — source: IIUG Forums & Mailing Lists

Sorry. IDS 9.40.UC5XD OS server A RedHat ES3 OS server B RedHat ES4 I would think this error would occur regardless of the IDS version as long as it's a ?NIX server with differing tape block sizes.

↪ replying to Paul Watson

Penza Kenneth at MITTS — Mon, 20 Nov 2006 06:52:11 — source: IIUG Forums & Mailing Lists

You must ensure that the block sizes of both drives match. I have experienced the same error message when the logical logs were being backed up with a drive having block size of 0 and restore then on another machine with the drive set to block size of 512. In my case setting the latter one to 0 fixed the problem. Kenneth Penza Technical Services Officer Systems and Database Services Service Management Department Malta Information Technology & Training Services Ltd Please read our Legal Notice: http://emailpolicy.mitts.gov.mt P Please consider your environmental responsibility before printing this e-mail. END OF TEXT -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Paul Watson Sent: 17 November 2006 20:55 To: ids@iiug.org Subject: RE: Floating point exception [7827] IDS version and OS would help Paul Watson Tel: +44 1414161772 Mob: +44 7818003457 Web: www.oninit.com GO FURTHER with DB2 GET THERE FASTER with Informix. Attend IDUG 2007 San Jose, North America May 6-10, 2007 Visit http://www.iiug.org/conf for more information. > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On > Behalf Of MICHAEL CLARK > Sent: 17 November 2006 13:53 > To: ids@iiug.org > Subject: Floating point exception [7826] > > > ontape -r> Floating point exception. > > and no restore occurs > > I'm posting this in case anyone else gets such an error when > trying to restore via ontape. It's a cryptic message. This > occurred to me when transferring an IDS database from one > server to another via ontape. The error occurred because the > block size of the tape drive on the server where ontape was > made did not match the block size of the drive where the > restore was being made. > > mt -f /dev/st? status showed > server A 1024 server B 0 > > server A where ontape was made > server B where restore was desired. > > I was under the impression that a block size of 0 meant the > tape device would read the tape and adjust accordingly. > That's not the case. Setting the tape block size via mt on > server B to match server A, the restore proceeds fine. > > > ************************************************************** > ***************** > Forum Note: Use "Reply" to post a response in the > discussion forum. ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum.

Glossary

ontape