SAP Note 523552 Note Language: EnglishDB2/390: BW: DB-Connect Version: 21 Validity: Valid Since 18.06.2009 Summary Symptom You want to extract data from a DB2 database on the mainframe and transfer it to a BW database of release equal or higher than 3.0B using a source system of type database. This note will help you to o Understand the pre-requisites for a successful database source system definition Setup the connection between your SAP BW and the DB2 database to transfer the data to your BW system o o Solve potential problems. This note will be updated as new information becomes available. For connecting a BW system running on DB2/390 to a database of different type, please refer to the database multiconnect notes for that database type Other terms DB2/390, MultiConnect, Data Extraction Reason and Prerequisites Solution I. Important Information +----------------------------------------------------------------------+ | Important Design Change | |To be consistent with UDC and other DB platforms, please implement the| |attached correction or apply: | | BW Support Package 33 for BW 3.0B | | BW Support Package 27 for BW 3.1 Content | | Basis Support Package 60 for BW 3.0B and 3.1 Content | | Support Package Stack 19 for Netweaver 2004 | | Support Package Stack 10 for Netweaver 2004s | | After the correction or the Support Package has been implemented, | | the parameter SCHEMA in DBCON can be any valid DB schema that the || connect user, specified in "User Name", is authorized to access. For|| example, if DOE is allowed to access table ACCOUNT belonging schema || CICSUSR, you can setup DBCON as shown below: | | User Name: DOE | | DB Password: xxxxxxxxxx xxxxxxxxxx | | Conn.info: SSID=D7F0,SCHEMA=CICSUSR,PS=SAP080501 | | After the connection to DB2 as user DOE with password XXXXXXXXXX, | | BW will be able to extract data from table CICSUSR.ACCOUNT | | Previously, only DB objects belonging to DOE, e.g. DOE.anyobj, can be| | extracted! | +----------------------------------------------------------------------+ Support of DB2 Connect V9 CLI Driver ------------------------------------If DB2 Connect V9 CLI driver is used, DBCON must be setup as indicated in note 160484. With the CLI driver, it is tougher to check if the connection to the source database works. But the combination of the "check" button in the source system drop-down menu and workprocess trace should help in the 29.09.2011 Page 1 of 10 For example.0X or 3. BW Database or BW DB: This is the SAP BW database that will store the extracted data. For example.0B. Errors of the type "SQL0805N Package "D7G0. in Case 1 you will need the DB2Connect client code on your SAP instance instead of the ICLI client code.V8 |DB2Connect/ICLI*| |640 | Unicode | Non-Unicode/Unicd| V7.5359534C564C3031" require a rebind of collection SAP080501.09.SYSLH100. This case applies to all non-OS/390 based BW platforms.) Pre-requisites: 29. if connectivity type is DB2Connect because your kernel is 640 and your SAP database is unicode.For those application servers that run on OS platforms that don't. +----------------------------------------------------------------------+ |SAP Kernel|SAP Database| Non-SAP Database |Db2 Ver.V8 | DB2Connect | |620 | Unicode | Any | Any | Use 640 Kernel | |620 | Non-Unicode| Non-Unicode | V7 | ICLI | |620 | Non-Unicode| Non-Unicode | V8 | Use 640 Kernel | |640 | Non-Unicode| Non-Unicode | V7. To successfully transfer the data to BW 3. Kernel release and connectivity type * You have to use the same connectivity type as your SAP database's if your SAP database is a DB2 database.SAP Note 523552 - DB2/390: BW: DB-Connect problem determination. Basis 620 support package 4 must have been applied. a work-around is to build a secondary SAP instance on WINDOW or on any of the previous OS platforms supporting a DB2 DbSl that is available and use that instance to "DBConnect" to the DB2 database using the instructions of this note. ----------------------------------------------------------------------This note is valid only for the application servers that run on an OS platform that supports a DB2 DbSl. This could be a database on any supported platform. Connectivity Types The following table gives the different configurations where extraction of data from a DB2 database with DBconnect is possible.2011 Page 2 of 10 . Defining a Source System of Type Database Terminology: Source DB2: This is a Non-R/3 DB2 Database where data to be extracted is stored.V8 | DB2Connect | |700 | Unicode | Non-Unicode/Unicd| V7. a.SAP080501. III. Source LPAR: LPAR where the source DB2 runs Remote BW Instance: BW application server not running on the source LPAR Local BW Instance: BW application server running on the source LPAR Case 1: Data Extraction From a Remote BW Instance. if you have a BW 3. II.V8 | DB2Connect | +----------------------------------------------------------------------+ Table 1.of| Connectivity | |release | | |non-SAP DB| Type | |----------+------------+------------------+----------+----------------+ |Any | Non-Unicode| Unicode | Any | Not supported | |640 | Unicode | Unicode | V7. Select your connectivity type and apply it to rest of this note.x (X<5) on DB2 and your connectivity to the SAP database is ICLI but you use a 640 kernel then you have to use ICLI to connect to your non-SAP DB2 database. SAP Note 523552 - DB2/390: BW: DB-Connect The following must be available on remote BW instance for ICLI: Appropriate ICLI client code for the hardware platform. Please check with the SAP on OS/390 Planning Guide for the complete details.0B on the source LPAR and listening to the port that isspecified in the DBCON "Conn. If pass-ticket is not used. set the environment variable ICLI_TRUSTED_CONNECTIONS to 1. pass-ticket file (if used). The current Multiconnect architecture allows only ONE pass-ticket or the same pass-ticket for all the connected DB2 databases. Put the iclipt file in /usr/sap/<SID>/SYS/exe/run directory. or if you want to use pass-ticket. For "Conn.2011 Page 3 of 10 .09. Before you can create a source system of type database in BW. If a pass-ticket file already exists. Create an authorization ID <sid>adm in the source DB2.PORT=4562. Click Save and then BACK.setup the pass-ticket file. To get access to the source DB2. that one should be used to setup in the source LPAR as well.SCHEMA=JOHN 29.SAPDBHOST=ihsapje.)Setting Up a Source System of Type Database for a DB2 Source Database In the Administrator Workbench Source System.PORT=<a free port number>.info" enter: SSDID=<ssid of source DB2>. Please check with the SAP on OS/390 Planning Guide on how to get the ICLI client and server code and how to set up the communication. b.info" o o o o o Additional details on ICLI setup can be found in section V.0B. create a source system of type database. Enter any identical strings of characters in both areas reserved for the password. The DB Password field is irrelevant. BW will try to access the source DB2 to validate the source system. Give DB Connection a name and enter DB2 in the DBMS field. This user name is the owner of the DB object you want to access. For DB2 Connect Setup please also refer to section V. This means a certain hardware and OS level for the source LPAR as well as additional software. SCHEMA=<yourschema>.SAPDBHOST=<TCPIP host name of source LPAR>. Install an ICLI server compatible with the BW release 3. appropriate SAP DB2 database library for the hardware platform. you have to: o Bind the ICLI server code to the source DB with a plan name and as plan owner the user whose data you want to extract. if you want to access a table created by user JOHN in DB2 database with SSID D8M0 with icli port 4562 in LPAR ihsapje then enter: User name: JOHN Conn info: SSID=D6M0. Pre-requisites for the source LPAR: The source LPAR must satisfy the requirements for the installation of an ICLI server of BW release 3. As User Name enter the user name whose data will be extracted. the source database must be accessible. Grant that authorization ID execute privilege on the previous plan If pass-ticket is used for the BW DB. For example. Unset the environment variable ICLI_TRUSTED_CONNECTIONS if it was set to 1. In this case there is no ICLI server or client code involved. Check if <sid>adm has been granted "execute privilege" on the plan. Following are hints on what could possibly went wrong. You cannot extract some data with rsdbc 6. You define the source system the same way.2011 Page 4 of 10 . check if source DB2 is up. You can also see it with transaction rsdbc but when you try to look at the data. the source system is defined and available. But you can define a view that converts the data and the name into acceptable types and format. a date DD in the ISO format like 2004-02-04 (February 4. DATE. 2004) can be easily viewed as a VARCHAR resembling the type DATS of DDIC (YYYYMMDD) by removing the "-" surrounding the month (02) with the transformation: 29. The data extraction process is the same as previously described. that field can be extracted. This transaction shows a list of valid tables and views that belong to the user ID defined above. So. In the "Conn.09. Possible Problems. This can only be an OS/390 based BW system. If ping works. Use the view to extract data rather than the table. create an authorization ID as described in the previous section with the same privilege. The table exists in the source database and contains data. Source DB2 is not up 3. BW could not attach to the source DB2 4. the parameter PORT=<a free port number> can be omitted. Hints. See design change above) c. and Restrictions When you save the source system and click on BACK. for example VARCHAR. You can start testing the data extraction with transaction rsdbc.SAP Note 523552 - DB2/390: BW: DB-Connect (SCHEMA can be any schema that JOHN is authorized to use. The possible causes are: 1. No communication to the source LPAR 2. you have a problem if you get a message indicating that the source DB2 is not accessible. Case 2: Data Extraction From a Local BW Instance. You need only to bind the client access code to the source DB2 with the same plan name as the one indicated by the environment variable DBS_DB2_PLANNAME. Check if the plan was bound correctly and successfully. You cannot therefore extract them DIRECTLY. and TIMESTAMP are some of a few data types that are not supported in the SAP data dictionary. Next. Following is an example. If a field of a table has an acceptable type. To solve this problem you can VIEW these data types with some supported data type. Transaction rsdbc will show them as not extractable. Try to ping the source LPAR.) Extracting Data From the Source Db2 If everything is correctly setup. If the data to be extracted does not have a type that is supported by the SAP data dictionary or if the field name format is not acceptable. IV. you cannot extract that data. when you do not use pass-ticket 5. Check the plan name in the case of a local BW instance. TIME. You forgot to set ICLI_TRUSTED_CONNECTIONS to 1. check if CREATE_THREAD is possible. It is is up check if BW could attach to source DB2. rsdbc says there is no data.ifo" field. UNICODE is supported in some SAP database of type other than DB2.SCHEMA=DOE (SCHEMA does not have to be DOE. and you can see the table with rsdbc but when you try to look at the table's data. at the beginning of this note. Note that here you are simply replacing "-" with nothing so there is no space around "-" and in ''. if you are extracting data from a UNICODE DB2 database. if you want to access tables created by DOE in the same DB2 database D6M0 as the one in the previous section.pdf). The result of this transformation for DD is 20040204 of DDIC type CHAR and of length 8 (therefore extractable) that can be easily converted to type DATS later.8). In summary.com/epubs/pdf/iapmpg10. Finally. '-'. You can access simultaneously objects belonging to two or more schemas in the same source database. The UNICODE kernel works only with DB2Connect.2011 Page 5 of 10 . Unicode is supported for the SAP DB2 Database only from release 640.'').PORT=4562. or if you attempt to extract this data to the PSA. How to setup DB2Connect is described in note 731937. Table 1. shows the different types of connectivity that can be used to "DBconnect" to the DB2 non-SAP database for extracting data. then you create another entry in DBCON that looks like: User name: DOE Conn info: SSID=D6M0.ISO). rsdbc says the table contains no data. we recommend that you check the extracted data before using them. You need to define as many source systems as the schemas you want to access. To solve it. Support for UNICODE and DB2Connect From SAP Kernel version 620.ibm.09.boulder. define an entry in DBCON as indicated above. 29. because of many possible differences in the source DB2 database and the BW database. your SAP database must be UNICODE and you need a 640 UNICODE kernel. This problem is caused by the fact that the schema and user name are not set properly.SAPDBHOST=ihsapje.the following section tells you how to setup a source system of type database system to extract data from the non-SAP database o Your application server is on Window If DB2Connect is used then the follwing variables must be in the environment: DB2CODEPAGE=XXX dbs_db2_user=<connect user> DB2DB6EKEY=<STRING>. For each source system. See design change above) A problem could arise when you know that your source table contains data. It can be any schema that DOE is authorized to use. For example. example DB2DB6EKEY=D8M0ihsapje dbs_db2_use_drda=1. V. Assuming that you have setup DB2Connect as indicated in 731937 and/or the ICLI as shown in the SAP on DB2 for OS/390 and z/OS Planning Guide (URL:http://publibz. you get a short dump. you will have to set the schema to the correct schema and the user name to the correct owner of the table.SAP Note 523552 - DB2/390: BW: DB-Connect VARCHAR(REPLACE(CHAR(DD. source system definition.SCHEMA=YYYY. 29. are: -SAPGLOBALHOST -SAPSYSTEMNAME The othe environment variable that has to be set is -ICLI_TRUSTED_CONNECTIONS In transaction RSA1. the parameters you have to set are: -Name of the connection -DBMS type: DB2 -User sname: any name -User password: anything -Conn. for example. info" you will have to enter the SSID of the non-SAP database. The additional parameters you need are -The DBMS type which must be set to DB2.2011 Page 6 of 10 .Give a name to the connection. and the schema of the tables/views where data will be extracted ICLI connectivity is used. The environment variables that MUST be set.. SSID=D8M0. See design change above o UNIX Basically a fewer environment variables have to be set. User "any name" must be authorized to access DB objects of schema YYYYY.Info: SSID=XXXX.SAPDBHOST=HHHH.09. source system definition: .although not used in the case of DBConnect..SAP Note 523552 - DB2/390: BW: DB-Connect DB2INSTANCE=<db2connect instance you use> In transaction RSA1. -A username which is your "connect user" as defined in note 731937 -The password of the previous user -In the "Conn.PORT=NNNN. ICLILIBRARY=D:\usr\sap\. and the package set as the connection parameters. Example: isplp31 is the application server where BI runs. If your BI database is DB2 then you can use db2radm as shown the example in the next section. If your BI 7. info" parameters. D7F0 is the source database running in LPAR ihsapje where the DDF location is D7F0 and the tcpip port is 7114. database. The rest is like in the case of Window. VI. info" section you only have to put the database SSID.0 database is not DB2 please see note 836882.2011 Page 7 of 10 . db2radm runs only when the environment looks like a DB2 environment.13:10:00". This means that you cannot extract a data from a user that does not have a TSO logon ID. If your BI database is a DB2 database then this is not a problem.05 . To fill out the "Conn. The SCHEMA is always that of the logon USER. The next paragraph shows how to setup DB Connect when your source DB is a DB2 database and DB2Connect is used for access. Since you will access the source DB2 with the package set specified in the connection parameters . Do a DIS DDF at the console and note the "location" and the "tcpport". version: "20. and dcs database. This is db2radm setting up DB2 Connect. patch level: "003". DDF for your source DB DB2 (V8 and V7) must be started.09. The environment is there and you should use db2radm. You can use db2radm or a manual bind depending on what your BI database platform. In the "Conn.09.0 The netweaver 2004s kernel supports data extraction from DB2 V8 and V7 with DB2Connect only. Message file is db2radm. You will need those imformations later to register your source DB2 database with DB2Connect. Please see note 722181 for explanation. The DEFAULT SSID if you do not set SSID is your SAP database.0 database is not a DB2 database then please see note 836882. You can use either db2radm or manually using DB2Connect commands to register D7F0 with DB2Connect. please see the section on BI 7. you will need to bind it to your source DB2 DB. db2radm finished (0000) ----------You should now be able to connect to your source database using a command 29. The command is then (assuming that DB2CONNUSER is a TSO User) isplp31:d8cadm 25> db2radm -m db2i -C SAP08501 -H ihsapje -P 7114 -L D7F0 -S D7F0 -u DB2CONNUSER -p DB2CONNUSERsPASSWD (output shown below) ----------This is db2radm release: "700".SAP Note 523552 - DB2/390: BW: DB-Connect -DB2Connect is used If DB2Connect is used and your database is not DB2 then please see note 836882 on how to manually setup DB2 Connect and how to execute a manual BIND.log. You will have to define the node. If your BI 7.0 -ICLI is used You don't have to set SAPGLOBALHOST and SAPSYSTEMNAME. BI 7. 2009 07:10:40 Joachim Rese Recommendations/additional info Hung Nguyen Joachim Rese Joachim Rese 01.SAP Note 523552 like the one shown below: DB2/390: BW: DB-Connect isplp31:d8cadm 25> db2 db2 => connect to D7F0 user DB2CONNUSER Enter current password for DB2CONNUSER: Database Connection Information Database server = DB2 OS/390 7.06.: Note Language: Master Language: Version: Valid Since: Release Status: Released on: Released by: Priority: Author: Entered by: Processed by: Last Changed by: On: Category: Standard Note: Primary Component: Secondary Components: BW-WHM-DST-DBC DB Connect 523552 English English 21 18. But please se note 731937 "Customizing DB2Connect for Web AS 620 and DB2 V8" on how to setup DB2Connect and note 836882 "Manually Customizing DB2 Connect" on how to customize DB2 Connect for use with SAP applications.12.2009 Consulting No BW-SYS-DB-DB2 BW DB2 for OS/390 07:10:40 Valid Releases Software Component SAP_BW SAP_BW SAP_BW SAP_BW Release 30 310 35 70 From Release 30B 310 350 700 To Release 30B 310 350 700 and Subsequent X X X X 29.2011 Page 8 of 10 .1 SQL authorization ID = DB2CONNUSER Local database alias = D7F0 If you are connected to your source DB2 database then DB Connect should work.1. Header Data SAP Note No. For non-DB2 BI databases. the environment is not setup to use db2radm.2009 Released for Customer 01.12.09. 2006 19:28:09 02.2006 19:57:30 17.07.08.SAP Note 523552 Software Component SAP_BW SAP_BASIS SAP_BASIS SAP_BW_VIRTUAL_COMP SAP_BW_VIRTUAL_COMP DB2/390: BW: DB-Connect From Release 710 620 700 30B 700 To Release 710 640 700 30B 700 and Subsequent Release 71 60 70 30 350 70 710 Support Packages Support Packages SAP_BASIS SAP_BASIS SAP_BASIS SAP_BW SAP_BW SAP_BW SAP_BW SAP_BW SAP_BW SAP_BW SAP_BW_VIRTUAL_COMP SAP_BW_VIRTUAL_COMP Release 620 640 700 30B 310 310 350 700 700 71 30B 700 Package Name SAPKB62060 SAPKB64021 SAPKB70010 SAPKW30B33 SAPKW31027 SAPKW31027 SAPKW35019 SAPKW70010 SAPKW70010 710 SAPK-30B40INVCBWTECH SAPK-70010INVCBWTECH Related Notes Number 836882 731937 722181 Short Text DB2-z/OS: Manually Customizing DB2 Connect DB2-z/OS: Customizing DB2 Connect for WebAS 6.2006 13:56:44 00:00:00 29.20 and DB2 V8 DB2-z/OS: BW: DB connect: Access with qualified schema Correction Instructions Correcti on Instruct ions 808376 808377 809977 816199 808491 808491 Valid from Valid to Software Component Typ e *) C C C C C C Reference Correction Last Changed 620 640 700 700 30B 30B 620 640 700 700 30B 30B SAP_BASIS SAP_BASIS SAP_BASIS SAP_BASIS SAP_BW_VIRTUA L_COMP SAP_BW Y6BK078368 Y6DK055180 Y7AK036411 BR9K035907 J19K025786 17.05.2011 Page 9 of 10 .09.07.07.2007 20:18:58 19.2006 13:49:26 23. 2011 Page 10 of 10 .2006 L_COMP 20:01:27 816238 30B 30B SAP_BW C 00:00:00 816238 310 310 SAP_BW C 00:00:00 816238 350 350 SAP_BW C 00:00:00 *) C Correction. B Preprocessing. A Postprocessing.2006 L_COMP 18:59:25 809973 700 700 SAP_BW C 00:00:00 816238 30B 30B SAP_BW_VIRTUA C J19K025964 02.09.SAP Note 523552 Correcti on Instruct ions 808491 808491 809973 Valid from Valid to DB2/390: BW: DB-Connect Typ e *) Reference Correction Last Changed Software Component SAP_BW C 00:00:00 SAP_BW C 00:00:00 SAP_BW_VIRTUA C BR9K035907 19.07. M Undefined Work 310 350 700 310 350 700 29.08.