home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9502.asc
< prev
next >
Wrap
Text File
|
1995-04-12
|
9KB
|
239 lines
TECHNICAL NOTE : ORACLE FOR NETWARE BACKUP USING THE PALINDROME TSA
VERSION NUMBER : 1.0
VERSION DATE : 10 Mar 95
PURPOSE OF THIS TECH NOTE
=============================================================================
To offer possible solutions or work arounds to common problems
encountered when using the Palindrome Oracle TSA.
CONTENTS
=============================================================================
1. Overview
2. General server tuning
3. Verifying the Oracle TSA is set up correctly
4. Problems & solutions
5. Where to locate updates mentioned in this tech note
6. Information to gather before calling for support
7. Issues with specific versions of Oracle
1. Overview
=============================================================================
Oracle is a relational database that runs on several different
platforms. Palindrome's TSA protects Oracle 7.x running on a Netware
server. Prior to the release of this TSA, the Oracle database had
to be shut down to be backed up by our software. This causes down time
for the Oracle server, which in many cases is run 24 hours a day.
Palindrome's Oracle TSA is able to backup the Oracle database while it is
running.
2. General server tuning
=============================================================================
The same updates that can be applied to the server for our 3.1A NLM
software are also applicable here. The patches are :
STRTL3, LIBUP4, LANDR3 & TSA0694. All of these are specific to
the version of Netware. These are the latest patches available &
subject to change with newer versions.
Make sure that you have used the updated files from the Oracle disk :
PNAVOL.EXE, PNAREST.NLM, PNABACK.NLM, PNAUTIL.NLM.
All of these files should be dated 10-21-94.
3. Verifying the Oracle TSA is set up correctly
=============================================================================
We support all versions of Oracle 7.0x, however we have
not tested the TSA with Oracle 7.1 which was recently released.
Oracle 7.1 allows multiple instances of a database to run on a
server which is not supported.
We need to make sure the Archivist user is created on the file
system & database of the Oracle server & given the rights we need.
There is a list of the minuimum rights in the Oracle database on
page 2-8 of the TSA book. A simple solution is to grant the Archivist
user DBA rights which is equivalent to unlimited rights.
Next the DATABASE LOG MODE should be set to ARCHIVELOG
& the AUTOMATIC ARCHIVAL should be set to ENABLED. This is
discussed on page 2-9. You will need to un-remark 3
lines in the INIT.ORA file which is detailed on page 2-10.
This is to PERMANENTLY turn on AUTOMATIC ARCHIVING, akin to adding
a line to AUTOEXEC.NCF, every time the database is brought up.
Both TSAPORA & the Netware file system TSA have to be loaded on the
server.
4. Problems & solutions
=============================================================================
The current shipping TSA cannot determine the path of the control file
when it is replicated. Replicating the Control file is done by adding a
line to INIT.ORA that contains the path of BOTH control files. The Oracle
TSA takes, both paths as 1 complete string (concatenated the paths) and
causes the following:
BS-28 Unable to read file <tablespace name>
fffa0406 The SMS API <NWSMTSReadDataSet> has failed.
The reason is <Oracle failed to parse an alter database
backup controlfile call.>.
ORA-1580 is the error reported on the ORACLE console / ALERT.LOG
There is a updated TSAPORA.NLM which was written to fix the
above problem. ORACL-UP.ZIP with a password of AMOCO.
===============================================================================
If Oracle is configured in the INIT.ORA to refer to the control
files location by a user defined variable Palindrome will report the
following. [ A user defined variable is any variable other than
a system defined one, example of system variable RDBMS70 ]
NOTE: (1 of 2) BS-28 Backup Session Exception
DESCRIPTION: Unable to read file <[AAFDLSF1.Oracle Database
System]AAFDLSF1/AAFDLSF1\SYSTEM>.
WARNING: (2 of 2) SMS-fffdfff2 SMS API Exception
DESCRIPTION: The Storage Management Services API <NWSMTSReadDataSet>
has failed. The reason given is <>.
The problem is that the archive log path Palindrome gets from Oracle does
not give a full path, but rather just a filename. This is due to the fact
that the TSA does not use a user defined variable to locate the path of
the archived log files. Palindrome can't get a full path to the archived
log files, thus the read errors during backup.
The following is an example of a user defined variable, %ORADUMP% , and how
it can be changed to resolve the above problem
Solution 1:
Put a full path in the INIT.ORA file:
old...
log_archive_dest = %ORADUMP%\archive\ #
^^^^^^^^^
change to...
log_archive_dest = SYS:ORACLE\TRACE\archive\ #
For this to take effect you will need to close down the instance then restart the
database and run the backup.
The next two solutions are a different way to achieve the same result as solution
#1. However they are more advanced and may require the assistance of a skilled
Oracle administrator
Solution 2:
Change the location of the archived files to be relative to the
RDBMS70 variable. This would mean they would be located in
\ORANW\RDBMS70\ARCHIVE instead of \ORACLE\TRACE\ARCHIVE. This
means changing the INIT.ORA line to:
log_archive_dest = %RDBMS70%\archive\ #
Solution 3: (temporary solution that can be implemented w/out closing the db)
Change the archived redo log destination parameter dynamically
without having to shut down the database. To do this issue:
ALTER SYSTEM ARCHIVE LOG START TO 'SYS:\ORACLE\TRACE\ARCHIVE\';
Note: the single quotes around the destination path are required.
This does not change where the archived log files are stored.
It only changes how Oracle stores the destination path internally.
Therefore, solution #1 should also be implemented for a
permanent change
All three of the solutions above show how Oracle can point to the path of
the archived log files without a user defined variable. Solution #1 is
5. Where to locate updates mentioned in this tech note.
=============================================================================
The following files mentioned in this tech note can be downloaded from
our BBS ( 708-505-3336).
FILENAME PASSWORD
-------------- --------
LIBUP4.EXE none
STRTL3.EXE none
TSA0694.ZIP none
LANDR3.ZIP none
ORACL-UP.ZIP AMOCO
PALASDUMP.ZIP none
PK204G.EXE none
6. Information to gather before calling for support
=============================================================================
To assist in solving your problem please gather the following
information prior to calling for technical support. Providing it in
advance will save time in getting the issue resolved. These files can be
placed in one ZIP file & uploaded to the Palindrome BBS. If you
decide to upload a file to our BBS you need to let the support engineer
you are working with know the file name. If you are having trouble with
PKZIP type " PKZIP /? " for help.
Files
=====
PALSDUMP.DAT For installation server & Oracle server
these may be the same
INIT.ORA Oracle configuration file
CONFIG.ORA Oracle configuration file
ALERT.LOG Oracle error log
PNA_LOG Palindrome error log
Also include a text file if possible including what output is on
the Oracle server console.
7. Issues with specific versions of Oracle
=============================================================================
7.0.15.5 had a problem in referring to the location of the archived log
files. The only workaround was to use a user defined variable. That is
where we have a problem.
7.0.15.5.2 was a specific patch to fix that problem & allow the location
of the archived log files to be specified by a absolute path or system
defined variable.
7.0.16.6.0 had severe problems in memory usage & should not be used
7.0.16.6.5 is the latest production 7.0x release which Oracle
want's 7.0x customers to update to. ( as of 3-16-95 )
7.1.3 is the latest Oracle release, however we do not
support backing it up since it allows multiple instances of a
database.
As long as Oracle is 7.0.15.5.2 or later, we will not have
trouble locating the location of the Archive Log Files.