From GE:
(for Oracle DB's)
Hi Ed,
Attached is the information regarding setting up a test server. Please note, this documentation is written to be used to migrations rather than a test server, but the steps are the same (minus swapping IP’s and whatnot)
When building the test database be sure the drive mappings are identical, as well as the install path of the Database and oracle binaries.
Please let me know if you have any questions.
Thank You,
Customer Support Engineer
GE Healthcare IT
Centricity Services – EMR
Then they'd attached this word document:
(If not migrating – and just setting up a test instance.. you can skip 1, 6,7, maybe 14.)
Essentially you need to set up the source and destination server (test) with the same install path/oracle file structure/etc, shutdown oracle on both, then copy 3 things:
1. \servernamed$oracleadmin
2. \sfh95000ot2d$oracledata
3. \sfh95000ot2d$oracleora11.2.0database
all to the respective locations in the test system. The boot them up, and see how it goes.
Migration of an Oracle database between Servers with compatible Operating Systems
Topic: Migration of an Oracle database between Servers with compatible Operating Systems. Or, more specifically, moving the database from a Win2k Server to another Win2k Server, or Windows 2003 to Windows 2003.
Product: All
Environment: Win2k, Win2k3, Oracle 9i & Oracle 10g
Severity: Low
Information: When a customer is migrating a database from one Server platform to another and the two are NOT compatible ie Novell or Unix to Win2k or Win2k3 or vice versa (or the customer feels the database requires defragmenting) see k-base http://kbase/LE/data/2340.html . If the Operating Systems are compatible, the procedure is much simpler:
NOTE: Do not put both Servers on the same network until you have completed steps 1-6.
1) 1) Before putting the destination Server on the network, be sure that the Server has the same IP Address and Name as the source Server.
2) 2) On the destination Server, install a fresh copy of the Logician DB version being migrated. Ensure the same Database Name and SID are used.
3) 3) Ensure that the destination database is functional and that a Logician client can access it.
4) 4) Ensure that the directory structure contained under the <drive>:Orant or <drive>:Oracle folder are the same on both Servers.
5) 5) On both Servers ensure that the Logician database is shut down.
6) 6) Change the Name, and IP address of the Source server (using the same subnet).
7) 7) Establish network connectivity between the two Servers. Preferably isolated from the production network, but either way should work.
8) 8) On the Destination Server browse to the “<drive>:orant folder and rename the “data” folder to “data_old”.
9) 9) Now browse to the source server, “<drive>:orant folder, highlight and copy the “data” folder.
10) 10) Paste the “data” folder into the destination Server’s “<drive>:orant” folder. Be patient, this could take some time depending on the size of the database.
11) 11) Next, also on the destination Server in the “<drive>:orant folder, rename the “admin” folder to “admin_old”.
12) 12) Now browse to the source server, “<drive>:orant folder, highlight and copy the “Admin” folder.
13) 13) Paste the “admin” folder into the destination Server’s “<drive>:orant” folder.
14) 14) If you aren’t already connected, you can connect the destination Server to the production network at this time.
15) 15) Startup the database on the destination Server and verify that Logician clients can connect and that all data is now available.
16) 16) You can now delete the “<drive>:orantdata_old” and “<drive>:orantadmin_old” folders.
17) 17) Normally, at this juncture I would say shutdown Oracle and make a good cold backup, but in this case one already exists on the source Server. It’s up to you whether that’s sufficient or not.
Hope that helps.
Posted : June 4, 2013 9:58 am
I have no experience with Oracle at all but I imagine it can't be too much different. Good luck getting it set up!
