®
IBM Software Group
WebSphere Partner Gateway v6.2 Database Problems, Tips and Hints
Amit Kumar Vijay W PG L3 Support
Sreelatha Sankaranarayanan W PG QA
WebSphere® Support Technical Exchange
IBM Software Group
Agenda
 What you should know before installing WebSphere
Partner Gateway v6.2 DBLoader
 General Information for all WebSphere Partner
Gateway v6.2 fixpack installation
 Selected list of database related APARs from
WebSphere Partner Gateway v6.2 Fixpacks with
further details
 Tips
 Summary
WebSphere ® Support Technical Exchange
2 of 42
IBM Software Group
Agenda
 What you should know before installing WebSphere
Partner Gateway v6.2 DBLoader
 General Information for all WebSphere Partner
Gateway v6.2 fixpack installation
 Selected List of Defects from Fixpacks with further
details (These defects are selected because they
have critical database fixes)
 Tips
 Summary
WebSphere ® Support Technical Exchange
3 of 42
IBM Software Group
WebSphere Partner Gateway v6.2 Database Installation
(1 of 2 )
 WebSphere Partner Gateway v6.2 supports two types of databases, DB2
and ORACLE.
 DBLoader installation on DB2 database
 Make sure DB2 level matches the minimum supported database level.
 Before installing DBLoader you should have login information of DB2
ADMINISTRATOR user.
 Once database installation is finished you should go and check
installation logs for keyword “command was”.
 Installation logs can be found in /tmp/bcgdbloader (for Unix® flavour
platforms) and
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\bcgdbloader for
Windows®.
 If you find any occurrence of “command was” in installation logs,
please try to rectify the problem or else report to support team for
assistance as DBLoader installation is not successful.
WebSphere ® Support Technical Exchange
4 of 42
IBM Software Group
WebSphere Partner Gateway 6.2 Database Installation
(2 of 2)
 DBLoader installation on Oracle database
 Make sure Oracle version matches the minimum supported database version.
 Before installing DBLoader you should have login information of SYS user.
 Please select 2 different names for Schema owner and database user for
security reasons.
 Once database installation is finished you should go and check installation logs
for errors, there should not be any errors.
 Connect to Partner Gateway application database and execute the below mention
command, the output of this command execution should be ‘0’.
“select count(*) from user_objects where status='INVALID‘”
 If output is not equal to ‘0’ then installation is not successful. Please try to rectify the
problem or else contact support team for assistance.
WebSphere ® Support Technical Exchange
5 of 42
IBM Software Group
Agenda
 What you should know before installing WebSphere
Partner Gateway 6.2 DBLoader
 General Information for all WebSphere Partner
Gateway v6.2 fixpack installation
 Selected list of database related APARs from
WebSphere Partner Gateway v6.2 Fixpacks with
further details
 Tips
 Summary
WebSphere ® Support Technical Exchange
6 of 42
IBM Software Group
General information for all WebSphere Partner
Gateway v6.2 fixpack installation

Where to download the fixpack
1. From internet search engine, enter “IBM Support”
2. Choose W ebSphere and any W PG product under the next
selection
3. At W PG product support page, choose Download, Fix packs by
version

Where is readme
1. From the above screen, choose the fixpack you are interested
2. Choose the proper operating system to be redirected to FixCentral
(IBM® Fix Location)
3. Download the Fixpack “*.pak” file, UPDI and the readme.
WebSphere ® Support Technical Exchange
7 of 42
IBM Software Group
General information for all WebSphere Partner Gateway
v6.2 fixpack installation.
( 1 of 3)

