RecoveryOne
ADSM.ORG Senior Member
- Joined
- Mar 15, 2017
- Messages
- 347
- Reaction score
- 81
- Points
- 0
Hello Everyone,
Long time lurker, first time posting here. Have a question regarding TDPO configuration. We have four Oracle boxes each running their own independent databases. No RAC involved. Currently they are all set up to use the same TDPO_NODE name. My understanding the reason for this was our DBA wanted to easily restore NODE_A to NODE_* with ease. Reading the doc at: https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.0/com.ibm.itsm.db.orc.doc/r_dporc_cfg_options.html#r_dporc_cfg_options
“To restore data from one Oracle server to another Oracle server with Data Protection for Oracle, be aware of the following tdpo_node considerations… The value of the tdpo_node option in the tdpo.opt file on the target Oracle server, must equal the value of the tdpo_node option in the tdpo.opt file on the source Oracle server.” Basically, everything was kept the same between all four nodes.
The concern I have is the constant attribute changes in the actlog, I see “ANR1639I Attributes changed for node DB_ORA: TCP Name from node_a to node_b…” or vice versa. Especially around the time the full backups kick off for the various nodes. Now I’m not seeing any evidence of the full or archive’s failing; however, wondering if the attribute switching could cause trouble? There are cases daily where one node is doing a full backup, and another comes in to send its archives.
Would it be best to break out each db into their own name, and then use asnodename for those (hopefully) rare cases of when we want to restore to a different node? Or just reference a different tdpo.opt file all together for that task?
Thanks everyone.
Long time lurker, first time posting here. Have a question regarding TDPO configuration. We have four Oracle boxes each running their own independent databases. No RAC involved. Currently they are all set up to use the same TDPO_NODE name. My understanding the reason for this was our DBA wanted to easily restore NODE_A to NODE_* with ease. Reading the doc at: https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.0/com.ibm.itsm.db.orc.doc/r_dporc_cfg_options.html#r_dporc_cfg_options
“To restore data from one Oracle server to another Oracle server with Data Protection for Oracle, be aware of the following tdpo_node considerations… The value of the tdpo_node option in the tdpo.opt file on the target Oracle server, must equal the value of the tdpo_node option in the tdpo.opt file on the source Oracle server.” Basically, everything was kept the same between all four nodes.
The concern I have is the constant attribute changes in the actlog, I see “ANR1639I Attributes changed for node DB_ORA: TCP Name from node_a to node_b…” or vice versa. Especially around the time the full backups kick off for the various nodes. Now I’m not seeing any evidence of the full or archive’s failing; however, wondering if the attribute switching could cause trouble? There are cases daily where one node is doing a full backup, and another comes in to send its archives.
Would it be best to break out each db into their own name, and then use asnodename for those (hopefully) rare cases of when we want to restore to a different node? Or just reference a different tdpo.opt file all together for that task?
Thanks everyone.