1 Rookie
•
26 Posts
0
613
storing database application credentials in the lockbox operation
Hi Expert ..!
We are trying to configure the AIX DB in networker.
Can you pls help me to understand this error..
All the host entry are added in the server and client but still the same error : not able to create the RAW INSTACE
bingo.1
2.4K Posts
0
November 3rd, 2022 09:00
I am not a DB expert but I think it is not necessary right now.
It seems as if you want to add the Oracle client FloluxOraDev-bu.cap.local. This is possible in general. However, in the DB applications you are using the complete different hostname bus-nwnmc-01-bu.cap.local which is rejected. As a consequence the whole operation fails.
It looks as if NW cannot resolve the name bus-nwnmc-01-bu.cap.local . Make sure that you use the correct name and that it can properly be resolved to an IP address.
barry_beckers
393 Posts
0
November 7th, 2022 06:00
We never actually started using the NW client wizard, as it requires setting username and passwords whereas this is not required when using client end configuration.
We don't want to know nor need to know any DB related users and passwords, nor don't want to share a RDP session for example, to have a DB admin look over the shoulder when creating the backup definitions.
I assume with AIX DB, actually is meant DB2?
We only create client definitions and the commands and settings to use, but expect the DB2 client to have setup everything else on their end, so setting the encrypted password in the config files on the client end using nsrdaadmin and putting the encrypted password in the config file using param USER_PSWD.
We always thought this was more easier to manage instead of at times maybe needing to change things like password changes, causing backup failures unless the client wizard is used to change the password... We as backup team do not want to keep track of any passwords on client end.
So we have no DB backup whatsoever configured with the NW client wizard and won't be anytime soon going to use it...
To be able to make transactional log backups for DB2, would require the Db2 admins to setup a backup to be triggered from client end anyways, as one cannot schedule any DB2 transactional log backups from a backup product side, as it needs to be triggered from client end (which is the only NW module NMDA DB backup that requires this).
So that is that about even using the nw client wizard. Getting to the error, it seems that there is a separate NMC being used to manage the backup server, by looking at its name? Or what is that bus-nwnmc-01-bu.cap.local?
wrg to the error, does this work for other clients or when using the nmc running locally on the NW backup server instead of using a separate NMC?
https://www.dell.com/support/kbdoc/en-us/article/lkbprint?ArticleNumber=000189377 states an example of this occurring after a NW server NSRDR was performed, however it also caused the lockbox not being able to be used for backups either. So is the lockbox also filled with other entries and is it still working? If not, then it might require the lockbox to be recreated and entries added again... Too early to tell as there is not enough input of what is going on in your environment...