Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Netware & Oracle8

Re: Netware & Oracle8

From: <edpp_at_my-deja.com>
Date: Mon, 06 Sep 1999 11:47:21 GMT
Message-ID: <7r09k8$hdn$1@nnrp1.deja.com> 





Hi,



Here an article which comes with Oracle CD:



(Regards, Eduardo D Piovesam)




Article-ID:         <Note:39582.1>
Document-ID:        OLS:10802111.6
Load-Action:        REPLACE
Creator:            OLSBB
Subject-Area:       platform.Desktop.Netware
Folder:             platform.Desktop.Netware
Topic:              *** Alerts
Subject:            ALERT: NETWARE BLOCK SUBALLOCATION
Creation-Date:      03-JUL-1996 04:31:25
Modified-Date:      11-JUN-1998 05:08:44
Seq#:               1.1
Distribution-Code:  EXTERNAL
Document-Type:      ALERT
Impact:             MEDIUM
Skill-Level:        NOVICE
Platform:           21
Content-Type:       TEXT/PLAIN
External-Key:       :BULLETIN
Keywords:           netware abenc block suballocation redo
Status:             PUBLISHED
Priority:           3
Owner:              EBURNS.US
Reviewer:           PTRENT.US
Moderator:          EBURNS.US
Assigned-Date:      10-JUN-1998 07:26:11
Due-Date:           01-JUL-1998 07:26:11
Version-String:     S.US245097526771:EBURNS.US245097618524





PURPOSE






This alert contains information about NetWare Block Suballocation
causing corrupt REDO LOGS with "OSD-2073 UNABLE TO WRITE TO FILE
(OS 4294967295)", or corrupt CONTROL FILES with "OSD-2075 UNABLE TO
READ FROM FILE (OS 4294967295)".


While this alert refers specifically to the preceding errors,
Oracle does not support suballocation and compression on any
NetWare volumes that contain Oracle data or executables, as
documented in the release notes.  Starting with version 7.3.2.3,
messages will appear in the alert log for any file that is
located on a volume with suballocation enabled.  Starting with
version 8.0.3.0.4, the Oracle Installer will not allow the Oracle RDBMS
to


be installed onto a volume with suballocation enabled.



The corruption that occurs from these NetWare options can affect
any Oracle files, not just the redo log and control files.  The
solution contained within should be used whenever any database
files have been on a NetWare volume with suballocation or
compression.



SCOPE & APPLICATION






The intended audience for this article is Oracle DBAs who have a
moderate knowledge of Oracle7 or Oracle8 Server and an in-depth
knowledge of


Novell NetWare.



This bulletin makes the following assumptions:


     Oracle 7.0, 7.1, 7.2, 7.3 or 8.0 has been installed.



CONVENTIONS AND DEFAULTS






For the purposes of this discussion, the following convention is
used:


     < > indicates a value that you must provide.





EDITING TEXT FILES





Do not edit any text file, such as CONFIG.ORA, INIT<sid>.ORA or
TNSNAMES.ORA using a Windows-based editor, such as Notepad or
Write.  These editors can embed hidden characters in the files,
even when they are saved as ASCII text files.  Instead, use
NetWare's EDIT.NLM or a DOS-based editor.



NETWARE BLOCK SUBALLOCATION






Block Suballocation was introduced with NetWare 4.x.
Block Suballocation optimizes disk space by allowing the
remainder of the OS block to be shared with other files.  For
example, if the NetWare volume block size is 16 KB and an 18 KB
file is created, the 18 KB file requires only one OS block and
four 512-byte suballocation blocks with Block Suballocation.
Thus, the remainder (14 KB) of the second block can be shared
with other files.  An Oracle file created on a suballocated
volume is corrupted immediately upon creation, however, the
corruption may not manifest itself or generate errors until
Oracle attempts to write to the last block of the datafile.



