03-13-2008
Data Migration(Oracle)
Hello All,
I am part of a planning process to migrated 40+ Sparc(Solaris8) server from site 'A' to site 'B', these server house oracle databases. We will setup a staging environment in site B, then go thru a cutover process. Currently we are thinking of TARing the ORACLE datafiles, saving them USBdrive or tape, then overnighting from site A to site B. Network transfer is not an option at this point.
What does everyone think of this approach?
TIA,
Vada010
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Good Morning.
The problem started after tha migration to a newer version of oracle - migration to oracle 9i. Before the migration jobs that were scheduled in crontabs were running ok. but after the migration they are not running.
I understand that is not easy to find out what the problem is.... (4 Replies)
Discussion started by: alexcol
4 Replies
2. UNIX for Dummies Questions & Answers
Hi,
i willbe very much grateful to u if u help me out..
if i simply connect pbx machine to printer by serial port RS232 then we find this view:
But i want to capture this data into database automatically when the pbx is running.The table in database will contain similar to this view inthe... (1 Reply)
Discussion started by: boss
1 Replies
3. Shell Programming and Scripting
Hi All,
I have a requirement to write a shell script for the following...
we have 3 different database.... lets say A, B, C
From these 3 DBs, i need to get data.. all have 3 different table...a,b, c
A.a => Emp_code, count(*)
B.b => emp_code, count(*)
C.c => emp_code, copunt(*)
Once get this... (4 Replies)
Discussion started by: Amit.Sagpariya
4 Replies
4. Solaris
Using Solaris 10 with Veritas Storage Foundation running. I want to copy all contents from DISKA LUN1 to DISKB LUN2. What would be the command syntax to do this? (0 Replies)
Discussion started by: soupbone38
0 Replies
5. Shell Programming and Scripting
Hi All
I am able to connect my oracle database with Perl and able to execute the queries.
There is one schema names master19 which contains 50 table.
I want to take backup of each table in and store at a given directory location in Perl
For example suppose if a table student is present in... (1 Reply)
Discussion started by: parthmittal2007
1 Replies
6. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
7. Web Development
Working on LP: 10. Lesson 1: Oracle JET 4.x - Lesson 1 - Part 4: Data Binding in this Oracle JET online course - Soar higher with Oracle JavaScript Extension Toolkit (JET), I have created this code for incidents.js
I cannot get the load average data in this Oracle JET test to update the... (4 Replies)
Discussion started by: Neo
4 Replies
rpc.lockd(8) System Manager's Manual rpc.lockd(8)
NAME
rpc.lockd, lockd - Network lock daemon
SYNOPSIS
/usr/sbin/rpc.lockd [-b hostname] [-c] [-d debug] [-g graceperiod] [-h hashsize] [-s] [-t timeout]
OPTIONS
The default behavior will create and bind a socket for each protocol per interface on the system. When the -b switch is specified, one
socket per protocol will be created and bind to the passed IP address. Available only on TruCluster Server systems. This option starts the
clusterwide lock daemon, which helps provide highly available NFS service. Do not use -c directly. Highly available NFS service is config-
ured by default and typically does not require intervention. If you do need to start the clusterwide lock daemon, use the CAA command,
caa_start cluster_lockd.
For more information, see the TruCluster Server Administration manual. Internal Use Only. Use this option only under the direction
of technical support personnel. Causes the rpc.lockd daemon to use the variable graceperiod (in seconds) as the grace period dura-
tion instead of the default value of 15 seconds. Internal Use Only. Causes the rpc.lockd daemon to use the variable timeout (in
seconds) as the interval instead of the default value of 5 seconds to retransmit a lock request to the remote server.
DESCRIPTION
The rpc.lockd daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking
service makes this advisory locking support possible by using the fcntl system call and the lockf subroutine. The rpc.lockd daemon forwards
lock requests for remote data to the server site's lock daemon. The rpc.lockd daemon then requests the status monitor daemon, rpc.statd,
for monitor service. The reply to the lock request is not sent to the kernel until the status daemon and the server site's lock daemon have
replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site lock daemons to submit reclaim requests. Client site lock daemons
are notified by rpc.statd of the server recovery and promptly resubmit previously granted lock requests. If a client site's lock daemon
fails to secure previously granted locks at the server site, it sends the signal SIGLOST to all the processes that were previously holding
locks and cannot reclaim them.
SEE ALSO
Commands: rpc.statd(8)
Functions: fcntl(2), signal(2), lockf(3)
rpc.lockd(8)