1.
2.
3.
i.
ii.
iii.
iv.
v.
vi.
vii.
Things to be remember while installing fixpack
Please verify your system, fulfill minimum Hardware and Software requirement before applying
the fixpack, specifically database requirement.
Fixpack installation is to be done through UPDI
Response file ,that is used by UPDI should contain the right information for below mentioned
fields as the most common reasons for failure are due to wrong input for these fields.
DB2 database user should give these information correctly
-W update.dbtype="DB2“
-W update.appsdbport=“<db2 port which db2 is using>“ – default “50000”.
-W update.appsdbname=“<application database name>” –default bcgapps
-W update.appsownername=“<db2 instance owner in capital letter>“
-W update.appsdbschemaname=“< schema name of application DB>“
-W update.appsownerpassword =“< db2 instance owner password>“
-W update.masdbname=“<mas database name>“ –default bcgmas (Only in case of distributed
mode)
Default db2 instance owner on Windows is DB2ADMIN and on Unix DB2INST1
Give the same information for MAS db also if WPG installed on distributed mode.
WebSphere ® Support Technical Exchange
8 of 42
IBM Software Group
General information for all WebSphere Partner Gateway
v6.2 fixpack installation.
( 2 of 3)
For Oracle database user the response file inputs should look like below
i.
-W update.dbtype=“ORACLE”
ii. -W update.appsdbname=“<Oracle SID for application database >"
iii. -W update.appsdbport=“<Oracle port number>“ – default “1521”.
iv. -W update.appsownername=“<application database user>“ –default bcgdb
v. -W update.appsdbschemaname=“< application database schema owner name >“
–default BCGAPPS
vi. -W update.appsownerpassword =“< application database schema owner
password>“ –default bcgapps’s password
vii. -W update.masdbname=“<Oracle SID for bcgmas database>“
viii. -W update.masownername=“<mas database schema owner name>“ –default
bcgmas
ix. -W update.masdbschemaname=“< mas database schema owner name>“ –default
bcgmas
x. -W update.masownerpassword=“< mas database schema owner password>“ –
default bcgmas password
WebSphere ® Support Technical Exchange
9 of 42
IBM Software Group
General Information for all WebSphere Partner
Gateway v6.2 fixpacks installation
( 3 of 3)


Take database backup before applying the fixpack.

If fixpack installation failed recover the failure and
restore the earlier database dump
Make sure all the application servers are stopped
before applying the fixpack.
WebSphere ® Support Technical Exchange
10 of 42
IBM Software Group
Agenda
 What you should know before installing WebSphere
Partner Gateway 6.2 DBLoader and Fixpacks
 General Information for all WebSphere Partner
Gateway 6.2 fixpack installation
 Selected list of database related APARs from
WebSphere Partner Gateway v6.2 Fixpacks with
further details
 Tips
 Summary
