Upgrade from SDS 6.4 to SDS 8.01 VA to use existing remote DB2 DB Companion Document. Document version 1.0

Transcription

1 Upgrade from SDS 6.4 to SDS 8.01 VA to use existing remote DB2 DB Companion Document Document version 1.0

2 Document change history Changed by Doc Date Changes Version Ramamohan T. Reddy 1.0 3/28/2017 Initial version IBM Security Directory Suite Page 2

3 Contents 1. Introduction SDS Installation - Virtual Machine setup SDS Installation - Virtual Appliance setup SDS Installation - Required Fixes Remote SDS 6.4 instance verification Backup SDS Directory Server migration from SDS 6.4 to SDS VA Unconfigure SDS 6.4 to retain the DB2 instance and database: Configuration on SDS VA to connect to remote database Rollback to SDS IBM Security Directory Suite Page 3

4 1. Introduction This companion document provides details for the steps provided in the presentation OpenMic- ISDS801_upgradefromSDS64_existingdb-presentation-28Mar2017-v1.pdf. 2. SDS Installation - Virtual Machine setup Start with Create New Virtual Machine on your VMWare ESXi Select Custom configuration Click Next button: IBM Security Directory Suite Page 4

5 Select a name and location for the virtual machine click Next : Select a Host / Cluster for the virtual machine click Next : IBM Security Directory Suite Page 5

6 Select a resource pool click Next : Select storage for virtual machine files click Next : IBM Security Directory Suite Page 6

7 Select Virtual Machine Version to be 8 and then click Next : Select Linux as Guest Operation System and Other 2.6.x Linux (64-bit) as version click Next : IBM Security Directory Suite Page 7

8 Select number of CPUs then click Next : Select Memory size click Next : IBM Security Directory Suite Page 8

9 Create 3 Network Connections (NICs) choose either E1000 or VMXNET 3 as adapter click Next : Take default or customize SCSI Controller click Next : IBM Security Directory Suite Page 9

10 Select option Create a new virtual disk and click Next : Specify Disk size, for Provisioning and Location check with your VMware admin and choose accordingly then click Next : IBM Security Directory Suite Page 10

11 Select either defaults or customize per VMware admin suggestions then click Next : IBM Security Directory Suite Page 11

12 Review Settings Select Edit the virtual machine settings before click Continue : IBM Security Directory Suite Page 12

13 For CD/DVD select Connect at power on In this case the sds801-limited-edition.iso file is already uploaded to the datastore folder and its selected Click on Finish : Here use SDS (or latest) ISO file. E.g.: ISS- ISDS_ iso Select the newly created virtual machine power on the virtual machine Click on Console : In the console Select Language and enter yes to proceed: IBM Security Directory Suite Page 13

14 After successful installation the following will be displayed: IBM Security Directory Suite Page 14

15 Goto Virtual Machine Settings CD/DVD Unselect/Uncheck Connected and Connect at power on options Click Finish : Now switch back to Console and hit Enter key: IBM Security Directory Suite Page 15

16 3. SDS Installation - Virtual Appliance setup After reboot the appliance console presents unconfigured.appliance login: prompt Enter admin for both login and Password: When prompted hit Enter key: Review license terms in 2 and 3 and then enter 4 to proceed to license acceptance: Enter 1 to agree and then press Enter key: When FIPS configuration is displayed (if really required then press 1) Otherwise simply Select n and press Enter key IBM Security Directory Suite Page 16

17 For Appliance Password select 1 and press Enter key: Enter old/default password admin and then a new password two times: After successful Password change Proceed to next section: For Host Name Configuration Select 1 then press Enter key: Provide Full Host Name: IBM Security Directory Suite Page 17

18 After hostname update proceed to next section: Configure at least 1 interface for appliance (remember we have 3 NICs 2 admin and 1 application) Provide a Manual/Static IPv4 address and corresponding configuration as per your network: IBM Security Directory Suite Page 18

19 After IP address update proceed to next section: To provide DNS Server select 1 and then press Enter key: Enter DNS IP address and then press Enter key: After DNS update proceed to next section: IBM Security Directory Suite Page 19

20 Review and update Time Zone (option 3) and date (option 2) as well as time (option 1) according to your date/time/timezone after time configuration proceed to next section: Review the Summary and press 1 and then Enter: IBM Security Directory Suite Page 20

21 After successful configuration the following is displayed: Reboot the system: IBM Security Directory Suite Page 21

22 4. SDS Installation - Required Fixes As of March 28 th 2017, there are no required fixes on top of This section is for information purpose only. Connect to SDS 801 Virtual Appliance via Web LMI using browser and login as admin user: In LMI Web interface click on Manage and then on Fix Packs IBM Security Directory Suite Page 22

23 Click on Green + New button In the Add fix pack dialog box, click on Browse for fix pack IBM Security Directory Suite Page 23

24 Browse and select f-ISS-ISDS-IFnnnn.fixpack file then click on Save Configuration button After successful installation: 5. Remote SDS 6.4 instance verification On SDS 6.4 system verify the instance details: ==> idsilist -a Directory server instances: Instance 1: Name: ldapdb2 Version: 6.4 Location: /home/ldapdb2 Description: IBM Security Directory Server Instance V6.4 IP Addresses: All available Port: 389 Secure Port: 636 Admin Server Port: 3538 Admin Server Secure Port: 3539 Type: Directory Server IBM Security Directory Suite Page 24

