ADSM-L

Why does TDP Oracle on Unix require Passwordaccess=prompt?

2003-05-01 15:56:19
Subject: Why does TDP Oracle on Unix require Passwordaccess=prompt?
From: Neil Rasmussen <rasmussn AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 1 May 2003 12:55:24 -0700
I just wanted to make clear why passwordaccess=prompt with Data Protection
for Oracle on Unix. Below is the knowledge for this explanation. However,
I also want to point out that in addition to the explanation below Oracle
specifications for a 3rd party vendor (that's DP for Oracle in this case)
cannot spawn a child process (that would be the TCA).


DCF Document ID: 1104553 - IBM Tivoli Storage Manager for Databases: TDP Oracle 
for Unix needs Passwordaccess=prompt

When using the TDP for Oracle on Unix, the passwordacess must be set to prompt.
This is different than Windows which uses passwordaccess generate.

The differences in how the operating systems work, makes this passwordaccess 
prompt necessary.

For the Unix operating system, theTSM passwords are saved in the TSM.PWD
file when passwordaccess generate is used. The dsmtca module for the TSM client 
is then utilized
to read the password from this encrypted file.

For the Oracle backup with the TDP, the dsmtca cannot be launched as this would 
be a
child process for the executable. The TDP is not an executable, so it is
not able to have a child process. Thus for Unix, there is no child process
capability for the dsmtca module to retrieve the password. Therefore, the
TDP Oracle for the Unix Operating Systems must use passwordaccess prompt.

For Windows, the password is stored in the registry and can be retrieved
directly without any dsmtca involvement.

<Prev in Thread] Current Thread [Next in Thread>
  • Why does TDP Oracle on Unix require Passwordaccess=prompt?, Neil Rasmussen <=