05-06-2014
Assuming that all the data files of the database are on the ufsbackup tape, then you should be able to restore on a replacement server. Are you doing this in preference to export/import of the data?
You might need to get the files in exactly the same location on the target server so that the devices that Oracle is expecting all exist as the correct names - apologies if this is stating the obvious. You would also need to consider files that oracle uses that are not the data files, e.g. the parameter file, /etc/oratab, any startup scripts etc.
Personally, I would favour building the new server with an up-to-date oracle install and export/import. If space to export to is a problem, then this can be done across the network and imported at the same time to the target.
Regards,
Robin
This User Gave Thanks to rbatte1 For This Post:
3 More Discussions You Might Find Interesting
1. Solaris
I installed Oracle 10 software on Solaris 11 Express, everything was fine execpt I can't create database using dbca.rsp file. I populated file with following options.
OPERATION_TYPE = "createDatabase"
GDBNAME = "solaris_user.domain.com"
SID = "solaris_user"
TEMPLATENAME = "General... (0 Replies)
Discussion started by: solaris_user
0 Replies
2. Solaris
Hi guys, long time no typing :D
I have problems when I try to connect to Oracle database from SQL Developer which is located on my Windows box.
Server is running Solaris 11/11 and Oracle 11 enterprise. I can log in locally with sys account to database, start it up and shut it down but when I... (2 Replies)
Discussion started by: solaris_user
2 Replies
3. UNIX and Linux Applications
Good evening
I nned your help pls, In an unix server i want to connect to a remote oracle databse server by sqlplus.
I tried to find out the user/passwd and service name by env variable and all Ive got is this:
ORACLE_SID_REPCOL=SCL_REPCOL
ORACLE_SID=xmeta
ORACLE_SID_TOL=SCL_PROTOLCOL... (2 Replies)
Discussion started by: alexcol
2 Replies
LEARN ABOUT SUSE
apache::session::oracle
Session::Oracle(3) User Contributed Perl Documentation Session::Oracle(3)
NAME
Apache::Session::Oracle - An implementation of Apache::Session
SYNOPSIS
use Apache::Session::Oracle;
#if you want Apache::Session to open new DB handles:
tie %hash, 'Apache::Session::Oracle', $id, {
DataSource => 'dbi:Oracle:sessions',
UserName => $db_user,
Password => $db_pass,
Commit => 1
};
#or, if your handles are already opened:
tie %hash, 'Apache::Session::Oracle', $id, {
Handle => $dbh,
Commit => 1
};
DESCRIPTION
This module is an implementation of Apache::Session. It uses the Oracle backing store and no locking. See the example, and the
documentation for Apache::Session::Store::Oracle for more details.
USAGE
The special Apache::Session argument for this module is Commit. You MUST provide the Commit argument, which instructs this module to
either commit the transaction when it is finished, or to simply do nothing. This feature is provided so that this module will not have
adverse interactions with your local transaction policy, nor your local database handle caching policy. The argument is mandatory in order
to make you think about this problem.
This module also respects the LongReadLen argument, which specifies the maximum size of the session object. If not specified, the default
maximum is 8 KB.
AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>.
SEE ALSO
Apache::Session::File, Apache::Session::Flex, Apache::Session::DB_File, Apache::Session::Postgres, Apache::Session
perl v5.12.1 2007-09-28 Session::Oracle(3)