WebSphere ® Support Technical Exchange
11 of 42
IBM Software Group
Selected list of APARs from v6.2 Fixpacks with
further details
Fixpack 1
JR32001 JR32371 JR32610 JR35005 JR32011
JR33012 JR33019 JR33022 JR33024 JR33026
Fixpack 2
JR33382 JR35161 JR35181 JR34161 JR35186
JR33827
Fixpack 3
JR35971 JR35243 JR34912 JR35574
More details to follow about each defect …….
WebSphere ® Support Technical Exchange
12 of 42
IBM Software Group
Fixpack 1 APARs
WebSphere ® Support Technical Exchange
13 of 42
IBM Software Group
JR32001
Symptoms: IMPORT OR UPDATE OF MAPS GREATER THAN 1 MB FAILS.
Database: DB2
Cause or Steps for re-create:
WebSphere Partner Gateway was not able to import or update the maps which are
greater than 1 MB.
Try to import a map which is greater than or equal to 1 MB.
WebSphere Partner Gateway will fail to import the map.
For whom this fix is required: For all the WebSphere Partner Gateway v6.2
customers who uses maps greater than 1 MB.
Description of fix: The Map size was set to 1MB as default which is now increased
to store more than 1 MB size maps.
WebSphere ® Support Technical Exchange
14 of 42
IBM Software Group
JR32371
Symptoms: DB2 HADR feature can not be used for WPG certificates.
Database: DB2
Cause or Steps for re-create:
WebSphere Partner Gateway certificate private key can not be mirrored to
secondary DB2 SERVER due to large size of the LOB data type columns.
For whom this fix is required: For all the WebSphere Partner Gateway v6.2
customer who are using DB2 HADR feature to mirror the database.
Description of fix: The LOB data type columns’ size reduced from 1GB to 1MB to
enable DB2 HADR utility.
WebSphere ® Support Technical Exchange
15 of 42
IBM Software Group
JR32610
Symptoms: Reponse time on AS viewer listing large number of AS documents
was very high .
Database: DB2
Cause or Steps for re-create:
When a huge number of AS documents are routed in WebSphere Partner
Gateway, it was seen that when a user attempts to view the routed documents
using the AS viewer from Partner Gateway Console, the results were displayed
after a considerable delay.
For whom this fix is required: For all WebSphere Partner Gateway v6.2
customers who transact large volumes of AS data.
Description of fix: Performance of AS viewer related procedures has been
improved.
WebSphere ® Support Technical Exchange
16 of 42
IBM Software Group
JR35005
Symptoms: A user can not be created with the same name as that of deleted partner’s user
name using Websphere Partner Gateway console.
Database: Both DB2 and ORACLE
Cause or Steps for re-create: Using Websphere Partner Gateway console, create a user
under a partner and then delete the partner, now try to create a new user with the same
name as that of deleted partner’s user name. WebSphere Partner Gateway throws an error
message which says “A user with given name already exists”.
For whom this fix is required: For all WebSphere Partner Gateway v6.2 customers.
Description of fix: With this fix, during a partner delete the user under that partner is also
deleted. Now a user can be created with the same name as that of a deleted partner's user
name.
WebSphere ® Support Technical Exchange
17 of 42
IBM Software Group
JR32011
Symptoms: In WebSphere Partner Gateway console, the results returned for
"Where Used“ on Destinations, always displayed all the connections instead of
providing the specific participant connections on which the destination was
configured.
Database: Both DB2 and ORACLE
Cause or Steps for re-create:
Create a destination in some partner and now use the destination in connection.
Now again go to partner’s destination page and click on WHERE USED icon on
left hand side. It will show you all the connections instead of providing the specific
connection on which the destination was used.
For whom this fix is required: For all WebSphere Partner Gateway v6.2 customers.
Description of fix: Related database procedure has been fixed to display the right
results.
WebSphere ® Support Technical Exchange
18 of 42
IBM Software Group
EDI PERFORMANCE IMPROVEMENT APARS
(1 of 3)
There was a substantial drop observed in EDI performance
on db2 database and to improve the performance, few fixes
has been done through below mentioned APARS
JR33012, JR33019, JR33022, JR33024, JR33026
JR33012:
Symptoms: Enveloper used to pick up only one completed batch in a
single run. W ith this fix the enveloper is changed to pick all completed
batches in a single run.
Description of fix: EDI Enveloper has been changed.
WebSphere ® Support Technical Exchange
19 of 42
IBM Software Group
EDI PERFORMANCE IMPROVEMENT APARS
(2 of 3)
JR33019:
Symptoms: Under moderate load, the enveloper stopped the generation of
envelopes.
Description of fix: New database indexes has been created and logic in
procedures has changed to improve the performance.
JR33022:
Symptoms: The enveloper throughput was very slow that it processed only two
documents per second. With this fix, the enveloper throughput is increased to
process around thirteen documents per second. .
Description of fix: New database indexes has been created and procedures has
changed to improve the performance.
WebSphere ® Support Technical Exchange
20 of 42
IBM Software Group
EDI PERFORMANCE IMPROVEMENT APARS
(3 of 3)
JR33024:
Symptoms: On AIX, the throughput steadily dropped in a 30-minute run from
nearly 30 documents per second to less than 15 documents per second. This
FixPack rectified the throughput drop on AIX.
Description of fix: Database procedures has changed to improve the performance.
JR33026:
Symptoms: In an outbound scenario, the FA process consumed more than the
normal processing power of DB2 CPU (almost 90%). With this fix, the FA process
will consume normal DB2 processing (20%-30%).
Description of fix: New database indexes have been created and procedures has
changed to improve the performance.
WebSphere ® Support Technical Exchange
21 of 42
IBM Software Group
Fixpack 2 APARs
WebSphere ® Support Technical Exchange
22 of 42
IBM Software Group
JR33382
Symptoms: W hen routing multiple documents that were associated to a
parent document it was seen that the document viewer displayed the
parent document redundantly.
Database: DB2
Cause or Steps for re-create:
Transact documents that are related to a parent document, check the
document viewer to see the parent and the child documents.
For whom this fix is required: For the customers who are using W PG with
DB2 database.
Description of fix: Database procedure has been changed to show the
correct result.
WebSphere ® Support Technical Exchange
23 of 42
IBM Software Group
JR35161
Symptoms: Selecting the Functional Acknowledgment overdue reports from
WebSphere Partner Gateway console for multiple From and To partners, greater
than 20 in number, resulted in SQL Exception. This has been corrected and now it
should be possible to retrieve reports for large number of partners at once.
Database:
DB2
Cause or Steps for re-create: From WebSphere Partner Gateway console
select the EDI FA overdue reports for multiple set of from and to partners (>25
partners)
For whom this fix is required: For all WebSphere Partner Gateway v6.2
customers who transact EDI documents.
Description of fix: Database procedure has been changed to show the right
reports when multiple partners are selected.
WebSphere ® Support Technical Exchange
24 of 42
IBM Software Group
JR35181
Symptoms: The EBMS Viewer in W ebSphere Partner Gateway console
did not display the retried documents under a conversation. This has
been corrected.
Database: Both DB2 and ORACLE
Cause or Steps for re-create:
Route ebms documents, when the acknowledgement is not received the
action message is retried. Go to ebms viewer and see if the action
message and its retries are displayed under the same conversation ID
For whom this fix is required: All customers of W ebSphere Partner
Gateway v6.2 who transact with ebms.
Description of fix: EBMS document processing related procedures has
been changed to display the correct output.
WebSphere ® Support Technical Exchange
25 of 42
IBM Software Group
JR34161
Symptoms: During routing of large volumes of Rosettanet documents,
deadlock errors such as SQL0911 errors were seen.
Database: DB2
Cause or Steps for re-creation:
Transacting large volumes of RNIF documents and check to see if there
are any occurrences of SQL0911 in the logs
For whom this fix is required: For all W ebSphere Partner Gateway
customers who uses RNIF transactions.
Description of Fix: Database procedure has been changed to solve the
problem.
WebSphere ® Support Technical Exchange
26 of 42
IBM Software Group
JR35186
Symptoms: There were a lot of duplicate key exceptions seen in the logs
while transacting ebms documents. These exceptions used to occur while
logging the retried documents.
Database: DB2
Cause or Steps for re-creation:
Route many ebms documents with retry option. Check the logs for
duplicate key exceptions.
For whom this fix is required: For all W ebSphere Partner Gateway v6.2
customers who transact EBMS.
Description of Fix: DB2 procedures has been changed to solve the issue.
WebSphere ® Support Technical Exchange
27 of 42
IBM Software Group
JR33827
Symptoms: EBMS performance degradation
Database: Both DB2 and Oracle
Cause or Steps for re-creation:
There was a performance degrade observed when large volumes of EBMS was
being transacted
For whom this fix is required: For all WebSphere Partner Gateway v6.2, who
use EBMS transactions.
Description of Fix: Database tables were altered, new indexes and procedure
has been created and old ones were fixed to improve the ebms performance in
WebSphere Partner Gateway.
WebSphere ® Support Technical Exchange
28 of 42
IBM Software Group
Fixpack 3 APARs
WebSphere ® Support Technical Exchange
29 of 42
IBM Software Group
JR35971
Symptoms : Sometimes, when using Oracle database for custom XML document
transactions, the WebSphere Partner Gateway used to log ‘SQLException
ORA-00001: unique constraint violated’ error.
Database: Oracle
Cause or Steps for re-creation:
To recreate the issue route many custom XML documents and check the logs,
there will be ‘SQLException ORA-00001: unique constraint violated’ error..
For whom this fix is required: For all WebSphere Partner Gateway v6.2
customers who use custom xml transactions.
Description of Fix: To mitigate the occurrence of this problem, bcgcommon
classes have been corrected to explicitly close the results set objects..
WebSphere ® Support Technical Exchange
30 of 42
IBM Software Group
JR35243
Symptoms : There was a degrade observed in summary engine
performance.
Database: Both DB2 and Oracle
For whom this fix is required: For all WebSphere Partner Gateway v6.2
customers.
Description of Fix: To improve the summary engine performance, data capture
logic in summary engine related tables has been changed.
WebSphere ® Support Technical Exchange
31 of 42
IBM Software Group
JR34912
Symptoms: SQLCODE -104 OCCURS WHILE INSTALLING WebSphere Partner
Gateway v6.2 FIXPACK ON SYSTEM USING DB2 V8.2 FIXPACK 9
Database: DB2 v8.2 Fixpack 9
Cause or Steps for re-creation:
To recreate the issue try to install WebSphere Partner Gateway v6.2 Fixpack on
system using DB2 v8.2 Fixpack 9, it will fail with SQLCODE -104.
For whom this fix is required: For the WebSphere Partner Gateway v6.2.
Description of Fix: To solve the problem new database scripts has been written
with Instructions to guide the customer for successful installation of fixpack.
WebSphere ® Support Technical Exchange
32 of 42
IBM Software Group
JR35574
Symptoms : AS documents were failing as CHARSET attribute was set to "N/A" by
default.
Database: Both DB2 and Oracle
Cause or Steps for re-creation:
This issue is in Websphere partner Gateway v6.2 Fixpack 2 ,try to route the AS
documents in fixpack 2 set up. All AS documents will fail as CHARSET is set to
“N/A”.
For whom this fix is required: For the customers of WPG 6.2 on Fixpack2.
Description of Fix: This problem is fixed in Fixpack 3,the default value for charset
is set to null instead of N/A.
WebSphere ® Support Technical Exchange
33 of 42
IBM Software Group
Agenda
 What you should know before installing WebSphere
