user3392221 wrote:do you relocate to RAC DB(existed)?
Scenaroi: relocate the database with 2 instances on the 2 existing Oracle RAC DB servers.
Q: 1) should I create or register resources for the new LISTENERs and VIP? The LISTENER and VIP will not use the existing LISTENER or VIP.If on existing RAC have VIP/LISTENER. don't create/ register new...
2) how many resorces and in what sequences to register or create with the existing Oracle Clusterware? Should start the DB first, and then complete the rest taks?i'm not sure resource number on RAC.
user3392221 wrote:OK.. I'm not sure I get your idea...
Thanks so much! It is very helpful.
Condition 1: The 2 dbs relocated on the existing servers are using different VIP, and it will also keep the VIP.
2: A new listener will need it to associate with the VIP, so it needs to create another listener.
Please advise to add different VIP and LISTENRE to the existing servers.
I really appreciate your help, thanks again!!!
user3392221 wrote:Actually On one node only uses on a Listener as well.
I see, 1 VIP for all databases which is Oracle's recommendation. I will check the VIP on all of the servers now, and find out.
Per metalink and Oracle Docs, srvctl can not new LISTENER with 10.2...., is there any other command to create new listener? The netca is not install on the server, I do not really add netca for this purpose.
Please continue helping, I really appreciate. Thanks again!
user3392221 wrote:Yes... you should make oracle user to run start VIP .
Thanks for the reply again!
The situation, with DoD, only allow to use the default port. Since 2 database under the CRS, the solution is to assign different IP for each DB.
Regarding the listener, the team will create listener manually, and then use crs_register with LISTENER_SERVER_NAME.cap to register the listener.
I tested the registration, I have seen the component for the new listener.
Now 1 more question, does the following is necessary to active the VIP for the coming DB:
1) Change the owner of the resource as root:
$ crs_setperm <network> –o root
2) Enable the db user to run the script as root:
$ crs_setperm <network> –u user:oracle:r-x
3) Start the VIP address as db_user:
$ crs_start <network>
Please advise, and I really appreciate the hlp.