Re: TDP Oracle config question
Does this mean the error is going to be produced every time we run the backup? Is this a known issue with TSM? Can we safely ignore it, then? -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:Conko, Steven [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
I don't think anyone answered today, you can sefely ignore. It's not a TSM issue, it's how RMAN works. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/25/03 09:32AM Does this mean the error is going to be produced every time we run the backup? Is this a known issue with TSM? Can we safely ignore it, then? -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:Conko, Steven [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: TDP Oracle config question
So is this an expected error message every time we run the TDP? Does that mean it can be ignored? -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:Conko, Steven [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:Conko, Steven [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
So, we should just ignore the error? -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, The reason that you are seeing this error is that Oracle/Rman first tries to delete the backuppiece that it is about to create on the TSM Server. In this way Oracle/Rman ensures that only one copy of the backuppiece exists on the Backup Media so Rman tries to delete the backuppiece in case it already exists. The Rman specifications state that only one copy of a backuppiece will exist at one time on Media Manager (DP for Oracle). Unfortunately, Oracle/Rman also specifies that the delete routine act as single and seperate operation, so when Oracle tries to delete a backuppiece that does not exist, that is an error and DP for Oracle returns that error. There is no way for DP for Oracle to determine if the deletion is a true delete of a backuppiece or if Oracle is checking for backuppiece existence prior to backup. Hope this helps clear things up. -- Date:Wed, 16 Jul 2003 13:13:39 -0600 From:Conko, Steven [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
Steve, Can you answer me this? Does your backup actually fail, or is this just something that shows up during a successful backup? The /adsmorc filespace is a TSM Server filespace and is the default for TDP Oracle and will get created during the backup, if it doesn't already exist. Unless of course, you are specifying something other than the default (the option is TDPO_FS). -- Date:Tue, 15 Jul 2003 13:42:36 -0600 From:Conko, Steven [EMAIL PROTECTED] Subject: TDP Oracle config question TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
Neil, Im still waiting to find out from the DBA running it if he thinks it is succeeding or failing. Right now we dont have TDPO_FS defined so it is defaulting to adsmorc. My question is: is this only a filespace created within TSM Server storage or does there need to be an actual directory/mount point on a server somewhere? The documents mention including this filespace in the include/exclude list which leads me to believe I need to create the directory somewhere. Is that so? Thanks Steve -Original Message- From: Neil Rasmussen [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 11:35 AM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question Steve, Can you answer me this? Does your backup actually fail, or is this just something that shows up during a successful backup? The /adsmorc filespace is a TSM Server filespace and is the default for TDP Oracle and will get created during the backup, if it doesn't already exist. Unless of course, you are specifying something other than the default (the option is TDPO_FS). -- Date:Tue, 15 Jul 2003 13:42:36 -0600 From:Conko, Steven [EMAIL PROTECTED] Subject: TDP Oracle config question TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve Regards, Neil Rasmussen Software Development TDP for Oracle
Re: TDP Oracle config question
You should NOT create a /adsmorc filesystem or mount point. The docs are correct, this is just the filespace name used on the server for this node name. You could change it to something else if you want with the TDPO_FS env variable. The message you are getting tells you that that particular object name does not exist on the server. Do a q filespace blah for the node name you are using and you should see /adsmorc. Is this happening when the RMAN scripts try to delete an object? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/15/03 03:42PM TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: TDP Oracle config question
Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question You should NOT create a /adsmorc filesystem or mount point. The docs are correct, this is just the filespace name used on the server for this node name. You could change it to something else if you want with the TDPO_FS env variable. The message you are getting tells you that that particular object name does not exist on the server. Do a q filespace blah for the node name you are using and you should see /adsmorc. Is this happening when the RMAN scripts try to delete an object? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/15/03 03:42PM TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: TDP Oracle config question
No idea about the missing -. I believe the long name is built by Oracle/RMAN and not TSM. So need to look there. I don't know how that is put together, need to get with your DBA or Oracle on that. (I just looked at mine and all my RMAN backups use _ as separators and have different numbering format, but still a long name.) We have unique names for each node with TDPO_FS, it's not really required though, you could use /adsmorc for each one. I think a good naming standard for your environment is best. David Longo [EMAIL PROTECTED] 07/16/03 03:13PM Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question You should NOT create a /adsmorc filesystem or mount point. The docs are correct, this is just the filespace name used on the server for this node name. You could change it to something else if you want with the TDPO_FS env variable. The message you are getting tells you that that particular object name does not exist on the server. Do a q filespace blah for the node name you are using and you should see /adsmorc. Is this happening when the RMAN scripts try to delete an object? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/15/03 03:42PM TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ## ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: TDP Oracle config question
Thanks again. One more quick question... does the filespace name, such as /adsmorc need to be included in the include/exclude list as the docs state? I suppose if so it would be on the TDP client? -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question No idea about the missing -. I believe the long name is built by Oracle/RMAN and not TSM. So need to look there. I don't know how that is put together, need to get with your DBA or Oracle on that. (I just looked at mine and all my RMAN backups use _ as separators and have different numbering format, but still a long name.) We have unique names for each node with TDPO_FS, it's not really required though, you could use /adsmorc for each one. I think a good naming standard for your environment is best. David Longo [EMAIL PROTECTED] 07/16/03 03:13PM Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question You should NOT create a /adsmorc filesystem or mount point. The docs are correct, this is just the filespace name used on the server for this node name. You could change it to something else if you want with the TDPO_FS env variable. The message you are getting tells you that that particular object name does not exist on the server. Do a q filespace blah for the node name you are using and you should see /adsmorc. Is this happening when the RMAN scripts try to delete an object? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/15/03 03:42PM TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ## ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions
Re: TDP Oracle config question
We use it here, well sort of. We have a separate node name for the RMAN backups on each client, that is one node name for B/A on this machine and a separate node name for the RMAN/TDPO client. Therefore we have two stanzas each in dsm.sys and dsm.opt and have separate backup.excl files. For the one for TDPO/RMAN, we have one line: include * oracleclass If you had one backup.excl, then I think you would have: include /adsmorc oracleclass plus whatever other includes/excludes you use. Haven't used it that way as ours was setup with separate files and I continued that format as it works o.k. for us. David Longo [EMAIL PROTECTED] 07/16/03 03:47PM Thanks again. One more quick question... does the filespace name, such as /adsmorc need to be included in the include/exclude list as the docs state? I suppose if so it would be on the TDP client? -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question No idea about the missing -. I believe the long name is built by Oracle/RMAN and not TSM. So need to look there. I don't know how that is put together, need to get with your DBA or Oracle on that. (I just looked at mine and all my RMAN backups use _ as separators and have different numbering format, but still a long name.) We have unique names for each node with TDPO_FS, it's not really required though, you could use /adsmorc for each one. I think a good naming standard for your environment is best. David Longo [EMAIL PROTECTED] 07/16/03 03:13PM Thanks for that bit of information... it definitely clears some things up. According to the docs, we should be using unique TDPO_FS names for each node we are backing up using TDP, correct? After doing the query and some further investigation into the BACKUPS table, it appears we are getting this message because of a missing - When I do a select in the BACKUPS table, the LL_NAME shows up as: c-3756527612-2003-0714-02 However, in the error we are getting, the name of the object is: c-3756527612-20030714-02 Any idea why this is?? Steve -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: Re: TDP Oracle config question You should NOT create a /adsmorc filesystem or mount point. The docs are correct, this is just the filespace name used on the server for this node name. You could change it to something else if you want with the TDPO_FS env variable. The message you are getting tells you that that particular object name does not exist on the server. Do a q filespace blah for the node name you are using and you should see /adsmorc. Is this happening when the RMAN scripts try to delete an object? David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 07/15/03 03:42PM TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ## ## This message is for the named person's use only. It may contain confidential, proprietary
TDP Oracle config question
TSM Server: AIX 4.3.3, TSM 5.1.5.4 RMAN Server: AIX4.3.3, TDP 5.2 RMAN Client: AIX 4.3.3, TSM 5.1.5, TDP5.2 The installation guide seems to be a little fuzzy on this topic... At some point during the backup process we get this error in our tdpoerror.log file: 23:28:55 ANS4994S TDP Oracle AIX ANU0599 ANU2602E The object /adsmorc//c-3756527612-20030714-03 was not found on the TSM Server After doing some of my own research I realize its telling me that the /adsmorc file space does not exist. My question is where is is supposed to exist? Am I supposed to create an adsmorc file system or directory on the TSM server, on the TDP/RMAN server, or the client? Is anything ever going to get put there? Does it need to be its own mount point? Any help would be greatly appreciated. Thanks in advance Steve