25 On SDS 6.4 system verify the db2 instance and database details: ==> cd /home/ldapdb2/idsslapd-ldapdb2/etc ==> egrep -i '(dblocation dbname dbinstance dbuser)' ibmslapd.conf ibm-slapddbinstance: ldapdb2 ibm-slapddblocation: /home/ldapdb2 ibm-slapddbname: ldapdb2 ibm-slapddbuserid: ldapdb2 ibm-slapddbuserpw: {AES256}... ibm-slapddbinstance: ldapdb2 ibm-slapddbname: ldapclog ibm-slapddbuserid: ldapdb2 ibm-slapddbuserpw: {AES256} Backup SDS 6.4 Backup configuration and schema as root user - run migbkup tool - also copy custom schema files: ==> mkdir /home/ldapdb2/ldapsaveconf ==> chmod g+w /home/ldapdb2/ldapsaveconf ==> chown ldapdb2:idsldap /home/ldapdb2/ldapsaveconf ==> cd /opt/ibm/ldap/v6.4/sbin ###for AIX/Solaris ==> cd /opt/ibm/ldap/v6.4/sbin ###for Linux ==>./migbkup /home/ldapdb2/idsslapd-ldapdb2 /home/ldapdb2/ldapsaveconf Backing up schema and configuration files... Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.ibm.at. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.ibm.oc. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.system.at. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.system.oc. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.user.at. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.user.oc. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.modifiedschema. Copying: file /home/ldapdb2/idsslapd-ldapdb2/ logs/perftune_stat.log. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/ibmslapd.conf. Copying: file /home/ldapdb2/idsslapd-ldapdb2/ etc/perftune_input.conf. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/ibmslapdcfg.ksf. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/ibmslapddir.ksf. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.config.at. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.config.oc. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.ldapsyntaxes. Copying: file /home/ldapdb2/idsslapd-ldapdb2/etc/v3.matchingrules. ==> cp /home/ldapdb2/idsslapd-ldapdb2/etc/<customschemafiles> /home/ldapdb2/ldapsaveconf/etc ==> cd /home/ldapdb2 ==> tar -cvf ldapsaveconf.tar ldapsaveconf a ldapsaveconf IBM Security Directory Suite Page 25

26 a ldapsaveconf/etc a ldapsaveconf/etc/v3.config.at 198 blocks. a ldapsaveconf/etc/v3.config.oc 29 blocks. a ldapsaveconf/etc/v3.customschema1.conf 46 blocks. a ldapsaveconf/etc/v3.customschema2.conf 47 blocks. a ldapsaveconf/etc/v3.customschema3.conf 13 blocks. a ldapsaveconf/etc/v3.customschema4.conf 149 blocks. a ldapsaveconf/etc/v3.customschema5.conf 7 blocks. a ldapsaveconf/etc/v3.customschema6.conf 6 blocks. a ldapsaveconf/etc/v3.ibm.at 681 blocks. a ldapsaveconf/etc/v3.ibm.oc 122 blocks. a ldapsaveconf/etc/v3.ldapsyntaxes 7 blocks. a ldapsaveconf/etc/v3.matchingrules 7 blocks. a ldapsaveconf/etc/v3.modifiedschema 1 blocks. a ldapsaveconf/etc/v3.system.at 135 blocks. a ldapsaveconf/etc/v3.system.oc 21 blocks. a ldapsaveconf/etc/v3.user.at 230 blocks. a ldapsaveconf/etc/v3.user.oc 62 blocks. a ldapsaveconf/etc/db2info 1 blocks. a ldapsaveconf/etc/ibmslapd.conf 29 blocks. a ldapsaveconf/etc/ibmslapdcfg.ksf 1 blocks. a ldapsaveconf/etc/ibmslapddir.ksf 1 blocks. a ldapsaveconf/etc/perftune_input.conf 5 blocks. a ldapsaveconf/etc/perftune_stat.log 11 blocks. a ldapsaveconf/etc/platforminfo 1 blocks. Backup method 1 - idsdbback from V6.4 - Using root login: ==> mkdir /home/ldapdb2/ldapbackup1 ==> chmod g+w /home/ldapdb2/ldapbackup1 ==> chown ldapdb2:idsldap /home/ldapdb2/ldapbackup1 ==> ibmslapd -I ldapdb2 -k GLPSRV176I Terminated directory server instance 'ldapdb2' normally. ==> idsdbback -I ldapdb2 -k /home/ldapdb2/ldapbackup1 -ndb2 GLPWRP123I The program '/opt/ibm/ldap/v6.4/sbin/64/dbback' is used with the following arguments '-I ldapdb2 -k /home/ldapdb2/ldapbackup1 -n'. You have chosen to perform the following actions: GLPDBB029I The database and configuration files for directory server instance 'ldapdb2' will be backed up offline to '/home/ldapdb2/ldapbackup1'. GLPDBB008I Backing up directory server instance GLPDBB015I Backing up the configuration file for the directory server instance GLPDBB016I Backed up the configuration file for the directory server instance GLPDBB018I Backing up the key stash files for the directory server instance GLPDBB019I Backed up the key stash files for the directory server instance IBM Security Directory Suite Page 26