On NetWare 4.x any volumes created automatically have
suballocation and compression enabled. These features must
specifically be disabled at the time the volume is created.
Compression can be disabled at the file or directory level, and
suballocation at the file level.  However suballocation cannot be
disabled until the file has already been created with
suballocation, so the file is already corrupted.  Therefor, we
recommend creating a new NetWare volume without compression or
suballocation.



CONFIRM THAT SUBALLOCATION OR COMPRESSION ARE ENABLED






At the server's console, or, from an RCONSOLE session type the
NetWare command VOLUMES.  This command displays all of the mounted
NetWare volumes on this server.  The last column is labeled FLAGS.
An Sa in the flag column indicates suballocation is enabled;
a Cp indicates compression is enabled.



COMMON ERRORS CAUSED BY SUBALLOCATION & COMPRESSION






If the following sequence of errors occur on the server screen,
in the ALERT.LOG, or in other Oracle trace files, suballocation
and compression might have caused file corruption:



     Hole filled in file xxx block xxx


     ORA-00345: redo log write error block # count #
     ORA-00312: online log 2 thread 1: 'volume:path\RedoLog'
     ORA-09232: Message 9232 not found; product=RDBMS70;
     facility=ORA
     OSD-02073: unable to write to file (OS 4294967295)

     ORA-00204: error in reading control file
     ORA-00447: fatal error in background process
     OSD-02075: unable to read from file (OS 4294967295)

     ORA-01114: IO error writing block to file <name> block #
     <num>
     ORA-09205: sfqio: error reading or writing to file
     OSD-02073: unable to write to file (OS 17)





SOLUTION





NOTE:  Backing up and restoring the database onto a volume

       without suballocation or compression will NOT fix the corruption.
       Once a file has been created on a suballocated volume it is
       corrupted.  Thus, corrupted files will be restored onto the new
       volume.

1.   Perform a full cold backup of the database (so we can return
     to this point in time, if needed).
2.   Perform a full export of the database.  Remember that
     NetWare's file size limitation is 4GB, so larger databases may
     need to be exported by user (schema) and/or table.
     Release 7.3.2.3.6, and later versions, allow the export of more
than 4GB
     by spanning multiple export dump files.
3.   Create as many new NetWare volumes as needed with both
     suballocation and compression disabled.
4.   Reinstall Oracle onto one of the newly created volumes.
5.   Recreate the database.




6.   Import data.


7.   Shutdown the database and immediately perform a cold backup



NOTE:  Do not turn on the AUTOEXEND option when creating a


       tablespace or adding a datafile to a tablespace.



POSSIBLE TEMPORARY WORKAROUND






If the volumes cannot be recreated right away, DIRECTFS may be
disabled.  This is only a temporary workaround and may not work;
the steps in the solution section above MUST be followed to fix
this problem.  To disable DIRECTFS, the following line needs to
be added or modified in the CONFIG.ORA file:


     For 7.0:
       NW_USEDFS=FALSE

     For 7.1 and above:
       NW_FSTYPE=CLIB

     The CONFIG.ORA file is located in the following directory:

       For 7.0           - <oracle_home>\RDBMS70
       For 7.1           - <oracle_home>\RDBMS71
       For 7.2 and above - <oracle_home>\NLM

     After adding the above line to the CONFIG.ORA do the
     following in order for the changes to take effect:

          1.   Shutdown Oracle instance(s).
          2.   Unload all Oracle modules (ORAUNLD).
          3.   Reload all Oracle modules (ORALOAD).
          4.   Restart instance(s).





The SCANFILE.NLM file may temporarily fix the
corrupted Oracle datafile. Contact Oracle Support Services (OSS) and
request


SCANFILE.NLM, which is downloadable from the OSS FTP site.


                                    Oracle Support Services






Sent via Deja.com http://www.deja.com/



Share what you know. Learn what you don't.
Received on Mon Sep 06 1999 - 06:47:21 CDT












Original text of this message













  HOME |
  ASK QUESTION |
  ADD INFO |
  SEARCH |
  E-MAIL US