Partner Gateway 6.2 DBLoader and Fixpacks
 General Information for all WebSphere Partner
Gateway v6.2 fixpack installation
 Selected list of database related APARs from
WebSphere Partner Gateway v6.2 Fixpacks with
further details
 Tips
 Summary
WebSphere ® Support Technical Exchange
34 of 42
IBM Software Group
Tips

Always use supported database versions for both Oracle and DB2.

Run the database utilities to update the database statics frequently,
this will help you to increase database performance and overall
W ebSphere Partner Gateway performance.

It is better to do stats check after every 10% of data has changed.
It is advisable to put automatic update option for statistics update, if
not then this can be done manually also.
DB2 database user can use
db2reorg and runstats
Oracle database user can use
dbms_stats.gather_schema_stats
WebSphere ® Support Technical Exchange
35 of 42
IBM Software Group
Tips

There are basically 2 types of data which W ebSphere Partner
gateway application database contains

Configuration data

Runtime data
Configuration data is nothing but configuration related data, for
example partner information, certificates, connections etc.
You can maintain this data by running house keeping scripts,
which will clean all the unnecessary data from configuration
table. House keeping scripts can be downloaded from below
mentioned link.
http://www-01.ibm.com/support/docview.wss?uid=swg27017471
WebSphere ® Support Technical Exchange
36 of 42
IBM Software Group
Tips
Runtime data: This is the data which is
generated while routing the documents. To
clean up the old data from application database
please use the archiver on regular basis.
Archiver provide you a provision to mention
retention period while archiving so that it will
archive all the data before the retention period
This will increase WebSphere Partner Gateway
application database performance and overall
performance.
WebSphere ® Support Technical Exchange
37 of 42
IBM Software Group
Agenda
 What you should know before installing WebSphere
