TDP for R3 - was TDP for Oracle and passwordaccess generate
We are having a heck of a time with passwordaccess generate and our TDP for R3 environment. Out environment dictates that passwords expire every X days. And, every X days, our TDP for R3 nodes get locked. Is this because we needed to run the aobpswd utility as mentioned in the TDP for Oracle thread? What is this utility? Did I miss this documentation in the TDP for R3 documentation? We are using Oracle on the R3 environment that is getting locked. TIA, John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com -Original Message- From: Stephen Mackereth [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 23, 2001 6:22 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Oracle and passwordaccess generate Hi Joel, The Documentation is correct. after you have registered the nodes in the TSM Server, You need to setup all the DSMO* variables in the current shell, and run the aobpswd utility. This will create a file with the encrypted password stored, this is how the TDPO connects into the TSM server. its all in the TDPO installation manual. Regards Stephen Mackereth Senior UNIX Consultant / Senior Storage Administrator (TSM) ITS Unix Systems Support Coles Myer Ltd. -Original Message- From: Joel Fuhrman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 24 January 2001 10:04 To: [EMAIL PROTECTED] Subject: TDP for Oracle and passwordaccess generate The TDP for Oracle Version 2.1 documentation says the PasswordAccess must be set to Prompted. Usually you want "PasswordAccess Generate" which is current setting for the Scheduler Service on this AIX host. Is "PasswordAccess Prompted" a true requirement or a just case of bad documentation. This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses.
Re: TDP for R3 - was TDP for Oracle and passwordaccess generate
We are having a heck of a time with passwordaccess generate and our TDP for R3 environment. Out environment dictates that passwords expire every X days. And, every X days, our TDP for R3 nodes get locked. Is this because we needed to run the aobpswd utility as mentioned in the TDP for Oracle thread? What is this utility? Did I miss this documentation in the TDP for R3 documentation? John - This is described in the Initializing the Password topic in the TDPO manual. The manual recommends running a discipline of running aobpswd before the password expires on the server, much as is the case with clients in general. You're kinda stuck, unless you can convince your site security people that this password, at least, should not have to change so often. Richard Sims, BU
Re: TDP for R3 - was TDP for Oracle and passwordaccess generate
If you're using TDP for R3 and one interface, it should work with passwordaccess generate. I've found that multiple interfaces to the same TSM server for the same node only gets *one* of the interfaces synced on the change. On TDP for R3 the utility is backint; run backint -f password -p path to backint parmfile and you will be prompted for the password for each *SM server listed in the parmfile with passwordacces prompt. The passwords are encrypted and stored in the backint.bki file. I'm about to set up a seperate node definition for our R3 instance with a non-expiring password (needed not only for this, but because we run an HACMP environment and the files belong to the SAP environment, not the particular node that happens to be running it at the time the backups happen). Tom Kauffman NIBCO, Inc -Original Message- From: Talafous, John G. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 6:59 AM To: [EMAIL PROTECTED] Subject: TDP for R3 - was TDP for Oracle and passwordaccess generate We are having a heck of a time with passwordaccess generate and our TDP for R3 environment. Out environment dictates that passwords expire every X days. And, every X days, our TDP for R3 nodes get locked. Is this because we needed to run the aobpswd utility as mentioned in the TDP for Oracle thread? What is this utility? Did I miss this documentation in the TDP for R3 documentation? We are using Oracle on the R3 environment that is getting locked. TIA, John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com -Original Message- From: Stephen Mackereth [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 23, 2001 6:22 PM To: [EMAIL PROTECTED] Subject: Re: TDP for Oracle and passwordaccess generate Hi Joel, The Documentation is correct. after you have registered the nodes in the TSM Server, You need to setup all the DSMO* variables in the current shell, and run the aobpswd utility. This will create a file with the encrypted password stored, this is how the TDPO connects into the TSM server. its all in the TDPO installation manual. Regards Stephen Mackereth Senior UNIX Consultant / Senior Storage Administrator (TSM) ITS Unix Systems Support Coles Myer Ltd. -Original Message- From: Joel Fuhrman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 24 January 2001 10:04 To: [EMAIL PROTECTED] Subject: TDP for Oracle and passwordaccess generate The TDP for Oracle Version 2.1 documentation says the PasswordAccess must be set to Prompted. Usually you want "PasswordAccess Generate" which is current setting for the Scheduler Service on this AIX host. Is "PasswordAccess Prompted" a true requirement or a just case of bad documentation. This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses.
TDP for Oracle and passwordaccess generate
The TDP for Oracle Version 2.1 documentation says the PasswordAccess must be set to Prompted. Usually you want "PasswordAccess Generate" which is current setting for the Scheduler Service on this AIX host. Is "PasswordAccess Prompted" a true requirement or a just case of bad documentation.
Re: TDP for Oracle and passwordaccess generate
Hi Joel, The Documentation is correct. after you have registered the nodes in the TSM Server, You need to setup all the DSMO* variables in the current shell, and run the aobpswd utility. This will create a file with the encrypted password stored, this is how the TDPO connects into the TSM server. its all in the TDPO installation manual. Regards Stephen Mackereth Senior UNIX Consultant / Senior Storage Administrator (TSM) ITS Unix Systems Support Coles Myer Ltd. -Original Message- From: Joel Fuhrman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 24 January 2001 10:04 To: [EMAIL PROTECTED] Subject: TDP for Oracle and passwordaccess generate The TDP for Oracle Version 2.1 documentation says the PasswordAccess must be set to Prompted. Usually you want "PasswordAccess Generate" which is current setting for the Scheduler Service on this AIX host. Is "PasswordAccess Prompted" a true requirement or a just case of bad documentation. This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses.
