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

Home -> Community -> Usenet -> c.d.o.server -> Re: move 4 instaces from one server to another

Re: move 4 instaces from one server to another

From: Jonathan Gennick <gennick_at_worldnet.att.net>
Date: Sat, 13 Jun 1998 03:10:07 GMT
Message-ID: <6lsqi4$nvt@bgtnsc03.worldnet.att.net>


On Thu, 11 Jun 1998 15:22:48 GMT,
Abeeda_Mohammed_at_xn.xerox.com wrote:

>Hello, If I have to move 4 intances from one server to another and I have a
>full backup, what are the steps to follow. This is on NT 4.0 and the RDBMS
>version is 8.03

Last time I moved an instance, I did something resembling the following:

	0.	I actually wrote all the scripts ahead of time,
		and then ran them in the order described below.
	1.	Created the new instance.
	2.	Created the tablespaces, rollback segments, etc.
	3. 	Created all neccessary user-ids and roles for the
		application users.
	4.	Arranged for TNSNAMES files on client PCs to
		be updated so that users could access the new
		database.
	5.	Send each user their new user-id & password.
		Asked them to test w/SQL*Plus to verify that
		they could connect. Our users are all developers
		and analysts, so they know how to use SQL*Plus.
	6. 	Resolved a number of configuration problems.
	7.	Wrote scripts to export and then import
		the schemas that actually had data. I did
		not export/ import the entire database. I did
		four exports, one for each owner. 
	8.	Did a preload of the data to test the
		export/import scripts, and so users 
		could test against the the new instance.
	9.	Told developers that the new instance was 
		up and assumed that they would test run
		the application against it. This was a bad 
		assumption. I should have specifically arranged
		for the application to be tested.
	10.	A week later, no problems were reported, so
		I cut everyone over one night.
	11.	Tore my hair out the next day because no one
		could connect with the application. Everyone had
		just tested w/SQL*Plus.
	12.	Resolved various SQL*Net and TCP/IP configuration
		problems.
	13.	Turned off the old database.

Do as much upfront planning as possible. If you can have both instances up and running simultaneously, use that to your advantage by testing your applications against the new instances. I don't know how big your databases are. Ours are less than a gig, so moving them once for testing and again for real was not a problem.

regards,

Jonathan Received on Fri Jun 12 1998 - 22:10:07 CDT

Original text of this message

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