Partner Gateway 6.2 DBLoader and Fixpacks
 General Information regarding installation of
DBLoader for WebSphere Partner Gateway 6.2
fixpacks
 Selected list of database related APARs from
WebSphere Partner Gateway v6.2 Fixpacks with
further details
 Tips
 Summary
WebSphere ® Support Technical Exchange
38 of 42
IBM Software Group
Summary
 Through this session we have discussed some of
the factors that need attention during a fixpack
installation.
 We have discussed APARs from WebSphere
Partner Gateway Fixpack 1, Fixpack 2 and Fixpack
3, which had important application database related
fixes.
 As a reminder, we add that Fixpacks are
cumulative and it is recommended that customers
be on the latest fixpack level for WebSphere
Partner Gateway.
WebSphere ® Support Technical Exchange
39 of 42
IBM Software Group
Additional WebSphere Product Resources

Learn about upcoming WebSphere Support Technical Exchange webcasts, and access
previously recorded presentations at:
http://www.ibm.com/software/websphere/support/supp_tech.html

Discover the latest trends in WebSphere Technology and implementation, participate in
technically-focused briefings, webcasts and podcasts at:
http://www.ibm.com/developerworks/websphere/community/

Join the Global WebSphere User Group Community:
http://www.websphere.org

Access key product show-me demos and tutorials by visiting IBM Education Assistant:
http://www.ibm.com/software/info/education/assistant

View a webcast replay with step-by-step instructions for using the Service Request (SR)
tool for submitting problems electronically:
http://www.ibm.com/software/websphere/support/d2w.html

Sign up to receive weekly technical My Notifications emails:
http://www.ibm.com/software/support/einfo.html
WebSphere ® Support Technical Exchange
40 of 42
IBM Software Group
We Want to Hear From You!
Tell us about what you want to learn
Suggestions for future topics
Improvements and comments about our webcasts
W e want to hear everything you have to say!
Please send your suggestions and comments to:
wsehelp@us.ibm.com
WebSphere ® Support Technical Exchange
41 of 42
IBM Software Group
Questions and Answers
WebSphere ® Support Technical Exchange
42 of 42