27 GLPDBB021I Backing up the schema files for the directory server instance GLPDBB022I Backed up the schema files for the directory server instance GLPDBB033I Backing up the database properties file 'ldapdb.properties' for the directory server instance GLPDBB034I Backed up the database properties file for the directory server instance GLPDBB036I Backing up the command files 'ibmslapdservice.cmd' and 'ibmdiradmservice.cmd' (Windows) or 'idsrun' (Unix) for the directory server instance GLPDBB037I Backed up the command files for the directory server instance GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL098I Backing up database ldapdb. GLPCTL099I Backed up database ldapdb. GLPDBB026I Saving backup information to a file. GLPDBB027I Saved backup information to a file. GLPDBB009I Backed up directory server instance Backup method 2 - db2ldif - Using root login: ==> mkdir /home/ldapdb2/ldapbackup2 ==> chmod g+w /home/ldapdb2/ldapbackup2 ==> chown ldapdb2:idsldap /home/ldapdb2/ldapbackup2 ==> idsdb2ldif -I ldapdb2 -o /home/ldapdb2/ldapbackup2/ldapdata.ldif GLPCTL113I Largest core file size creation limit for the process (in bytes): '-1'(Soft limit) and '-1'(Hard limit). GLPCTL119I Maximum Data Segment(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is GLPCTL119I Maximum File Size(512 bytes block) soft ulimit for the process is -1 and the prescribed minimum is GLPCTL122I Maximum Open Files soft ulimit for the process is 8000 and the prescribed minimum is 500. GLPCTL119I Maximum Physical Memory(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is GLPCTL121I Maximum Stack Size(Kbytes) soft ulimit for the process was and it is modified to the prescribed minimum GLPCTL119I Maximum Virtual Memory(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is GLPSRV221I Replication of security attributes feature is disabled. GLPSRV200I Initializing primary database and its connections. GLPD2L011I 100 entries have been successfully exported from the directory. GLPD2L011I 200 entries have been successfully exported from the directory. GLPD2L011I 300 entries have been successfully exported from the directory IBM Security Directory Suite Page 27

28 GLPD2L011I entries have been successfully exported from the directory. GLPD2L011I entries have been successfully exported from the directory. ==> cd /home/ldapdb2/idsslapd-ldapdb2 ==> tar -cvf /home/ldapdb2/ldapbackup2/ldapdb2etc.tar etc a etc a etc/v3.config.at 198 blocks. a etc/v3.config.oc 29 blocks. a etc/v3.customschema1.conf 46 blocks. a etc/v3.customschema2.conf 47 blocks. a etc/v3.customschema3.conf 13 blocks. a etc/v3.customschema4.conf 149 blocks. a etc/v3.customschema5.conf 7 blocks. a etc/v3.customschema6.conf 6 blocks. a etc/v3.ibm.at 681 blocks. a etc/v3.ibm.oc 122 blocks. a etc/v3.ldapsyntaxes 7 blocks. a etc/v3.matchingrules 7 blocks. a etc/v3.modifiedschema 1 blocks. a etc/v3.system.at 135 blocks. a etc/v3.system.oc 21 blocks. a etc/v3.user.at 230 blocks. a etc/v3.user.oc 62 blocks. a etc/ibmslapd.conf 29 blocks. a etc/ibmslapd.conf.save 29 blocks. a etc/ibmslapdcfg.ksf 1 blocks. a etc/ibmslapddir.ksf 1 blocks. a etc/idsrun 77 blocks. a etc/ldapdb.properties 1 blocks. a etc/perftune_input.conf 5 blocks. a etc/tdsdelref.conf 3 blocks. IBM Security Directory Suite Page 28

29 7. Directory Server migration from SDS 6.4 to SDS VA Using a browser login to VA Web LMI as admin user Navigate to Custom File Management IBM Security Directory Suite Page 29

30 Select All Files tab -> then select CustomIn -> click on Upload In the resulting File Upload dialog click on Browse : Navigate and select ldapsaveconf.tar file and then click on Save Configuration : Uploaded file will be displayed in CustomIn folder along with System Notification that the file was uploaded successfully: IBM Security Directory Suite Page 30

31 Alternatively, login to SDS VA system as admin, and use idsgetfile tool to download the ldapsaveconf.tar directly onto SDS VA from remote SDS 6.4 AIX/Solaris/Linux server: sds801va1 > sds client_tools idsgetfile USAGE: idsgetfile -h <host> -u <user> -p <port>(optional) -f <absolute_path_to_file> sds801va1 > sds client_tools idsgetfile -h sdsp8aix72 -u root -f /home/ldapdb2/ldapsaveconf.tar password: ldapsaveconf.tar 100% 920KB 920.0KB/s 00:00 Successfully received the file. File can be viewed under CustomIn folder in LMI. Run idsimigr utility: sds801va1 > sds migration_tools idsimigr -u <schema_conf_archive_file_from_6.4> sds801va1 > sds migration_tools idsimigr -u ldapsaveconf.tar :03:00:19 - [INFO] md5sum for the /userdata/directory/customin/ldapsaveconf.tar is shown below: 87df1ec82956fd42e988de74fcb6b70e /userdata/directory/customin/ldapsaveconf.tar :03:00:19 - [INFO] BACKUP_DIR_ETC=/userdata/directory/CustomIn/ldapsaveconf/etc :03:00:19 - [INFO] BACKUP_ROOT_DIR=/userdata/directory/CustomIn/ldapsaveconf :03:00:19 - [INFO] Unarchiving /userdata/directory/customin/ldapsaveconf.tar :03:00:19 - [INFO] md5sum for the /userdata/directory/customin/ldapsaveconf.tar is shown below: 87df1ec82956fd42e988de74fcb6b70e /userdata/directory/customin/ldapsaveconf.tar :03:00:19 - [INFO] Successfully unarchived /userdata/directory/customin/ldapsaveconf.tar :03:00:19 - [INFO] Taking sdsinst1 backup :03:00:30 - [INFO] Completed taking sdsinst1 backup :03:00:30 - [INFO] Stopping ibmslapd service for instance sdsinst1 GLPSRV124I The directory server instance 'sdsinst1' is already stopped :03:00:31 - [INFO] Stopped ibmslapd service for instance sdsinst :03:00:31 - [INFO] Stopping ibmdiradm service for instance sdsinst1 GLPADM034I Stopped Admin server instance: :03:00:31 - [INFO] Stopped ibmdiradm service for instance sdsinst :03:01:07 - [INFO] Dropped instance sdsinst :03:01:07 - [INFO] Started idsimigr execution :03:02:02 - [INFO] Completed idsimigr execution :03:02:02 - [INFO] Updating plugin extensions :03:02:02 - [INFO] Updated plugin extensions :03:02:02 - [INFO] Removing /userdata/directory/customin/ldapsaveconf IBM Security Directory Suite Page 31

32 :03:02:02 - [INFO] Removed /userdata/directory/customin/ldapsaveconf :03:02:02 - [INFO] Removing sdsinst1 backup :03:02:02 - [INFO] Removed sdsinst1 backup :03:02:02 - [INFO] Task completed. " Configure a new, blank local database using idscfgdb tool: (this step is required): sds801va1 > sds server_tools idscfgdb -I sdsinst1 -a sdsinst1 -w sdsinst1 -t sdsinst1 -l /home/sdsinst1 -n GLPCDB037W The specified directory, '/home/sdsinst1', does not have read, write, and execute permissions for the primary group 'idsldap' of directory server instance owner GLPWRP123I The program '/opt/ibm/ldap/v8.0.1/sbin/64/idscfgdb' is used with the following arguments '-I sdsinst1 -a sdsinst1 -w ***** -t sdsinst1 -l /home/sdsinst1 -n'. You have chosen to perform the following actions: GLPCDB023I Database 'sdsinst1' will be configured. GLPCDB024I Database 'sdsinst1' will be created at '/home/sdsinst1' GLPCDB035I Adding database 'sdsinst1' to directory server instance: GLPCTL017I Cataloging database instance node: GLPCTL018I Cataloged database instance node: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL026I Creating database: GLPCTL027I Created database: GLPCTL034I Updating the database: 'sdsinst1' GLPCTL035I Updated the database: 'sdsinst1' GLPCTL020I Updating the database manager: GLPCTL021I Updated the database manager: GLPCTL023I Enabling multi-page file allocation: 'sdsinst1' GLPCTL024I Enabled multi-page file allocation: 'sdsinst1' GLPCDB005I Configuring database 'sdsinst1' for directory server instance: GLPCDB006I Configured database 'sdsinst1' for directory server instance: GLPCTL037I Adding local loopback to database: GLPCTL038I Added local loopback to database: GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCDB003I Added database 'sdsinst1' to directory server instance: IBM Security Directory Suite Page 32

33 8. Unconfigure SDS 6.4 to retain the DB2 instance and database: Login to SDS 6.4 system as root user - stop Directory Server and Admin Server processes: ==> ps -aef egrep "PID ibmslapd ibmdiradm" UID PID PPID C STIME TTY TIME CMD ldapdb :42:24 pts/0 0:00 /opt/ibm/ldap/v6.4/sbin/64/ibmslapd -I ldapdb2 -n ldapdb :42:45 pts/0 0:00 /opt/ibm/ldap/v6.4/sbin/64/ibmdiradm -I ldapdb2 ==> ibmdiradm -I ldapdb2 k GLPADM034I Stopped Admin server instance: ==> ibmslapd -I ldapdb2 k GLPSRV176I Terminated directory server instance 'ldapdb2' normally. Unconfigure the database (without deleting) from Directory server configuration using idsucfgdb tool (do not use -r flag): ==> idsucfgdb -I ldapdb2 -n GLPWRP123I The program '/opt/ibm/ldap/v6.4/sbin/64/idsucfgdb' is used with the following arguments '-I ldapdb2 -n'. You have chosen to perform the following actions: GLPUDB017I The database for directory server instance 'ldapdb2' will be unconfigured. GLPUDB018I Database will be left on your system. GLPUDB002I Removing the DB2 database from directory server instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL040I Removing local loopback from database: 'ldapdb2b'. GLPCTL041I Removed local loopback from database: 'ldapdb2b'. GLPUDB005I Unconfiguring database 'ldapdb' for directory server instance: GLPUDB006I Unconfigured database 'ldapdb' for directory server instance: GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: GLPUDB003I Removed the DB2 database from directory server instance: Drop/delete the SDS instance without deleting the DB2 instance using idsidrop tool (do not use -r flag): ==> idsidrop -I ldapdb2 -n GLPWRP123I The program '/opt/ibm/ldap/v6.4/sbin/64/idsidrop' is used with the following arguments '-I ldapdb2 -n'. You have chosen to perform the following actions: IBM Security Directory Suite Page 33

34 GLPIDP043I The directory server instance 'ldapdb2' will be deleted. Note: The configuration file, the schema files, the log files, and key stash files associated with this directory server instance will be deleted. All information regarding how the directory server instance was configured and how the directory data was encrypted will be lost. GLPIDP071I The database instance configured for directory server instance 'ldapdb2' will be unconfigured. The database instance and the databases contained in the database instance will be preserved. GLPIDP002I Deleting directory server instance: GLPCTL077I Stopping admin server for directory server instance: GLPCTL078I Stopped admin server for directory server instance: GLPIDP072I Deleting the runtime executable for directory server instance: GLPIDP073I Deleted the runtime executable for directory server instance: GLPIDP035I Removing entry from /etc/inittab for the admin server for directory server instance GLPIDP036I Removed entry from /etc/inittab for the admin server for directory server instance GLPIDP057I Removing instance information from the.profile file for directory server instance: GLPIDP058I Removed instance information from the.profile file for directory server instance: GLPIDP020I Deleting profile scripts for directory server instance: GLPIDP021I Deleted profile scripts for directory server instance: GLPIDP011I Deleting log files for directory server instance: GLPIDP012I Deleted log files for directory server instance: GLPIDP008I Deleting schema files for directory server instance: GLPIDP009I Deleted schema files for directory server instance: GLPIDP014I Deleting configuration file for directory server instance: GLPIDP015I Deleted configuration file for directory server instance: GLPIDP017I Deleting key stash files for directory server instance: GLPIDP018I Deleted key stash files for directory server instance: GLPIDP077I Deleting the ldapdb.properties file for directory server instance: GLPIDP075I Deleted the ldapdb.properties file for directory server instance: IBM Security Directory Suite Page 34

35 GLPIDP023I Deleting directories for directory server instance: GLPIDP024I Deleted directories for directory server instance: GLPIDP039I Unregistering directory server instance: GLPIDP040I Unregistered directory server instance: GLPIDP003I Deleted directory server instance: Identify the DB2 instance name and the db name: From grep command before: ==> egrep -i '(dblocation dbname dbinstance dbuser)' ibmslapd.conf ibm-slapddbinstance: ldapdb2 ibm-slapddblocation: /home/ldapdb2 ibm-slapddbname: ldapdb ibm-slapddbuserid: ldapdb2 ibm-slapddbuserpw: {AES256}... ==> /usr/local/bin/db2ls Install Path Level Fix Pack Install Date Installer UID /opt/ibm/db2/v Sun Jan 15 07:29: CST 0 ==> /opt/ibm/db2/v10.5/instance/db2ilist ldapdb2 ==> su - ldapdb2 -c "db2 list db directory" System Database Directory Number of entries in the directory = 1 Database 1 entry: Database alias = LDAPDB Database name = LDAPDB Local database directory = /home/ldapdb2 Database release level = Comment = Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = Alternate server port number = Identify the DB2 service port from /etc/services file & also from db2 dbm config (in this case its 3708): ==> su - ldapdb2 $ db2set -g -all ### DB2COMM should be set to TCPIP [i] DB2_SELECTIVITY=YES [i] DB2COMM=TCPIP [g] DB2SYSTEM=sdsp8aix72.rtp.raleigh.ibm.com IBM Security Directory Suite Page 35

36 $ grep -i ldapdb2svcids /etc/services ldapdb2svcids 3708/tcp ### This is DB2 TCPIP Service port. ldapdb2svcidsi 3737/tcp. $ db2 get dbm cfg grep -i SVCENAME ### SVCENAME confirms the port TCP/IP Service name (SVCENAME) = ldapdb2svcids SSL service name (SSL_SVCENAME) = $ db2start 03/26/ :31: SQL1063N DB2START processing was successful. SQL1063N DB2START processing was successful. $ netstat -an grep 3708 tcp4 0 0 *.3708 *.* LISTEN ### indicates that DB2 service port is listening. 9. Configuration on SDS VA to connect to remote database Configure SDS VA directory instance to connect with remote DB2 database using idscfgdb: sds801va1> sds server_tools idscfgdb -I sdsinst1 -a sdsinst1 -t ldapdb -w sdsinst1 -Y -S l /home/sdsinst1 -P sdsp8aix72 -u ldapdb2 -p passwd -n GLPCDB037W The specified directory, '/home/sdsinst1', does not have read, write, and execute permissions for the primary group 'idsldap' of directory server instance owner GLPWRP123I The program '/opt/ibm/ldap/v8.0.1/sbin/64/idscfgdb' is used with the following arguments '-I sdsinst1 -a sdsinst1 -t ldapdb -w ***** -Y -S l /home/sdsinst1 -P sdsp8aix72 -u ldapdb2 -p ***** -n'. You have chosen to perform the following actions: GLPCDB023I Database 'ldapdb' will be configured. GLPCDB035I Adding database 'ldapdb' to directory server instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL020I Updating the database manager: GLPCTL021I Updated the database manager: GLPCDB005I Configuring database 'ldapdb' for directory server instance: GLPCDB006I Configured database 'ldapdb' for directory server instance: GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: IBM Security Directory Suite Page 36

37 GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCDB003I Added database 'ldapdb' to directory server instance: Start ibmslapd in configuration only mode and re-configure SSL settings: sds801va1 > sds server_tools ibmslapd -I sdsinst1 -a GLPSRV034I Server starting in configuration only mode. from libevent.so. GLPSRV155I The DIGEST-MD5 SASL Bind mechanism is enabled in the configuration file. GLPCOM021I The preoperation plugin is successfully loaded from libdigest.so. from libevent.so. from libtranext.so. GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so. from libpsearch.so. GLPCOM025I The audit plugin is successfully loaded from libldapaudit.so. from libevent.so. GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so. from libpsearch.so. GLPCOM022I The database plugin is successfully loaded from libbackconfig.so. GLPSRV015I Server configured to use 636 as the secure port. from libloga.so. from libidsfget.so. GLPSRV232I Pass-through authentication is disabled. GLPSRV234I Pass-through support for compare operations is disabled. GLPCOM003I Non-SSL port initialized to 389. GLPCOM004I SSL port initialized to 636. GLPCOM039I Suite B mode is disabled. GLPSSL039I Secure communication using the SSLV3 protocol is enabled. GLPSSL039I Secure communication using the TLS10 protocol is enabled. GLPSSL039I Secure communication using the TLS11 protocol is enabled. GLPSSL039I Secure communication using the TLS12 protocol is enabled. IBM Security Directory Suite Page 37

38 T00:45: :00 T GSK_STRICTCHECK_CBCPADBYTES is enabled T00:45: :00 T GSK_STRICTCHECK_CBCPADBYTES_SSL is enabled T00:45: :00 T GSK_VACCINATE is disabled T00:45: :00 T GSK_ENFORCE_TDEA_RESTRICTION is enabled GLPSSL003E Open of SSL key database file GSK_KEYRING_OPEN_ERROR failed. GLPSRV114E Server failed to start normally with SSL; starting in configuration only mode without SSL. GLPCOM003I Non-SSL port initialized to 389. GLPSRV009I server started. Launch Web Admin Tool in Browser by connecting to URL such as You will find the IP address of SDS VA is already configured as an LDAP server - select the same and provide cn=root credential to login: IBM Security Directory Suite Page 38

39 Expand Server administration -> click on Manage security properties -> click on Key database -> Fill the fields as below: Key database path and file name: /userdata/directory/certificates/serverc.kdb Key password: server Confirm password: server Key label: server_cert Then click on OK. Alternatively use the command line method : sds801va1. > sds client_tools idsldapmodify -h sds801va1 -p 389 -D cn=root -w secret cn=ssl, cn=configuration ibmslapdsslkeydatabase=/userdata/directory/certificates/serverc.kdb ibm-slapdsslkeydatabasepw=server ibm-slapdsslcertificate=server_cert <enter> Operation 0 modifying entry cn=ssl, cn=configuration <CTRL+D> Restart Directory Server (ibmslapd) and also start Admin Server (ibmdiradm): sds801va1 > sds server_tools ibmslapd -k GLPSRV176I Terminated directory server instance 'sdsinst1' normally. sds801va1 > sds server_tools ibmdiradm GLPADM056I Admin server starting. IBM Security Directory Suite Page 39

40 GLPCOM025I The audit plugin is successfully loaded from libldapaudit.so. GLPCOM022I The database plugin is successfully loaded from libbackconfig.so. GLPADM060I The admin server backup and restore server configuration entry is not enabled. GLPSRV015I Server configured to use 3539 as the secure port. from libloga.so. GLPCOM003I Non-SSL port initialized to GLPCOM004I SSL port initialized to sds801va1 > sds server_tools ibmslapd -n GLPSRV041I Server starting. GLPCTL113I Largest core file size creation limit for the process (in bytes): '-1'(Soft limit) and '-1'(Hard limit). GLPCTL119I Maximum Data Segment(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is GLPCTL119I Maximum File Size(512 bytes block) soft ulimit for the process is -1 and the prescribed minimum is GLPCTL122I Maximum Open Files soft ulimit for the process is 1024 and the prescribed minimum is 500. GLPCTL119I Maximum Stack Size(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is GLPCTL119I Maximum Virtual Memory(Kbytes) soft ulimit for the process is -1 and the prescribed minimum is from libevent.so. from libtranext.so. from libldaprepl.so. GLPSRV155I The DIGEST-MD5 SASL Bind mechanism is enabled in the configuration file. GLPCOM021I The preoperation plugin is successfully loaded from libdigest.so. from libevent.so. from libtranext.so. GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so. from libpsearch.so. GLPCOM025I The audit plugin is successfully loaded from libldapaudit.so. from libevent.so. GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so. IBM Security Directory Suite Page 40

41 from libpsearch.so. GLPCOM022I The database plugin is successfully loaded from libbackconfig.so. from libevent.so. from libtranext.so. GLPCOM023I The postoperation plugin is successfully loaded from libpsearch.so. from libpsearch.so. GLPCOM022I The database plugin is successfully loaded from libbackrdbm.so. GLPCOM010I Replication plugin is successfully loaded from libldaprepl.so. GLPSRV189I Virtual list view support is enabled. GLPCOM021I The preoperation plugin is successfully loaded from libpta.so. GLPSRV194I The Record Deleted Entries feature is disabled. Deleted entries are immediately removed from the database. GLPSRV207I Group conflict resolution during replication is disabled. GLPSRV221I Replication of security attributes feature is disabled. GLPSRV247I Initializing primary REMOTE database 'ldapdb' and its connections. VAUUID check on the remote database passed. GLPRDB126I The directory server will not use DB2 selectivity. GLPSRV015I Server configured to use 636 as the secure port. from libloga.so. from libidsfget.so. GLPSRV232I Pass-through authentication is disabled. GLPSRV234I Pass-through support for compare operations is disabled. GLPCOM003I Non-SSL port initialized to 389. GLPCOM004I SSL port initialized to T01:23: :00 VAUUID check on the remote database passed. GLPRPL137I Restricted Access to the replication topology is set to false. GLPRDB091W Attribute ibm-replicaserverid is not indexed but is used in searches 10 times. GLPCOM039I Suite B mode is disabled. GLPSSL039I Secure communication using the SSLV3 protocol is enabled. GLPSSL039I Secure communication using the TLS10 protocol is enabled. GLPSSL039I Secure communication using the TLS11 protocol is enabled. IBM Security Directory Suite Page 41

42 GLPSSL039I Secure communication using the TLS12 protocol is enabled T01:23: :00 T GSK_STRICTCHECK_CBCPADBYTES is enabled T01:23: :00 T GSK_STRICTCHECK_CBCPADBYTES_SSL is enabled T01:23: :00 T GSK_VACCINATE is disabled T01:23: :00 T GSK_ENFORCE_TDEA_RESTRICTION is enabled GLPSRV009I server started. Verify the ldap server functionality: sds801va1 > tools ps egrep "ibmslapd ibmdiradm" grep -v grep 6541 root 1140m S /opt/ibm/ldap/v8.0.1/sbin/64/ibmdiradm -I sdsinst sdsinst1 1987m S /opt/ibm/ldap/v8.0.1/sbin/64/ibmslapd -n -I sdsinst1 -t sds801va1 > sds client_tools idsldapsearch -h sds801va1 -p 389 -D cn=root -w secret -s base -b dc=com objectclass=* dc=com dc=com objectclass=top objectclass=domain To unconfigure SDS VA directory instance remote DB2 database using idsucfgdb: sds801va1> sds server_tools idsucfgdb -I sdsinst1 -Y -n GLPWRP123I The program '/opt/ibm/ldap/v8.0.1/sbin/64/idsucfgdb' is used with the following arguments '-I sdsinst1 -Y -n'. You have chosen to perform the following actions: GLPUDB017I The database for directory server instance 'sdsinst1' will be unconfigured. GLPUDB018I Database will be left on your system. GLPUDB002I Removing the DB2 database from directory server instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPUDB005I Unconfiguring database 'ldapdb' for directory server instance: GLPUDB006I Unconfigured database 'ldapdb' for directory server instance: GLPCTL014I Uncataloging database instance node: GLPCTL015I Uncataloged database instance node: GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: GLPUDB003I Removed the DB2 database from directory server instance: IBM Security Directory Suite Page 42

43 To reconfigure (unconfigure/configure) SDS VA directory local/embedded DB2 database: sds801va1> sds server_tools idsucfgdb -r -n GLPWRP123I The program '/opt/ibm/ldap/v8.0.1/sbin/64/idsucfgdb' is used with the following arguments '-r -n -I sdsinst1'. You have chosen to perform the following actions: GLPUDB017I The database for directory server instance 'sdsinst1' will be unconfigured. GLPUDB019I Database will be completely removed. GLPUDB002I Removing the DB2 database from directory server instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL040I Removing local loopback from database: 'ldapdb2b'. GLPCTL041I Removed local loopback from database: 'ldapdb2b'. GLPUDB005I Unconfiguring database 'sdsinst1' for directory server instance: GLPUDB006I Unconfigured database 'sdsinst1' for directory server instance: GLPCTL031I Removing database: GLPCTL032I Removed database: GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: GLPUDB003I Removed the DB2 database from directory server instance: sds801va1> sds server_tools idscfgdb -I sdsinst1 -a sdsinst1 -w sdsinst1 -t sdsinst1 -l /home/sdsinst1 -n GLPWRP123I The program '/opt/ibm/ldap/v8.0.1/sbin/64/idscfgdb' is used with the following arguments '-I sdsinst1 -a sdsinst1 -w ***** -t sdsinst1 -l /home/sdsinst1 -n'. You have chosen to perform the following actions: GLPCDB023I Database 'sdsinst1' will be configured. GLPCDB024I Database 'sdsinst1' will be created at '/home/sdsinst1' GLPCDB035I Adding database 'sdsinst1' to directory server instance: GLPCTL017I Cataloging database instance node: GLPCTL018I Cataloged database instance node: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL026I Creating database: GLPCTL027I Created database: GLPCTL034I Updating the database: 'sdsinst1' IBM Security Directory Suite Page 43

44 GLPCTL035I Updated the database: 'sdsinst1' GLPCTL020I Updating the database manager: GLPCTL021I Updated the database manager: GLPCTL023I Enabling multi-page file allocation: 'sdsinst1' GLPCTL024I Enabled multi-page file allocation: 'sdsinst1' GLPCDB005I Configuring database 'sdsinst1' for directory server instance: GLPCDB006I Configured database 'sdsinst1' for directory server instance: GLPCTL037I Adding local loopback to database: GLPCTL038I Added local loopback to database: GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCDB003I Added database 'sdsinst1' to directory server instance: 10. Rollback to SDS 6.4 To unconfigure SDS VA directory instance remote DB2 database using idsucfgdb: sds801va1> sds server_tools idsucfgdb -I sdsinst1 -Y -n GLPWRP123I The program '/opt/ibm/ldap/v8.0.1/sbin/64/idsucfgdb' is used with the following arguments '-I sdsinst1 -Y -n'. You have chosen to perform the following actions: GLPUDB017I The database for directory server instance 'sdsinst1' will be unconfigured. GLPUDB018I Database will be left on your system. GLPUDB002I Removing the DB2 database from directory server instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPUDB005I Unconfiguring database 'ldapdb' for directory server instance: GLPUDB006I Unconfigured database 'ldapdb' for directory server instance: GLPCTL014I Uncataloging database instance node: GLPCTL015I Uncataloged database instance node: GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: IBM Security Directory Suite Page 44

45 GLPUDB003I Removed the DB2 database from directory server instance: On SDS 6.4 system - Verify SDS 6.4 instance: ==> idsilist -a Directory server instance(s): ### none returned. On SDS 6.4 system - If the SDS 6.4 instance exists, then drop it completely: ==> idsidrop -I ldapdb2 -r -n ### not applicable as none returned with idsilist. On SDS 6.4 system - Verify if the DB instance exists from the output of db2ilist: ==> /opt/ibm/db2/v10.5/instance/db2ilist ldapdb2 On SDS 6.4 system - If the DB instance exists drop the same: ==> su - ldapdb2 -c db2stop 03/27/ :06: SQL1064N DB2STOP processing was successful. SQL1064N DB2STOP processing was successful. ==> /opt/ibm/db2/v10.5/instance/db2idrop ldapdb2 DBI1446I The db2idrop command is running. DB2 installation is being initialized. Total number of tasks to be performed: 2 Total estimated time for all tasks to be performed: 305 second(s) Task #1 start Description: Initializing instance list Estimated time 5 second(s) Task #1 end Task #2 start Description: Configuring DB2 instances Estimated time 300 second(s) Task #2 end The execution completed successfully. For more information see the DB2 installation log at "/tmp/db2idrop.log ". DBI1070I Program db2idrop completed successfully. On SDS 6.4 system - Further clean up: ==> cd /home/ldapdb2 ==> rm -rf idsslapd-ldapdb2 ==> rm -rf sqllib* 8.log ==> rm -rf sqllib* *.log ==> rm -rf ldapdb2 ldap32kcont_ldapdb IBM Security Directory Suite Page 45

46 Create 6.4 instance and associated db2 instance (same settings as before): ==> /opt/ibm/ldap/v6.4/sbin/idsicrt -I ldapdb2 -e encrypt_seed -g encrypt_salt -t ldapdb2 -l /home/ldapdb2 -n GLPWRP123I The program '/opt/ibm/ldap/v6.4/sbin/64/idsicrt' is used with the following arguments 'idsicrt -I ldapdb2 -e ***** -g ***** -t ldapdb2 -l /home/ldapdb2 -n'. You have chosen to perform the following actions: GLPICR020I A new directory server instance 'ldapdb2' will be created. GLPICR057I The directory server instance will be created at: '/home/ldapdb2'. GLPICR013I The directory server instance's port will be set to '389'. GLPICR014I The directory server instance's secure port will be set to '636'. GLPICR015I The directory instance's administration server port will be set to '3538'. GLPICR016I The directory instance's administration server secure port will be set to '3539'. GLPICR019I The description will be set to: 'IBM Security Directory Server Instance V6.4'. GLPICR021I Database instance 'ldapdb2' will be configured. GLPICR028I Creating directory server instance: GLPICR025I Registering directory server instance: GLPICR026I Registered directory server instance: : GLPICR049I Creating directories for directory server instance: GLPICR050I Created directories for directory server instance: GLPICR043I Creating key stash files for directory server instance: GLPICR044I Created key stash files for directory server instance: GLPICR040I Creating configuration file for directory server instance: GLPICR041I Created configuration file for directory server instance: GLPICR034I Creating schema files for directory server instance: GLPICR035I Created schema files for directory server instance: GLPICR037I Creating log files for directory server instance: GLPICR038I Created log files for directory server instance: GLPICR088I Configuring log files for directory server instance: GLPICR089I Configured log files for directory server instance: IBM Security Directory Suite Page 46

47 GLPICR085I Configuring schema files for directory server instance: GLPICR086I Configured schema files for directory server instance: GLPICR073I Configuring ports and IP addresses for directory server instance: GLPICR074I Configured ports and IP addresses for directory server instance: GLPICR077I Configuring key stash files for directory server instance: GLPICR078I Configured key stash files for directory server instance: GLPICR046I Creating profile scripts for directory server instance: GLPICR047I Created profile scripts for directory server instance: GLPICR103I Adding instance information to the.profile file for directory server instance: GLPICR104I Added instance information to the.profile file for directory server instance: GLPICR069I Adding entry to /etc/inittab for the administration server for directory instance: GLPICR070I Added entry to /etc/inittab for the administration server for directory instance: GLPICR118I Creating runtime executable for directory server instance: GLPICR119I Created runtime executable for directory server instance: GLPCTL074I Starting admin server for directory server instance: GLPCTL075I Started admin server for directory server instance: GLPICR029I Created directory server instance: : GLPICR031I Adding database instance 'ldapdb2' to directory server instance: GLPCTL002I Creating database instance: GLPCTL003I Created database instance: GLPICR133I Setting the DB2 registry for database instance 'ldapdb2' to allow DB2 SELECTIVITY. GLPICR134I The DB2 registry for database instance 'ldapdb2' has been set to allow DB2 SELECTIVITY. GLPCTL017I Cataloging database instance node: GLPCTL018I Cataloged database instance node: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL049I Adding TCP/IP services to database instance: GLPCTL050I Added TCP/IP services to database instance: GLPICR081I Configuring database instance 'ldapdb2' for directory server instance: IBM Security Directory Suite Page 47

48 GLPICR082I Configured database instance 'ldapdb2' for directory server instance: GLPICR052I Creating DB2 instance link for directory server instance: GLPICR053I Created DB2 instance link for directory server instance: GLPICR032I Added database instance 'ldapdb2' to directory server instance: Configure an associated database (same settings as before so that we can do a restore): ==> /opt/ibm/ldap/v6.4/sbin/idscfgdb -I ldapdb2 -a ldapdb2 -w passwd -t ldapdb -l /home/ldapdb2 -n GLPWRP123I The program '/opt/ibm/ldap/v6.4/sbin/64/idscfgdb' is used with the following arguments '-I ldapdb2 -a ldapdb2 -w ***** - t ldapdb -l /home/ldapdb2 -n'. You have chosen to perform the following actions: GLPCDB023I Database 'ldapdb' will be configured. GLPCDB024I Database 'ldapdb' will be created at '/home/ldapdb2' GLPCDB035I Adding database 'ldapdb' to directory server instance: GLPCTL017I Cataloging database instance node: GLPCTL018I Cataloged database instance node: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL026I Creating database: 'ldapdb'. GLPCTL027I Created database: 'ldapdb'. GLPCTL034I Updating the database: 'ldapdb' GLPCTL035I Updated the database: 'ldapdb' GLPCTL020I Updating the database manager: GLPCTL021I Updated the database manager: GLPCTL023I Enabling multi-page file allocation: 'ldapdb' GLPCTL024I Enabled multi-page file allocation: 'ldapdb' GLPCDB005I Configuring database 'ldapdb' for directory server instance: GLPCDB006I Configured database 'ldapdb' for directory server instance: GLPCTL037I Adding local loopback to database: 'ldapdb'. GLPCTL038I Added local loopback to database: 'ldapdb'. GLPCTL011I Stopping database manager for the database instance: GLPCTL012I Stopped database manager for the database instance: GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCDB003I Added database 'ldapdb' to directory server instance: IBM Security Directory Suite Page 48

49 Configure Admin DN and password : ==> /opt/ibm/ldap/v6.4/sbin/idsdnpw -I ldapdb2 -u cn=root -p passwd -n GLPWRP123I The program '/opt/ibm/ldap/v6.4/sbin/64/idsdnpw' is used with the following arguments '-I ldapdb2 -u cn=root -p ***** -n'. You have chosen to perform the following actions: GLPDPW004I The directory server administrator DN will be set. GLPDPW005I The directory server administrator password will be set. GLPDPW009I Setting the directory server administrator DN. GLPDPW010I Directory server administrator DN was set. GLPDPW006I Setting the directory server administrator password. GLPDPW007I Directory server administrator password was set. Back-out method 1 - if the backup method 1 was done: ==> /opt/ibm/ldap/v6.4/sbin/idsdbrestore -I ldapdb2 -k /home/ldapdb2/ldapbackup1 -n GLPWRP123I The program '/opt/ibm/ldap/v6.4/sbin/64/dbrestore' is used with the following arguments '-I ldapdb2 -k /home/ldapdb2/ldapbackup1 -n'. You have chosen to perform the following actions: GLPDBR026I The database and configuration files for directory server instance 'ldapdb2' will be restored from files in directory '/home/ldapdb2/ldapbackup1'. The data in the currently configured database will be overwritten and will be lost. The schema files and directory key stash file currently configured will be overwritten. Unless the -r option was specified, the configuration file and configuration key stash file will also be overwritten. GLPDBR002I Restoring directory server instance GLPDBR005I Loading backup information from a file '/home/ldapdb2/ldapbackup1/backup_files/dbback.dat'. GLPDBR006I Loaded backup information from a file. GLPCTL008I Starting database manager for database instance: GLPCTL009I Started database manager for database instance: GLPCTL101I Restoring backup database ldapdb to configured database ldapdb. GLPCTL102I Restored backup database ldapdb to configured database ldapdb. GLPCTL037I Adding local loopback to database: 'ldapdb'. GLPCTL038I Added local loopback to database: 'ldapdb'. GLPDBR012I Restoring the configuration file for the directory server instance GLPDBR013I Restored the configuration file for the directory server instance GLPDBR015I Restoring the key stash files for the directory server instance GLPDBR016I Restored the key stash files for the directory server instance IBM Security Directory Suite Page 49

50 GLPDBR018I Restoring the schema files for the directory server instance GLPDBR019I Restored the schema files for the directory server instance GLPDBR034I Restoring the database properties file 'ldapdb.properties' for the directory server instance GLPDBR035I Restored the database properties file for the directory server instance GLPDBR037I Restoring the command files 'ibmslapdservice.cmd' and 'ibmdiradmservice.cmd' (Windows) or 'idsrun' (Unix) for the directory server instance 'ibmslapdservice.cmd'. GLPDBR038I Restored the command files for the directory server instance GLPDBR003I Restored directory server instance Alternatively - Back-out method 2 - if the backup method 2 was done: ==> cd /home/ldapdb2/idsslapd-ldapdb2 ==> tar -xf /home/ldapdb2/ldapbackup2/ldapdb2etc.tar ==> /opt/ibm/ldap/v6.4/sbin/idsbulkload -I ldapdb2 -i /home/ldapdb2/ldapbackup2/ldapdata.ldif Perform runstats: ==> idsrunstats -I ldapdb2 Validate the instances and database: ==> idsilist -a Directory server instance(s): Instance 1: Name: ldapdb2 Version: 6.4 Location: /home/ldapdb2 Description: IBM Security Directory Server Instance V6.4 IP Addresses: All available Port: 389 Secure Port: 636 Admin Server Port: 3538 Admin Server Secure Port: 3539 Type: Directory Server ==> /opt/ibm/db2/v10.5/instance/db2ilist ldapdb2 ==> su - ldapdb2 -c db2level DB21085I This instance or install (instance name, where applicable: "ldapdb2") uses "64" bits and DB2 code release "SQL10058" with level identifier " E". Informational tokens are "DB2 v ", "s160901", "IP23998", and Fix Pack "8". Product is installed at "/opt/ibm/db2/v10.5". IBM Security Directory Suite Page 50