You should note the following about using a relational database:

• If you are using Embedded RDB as the relational database, there are no tools that access Embedded RDB directly. Do not attempt to access Embedded RDB directly.
• If your relational database is Oracle and you change your account password, you must also change the account and password of the Remote Installer Server service.
• If you set up the server core facility on a machine that has more than one NIC while you are using Embedded RDB as the relational database, choose one of the machine's IP addresses to use for JP1 communication, and then specify that IP address as the client environment variable PDCLTRCVADDR in the files listed below. Back up the HiRDB.ini file before you edit it. Note that if you do not specify an IP address as the client environment variable PDCLTRCVADDR, an IP address on a higher-priority network adapter will be used for JP1 communication.
  JP1/Software-Distribution-installation-directory\Setup_Input\ini\HiRDB.ini
  JP1/Software-Distribution-installation-directory\Setup_Input_HA\ini\HiRDB.ini
  
• If you install only the remote installation manager facility on a machine with more than one NIC while you are using Embedded RDB as the relational database, choose one of the machine's IP addresses to use for JP1 communication, and then specify that IP address as the client environment variable PDCLTRCVADDR in the file below. Back up the HiRDB.ini file before you edit it. Note that if you do not specify an IP address as the client environment variable PDCLTRCVADDR, an IP address on a higher-priority network adapter will be used for JP1 communication.
  JP1/Software-Distribution-installation-directory\NETMDBCLT\HiRDB.ini
  
• If you use the remote installation manager facility and the server core facility on different machines, and the machine running the server core facility has more than one NIC, and you are using Embedded RDB as the relational database, then configure the IP addresses to be used for JP1 communication by following these steps:
  
  1. Stop Remote Installation Manager.
  2. Stop the Remote Install Server service.
  3. Open the command prompt and change the current directory to the following directory.
     JP1/Software-Distribution-installation-directory\BIN
     
  4. Execute netmdb_stop.bat command that is stored in the directory JP1/Software-Distribution-installation-directory\BIN to stop the database.
  5. Use a text editor to open the pdsys file that is stored in the directory shown below. Back up the pdsys file before you edit it.
     JP1/Software-Distribution--installation-directory\NETMDB\conf
     
  6. Enter an IP address to be used for the JP1 communication in the following line:
     (xxx.xxx.xxx.xxx:IP address)
     Before:
     pdstart -t SDS -s sds01 -u unt1
     After:
     pdstart -t SDS -s sds01 -u unt1 -m xxx.xxx.xxx.xxx
     
  7. Save the pdsys file.
  8. Execute the netmdb_start.bat command that is stored in JP1/Software-Distribution- installation-directory\BIN to start the database.
  9. Start the Remote Install Server service.
• If a message indicating an error communicating with RDBMS is output to the server's Windows event log (MAIN.LOG or RDBSRV.LOG), an attempt may have been made to connect to a relational database server after the server had been started but before startup had completed. If the message is output even though you waited a while before trying to connect to the relational database server, collect maintenance data and contact the system administrator. For details about collecting maintenance data, see 6.7 Collecting maintenance data in the manual Administrator's Guide Volume 2.
• When a JP1/Software Distribution GUI operation or command is executed, a message or dialog box may be displayed indicating that a connection could not be made to the server or to the relational database server, or the GUI operation may be forcibly terminated. In this case, an attempt may have been made to connect to a relational database server after the server had been started but before startup had completed. If the error recurs even though you waited a while before executing GUI operations or commands, collect maintenance data and contact the system administrator. For details about collecting maintenance data, see 6.7 Collecting maintenance data in the manual Administrator's Guide Volume 2.
• Specify a directory on a local drive as the location of the database files and the backup files that are used by Asset Information Manager Subset and the managing server, and of the temporary files and result output files that are used during database maintenance.