How to :Migration from existing 595 into new 595 in RAC?

Hi all,
This is the bit complicated task for me(i.e) first let me explain our environment
We are having 595 two instances (RAC) and 8300 is our storage due to the position we are not able to enhance the memory and CPU in this existing 595 Server.So what we are planning to make another 595 servers with some high configuration?
Since this is new area for me dont know any idea of how to migrate these into new 595 Servers.
fy.i storage will not get any change it will be as it is.
I need any docs or anyone pls share their ideas and steps how they did(suppose if anyone did this already)
Waiting For your reply.
Thanks & Regards
M.Murali..

If your objective is to replace the exiting 595's with new one's then follow the steps below :-
1. configure both the new servers (595) for RAC installation - follow the pre-install steps required for installing clusterware etc. e.g. storage, network, ssh etc..
2. add both the new servers as a "node3" and "node4" into the existing 2-node cluster - follow the "node add" procedure in the documentation
3. turn-off the first 2 nodes on old servers (node1 and node2)
4. test your application with only the nodes...
5. remove the old nodes using "node delete" procedure given in the documentation
reference - http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/adddelunix.htm#BEICADHD
- Siba
http://dbathoughts.blogspot.com

Similar Messages

  • How to migrate from existing Database Usermanagement to Active Directory?

    Hello experts,
    we are running a portal with more than 2000 users. So far our user management is done by the portal´s own identity management with the database as data source.
    However for many reasons instead of the database we would like to use an existing company´s Active Directory (=AD) as a data source for identity management. That means that we would like only to use the AD-users and AD-groups in the portal.
    All users who are in the portal´s database now you can find also in the existing company´s Active Directory. Luckily the users have the same ID both in the database and in the AD.
    We know that the migration form the database to AD is a big issue since many portal objects depend on the existing structures. However because the IDs of users are identical in both systems we hope to finde a way to "override" the existing usermanagement data with the AD data without loosing the existing settings (e.g. KM-Permissions, user profiles etc.).
    Generally I am asking you if you have had already experience with changing the user management´s datasource of an already "living" portal (several 1000 users) to Active Directory User Managent.
    What problems can occour?
    Which modifications need to be done?
    Which portal´s objects are affected by the migration?
    Is a migration possible at all?
    I will appreciate all suggestions, remarks, ideas.
    Thanks in advance.
    Thomas

    Hello experts,
    the current permissions in the KM-Objects are based on both groups and users from database.
    Because it is not possible to modify the Group´s Display Name in the portal´s database we would also like to use LDAP-Groups in the portal: All users and groups in the portal shall be managed by Active Directory in future.
    In the Active Directory it is possible to modify the Display Name of groups. This is a necessary feature because of reorganisations of departments in our company which occur from time to time.
    Creating new groups with the new department names is not an option because one has to assign all department members to the new group again. Otherwise one need to asign the new group to the ACLs of all KM objects in question. This is a too big deal.
    However, thank you for that hint Michael.
    Any other experiences?
    I will appreciate any ideas, foreseen problems.
    Thomas

  • How do I migrate from old Imac to new?

    How do I migrate from old Imac to new?

    Setting-up a new Mac from an old one, its Backups, or a PC 

  • How do I download my music and photos from existing iPad to new iphone

    How do I download music and photos from existing iPad to new iphone

    Perform a backup to iTunes from the old device and then a restore to the new device, use ITunes to do this.  BTW, always sync photos to a computer to store them safely (use iPhoto on a mac or to a designated folder on a PC).  Never trust an iOS device to keep photos without having them synced to a computer.

  • Migrating from old MBP to new

    I've just purchased a new MBP 17" i7 to replace my 2008 MBP 15". When I got my 2008 version, I just used the Firewire 800 to move all of my stuff from my iMac to my MBP. Spent a few minutes fixing some passwords, and that was that. Probably took around an hour.
    So, I haven't migrated between Macs for a couple of years, and I want to find out what the best way to proceed. I use Time Machine to back up my computer, and have all of my iTunes media files on a portable 1TB hard drive (I've got thousands of songs in Apple Lossless). So here are my questions:
    1. Should I migrate from my old to new via Firewire? Or is it best to restore from Time Machine?
    2. Will Time Machine "start over." Will I lose 2 years of incremental backups? It's nice to know I can go digging back a couple of years to find that file I shouldn't have erased. Also, every once in a while a piece of music gets corrupted, and I've got to get it replaced by an older saved version.
    3. This might not be the right place, but will I be able to point iTunes on the new MBP to my media files? I'm convinced I can, but I'm not sure.
    I'm going to wait a few days to do the migration, because I want to do this right. A few years ago, I did it wrong and lost years of photos, of which 90% were lost forever.

    OrangeMarlin wrote:
    So, I haven't migrated between Macs for a couple of years, and I want to find out what the best way to proceed.
    +Setup Assistant+ has been greatly improved for Snow Leopard. See #19 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).
    1. Should I migrate from my old to new via Firewire? Or is it best to restore from Time Machine?
    Makes little difference. It's a bit easier from Time Machine, since you don't have to start up the old Mac in Target Disk mode and make the connection, but otherwise it makes no difference (assuming you didn't exclude anything important from Time Machine).
    2. Will Time Machine "start over."
    As William says, yes.
    Will I lose 2 years of incremental backups?
    Depends on how much space is on your Time Machine drive.
    It's nice to know I can go digging back a couple of years to find that file I shouldn't have erased. Also, every once in a while a piece of music gets corrupted, and I've got to get it replaced by an older saved version.
    Yup, absolutely. If you keep the old drive "on the shelf" you can always display and restore from it via the +*Browse ...+ option, per #17 in the FAQ.
    Or, if you get a new, larger drive, you can copy the existing backups to it, and continue backing-up to the same set of backups. See #18 in the FAQ. If you do that, when the first backup of the new Mac starts, you'll get the prompt in #B5 of Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).
    3. This might not be the right place, but will I be able to point iTunes on the new MBP to my media files? I'm convinced I can, but I'm not sure.
    Yup. Just hold down the Option key while starting iTunes; you get a prompt to Create a library or Choose an existing one.
    I'm going to wait a few days to do the migration, because I want to do this right. A few years ago, I did it wrong and lost years of photos, of which 90% were lost forever.
    I'd recommend against that. +Setup Assistant+ runs immediately when you first boot the new Mac up; if you take all the defaults, it will move everything from the old Mac (or backups) except OSX. No temporary user profile, no setting-up communications, etc.
    If you're nervous about losing things, and don't have secondary backups, do your final Time Machine backup of the old Mac, and turn it off. Use the backups to transfer your data, so the old Mac won't be involved at all.

  • I have chosen to fil migrate from old ibook to new MacBook Pro using Time Machine after establishing admin account. I now have two admin. accounts and wish to delete the later one and transfer files manually. I am worried I will loose both accounts. ??

    I have chosen to fil migrate from old ibook to new MacBook Pro using Time Machine after establishing admin account. I now have two admin. accounts and wish to delete the later one and transfer files manually. I am worried I will loose both accounts. ??

    Use the Office for Mac and ignore using Parallels for that. If you have PC only apps you have to run that are MS Windows only then consider Parallels. Just transfer your main PC, using Migration Assistant.  If you don't know how then simply read over Pondini's article called Lion or Mountain Lion Setup Assistant tips and look for the section on migrating from a PC. Millions have done what you are about to, it's far from leading edge these days, if you go to an Apple Store to purchase they will offer this as a service, something you might be interested in.

  • HT4413 I migrating from my macbook to new imac. nothing showed up until I turned off the imac but everything I had done previously on the imac disappeared.

    I was migrating from macbook to a new imac.
    Nothing showed up until I turned off the imac.
    When I restarted the imac everythign I'd previously done was gome and the migrated macbook desktop had taken over.
    How do I bring back the original imac settings.
    Thanks

    You can't. When you migrate user accounts, those settings will be used. That's the point of migrating, not to have to reset things Peruse Pondini's Setup New Mac guide for details.
    If you want to revert to the original user settings, create an new admin user account. That'll use the default user setup.

  • How to Migrate the Existing Content

    Hi every1,
      I want to know how to Migrate the existing content in Interwoven to new Content Management system
    Thanks & Regards
    Vasu

    Hi Vasu,
    as said, I don't know Interwoven in detail. But if you would get the Interwoven Business Package, maybe you could get some insight how to access Interwoven content per API (at least, Interwoven <i>has</i> a Java API, see http://blogs.ittoolbox.com/km/content/archives/005150.asp for example; but I would ask Interwoven or within some Interwoven forum for the details, and on this site for the details of SAP KM API... ).
    Hope it helps
    Detlev
    PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

  • How to migrate PowerBook G4 Tiger to new MacBook Pro 15" Lion via ethernet cable? Migration Assistant to old to update, apparently.

    How to migrate PowerBook G4 Tiger to new MacBook Pro 15" Lion via ethernet cable? Migration Assistant to old to update, apparently.

    Ah, a Powerbook. I miss that.  Anyways, I believe that the Powerbook G4 has an Firewire 400/800 port.  Why don't you do that?  It's fast, and you don't have to set up one of those funky reverse wire ethernet cables.  I wouldn't use Migration Assistant, but that's just me.  Too many issues.  I'd start up your brand new MacBook Pro and during the setup assistant, it'll ask you to transfer data from an older Mac.  Using firewire with a Target Disk Mode, it's pretty fast.
    If you have already opened up your new Mac and are using it, then use Migration assistant, but also with the Firewire (preferably 800).

  • Cant find my iTunes library after migration from old PC to new Mac

    Can't find my iTunes library after migration from old PC to new Mac?

    Migration Assistant has transferred itunes content, but where is it on new iMac?
    https://discussions.apple.com/thread/3358162?start=0&tstart=0   <<< click here for a possible answer.

  • I am trying to migrate from macbook to a new imac and the looking for source keeps spinning

    I am trying to migrate from macbook to a new imac and the looking for source keeps spinning

    The warranty entitles you to complimentary phone support for the first 90 days of ownership.

  • HT1444 how to migrate from yosemite beta to full vesion

    Hi
    how to migrate from yosemite beta to full vesion

    When I look in "about this mac" - it says Yosemite 10.10. Do I really need to download it again?
    I found on a blog that someone contacted the Apple service:
    “simply install the final version of the software you are testing when it appears in Software Update” – that means the final version of the beta software you are given to test is what will be made public. So we’re on the same build as what is now in the App Store.
    My compute OSX is 10.10 but build is (14A388b) while some say that app store version is (build 14A389).
    Does it really make a difference? If I don't download it will it continue to update?

  • How do I migrate from 2008 iMac to new iMac?

    How do I migrate from a 2008 iMac to a new 2014 iMac?

    You can use Migration Assistant to move your older iMac's data to your new iMac:
    http://macs.about.com/od/OS-X-Yosemite/ss/OS-X-Yosemite-Migration-Assistant-Tran sfer-Your-Data-to-a-New-Mac.htm
    Tom

  • How to migrate from a standard store setup in a splitted store (msg - idx) setup

    How can I migrate from a standard store setup in a splitted setup described in
    https://wikis.oracle.com/display/CommSuite/Best+Practices+for+Messaging+Server+and+ZFS
    can a 'reconstruct' run do the migration or have I do a
    imsbackup - imsrestore ?

    If your new setup would use the same filesystem layout as the old one (i.e. directory paths to the files would be the same when your migration is complete) you can just copy the existing store into the new structure, rename the old store directory into some other name, and mount the new hierarchy instead of it (zfs set mountpoint=...). The CommSuite Wiki also includes pages on more complex migrations, such as splitting the user populace into several stores (on different storage) and/or separate mailhosts. That generally requires that you lock the user in LDAP (perhaps deferring his incoming mail for later processing into the new location), migrate his mailbox, rewrite the pointers from LDAP, reenable account. The devil is in the details, for both methods. For the latter, see Wiki; for the former I'll elaborate a bit here
    1) To avoid any surprises, you should stop the messaging services before making the filesystem switch, finalize the data migration (probably with prepared data already mostly correct in the new hierarchy before you shut down the server, just resync'ing the recent changes into new structure), make the switch and reenable the server. If this is a lightly-used server which can tolerate some downtime - good for you If it is a production server, you should schedule some time when it is not very used so you can shut it down, and try to be fast - so perhaps practice on a test system or a clone first.
    I'd strongly recommend taking this adventure in small reversible steps, using snapshots and backups, and renaming old files and directories instead of removing them - until you're sure it all works, at least.
    2) If your current setup already includes a message store on ZFS, and it is large enough for size to be a problem, you can save some time and space by tricks that lead to direct re-use of existing files as if they are the dataset with a prepopulated message store.
    * If this is a single dataset with lots of irrelevant data (i.e. one dataset for the messaging local zone root with everything in it, from OS to mailboxes) you can try zfs-cloning a snapshot of the existing filesystem and moving the message files to that clone's root (eradicating all irrelevant directories and files on the clone). Likewise, you'd remove the mailbox files on the original system (when the time is right, and after sync-ing).
    * If this is already a dedicated store dataset which contains the directories like dbdata/    mboxlist/  partition/ session/   and which you want to split further to store just some files (indices, databases) separately, you might find it easier to just make new filesystem datasets with proper recordsizes and relocate these files there, and move the partition/primary to the remaining dataset's root, as above. In our setups, the other directories only take up a few megabytes and are not worth the hassle of cloning - which you can also do for larger setups (i.e. make 4 clones and make different data at each one's root). Either way, when you're done, you can and should make sure that these datasets can mount properly into the hierarchy, yielding the pathnames you need.
    3) You might also look into separating the various log-file directories into datasets, perhaps with gzip-9 compression. In fact, to reduce needed IOPS and disk space at expense of available CPU-time, you might use lightweight compression (lzjb) on all messaging data, and gzip on WORM data sets - local zone, but not global OS, roots; logs; etc. Structured databases might better be left without compression, especially if you use reduced record sizes - they might just not compress enough to make a difference, just burning CPU cycles. Though you could look into "zle" compression which would eliminate strings of null bytes only - there's lots of these in fresh database files.
    4) If you need to recompress the data as suggested in point (3), or if you migrate from some other storage to ZFS, rsync may be your friend (at least, if your systems don't rely on ZFS/NFSv4 ACLs - in that case you're limited to Solaris tar or cpio, or perhaps to very recent rsync versions which claim ACL support). Namely, I'd suggest "rsync -acvPHK --delete-after $SRC/ $DST/" with maybe some more flags added for your needs. This would retain the hardlink structure which Messaging server uses a lot, and with "-c" it verifies file contents to make sure you've copied everything over (i.e. if a file changes without touching the timestamp).
    Also, if you were busy preparing the new data hierarchy with a running server, you'd need to rsync old data to new while the services are down. Note that reading and comparing the two structures can take considerable time - translating to downtime for the services.
    Note that if you migrate from ZFS to ZFS (splitting as described in (2)), you might benefit from "zfs diff" if your ZFS version supports it - this *should* report all ofjects that changes since the named snapshot, and you can try to parse and feed this to rsync or some other migration tool.
    Hope this helps and you don't nuke your system,
    //Jim Klimov

  • Migrated from old Mac to new Mac with Lion, iPhoto 6 still here, can't update

    Hi, I just migrated from an old MacBook to a brand new MacBook Pro. The Apple Store did the migration for me. For some strange reason, iPhoto 6 is present on this Mac, even though it should have come with iPhoto '11. I understand that I should be able to install iPhoto '11 from the App Store, since this Mac is entitled to it, but it only shows up as a $15 purcahse instead.
    Does anyone know how to get the App Store to recognise that this Mac shipped with, and is entitled to, iPhoto '1?

    First, get rid of any old copy of iPhoto you have on the new computer. Log into the App Store using your Apple ID. Click on Purchases icon. At the top you should find the three iLife apps with an Accept button to click on. Then you can download iPhoto without having to pay for it.

Maybe you are looking for