Updating the Oracle server for V5.2.1 manually IBM

Transcription

1 Updating the Oracle server for V5.2.1 manually IBM

2 ii Updating the Oracle server for V5.2.1 manually

3 Contents Updating the Oracle server for V5.2.1 manually iii

4 iv Updating the Oracle server for V5.2.1 manually

5 Updating the Oracle server for V5.2.1 manually To update an IBM Security Identity Governance Version 5.2 installation to IBM Security Identity Governance and Intelligence Version 5.2.1, install the firmware update. After you install the Oracle server, you must configure it for IBM Security Identity Governance and Intelligence virtual appliance. Before you begin v Verify that you are starting your migration from IBM Security Identity Governance Version 5.2. v The Oracle Server version 12c must be installed. It is the minimum version level required for updating to IBM Security Identity Governance and Intelligence Version v The Oracle Client must be installed. v You must know the common database parameters such as the IP address, server port, and SID. Note: During the migration procedure, for some particular conditions, this diagnostic message can be present in the log file. "NO FLOW <something> FOUND". This message does not identify an error of the procedure and can be ignored. About this task The following tags customize the IBM Security Identity Governance and Intelligence Oracle database installation. Table 1. Tags to customize the IBM Security Identity Governance and Intelligence Oracle database installation. Tags IgiSID DBServer DBPort ServiceName Description Oracle database instance name (SID Oracle Server IP address or DNS name Oracle listener port Oracle Service Name The scripts for the installation of the DB can be delivered in 4 distinct.zip files, all containing the same set of files and distinguished by the license: v SEC_IDNTY_GVN_INTL_CMP_V5.2.1_DT_IN_.zip v SEC_IDNTY_GVN_INTL_ANL_V5.2.1_DT_IN_.zip v SEC_IDNTY_GVN_INTL_LFC_V5.2.1_DT_IN_.zip v SEC_IDNTY_GVN_INTL_IEE_V5.2.1_DT_IN_.zip Depending on the license that you purchased, you must use the right.zip file. See step 2. 1

6 Procedure 1. Configure the tnsnames.ora file. a. Log in with root or Administrator privileges. On UNIX and Linux: sudo su - b. Switch to the oracle user. On UNIX and Linux: sudo su oracle c. Browse to the tnsnames.ora file. For example, oracle_home/db/network/ admin. d. Edit the file in a text editor. For example, vi or Notepad. e. If the network instance is not configured correctly, add the following section: <IgiSID> = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP(HOST = <DBserver>(PORT = <DBport> (CONNECT_DATA = (SERVICE_NAME = <ServiceName> Example 1 XE = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP(HOST = (PORT = <1521> (CONNECT_DATA = (SERVICE_NAME = <XE> Example 2 MYDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP(HOST = <oracle_server_ip>(port = <1521> (CONNECT_DATA = (SERVICE_NAME = <MyDB_service_name> f. Check that the configuration is working by connecting to the database with the following command: sqlplus system/<password>@<igisid> If the connection test ended well, you can exit from the sqlplus with the following command: exit And exit from the oracle user with the following command: exit 2. Run the update scripts. Note: Check the log in the folders after you run each script to see any errors. The log content is the same that you see on the screen during the script execution. 2 Updating the Oracle server for V5.2.1 manually

7 a. With root or Administrator privileges, unpack the.zip file that contains the scripts into a directory of your choice, <your_path>/<updscriptdir>. b. Change the directory to <UPDSCRIPTDIR> with the following command. cd <your_path>/<updscriptdir> c. On UNIX and Linux systems, run the following command. chmod -R 777 * d. Change the directory to AccessGovernanceCoreBackend. cd <UPDSCRIPTDIR>/AccessGovernanceCoreBackend sqlplus sqlplus sqlplus e. Change the directory to Localization. cd../localization sqlplus sqlplus sqlplus f. Change the directory to AccessGovernanceCoreBackend. cd../accessgovernancecorebackend sqlplus sqlplus sqlplus g. Change the directory to AccessRequestsBackend. cd../accessrequestsbackend sqlplus sqlplus h. Change the directory to AccessOptimizerBackend. cd../accessoptimizerbackend sqlplus sqlplus i. Change the directory to AccessRiskControlsForSAPBackend. cd../accessriskcontrolsforsapbackend Run the following command. sqlplus j. Change the directory to DeskBackend. cd../deskbackend Run the following command. sqlplus k. Change the directory to Backend. : cd../ backend sqlplus sqlplus l. Change the directory to EnterpriseConnectorsBackend. cd../enterpriseconnectorsbackend Updating the Oracle server for V5.2.1 manually 3

8 m. Change the directory to JobBackend. cd../jobbackend n. Change the directory to ReportBackend. cd../reportbackend o. Change the directory to RuleEngineBackend. cd../ruleenginebackend p. Change the directory to TaskPlannerBackend. cd../taskplannerbackend q. Change the directory to AuditHelper. cd../audithelper Run the following command. r. Change the directory to SIB_IB_ILC. cd../sib_ib_ilc s. Change the directory to AccessGovernanceCoreBackend. cd../accessgovernancecorebackend t. Change the directory to ReportBackend. cd../reportbackend u. Change the directory to IdeasModule. cd../ideasmodule 4 Updating the Oracle server for V5.2.1 manually

9 Updating the Oracle server for V5.2.1 manually 5