Datasets:

param-bharat

/

ragbench-context-relevance-filtered

like 1

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IQQG0188E The constructor [ContentCollector4Email] is not initialized properly. How to troubleshoot this error? \n\nSYMPTOM\nThe following error is reported repeatedly in the p8_server_error.log: \n\n * \n * 2016-01-01T11:26:59.803Z 1B471B47 CBR FNRCB0040E - ERROR Object Id: {EAC867B3-6779-58C7-3EE6-6EE9B58E3F5F} ObjectStore Id: {892D8364-A692-4FDA-B2F6-319B159E289A} failed to index into /index/ICCEmail/ICCEmail_Document_20160503091254_F2E934F991D740C4B1BFE247C0A2C136 path /index/ICCEmail/ICCEmail_Document_20160503091254_F2E934F991D740C4B1BFE247C0A2C136/data\\ncom.filenet.api.exception.EngineRuntimeException: \n * \n * \n * FNRCB0040E: CBR_TS_INDEXING_FAILED_EXCEPTION: An IBM Content Search Services server could not complete an indexing operation while accessing the /index/ICCEmail/ICCEmail_Document_20160503091254_F2E934F991D740C4B1BFE247C0A2C136 index. The text for a Content Engine object in batch \"52,835\" could not be indexed for the following reason: \n * \n * \n * \"\n * IQQG0188E The constructor [ContentCollector4Email] is not initialized properly\n * .\". See the p8_server_error.log file for the error message stack that includes this error for more information on the specific cause of the error. For information about the location of this log, see \"Viewing the IBM FileNet P8 log files\" in the IBM FileNet P8 information center. If you cannot determine the specific cause of the error, contact IBM Software Support.\n\n\nSimilar error message can also been seen in the CSS default0.log or trace0.log. \nCAUSE\nStarting with IBM Content Collector (ICC) V3.0, the Content Search Services Support (CSSS) configuration is stored in the configuration store. If CSS cannot access this configuration data during CSS starts up, email may not be indexed properly and cannot be searched. To access the configuration store, the ICC Web Application service must be running. \n\n\nENVIRONMENT\nIBM Content Collector for Email \n\nIBM FileNet P8 repository with Content Search Services\n\n\nDIAGNOSING THE PROBLEM\nDuring the troubleshooting process, you will need the following virtual status URL several times. The output of the URL indicates whether you can reach the ICC configuration web service. \n\nEnter the URL in a browser. Replace <ICC_server_hostname> with your actual ICC server hostname. \n\n * https://\n * <ICC_server_hostname>\n * :11443/AFUConfig/Configuration?type=virtual.status\n * \n\n\nIf you can successfully reach the ICC configuration web service, you should see an XML output similar to the following: * <components>\n * \n * <server>\n * ICC_server_hostname\n * </server>\n * \n * </components>\n * \n\n\nIf you fail to reach the ICC configuration web service, you will get a page cannot be displayed error. \n\nRESOLVING THE PROBLEM\nTo troubleshoot the problem, check the following items step by step: \n\nICC configuration web service is available: \n\n * If the ICC Web Application service is not already running, start the service. \n * On the ICC server, enter the virtual status URL and verify that you get the expected XML output. \n * If this step fails, you have an issue with the ICC Web Application. You will need to resolve that issue before proceeding to the next step.\n\n\nICC configuration web service is accessible from CSS server: * On the CSS server, enter the virtual status URL and verify that you get the expected XML output. \n * If this step fails, use ping <ICC_server_hostname> to verify that you can first reach the ICC server from the CSS server. \n * Next, also check if there is any firewall blocking the default port 11443. \n * Proceed to next step after you verify the virtual status URL works fine on the CSS server.\n\n\nCSS service can contact the configuration store during startup: * Restart the CSS service. \n * Examine the CSS log file if there are any errors. \n trace0.log or default0.log always have the latest entries after you restart the service. \n The location of the log file is, for example, ContentSearchServices\\CSSServer\\log\\trace0.log \n * If there are still issues contacting the ICC configuration web service, you may see the following error in the log file: * \n * <record>\n * \n * <date>2016-05-06T15:08:59</date>\n * \n * <millis>1462572539784</millis>\n * \n * <sequence>6</sequence>\n * \n * <logger>com.ibm.afu.configuration.client</logger>\n * \n * <level>SEVERE</level>\n * \n * <class>com.ibm.afu.configuration.client.RemoteConfigurationManager</class>\n * \n * <method>getConfiguration</method>\n * \n * <thread>0</thread>\n * \n * <message>The number of maximum retries has exceeded</message>\n * \n * </record>\n * \n \n \n * Check previous steps if any of them are failing. \n * Contact IBM support if you need further assistance to resolve this error. \n * If there are no errors in the log, proceed with the next step to re-index documents which failed \n\n\nReindex documents which previously failed: * Depending on the number of problem documents you have, you can re-index and verify one document before re-indexing all of them. \n * Documents can be reindexed via the FileNet Enterprise Manager (FEM) or Application Console for Content Engine (ACCE ). Verify that the index request is completed and no further errors reported.\n\n\nTo reindex one document: * If using FEM, search for the test document, right-click and select All Tasks > Index for Content Search. \n Expand the object store name and select Indexing Queue. If using ACCE, search for the test document. Open the document in a new tab, go to Actions > Index > Index for Content Search. \n Expand the object store name, select Administrative > Indexing Queue. If there is an error during indexing, a return code will be set to the Indexing Failure Code property for that document. If indexing failure code is 0, it means indexing is successful. Proceed to the next step to re-index all documents that have previously failed. \n\nTo re-index all documents that have previously failed: * If using FEM, search for all documents where Indexing Failure Code equals to 1. In the Actions tab, select the check box for Index for Content Search. \n Right-click on the object store name, select All Tasks > Index Job Management. Monitor the progress of the new index job created. If using ACCE, search for all documents where Indexing Failure Code equals to 1. In the Bulk Actions tab, select the check box for Index for Content Search.\n Expand the object store name, select Administrative > Index Job Manager. Monitor the progress of the new index job created. \n\nAdditional considerations: * A non-zero indexing failure code sometimes does not mean there is a problem in the environment. For example, an email that contains a password-protected or encrypted attachment may result in a non-zero return code. \n Refer to this page of the documentation to determine if you need to be concerned of the error code:\n Content Search Services Support document processing errors [http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/p8_indexing/r_afu_css_document_processing_errors.dita] \n * If you regularly restart servers as part of your maintenance routine, consider starting the ICC server before the CSS server. The ICC Web Application service should also set to start Automatic.", "ICC; Task Status; Log Level TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Task Status can be used to affect the behavior of ICC processing. If a task does not complete successfully it may not make sense to continue on to the next step.\n\nChecking the task status in a decision point immediately after a task can be used to determine what steps to take next. \n\nSYMPTOM\nExample: The \"SP Manage P8 Links\" task route deletes P8 document links that can not be resolved to a specific P8 document, and updates all other links.\n\nThe \"P8 Confirm Document\" task checks if the stub link is still point to a document in P8. The link test result is passed on to the next task. Then the SP Manage Link task checks this result and if the link was not successfully resolved it is deleted.\n\nUnfortunately, when the \"P8 Confirm Document\" tasks fails to connect to the P8 repository is also results in links not being resolved. In this situation because the P8 document link could not be resolved, the \"SP Manage Link\" task deletes them from SharePoint.\n\n\nCAUSE\nWhen the \"P8 Confirm Document\" fails to authenticate to P8 it results in a status of \"Warning\". As a result the task route continues to processing on the next task. However, in this specific situation, because the SharePoint Links were not resolved the \"SP Manage Link\" task deletes them.\n\n\nENVIRONMENT\nAll tasks which return a Task Status.\n\nFrom example given: The \"P8 Confirm Document\" task returns a \"Warning\" status when their is a failure to authenticate to P8. In this situation ICC should avoid running the \"SP Manage Link\" task.\n\nDIAGNOSING THE PROBLEM\nFor the example provided above:\n\n1) Valid SharePoint Stub Links were deleted unexpectedly.\n\n2) The P84xConnector log contains log entries with a \"Warning\" status like:\n\nWarning Could not fetch any documents with id = '{xxxxxxxxxxxxx}' using a P8 search scope.Reason: The user is not authenticated. \n\nRESOLVING THE PROBLEM\n1. Add a decision point into the task route between the \"P8 Confirm Document\" task, and the \"SP Manage Link\" task.\n\n2. Configure the rule on the branch that links to the \"SP Manage Link\" task with this rule: \n\n\n\n\n\n GreaterThan ( 3, <Task Status, Log Level> )\n\nNote: This rule will check the task status Log Level and returns TRUE, if the value is >3\n\nFor reference here are the log levels:\nLog Level 1 = Fatal\nLog Level 2 = Error\nLog Level 3 = Warning\nLog Level 4 = Information\nLog Level 5 = Trace\nLog Level 6 = Trace2\n\n\nA return Log Level value of 1 or 2 causes the task route to report an error and transfers further processing to the Error Task Route. \n\nA return Log Level value of 3 is a warning, which is written to the logs, but processing continues on the existing task route. It it these warning situations where alternate processing can be beneficial in avoiding unexpected results (as in the example above).\n\n3. While a second branch is optional, you should add one to bypass the \"SP Manage Link\" task.", "icc TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Content Collector (ICC) email archiving task route fails with \"The list of available property mappings does not contain a definition for the class ICCDocument\" \n\nSYMPTOM\nAll email documents failed with the following error: \n\nThe list of available property mappings does not contain a definition for the class ICCDocument.\n\n\nCAUSE\nThere is a mismatch of document class in the P8 Find Duplicate Email task and the P8 Archive Email task.\n\n\nENVIRONMENT\nIBM Content Collector email archiving with IBM FileNet P8 repository\n\n\n\nDIAGNOSING THE PROBLEM\nReview the email archiving task route and note the document class being used in the following places in ICC Configuration Manager: \n\n * P8 Find Duplicate Email > Options > Document Class \n * P8 Archive Email > Common Settings > Property Mappings > Document Class\n\n\nThe document class in the above two settings should match. \n\nRESOLVING THE PROBLEM\n \n\n * Determine the correct document class that should be used. For example, ICCMail3 document class is created by ICC and can be used for email archiving. \n * Configure the same document class in both places.", " TECHNOTE (FAQ)\n\nQUESTION\n How do I configure IBM Content Collector (ICC) to use SSL to communicate with IBM FileNet P8 for all components? \n\nCAUSE\nICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places.\n\nANSWER\nDo the following steps to install P8 certificates. Depending on your business requirements, you may not use all of the components so some steps may not be necessary. \n\n * First obtain a P8 server certificate by accessing the P8 Content Engine ping page using this URL: https://<ce_server>:<ssl_port>/FileNet/Engine \n \n From the browser, view the certificate and copy it to a file. Use it for later steps. \n Do not use the MTOM page as it may not produce the same certificate that ICC requires. \n \n \n \n \n * Perform this step if you are going to run ICC Initial Configuration to create new document classes in P8 object store. * To import the certificate, issue the following command, whereICCInstallDiris the directory of your Content Collector installation andP8CertificatFileis the certificate for the FileNet P8 server: \"ICCInstallDir\\java\\jre\\bin\\keytool.exe\" -import -file P8CertificateFile\n -keystore \"ICCInstallDir\\java\\jre\\lib\\security\\cacerts\" -alias afup8 \n \n \n * At the password prompt, enter the password for the JRE keystore. (The default password is changeit.) \n * Enterywhen asked whether to trust the certificate. \n * Run ICC Initial Configuration and you should then be able to validate the connection with P8 using SSL.\n \n \n\n * Perform this step if you are going to run task route archiving to P8: * Add the P8 certificate into the Windows Trusted Root Certificate Authorities via the Microsoft Management Console. \n * For more details instructions, refer to this document:\n http://www-01.ibm.com/support/docview.wss?uid=swg21610358 [http://www-01.ibm.com/support/docview.wss?uid=swg21610358]\n \n \n\n * Perform this step if you are going to retrieve, restore, or search for documents from P8: * Start ikeyman from ICC-install-directory\\AFUWeb\\ewasfor the ICC embedded web application server. \n * In the ikeyman utility, select Key Database File>Open, and select PKCS12as key database type. \n * In theLocationfield, specify theWAShome\\profiles\\profile name\\config\\cells\\cell name\\nodes\\node name\\trust.p12file.\n ReplaceWAShome,profile name,cell name, andnode namewith the proper values of your web application server installation. \n * Click OK. \n * When prompted for a password, enter the password. ClickOK. The default password is WebAS. \n * Under theSigner certificateslist, clickAddto add the P8 certificate. \n * Exit ikeyman utility and restart IBM Content Collector Web Application service. \n * For more details instructions, refer to this document: http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en [http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en]", " TECHNOTE (FAQ)\n\nQUESTION\n How do I append the folder and sub-folder structure from a Lotus Notes user mailbox into a FileNet P8 object store using IBM Content Collector (ICC)? \n\nCAUSE\nAs documented in the 'Email system metadata properties' section in ICC Infocenter (linked below), using ICC \"P8 File Document in Folder\" task, the option <Email,Folder> is not always available. \n\nANSWER\nThe folder name will only be extracted if a folder 'include' or 'exclude' has been specified, as that forces ICC to take a less efficient approach in processing the mailbox and traversing the folders instead of just performing a database search. \n\nTo append the folder and sub-folder structure, specify a non-existent folder 'exclude' (e.g. /thisFolderWillNeverExist/ ) in the collector task. \n\n[/support/docview.wss?uid=swg21638520&amp;aid=1] \n\nAlso, because a document may exist in a Notes view, the view name will be extracted if a document is not found in any folder.\n\nRELATED INFORMATION\n IBM Content Collector Email System Metadata Properties [http://publib.boulder.ibm.com/infocenter/email/v3r0m0/topic/com.ibm.content.collector.doc/metadata_and_lists/r_afu_system_metadata_email.htm]" ]

[ [ "3a", " TECHNOTE (FAQ) QUESTION" ], [ "3b", " How do I configure IBM Content Collector (ICC) to use SSL to communicate with IBM FileNet P8 for all components? CAUSE" ], [ "3c", "ICC communicates with P8 in several different components." ], [ "3d", "Depending on the API used for the various components, P8 certificates need to be installed in multiple places. ANSWER" ], [ "3e", "Do the following steps to install P8 certificates." ], [ "3f", "Depending on your business requirements, you may not use all of the components so some steps may not be necessary." ], [ "3g", " * First obtain a P8 server certificate by accessing the P8 Content Engine ping page using this URL: https://<ce_server>:<ssl_port>/FileNet/Engine" ], [ "3h", " From the browser, view the certificate and copy it to a file." ], [ "3i", "Use it for later steps." ], [ "3j", " Do not use the MTOM page as it may not produce the same certificate that ICC requires." ], [ "3k", " * Perform this step if you are going to run ICC Initial Configuration to create new document classes in P8 object store." ], [ "3l", "* To import the certificate, issue the following command, whereICCInstallDiris the directory of your Content Collector installation andP8CertificatFileis the certificate for the FileNet P8 server: \"ICCInstallDir\\java\\jre\\bin\\keytool.exe\" -import -file P8CertificateFile" ], [ "3m", " -keystore \"ICCInstallDir\\java\\jre\\lib\\security\\cacerts\" -alias afup8" ], [ "3n", " * At the password prompt, enter the password for the JRE keystore." ], [ "3o", "(The default password is changeit.)" ], [ "3p", " * Enterywhen asked whether to trust the certificate." ], [ "3q", " * Run ICC Initial Configuration and you should then be able to validate the connection with P8 using SSL." ], [ "3r", " * Perform this step if you are going to run task route archiving to P8: * Add the P8 certificate into the Windows Trusted Root Certificate Authorities via the Microsoft Management Console." ], [ "3s", " * For more details instructions, refer to this document:" ], [ "3t", " http://www-01.ibm.com/support/docview.wss?uid=swg21610358 [http://www-01.ibm.com/support/docview.wss?uid=swg21610358]" ], [ "3u", " * Perform this step if you are going to retrieve, restore, or search for documents from P8: * Start ikeyman from ICC-install-directory\\AFUWeb\\ewasfor the ICC embedded web application server." ], [ "3v", " * In the ikeyman utility, select Key Database File>Open, and select PKCS12as key database type." ], [ "3w", " * In theLocationfield, specify theWAShome\\profiles\\profile name\\config\\cells\\cell name\\nodes\\node name\\trust.p12file." ], [ "3x", " ReplaceWAShome,profile name,cell name, andnode namewith the proper values of your web application server installation." ], [ "3y", " * Click OK." ], [ "3z", " * When prompted for a password, enter the password. ClickOK." ], [ "3aa", "The default password is WebAS." ], [ "3ab", " * Under theSigner certificateslist, clickAddto add the P8 certificate." ], [ "3ac", " * Exit ikeyman utility and restart IBM Content Collector Web Application service." ], [ "3ad", " * For more details instructions, refer to this document: http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en [http://www.ibm.com/support/knowledgecenter/SSAE9L_4.0.1/com.ibm.content.collector.doc_kc/installing/t_afu_establish_trust_relationship.dita?lang=en]" ] ]

[ "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n", "3o", "3p", "3q", "3r", "3s", "3t", "3u", "3v", "3w", "3x", "3y", "3z", "3aa", "3ab", "3ac", "3ad" ]

[ "atlas; pss TECHNOTE (FAQ)\n\nQUESTION\n We have configured a new LDAP server in Atlas but why does authentication work for only some users ? \n\nCAUSE\nAtlas login fails with \"Authentication failed: Unknown user (or) password\"\n\nANSWER\nMake sure the user who failed to login exists in Atlas and is active. If not , create the corresponding user manually or use HR Loader to import those users who are part of the new LDAP server.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS FIXED IF NEXT.\n \n \n \n\nERROR DESCRIPTION\n * LDAP authentication DOES NOT WORK\n Client OS and level: Windows XP\n Server OS and level: Windows 2003 server\n Database and level: Oracle 9i\n Scenario:\n 1. Please find below HotLine call: USA (HL) -\n 0015073\n 2. Once we have imported the users, we can not\n authenticate them using LDAP authentication. (We\n were able to import one by one - not a good\n solution for the long term, but in order to see\n that it did not authenticate we imported one at\n a time.)\n Following is our user dump from LDAP:\n Unable to authenticate using LDAP using this\n test account:\n dn:\n motguid=SMARTM,ou=people,ou=intranet,dc=motor\n ola,\n dc=com\n motGUID: SMARTM\n motCoreID: SMARTM\n displayName: Smarteam Admin-SMARTM\n objectClass: top\n objectClass: person\n objectClass: organizationalPerson\n objectClass: inetOrgPerson\n objectClass: motIntranetPerson\n objectClass: motapplications\n objectClass: motaccount\n telephoneNumber: 8475235219\n motDirectoryStatus: A\n motSupervisorID: 10133452\n motEmploymentActivity: A\n motCommerceID: 12017853\n motCommonNames: Admin Smarteam-SMARTM\n cn: Admin Smarteam\n cn: Admin Smarteam-SMARTM\n sn: Smarteam\n motDisplayFirstName: Admin\n motDisplayLastName: Smarteam\n givenName: Admin\n motDirAccountType: A\n uid: SMARTM\n Using the default attribute mapping the username\n in Smarteam appears as \"Admin Smarteam, Admin\n Smarteam-SMARTM\" if I recall, and trying to\n login as \"SMARTM\" with LDAP Authentication using\n search attribute of cn or motguid does not\n work. We have tried multiple combinations.\n Scenario for LDAP issue 33967:\n 1. Have SUN LDAP in the enterprise\n 2. Import users from LDAP to ST via the ST LDAP\n Import Utility\n 3. Change Authentication of ST to authenticate\n through LDAP\n 4. Try to log in as you do using all other customer\n applications with your UID\n 5. Get an error message: Can not authenticate\n user can not be found in DB.\n Thanks 05/05/05\n Baruch\n there is already BUG for this issue:BID-72285\n .\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * LDAP authentication DOES NOT WORK\n LDAP authentication DOES NOT WORK\n Client OS and level: Windows XP\n Server OS and level: Windows 2003 server\n Database and level: Oracle 9i\n Scenario:\n 1. Please find below HotLine call: USA (HL) -\n 0015073\n 2. Once we have imported the users, we can not\n authenticate them using LDAP authentication. (We\n were able to import one by one - not a good\n solution for the long term, but in order to see\n that it did not authenticate we imported one at\n a time.)\n Following is our user dump from LDAP:\n Unable to authenticate using LDAP using this\n test account:\n dn:\n motguid=SMARTM,ou=people,ou=intranet,dc=motor\n ola,\n dc=com\n motGUID: SMARTM\n motCoreID: SMARTM\n displayName: Smarteam Admin-SMARTM\n objectClass: top\n objectClass: person\n objectClass: organizationalPerson\n objectClass: inetOrgPerson\n objectClass: motIntranetPerson\n objectClass: motapplications\n objectClass: motaccount\n telephoneNumber: 8475235219\n motDirectoryStatus: A\n motSupervisorID: 10133452\n motEmploymentActivity: A\n motCommerceID: 12017853\n motCommonNames: Admin Smarteam-SMARTM\n cn: Admin Smarteam\n cn: Admin Smarteam-SMARTM\n sn: Smarteam\n motDisplayFirstName: Admin\n motDisplayLastName: Smarteam\n givenName: Admin\n motDirAccountType: A\n uid: SMARTM\n Using the default attribute mapping the username\n in Smarteam appears as \"Admin Smarteam, Admin\n Smarteam-SMARTM\" if I recall, and trying to\n login as \"SMARTM\" with LDAP Authentication using\n search attribute of cn or motguid does not\n work. We have tried multiple combinations.\n Scenario for LDAP issue 33967:\n 1. Have SUN LDAP in the enterprise\n 2. Import users from LDAP to ST via the ST LDAP\n Import Utility\n 3. Change Authentication of ST to authenticate\n through LDAP\n 4. Try to log in as you do using all other Motorola\n application with your UID\n 5. Get an error message: Can not authenticate\n user can not be found in DB.\n Thanks 05/05/05\n Baruch\n there is already BUG for this issue:BID-72285\n .\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n * Default TEXTAREA value goes here\n .\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n HD39192\n \n \n * REPORTED COMPONENT NAME\n SMARTEAM NT>XP\n \n \n * REPORTED COMPONENT ID\n 569199970\n \n \n * REPORTED RELEASE\n 514\n \n \n * STATUS\n CLOSED FIN\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2005-05-05\n \n \n * CLOSED DATE\n 2009-04-06\n \n \n * LAST MODIFIED DATE\n 2009-06-24\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS\n * R516 PSN\n UP\n \n \n * R514 PSN SP51407\n UP05/07/05 N 1000\n \n \n * R517 PSN\n UP\n \n \n * R515 PSN\n UP\n \n \n * R518 PSN\n UP", " PRODUCT DOCUMENTATION\n\nABSTRACT\n This document describes how to configure IBM Atlas Policy Suite for Kerberos for IBM WebSphere Application Server or the IBM Employee Retention Portal. Users logged in to a Window Active Directory domain can use IBM Atlas Policy Suite and the IBM Employee Portal without being prompted for credentials. \n\nCONTENT\nYou must complete three main steps to configure IBM Atlas Policy Suite or the IBM Emplyoee Retention Portal to use Kerberos SSO:\n\n\n\n\n 1. Configure your SSO environment. \n 2. Verify your SSO configuration. \n 3. Configure and deploy IBM Atlas Policy Suite (PolicyAtlas) or the IBM Employee Portal (AtlasPortal) with Kerberos/SPNEGO.\n\n\nStep 1: Configure your SSO environment\n\nBefore you configure single sign-on for SPNEGO/Kerberos for IBM Atlas Policy Suite, you must configure your web application server for SPNEGO/Kerberos. \n\nPrerequisites \n\n 1. Configure your Windows Active Directory domain and configure all client workstations as members of the same domain as your Active Directory server. You must use Windows Active Directory as your directory service to use Kerberos. If you have a more complex configuration, you can configure the client workstations as members of a different domain. However, you must cross-certify the servers. \n 2. Install WebSphere Application Server and enable application level security. If you are using WebSphere Application Server V7, fix pack 5 or later is recommended. Earlier versions send unnecessary but harmless HTTP authentication requests. \n 3. Configure WebSphere Application Server to use the domain controller (also called the KDC) for the LDAP repository.\n\n\n\nProcedure 1. To configure your single-server environment for SSO, see chapter 7 (\"Single sign-on to WebSphere Application Server using SPNEGO\") of the IBM Redbook, Implementing Kerberos in a WebSphere Application Server Environment [http://www.redbooks.ibm.com/abstracts/sg247771.html]. \n\n\nStep 2: Verify your SSO configuration\n\nTo verify that SPNEGO/Kerberos is configured correctly, you must configure the web browsers on the client workstations in your environment and authenticate to the LDAP server by using SSO.\n\nPrerequisite\nEnsure that the browsers that are installed on the client workstations support SPNEGO authentication. \n\nProcedure \n\n 1. Log into the client workstation by using an Active Directory user ID. \n 2. Configure your web browser per chapter 7 of the IBM redbook, Implementing Kerberos in a WebSphere Application Server Environment [http://www.redbooks.ibm.com/abstracts/sg247771.html]. \n 3. From your web browser, connect to the snoop servlet by using the fully qualified host name of the WebSphere Application Server instance where you plan to deploy IBM Atlas Policy Suite. When SSO is correctly configured, the snoop servlet issues an authentication challenge to your web browser, which initiates the SPNEGO/Kerberos exchange.\n For example, enter: appserver1.addomain.home.com:9080/snoop \n 4. If the snoop servlet runs successfully, you can configure and deploy IBM Atlas Policy Suite. If the snoop servlet does not run successfully, troubleshoot your SSO configuration before you continue. For more information, see theTroubleshooting your deployment section [http://www-01.ibm.com/support/docview.wss?uid=swg27036837#ts]at the end of this document.\n \n\n\nStep 3: Configure and deploy IBM Atlas Policy Suite (PolicyAtlas) or the IBM Employee Portal (AtlasPortal) with Kerberos/SPNEGO or both\n\nProcedure 1. Run the Atlas installation program. AtlasHome is the installation directory, for example, AtlasHome:C:\\Program Files (x86)\\IBM\\IBM_Atlas_Policy_Suite \n 2. Edit the AtlasHome\\Atlas\\Properties\\ssoConfig.properties file and set the following properties:\n sso.enabled=true\n sso.type=KRB\n # LoginID or other column used as the Person identifier\n sso.column.name=LoginID \n 3. Open a command prompt or shell and enter the command to set the WAS_HOME environment variable. This is a convenience for referencing WebSphere's Apache Ant. For example, set WAS_HOME=C:\\Program Files\\IBM\\WebSphere\\AppServer \n 4. Change to the /AtlasHome directory, for example cd /AtlasHome\n\n\nTo configure IBM Atlas Policy Suite for Kerberos: \n\n 1. Run the Ant command to update PolicyAtlas.ear for Kerberos using the supplied Ant script. For example (in a Windows environment), \"%WAS_HOME%\\bin\\ws_ant.bat\" -buildfile Atlas\\setup\\WebSphere\\Kerberos\\updateForKerberos.xml \n 2. Install Atlas\\EAR\\PolicyAtlas.ear with the WebSphere Integrated Solutions Console. \n 3. Specifiy the class loader order. 1. In the WebSphere Integrated Solutions Console, navigate to the Enterprise Applications node in the Task menu. \n 2. Click the name of the application that you just deployed (AtlasPortal). \n 3. In the Modules section of the Configuration tab, click Manage Modules. \n 4. In the Module column, click web.war. \n 5. In the General Properties section, for Class loader order, select Classes loaded with local class loader first (parent last). \n 6. Click Apply and then click Save in the Messages section.\n \n \n 4. Map PolicyAtlas's security role. See \"Map Security role using the WebSphere Integrated Solutions Console\" below.\n \n 5. Start the application with the WebSphere Integrated Solutions Console.\n\n\nTo configure the IBM Employee Portal for Kerberos: \n\n 1. Run the Ant command to update AtlasPortal.ear by using the supplied Ant script, for example, \"%WAS_HOME%\\bin\\ws_ant.bat\" -buildfile Portal\\Kerberos\\WebSphere\\updateForKerberos.xml \n 2. Install Portal\\Kerberos\\WebSphere\\AtlasPortal.ear with the WebSphere Integrated Solutions Console. Important: Do not install the WAR file. Only the EAR file in this directory supports Kerberos. \n 3. Map AtlasPortal's security role. See \"Map Security role using the WebSphere Integrated Solutions Console.\" \n 4. Start the application with the WebSphere Integrated Solutions Console.\n\n\nMap Security role by using the WebSphere Integrated Solutions Console \n\n 1. Navigate to Applications > Application Types > WebSphere enterprise applications. \n 2. Click the appropriate application (PolicyAtlas or AtlasPortal). \n 3. Click Security role to user/group mapping. \n 4. In the Select column, select the row for the Authenticated role \n 5. In the Map Special Subjects pull-down menu, select All Authenticated in Application's Realm. \n 6. Click OK.\n\n\nTroubleshooting your deployment \n\n\nProblem \nYou receive this error message when attempting to connect to the Policy Atlas URL: \n\nUnauthorized Page you cannot access this page because you do not have the required permissions. Contact your Atlas System Administrator.\n\nSolution \nCheck the following items: \n\n 1. The logged in Active Directory user is also defined as an Atlas person. To check whether the Active Directory account is also defined as an Atlas person, open the IBM Atlas Policy Suite web client, click Admin > Persons, and ensure that the Active Directory account is also defined as an Atlas person. \n 2. \"PolicyAtlas\" is in the filter criteria of SPNEGO Web Authentication in the WebSphere Integrated Solutions Console. Chapter 7 of the IBM redbook, Implementing Kerberos in a WebSphere Application Server Environment [http://www.redbooks.ibm.com/abstracts/sg247771.html]., has an example of specifying snoop in the filter criteria. \n Example: To specify SPNEGO for both snoop and PolicyAtlas: request-url^=snoop|PolicyAtlas \n 3. \n\nProblem \nYou see the following error in the application server log: \n[ 10/18/13 10:35:53:600 PDT] 00000020 srt W om.ibm.ws.webcontainer.srt.SRTServletResponse addSessionCookie WARNING: Cannot set session cookie. Response already committed\n[10/18/13 10:35:53:694 PDT] 00000020 Context E com.ibm.ws.security.spnego.Context begin CWSPN0011E: A non-valid SPNEGO token has been encountered while authenticating a HttpServletRequest \n\nSolution \nUsually, the Service Principal Name (SPN) user’s password has been changed. Reset the SPN user’s password to what it was when the keytab file was generated or generate a new keytab file while you are logged in with the current (changed) password. \n\nProblem \nYou receive unnecessary 401 responses. \n\nSolution \nUpgrade to WebSphere Application Server Version 7.0.0.5. This is known issue that occurs only in a WebSphere Application Server Version 7.0.0.0 environment.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Environment:\n RHEL 3.0\n ITDS 5.2\n DB2 8.1 FP 5\n Problem Description :\n Customer used some scripts which genreate Samba users in the\n LDAP tree.The command which we use is smbldap-useradd.\n Customer ran smbldap-useradd testuser<xx> which is supposed to\n look up users in LDAP,determine LDAP, determine the next\n available UID for the user and then create the necessary\n entries. This hung first time. So does the gententpasswd\n command etc.\n \n There is an unusual code path taken by this script and hence\n is hung in a call to pthread_mutex_lock\n the mutex is left in a locked state.\n \n \n \n \n \n\nLOCAL FIX\n * No work around /local fix\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Systems that have name resolution order configured to use ldap\n authentication might cause ibmslapd to hang. This is because DB2\n will use LDAP to authenticate, and LDAP must call DB2 to service\n the request, creating in theory an infinite recursion, but in\n actual practice leads to a resource deadlock.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Technote #1173490: Name resolution order can cause infinite\n recursion\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IR53786\n \n \n * REPORTED COMPONENT NAME\n ITDS SERVER V5.\n \n \n * REPORTED COMPONENT ID\n 5724E95S0\n \n \n * REPORTED RELEASE\n 520\n \n \n * STATUS\n CLOSED DOC\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2004-05-11\n \n \n * CLOSED DATE\n 2004-07-02\n \n \n * LAST MODIFIED DATE\n 2004-07-02\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n We would like to configure embedded application server login settings to enable user authentication with LDAP. (Note that we are not using WebSphere Application Server.)\n\nWhen we are using Active Directory as LDAP server, the default configuration does not work even if we input correct user name and password in search/text miner application login page.\n\nHow do you configure embedded application server login settings when using Active Directory as LDAP server? \n\nSYMPTOM\nYou will see FFQM0104E when trying to login to search application (or text miner application) with correct user name and password even.\n\n\nENVIRONMENT\nUsing Active Directory as LDAP server.\n\nDIAGNOSING THE PROBLEM\nUse ldifde utility on Active Directory server, or ldapsearch utility to see how the LDAP server is configured. \n\nFor example, run ldifde utility like as follows would results \"export.ldf\" file:\n\nldifde -m -f export.ldf -s <target LDAP server name> -d \"cn=users,dc=example,dc=com\" -b BIND_USERNAME DOMAINNAME PASSWORD\n\nOr, you can get the same sort of result using ldapsearch utility:\n\nldapsearch -h <target LDAP server name> -D <bind user name> -W <bind user password> -b \"cn=users,dc=example,dc=com\"\n\nThose command would show LDAP search result with filter like objectClass=*, thus you can confirm which object/attribute should be used for user authentication in the administration console.\n\n\n\nRESOLVING THE PROBLEM\nGenerally speaking, when you are using Active Directory as LDAP server, specify following values in the administration console, not use all default values. \n\n\nNote: This is nothing but an example thus you must use your own environment value, especially DC component value. In this example, we use \"dc=example,dc=com\" as domain name.\n\n\n 1. BaseDN : cn=Users,dc=example,dc=com \n 2. User ID attribute : sAMAccountName \n 3. Object class for user entries : person (this is the default value) \n 4. Base DN for group entries : dc=example,dc=com \n 5. Group ID attribute : cn \n 6. Member attribute in group entries : member \n 7. Object class for group entries : group\n\n\n\nAlso, make sure to specify \"Use credentials to access to the LDAP server\" with proper user name and password to perform bind with that user privilege. \n\n\n\nCross reference information Segment Product Component Platform Version Edition Watson Group OmniFind Enterprise Edition Not Applicable AIX, Linux, Windows, Linux on System z 9.1" ]

[ [ "0a", "atlas; pss TECHNOTE (FAQ) QUESTION" ], [ "0b", " We have configured a new LDAP server in Atlas but why does authentication work for only some users ? CAUSE" ], [ "0c", "Atlas login fails with \"Authentication failed: Unknown user (or) password\" ANSWER" ], [ "0d", "Make sure the user who failed to login exists in Atlas and is active." ], [ "0e", "If not , create the corresponding user manually or use HR Loader to import those users who are part of the new LDAP server." ] ]

[ "0b", "0c", "0d", "0e", "1l", "1m", "1r", "1s", "1u", "1aw", "1ax", "1ay", "1az", "1bc" ]

[ "atlas; pss TECHNOTE (FAQ)\n\nQUESTION\n We have configured a new LDAP server in Atlas but why does authentication work for only some users ? \n\nCAUSE\nAtlas login fails with \"Authentication failed: Unknown user (or) password\"\n\nANSWER\nMake sure the user who failed to login exists in Atlas and is active. If not , create the corresponding user manually or use HR Loader to import those users who are part of the new LDAP server.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS FIXED IF NEXT.\n \n \n \n\nERROR DESCRIPTION\n * LDAP authentication DOES NOT WORK\n Client OS and level: Windows XP\n Server OS and level: Windows 2003 server\n Database and level: Oracle 9i\n Scenario:\n 1. Please find below HotLine call: USA (HL) -\n 0015073\n 2. Once we have imported the users, we can not\n authenticate them using LDAP authentication. (We\n were able to import one by one - not a good\n solution for the long term, but in order to see\n that it did not authenticate we imported one at\n a time.)\n Following is our user dump from LDAP:\n Unable to authenticate using LDAP using this\n test account:\n dn:\n motguid=SMARTM,ou=people,ou=intranet,dc=motor\n ola,\n dc=com\n motGUID: SMARTM\n motCoreID: SMARTM\n displayName: Smarteam Admin-SMARTM\n objectClass: top\n objectClass: person\n objectClass: organizationalPerson\n objectClass: inetOrgPerson\n objectClass: motIntranetPerson\n objectClass: motapplications\n objectClass: motaccount\n telephoneNumber: 8475235219\n motDirectoryStatus: A\n motSupervisorID: 10133452\n motEmploymentActivity: A\n motCommerceID: 12017853\n motCommonNames: Admin Smarteam-SMARTM\n cn: Admin Smarteam\n cn: Admin Smarteam-SMARTM\n sn: Smarteam\n motDisplayFirstName: Admin\n motDisplayLastName: Smarteam\n givenName: Admin\n motDirAccountType: A\n uid: SMARTM\n Using the default attribute mapping the username\n in Smarteam appears as \"Admin Smarteam, Admin\n Smarteam-SMARTM\" if I recall, and trying to\n login as \"SMARTM\" with LDAP Authentication using\n search attribute of cn or motguid does not\n work. We have tried multiple combinations.\n Scenario for LDAP issue 33967:\n 1. Have SUN LDAP in the enterprise\n 2. Import users from LDAP to ST via the ST LDAP\n Import Utility\n 3. Change Authentication of ST to authenticate\n through LDAP\n 4. Try to log in as you do using all other customer\n applications with your UID\n 5. Get an error message: Can not authenticate\n user can not be found in DB.\n Thanks 05/05/05\n Baruch\n there is already BUG for this issue:BID-72285\n .\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * LDAP authentication DOES NOT WORK\n LDAP authentication DOES NOT WORK\n Client OS and level: Windows XP\n Server OS and level: Windows 2003 server\n Database and level: Oracle 9i\n Scenario:\n 1. Please find below HotLine call: USA (HL) -\n 0015073\n 2. Once we have imported the users, we can not\n authenticate them using LDAP authentication. (We\n were able to import one by one - not a good\n solution for the long term, but in order to see\n that it did not authenticate we imported one at\n a time.)\n Following is our user dump from LDAP:\n Unable to authenticate using LDAP using this\n test account:\n dn:\n motguid=SMARTM,ou=people,ou=intranet,dc=motor\n ola,\n dc=com\n motGUID: SMARTM\n motCoreID: SMARTM\n displayName: Smarteam Admin-SMARTM\n objectClass: top\n objectClass: person\n objectClass: organizationalPerson\n objectClass: inetOrgPerson\n objectClass: motIntranetPerson\n objectClass: motapplications\n objectClass: motaccount\n telephoneNumber: 8475235219\n motDirectoryStatus: A\n motSupervisorID: 10133452\n motEmploymentActivity: A\n motCommerceID: 12017853\n motCommonNames: Admin Smarteam-SMARTM\n cn: Admin Smarteam\n cn: Admin Smarteam-SMARTM\n sn: Smarteam\n motDisplayFirstName: Admin\n motDisplayLastName: Smarteam\n givenName: Admin\n motDirAccountType: A\n uid: SMARTM\n Using the default attribute mapping the username\n in Smarteam appears as \"Admin Smarteam, Admin\n Smarteam-SMARTM\" if I recall, and trying to\n login as \"SMARTM\" with LDAP Authentication using\n search attribute of cn or motguid does not\n work. We have tried multiple combinations.\n Scenario for LDAP issue 33967:\n 1. Have SUN LDAP in the enterprise\n 2. Import users from LDAP to ST via the ST LDAP\n Import Utility\n 3. Change Authentication of ST to authenticate\n through LDAP\n 4. Try to log in as you do using all other Motorola\n application with your UID\n 5. Get an error message: Can not authenticate\n user can not be found in DB.\n Thanks 05/05/05\n Baruch\n there is already BUG for this issue:BID-72285\n .\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n * Default TEXTAREA value goes here\n .\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n HD39192\n \n \n * REPORTED COMPONENT NAME\n SMARTEAM NT>XP\n \n \n * REPORTED COMPONENT ID\n 569199970\n \n \n * REPORTED RELEASE\n 514\n \n \n * STATUS\n CLOSED FIN\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2005-05-05\n \n \n * CLOSED DATE\n 2009-04-06\n \n \n * LAST MODIFIED DATE\n 2009-06-24\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS\n * R516 PSN\n UP\n \n \n * R514 PSN SP51407\n UP05/07/05 N 1000\n \n \n * R517 PSN\n UP\n \n \n * R515 PSN\n UP\n \n \n * R518 PSN\n UP", " PRODUCT DOCUMENTATION\n\nABSTRACT\n This document describes how to configure IBM Atlas Policy Suite for Kerberos for IBM WebSphere Application Server or the IBM Employee Retention Portal. Users logged in to a Window Active Directory domain can use IBM Atlas Policy Suite and the IBM Employee Portal without being prompted for credentials. \n\nCONTENT\nYou must complete three main steps to configure IBM Atlas Policy Suite or the IBM Emplyoee Retention Portal to use Kerberos SSO:\n\n\n\n\n 1. Configure your SSO environment. \n 2. Verify your SSO configuration. \n 3. Configure and deploy IBM Atlas Policy Suite (PolicyAtlas) or the IBM Employee Portal (AtlasPortal) with Kerberos/SPNEGO.\n\n\nStep 1: Configure your SSO environment\n\nBefore you configure single sign-on for SPNEGO/Kerberos for IBM Atlas Policy Suite, you must configure your web application server for SPNEGO/Kerberos. \n\nPrerequisites \n\n 1. Configure your Windows Active Directory domain and configure all client workstations as members of the same domain as your Active Directory server. You must use Windows Active Directory as your directory service to use Kerberos. If you have a more complex configuration, you can configure the client workstations as members of a different domain. However, you must cross-certify the servers. \n 2. Install WebSphere Application Server and enable application level security. If you are using WebSphere Application Server V7, fix pack 5 or later is recommended. Earlier versions send unnecessary but harmless HTTP authentication requests. \n 3. Configure WebSphere Application Server to use the domain controller (also called the KDC) for the LDAP repository.\n\n\n\nProcedure 1. To configure your single-server environment for SSO, see chapter 7 (\"Single sign-on to WebSphere Application Server using SPNEGO\") of the IBM Redbook, Implementing Kerberos in a WebSphere Application Server Environment [http://www.redbooks.ibm.com/abstracts/sg247771.html]. \n\n\nStep 2: Verify your SSO configuration\n\nTo verify that SPNEGO/Kerberos is configured correctly, you must configure the web browsers on the client workstations in your environment and authenticate to the LDAP server by using SSO.\n\nPrerequisite\nEnsure that the browsers that are installed on the client workstations support SPNEGO authentication. \n\nProcedure \n\n 1. Log into the client workstation by using an Active Directory user ID. \n 2. Configure your web browser per chapter 7 of the IBM redbook, Implementing Kerberos in a WebSphere Application Server Environment [http://www.redbooks.ibm.com/abstracts/sg247771.html]. \n 3. From your web browser, connect to the snoop servlet by using the fully qualified host name of the WebSphere Application Server instance where you plan to deploy IBM Atlas Policy Suite. When SSO is correctly configured, the snoop servlet issues an authentication challenge to your web browser, which initiates the SPNEGO/Kerberos exchange.\n For example, enter: appserver1.addomain.home.com:9080/snoop \n 4. If the snoop servlet runs successfully, you can configure and deploy IBM Atlas Policy Suite. If the snoop servlet does not run successfully, troubleshoot your SSO configuration before you continue. For more information, see theTroubleshooting your deployment section [http://www-01.ibm.com/support/docview.wss?uid=swg27036837#ts]at the end of this document.\n \n\n\nStep 3: Configure and deploy IBM Atlas Policy Suite (PolicyAtlas) or the IBM Employee Portal (AtlasPortal) with Kerberos/SPNEGO or both\n\nProcedure 1. Run the Atlas installation program. AtlasHome is the installation directory, for example, AtlasHome:C:\\Program Files (x86)\\IBM\\IBM_Atlas_Policy_Suite \n 2. Edit the AtlasHome\\Atlas\\Properties\\ssoConfig.properties file and set the following properties:\n sso.enabled=true\n sso.type=KRB\n # LoginID or other column used as the Person identifier\n sso.column.name=LoginID \n 3. Open a command prompt or shell and enter the command to set the WAS_HOME environment variable. This is a convenience for referencing WebSphere's Apache Ant. For example, set WAS_HOME=C:\\Program Files\\IBM\\WebSphere\\AppServer \n 4. Change to the /AtlasHome directory, for example cd /AtlasHome\n\n\nTo configure IBM Atlas Policy Suite for Kerberos: \n\n 1. Run the Ant command to update PolicyAtlas.ear for Kerberos using the supplied Ant script. For example (in a Windows environment), \"%WAS_HOME%\\bin\\ws_ant.bat\" -buildfile Atlas\\setup\\WebSphere\\Kerberos\\updateForKerberos.xml \n 2. Install Atlas\\EAR\\PolicyAtlas.ear with the WebSphere Integrated Solutions Console. \n 3. Specifiy the class loader order. 1. In the WebSphere Integrated Solutions Console, navigate to the Enterprise Applications node in the Task menu. \n 2. Click the name of the application that you just deployed (AtlasPortal). \n 3. In the Modules section of the Configuration tab, click Manage Modules. \n 4. In the Module column, click web.war. \n 5. In the General Properties section, for Class loader order, select Classes loaded with local class loader first (parent last). \n 6. Click Apply and then click Save in the Messages section.\n \n \n 4. Map PolicyAtlas's security role. See \"Map Security role using the WebSphere Integrated Solutions Console\" below.\n \n 5. Start the application with the WebSphere Integrated Solutions Console.\n\n\nTo configure the IBM Employee Portal for Kerberos: \n\n 1. Run the Ant command to update AtlasPortal.ear by using the supplied Ant script, for example, \"%WAS_HOME%\\bin\\ws_ant.bat\" -buildfile Portal\\Kerberos\\WebSphere\\updateForKerberos.xml \n 2. Install Portal\\Kerberos\\WebSphere\\AtlasPortal.ear with the WebSphere Integrated Solutions Console. Important: Do not install the WAR file. Only the EAR file in this directory supports Kerberos. \n 3. Map AtlasPortal's security role. See \"Map Security role using the WebSphere Integrated Solutions Console.\" \n 4. Start the application with the WebSphere Integrated Solutions Console.\n\n\nMap Security role by using the WebSphere Integrated Solutions Console \n\n 1. Navigate to Applications > Application Types > WebSphere enterprise applications. \n 2. Click the appropriate application (PolicyAtlas or AtlasPortal). \n 3. Click Security role to user/group mapping. \n 4. In the Select column, select the row for the Authenticated role \n 5. In the Map Special Subjects pull-down menu, select All Authenticated in Application's Realm. \n 6. Click OK.\n\n\nTroubleshooting your deployment \n\n\nProblem \nYou receive this error message when attempting to connect to the Policy Atlas URL: \n\nUnauthorized Page you cannot access this page because you do not have the required permissions. Contact your Atlas System Administrator.\n\nSolution \nCheck the following items: \n\n 1. The logged in Active Directory user is also defined as an Atlas person. To check whether the Active Directory account is also defined as an Atlas person, open the IBM Atlas Policy Suite web client, click Admin > Persons, and ensure that the Active Directory account is also defined as an Atlas person. \n 2. \"PolicyAtlas\" is in the filter criteria of SPNEGO Web Authentication in the WebSphere Integrated Solutions Console. Chapter 7 of the IBM redbook, Implementing Kerberos in a WebSphere Application Server Environment [http://www.redbooks.ibm.com/abstracts/sg247771.html]., has an example of specifying snoop in the filter criteria. \n Example: To specify SPNEGO for both snoop and PolicyAtlas: request-url^=snoop|PolicyAtlas \n 3. \n\nProblem \nYou see the following error in the application server log: \n[ 10/18/13 10:35:53:600 PDT] 00000020 srt W om.ibm.ws.webcontainer.srt.SRTServletResponse addSessionCookie WARNING: Cannot set session cookie. Response already committed\n[10/18/13 10:35:53:694 PDT] 00000020 Context E com.ibm.ws.security.spnego.Context begin CWSPN0011E: A non-valid SPNEGO token has been encountered while authenticating a HttpServletRequest \n\nSolution \nUsually, the Service Principal Name (SPN) user’s password has been changed. Reset the SPN user’s password to what it was when the keytab file was generated or generate a new keytab file while you are logged in with the current (changed) password. \n\nProblem \nYou receive unnecessary 401 responses. \n\nSolution \nUpgrade to WebSphere Application Server Version 7.0.0.5. This is known issue that occurs only in a WebSphere Application Server Version 7.0.0.0 environment.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Environment:\n RHEL 3.0\n ITDS 5.2\n DB2 8.1 FP 5\n Problem Description :\n Customer used some scripts which genreate Samba users in the\n LDAP tree.The command which we use is smbldap-useradd.\n Customer ran smbldap-useradd testuser<xx> which is supposed to\n look up users in LDAP,determine LDAP, determine the next\n available UID for the user and then create the necessary\n entries. This hung first time. So does the gententpasswd\n command etc.\n \n There is an unusual code path taken by this script and hence\n is hung in a call to pthread_mutex_lock\n the mutex is left in a locked state.\n \n \n \n \n \n\nLOCAL FIX\n * No work around /local fix\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Systems that have name resolution order configured to use ldap\n authentication might cause ibmslapd to hang. This is because DB2\n will use LDAP to authenticate, and LDAP must call DB2 to service\n the request, creating in theory an infinite recursion, but in\n actual practice leads to a resource deadlock.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Technote #1173490: Name resolution order can cause infinite\n recursion\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IR53786\n \n \n * REPORTED COMPONENT NAME\n ITDS SERVER V5.\n \n \n * REPORTED COMPONENT ID\n 5724E95S0\n \n \n * REPORTED RELEASE\n 520\n \n \n * STATUS\n CLOSED DOC\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2004-05-11\n \n \n * CLOSED DATE\n 2004-07-02\n \n \n * LAST MODIFIED DATE\n 2004-07-02\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n We would like to configure embedded application server login settings to enable user authentication with LDAP. (Note that we are not using WebSphere Application Server.)\n\nWhen we are using Active Directory as LDAP server, the default configuration does not work even if we input correct user name and password in search/text miner application login page.\n\nHow do you configure embedded application server login settings when using Active Directory as LDAP server? \n\nSYMPTOM\nYou will see FFQM0104E when trying to login to search application (or text miner application) with correct user name and password even.\n\n\nENVIRONMENT\nUsing Active Directory as LDAP server.\n\nDIAGNOSING THE PROBLEM\nUse ldifde utility on Active Directory server, or ldapsearch utility to see how the LDAP server is configured. \n\nFor example, run ldifde utility like as follows would results \"export.ldf\" file:\n\nldifde -m -f export.ldf -s <target LDAP server name> -d \"cn=users,dc=example,dc=com\" -b BIND_USERNAME DOMAINNAME PASSWORD\n\nOr, you can get the same sort of result using ldapsearch utility:\n\nldapsearch -h <target LDAP server name> -D <bind user name> -W <bind user password> -b \"cn=users,dc=example,dc=com\"\n\nThose command would show LDAP search result with filter like objectClass=*, thus you can confirm which object/attribute should be used for user authentication in the administration console.\n\n\n\nRESOLVING THE PROBLEM\nGenerally speaking, when you are using Active Directory as LDAP server, specify following values in the administration console, not use all default values. \n\n\nNote: This is nothing but an example thus you must use your own environment value, especially DC component value. In this example, we use \"dc=example,dc=com\" as domain name.\n\n\n 1. BaseDN : cn=Users,dc=example,dc=com \n 2. User ID attribute : sAMAccountName \n 3. Object class for user entries : person (this is the default value) \n 4. Base DN for group entries : dc=example,dc=com \n 5. Group ID attribute : cn \n 6. Member attribute in group entries : member \n 7. Object class for group entries : group\n\n\n\nAlso, make sure to specify \"Use credentials to access to the LDAP server\" with proper user name and password to perform bind with that user privilege. \n\n\n\nCross reference information Segment Product Component Platform Version Edition Watson Group OmniFind Enterprise Edition Not Applicable AIX, Linux, Windows, Linux on System z 9.1" ]

[ [ "1a", " SUBSCRIBE You can track all active APARs for this component. APAR STATUS" ], [ "1b", " * CLOSED AS FIXED IF NEXT. ERROR DESCRIPTION" ], [ "1c", " * LDAP authentication DOES NOT WORK" ], [ "1d", " Client OS and level: Windows XP" ], [ "1e", " Server OS and level: Windows 2003 server" ], [ "1f", " Database and level: Oracle 9i" ], [ "1g", " Scenario:" ], [ "1h", " 1." ], [ "1i", "Please find below HotLine call: USA (HL) -" ], [ "1j", " 0015073" ], [ "1k", " 2." ], [ "1l", "Once we have imported the users, we can not" ], [ "1m", " authenticate them using LDAP authentication. (We" ], [ "1n", " were able to import one by one - not a good" ], [ "1o", " solution for the long term, but in order to see" ], [ "1p", " that it did not authenticate we imported one at" ], [ "1q", " a time.)" ], [ "1r", " Following is our user dump from LDAP:" ], [ "1s", " Unable to authenticate using LDAP using this" ], [ "1t", " test account:" ], [ "1u", " dn:" ], [ "1v", " motguid=SMARTM,ou=people,ou=intranet,dc=motor" ], [ "1w", " ola," ], [ "1x", " dc=com" ], [ "1y", " motGUID: SMARTM" ], [ "1z", " motCoreID: SMARTM" ], [ "1aa", " displayName: Smarteam Admin-SMARTM" ], [ "1ab", " objectClass: top" ], [ "1ac", " objectClass: person" ], [ "1ad", " objectClass: organizationalPerson" ], [ "1ae", " objectClass: inetOrgPerson" ], [ "1af", " objectClass: motIntranetPerson" ], [ "1ag", " objectClass: motapplications" ], [ "1ah", " objectClass: motaccount" ], [ "1ai", " telephoneNumber: 8475235219" ], [ "1aj", " motDirectoryStatus: A" ], [ "1ak", " motSupervisorID: 10133452" ], [ "1al", " motEmploymentActivity: A" ], [ "1am", " motCommerceID: 12017853" ], [ "1an", " motCommonNames: Admin Smarteam-SMARTM" ], [ "1ao", " cn: Admin Smarteam" ], [ "1ap", " cn: Admin Smarteam-SMARTM" ], [ "1aq", " sn: Smarteam" ], [ "1ar", " motDisplayFirstName: Admin" ], [ "1as", " motDisplayLastName: Smarteam" ], [ "1at", " givenName: Admin" ], [ "1au", " motDirAccountType: A" ], [ "1av", " uid: SMARTM" ], [ "1aw", " Using the default attribute mapping the username" ], [ "1ax", " in Smarteam appears as \"Admin Smarteam, Admin" ], [ "1ay", " Smarteam-SMARTM\" if I recall, and trying to" ], [ "1az", " login as \"SMARTM\" with LDAP Authentication using" ], [ "1ba", " search attribute of cn or motguid does not" ], [ "1bb", " work." ], [ "1bc", "We have tried multiple combinations." ], [ "1bd", " Scenario for LDAP issue 33967:" ], [ "1be", " 1." ], [ "1bf", "Have SUN LDAP in the enterprise" ], [ "1bg", " 2." ], [ "1bh", "Import users from LDAP to ST via the ST LDAP" ], [ "1bi", " Import Utility" ], [ "1bj", " 3." ], [ "1bk", "Change Authentication of ST to authenticate" ], [ "1bl", " through LDAP" ], [ "1bm", " 4." ], [ "1bn", "Try to log in as you do using all other customer" ], [ "1bo", " applications with your UID" ], [ "1bp", " 5." ], [ "1bq", "Get an error message: Can not authenticate" ], [ "1br", " user can not be found in DB." ], [ "1bs", " Thanks 05/05/05" ], [ "1bt", " Baruch" ], [ "1bu", " there is already BUG for this issue:BID-72285" ], [ "1bv", " . LOCAL FIX PROBLEM SUMMARY" ], [ "1bw", " * LDAP authentication DOES NOT WORK" ], [ "1bx", " LDAP authentication DOES NOT WORK" ], [ "1by", " Client OS and level: Windows XP" ], [ "1bz", " Server OS and level: Windows 2003 server" ], [ "1ca", " Database and level: Oracle 9i" ], [ "1cb", " Scenario:" ], [ "1cc", " 1." ], [ "1cd", "Please find below HotLine call: USA (HL) -" ], [ "1ce", " 0015073" ], [ "1cf", " 2." ], [ "1cg", "Once we have imported the users, we can not" ], [ "1ch", " authenticate them using LDAP authentication. (We" ], [ "1ci", " were able to import one by one - not a good" ], [ "1cj", " solution for the long term, but in order to see" ], [ "1ck", " that it did not authenticate we imported one at" ], [ "1cl", " a time.)" ], [ "1cm", " Following is our user dump from LDAP:" ], [ "1cn", " Unable to authenticate using LDAP using this" ], [ "1co", " test account:" ], [ "1cp", " dn:" ], [ "1cq", " motguid=SMARTM,ou=people,ou=intranet,dc=motor" ], [ "1cr", " ola," ], [ "1cs", " dc=com" ], [ "1ct", " motGUID: SMARTM" ], [ "1cu", " motCoreID: SMARTM" ], [ "1cv", " displayName: Smarteam Admin-SMARTM" ], [ "1cw", " objectClass: top" ], [ "1cx", " objectClass: person" ], [ "1cy", " objectClass: organizationalPerson" ], [ "1cz", " objectClass: inetOrgPerson" ], [ "1da", " objectClass: motIntranetPerson" ], [ "1db", " objectClass: motapplications" ], [ "1dc", " objectClass: motaccount" ], [ "1dd", " telephoneNumber: 8475235219" ], [ "1de", " motDirectoryStatus: A" ], [ "1df", " motSupervisorID: 10133452" ], [ "1dg", " motEmploymentActivity: A" ], [ "1dh", " motCommerceID: 12017853" ], [ "1di", " motCommonNames: Admin Smarteam-SMARTM" ], [ "1dj", " cn: Admin Smarteam" ], [ "1dk", " cn: Admin Smarteam-SMARTM" ], [ "1dl", " sn: Smarteam" ], [ "1dm", " motDisplayFirstName: Admin" ], [ "1dn", " motDisplayLastName: Smarteam" ], [ "1do", " givenName: Admin" ], [ "1dp", " motDirAccountType: A" ], [ "1dq", " uid: SMARTM" ], [ "1dr", " Using the default attribute mapping the username" ], [ "1ds", " in Smarteam appears as \"Admin Smarteam, Admin" ], [ "1dt", " Smarteam-SMARTM\" if I recall, and trying to" ], [ "1du", " login as \"SMARTM\" with LDAP Authentication using" ], [ "1dv", " search attribute of cn or motguid does not" ], [ "1dw", " work." ], [ "1dx", "We have tried multiple combinations." ], [ "1dy", " Scenario for LDAP issue 33967:" ], [ "1dz", " 1." ], [ "1ea", "Have SUN LDAP in the enterprise" ], [ "1eb", " 2." ], [ "1ec", "Import users from LDAP to ST via the ST LDAP" ], [ "1ed", " Import Utility" ], [ "1ee", " 3." ], [ "1ef", "Change Authentication of ST to authenticate" ], [ "1eg", " through LDAP" ], [ "1eh", " 4." ], [ "1ei", "Try to log in as you do using all other Motorola" ], [ "1ej", " application with your UID" ], [ "1ek", " 5." ], [ "1el", "Get an error message: Can not authenticate" ], [ "1em", " user can not be found in DB." ], [ "1en", " Thanks 05/05/05" ], [ "1eo", " Baruch" ], [ "1ep", " there is already BUG for this issue:BID-72285" ], [ "1eq", " . PROBLEM CONCLUSION TEMPORARY FIX COMMENTS" ], [ "1er", " * Default TEXTAREA value goes here" ], [ "1es", " . APAR INFORMATION" ], [ "1et", " * APAR NUMBER" ], [ "1eu", " HD39192" ], [ "1ev", " * REPORTED COMPONENT NAME" ], [ "1ew", " SMARTEAM NT>XP" ], [ "1ex", " * REPORTED COMPONENT ID" ], [ "1ey", " 569199970" ], [ "1ez", " * REPORTED RELEASE" ], [ "1fa", " 514" ], [ "1fb", " * STATUS" ], [ "1fc", " CLOSED FIN" ], [ "1fd", " * PE" ], [ "1fe", " NoPE" ], [ "1ff", " * HIPER" ], [ "1fg", " NoHIPER" ], [ "1fh", " * SPECIAL ATTENTION" ], [ "1fi", " NoSpecatt" ], [ "1fj", " * SUBMITTED DATE" ], [ "1fk", " 2005-05-05" ], [ "1fl", " * CLOSED DATE" ], [ "1fm", " 2009-04-06" ], [ "1fn", " * LAST MODIFIED DATE" ], [ "1fo", " 2009-06-24" ], [ "1fp", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "1fq", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "1fr", "APPLICABLE COMPONENT LEVELS" ], [ "1fs", " * R516 PSN" ], [ "1ft", " UP" ], [ "1fu", " * R514 PSN SP51407" ], [ "1fv", " UP05/07/05 N 1000" ], [ "1fw", " * R517 PSN" ], [ "1fx", " UP" ], [ "1fy", " * R515 PSN" ], [ "1fz", " UP" ], [ "1ga", " * R518 PSN" ], [ "1gb", " UP" ] ]

[ "0b", "0c", "0d", "0e", "1l", "1m", "1r", "1s", "1u", "1aw", "1ax", "1ay", "1az", "1bc" ]

[ " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * After migrating a WebSphere MQ v7 classes for JMS application to\n the IBM MQ v8 classes for JMS, the application experiences\n decreased performance when connecting to pre-IBM MQ v8 queue\n managers using the CLIENT transport mode where the SHARECNV\n property on the server-connection channel in use has a value\n greater than 1.\n \n \n \n \n \n\nLOCAL FIX\n * Set the channel property \"SHARECNV\" to have the value '1' for\n the channel which the application is using to communicate with\n the queue manager.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n Users of the IBM MQ classes for JMS v8.0 which are:\n \n (a) Communicating with a queue manager that predates version 8.0\n \n (b) Using a channel to establish a TCP/IP connection where the\n channel's SHARECNV property is set to a value greater than 1\n \n (c) Creating a total number of JMS Connections and JMS Sessions\n which exceeds the value of the SHARECNV property as defined on\n the channel.\n \n \n Platforms affected:\n MultiPlatform, AIX, HP-UX Itanium, IBM iSeries, Linux on Power,\n Linux on S390, Linux on x86, Linux on x86-64, Linux on zSeries,\n Solaris x86-64, Solaris SPARC, Windows, z/OS\n \n ****************************************************************\n PROBLEM DESCRIPTION:\n A performance optimisation in the IBM MQ v8.0 product is\n utilised by an IBM MQ v8.0 classes for JMS application such that\n with a specific configuration (primarily when a channel's\n SHARECNV value is set to the value '1'), a request for messages\n by the application are translated into a synchronous MQ-API call\n to the queue manager.\n \n When this is used, the queue manager channel instance process\n uses a dedicated thread to carry out the attempted retrieval of\n a message.\n \n For example, if a JMS application makes the method call:\n \n MessageConsumer.receive(30000);\n \n it is requesting to wait 30,000ms (or 30 seconds) for a message\n from a queue. When this v8.0 performance optimisation is in\n operation, the dedicated channel instance thread will receive\n the request from the application over TCP/IP, and make a\n synchronous MQGET call to the queue manager. While the thread\n does this, it cannot be used to service any other requests which\n are made over the channel instance. This synchronous method\n should only be used when SHARECNV=1, such that there will be no\n other requests over the channel instance from a client\n application.\n \n \n However, a program defect within the IBM MQ v8.0 classes for JMS\n meant that under a specific circumstance, this synchronous\n optimisation could be activated when communicating with a queue\n manager version earlier than v8.0 and where the SHARECNV value\n on the channel was greater than '1'.\n \n \n The consequence of this was that if multiple requests are being\n made over the same TCP/IP socket, the dedicated thread\n associated with the channel instance would service one after the\n other, meaning that the second and subsequent requests would be\n delayed until the previous was complete.\n \n For example, consider that two JMS Sessions are using the same\n TCP/IP socket to communicate with the queue manager. A\n MessageConsumer has been created from each Session, to consume\n messages from different queues on the queue manager.\n \n If the queue that \"MessageConsumer_1\" was consuming messages\n from contains no messages and requests a 30 second wait time on\n the receive call, \"MessageConsumer_2\" which makes a receive call\n to the different queue (which contains messages) must wait the\n 30 seconds for the first operation to complete, eg:\n \n 00:00:00 MessageConsumer_1.receive(30000)\n 00:00:01 MessageConsumer_2.receive(30000)\n 00:00:30 MessageConsumer_1 completes, returning no messages\n 00:00:30 MessageConsumer_2 returns a message from the second\n queue\n \n \n \n To understand how JMS Sessions might share a TCP/IP connection\n and trigger this performance problem, we need to look at how\n MQ-JMS objects use 'hconns'.\n \n A 'hconn' is the object that is used by a thread to communicate\n with the queue manager. The number of 'hconns' which fit over a\n TCP/IP socket is that which is specified by the SHARECNV channel\n property.\n \n For example, for a default channel the SHARECNV value is 10.\n This means that 10 'hconns' can use the same TCP/IP socket. If\n an 11th 'hconn' is required, a new TCP/IP socket is created.\n \n For the MQ-JMS API, every JMS Session and JMS Connection use one\n 'hconn'. The performance problem described by this APAR is only\n triggered when a JMS Session is created which triggers the\n generation of a new TCP/IP socket to a queue manager version\n which is less than v8.0.\n \n For example, consider the following application:\n \n SHARECNV=10\n \n (1) Application creates a JMS Connection (1 'hconn')\n (2) Application creates nine JMS Sessions from this Connection\n (9 'hconns').\n \n Now the TCP/IP socket is 'full'. The next JMS Connection or\n Session created will require a new TCP/IP socket.\n \n (3) Application creates a further 2 JMS Sessions from the above\n Connection.\n \n The first of these incorrectly negotiates with the queue manager\n to use this synchronous performance enhancement, and now all\n 'hconns' created which use this TCP/IP socket will be affected\n by the single threading behaviour of the channel instance for\n the socket.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The IBM MQ classes for JMS have been updated to ensure that this\n new synchronous requesting performance feature is not enabled\n for a queue manager which is at a version less than v8.0.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v8.0 8.0.0.4\n \n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n \n If the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT10730\n \n \n * REPORTED COMPONENT NAME\n WMQ BASE MULTIP\n \n \n * REPORTED COMPONENT ID\n 5724H7251\n \n \n * REPORTED RELEASE\n 800\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2015-08-17\n \n \n * CLOSED DATE\n 2015-08-25\n \n \n * LAST MODIFIED DATE\n 2015-08-25\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WMQ BASE MULTIP\n \n \n * FIXED COMPONENT ID\n 5724H7251\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R800 PSY\n UP", "2059 2058 client connection multi queue managers mqchllib mqchltab amqclchl.tab 2058 2059 2058 2059 2058 2059 2058 2059 2058 2059 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You encounter problems when trying to connect your WebSphere MQ (WMQ) client applications to more than one queue manager. You want to know how to connect an MQ client to more than one queue manager. \n\nSYMPTOM\nTypical return codes when you are encountering problems: \n\n2058 0x0000080a MQRC_Q_MGR_NAME_ERROR\n2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE\n2009 0x000007d9 MQRC_CONNECTION_BROKEN\n\n\nRESOLVING THE PROBLEM\nTo connect a client to multiple queue managers you can use a Client Channel Definition Table (CCDT). In UNIX the channel table is created on the server machine in the /mqmtop/qmgrs/QUEUEMANAGERNAME/@ipcc directory when you define your client connection channels. \n\n- You can define multiple client connection channels for the different queue managers to which you want the client to connect. \n\n- You need to ensure that each queue manager has a corresponding server connection channel for the client connection channel defined for that queue manager in the CCDT. \n\n- Copy the client channel table (AMQCLCHL.TAB) from the server machine to the client machine as a binary file. This can be copied into any directory that you choose on the client machine. \n\n- In the client application, you will need to have multiple MQCONNs for each of the queue managers to which you want to connect, and use appropriately the corresponding queue manager handle for each connection, which will use a different server-connection channel. \n\n- On the client machine you must unset the MQSERVER environment variable: \n\nWindows: set MQSERVER= \n\nUNIX: unset MQSERVER \n\n- On the client machine you must set the MQCHLLIB and MQCHLTAB environment variables. \n+ The MQCHLLIB environment variable must have the fully qualified path to the CCDT file. \n\n + The MQCHLTAB environment variable must have the name of the CCDT file. \n\n\nFor example, if you copied the client channel table into the /var/mydir directory, then you can set the environment variables on a UNIX system by typing:\n\nexport MQCHLLIB=/var/mydir\nexport MQCHLTAB=AMQCLCHL.TAB\n\n\nNotes: \n- The MQCHLLIB can be in any directory that you choose on the client.\n\n- You should only copy the channel table on the server machine to the client machines. You should not delete the channel table from the server machine: it is not recreated by the queue manager.\n\n\n- This will work the same on all platforms except OpenVMS. The client channel table file is binary so will be able to be read on all platforms. \n\n- For more detailed information see: Accessing client-connection channel definitions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.con.doc/q016770_.htm?lang=en]\n\n- See MQCHLLIB [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.con.doc/q016950_.htm?lang=en] and MQCHLTAB [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.con.doc/q016960_.htm?lang=en] for more information. \n\n- The following high availability sample program uses automated client reconnection and moves a message from the queue of a source queue manager to a remote queue manager.\nThe source code illustrates how to handle separate connections to multiple queue managers.\nWindows: MQ_INSTALL\\tools\\c\\Samples\\amqsmhac.c\nUnix: MQ_INSTALL/samp/amqsmhac.c\n\n\nReferences:\n\n\n * Webcast: Using a Client Channel Definition Table (CCDT) in WebSphere MQ V7 for Queue Manager Groups [http://www.ibm.com/support/docview.wss?uid=swg27024109] \n * Techdoc: Using a Client Channel Definition Table (CCDT) in WebSphere MQ V7 for Queue Manager Groups [http://www.ibm.com/support/docview.wss?uid=swg27020848] \n * Techdoc: Using a CCDT file to connect to multiple WebSphere MQ queue managers using JMS [http://www.ibm.com/support/docview.wss?uid=swg27020862] \n * Techdoc: Exploiting the Automatic Client Reconnect feature in WebSphere MQ JMS 7.0.1 [http://www.ibm.com/support/docview.wss?rs=171&uid=swg27023313] \n * Techdoc: Exploiting the Automatic Client Reconnect feature introduced in WebSphere MQ 7.0.1 – MQI (C Code) [http://www.ibm.com/support/docview.wss?rs=171&uid=swg27017882]\n\n \n\nPRODUCT ALIAS/SYNONYM\n WebSphere MQ WMQ", "z/os SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DUPLICATE OF ANOTHER APAR.\n \n \n \n\nERROR DESCRIPTION\n * MDB listeners fail with reason '2500'(MQRC_HCONN_ASYNC_ACTIVE)\n after migration to MQ V701.\n .\n The following information is found in the WAS Control\n Region joblog.\n .\n com.ibm.ejs.jms.listener.MDBCppUtilitiesInterfaceImpl.startListe\n ning(MDBCppUtilitiesInterfaceImpl.java:505)\n at\n com.ibm.ws390.mdb.MDBCppUtilities.startListening(MDBCppUtilities\n .java:190)\n Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call\n failed with compcode '2' ('MQCC_FAILED') reason '2500'\n ('MQRC_HCONN_ASYNC_ACTIVE').\n .\n .\n The problem is caused by the way the MQ code determines\n which enviornment it is running in. For WAS V6, we do not\n correctly identify that the code is running in the WAS Control\n Region. This causes us to use the wrong threading model for\n the MDB listeners. The model is incompatible with the async\n consume processing used by the listeners, and results in thread\n reuse problems when MDB listeners are active. The bad thread\n reuse causes the failure with the 2500 reason code.\n \n \n \n \n \n\nLOCAL FIX\n * ++APARs are available:\n ++APAR ANE4673, built on the Fix Pack 7.0.1.1 (UK53422) level\n ++APAR ANE5625, built on the Fix Pack 7.0.1.2 (UK56957) level\n -OR-\n In WebSphere Application Server V6, the system property can be\n set using the Admin console:\n Servers->Application Servers (from the left hand menu) then\n select:\n <server name>->Java and Process Management->Process\n Definition->Servant->Java Virtual Machine->CustomProperties->New\n Name=com.ibm.msg.client.wmq.overrideProviderVersion\n Value=6\n .\n \n The same property should be set in the control region using:\n <server name>->Java and Process Management->Process\n Definition->Control->Java Virtual Machine->CustomProperties->New\n Name=com.ibm.msg.client.wmq.overrideProviderVersion\n Value=6\n \n \n \n \n \n\nPROBLEM SUMMARY\n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n * Problem summary:\n In WebSphere Application Server Version 6, an MDB listener is\n configured to monitor a queue, or a topic with a durable\n subscription.\n \n If the MDB listener is using a bindings mode connection to the\n queue manager, it incorrectly performs asynchronous message\n consumption on the WebSphere thread that started the listener.\n \n This causes subsequent JMS work on the same WebSphere thread to\n fail with compcode 2 and rsncode 2500 (MQRC_HCONN_ASYNC_ACTIVE).\n \n Exceptions similar to the following are seen in the control\n region:\n \n com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call\n failed with compcode '2' ('MQCC_FAILED') reason '2500'\n ('MQRC_HCONN_ASYNC_ACTIVE').\n .at com.ibm.msg.client.wmq.common.internal.Reason.\n createException(Reason.java:223)\n \n Problem resolution:\n The MQ JMS code has been updated so that MDB listeners running\n in the control region use a separate thread for asynchronous\n message consumption.\n \n This fix changes the Java component of MQ, and will be\n included in FixPack 7.0.1.3 (PM09662 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM09662]).\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n PM11411\n \n \n * REPORTED COMPONENT NAME\n WMQ Z/OS V7\n \n \n * REPORTED COMPONENT ID\n 5655R3600\n \n \n * REPORTED RELEASE\n 018\n \n \n * STATUS\n CLOSED DUB\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2010-04-01\n \n \n * CLOSED DATE\n 2010-05-27\n \n \n * LAST MODIFIED DATE\n 2010-08-24\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS", "MQPRB MQPRB3189 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When attempting to create an XA connection to WebSphere® MQ from either WebSphere Application Server Version 7.x or Version 8.x with a connection factory that uses the Client Channel Definition Table (CCDT), the following error appears in the application server's SystemOut.log file: \n\n J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource <connection factory>. The exception which was received is javax.jms.JMSException: MQJMS1068: failed to obtain XAResource \n\n\n\nCAUSE\nThe reason why it is not possible to use the CCDT with XA connections is related to transaction recovery. \n\n If the application server stops while there are still active transactions, there is no way with the current implementation to ensure that it will connect to the same queue manager when it restarts. This can lead to in-doubt transactions being left dangling, and never resolved. \n\n It is hoped that this restriction will be resolved in future releases of WebSphere Application Server and WebSphere MQ.\n\nRESOLVING THE PROBLEM\nThe use of the Client Channel Definition Table (CCDT) with XA connections is not supported.\n\n \n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Java Message Service (JMS) Application Servers Runtimes for Java Technology Java SDK \nPRODUCT ALIAS/SYNONYM\n WMQ WASAS WAS", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Collective service delivery for WebSphere MQ v7.0\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Collective service MDV 7.0.0.2 for WebSphere MQ v7.0\n \n Details of problems fixed for JAVA/JMS are included in\n APAR SE37101 - 5724L26 (option *BASE)\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Collective service MDV 7.0.0.2 for WebSphere MQ v7.0\n - which contains fixes for all the problems listed below:\n \n . .\n IZ40651 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ40651] - MESSAGE-DRIVEN BEANS HANG WHEN MESSAGE ENDPOINTS ARE .\n STOPPED DUE TO AN UNHANDLED EXCEPTION .\n IZ39041 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ39041] - WEBSPHERE MQ BASE JAVA AND JMS CLIENTS DO NOT MAP .\n CODEPAGE 1386 TO GBK. .\n IZ39036 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ39036] - CONCURRENTMODIFICATIONEXCEPTIONS OCCUR WHEN USING THE.\n WEBSPHERE MQ RESOURCE ADAPTER. .\n IZ39034 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ39034] - MESSAGE-DRIVEN BEANS ARE NOT GETTING RESTARTED IF THE.\n CONNECTION IS BROKEN OR THE QUEUE MANAGER IS .\n RESTARTED. .\n IZ36978 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ36978] - JMSREPLYTO ALWAYS CONTAINS QUEUE MANAGER NAME AFTER .\n APAR IZ15279 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ15279] HAS BEEN APPLIED .\n IZ36664 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ36664] - WEBSPHERE MQ JAVA APPLICATIONS THAT USE SSL AND .\n COMPRESSED CHANNELS MAY RECEIVE CORRUPTED DATA WITH .\n LARGE MESSAGES .\n IC60100 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC60100] - WEBSPHERE MQ V7 JMS APPLICATIONS USING RECEIVENOWAIT()\n WILL FAIL TO PROCESS MORE THAN ONE MESSAGE .\n IC59871 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59871] - WEBSPHERE MQ VERSION 7 JMS CLIENTS RECEIVING MESSAGES.\n FROM A VERSION 6 QUEUE MANAGER FAIL TO GET MESSAGES, .\n WITH NO ERRORS. .\n IC59701 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59701] - WEBSPHERE MQ JMS CLIENTS FAIL TO PARSE RFH HEADERS IF.\n THE JMSTYPE FIELD OF THE INCOMING MESSAGE CONTAINS A .\n NAMESPACE. .\n IC59462 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59462] - WEBSPHERE MQ V7 JMS APPLICATIONS MAY CREATE TOO MANY,.\n OR TOO FEW SHARED CONVERSATIONS PER CONNECTION. .\n IC59304 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59304] - AMQ9640 ERROR WHEN USING A WEBSPHERE MQ VERSION 7 JAVA\n CLIENT WITH A CCDT GENERATED BY WEBSPHERE MQ VERSION .\n 6. .\n IC58936 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC58936] - THE USER DATA BUFFER LENGTH FOR WEBSPHERE MQ JAVA .\n SECURITY EXITS IS NOT RESET FOR EMPTY BUFFERS. .\n IC58897 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC58897] - JMSBYTESMESSAGE.GETBODYLENGTH() DOES NOT RETURN THE .\n CORRECT VALUE FOR WEBSPHERE MQ JMS MESSAGES .\n 130435 - WEBSPHERE MQ VERSION 7 JAVA MESSAGE SERVICE (JMS) .\n APPLICATIONS GENERATE FDC FROM .\n HANDLEMESSAGEREFERENCE() METHOD .\n 129338 - ABORTED IN-FLIGHT XA CLIENT TRANSACTION LEAVES .\n UNCOMMITTED MESSAGES ON THE QUEUE .\n 129335 - JMSCS0006 ERRORS AFTER MIGRATING WEBSPHERE MQ JAVA .\n MESSAGE SERVICE PUBLISH/SUBSCRIBE APPLICATIONS FROM V6\n TO V7 .\n 128450 - MEMORY LEAK WHEN WEBSPHERE MQ VERSION 7 JAVA MESSAGE .\n SERVICE APPLICATIONS CREATE TEMPORARY DESTINATIONS .\n 128218 - WEBSPHERE MQ V7 JAVA MESSAGE SERVICE APPLICATIONS THAT\n USE ASYNCHRONOUS MESSAGE CONSUMERS HANG DURING .\n SHUTDOWN .\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n * Collective service MDV 7.0.0.2 for WebSphere MQ v7.0\n - which contains fixes for all the problems listed below:\n \n . .\n IZ40651 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ40651] - MESSAGE-DRIVEN BEANS HANG WHEN MESSAGE ENDPOINTS ARE .\n STOPPED DUE TO AN UNHANDLED EXCEPTION .\n IZ39041 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ39041] - WEBSPHERE MQ BASE JAVA AND JMS CLIENTS DO NOT MAP .\n CODEPAGE 1386 TO GBK. .\n IZ39036 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ39036] - CONCURRENTMODIFICATIONEXCEPTIONS OCCUR WHEN USING THE.\n WEBSPHERE MQ RESOURCE ADAPTER. .\n IZ39034 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ39034] - MESSAGE-DRIVEN BEANS ARE NOT GETTING RESTARTED IF THE.\n CONNECTION IS BROKEN OR THE QUEUE MANAGER IS .\n RESTARTED. .\n IZ36978 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ36978] - JMSREPLYTO ALWAYS CONTAINS QUEUE MANAGER NAME AFTER .\n APAR IZ15279 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ15279] HAS BEEN APPLIED .\n IZ36664 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ36664] - WEBSPHERE MQ JAVA APPLICATIONS THAT USE SSL AND .\n COMPRESSED CHANNELS MAY RECEIVE CORRUPTED DATA WITH .\n LARGE MESSAGES .\n IC60100 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC60100] - WEBSPHERE MQ V7 JMS APPLICATIONS USING RECEIVENOWAIT()\n WILL FAIL TO PROCESS MORE THAN ONE MESSAGE .\n IC59871 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59871] - WEBSPHERE MQ VERSION 7 JMS CLIENTS RECEIVING MESSAGES.\n FROM A VERSION 6 QUEUE MANAGER FAIL TO GET MESSAGES, .\n WITH NO ERRORS. .\n IC59701 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59701] - WEBSPHERE MQ JMS CLIENTS FAIL TO PARSE RFH HEADERS IF.\n THE JMSTYPE FIELD OF THE INCOMING MESSAGE CONTAINS A .\n NAMESPACE. .\n IC59462 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59462] - WEBSPHERE MQ V7 JMS APPLICATIONS MAY CREATE TOO MANY,.\n OR TOO FEW SHARED CONVERSATIONS PER CONNECTION. .\n IC59304 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC59304] - AMQ9640 ERROR WHEN USING A WEBSPHERE MQ VERSION 7 JAVA\n CLIENT WITH A CCDT GENERATED BY WEBSPHERE MQ VERSION .\n 6. .\n IC58936 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC58936] - THE USER DATA BUFFER LENGTH FOR WEBSPHERE MQ JAVA .\n SECURITY EXITS IS NOT RESET FOR EMPTY BUFFERS. .\n IC58897 [http://www-01.ibm.com/support/docview.wss?uid=swg1IC58897] - JMSBYTESMESSAGE.GETBODYLENGTH() DOES NOT RETURN THE .\n CORRECT VALUE FOR WEBSPHERE MQ JMS MESSAGES .\n 130435 - WEBSPHERE MQ VERSION 7 JAVA MESSAGE SERVICE (JMS) .\n APPLICATIONS GENERATE FDC FROM .\n HANDLEMESSAGEREFERENCE() METHOD .\n 129338 - ABORTED IN-FLIGHT XA CLIENT TRANSACTION LEAVES .\n UNCOMMITTED MESSAGES ON THE QUEUE .\n 129335 - JMSCS0006 ERRORS AFTER MIGRATING WEBSPHERE MQ JAVA .\n MESSAGE SERVICE PUBLISH/SUBSCRIBE APPLICATIONS FROM V6\n TO V7 .\n 128450 - MEMORY LEAK WHEN WEBSPHERE MQ VERSION 7 JAVA MESSAGE .\n SERVICE APPLICATIONS CREATE TEMPORARY DESTINATIONS .\n 128218 - WEBSPHERE MQ V7 JAVA MESSAGE SERVICE APPLICATIONS THAT\n USE ASYNCHRONOUS MESSAGE CONSUMERS HANG DURING .\n SHUTDOWN .\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n SE37101\n \n \n * REPORTED COMPONENT NAME\n JAVA CLIENT ISE\n \n \n * REPORTED COMPONENT ID\n 5724L2620\n \n \n * REPORTED RELEASE\n 700\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2009-03-02\n \n \n * CLOSED DATE\n 2009-03-02\n \n \n * LAST MODIFIED DATE\n 2009-05-08\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nMODULES/MACROS\n * RCHMGR\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n 1AVA CLIENT ISE\n \n \n * FIXED COMPONENT ID\n 5724L2620\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY SI34791\n UP A" ]

[ [ "3a", "MQPRB MQPRB3189 TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " When attempting to create an XA connection to WebSphere® MQ from either WebSphere Application Server Version 7.x or Version 8.x with a connection factory that uses the Client Channel Definition Table (CCDT), the following error appears in the application server's SystemOut.log file:" ], [ "3c", " J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource <connection factory>." ], [ "3d", "The exception which was received is javax.jms.JMSException: MQJMS1068: failed to obtain XAResource CAUSE" ], [ "3e", "The reason why it is not possible to use the CCDT with XA connections is related to transaction recovery." ], [ "3f", " If the application server stops while there are still active transactions, there is no way with the current implementation to ensure that it will connect to the same queue manager when it restarts." ], [ "3g", "This can lead to in-doubt transactions being left dangling, and never resolved." ], [ "3h", " It is hoped that this restriction will be resolved in future releases of WebSphere Application Server and WebSphere MQ." ], [ "3i", "RESOLVING THE PROBLEM" ], [ "3j", "The use of the Client Channel Definition Table (CCDT) with XA connections is not supported." ], [ "3k", "Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Java Message Service (JMS) Application Servers Runtimes for Java Technology Java SDK PRODUCT ALIAS/SYNONYM" ], [ "3l", " WMQ WASAS WAS" ] ]

[ "3b", "3c", "3d", "3e", "3f", "3g", "3h", "3i", "3j", "3k" ]

[ "CC; global monitor; srfm; synchronous request for mastership; reqmaster; vob; srfm enabled; gen_replica_sits.bat; gen_replica_sits; bat; configure; setup TECHNOTE (FAQ)\n\nQUESTION\n How can you configure IBM Rational ClearCase MultiSite Global Monitor for use with Synchronous Request for Mastership (SRFM) enabled VOBs? \n\nANSWER\n \n\nSynchronous request for mastership \n\n \n\nSynchronous request for mastership (SRFM) allows a user to immediately checkout a file or directory version even if the branch is initially mastered at another replica in the VOB family, provided it is safe to do so. When invoked on a remotely mastered branch, the feature silently sends a request for mastership to the remote master. If any blocking conditions are encountered, for instance, if someone already has a reserved checkout on the branch at the mastering site, the SRFM request is denied, and the requesting user’s SRFM checkout fails. However, if no blocking conditions are encountered, the remote master transfers mastership as it would for any reqmaster request. In this case, the requesting user’s SRFM checkout succeeds, and the user can modify the file or directory. The SRFM checkout is said to be in a pending reserved state. No one else may perform a reserved checkout on that branch. However the user may not check in the file or directory until mastership arrives (by the normal MultiSite syncreplica process). \n\n \n\nRefer to technote 1470733 [http://www.ibm.com/support/docview.wss?uid=swg21470733]for more details of how to configure and use SRFM. \n\n \n\n \n\nConfigure Global Monitoring for use with SRFM enabled VOBs \n\n \n\nTo use the SRFM feature, a ClearCase administrator must raise the family feature level of every replicated VOB family where users will be allowed to use SRFM to Feature Level 6. This feature level change requires the administrator to modify a script file to reflect the change used by the Global Monitoring function. See Raising the VOB family feature level [https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m2/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_admin.doc/c_raising_vob_fam_feat_lvls.htm] and the cleartool chflevel [https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m2/index.jsp?topic=/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_chflevel.htm]man page for details. \n\n \n\n \n\nLocation of script file and how to change it \n\n \n\nAfter installing ClearCase 7.1.2.2 patch (or newer version) on a VOB server host or a view server host, you need to modify the following script file: \n\n\n/opt/IBM/ITM/platform/rc/bin/gen_replica_sits.bat (on Unix and Linux) \n\nC:\\IBM\\ITM\\TAMITM6\\gen_replica_sits.bat (on Windows) \n\n \n\nReplace this line in VerMapFL subroutine: \n\n if ( $cc_ver =~ m/7(.*)/ ) { \n\n \n\nwith the following lines: \n\n \n\n if ( $cc_ver =~ m/7.1.(\\d).(\\d)/ ) {\nif ( $1 == 2 && $2 >= 2 ) {\n$fl = \"6\";\n} elsif ($1 > 2) {\n$fl = \"6\";\n} else {\n$fl = \"5\";\n}\n} elsif ( $cc_ver =~ m/7.1.(\\d)/ ) {\nif ( $1 >= 3 ) {\n$fl = \"6\";\n}\nelse {\n$fl = \"5\";\n}\n} elsif ( $cc_ver =~ m/7(.*)/ ) {\n\n\n \n\nThe ClearCase administrator must stop Global Monitoring on that VOB or view server host and restart it after modifying the script file.\n\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational ClearCase Mastership: Reqmaster AIX, HP-UX, Linux, Solaris, Windows 7.1.2.2", "1255007; ClearCase MultiSite Full Function Installation; ClearCase Web Interface Server; install features; install components; view support; local views; vob support; local vobs; component uninstall; feature uninstall; remove components; view and vob support; add/remove programs TECHNOTE (FAQ)\n\nQUESTION\n How do you add additional IBM® Rational® ClearCase® components such as MultiSite®, the Rational Web Platform (RWP) and other components to an existing installation on Microsoft® Windows®, UNIX® and Linux®? \n\nANSWER\n\n\n\n\n\n\n\nUNIX and Linux\n\nMicrosoft Windows\n\nIMPORTANT NOTE for 2003.06.00 modifications on Windows\n\n\n\n\n \n\nUNIX and Linux \n\nTo Add or Remove ClearCase components, follow the these instructions: \n\n 1. Run the ./install_release script. You can select the option to install or de-install a component from the ./install_release menu presented.\n \n 1 : Select local install\n 2 : Select remote install\n 3 : Multiple Remote install\n 4 : Local deinstall\n \n Note: The Local deinstall option will allow for a component deinstall as well as a full uninstall. The script will also stop ClearCase during the installation/deinstallation process to Add or Remove the selected component. \n \n \n 2. When prompted for components to install, (for example RWP), add the * mark in front of the selection as shown below to reinstall with the selected component:\n \n Note: The Rational Web Platform is installed when ClearCase Web Interface Server is installed.\n \n Similarly, to remove a component, remove the * mark for that component.\n \n Components preceded with a '*' are selected for installation.\n 1 : ClearCase Minimal Developer Installation\n 2 : ClearCase Server-only Installation\n * 3 : ClearCase MultiSite Full Function Installation\n * 4 : ClearCase Web Interface Server\n 5 : ClearQuest Integration with ClearCase\n 6 : ClearDDTS Integration with ClearCase\n 7 : ClearCase Mainframe Connectors\n 8 : ClearCase MultiSite Shipping Server-only Installation\n 9 : ClearCase Full Function Installation\n a : Select all\n f : Finish selection\n x : Toggle expanded descriptions\n r : Reset selections\n q : Quit\n\n\n\nNote: Review technote 1254974 [http://www.ibm.com/support/docview.wss?rs=984&uid=swg21254974] for an explanation as to why the Web options do not appear for Solaris® 10 running on the x86-32 platform. \n\n Back to top \n\n\n\n\n \n\nMicrosoft Windows \n\nFor the Windows operating system, you will use the Add or Remove Programs GUI in the Control Panel.\n\n\n1. Open the Control Panel (Start > (Settings) > Control Panel) and click Add or Remove Programs\n\n\n\n2. Find IBM Rational ClearCase in the list and click Change\n\n[/support/docview.wss?uid=swg21255007&aid=1] [/support/docview.wss?uid=swg21255007&aid=1] \n\nNote: Review technote 1254998 [http://www.ibm.com/support/docview.wss?rs=984&uid=swg21254998] if you receive the following error:\n\nThe installed product does not match the installation source(s)....\n\n[/support/docview.wss?uid=swg21255007&amp;aid=2] \n\n\n\n3. Click Next \n\n[/support/docview.wss?uid=swg21255007&aid=3] [/support/docview.wss?uid=swg21255007&aid=3] \n\n\n\n\n4. Ensure Modify is selected and click Next. \n\n[/support/docview.wss?uid=swg21255007&aid=4] [/support/docview.wss?uid=swg21255007&aid=4] \n\n\n\n\n5. Select the feature to Add or Remove based on your need. \n\n\nFor example, all features except the ClearCase Client for VS.NET are installed below: \n\n[/support/docview.wss?uid=swg21255007&aid=5] [/support/docview.wss?uid=swg21255007&aid=5] \n\n \n\n * To Uninstall and existing component\n \n Click the drop down arrow next to the component you wish to remove.\n Click This feature will not be available\n Click Next and complete the wizard.\n \n [/support/docview.wss?uid=swg21255007&aid=6] [/support/docview.wss?uid=swg21255007&aid=6]\n\n\n * To Install a new component\n \n Click the drop down arrow next to the component you wish to add.\n Click This feature will be installed on the local hard drive\n Click Next and complete the wizard.\n \n [/support/docview.wss?uid=swg21255007&aid=7] [/support/docview.wss?uid=swg21255007&aid=7]\n\n\n Back to top \n\n\n\n\n\nIMPORTANT NOTE for 2003.06.00 modifications on Windows\n\nIf you have applied one of the non-Service Release patches to an existing ClearCase service release and have subsequently done a Modify install to change your features as noted above, you must re-apply that patch afterwards to ensure that any fixes to that added feature are properly applied.\n\nThis step of re-applying the patch is necessary because the features are being installed from the installation media, and as such are not patched yet. Re-applying the patch will bring all the files on the system up to the same version.\n\nBelow is one scenario where this issue can be observed:\n\n\n * ClearCase 2003.06.16 (Service Release 6) was installed on a Windows host \n * Patch clearcase_p2003.06.16.NT-2007B was subsequently installed on that host. \n * A feature was mistakenly left out and needs to be added \n * A modify install (a feature of the MSI install) of ClearCase 2003.06.16 is then performed over the existing installation in order to add the (previously not installed) missing feature. \n * The newly added feature is installed at the 2003.06.16 level, however, it will not be up to date with any fixes that may be contained in the 2007B patch.\n \n\nNote: The above scenario holds true for any of the following ClearCase 2003.06.16 patches: \nclearcase_p2003.06.16.NT-2007A \nclearcase_p2003.06.16.NT-2007B \nclearcase_p2003.06.16.NT-2007C \nclearcase_p2003.06.16.NT-2006E \n\n\nRefer to technote 1223699 [http://www-1.ibm.com/support/docview.wss?uid=swg21223699]for information about a related issue regarding uninstall not removing service release updates: \n\n\n Back to top \n\n\n\nRELATED INFORMATION\n#ClearCase UNIX/Linux: Installation and Upgrade Guide [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/topic/com.ibm.rational.clearcase.books.cc_ms_install_ux.doc/cc_ms_install.htm]\nClearCase Windows: Installation and Upgrade Guide [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/topic/com.ibm.rational.clearcase.books.cc_ms_install_win.doc/cc_ms_install.htm]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational ClearCase Installation", "1146197; text_file_delta; 8000; failed create_version operation; z_text_file; contains a line exceeding 8000 bytes; PK34583 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains why attempts to checkin an IBM® Rational® ClearCase® file causes an error stating the file contains a line exceeding 8000 bytes along with steps to resolve the problem. \n\nSYMPTOM\n \n\nDuring checkin the following error occurs: \n\n \n\ntext_file_delta: Error: \"foo.c\" is not a 'text file': it contains a line exceeding 8000 bytes.\nUse a different type manager (such as compressed file).\ncleartool: Error: Type manager \"text_file_delta\" failed create_version operation.\ncleartool: Error: Unable to check in \"foo.c\".\n\n\nCAUSE\n \n\nThis is due to the text_file_delta type manager is unable to handle a single line of 8000 bytes or more.\n\nNote: Some type manager errors on Windows are reported in the Windows Application Log (Source:ClearCase, Category:Debug). Therefore, when performing the checkin operation on Windows the error below will be displayed and the more detailed message as noted above will be reported in the \nApplication Log.\n\ncleartool: Error Type manager \"text_file_delta\". failed create_version operation.\ncleartool: Error: Unable to check in \"testfile\".\n\n\nRESOLVING THE PROBLEM\n \n\n \n\nThis issue has been addressed by new type managers that were made available in ClearCase 2002.05.00, refer to technote 1127954 [http://www-1.ibm.com/support/docview.wss?&rs=984&uid=swg21127954] on how to implement them in your environment. \n\n \n\nThe details in technote 1119269 [http://www-1.ibm.com/support/docview.wss?rs=984&uid=swg21119269] discuss how these new type managers are integrated after upgrading to ClearCase 2003.06.00. \n\n \n\nThe new type managers are only made available in a VOB that is at feature level 4. If you have upgraded to Rational ClearCase 7.0 [http://www-1.ibm.com/support/docview.wss?rs=984&uid=swg24012293], but have not upgraded the VOB to feature level 4, then the new type managers are not available for use. \n\n \n\nWORKAROUNDS: \n\nThere are two possible ways to resolve this issue without using the new type managers detailed above: \n\n \n\n 1. Insert line breaks in the file so that the length of every line is less than 8000 characters to allow the checkin to succeed.\n \n \n OR \n \n \n 2. Modify the file type so that it uses a different type manager like compressed_file.\n \n Example: cleartool chtype compressed_file foo.c\n \n\n\nRefer to the IBM RFE Community [https://www.ibm.com/developerworks/rfe/] for information about a Change request (RFE) 3656 [http://www.ibm.com/developerworks/support/rational/rfe/execute?use_case=viewChangeRequest&CR_ID=3656]that was opened to request support for exceeding 8,000 bytes per line on text files. RELATED INFORMATION\n#New type managers introduced in v2002.05.00 [http://www.ibm.com/support/docview.wss?uid=swg21127954]\nDetecting lines with 8000 or more characters [http://www.ibm.com/support/docview.wss?uid=swg21179082]\nKnowledge Collection: Type manager \"text_file_delta\" [http://www.ibm.com/support/docview.wss?uid=swg21259086]\nCompare and merge functionality is for text files only [http://www.ibm.com/support/docview.wss?uid=swg21259298]\nA Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21459446]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational ClearCase Type Manager", "feature level; chflevel; unreplicated; non-replicated; base; clearcase; 1150579; feature levels; replicated VOB TECHNOTE (FAQ)\n\nQUESTION\n How can you increase the feature level of a single non-replicated IBM Rational ClearCase VOB without increasing the feature level for the other VOBs on the server? \n\nANSWER\n \n\nExecute the following two commands: \n\n 1. cleartool chflevel -replica <new feature level> replica:<replica name>@\\<vob tag>\n \n \n 2. cleartool chflevel -family <new feature level> vob:\\<vob tag>\n\n\n\nNotes: * These commands are used for replicated VOB as well; however, there are special considerations that need to be taken when changing the feature level of a VOB that is replicated. Review the MultiSite Administrator's Guide under the topic of Feature levels [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_admin.doc/c_feature_levels.htm]for more details.\n \n * If a VOB is used in a UCM environment, the PVOB and all Component VOBs must be at the same feature level in order to utilize the features of that level.\n\n\nExample: \n\n 1. Open a command prompt and set into a view\n \n \n 2. Mount and change directory into the VOB tag\n \n \n 3. Describe the VOB to show current feature level\n \n > cleartool describe -long vob:.\n versioned object base \"/vobstore/test_vob\"\n created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)\n VOB family feature level: 2\n VOB storage host:pathname \"host1:/vobstore/test_vob.vbs\"\n VOB storage global pathname \"/net/host1/vobstore/test_vob.vbs\"\n database schema version: 53\n VOB ownership:\n owner ibm.com/jdoe\n group ibm.com/group1\n Additional groups:\n group ibm.com/other\n VOB holds objects from the following views:\n Attributes:\n FeatureLevel = 2 \n \n \n 4. Determine the replica name (by default is original)\n \n > cleartool lsreplica\n For VOB replica \"/vobstore/test_vob\":\n 23-Mar.09:36 jdoe replica \"original\"\n \n \n 5. Change the feature level. * Step 1:\n > cleartool chflevel -replica 3 replica:original@/vobstore/test_vob\n Replica feature level raised to 3.\n \n \n * Step 2:\n > cleartool chflevel -family 3 vob:/vobstore/test_vob\n cleartool: Warning: Raising the VOB family feature level may make it impossible to move this VOB to servers running an earlier revision of ClearCase and to create MultiSite replicas of this VOB on such servers.\n Raise VOB family feature level? [no] y\n VOB family feature level raised to 3.\n \n \n \n \n 6. Describe the VOB to show new feature level:\n \n > cleartool describe -long vob:.\n versioned object base \"/vobstore/test_vob\"\n created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)\n VOB family feature level: 3\n VOB storage host:pathname \"host1:/vobstore/test_vob.vbs\"\n VOB storage global pathname \"/net/host1/vobstore/test_vob.vbs\"\n database schema version: 53\n VOB ownership:\n owner ibm.com/jdoe\n group ibm.com/user\n Additional groups:\n group ibm.com/other\n VOB holds object from the following views:\n Attributes:\n FeatureLevel = 3 \n\n\nReview the ClearCase Command Reference Guide on the topic of chflevel (cleartool man chflevel) for more information. \n\n \n\n\n\n\n\nRELATED INFORMATION\n#About Feature Levels and ClearCase [http://www.ibm.com/support/docview.wss?uid=swg21119269]", "CC; cleartool: Error: VOB schema; feature level; and element's type manager must support large file versions; Support for large files; support large file versions; Feature Level 5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to resolve an error, cleartool: Error: VOB schema, feature level, and element's type manager must support large file versions., that can occur when using IBM Rational ClearCase (CC) and performing checkin or checkout operations in a VOB. \n\nSYMPTOM\n \n\n\nThe 2GB limit appears to have been reached even with CC 7.0.1 or later installed which should have included this support for certain file types. \n\nWhen working with files, actions such as checkins or checkouts result in the error: \n\n \n\ncleartool: Error: VOB schema, feature level, and element's type manager must support large file versions.\n\n\n\nCAUSE\n \n\nThe VOB in question was itself created on a machine running an older (pre 7.x) version of ClearCase and the VOB is still at Feature Level 4 (or earlier). Feature Level 5 (introduced in ClearCase 7.0) is required in order to support large file versions. \n\n\nRefer to the IBM Rational ClearCase 7.0 Release Notes under the topic of Support for large files in VOBs [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/index.jsp?topic=/com.ibm.rational.clearcase.help.doc/cc_ms_release_notes.htm]for further information.\n\n\nRESOLVING THE PROBLEM\n \n\n \n\nUpgrade the VOB to Feature Level 5." ]

[ [ "3a", "feature level; chflevel; unreplicated; non-replicated; base; clearcase; 1150579; feature levels; replicated VOB TECHNOTE (FAQ) QUESTION" ], [ "3b", " How can you increase the feature level of a single non-replicated IBM Rational ClearCase VOB without increasing the feature level for the other VOBs on the server? ANSWER" ], [ "3c", "Execute the following two commands:" ], [ "3d", " 1. cleartool chflevel -replica <new feature level> replica:<replica name>@\\<vob tag>" ], [ "3e", " 2. cleartool chflevel -family <new feature level> vob:\\<vob tag>" ], [ "3f", "Notes: * These commands are used for replicated VOB as well; however, there are special considerations that need to be taken when changing the feature level of a VOB that is replicated." ], [ "3g", "Review the MultiSite Administrator's Guide under the topic of Feature levels [http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_admin.doc/c_feature_levels.htm]for more details." ], [ "3h", " * If a VOB is used in a UCM environment, the PVOB and all Component VOBs must be at the same feature level in order to utilize the features of that level. Example: 1." ], [ "3i", "Open a command prompt and set into a view 2." ], [ "3j", "Mount and change directory into the VOB tag 3." ], [ "3k", "Describe the VOB to show current feature level" ], [ "3l", " > cleartool describe -long vob:." ], [ "3m", " versioned object base \"/vobstore/test_vob\"" ], [ "3n", " created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)" ], [ "3o", " VOB family feature level: 2" ], [ "3p", " VOB storage host:pathname \"host1:/vobstore/test_vob.vbs\"" ], [ "3q", " VOB storage global pathname \"/net/host1/vobstore/test_vob.vbs\"" ], [ "3r", " database schema version: 53" ], [ "3s", " VOB ownership:" ], [ "3t", " owner ibm.com/jdoe" ], [ "3u", " group ibm.com/group1" ], [ "3v", " Additional groups:" ], [ "3w", " group ibm.com/other" ], [ "3x", " VOB holds objects from the following views:" ], [ "3y", " Attributes:" ], [ "3z", " FeatureLevel = 2 4." ], [ "3aa", "Determine the replica name (by default is original)" ], [ "3ab", " > cleartool lsreplica" ], [ "3ac", " For VOB replica \"/vobstore/test_vob\":" ], [ "3ad", " 23-Mar.09:36 jdoe replica \"original\" 5." ], [ "3ae", "Change the feature level." ], [ "3af", "* Step 1:" ], [ "3ag", " > cleartool chflevel -replica 3 replica:original@/vobstore/test_vob" ], [ "3ah", " Replica feature level raised to 3." ], [ "3ai", " * Step 2:" ], [ "3aj", " > cleartool chflevel -family 3 vob:/vobstore/test_vob" ], [ "3ak", " cleartool: Warning: Raising the VOB family feature level may make it impossible to move this VOB to servers running an earlier revision of ClearCase and to create MultiSite replicas of this VOB on such servers." ], [ "3al", " Raise VOB family feature level? [no] y" ], [ "3am", " VOB family feature level raised to 3. 6." ], [ "3an", "Describe the VOB to show new feature level:" ], [ "3ao", " > cleartool describe -long vob:." ], [ "3ap", " versioned object base \"/vobstore/test_vob\"" ], [ "3aq", " created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)" ], [ "3ar", " VOB family feature level: 3" ], [ "3as", " VOB storage host:pathname \"host1:/vobstore/test_vob.vbs\"" ], [ "3at", " VOB storage global pathname \"/net/host1/vobstore/test_vob.vbs\"" ], [ "3au", " database schema version: 53" ], [ "3av", " VOB ownership:" ], [ "3aw", " owner ibm.com/jdoe" ], [ "3ax", " group ibm.com/user" ], [ "3ay", " Additional groups:" ], [ "3az", " group ibm.com/other" ], [ "3ba", " VOB holds object from the following views:" ], [ "3bb", " Attributes:" ], [ "3bc", " FeatureLevel = 3" ], [ "3bd", "Review the ClearCase Command Reference Guide on the topic of chflevel (cleartool man chflevel) for more information. RELATED INFORMATION" ], [ "3be", "#About Feature Levels and ClearCase [http://www.ibm.com/support/docview.wss?uid=swg21119269]" ] ]

[ "3c", "3d", "3e", "3l", "3n", "3ae", "3ag", "3aj" ]

[ " PRODUCT DOCUMENTATION\n\nABSTRACT\n This document contains system requirements for WebSphere MQ Hypervisor Edition V7.5 \n\nCONTENT\n \n\nIBM has provided customers with a Software Product Compatibility Reports (SPCR) tool where you can locate and find complete lists of supported operating systems, system requirements, prerequisites, and optional supported software for WebSphere MQ Hypervisor Edition 7.5.\n\nThe SPCR tool links to information about the minimum product levels that must be installed before opening a problem report with IBM WebSphere Message Broker Technical Support. The software versions and any maintenance levels listed in the tool have been explicitly verified as working.\n\n\nSupported System Requirements: \nThe links below are located in the SPCR tool and go directly to the supported operating systems, prerequisites, system requirements, and optional supported software for the specific operating system. \n\n\nWebSphere MQ Hypervisor Edition 7.5 \n\nAix [http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1335198861736&osPlatform=AIX]\nLinux [http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1335198041457&osPlatform=Linux]\n\n\nSPCR tool available for all software products:\nThe generic link to the IBM Software Product Compatibility Reports (SPCR) tool is below. You can access the tool for any product and obtain the supported operating systems, system requirements, and optional supported software for your product version. \n\nClick the link below to reach the front page of SPCR:\nDetailed system requirements for a specific product in SPCR [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/softwareReqsForProduct.html]\n\nThen choose the following options to obtain the supported operating systems, system requirements, and optional supported software for your product version.\n\n1. Select the desired product.\n2. Select the desired version.\n3. Select your operating system.\n\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", " TECHNOTE (FAQ)\n\nQUESTION\n - Scenario 1:\nYou want to install WebSphere MQ 7.1 or 7.5 or 8.0 on AIX and noticed that the fileset \"mqm.ikeyman.rte\" that was available with MQ 6.0 and MQ 7.0 is no longer provided. Instead you see the new fileset \"mqm.gskit.rte\".\n\n- Scenario 2:\nYou want to install WebSphere MQ 7.1 or 7.5 or 8.0 on Linux and notice that the gsk7bas*, gsk7bas64* and MQSeriesKeyMan-7.0* filesets are no longer provided. Instead you see the new fileset: MQSeriesGSKit-7.1.*.rpm\n\n- Scenario 3:\nYou get the following error in AIX, during the installation:\nMISSING REQUISITES: The following filesets are required by one or more of the selected filesets listed above. They are not currently installed and could not be found on the installation media. \nmqm.keyman.rte 7.1.0.0 # Base Level Fileset \n\n\nANSWER\n+++ Scenarios 1 and 2:\nGSKit V8.0 is now integrated with WebSphere MQ version 7.1 and 7.5. \nIn previous versions of WebSphere MQ, GSKit was installed separately into a machine-wide shared directory.\n\nMQ 7.1 does not use a machine-wide shared installation of GSKit: instead it uses a private GSKit installation in the WebSphere MQ installation directory. \n\n+ New filesets in MQ 7.1 and 7.5\n\nThese are the new filesets that are delivered with MQ 7.1 and 7.5 for GSKit and SSL Support (IBM Global Security Kit V8 Certificate and SSL Base Runtime):\n\nAIX: mqm.gskit.rte\nHP-UX: MQSERIES.MQM-GSKIT\nLinux: MQSeriesGSKit-7.1.*.rpm\nSolaris: gskit (file class in the mqm package)\nWindows: Client and Server (installed by default)\n\nThe following filesets from MQ 6 and MQ 7.0 are no longer provided with MQ 7.1 and 7.5:\n\nAIX: mqm.ikeyman.rte\nHP-UX: MQSERIES.MQM-KEYMAN\nLinux: MQSeriesKeyMan-7.0*\nSolaris: keyman (file class in the mqm package)\nCommon: gsk7bas* gsk7bas64* gskcrypt32-8.0* gskssl32-8.0*\n\n+ Renamed GSKit commands \n\nEach WebSphere MQ Version 7.1 installation may use a different GSKit version. \nTo display the version number of GSKit embedded in a particular WebSphere MQ installation, run the dspmqver command from that installation as shown in the following table:\n\nMQ V7.0 command MQ 7.1 or later Purpose\ngsk7cmd runmqckm iKeycmd command-line tool\ngsk7ikm strmqikm iKeyman GUI tool\ngsk7capicmd runmqakm non-Java tool\ngsk7cmd,gsk7ver dspmqver -p 64 display version\ngsk8ver dspmqver -p 64 display version\n\n\n+++ Scenario 3\n\nThis is a known issue and is caused by the previous installation of the mqm.keyman.rte package being present on the system. \n\nThis issue is documented as APAR IV12566 [http://www.ibm.com/support/docview.wss?uid=swg1IV12566]. To resolve this issue, you will need to uninstall the current mqm.keyman.rte package.\n\nThe reason for the error is that mqm.keyman.rte was included with V6 and V7.0 of WMQ but not with 7.1. There is a prerequisite test during the install to make sure that there is not a mixture of filesets from different releases. If mqm.keyman.rte or any other fileset is installed that is not in 7.1 it must be uninstalled first.\n\n\n+ References:\n\n\nWebSphere MQ > Migrating and upgrading > List of changes by version, release, and maintenance level > V7.0.1 to V7.1 changes > GSKit: Changes from GSKit V7.0 to GSKit V8.0 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77159_.htm?cp=SSFKSJ_7.1.0%2F1-0-3-2-9-2&lang=en]\nGSKit: Commands renamed [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77159_.htm?cp=SSFKSJ_7.1.0%2F1-0-3-2-9-2&lang=en]\n\n\nWebSphere MQ > Installing > Installing WebSphere MQ > Planning your installation > Choosing what to install\nWebSphere MQ components for UNIX and Linux [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/zi00920_.htm?lang=en]\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ MQSeries", " DOWNLOADABLE FILES\n\nABSTRACT\n This document describes how to download IBM MQ Version 8.0 Interim Feature Release (IFR)1. This manufacturing level is equivalent to MQ Version 8.0.0.2/3, but excludes IBM MQ V8.0 \n\nDOWNLOAD DESCRIPTION\n\n\n\nTAB NAVIGATION\n * Overview [http://www.ibm.com/support/docview.wss?uid=swg24037501]- selected tab,\n * MQ V8.0.0.9 [http://www.ibm.com/support/docview.wss?uid=swg24044732]\n * MQ V8.0.0.8 [http://www.ibm.com/support/docview.wss?uid=swg24044322]\n * MQ V8.0.0.5 [http://www.ibm.com/support/docview.wss?uid=swg24042095]\n * MQ V8.0.0.4 [http://www.ibm.com/support/docview.wss?uid=swg24040022]\n * MQ V8.0 IFR1 (V8.0.0.2/3) [http://www.ibm.com/support/docview.wss?uid=swg24040040]\n * MQ V8.0.0.2/3 [http://www.ibm.com/support/docview.wss?uid=swg24040027]\n * MQ V8.0.0.0/1 [http://www.ibm.com/support/docview.wss?uid=swg24040028]\n\nContents For IBM MQ Version 8.0 IFR1, this section provides the part number and description of each eAssembly, followed by a list of the installation images available in the eAssembly. This manufacturing level is equivalent to MQ Version 8.0.0.2/3. Note that the IBM MQ V8.0 Sterling for Multiplatform Multilingual eAssemblies are not included in MQ V8.0 IFR1. Note also that the only difference between V8.0.0.2 and V8.0.0.3 is that, for V8.0.0.3, an extra eImage is added for MQ Advanced V8.0.0.3 Virtual System Pattern Type for IBM PureApplication System Multilingual.\n\nDownloading the release Sign in to Passport Advantage [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]. For the full release, search for part number CRW5XML. If you don't need the full release, you can instead search for any of the eImages that make up the full release. The eImage part numbers are given in the following table.\n\n\nIBM MQ V8.0 IFR1 for Multiplatform Multilingual eAssembly\n\nPart Number Description CRW5XML MQ V8.0 IFR1 for Multiplatform Multilingual eAssembly CN2BYML MQ V8.0 Quick Start Guide Multiplatform Multilingual eImage CN5G6ML MQ for AIX V8.0 IFR1 Multilingual eImage CN5G7ML MQ for HP-UX on Itanium V8.0 IFR1 Multilingual eImage CN5G8ML MQ for IBMi V8.0 IFR1 Multilingual eImage CN5G9ML MQ for Linux on POWER V8.0 IFR1 Multilingual eImage CN5GPML MQ for Linux on LE Power V8.0 IFR1 Multilingual elmage CN5GAML MQ for Linux on System z 64bit V8.0 IFR1 Multilingual eImage CN5GBML MQ for Linux on x86 64 V8.0 IFR1 Multilingual eImage CN5GDML MQ for Solaris on SPARC V8.0 IFR1 Multilingual eImage CN5GEML MQ for Solaris on x86 64 V8.0 IFR1 Multilingual eImage CN5GCML MQ for Windows V8.0 IFR1 Multilingual eImage CN6UUML MQ Advanced V8.0.0.3 Virtual System Pattern Type for IBM PureApplication System Multilingual eImage CN5GFML MQ Client for AIX V8.0 IFR1 Multilingual eImage CN5GGML MQ Client for HP-UX on Itanium V8.0 IFR1 Multilingual eImage CN5GHML MQ Client for IBMi V8.0 IFR1 Multilingual eImage CN5GIML MQ Client for Linux on POWER V8.0 IFR1 Multilingual eImage CN5GQML MQ Client for Linux on LE Power V8.0 IFR1 Multilingual elmage CN5GJML MQ Client for Linux on System z 64 bit V8.0 IFR1 Multilingual eImage CN5GKML MQ Client for Linux on x86 32bit V8.0 IFR1 Multilingual eImage CN5GRML MQ Client for Linux on x86 64 V8.0 IFR1 Multilingual eImage CN5GMML MQ Client for Solaris on SPARC V8.0 IFR1 Multilingual eImage CN5GNML MQ Client for Solaris on x86 64 V8.0 IFR1 Multilingual eImage CN5GLML MQ Client for Windows 32-bit V8.0 IFR1 Multilingual eImage CN5GSML MQ Client for Windows 64-bit V8.0 IFR1 Multilingual eImage CN5PHML Managed File Transfer Agent V7.5 IFR2 for IBM 4690 Operating System Multilingual eImage \nOther Fix Central resources A number of MQ V8.0.0.2/3 components are also made available on Fix Central for ease of download. Here are links to the available components:\n\n * The IBM MQ V8.0.0.2 Resource Adapter [https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=All&function=fixId&fixids=8.0.0.2-WS-MQ-Java-InstallRA&useReleaseAsTarget=true&includeSupersedes=0] for use with any JEE 7.0 compliant application server\n * The IBM MQ V8.0.0.3 Resource Adapter [https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.3&platform=All&function=fixId&fixids=8.0.0.3-WS-MQ-Java-InstallRA&useReleaseAsTarget=true&includeSupersedes=0] for use with any JEE 7.0 compliant application server\n * The IBM MQ V8.0.0.2 C clients [https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=All&function=fixId&fixids=8.0.0.2-WS-MQC-SolarisX64,8.0.0.2-WS-MQC-SolarisSparc64,8.0.0.2-WS-MQC-LinuxS390X,8.0.0.2-WS-MQC-AixPPC64,8.0.0.2-WS-MQC-HpuxIA64,8.0.0.2-WS-MQC-LinuxX64,8.0.0.2-WS-MQC-Win64,8.0.0.2-WS-MQC-IBM_i,8.0.0.2-WS-MQC-LinuxPPC64LE&useReleaseAsTarget=true&includeSupersedes=0]\n * The IBM MQ V8.0.0.3 C clients [https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.3&platform=All&function=fixId&fixids=8.0.0.3-WS-MQC-SolarisX64,8.0.0.3-WS-MQC-SolarisSparc64,8.0.0.3-WS-MQC-LinuxS390X,8.0.0.3-WS-MQC-AixPPC64,8.0.0.3-WS-MQC-HpuxIA64,8.0.0.3-WS-MQC-LinuxX64,8.0.0.3-WS-MQC-Win64,8.0.0.3-WS-MQC-IBM_i,8.0.0.3-WS-MQC-LinuxPPC64LE&useReleaseAsTarget=true&includeSupersedes=0]\n * The IBM MQ V8.0.0.2 JMS and Java client [https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.2&platform=All&function=fixId&fixids=8.0.0.2-WS-MQ-Install-Java-All&useReleaseAsTarget=true&includeSupersedes=0]\n * The IBM MQ V8.0.0.3 JMS and Java client [https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm/WebSphere/WebSphere+MQ&release=8.0.0.3&platform=All&function=fixId&fixids=8.0.0.3-WS-MQ-Install-Java-All&useReleaseAsTarget=true&includeSupersedes=0]\n\n\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", " PRODUCT DOCUMENTATION\n\nABSTRACT\n This document contains system requirements for WebSphere MQ V8.0 and a note about IBM WebSphere MQ Advanced entitlement. \n\nCONTENT\nIBM has provided customers with a Software Product Compatibility Reports (SPCR) tool where you can locate and find complete lists of supported operating systems, system requirements, prerequisites, and optional supported software for WebSphere MQ 8.0. \n\nRHEL Compatible OS. Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V6. Unless stated otherwise, WebSphere MQ has not been specifically tested in such compatible environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the linux environment itself. If issues arise that are related to the compatible linux environment, the user may need to contact the linux environment vendor for support, or the issue may need to be recreated inside an environment tested by IBM in order to receive WebSphere MQ support. \n\nVirtualization. Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere MQ. Unless stated elsewhere in the system requirements WebSphere MQ has not been specifically tested in virtualization environments. \n\nWebSphere MQ support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself. \n\nPlease also refer to:\nWebSphere MQ's support position on Virtualization, low-level hardware, file systems on networks and high availability. [http://www.ibm.com/support/docview.wss?uid=swg21392025]\n\n\nThe SPCR tool links to information about the minimum product levels that must be installed before opening a problem report with IBM WebSphere MQ Technical Support. The software versions and any maintenance levels listed in the tool have been explicitly verified as working.\n\n\nSupported System Requirements: \nThe links below are located in the SPCR tool and go directly to the supported operating systems, prerequisites, system requirements, and optional supported software for the specific operating system. \n\n\nWebSphere MQ 8.0\n\nBy Operating System\nAIX [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=AIX]\nHP [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=HP]\nIBM i [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=IBM%20i]\nLinux [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Linux]\n4690 (Managed File Transfer Agent Only) [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Other]\nSolaris [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Solaris]\nWindows [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Windows]\nz/OS [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=z/OS]\n\nBy Component\nMQ Advanced Message Security [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568DDB101AEF11E38F7D228059AF1569]\nMQ Client [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_569814401AEF11E38F7D228059AF1569]\nMQ Explorer [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Desktop_56A6BA401AEF11E38F7D228059AF1569]\nMQ Managed File Transfer Agent [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_56910F601AEF11E38F7D228059AF1569]\nMQ Managed File Transfer Service [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568AA6C01AEF11E38F7D228059AF1569]\nMQ Queue Manager [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568C06501AEF11E38F7D228059AF1569]\nMQ Resource Adapter [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_5685EBD01AEF11E38F7D228059AF1569]\nMQ Telemetry Server [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568CF0B01AEF11E38F7D228059AF1569]\n\nSPCR tool available for all software products:\nThe generic link to the IBM Software Product Compatibility Reports (SPCR) tool is below. You can access the tool for any product and obtain the supported operating systems, system requirements, and optional supported software for your product version. \n\nClick the link below to reach the front page of SPCR:\nDetailed system requirements for a specific product in SPCR [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/softwareReqsForProduct.html]\n\nThen choose the following options to obtain the supported operating systems, system requirements, and optional supported software for your product version.\n\n1. Select the desired product.\n2. Select the desired version.\n3. Select your operating system.\n\n----------------------------------------------------------------------------------------------------------------\nIBM WebSphere MQ Advanced entitlement\n\nIBM WebSphere MQ Advanced and IBM WebSphere MQ Advanced Idle Standby grants entitlement to the following components: \n\n * IBM WebSphere MQ \n * IBM WebSphere Advanced Message Security \n * IBM WebSphere Managed File Transfer Service \n * IBM WebSphere MQ Telemetry \n\nIBM WebSphere MQ Advanced for Developers grants entitlement to the following components: * IBM WebSphere MQ \n * IBM WebSphere Advanced Message Security \n * IBM WebSphere Managed File Transfer Service \n * IBM WebSphere MQ Telemetry \n * IBM WebSphere Managed File Transfer Managed Endpoint\n\n----------------------------------------------------------------------------------------------------------------", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Why is my Guardium System Backup Config file so large ? \n\nSYMPTOM\nThe SQLGUARD_CONFIG.tgz file generated by the System Backup config process is larger than expected, sometimes in the order of hundreds of MB or greater.\n\n\nCAUSE\nThe System Backup config file includes various configuration files including dumps from a subset of tables within the database. If any of these tables become excessively large it can affect the size of the config backup file. The table most likely to increase the config file size is REPORT_RESULT_DATA_ROW which contain audit results that have not been signed or reviewed\n\nDIAGNOSING THE PROBLEM\nIn v8.01 or above run the following \"cli\" command to establish if REPORT_RESULT_DATA_ROW is one of the largest tables in the database:\n\n\nsupport show db-top-tables all \n\n \n\nIn v8.0 or below seek guidance from Technical Support. \n\n\n\n\n\nRESOLVING THE PROBLEM\nPurge the REPORT_RESULT_DATA_ROW table to reduce size. \n\nAudit reports are only purged form the REPORT_RESULT_DATA_ROW table as part of the normal purge process if :- \n\n * the \"Keep for a minimum of \" value has been satisfied and/or the audit report has been reviewed or signed-off as per the \"Action Required\" setting. \n\n \n\nBoth the above settings can be found by Tools -> Config & Control -> Audit Process Builder \n\nFor any of the individual processes listed , the Audit Process Definition and Receiver Table sections will show the settings" ]

[ [ "3a", " PRODUCT DOCUMENTATION ABSTRACT" ], [ "3b", " This document contains system requirements for WebSphere MQ V8.0 and a note about IBM WebSphere MQ Advanced entitlement. CONTENT" ], [ "3c", "IBM has provided customers with a Software Product Compatibility Reports (SPCR) tool where you can locate and find complete lists of supported operating systems, system requirements, prerequisites, and optional supported software for WebSphere MQ 8.0." ], [ "3d", "RHEL Compatible OS." ], [ "3e", "Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V6." ], [ "3f", "Unless stated otherwise, WebSphere MQ has not been specifically tested in such compatible environments." ], [ "3g", "WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the linux environment itself." ], [ "3h", "If issues arise that are related to the compatible linux environment, the user may need to contact the linux environment vendor for support, or the issue may need to be recreated inside an environment tested by IBM in order to receive WebSphere MQ support. Virtualization." ], [ "3i", "Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere MQ." ], [ "3j", "Unless stated elsewhere in the system requirements WebSphere MQ has not been specifically tested in virtualization environments." ], [ "3k", "WebSphere MQ support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself." ], [ "3l", "Please also refer to:" ], [ "3m", "WebSphere MQ's support position on Virtualization, low-level hardware, file systems on networks and high availability. [http://www.ibm.com/support/docview.wss?uid=swg21392025]" ], [ "3n", "The SPCR tool links to information about the minimum product levels that must be installed before opening a problem report with IBM WebSphere MQ Technical Support." ], [ "3o", "The software versions and any maintenance levels listed in the tool have been explicitly verified as working." ], [ "3p", "Supported System Requirements:" ], [ "3q", "The links below are located in the SPCR tool and go directly to the supported operating systems, prerequisites, system requirements, and optional supported software for the specific operating system." ], [ "3r", "WebSphere MQ 8.0" ], [ "3s", "By Operating System AIX [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=AIX] HP [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=HP]" ], [ "3t", "IBM i [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=IBM%20i] Linux [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Linux]" ], [ "3u", "4690 (Managed File Transfer Agent Only) [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Other] Solaris [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Solaris] Windows [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Windows] z/OS [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=z/OS] By Component" ], [ "3v", "MQ Advanced Message Security [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568DDB101AEF11E38F7D228059AF1569]" ], [ "3w", "MQ Client [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_569814401AEF11E38F7D228059AF1569]" ], [ "3x", "MQ Explorer [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Desktop_56A6BA401AEF11E38F7D228059AF1569]" ], [ "3y", "MQ Managed File Transfer Agent [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_56910F601AEF11E38F7D228059AF1569]" ], [ "3z", "MQ Managed File Transfer Service [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568AA6C01AEF11E38F7D228059AF1569]" ], [ "3aa", "MQ Queue Manager [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568C06501AEF11E38F7D228059AF1569]" ], [ "3ab", "MQ Resource Adapter [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_5685EBD01AEF11E38F7D228059AF1569]" ], [ "3ac", "MQ Telemetry Server [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568CF0B01AEF11E38F7D228059AF1569]" ], [ "3ad", "SPCR tool available for all software products:" ], [ "3ae", "The generic link to the IBM Software Product Compatibility Reports (SPCR) tool is below." ], [ "3af", "You can access the tool for any product and obtain the supported operating systems, system requirements, and optional supported software for your product version." ], [ "3ag", "Click the link below to reach the front page of SPCR:" ], [ "3ah", "Detailed system requirements for a specific product in SPCR [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/softwareReqsForProduct.html]" ], [ "3ai", "Then choose the following options to obtain the supported operating systems, system requirements, and optional supported software for your product version. 1." ], [ "3aj", "Select the desired product. 2." ], [ "3ak", "Select the desired version. 3." ], [ "3al", "Select your operating system. ----------------------------------------------------------------------------------------------------------------" ], [ "3am", "IBM WebSphere MQ Advanced entitlement" ], [ "3an", "IBM WebSphere MQ Advanced and IBM WebSphere MQ Advanced Idle Standby grants entitlement to the following components:" ], [ "3ao", " * IBM WebSphere MQ" ], [ "3ap", " * IBM WebSphere Advanced Message Security" ], [ "3aq", " * IBM WebSphere Managed File Transfer Service" ], [ "3ar", " * IBM WebSphere MQ Telemetry" ], [ "3as", "IBM WebSphere MQ Advanced for Developers grants entitlement to the following components: * IBM WebSphere MQ" ], [ "3at", " * IBM WebSphere Advanced Message Security" ], [ "3au", " * IBM WebSphere Managed File Transfer Service" ], [ "3av", " * IBM WebSphere MQ Telemetry" ], [ "3aw", " * IBM WebSphere Managed File Transfer Managed Endpoint ----------------------------------------------------------------------------------------------------------------" ] ]

[ "3b", "3c", "3r", "3s", "3t", "3u", "3v", "4y", "4z" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When trying to create or open a project in a web browser using the Cloud version of Studio (Studio Cloud) , Cast Iron v6.x attempts to launch Web Start Studio Cloud under the covers but it fails and produces an error. \n\nCAUSE\nThe \"Unable to launch application\" error associated with the exception:\ncom.sun.deploy.net.FailedDownloadException: Unable to load resource: \nhttps://cloud2.castiron.com/flash/design/com.approuter.studio.launcher-1.0.0.jar\n\ncould possibly occur because the Windows machine has Java v1.7 JRE installed and is using that version of Java to try to launch the Cast Iron v6.x Web Start Studio Cloud instead of using Java v1.6 JRE. Cast Iron v6.x Web Start Studio Cloud does not support Java v1.7.\n\n\nDIAGNOSING THE PROBLEM\nA snippet of the exception stack trace that occurs is similar to the following: \n\n \ncom.sun.deploy.net.FailedDownloadException: Unable to load resource: https://cloud2.castiron.com/flash/design/com.approuter.studio.launcher-1.0.0.jar \n\n\nat com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getResource(Unknown Source) \nat com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source) \nat java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) \nat java.util.concurrent.FutureTask.run(Unknown Source) \nat java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) \nat java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) \nat java.lang.Thread.run(Unknown Source) \n\nand wrapped exception:\n\njavax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name \n\nat sun.security.ssl.ClientHandshaker.handshakeAlert(Unknown Source) \nat sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source) \nat sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) \nat sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) \nat sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) \nat sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source) \nat sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) \nat sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) \nat sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source) \nat com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source) \nat com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source) \nat com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source) \nat com.sun.deploy.net.DownloadEngine.getResource(Unknown Source) \nat com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source) \nat java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) \nat java.util.concurrent.FutureTask.run(Unknown Source) \nat java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) \nat java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) \nat java.lang.Thread.run(Unknown Source)\n\n\nRESOLVING THE PROBLEM\nTo resolve the exception and launch Cast Iron v6.x Web Start Studio Cloud, uninstall the Java v1.7 JRE from the Windows machine and browser. Once the Java v1.7 JRE is successfully removed from the machine you can then install Java v1.6 JRE and try to launch Cast Iron v6.x Web Start Studio Cloud again. \n\nJava v1.6 JRE is the supported Java runtime to be used with Cast Iron v6.x Studio Cloud.", "DB2 LUW v10.1 FP1 Data Studio 3.1.1 FLASH (ALERT)\n\nABSTRACT\n The Administration Explorer and Data Source Explorer from Data Studio 3.1.1 displays the incorrect database version. When connecting to DB2 for Linux, UNIX, and Windows Version 10.1 FP1, the database information is incorrectly displayed as (DB2 for Linux, UNIX, and Windows V9.1). \n\nCONTENT\n \n\nSymptom:\nSymptoms include missing functionality and missing features in the Administration Explorer and Data Source Explorer.\n\nThe Admin Explorer and Data Source Explorer incorrectly displays a DB2 V10.1 database version as DB2 for Linux, UNIX, and Windows V9.1 \nExample:\n[/support/docview.wss?uid=swg21610862&amp;aid=1]\n\nMany behavior and catalog changes were made from DB2 V9.1 to DB2 V10.1 FP1. Items were renamed, moved and removed. Because the database is incorrectly displayed as V9.1, Data Studio checks for information in places where it would be, if the database were V9.1. But of course it is actually DB2 V10.1 FP1 or later. So there might be possible problems when loading objects from the database catalog in the form of missing information, failures or errors. Another example would be delta ddl and generate ddl. They would be based on V9.1. objects, which is incorrect.\n\n\nCause:\nDuring the database connection establishment, Data Studio 3.1.1 fails to properly classify the correct database version. When that happens, Data Studio falsely thinks that it is a DB2 V9.1 connection.\n\n\nEnvironment:\nAll users of Data Studio 3.1.1 connecting to a database on \nDB2 Version 10.1 fix pack 1 (10.1.0.1) or newer on Linux, UNIX and Windows.\nThe following products are affected: \n\n * Data Studio 3.1.1 \n * Optim Query Workload Tuner 3.1.1 \n * InfoSphere Data Architect 8.1 \n * InfoSphere Warehouse Design Studio V10.1\n\n\n\nDiagnosing the problem: \nUse the following information to validate if you are encountering this issue. \n 1. Connect to a DB2 LUW V10.1 FP1 or later database using Data Studio 3.1.1 \n 2. Database version information is displayed as V9.1 instead of V10.1 in the Admin Explorer and the Data Source Explorer \n\n\n\nResolving the problem: \nA temporary fix can be implemented by obtaining a patch for RTC 14510 \nThe patches are packaged with IBM Installation Manager. \nInstallation instructions are in the readme.txt included with the patch. \nDownload the corresponding patch for your product: \nProduct Version Download Data Studio 3.1.1 Fix Central [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Information+Management&product=ibm/Information+Management/IBM+Data+Studio&release=3.1.1&platform=All&function=all] Optim Query Workload Tuner 3.1.1 Fix Central [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Information+Management&product=ibm/Information+Management/IBM+Data+Studio&release=3.1.1&platform=All&function=all] InfoSphere Data Architect 8.1 Fix Central [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Information+Management&product=ibm/Information+Management/Infosphere+Data+Architect&release=8.1.0.0&platform=All&function=all] InfoSphere Warehouse Design Studio 10.1 Contact the IBM InfoSphere \nWarehouse support team to obtain a patch \nfor resolving this problem. \n\n\nTechnical Support \nIn the United States and Canada dial 1-800-IBM-SERV \nView support contacts for other countries [http://www.ibm.com/planetwide/] \nOpen a Service Request [https://www.ibm.com/support/servicerequest/] with Technical Support \n\n\nMy Notifications \nSign-up to receive e-mail notification of changes to this document. 1. Sign in [http://www.ibm.com/support/mynotifications] to My Notifications \n 2. select Subscribe tab \n 3. select \"Information Management\" from the Software column \n 4. select the check box for \"DB2 for Linux, UNIX and Windows\" \n click the Continue button. \n 5. select the check box for \"Flashes\" and all other document types\n click the Submit button.\n\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Information Management DB2 for Linux- UNIX and Windows AIX, HP-UX, Linux, Solaris, Windows 10.1 Information Management InfoSphere Optim Query Workload Tuner for DB2 for Linux- UNIX and Windows 3.1.1 Information Management InfoSphere Data Architect 8.1 Information Management InfoSphere Warehouse DWE - Design Studio 10.1", " TECHNOTE (FAQ)\n\nQUESTION\n We are able to install Data Studio (DS) 4.1.2 successfully but unable to uninstall the \nexisting Data Studio 3.1.1. When uninstall Data Studio 3.1.1 from Control Panel, it \nraises an error message pop-up window and can not uninstall it. Here is the message:\n\n+-------------------------------------------------------------------------\n| Java Virtual Machine Launcher\n+-------------------------------------------------------------------------\n| X Could not find the main class: com.zerog.lax.LAX. Program will exit.\n+-------------------------------------------------------------------------\n\nHow can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error?\n\n\nCAUSE\nIt is an known behavior/limitation. \n\nANSWER\nIt may be happened where two versions Data Studio 3.1.1 and 4.1.2 installed machine. \n\nHere is an workaround. Please try to uninstall all products including Install Manager \n(IM) then reinstall IM and Data Studio 4.1.2. Below are detailed steps:\n\n1. Use IM to uninstall as many packages as possible.\n\n2. Identify the packages that are still installed, and manually clean \nthem up.\n\nExample on Windows:\n- C:\\Program Files\\IBM\\{IBMIMShared | SDPShared}\n\n3. Delete IBM Installation Manager.\n\nExample on Windows:\n- Delete the IM install directory:\nC:\\Program Files\\IBM\\Installation Manager\\\n- Delete the AppData directory (IM Agent Data):\nWindows 7: C:\\ProgramData\\IBM\\Installation Manager\n- Delete the Windows registry (regedit) entry : \nHKEY_LOCAL_MACHINE\\SOFTWARE\\IBM\\Installation Manager\n- re-install IM\n\n4. Reinstall DS 4.1.2 and other products.\n\nNote:\nThis behavior might be changed without notice in the future. We can confirm whether this technote\nis valid or not by following above.\nPlease contact your Sales Rep to submit a potential design change towards a future release.\nOr please open a ticket, Request For Enhancement at https://www.ibm.com/developerworks/rfe/ [https://www.ibm.com/developerworks/rfe/]", "OMPEDB2XE FLASH (ALERT)\n\nABSTRACT\n This document describes how to enable integrated query workload tuning support in OMEGAMON XE for Db2 Performance Expert V540 for Db2 11 or Db2 12 originated queries when using the integrated Infosphere Optim Performance Manager UI (commonly referred to as Extended Insight or the SQL Dashboard) or the PE Client Java GUI. \n\nCONTENT\nThe purpose of this flash is to inform technical support personnel how to get query workload tuning support in OMEGAMON XE for Db2 Performance Expert V540 for Db2 11 or Db2 12 originated queries when using the integrated Infosphere Optim Performance Manager UI (commonly referred to as Extended Insight or the SQL Dashboard) or the PE Client Java GUI. (See Entitlement below.) \nProblem Symptoms: Customer could experience the following trying to call the Data Studio Query Workload Tuner integration points from Extended Insight, the SQL Dashboard, or the PE Client: \n\n * The Data Studio UI freezes when trying to pass a query workload to DataStudio 4.1.2. \n * The only resolution is to kill the Java process running DataStudio. \n * This happens with Db2 11 statements as well as Db2 12.\n\n\nSolution 1. Download and install Data Studio 4.1.3 if not already installed. Note that older versions of Data Studio cannot be migrated (overlayed); 4.1.3 needs to be a new installation \n 2. Burn the LAK (License Activation Kit) you received from IBM to DVD and run the LAK. Extracting the .iso file also works e.g. using 7zip. [See below for Entitlement]\n\n\nThis link describes how to install LAK on Data Studio: https://www.ibm.com/support/knowledgecenter/en/SS7LB8_4.1.1/com.ibm.datatools.qrytune.installconfig.doc/topics/ioqwt411_installwithim.html [https://www.ibm.com/support/knowledgecenter/en/SS7LB8_4.1.1/com.ibm.datatools.qrytune.installconfig.doc/topics/ioqwt411_installwithim.html] \n\n*** Be advised that even though the License Activation Kit install Welcome message says Version 4.1.2, that it is still applicable to 4.1.3 \n[/support/docview.wss?uid=swg22014252&aid=1] [/support/docview.wss?uid=swg22014252&aid=1] \n\nThis link describes how to activate full set of tuning features (after LAK is installed): https://www.ibm.com/support/knowledgecenter/en/SS7LB8_4.1.1/com.ibm.datatools.qrytune.installconfig.doc/topics/ioqwt411_top.html [https://www.ibm.com/support/knowledgecenter/en/SS7LB8_4.1.1/com.ibm.datatools.qrytune.installconfig.doc/topics/ioqwt411_top.html] \n\nEntitlement OMEGAMON XE for Db2 Performance Expert/Monitor on z/OS (5655-W37 / 5655-W38) customers can receive on request a License Activation Kit (LAK) to be used together with Data Studio V4.1.3 if they have licensed any of the following: * IBM Db2 Performance Solution Pack V1.4 (5655-E74) or higher \n * IBM Db2 SQL Performance Solution Pack V1 (5655-SQ1) or higher \n * IBM Db2 Query Workload Tuner for z/OS V5 (5655-AB4) or higher for the purposes of performing SQL tuning via launch of IBM Data Studio from the OMEGAMON XE for Db2 PE SQL Dashboard, the Extended Insight Analysis Dashboard, or the PE client GUI. \n\n\nTo receive a copy of the License Activation Kit, open a Service Request with IBM.", "disc; disc41relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n While running Column Analysis, the task completed with errors: \n\nThe value of a host variable in the EXECUTE or OPEN statement is too large \n\nSYMPTOM\nThe issue was replicated in DB2 Express version 9.7. \n\n\nENVIRONMENT\nDiscovery Server, Discovery Engine, Discovery Studio version 4.1.1.068\n\nRESOLVING THE PROBLEM\nThe issue occurs while running text file for source data for InfoSphere Discovery version 4.1.1.068 and using DB2 Express version 9.7 for staging and repository. For InfoSphere Discovery 4.1.1.068, we only certify and support DB2 version 9.1 for staging and repository. Uninstall DB2 Express version 9.7 and install DB2 9.1 to resolve the issue.\n\n\n\nCross reference information Segment Product Component Platform Version Edition Information Management InfoSphere Discovery Discovery Studio Windows 4.1.1 Enterprise" ]

[ [ "2a", " TECHNOTE (FAQ) QUESTION" ], [ "2b", " We are able to install Data Studio (DS) 4.1.2 successfully but unable to uninstall the" ], [ "2c", "existing Data Studio 3.1.1." ], [ "2d", "When uninstall Data Studio 3.1.1 from Control Panel, it" ], [ "2e", "raises an error message pop-up window and can not uninstall it." ], [ "2f", "Here is the message: +-------------------------------------------------------------------------" ], [ "2g", "| Java Virtual Machine Launcher +-------------------------------------------------------------------------" ], [ "2h", "| X Could not find the main class: com.zerog.lax.LAX." ], [ "2i", "Program will exit. +-------------------------------------------------------------------------" ], [ "2j", "How can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error? CAUSE" ], [ "2k", "It is an known behavior/limitation. ANSWER" ], [ "2l", "It may be happened where two versions Data Studio 3.1.1 and 4.1.2 installed machine." ], [ "2m", "Here is an workaround." ], [ "2n", "Please try to uninstall all products including Install Manager" ], [ "2o", "(IM) then reinstall IM and Data Studio 4.1.2." ], [ "2p", "Below are detailed steps: 1." ], [ "2q", "Use IM to uninstall as many packages as possible. 2." ], [ "2r", "Identify the packages that are still installed, and manually clean them up." ], [ "2s", "Example on Windows:" ], [ "2t", "- C:\\Program Files\\IBM\\{IBMIMShared | SDPShared} 3." ], [ "2u", "Delete IBM Installation Manager." ], [ "2v", "Example on Windows:" ], [ "2w", "- Delete the IM install directory:" ], [ "2x", "C:\\Program Files\\IBM\\Installation Manager\\" ], [ "2y", "- Delete the AppData directory (IM Agent Data):" ], [ "2z", "Windows 7: C:\\ProgramData\\IBM\\Installation Manager" ], [ "2aa", "- Delete the Windows registry (regedit) entry : HKEY_LOCAL_MACHINE\\SOFTWARE\\IBM\\Installation Manager" ], [ "2ab", "- re-install IM 4." ], [ "2ac", "Reinstall DS 4.1.2 and other products. Note:" ], [ "2ad", "This behavior might be changed without notice in the future." ], [ "2ae", "We can confirm whether this technote" ], [ "2af", "is valid or not by following above." ], [ "2ag", "Please contact your Sales Rep to submit a potential design change towards a future release." ], [ "2ah", "Or please open a ticket, Request For Enhancement at https://www.ibm.com/developerworks/rfe/ [https://www.ibm.com/developerworks/rfe/]" ] ]

[ "2b", "2c", "2d", "2e", "2f", "2g", "2h", "2i", "2l", "2m", "2n", "2o", "2p", "2q", "2r", "2s", "2t", "2u", "2v", "2w", "2x", "2y", "2z", "2aa", "2ab", "2ac", "2ad", "2ae", "2ag", "2ah" ]

[ "SQLCODE 206 -206 SQL0206 SQL0206N DSM incompatible db2level fixpack fix pack db2iupdt TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Data Server Manager log files are full of SQLCODE=-206 \"<name> is not valid in the context where it\nis used.\" error \n\nSYMPTOM\nThe symptoms can vary depending on each installation. \n\nMost common scenario, DSM shows Data Pending status for the monitored database.\n\n\nCAUSE\nWhen you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release. \n\nBut that command does not necessarily update the database system catalog to support the new fix pack that you have installed.\nMeaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level. \n\n\n\nDIAGNOSING THE PROBLEM\nOne way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database: \n\ndb2 \"select versionnumber from sysibm.sysversions order by 1 desc\" \n\nIf the results is showing a lower level than the ones DSM supports, that means your environment\nis not supported, and you are getting the SQLCODE=-206 error.\n\nTo verify what are the DB2 levels supported by DSM, please refer to the links below:\n- System requirements for IBM Data Server Manager, version 1.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27045176]\n- System requirements for IBM Data Server Manager, version 2.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048115]\n\n\n\nRESOLVING THE PROBLEM\nRun the db2updvnn command according to the db2level of your monitored database: \n\n- For DB2 V9.7 run db2updv97 [https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.1 run db2updv10 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.5 run db2updv105 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V11.1 run db2updv111 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command", "DSM SQLCODE=-206 T1.TOTAL_RQST_TIME TOTAL_ROLLBACK_PROC_TIME SQL0206 migration HealthSnapshotLogger TECHNOTE (FAQ)\n\nQUESTION\n Why is Data Server Manager (DSM) showing the following error in HealthSnapshotLogger file, after installing/migrating DSM to a newer version:\n\"T1.TOTAL_RQST_TIME\" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.69.56 \n\nCAUSE\nTwo new columns have been added to the IBMOTS.WORKLOAD_STATS table in DSM Repository Database after V1.1.2.1:\n- TOTAL_ROLLBACK_PROC_TIME bigint\"\n- TOTAL_RQST_TIME bigint\"\n\nFor some reason the migration process did not update the table successfully.\n\n\nANSWER\nTo fix the issue, stop DSM, connect to the DSM Repository Database using the DSM instance owner, and run the following DB2 commands: \n\n- db2 \"alter table IBMOTS.WORKLOAD_STATS add column TOTAL_ROLLBACK_PROC_TIME bigint\"\n- db2 \"alter table IBMOTS.WORKLOAD_STATS add column TOTAL_RQST_TIME bigint\"\n\nRestart DSM.", "BCU; Balanced Warehouse; software level; firmware level; version; Smart Analytics System; balanced configuration unit; ISAS TECHNOTE (FAQ)\n\nQUESTION\n How do I manually install a DB2 special build or DB2 fix pack on an IBM Smart Analytics System? \n\nANSWER\nIf your system is installed with the IBM Smart Analytics System Control Console software, use an IBM Smart Analytics System fix pack available on Fix Central to update your software stack. If the DB2 fix you need is not available in an IBM Smart Analytics System fix pack or your system does not have the control console software installed, use the instructions in this document to manually install a DB2 special build or DB2 fix pack on your IBM Smart Analytics System. \nBefore you begin\nThis document uses the following variables. Substitute the appropriate values for your environment. \n\n\n\nVariable name Example name to use Notes MGMT, ADMIN, ADMIN_ALL, DATA, STANDBY [/support/docview.wss?uid=swg21502587&amp;aid=1] These variables refer to the role of the different servers. Replace each variable with the appropriate host names from your environment. * MGMT = management node used to manage all nodes in the cluster. \n * ADMIN = administration node or NODE0000 or primary coordinator node. \n * ADMIN_ALL = all coordinator nodes \n * DATA = all data nodes in the core warehouse \n * STANDBY = all standby nodes the core warehouse\n\nBCU_share * All AIX systems: /BCU_share \n * 5600 systems: /BCU_share \n * D5000 and D5100: /csminstall\n\n[/support/docview.wss?uid=swg21502587&amp;aid=1] install_path * AIX systems: /usr \n * Linux systems: /opt\n\nThe installation path is operating-system dependent. You can use the db2level command to validate the current installation path. hostname bcudata001 Use the appropriate server host name. date 20110801 Use the format YYYYMMDD, where YYYY represents a 4-digit year, MM represents a 2-digit month, and DD represents a 2-digit month. new_path_to_fixpack DB2_97fp1 Use a name that clearly labels the directory with the product, version, and build number (if you are applying a special build). If you need to install the product in the future, this naming convention will allow you to easily identify the product and correct version to install. nlpack_path NLPack_97fp1 Use a name that clearly identifies the national language pack content and the version contained in the directory. instance_user db2inst1 The name of the DB2 instance owner. fenced_user db2fenc1 The name of the DB2 fenced user. You can find the fenced user name and group by looking at the owner and group of the following file:\nls -l ~<instance_user>/sqllib/adm/.fenced \nNote: You can use any utility you prefer to issue remote commands to the servers in the cluster. If you choose not to use a remote command utility, you can log on to each server and run the commands locally. \n\nProcedure \n1. Mount the installation media directory from the management node * \n * For IBM Smart Analytics System 7600 or 7700, Balanced Warehouse E7100, or IBM Smart Analytics System 5600 environments, issue the following command as root on ADMIN_ALL, DATA, and STANDBY nodes: * \n * \n * \n \n For Balanced Warehouse D5000 or D5100 environments, issue the following command as root on ADMIN_ALL, DATA, and STANDBY nodes: * \n \n \n * Note: In newer configurations, the /BCU_share directory has replaced the /csminstall directory. If you mounted the /csminstall directory, substitute /csminstall for /BCU_share as you follow the instructions in this document. Alternatively, you can create a symbolic link. \n * \n * \n * ln -s /csminstall /BCU_share \n \n \n * \n * new_path_to_fixpack\n * \n * nlpack_path\n * \n * \n * \n\n2. Download the necessary files * \n * If you are applying a special build, your technical support engineer will provide you with the correct download instructions. If you are applying a generally available DB2 fix pack, download the universal build (called the DB2 Universal Fix Pack or DB2 Universal Build) from the following Fix Central page:\n http://www.ibm.com/support/docview.wss?uid=swg27007053 [http://www.ibm.com/support/docview.wss?uid=swg27007053] \n * \n * \n * Verify that the version of the NLPack you download matches the version of the special build or the fix pack you downloaded in step 2a. \n * \n * \n * new_path_to_fixpack\n * \n * nlpack_path\n * \n * \n * \n * \n * * uncompress <filename> or gunzip <filename> \n * tar xvf <filename>.tar\n \n \n\n\n3. Copy the contents of the SApolicy directory * \n * \n * \n * \n * \n * \n * \n * \n * \n * cd /usr/sbin/rsct/sapolicies/db2/ \n \n * \n * tar cvf /BCU_share/sapolicies.save.tar * \n \n \n\n4. Disable high availability (HA) if it is enabled * \n * \n * \n * samctrl -M T \n \n \n * \n * chrsrc -c IBM.PeerNode CritRsrcProtMethod=5 \n\n\n\n5. Stop the instance * \n * db2stop force \n * \n * \n * ps -ef | grep db2 \n \n \n * \n * db2_kill \n \n \n * \n * /< install_path>/IBM/dwe/db2/V9.7/bin/db2fmcu -d \n \n \n * \n * /< install_path>/IBM/dwe/db2/V9.7/bin/db2fm -i < instance_name> -D \n \n \n\n * \n * \n * \n * \n * \n * \n * Note\n * \n * Running the installfixpack command may fail with errors from db2chglibpath (#1598819)\n * \n * \n\n6. Install the fix pack or special build and update the instance \n\nNote: The \"-f NOTSAMP\" option specifies that Tivoli SAMP or RSCT are not updated as part of the DB2 installation process. For fix packs 3a and higher, Tivoli SAMP and RSCT are updated by default, and will cause the scripts in /usr/sbin/rsct/sapolicies/db2/ to be overwritten. Use the following steps to install maintain the same Tivoli SAMP and RSCT version and to keep the SApolicy scripts from being overwritten. * \n * \n * /BCU_share/< new_path_to_fixpack>/installFixPack -b /< install_path>/IBM/dwe/db2/V9.7 -c /BCU_share/< nlpack_path> -f NOTSAMP -f install > /tmp/update_< hostname>_< date>.log \n \n \n * \n * grep execution /tmp/update_< hostname>_< date>.log \n * For each node you should see the following text: \n < hostname>: The execution completed successfully. \n \n \n * \n * As the root user on the ADMIN node, issue the following commands: \n cd /< install_path>/IBM/dwe/db2/V9.7/instance \n ./db2iupdt -u <fenced_user> <instance_user> \n \n \n * \n * /< install_path>/IBM/dwe/db2/V9.7/bin/db2fmcu -d \n \n * \n * i) To remove the instance record which refers to the old DB2 path, issue * \n * install_path\n * \n * <instance_user>\n * \n \n ii) Add the instance record which refers to the new DB2 path, issue * \n * install_path\n * \n * <instance_user>\n * \n * \n \n \n * \n * rah db2level \n * \n * \n * db2start \n * \n * \n * * Verify that users can connect to all nodes \n * Activate the database or follow your normal procedures to release the system to the user community \n * Run the SELECT command against a partitioned table\n \n \n * \n * \n * Binding bind files after installing fix packs\n * \n * \n * \n * \n * \n * \n * db2updv97 - Update database to Version 9.7 fix pack command\n * \n\n\n\n7. Restore the SApolicy scripts * \n * \n * \n * \n * \n * \n * \n * cd /usr/sbin/rsct/sapolicies/db2/ \n * \n * \n * tar xvf /BCU_share/sapolicies.save.tar \n * \n\n8. Enable high availability (HA) if required * \n * chrsrc -c IBM.PeerNode CritRsrcProtMethod=1 \n * \n * \n * samctrl -M F \n\n\n\nBackout procedure (optional) \nIf you need to revert the fix pack update, you will use a procedure similar to the steps described previously, except you will use a different command in step 6a. Use the following steps to back out from a fix pack update. \n\na. Complete steps 1 and 2 previously discussed in this document to download the appropriate universal build and national language pack files. Alternatively you can use files in the /BCU_share directory if you maintained them from a previous installation. \n\nb. Complete steps 3 to 5 previously discussed in this document. \n\nc. Run the following command instead of the command specified in step 6a. Issue the following command as the root user on the ADMIN_ALL, DATA, and STANDBY nodes: * \n * new_path_to_fixpack\n * \n * install_path\n * \n * nlpack_path\n * \n * hostname\n * \n * date\n * \n\n\nd. Complete steps 6b to 8. RELATED INFORMATION\n How to configure dsh [http://www.ibm.com/support/docview.wss?uid=swg21515254]", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * 7.5.0.7\n \n 1. Create a Custom ALN-Domain (Upper(20)\n 2. insert some example items into the domain\n 3. modify the Object DOCLINKS:- attach the attribute DOCUMENT\n to the created domain\n 4. configDB\n 5. modify LIBRARY.xml\n - search for line 7364:\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n label=\"\n Dokument benennen\"/>\n - insert the red marked options\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n lookup=\"\n valuelist\" inputmode=\"REQUIRED\" label=\"Dokument benennen\"/>\n 6.import the changed LIBRARY.xml\n \n Go to PR Application,try to attach a document you will have the\n option to select the value from the field but no results\n displayed for the domain values.\n \n \n The following Errormessage is in the logs:\n \n [ERROR] [MXServer] [] BMXAA6713E - The MBO fetch operation\n failed in the mboset with the SQL error code -206. The record\n could not be retrieved from the database. See the log file for\n more details about the\n error.com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is\n not valid in the context where it is used.. SQLCODE=-206,\n SQLSTATE=42703,\n \n \n \n \n \n\nLOCAL FIX\n * No workaround\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * Maximo users of linked documents who have attached a domain *\n * to DOCLINKS.DOCUMENT *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * BMXAA6713E - The MBO fetch operation failed in the mboset *\n * with the SQL error code -206. The record *\n * could not be retrieved from the database. See the log file *\n * for more details about the error. *\n * *\n * com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is not *\n * valid in the context where it is used.. SQLCODE=-206, *\n * SQLSTATE=42703 *\n ****************************************************************\n * RECOMMENDATION: *\n * Apply latest fix pack. *\n ****************************************************************\n Reproduced in 7.5.0.6 and 7.5.0.7\n \n 1. Create a Custom ALN-Domain (Upper(20))\n 2. Insert some example items into the domain\n 3. In Database Configuration, modify the DOCLINKS object by\n attaching the new domain to the DOCUMENT attribute.\n 4. Configure this change.\n 5. Modify LIBRARY.xml\n a) Search for id=\"addnewattachments_file_1_4\"\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n label=\"Name the document\"/>\n \n b) Modify this line as follows:\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n lookup=\"valuelist\" inputmode=\"REQUIRED\" label=\"Name the\n document\"/>\n \n 6. Import the changed LIBRARY.xml\n \n Go to PR Application,try to attach a document you will have the\n option to select the value from the field but no results\n displayed for the domain values.\n \n The following error message is in the logs: BMXAA6713E - The MBO\n fetch operation failed in the mboset with the SQL error code\n -206.\n The record could not be retrieved from the database. See the log\n file for more details about the error.\n \n com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is not\n valid in the context where it is used..\n SQLCODE=-206,SQLSTATE=42703\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Error message \"BMXAA6713E - The MBO fetch operation failed in\n the mboset with the SQL error code -206. The record could not be\n retrieved from the database. See the log file for more details\n about the error.\n com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is not\n valid in the context where it is used..\n SQLCODE=-206,SQLSTATE=42703\" is no longer encountered when a\n domain is attached to DOCLINKS.DOCUMENT.\n \n The fix for this APAR is contained in the following maintenance\n package:\n | release\\fix pack\\interim fix for Release 7.5.0.9 and Release\n 7.6.0.1 of Base Services\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV70960\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION\n \n \n * REPORTED COMPONENT ID\n 5724R46I1\n \n \n * REPORTED RELEASE\n 750\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2015-03-12\n \n \n * CLOSED DATE\n 2015-04-14\n \n \n * LAST MODIFIED DATE\n 2015-04-14\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nMODULES/MACROS\n * MAXIMO\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n INTEGRATION\n \n \n * FIXED COMPONENT ID\n 5724R46I1\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R750 PSY\n UP", "DSM SQL0204 SQL0204N SQLCODE 204 QUERYTUNER.OQWT_QUERY_RESULT Query Tuning SQLSTATE=42704 TECHNOTE (FAQ)\n\nQUESTION\n Why is Data Server Manager (DSM) showing the \"<table_name>\" is an undefined name SQLCODE=-204, error when running Query Tuning? \n\nCAUSE\nThe <table_name> was not created during the initial DSM setup.\n\nANSWER\nRebuild the missing table by following these steps: \n\n1. Stop DSM (via stop.bat or stop.sh script from <DSM_install>/bin directory). Make sure that there is no DSM processes running.\n\n2. Backup the DSM repository database\n\n3. Connect to the DSM repository database\n\n4. \"AUTOMATIC STORAGE\" needs to be set to \"YES\" for the DSM repository database. Run the following DB2 command: \nALTER DATABASE <DSM_repository_database> ADD STORAGE ON '<storage_path>\n\n5. From <DSM_install>/samples/DB2LUW directory, run the create.sql against the repository database (for example: db2 -tvf create.sql > create.log)\nThis command will attempt to create tables and functions needed for DSM in the repository database.\nIf the objects already exist, that creation will fail and the script proceeds to the next creation. It won't drop the existing objects, and missing objects will be created. \n\n6. Check if all SQLs in create.log output file were executed successfully. \n\n7. From <DSM_install>/samples/DB2LUW directory, run the validate.sql against the repository database (for example: db2 -tvf validate.sql > validate.log), to verify that all the needed repository tables and functions exist. Confirm that all ran successfully.\nIf you have errors referring to the schema DB2OSC, that schema is for z/OS databases, and it can be ignored if you are monitoring LUW databases only. \n\n8. Start DSM (via start.bat or start.sh script from <DSM_install>/bin directory)" ]

[ [ "0a", "SQLCODE 206 -206 SQL0206 SQL0206N DSM incompatible db2level fixpack fix pack db2iupdt TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " Data Server Manager log files are full of SQLCODE=-206 \"<name> is not valid in the context where it is used.\" error SYMPTOM" ], [ "0c", "The symptoms can vary depending on each installation." ], [ "0d", "Most common scenario, DSM shows Data Pending status for the monitored database. CAUSE" ], [ "0e", "When you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release." ], [ "0f", "But that command does not necessarily update the database system catalog to support the new fix pack that you have installed." ], [ "0g", "Meaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level." ], [ "0h", "DIAGNOSING THE PROBLEM" ], [ "0i", "One way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database:" ], [ "0j", "db2 \"select versionnumber from sysibm.sysversions order by 1 desc\"" ], [ "0k", "If the results is showing a lower level than the ones DSM supports, that means your environment" ], [ "0l", "is not supported, and you are getting the SQLCODE=-206 error." ], [ "0m", "To verify what are the DB2 levels supported by DSM, please refer to the links below:" ], [ "0n", "- System requirements for IBM Data Server Manager, version 1.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27045176]" ], [ "0o", "- System requirements for IBM Data Server Manager, version 2.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048115]" ], [ "0p", "RESOLVING THE PROBLEM" ], [ "0q", "Run the db2updvnn command according to the db2level of your monitored database:" ], [ "0r", "- For DB2 V9.7 run db2updv97 [https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command" ], [ "0s", "- For DB2 V10.1 run db2updv10 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command" ], [ "0t", "- For DB2 V10.5 run db2updv105 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command" ], [ "0u", "- For DB2 V11.1 run db2updv111 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command" ] ]

[ "0b", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0o", "0q", "0r", "0s", "0t", "0u", "1b", "1c", "1d", "1f", "1g", "1h", "1i", "1j" ]

[ "SQLCODE 206 -206 SQL0206 SQL0206N DSM incompatible db2level fixpack fix pack db2iupdt TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Data Server Manager log files are full of SQLCODE=-206 \"<name> is not valid in the context where it\nis used.\" error \n\nSYMPTOM\nThe symptoms can vary depending on each installation. \n\nMost common scenario, DSM shows Data Pending status for the monitored database.\n\n\nCAUSE\nWhen you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release. \n\nBut that command does not necessarily update the database system catalog to support the new fix pack that you have installed.\nMeaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level. \n\n\n\nDIAGNOSING THE PROBLEM\nOne way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database: \n\ndb2 \"select versionnumber from sysibm.sysversions order by 1 desc\" \n\nIf the results is showing a lower level than the ones DSM supports, that means your environment\nis not supported, and you are getting the SQLCODE=-206 error.\n\nTo verify what are the DB2 levels supported by DSM, please refer to the links below:\n- System requirements for IBM Data Server Manager, version 1.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27045176]\n- System requirements for IBM Data Server Manager, version 2.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048115]\n\n\n\nRESOLVING THE PROBLEM\nRun the db2updvnn command according to the db2level of your monitored database: \n\n- For DB2 V9.7 run db2updv97 [https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.1 run db2updv10 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.5 run db2updv105 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V11.1 run db2updv111 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command", "DSM SQLCODE=-206 T1.TOTAL_RQST_TIME TOTAL_ROLLBACK_PROC_TIME SQL0206 migration HealthSnapshotLogger TECHNOTE (FAQ)\n\nQUESTION\n Why is Data Server Manager (DSM) showing the following error in HealthSnapshotLogger file, after installing/migrating DSM to a newer version:\n\"T1.TOTAL_RQST_TIME\" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.69.56 \n\nCAUSE\nTwo new columns have been added to the IBMOTS.WORKLOAD_STATS table in DSM Repository Database after V1.1.2.1:\n- TOTAL_ROLLBACK_PROC_TIME bigint\"\n- TOTAL_RQST_TIME bigint\"\n\nFor some reason the migration process did not update the table successfully.\n\n\nANSWER\nTo fix the issue, stop DSM, connect to the DSM Repository Database using the DSM instance owner, and run the following DB2 commands: \n\n- db2 \"alter table IBMOTS.WORKLOAD_STATS add column TOTAL_ROLLBACK_PROC_TIME bigint\"\n- db2 \"alter table IBMOTS.WORKLOAD_STATS add column TOTAL_RQST_TIME bigint\"\n\nRestart DSM.", "BCU; Balanced Warehouse; software level; firmware level; version; Smart Analytics System; balanced configuration unit; ISAS TECHNOTE (FAQ)\n\nQUESTION\n How do I manually install a DB2 special build or DB2 fix pack on an IBM Smart Analytics System? \n\nANSWER\nIf your system is installed with the IBM Smart Analytics System Control Console software, use an IBM Smart Analytics System fix pack available on Fix Central to update your software stack. If the DB2 fix you need is not available in an IBM Smart Analytics System fix pack or your system does not have the control console software installed, use the instructions in this document to manually install a DB2 special build or DB2 fix pack on your IBM Smart Analytics System. \nBefore you begin\nThis document uses the following variables. Substitute the appropriate values for your environment. \n\n\n\nVariable name Example name to use Notes MGMT, ADMIN, ADMIN_ALL, DATA, STANDBY [/support/docview.wss?uid=swg21502587&amp;aid=1] These variables refer to the role of the different servers. Replace each variable with the appropriate host names from your environment. * MGMT = management node used to manage all nodes in the cluster. \n * ADMIN = administration node or NODE0000 or primary coordinator node. \n * ADMIN_ALL = all coordinator nodes \n * DATA = all data nodes in the core warehouse \n * STANDBY = all standby nodes the core warehouse\n\nBCU_share * All AIX systems: /BCU_share \n * 5600 systems: /BCU_share \n * D5000 and D5100: /csminstall\n\n[/support/docview.wss?uid=swg21502587&amp;aid=1] install_path * AIX systems: /usr \n * Linux systems: /opt\n\nThe installation path is operating-system dependent. You can use the db2level command to validate the current installation path. hostname bcudata001 Use the appropriate server host name. date 20110801 Use the format YYYYMMDD, where YYYY represents a 4-digit year, MM represents a 2-digit month, and DD represents a 2-digit month. new_path_to_fixpack DB2_97fp1 Use a name that clearly labels the directory with the product, version, and build number (if you are applying a special build). If you need to install the product in the future, this naming convention will allow you to easily identify the product and correct version to install. nlpack_path NLPack_97fp1 Use a name that clearly identifies the national language pack content and the version contained in the directory. instance_user db2inst1 The name of the DB2 instance owner. fenced_user db2fenc1 The name of the DB2 fenced user. You can find the fenced user name and group by looking at the owner and group of the following file:\nls -l ~<instance_user>/sqllib/adm/.fenced \nNote: You can use any utility you prefer to issue remote commands to the servers in the cluster. If you choose not to use a remote command utility, you can log on to each server and run the commands locally. \n\nProcedure \n1. Mount the installation media directory from the management node * \n * For IBM Smart Analytics System 7600 or 7700, Balanced Warehouse E7100, or IBM Smart Analytics System 5600 environments, issue the following command as root on ADMIN_ALL, DATA, and STANDBY nodes: * \n * \n * \n \n For Balanced Warehouse D5000 or D5100 environments, issue the following command as root on ADMIN_ALL, DATA, and STANDBY nodes: * \n \n \n * Note: In newer configurations, the /BCU_share directory has replaced the /csminstall directory. If you mounted the /csminstall directory, substitute /csminstall for /BCU_share as you follow the instructions in this document. Alternatively, you can create a symbolic link. \n * \n * \n * ln -s /csminstall /BCU_share \n \n \n * \n * new_path_to_fixpack\n * \n * nlpack_path\n * \n * \n * \n\n2. Download the necessary files * \n * If you are applying a special build, your technical support engineer will provide you with the correct download instructions. If you are applying a generally available DB2 fix pack, download the universal build (called the DB2 Universal Fix Pack or DB2 Universal Build) from the following Fix Central page:\n http://www.ibm.com/support/docview.wss?uid=swg27007053 [http://www.ibm.com/support/docview.wss?uid=swg27007053] \n * \n * \n * Verify that the version of the NLPack you download matches the version of the special build or the fix pack you downloaded in step 2a. \n * \n * \n * new_path_to_fixpack\n * \n * nlpack_path\n * \n * \n * \n * \n * * uncompress <filename> or gunzip <filename> \n * tar xvf <filename>.tar\n \n \n\n\n3. Copy the contents of the SApolicy directory * \n * \n * \n * \n * \n * \n * \n * \n * \n * cd /usr/sbin/rsct/sapolicies/db2/ \n \n * \n * tar cvf /BCU_share/sapolicies.save.tar * \n \n \n\n4. Disable high availability (HA) if it is enabled * \n * \n * \n * samctrl -M T \n \n \n * \n * chrsrc -c IBM.PeerNode CritRsrcProtMethod=5 \n\n\n\n5. Stop the instance * \n * db2stop force \n * \n * \n * ps -ef | grep db2 \n \n \n * \n * db2_kill \n \n \n * \n * /< install_path>/IBM/dwe/db2/V9.7/bin/db2fmcu -d \n \n \n * \n * /< install_path>/IBM/dwe/db2/V9.7/bin/db2fm -i < instance_name> -D \n \n \n\n * \n * \n * \n * \n * \n * \n * Note\n * \n * Running the installfixpack command may fail with errors from db2chglibpath (#1598819)\n * \n * \n\n6. Install the fix pack or special build and update the instance \n\nNote: The \"-f NOTSAMP\" option specifies that Tivoli SAMP or RSCT are not updated as part of the DB2 installation process. For fix packs 3a and higher, Tivoli SAMP and RSCT are updated by default, and will cause the scripts in /usr/sbin/rsct/sapolicies/db2/ to be overwritten. Use the following steps to install maintain the same Tivoli SAMP and RSCT version and to keep the SApolicy scripts from being overwritten. * \n * \n * /BCU_share/< new_path_to_fixpack>/installFixPack -b /< install_path>/IBM/dwe/db2/V9.7 -c /BCU_share/< nlpack_path> -f NOTSAMP -f install > /tmp/update_< hostname>_< date>.log \n \n \n * \n * grep execution /tmp/update_< hostname>_< date>.log \n * For each node you should see the following text: \n < hostname>: The execution completed successfully. \n \n \n * \n * As the root user on the ADMIN node, issue the following commands: \n cd /< install_path>/IBM/dwe/db2/V9.7/instance \n ./db2iupdt -u <fenced_user> <instance_user> \n \n \n * \n * /< install_path>/IBM/dwe/db2/V9.7/bin/db2fmcu -d \n \n * \n * i) To remove the instance record which refers to the old DB2 path, issue * \n * install_path\n * \n * <instance_user>\n * \n \n ii) Add the instance record which refers to the new DB2 path, issue * \n * install_path\n * \n * <instance_user>\n * \n * \n \n \n * \n * rah db2level \n * \n * \n * db2start \n * \n * \n * * Verify that users can connect to all nodes \n * Activate the database or follow your normal procedures to release the system to the user community \n * Run the SELECT command against a partitioned table\n \n \n * \n * \n * Binding bind files after installing fix packs\n * \n * \n * \n * \n * \n * \n * db2updv97 - Update database to Version 9.7 fix pack command\n * \n\n\n\n7. Restore the SApolicy scripts * \n * \n * \n * \n * \n * \n * \n * cd /usr/sbin/rsct/sapolicies/db2/ \n * \n * \n * tar xvf /BCU_share/sapolicies.save.tar \n * \n\n8. Enable high availability (HA) if required * \n * chrsrc -c IBM.PeerNode CritRsrcProtMethod=1 \n * \n * \n * samctrl -M F \n\n\n\nBackout procedure (optional) \nIf you need to revert the fix pack update, you will use a procedure similar to the steps described previously, except you will use a different command in step 6a. Use the following steps to back out from a fix pack update. \n\na. Complete steps 1 and 2 previously discussed in this document to download the appropriate universal build and national language pack files. Alternatively you can use files in the /BCU_share directory if you maintained them from a previous installation. \n\nb. Complete steps 3 to 5 previously discussed in this document. \n\nc. Run the following command instead of the command specified in step 6a. Issue the following command as the root user on the ADMIN_ALL, DATA, and STANDBY nodes: * \n * new_path_to_fixpack\n * \n * install_path\n * \n * nlpack_path\n * \n * hostname\n * \n * date\n * \n\n\nd. Complete steps 6b to 8. RELATED INFORMATION\n How to configure dsh [http://www.ibm.com/support/docview.wss?uid=swg21515254]", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * 7.5.0.7\n \n 1. Create a Custom ALN-Domain (Upper(20)\n 2. insert some example items into the domain\n 3. modify the Object DOCLINKS:- attach the attribute DOCUMENT\n to the created domain\n 4. configDB\n 5. modify LIBRARY.xml\n - search for line 7364:\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n label=\"\n Dokument benennen\"/>\n - insert the red marked options\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n lookup=\"\n valuelist\" inputmode=\"REQUIRED\" label=\"Dokument benennen\"/>\n 6.import the changed LIBRARY.xml\n \n Go to PR Application,try to attach a document you will have the\n option to select the value from the field but no results\n displayed for the domain values.\n \n \n The following Errormessage is in the logs:\n \n [ERROR] [MXServer] [] BMXAA6713E - The MBO fetch operation\n failed in the mboset with the SQL error code -206. The record\n could not be retrieved from the database. See the log file for\n more details about the\n error.com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is\n not valid in the context where it is used.. SQLCODE=-206,\n SQLSTATE=42703,\n \n \n \n \n \n\nLOCAL FIX\n * No workaround\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * Maximo users of linked documents who have attached a domain *\n * to DOCLINKS.DOCUMENT *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * BMXAA6713E - The MBO fetch operation failed in the mboset *\n * with the SQL error code -206. The record *\n * could not be retrieved from the database. See the log file *\n * for more details about the error. *\n * *\n * com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is not *\n * valid in the context where it is used.. SQLCODE=-206, *\n * SQLSTATE=42703 *\n ****************************************************************\n * RECOMMENDATION: *\n * Apply latest fix pack. *\n ****************************************************************\n Reproduced in 7.5.0.6 and 7.5.0.7\n \n 1. Create a Custom ALN-Domain (Upper(20))\n 2. Insert some example items into the domain\n 3. In Database Configuration, modify the DOCLINKS object by\n attaching the new domain to the DOCUMENT attribute.\n 4. Configure this change.\n 5. Modify LIBRARY.xml\n a) Search for id=\"addnewattachments_file_1_4\"\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n label=\"Name the document\"/>\n \n b) Modify this line as follows:\n <multiparttextbox dataattribute=\"document\"\n descdataattribute=\"description\" id=\"addnewattachments_file_1_4\"\n lookup=\"valuelist\" inputmode=\"REQUIRED\" label=\"Name the\n document\"/>\n \n 6. Import the changed LIBRARY.xml\n \n Go to PR Application,try to attach a document you will have the\n option to select the value from the field but no results\n displayed for the domain values.\n \n The following error message is in the logs: BMXAA6713E - The MBO\n fetch operation failed in the mboset with the SQL error code\n -206.\n The record could not be retrieved from the database. See the log\n file for more details about the error.\n \n com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is not\n valid in the context where it is used..\n SQLCODE=-206,SQLSTATE=42703\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Error message \"BMXAA6713E - The MBO fetch operation failed in\n the mboset with the SQL error code -206. The record could not be\n retrieved from the database. See the log file for more details\n about the error.\n com.ibm.db2.jcc.am.SqlSyntaxErrorException: \"DOCTYPE\" is not\n valid in the context where it is used..\n SQLCODE=-206,SQLSTATE=42703\" is no longer encountered when a\n domain is attached to DOCLINKS.DOCUMENT.\n \n The fix for this APAR is contained in the following maintenance\n package:\n | release\\fix pack\\interim fix for Release 7.5.0.9 and Release\n 7.6.0.1 of Base Services\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV70960\n \n \n * REPORTED COMPONENT NAME\n INTEGRATION\n \n \n * REPORTED COMPONENT ID\n 5724R46I1\n \n \n * REPORTED RELEASE\n 750\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2015-03-12\n \n \n * CLOSED DATE\n 2015-04-14\n \n \n * LAST MODIFIED DATE\n 2015-04-14\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nMODULES/MACROS\n * MAXIMO\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n INTEGRATION\n \n \n * FIXED COMPONENT ID\n 5724R46I1\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R750 PSY\n UP", "DSM SQL0204 SQL0204N SQLCODE 204 QUERYTUNER.OQWT_QUERY_RESULT Query Tuning SQLSTATE=42704 TECHNOTE (FAQ)\n\nQUESTION\n Why is Data Server Manager (DSM) showing the \"<table_name>\" is an undefined name SQLCODE=-204, error when running Query Tuning? \n\nCAUSE\nThe <table_name> was not created during the initial DSM setup.\n\nANSWER\nRebuild the missing table by following these steps: \n\n1. Stop DSM (via stop.bat or stop.sh script from <DSM_install>/bin directory). Make sure that there is no DSM processes running.\n\n2. Backup the DSM repository database\n\n3. Connect to the DSM repository database\n\n4. \"AUTOMATIC STORAGE\" needs to be set to \"YES\" for the DSM repository database. Run the following DB2 command: \nALTER DATABASE <DSM_repository_database> ADD STORAGE ON '<storage_path>\n\n5. From <DSM_install>/samples/DB2LUW directory, run the create.sql against the repository database (for example: db2 -tvf create.sql > create.log)\nThis command will attempt to create tables and functions needed for DSM in the repository database.\nIf the objects already exist, that creation will fail and the script proceeds to the next creation. It won't drop the existing objects, and missing objects will be created. \n\n6. Check if all SQLs in create.log output file were executed successfully. \n\n7. From <DSM_install>/samples/DB2LUW directory, run the validate.sql against the repository database (for example: db2 -tvf validate.sql > validate.log), to verify that all the needed repository tables and functions exist. Confirm that all ran successfully.\nIf you have errors referring to the schema DB2OSC, that schema is for z/OS databases, and it can be ignored if you are monitoring LUW databases only. \n\n8. Start DSM (via start.bat or start.sh script from <DSM_install>/bin directory)" ]

[ [ "1a", "DSM SQLCODE=-206 T1.TOTAL_RQST_TIME TOTAL_ROLLBACK_PROC_TIME SQL0206 migration HealthSnapshotLogger TECHNOTE (FAQ) QUESTION" ], [ "1b", " Why is Data Server Manager (DSM) showing the following error in HealthSnapshotLogger file, after installing/migrating DSM to a newer version:" ], [ "1c", "\"T1.TOTAL_RQST_TIME\" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=3.69.56 CAUSE" ], [ "1d", "Two new columns have been added to the IBMOTS.WORKLOAD_STATS table in DSM Repository Database after V1.1.2.1:" ], [ "1e", "- TOTAL_ROLLBACK_PROC_TIME bigint\"" ], [ "1f", "- TOTAL_RQST_TIME bigint\"" ], [ "1g", "For some reason the migration process did not update the table successfully. ANSWER" ], [ "1h", "To fix the issue, stop DSM, connect to the DSM Repository Database using the DSM instance owner, and run the following DB2 commands:" ], [ "1i", "- db2 \"alter table IBMOTS.WORKLOAD_STATS add column TOTAL_ROLLBACK_PROC_TIME bigint\"" ], [ "1j", "- db2 \"alter table IBMOTS.WORKLOAD_STATS add column TOTAL_RQST_TIME bigint\" Restart DSM." ] ]

[ "0b", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0o", "0q", "0r", "0s", "0t", "0u", "1b", "1c", "1d", "1f", "1g", "1h", "1i", "1j" ]

[ "CF; CF_MEM_SZ; 256 GB TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customer wants to use more than 256 GB memory for purescale CF on Linux AMD64 platform, but CF cannot be started if CF_MEM_SZ is defined to larger than 256 GB. \n\nSYMPTOM\ndb2diag.log prints:\n\n2014-08-08-16.45.41.774177+480 I132020E514 LEVEL: Error\nPID : 64247 TID : 46912853183040 PROC : ca-wdog 128 [db2sdin1]\nINSTANCE: db2sdin1 NODE : 128\nHOSTNAME: test1\nFUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876\nDATA #1 : <preformatted>\nCA Configure command failed: mrb rc = (-2147090354)\nDATA #1 : <preformatted>\nIf a CF return code is displayed above and you wish to get\nmore information then please run the following command:\n\ndb2diag -cfrc <CF_errcode>\n\n2014-08-08-16.45.41.774482+480 E132535E418 LEVEL: Severe\nPID : 64247 TID : 46912853183040 PROC : ca-wdog 128 [db2sdin1]\nINSTANCE: db2sdin1 NODE : 128\nHOSTNAME: test1\nFUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for CF, sqleSendCFServerConfig, probe:2687\nMESSAGE : ECF=0x94C6004E=-1798963122\nDATA #1 : String, 43 bytes\nUnable to configure and start the CF server\n\n\nFrom the output of 'db2diag -cfrc -2147090354', rc = (-2147090354) means CF_MGMNT_SHMEM_CREATE_FAILURE.\n\ncfdiag.log prints:\n\n2014-08-08-16.44.18.0740598305+480 E123456789A328 LEVEL : Error\nPID : 59532 TID : 2863404512\nNODE : 000\nHOSTNAME : test1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nmgmnt_castart() shmget failed trying to alllocate Shared Memory for the Coupling Memory. errno: 22\n\n\nCAUSE\nThe 256 GB maximum size restriction for a single shared memory segment is a hard architectural limit in the Linux implementation on AMD64 (x86_64).\n\n\nENVIRONMENT\nOS: Linux AMD64 platform\n\n\n\nDIAGNOSING THE PROBLEM\nThe following simple program can reveal this limit:\n\n[root@IM002_redhat ~]# cat test.c\n#include <sys/ipc.h>\n#include <sys/types.h>\n#include <sys/shm.h>\n#include <errno.h>\n\n#include <stdio.h>\n#include <stdlib.h>\n\nint main ( int argc, char ** argv )\n{\nvoid *attachAddress = NULL;\nint shmid = 0;\n\nsize_t shmSize = 362041049088 ;\nint shmFlag = 0x000007C1;\nint rc = 0 ;\nstruct shmid_ds buf;\nint sizeInGB = 0 ;\n\nif( argc != 2 )\n{\nfprintf(stderr, \"One argument , the segment size in GB is required \\n\" );\nexit(-1);\n}\n\nsizeInGB = atoi(argv[1]) ;\nshmSize = (size_t)( sizeInGB * 0x40000000L) ;\nfprintf( stdout , \" Going to allocate %d GB , or %lld bytes \\n\", sizeInGB, shmSize);\n\nshmid = shmget ( IPC_PRIVATE, shmSize, shmFlag ) ;\nif( shmid == -1 )\n{\nfprintf(stderr, \"Error received in shmget, errno = %d\\n\", errno );\nexit( -1 );\n}\n\nfprintf(stdout, \"Memory segment is created\\n\" );\nattachAddress = shmat( shmid, NULL, 0 );\nif ( ( void * )-1 == attachAddress )\n{\nfprintf(stderr, \"Error received in shmat, errno = %d\\n\", errno );\n}\nfprintf(stdout, \"Memory attached at address 0x%llx\\n\", attachAddress );\n\nshmdt(attachAddress);\n\n\nrc = shmctl( shmid ,IPC_RMID,&buf);\nif( -1 == rc )\n{\nfprintf(stderr, \"Error received in shmctl, errno = %d\\n\", errno );\n}\nreturn 0;\n\n}\n\nCompile:\ngcc test.c -o test\n\nMake sure SHMMAX is set to larger than the memory you want to allocate by shmget().\n\nRun:\n./test 256\n./test 257\n\nThe first one will succeed, the second one will fail with errno 22.\n\n\n\nRESOLVING THE PROBLEM\nDo not set CF_MEM_SZ to larger than 256 GB on Linux AMD64 platform.", "DB2; db; HADR; db2diag.log TECHNOTE (FAQ)\n\nQUESTION\n What is the impact of the following entries in the db2diag.log?\n\n\n\n2016-05-23-23.22.52.962778-240 I159583626A459 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleRemoteConn, probe:30160\n\nMESSAGE : TCP socket connection accepted. Remote Host: xx.xx.xx.xxx\n\nPort: 4697\n\n\n\n2016-05-23-23.23.37.957348-240 I159584086A548 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrGetTcpMessage, probe:36800\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nRemote connection is not following correct msg format\n\n\n\n2016-05-23-23.23.37.958079-240 I159584635A532 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrHandleHsAck,\n\nprobe:39960\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with remote host failed.\n\n\n\n2016-05-23-23.23.37.958678-240 I159585168A566 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleHsErrors, probe:30545\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with Unknown (0) failed. continue with old connection\n\n\n\n2016-05-23-23.23.37.959277-240 I159585735A376 LEVEL: Severe\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrEduAcceptEvent, probe:20290\n\n\n\n2016-05-23-23.23.37.961422-240 I159586112A459 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleRemoteConn, probe:30160\n\nMESSAGE : TCP socket connection accepted. Remote Host: xx.xx.xx.xx\n\nPort: 6036\n\n\n\n2016-05-23-23.23.37.965151-240 I159586572A596 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrGetTcpMessage, probe:37010\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nClosing new connection that didn't send enough data.\n\nThere is an existing Primary-Standby connection.\n\n\n\n2016-05-23-23.23.37.965977-240 I159587169A532 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrHandleHsAck,\n\nprobe:39960\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with remote host failed.\n\n\n\n2016-05-23-23.23.37.966668-240 I159587702A566 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleHsErrors, probe:30545\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with Unknown (0) failed. continue with old connection \n\nCAUSE\nExternal to DB2\n\nANSWER\nThese diag.log messages indicate that there is an unrelated program\ntrying to contact the ports used by DB2 for HADR, like a ping program\nor some network monitoring program, or some other. This used to cause\nconfusion to DB2 and we ended up dropping a good HADR connection with\nthe standby. We have enhanced to limit the impact and not let such\nevent to damage the good HADR connection. It is still good to track down the source of this program\nand hopefully not be generating such noise, but it is outside of control of DB2\nWe can only protect ourselves and not let such event cause damage to the database service.", "CF 启动失败; register_notify_memory; -2146893782; 0x8009002a TECHNOTE (TROUBLESHOOTING)\n\n本文档仅适用于以下语言版本：\n 简体中文 \n\n问题（摘要）\n 由于Mellanox adapter registration内存限制导致Purescale CF 启动失败 \n\n症状\n从 \"db2instance -list\" 输出可以看到对应CF呈 \"ERROR\" 状态. 还可以看到下面的警告： \n\n$ db2cluster -cm -list -alert \n1. \nAlert: The cluster caching facility (CF) failed to start on the host.\nHost: 'AAPS3PPD'. CF: '128'.\n\n\ndb2diag.log 里面可以看到类似下面的错误信息，最重要的是看到错误代码 -2146893782:\n\n2014-08-14-16.45.27.527334+480 I11010E516 LEVEL: Error\nPID : 32560 TID : 47147934016672 PROC : ca-wdog 128 [db2pure]\nINSTANCE: db2pure NODE : 128\nHOSTNAME: HOSTNAME1\nFUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876\nDATA #1 : <preformatted>\nCA Configure command failed: mrb rc = (-2146893782)\nDATA #1 : <preformatted>\nIf a CF return code is displayed above and you wish to get\nmore information then please run the following command:\n\ndb2diag -cfrc <CF_errcode>\n\n2014-08-14-16.45.27.529735+480 E11527E420 LEVEL: Severe\nPID : 32560 TID : 47147934016672 PROC : ca-wdog 128 [db2pure]\nINSTANCE: db2pure NODE : 128\nHOSTNAME: HOSTNAME1\nFUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for CF, sqleSendCFServerConfig, probe:2687\nMESSAGE : ECF=0x97C9002A=-1748434902\nDATA #1 : String, 43 bytes\nUnable to configure and start the CF server\n\n\n原因\n这个问题很可能是由于Mellanox adapter registration 内存限制导致的。\n\n\n环境\nPurescale server on Linux\n\n\n\n诊断问题\n1.搜集 db2support . -purescale，至少得搜集问题发生时候的db2diag.log日志 \n\n2. 从cfdiag.xxx.log中, 可以看到 register_notify_memory() 返回错误代码 0x8009002a: \n\n\n2014-08-15-09.01.52.0037546570+480 E123456789A313 LEVEL : Error\nPID : 3363 TID : 1546295264\nHOSTNAME : HOSTNAME1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nregister_notify_memory() Local Memory Region Create (dat_lmr_create) failed. DAT Status: 0x30000\n\n2014-08-15-09.01.52.0037588678+480 E123456789A304 LEVEL : Error\nPID : 3363 TID : 1546295264\nHOSTNAME : HOSTNAME1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nregister_notify_memory() Notify Memory Registration failed on HCA 0. status: 0x8009002a\n\n2014-08-15-09.01.52.0037609689+480 E123456789A325 LEVEL : Error\nPID : 3363 TID : 1546295264\nHOSTNAME : HOSTNAME1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nmgmnt_castart() CA Server start-up aborted due errors during start-up and initialization. Status: 0x8009002a\n\n\n解决问题\n参照信息中心下面链接中的第五步增加 Mellanox adapter registration内存大小： \n\n\nhttp://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html]\n\n将 CF 所在节点机器上的 Mellanox HCA 驱动的 mlx4_core 参数 log_mtts_per_seg 的值从3 (默认值) 增加到 7。 这需要使用root 用户， 具体步骤如下：\n\n\n * 如果是 SUSE:\n\n\necho \"options mlx4_core log_mtts_per_seg=7\" >> /etc/modprobe.conf.local \n * 如果是 RHEL:\n\n\necho \"options mlx4_core log_mtts_per_seg=7\" >> /etc/modprobe.d/modprobe.conf \noptions mlx4_core log_mtts_per_seg=7 \n\n上面的操作后需要重启操作系统使更高生效。 重启后可以使用下面的命令查看参数修改是否生效： \n\n<host-name>/sys/module/mlx4_core/parameters # cat /sys/module/mlx4_core/parameters/log_mtts_per_seg \n7 相关信息\n#Preinstallation checklist for DB2 pureScale Feature (Li [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n SQL1768N Unable to start HADR. Reason code = \"5\" while initializing high availability disaster recovery (HADR) \n\nCAUSE\nThe error might come while starting HADR for ex. db2 start hadr on database <db_name> as primary, when service port/socket is already used for other service.\n\nDIAGNOSING THE PROBLEM\nSocket allocated for HADR - \n\n$ cat /etc/services | grep -i 60070\ndb2_hadr_1 60070/tcp\n\ndb2 get db cfg for sample | grep -i HADR_LOCAL\nHADR local host name (HADR_LOCAL_HOST) = 9.182.192.146\nHADR local service name (HADR_LOCAL_SVC) = 60070\n\nCheck the db2diag.log file for errors. When it is socket in use problem, you should see message similar to following -\n\n2016-09-17-03.17.58.515457+330 I99076A572 LEVEL: Warning\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrBindAndListen, probe:20310\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nDATA #1 : String, 45 bytes\nRetrying bind, socket is in use. Retry count:\nDATA #2 : unsigned integer, 8 bytes\n5\n\n2016-09-17-03.17.58.513634+330 E98071A520 LEVEL: Error (OS)\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, oper system services, sqloPdbBindSocket, probe:20\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nCALLED : OS, -, bind\nOSERR : EADDRINUSE (67) \"Address already in use\"\n\n2016-09-17-03.17.58.514530+330 E98592A483 LEVEL: Severe\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, oper system services, sqloPdbBindSocket, probe:1131\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nDATA #1 : <preformatted>\nPort=[60070]\n\n2016-09-17-03.17.59.016412+330 I99649A459 LEVEL: Error\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrBindAndListen, probe:20320\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\n\n2016-09-17-03.17.59.017161+330 I100109A553 LEVEL: Error\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetupListenerSocket, probe:22030\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nDATA #1 : <preformatted>\nFailed to setup listener socket on address=9.182.192.146:60070\n\n..\n\n2016-09-17-03.17.59.053310+330 I109827A890 LEVEL: Severe\nPID : 27066368 TID : 8140 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nAPPHDL : 0-12174 APPID: *LOCAL.milindt.160916214757\nAUTHID : MILINDT HOSTNAME: ihubaix1.in.ibm.com\nEDUID : 8140 EDUNAME: db2agent (SAMPLE) 0\nFUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::FirstConnect, probe:8777\nDATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes\nsqlcaid : SQLCA sqlcabc: 136 sqlcode: -1768 sqlerrml: 1\nsqlerrmc: 5\nsqlerrp : SQL10012\nsqlerrd : (1) 0x00000000 (2) 0x00000005 (3) 0x00000000\n(4) 0x00000000 (5) 0x00000000 (6) 0x00000000\nsqlwarn : (1) (2) (3) (4) (5) (6)\n(7) (8) (9) (10) (11)\nsqlstate:\n\n\n\nRESOLVING THE PROBLEM\nCheck if the socket listed in db2diag.log is already in use using netstat and lsof commands. \n\n$ netstat -an | grep -i 60070\ntcp4 0 0 9.182.192.146.60070 9.182.192.147.41473 ESTABLISHED\ntcp4 0 0 9.182.192.146.60070 9.182.192.147.41474 ESTABLISHED\ntcp4 0 0 9.182.192.146.60070 *.* LISTEN\n\n# lsof -i :60070\nlsof: WARNING: compiled for AIX version 5.3.0.0; this is 7.1.0.0.\nCOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME\ndb2sysc 27066368 xxxxxxx 48u IPv4 0xf1000e0004ac33b8 0t0 TCP ihubaix1.in.ibm.com:db2_hadr_1 (LISTEN)\ndb2sysc 27066368 xxxxxxx 49u IPv4 0xf1000e00108ad3b8 0t0 TCP ihubaix1.in.ibm.com:db2_hadr_1->ihubaix2.in.ibm.com:41473 (ESTABLISHED)\ndb2sysc 27066368 xxxxxxx 50u IPv4 0xf1000e0005c7d3b8 0t0 TCP ihubaix1.in.ibm.com:db2_hadr_1->ihubaix2.in.ibm.com:41474 (ESTABLISHED)\n\nEither allocate new port for HADR_LOCAL_SVC or deallocate port 60070 from the existing service and re-issue the start hadr command.\n\nhttp://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.sql.doc/doc/msql01768n.html [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.sql.doc/doc/msql01768n.html] \n\n\n\nCross reference information Segment Product Component Platform Version Edition Information Management DB2 for Linux- UNIX and Windows", " TECHNOTE (FAQ)\n\nQUESTION\n What are known issues on Linux platforms related to DB2® database products ? \n\nANSWER\nKnown Issues with DB2 on Linux \n\n[/support/docview.wss?uid=swg21681093&amp;aid=1]\nBug ID [/support/docview.wss?uid=swg21681093&amp;aid=2]Description\nLinux Flavor [/support/docview.wss?uid=swg21681093&amp;aid=3]\nComments 1076574 DB2's 'db2syc' process exhibits memory leak. Redhat v6 DB2 'db2sysc' process will see memory leak. Eventually, RAM and swap will be 100% consumed. The machine will be non-responsive. This memory is released when DB2 engine is stopped with 'db2stop'.\n\nThis is a RedHat Linux issue and is discussed here:https://access.redhat.com/support/cases/01054560/ [https://access.redhat.com/support/cases/01054560/] \n\nThis problem is already fixed by RedHat. The detailed description of all the Redhat Linux versions affected by this bug and fix details are available at:https://rhn.redhat.com/errata/RHBA-2014-0470.html [https://rhn.redhat.com/errata/RHBA-2014-0470.html] 1042807 32-bit applications running on 64-bit platforms where issuing msgrcv with -ve message type hangs with error: \nerror: msgrcv: No message of the desired type. Redhat v7\nkernel-3.10.0-54.0.1.e17.x86_64 32-bit application does not work on RHEL 7.0 with 64-bit DB2 engine. When the sample programs under sqllib/samples/c/ like inattach.c or dbinfo.c is compiled by bldapp with BITWIDTH=32, it hangs in sqlorqueInternal.\n\nThis is a RedHat Linux issue and is discussed here:\nhttps://access.redhat.com/solutions/1202773 [https://access.redhat.com/solutions/1202773]\n\nThis problem will be fixed by RedHat in v7.1 1264533 DB2 Panic, due to removed IPC resources. Redhat v7.2 The problem is caused by logind removing IPC resources owned by user when this user logs off. The bug is described here:\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1264533 [https://bugzilla.redhat.com/show_bug.cgi?id=1264533]\n\nLocal Fix:\nAdd the following setting to file /etc/systemd/logind.conf\nRemoveIPC=no 948149 db2dart reports incorrect container tag for container which resides on XFS SLES 12 This problem exists for XFS and only if container is opened in Direct IO mode. In reality the container tag is not corrupted but result buffer will return empty after pread call, which did not report any errors. More information here:\nhttps://bugzilla.linux.ibm.com/show_bug.cgi?id=131069 [https://bugzilla.linux.ibm.com/show_bug.cgi?id=131069] \n\nThe problem is fixed in \nkernel-default-3.12.32-33.1.x86_64.rpm\n\n1165277 db2 local connections may hang in semop function Redhat/CentOS v6.6. The problem is caused by a IPC bug, first seen in kernel kernel 2.6.32-434.el6. More information here: https://bugzilla.linux.ibm.com/show_bug.cgi?id=119049 [https://bugzilla.linux.ibm.com/show_bug.cgi?id=119049]\n\nFixed in https://rhn.redhat.com/errata/RHSA-2015-1272.html [https://rhn.redhat.com/errata/RHSA-2015-1272.html]\n\nLocal Fix:\nConfigure local clients' connections through TCP/IP loopback." ]

[ [ "0a", "CF; CF_MEM_SZ; 256 GB TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " Customer wants to use more than 256 GB memory for purescale CF on Linux AMD64 platform, but CF cannot be started if CF_MEM_SZ is defined to larger than 256 GB. SYMPTOM db2diag.log prints:" ], [ "0c", "2014-08-08-16.45.41.774177+480 I132020E514 LEVEL: Error" ], [ "0d", "PID : 64247 TID : 46912853183040 PROC : ca-wdog 128 [db2sdin1]" ], [ "0e", "INSTANCE: db2sdin1 NODE : 128 HOSTNAME: test1" ], [ "0f", "FUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876" ], [ "0g", "DATA #1 : <preformatted>" ], [ "0h", "CA Configure command failed: mrb rc = (-2147090354)" ], [ "0i", "DATA #1 : <preformatted>" ], [ "0j", "If a CF return code is displayed above and you wish to get" ], [ "0k", "more information then please run the following command:" ], [ "0l", "db2diag -cfrc <CF_errcode>" ], [ "0m", "2014-08-08-16.45.41.774482+480 E132535E418 LEVEL: Severe" ], [ "0n", "PID : 64247 TID : 46912853183040 PROC : ca-wdog 128 [db2sdin1]" ], [ "0o", "INSTANCE: db2sdin1 NODE : 128 HOSTNAME: test1" ], [ "0p", "FUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for CF, sqleSendCFServerConfig, probe:2687" ], [ "0q", "MESSAGE : ECF=0x94C6004E=-1798963122" ], [ "0r", "DATA #1 : String, 43 bytes" ], [ "0s", "Unable to configure and start the CF server" ], [ "0t", "From the output of 'db2diag -cfrc -2147090354', rc = (-2147090354) means CF_MGMNT_SHMEM_CREATE_FAILURE. cfdiag.log prints:" ], [ "0u", "2014-08-08-16.44.18.0740598305+480 E123456789A328 LEVEL : Error" ], [ "0v", "PID : 59532 TID : 2863404512" ], [ "0w", "NODE : 000" ], [ "0x", "HOSTNAME : test1" ], [ "0y", "FUNCTION : CA trace, log_error" ], [ "0z", "MESSAGE : CA server has encountered an error." ], [ "0aa", "DATA #1 :" ], [ "0ab", "mgmnt_castart() shmget failed trying to alllocate Shared Memory for the Coupling Memory. errno: 22 CAUSE" ], [ "0ac", "The 256 GB maximum size restriction for a single shared memory segment is a hard architectural limit in the Linux implementation on AMD64 (x86_64). ENVIRONMENT" ], [ "0ad", "OS: Linux AMD64 platform" ], [ "0ae", "DIAGNOSING THE PROBLEM" ], [ "0af", "The following simple program can reveal this limit:" ], [ "0ag", "[root@IM002_redhat ~]# cat test.c #include <sys/ipc.h> #include <sys/types.h> #include <sys/shm.h> #include <errno.h> #include <stdio.h> #include <stdlib.h>" ], [ "0ah", "int main ( int argc, char ** argv ) {" ], [ "0ai", "void *attachAddress = NULL;" ], [ "0aj", "int shmid = 0;" ], [ "0ak", "size_t shmSize = 362041049088 ;" ], [ "0al", "int shmFlag = 0x000007C1;" ], [ "0am", "int rc = 0 ;" ], [ "0an", "struct shmid_ds buf;" ], [ "0ao", "int sizeInGB = 0 ;" ], [ "0ap", "if( argc != 2 ) {" ], [ "0aq", "fprintf(stderr, \"One argument , the segment size in GB is required \\n\" ); exit(-1); }" ], [ "0ar", "sizeInGB = atoi(argv[1]) ;" ], [ "0as", "shmSize = (size_t)( sizeInGB * 0x40000000L) ;" ], [ "0at", "fprintf( stdout , \" Going to allocate %d GB , or %lld bytes \\n\", sizeInGB, shmSize);" ], [ "0au", "shmid = shmget ( IPC_PRIVATE, shmSize, shmFlag ) ;" ], [ "0av", "if( shmid == -1 ) {" ], [ "0aw", "fprintf(stderr, \"Error received in shmget, errno = %d\\n\", errno );" ], [ "0ax", "exit( -1 ); }" ], [ "0ay", "fprintf(stdout, \"Memory segment is created\\n\" );" ], [ "0az", "attachAddress = shmat( shmid, NULL, 0 );" ], [ "0ba", "if ( ( void * )-1 == attachAddress ) {" ], [ "0bb", "fprintf(stderr, \"Error received in shmat, errno = %d\\n\", errno ); }" ], [ "0bc", "fprintf(stdout, \"Memory attached at address 0x%llx\\n\", attachAddress ); shmdt(attachAddress);" ], [ "0bd", "rc = shmctl( shmid ,IPC_RMID,&buf);" ], [ "0be", "if( -1 == rc ) {" ], [ "0bf", "fprintf(stderr, \"Error received in shmctl, errno = %d\\n\", errno ); } return 0; } Compile:" ], [ "0bg", "gcc test.c -o test" ], [ "0bh", "Make sure SHMMAX is set to larger than the memory you want to allocate by shmget(). Run: ./test 256 ./test 257" ], [ "0bi", "The first one will succeed, the second one will fail with errno 22." ], [ "0bj", "RESOLVING THE PROBLEM" ], [ "0bk", "Do not set CF_MEM_SZ to larger than 256 GB on Linux AMD64 platform." ] ]

[ "0b", "0m", "0s", "0t", "0ac", "2f", "2g", "2l" ]

[ "CF; CF_MEM_SZ; 256 GB TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customer wants to use more than 256 GB memory for purescale CF on Linux AMD64 platform, but CF cannot be started if CF_MEM_SZ is defined to larger than 256 GB. \n\nSYMPTOM\ndb2diag.log prints:\n\n2014-08-08-16.45.41.774177+480 I132020E514 LEVEL: Error\nPID : 64247 TID : 46912853183040 PROC : ca-wdog 128 [db2sdin1]\nINSTANCE: db2sdin1 NODE : 128\nHOSTNAME: test1\nFUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876\nDATA #1 : <preformatted>\nCA Configure command failed: mrb rc = (-2147090354)\nDATA #1 : <preformatted>\nIf a CF return code is displayed above and you wish to get\nmore information then please run the following command:\n\ndb2diag -cfrc <CF_errcode>\n\n2014-08-08-16.45.41.774482+480 E132535E418 LEVEL: Severe\nPID : 64247 TID : 46912853183040 PROC : ca-wdog 128 [db2sdin1]\nINSTANCE: db2sdin1 NODE : 128\nHOSTNAME: test1\nFUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for CF, sqleSendCFServerConfig, probe:2687\nMESSAGE : ECF=0x94C6004E=-1798963122\nDATA #1 : String, 43 bytes\nUnable to configure and start the CF server\n\n\nFrom the output of 'db2diag -cfrc -2147090354', rc = (-2147090354) means CF_MGMNT_SHMEM_CREATE_FAILURE.\n\ncfdiag.log prints:\n\n2014-08-08-16.44.18.0740598305+480 E123456789A328 LEVEL : Error\nPID : 59532 TID : 2863404512\nNODE : 000\nHOSTNAME : test1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nmgmnt_castart() shmget failed trying to alllocate Shared Memory for the Coupling Memory. errno: 22\n\n\nCAUSE\nThe 256 GB maximum size restriction for a single shared memory segment is a hard architectural limit in the Linux implementation on AMD64 (x86_64).\n\n\nENVIRONMENT\nOS: Linux AMD64 platform\n\n\n\nDIAGNOSING THE PROBLEM\nThe following simple program can reveal this limit:\n\n[root@IM002_redhat ~]# cat test.c\n#include <sys/ipc.h>\n#include <sys/types.h>\n#include <sys/shm.h>\n#include <errno.h>\n\n#include <stdio.h>\n#include <stdlib.h>\n\nint main ( int argc, char ** argv )\n{\nvoid *attachAddress = NULL;\nint shmid = 0;\n\nsize_t shmSize = 362041049088 ;\nint shmFlag = 0x000007C1;\nint rc = 0 ;\nstruct shmid_ds buf;\nint sizeInGB = 0 ;\n\nif( argc != 2 )\n{\nfprintf(stderr, \"One argument , the segment size in GB is required \\n\" );\nexit(-1);\n}\n\nsizeInGB = atoi(argv[1]) ;\nshmSize = (size_t)( sizeInGB * 0x40000000L) ;\nfprintf( stdout , \" Going to allocate %d GB , or %lld bytes \\n\", sizeInGB, shmSize);\n\nshmid = shmget ( IPC_PRIVATE, shmSize, shmFlag ) ;\nif( shmid == -1 )\n{\nfprintf(stderr, \"Error received in shmget, errno = %d\\n\", errno );\nexit( -1 );\n}\n\nfprintf(stdout, \"Memory segment is created\\n\" );\nattachAddress = shmat( shmid, NULL, 0 );\nif ( ( void * )-1 == attachAddress )\n{\nfprintf(stderr, \"Error received in shmat, errno = %d\\n\", errno );\n}\nfprintf(stdout, \"Memory attached at address 0x%llx\\n\", attachAddress );\n\nshmdt(attachAddress);\n\n\nrc = shmctl( shmid ,IPC_RMID,&buf);\nif( -1 == rc )\n{\nfprintf(stderr, \"Error received in shmctl, errno = %d\\n\", errno );\n}\nreturn 0;\n\n}\n\nCompile:\ngcc test.c -o test\n\nMake sure SHMMAX is set to larger than the memory you want to allocate by shmget().\n\nRun:\n./test 256\n./test 257\n\nThe first one will succeed, the second one will fail with errno 22.\n\n\n\nRESOLVING THE PROBLEM\nDo not set CF_MEM_SZ to larger than 256 GB on Linux AMD64 platform.", "DB2; db; HADR; db2diag.log TECHNOTE (FAQ)\n\nQUESTION\n What is the impact of the following entries in the db2diag.log?\n\n\n\n2016-05-23-23.22.52.962778-240 I159583626A459 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleRemoteConn, probe:30160\n\nMESSAGE : TCP socket connection accepted. Remote Host: xx.xx.xx.xxx\n\nPort: 4697\n\n\n\n2016-05-23-23.23.37.957348-240 I159584086A548 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrGetTcpMessage, probe:36800\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nRemote connection is not following correct msg format\n\n\n\n2016-05-23-23.23.37.958079-240 I159584635A532 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrHandleHsAck,\n\nprobe:39960\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with remote host failed.\n\n\n\n2016-05-23-23.23.37.958678-240 I159585168A566 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleHsErrors, probe:30545\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with Unknown (0) failed. continue with old connection\n\n\n\n2016-05-23-23.23.37.959277-240 I159585735A376 LEVEL: Severe\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrEduAcceptEvent, probe:20290\n\n\n\n2016-05-23-23.23.37.961422-240 I159586112A459 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleRemoteConn, probe:30160\n\nMESSAGE : TCP socket connection accepted. Remote Host: xx.xx.xx.xx\n\nPort: 6036\n\n\n\n2016-05-23-23.23.37.965151-240 I159586572A596 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrGetTcpMessage, probe:37010\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nClosing new connection that didn't send enough data.\n\nThere is an existing Primary-Standby connection.\n\n\n\n2016-05-23-23.23.37.965977-240 I159587169A532 LEVEL: Error\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrHandleHsAck,\n\nprobe:39960\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with remote host failed.\n\n\n\n2016-05-23-23.23.37.966668-240 I159587702A566 LEVEL: Warning\n\nPID : 16449544 TID : 9174 PROC : db2sysc 0\n\nINSTANCE: abcd NODE : 000 DB : TADDM\n\nHOSTNAME: abcde\n\nEDUID : 9174 EDUNAME: db2hadrp.0.1 (TADDM) 0\n\nFUNCTION: DB2 UDB, High Availability Disaster Recovery,\n\nhdrHandleHsErrors, probe:30545\n\nMESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR\n\n\"generic HADR error code\"\n\nDATA #1 : <preformatted>\n\nHADR handshake with Unknown (0) failed. continue with old connection \n\nCAUSE\nExternal to DB2\n\nANSWER\nThese diag.log messages indicate that there is an unrelated program\ntrying to contact the ports used by DB2 for HADR, like a ping program\nor some network monitoring program, or some other. This used to cause\nconfusion to DB2 and we ended up dropping a good HADR connection with\nthe standby. We have enhanced to limit the impact and not let such\nevent to damage the good HADR connection. It is still good to track down the source of this program\nand hopefully not be generating such noise, but it is outside of control of DB2\nWe can only protect ourselves and not let such event cause damage to the database service.", "CF 启动失败; register_notify_memory; -2146893782; 0x8009002a TECHNOTE (TROUBLESHOOTING)\n\n本文档仅适用于以下语言版本：\n 简体中文 \n\n问题（摘要）\n 由于Mellanox adapter registration内存限制导致Purescale CF 启动失败 \n\n症状\n从 \"db2instance -list\" 输出可以看到对应CF呈 \"ERROR\" 状态. 还可以看到下面的警告： \n\n$ db2cluster -cm -list -alert \n1. \nAlert: The cluster caching facility (CF) failed to start on the host.\nHost: 'AAPS3PPD'. CF: '128'.\n\n\ndb2diag.log 里面可以看到类似下面的错误信息，最重要的是看到错误代码 -2146893782:\n\n2014-08-14-16.45.27.527334+480 I11010E516 LEVEL: Error\nPID : 32560 TID : 47147934016672 PROC : ca-wdog 128 [db2pure]\nINSTANCE: db2pure NODE : 128\nHOSTNAME: HOSTNAME1\nFUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876\nDATA #1 : <preformatted>\nCA Configure command failed: mrb rc = (-2146893782)\nDATA #1 : <preformatted>\nIf a CF return code is displayed above and you wish to get\nmore information then please run the following command:\n\ndb2diag -cfrc <CF_errcode>\n\n2014-08-14-16.45.27.529735+480 E11527E420 LEVEL: Severe\nPID : 32560 TID : 47147934016672 PROC : ca-wdog 128 [db2pure]\nINSTANCE: db2pure NODE : 128\nHOSTNAME: HOSTNAME1\nFUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for CF, sqleSendCFServerConfig, probe:2687\nMESSAGE : ECF=0x97C9002A=-1748434902\nDATA #1 : String, 43 bytes\nUnable to configure and start the CF server\n\n\n原因\n这个问题很可能是由于Mellanox adapter registration 内存限制导致的。\n\n\n环境\nPurescale server on Linux\n\n\n\n诊断问题\n1.搜集 db2support . -purescale，至少得搜集问题发生时候的db2diag.log日志 \n\n2. 从cfdiag.xxx.log中, 可以看到 register_notify_memory() 返回错误代码 0x8009002a: \n\n\n2014-08-15-09.01.52.0037546570+480 E123456789A313 LEVEL : Error\nPID : 3363 TID : 1546295264\nHOSTNAME : HOSTNAME1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nregister_notify_memory() Local Memory Region Create (dat_lmr_create) failed. DAT Status: 0x30000\n\n2014-08-15-09.01.52.0037588678+480 E123456789A304 LEVEL : Error\nPID : 3363 TID : 1546295264\nHOSTNAME : HOSTNAME1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nregister_notify_memory() Notify Memory Registration failed on HCA 0. status: 0x8009002a\n\n2014-08-15-09.01.52.0037609689+480 E123456789A325 LEVEL : Error\nPID : 3363 TID : 1546295264\nHOSTNAME : HOSTNAME1\nFUNCTION : CA trace, log_error\nMESSAGE : CA server has encountered an error.\nDATA #1 :\nmgmnt_castart() CA Server start-up aborted due errors during start-up and initialization. Status: 0x8009002a\n\n\n解决问题\n参照信息中心下面链接中的第五步增加 Mellanox adapter registration内存大小： \n\n\nhttp://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html]\n\n将 CF 所在节点机器上的 Mellanox HCA 驱动的 mlx4_core 参数 log_mtts_per_seg 的值从3 (默认值) 增加到 7。 这需要使用root 用户， 具体步骤如下：\n\n\n * 如果是 SUSE:\n\n\necho \"options mlx4_core log_mtts_per_seg=7\" >> /etc/modprobe.conf.local \n * 如果是 RHEL:\n\n\necho \"options mlx4_core log_mtts_per_seg=7\" >> /etc/modprobe.d/modprobe.conf \noptions mlx4_core log_mtts_per_seg=7 \n\n上面的操作后需要重启操作系统使更高生效。 重启后可以使用下面的命令查看参数修改是否生效： \n\n<host-name>/sys/module/mlx4_core/parameters # cat /sys/module/mlx4_core/parameters/log_mtts_per_seg \n7 相关信息\n#Preinstallation checklist for DB2 pureScale Feature (Li [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n SQL1768N Unable to start HADR. Reason code = \"5\" while initializing high availability disaster recovery (HADR) \n\nCAUSE\nThe error might come while starting HADR for ex. db2 start hadr on database <db_name> as primary, when service port/socket is already used for other service.\n\nDIAGNOSING THE PROBLEM\nSocket allocated for HADR - \n\n$ cat /etc/services | grep -i 60070\ndb2_hadr_1 60070/tcp\n\ndb2 get db cfg for sample | grep -i HADR_LOCAL\nHADR local host name (HADR_LOCAL_HOST) = 9.182.192.146\nHADR local service name (HADR_LOCAL_SVC) = 60070\n\nCheck the db2diag.log file for errors. When it is socket in use problem, you should see message similar to following -\n\n2016-09-17-03.17.58.515457+330 I99076A572 LEVEL: Warning\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrBindAndListen, probe:20310\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nDATA #1 : String, 45 bytes\nRetrying bind, socket is in use. Retry count:\nDATA #2 : unsigned integer, 8 bytes\n5\n\n2016-09-17-03.17.58.513634+330 E98071A520 LEVEL: Error (OS)\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, oper system services, sqloPdbBindSocket, probe:20\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nCALLED : OS, -, bind\nOSERR : EADDRINUSE (67) \"Address already in use\"\n\n2016-09-17-03.17.58.514530+330 E98592A483 LEVEL: Severe\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, oper system services, sqloPdbBindSocket, probe:1131\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nDATA #1 : <preformatted>\nPort=[60070]\n\n2016-09-17-03.17.59.016412+330 I99649A459 LEVEL: Error\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrBindAndListen, probe:20320\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\n\n2016-09-17-03.17.59.017161+330 I100109A553 LEVEL: Error\nPID : 27066368 TID : 6027 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nHOSTNAME: ihubaix1.in.ibm.com\nEDUID : 6027 EDUNAME: db2hadrp.0.1 (SAMPLE) 0\nFUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetupListenerSocket, probe:22030\nMESSAGE : ZRC=0x810F001B=-2129723365=SQLO_ADDR_IN_USE \"Address already in use\"\nDATA #1 : <preformatted>\nFailed to setup listener socket on address=9.182.192.146:60070\n\n..\n\n2016-09-17-03.17.59.053310+330 I109827A890 LEVEL: Severe\nPID : 27066368 TID : 8140 PROC : db2sysc 0\nINSTANCE: XXXXXXX NODE : 000 DB : SAMPLE\nAPPHDL : 0-12174 APPID: *LOCAL.milindt.160916214757\nAUTHID : MILINDT HOSTNAME: ihubaix1.in.ibm.com\nEDUID : 8140 EDUNAME: db2agent (SAMPLE) 0\nFUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::FirstConnect, probe:8777\nDATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes\nsqlcaid : SQLCA sqlcabc: 136 sqlcode: -1768 sqlerrml: 1\nsqlerrmc: 5\nsqlerrp : SQL10012\nsqlerrd : (1) 0x00000000 (2) 0x00000005 (3) 0x00000000\n(4) 0x00000000 (5) 0x00000000 (6) 0x00000000\nsqlwarn : (1) (2) (3) (4) (5) (6)\n(7) (8) (9) (10) (11)\nsqlstate:\n\n\n\nRESOLVING THE PROBLEM\nCheck if the socket listed in db2diag.log is already in use using netstat and lsof commands. \n\n$ netstat -an | grep -i 60070\ntcp4 0 0 9.182.192.146.60070 9.182.192.147.41473 ESTABLISHED\ntcp4 0 0 9.182.192.146.60070 9.182.192.147.41474 ESTABLISHED\ntcp4 0 0 9.182.192.146.60070 *.* LISTEN\n\n# lsof -i :60070\nlsof: WARNING: compiled for AIX version 5.3.0.0; this is 7.1.0.0.\nCOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME\ndb2sysc 27066368 xxxxxxx 48u IPv4 0xf1000e0004ac33b8 0t0 TCP ihubaix1.in.ibm.com:db2_hadr_1 (LISTEN)\ndb2sysc 27066368 xxxxxxx 49u IPv4 0xf1000e00108ad3b8 0t0 TCP ihubaix1.in.ibm.com:db2_hadr_1->ihubaix2.in.ibm.com:41473 (ESTABLISHED)\ndb2sysc 27066368 xxxxxxx 50u IPv4 0xf1000e0005c7d3b8 0t0 TCP ihubaix1.in.ibm.com:db2_hadr_1->ihubaix2.in.ibm.com:41474 (ESTABLISHED)\n\nEither allocate new port for HADR_LOCAL_SVC or deallocate port 60070 from the existing service and re-issue the start hadr command.\n\nhttp://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.sql.doc/doc/msql01768n.html [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.sql.doc/doc/msql01768n.html] \n\n\n\nCross reference information Segment Product Component Platform Version Edition Information Management DB2 for Linux- UNIX and Windows", " TECHNOTE (FAQ)\n\nQUESTION\n What are known issues on Linux platforms related to DB2® database products ? \n\nANSWER\nKnown Issues with DB2 on Linux \n\n[/support/docview.wss?uid=swg21681093&amp;aid=1]\nBug ID [/support/docview.wss?uid=swg21681093&amp;aid=2]Description\nLinux Flavor [/support/docview.wss?uid=swg21681093&amp;aid=3]\nComments 1076574 DB2's 'db2syc' process exhibits memory leak. Redhat v6 DB2 'db2sysc' process will see memory leak. Eventually, RAM and swap will be 100% consumed. The machine will be non-responsive. This memory is released when DB2 engine is stopped with 'db2stop'.\n\nThis is a RedHat Linux issue and is discussed here:https://access.redhat.com/support/cases/01054560/ [https://access.redhat.com/support/cases/01054560/] \n\nThis problem is already fixed by RedHat. The detailed description of all the Redhat Linux versions affected by this bug and fix details are available at:https://rhn.redhat.com/errata/RHBA-2014-0470.html [https://rhn.redhat.com/errata/RHBA-2014-0470.html] 1042807 32-bit applications running on 64-bit platforms where issuing msgrcv with -ve message type hangs with error: \nerror: msgrcv: No message of the desired type. Redhat v7\nkernel-3.10.0-54.0.1.e17.x86_64 32-bit application does not work on RHEL 7.0 with 64-bit DB2 engine. When the sample programs under sqllib/samples/c/ like inattach.c or dbinfo.c is compiled by bldapp with BITWIDTH=32, it hangs in sqlorqueInternal.\n\nThis is a RedHat Linux issue and is discussed here:\nhttps://access.redhat.com/solutions/1202773 [https://access.redhat.com/solutions/1202773]\n\nThis problem will be fixed by RedHat in v7.1 1264533 DB2 Panic, due to removed IPC resources. Redhat v7.2 The problem is caused by logind removing IPC resources owned by user when this user logs off. The bug is described here:\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1264533 [https://bugzilla.redhat.com/show_bug.cgi?id=1264533]\n\nLocal Fix:\nAdd the following setting to file /etc/systemd/logind.conf\nRemoveIPC=no 948149 db2dart reports incorrect container tag for container which resides on XFS SLES 12 This problem exists for XFS and only if container is opened in Direct IO mode. In reality the container tag is not corrupted but result buffer will return empty after pread call, which did not report any errors. More information here:\nhttps://bugzilla.linux.ibm.com/show_bug.cgi?id=131069 [https://bugzilla.linux.ibm.com/show_bug.cgi?id=131069] \n\nThe problem is fixed in \nkernel-default-3.12.32-33.1.x86_64.rpm\n\n1165277 db2 local connections may hang in semop function Redhat/CentOS v6.6. The problem is caused by a IPC bug, first seen in kernel kernel 2.6.32-434.el6. More information here: https://bugzilla.linux.ibm.com/show_bug.cgi?id=119049 [https://bugzilla.linux.ibm.com/show_bug.cgi?id=119049]\n\nFixed in https://rhn.redhat.com/errata/RHSA-2015-1272.html [https://rhn.redhat.com/errata/RHSA-2015-1272.html]\n\nLocal Fix:\nConfigure local clients' connections through TCP/IP loopback." ]

[ [ "2a", "CF 启动失败; register_notify_memory; -2146893782; 0x8009002a TECHNOTE (TROUBLESHOOTING) 本文档仅适用于以下语言版本： 简体中文 问题（摘要）" ], [ "2b", " 由于Mellanox adapter registration内存限制导致Purescale CF 启动失败 症状" ], [ "2c", "从 \"db2instance -list\" 输出可以看到对应CF呈 \"ERROR\" 状态. 还可以看到下面的警告：" ], [ "2d", "$ db2cluster -cm -list -alert 1." ], [ "2e", "Alert: The cluster caching facility (CF) failed to start on the host. Host: 'AAPS3PPD'. CF: '128'." ], [ "2f", "db2diag.log 里面可以看到类似下面的错误信息，最重要的是看到错误代码 -2146893782:" ], [ "2g", "2014-08-14-16.45.27.527334+480 I11010E516 LEVEL: Error" ], [ "2h", "PID : 32560 TID : 47147934016672 PROC : ca-wdog 128 [db2pure]" ], [ "2i", "INSTANCE: db2pure NODE : 128 HOSTNAME: HOSTNAME1" ], [ "2j", "FUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876" ], [ "2k", "DATA #1 : <preformatted>" ], [ "2l", "CA Configure command failed: mrb rc = (-2146893782)" ], [ "2m", "DATA #1 : <preformatted>" ], [ "2n", "If a CF return code is displayed above and you wish to get" ], [ "2o", "more information then please run the following command:" ], [ "2p", "db2diag -cfrc <CF_errcode>" ], [ "2q", "2014-08-14-16.45.27.529735+480 E11527E420 LEVEL: Severe" ], [ "2r", "PID : 32560 TID : 47147934016672 PROC : ca-wdog 128 [db2pure]" ], [ "2s", "INSTANCE: db2pure NODE : 128 HOSTNAME: HOSTNAME1" ], [ "2t", "FUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for CF, sqleSendCFServerConfig, probe:2687" ], [ "2u", "MESSAGE : ECF=0x97C9002A=-1748434902" ], [ "2v", "DATA #1 : String, 43 bytes" ], [ "2w", "Unable to configure and start the CF server 原因" ], [ "2x", "这个问题很可能是由于Mellanox adapter registration 内存限制导致的。 环境" ], [ "2y", "Purescale server on Linux 诊断问题" ], [ "2z", "1.搜集 db2support . -purescale，至少得搜集问题发生时候的db2diag.log日志 2." ], [ "2aa", "从cfdiag.xxx.log中, 可以看到 register_notify_memory() 返回错误代码 0x8009002a:" ], [ "2ab", "2014-08-15-09.01.52.0037546570+480 E123456789A313 LEVEL : Error" ], [ "2ac", "PID : 3363 TID : 1546295264" ], [ "2ad", "HOSTNAME : HOSTNAME1" ], [ "2ae", "FUNCTION : CA trace, log_error" ], [ "2af", "MESSAGE : CA server has encountered an error." ], [ "2ag", "DATA #1 :" ], [ "2ah", "register_notify_memory() Local Memory Region Create (dat_lmr_create) failed." ], [ "2ai", "DAT Status: 0x30000" ], [ "2aj", "2014-08-15-09.01.52.0037588678+480 E123456789A304 LEVEL : Error" ], [ "2ak", "PID : 3363 TID : 1546295264" ], [ "2al", "HOSTNAME : HOSTNAME1" ], [ "2am", "FUNCTION : CA trace, log_error" ], [ "2an", "MESSAGE : CA server has encountered an error." ], [ "2ao", "DATA #1 :" ], [ "2ap", "register_notify_memory() Notify Memory Registration failed on HCA 0. status: 0x8009002a" ], [ "2aq", "2014-08-15-09.01.52.0037609689+480 E123456789A325 LEVEL : Error" ], [ "2ar", "PID : 3363 TID : 1546295264" ], [ "2as", "HOSTNAME : HOSTNAME1" ], [ "2at", "FUNCTION : CA trace, log_error" ], [ "2au", "MESSAGE : CA server has encountered an error." ], [ "2av", "DATA #1 :" ], [ "2aw", "mgmnt_castart() CA Server start-up aborted due errors during start-up and initialization. Status: 0x8009002a 解决问题" ], [ "2ax", "参照信息中心下面链接中的第五步增加 Mellanox adapter registration内存大小： http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html]" ], [ "2ay", "将 CF 所在节点机器上的 Mellanox HCA 驱动的 mlx4_core 参数 log_mtts_per_seg 的值从3 (默认值) 增加到 7。 这需要使用root 用户， 具体步骤如下：" ], [ "2az", " * 如果是 SUSE:" ], [ "2ba", "echo \"options mlx4_core log_mtts_per_seg=7\" >> /etc/modprobe.conf.local" ], [ "2bb", " * 如果是 RHEL:" ], [ "2bc", "echo \"options mlx4_core log_mtts_per_seg=7\" >> /etc/modprobe.d/modprobe.conf" ], [ "2bd", "options mlx4_core log_mtts_per_seg=7 上面的操作后需要重启操作系统使更高生效。 重启后可以使用下面的命令查看参数修改是否生效：" ], [ "2be", "<host-name>/sys/module/mlx4_core/parameters # cat /sys/module/mlx4_core/parameters/log_mtts_per_seg 7 相关信息" ], [ "2bf", "#Preinstallation checklist for DB2 pureScale Feature (Li [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0057204.html]" ] ]

[ "0b", "0m", "0s", "0t", "0ac", "2f", "2g", "2l" ]

[ "IMF50 PRODUCT DOCUMENTATION\n\nABSTRACT\n This document explains how to install Worklight Server 5.0.6 into a set of WebSphere Application Server Network Deployment (WAS ND) servers. \n\nCONTENT\nFor a general description of the installation process, see the documentation chapter at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_installation.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_installation.html]. \n\nInstallation into an unmanaged server (that is, a server which is not under the control of a Deployment Manager) works exactly like in version 5.0.5: In Installation Manager, in the panel where you specify the WAS installation directory, you select the “application server” profile and then the specific server. When Installation Manager is done, you need to restart the WAS server.\n\nThe rest of this document deals with installing into a set of managed servers, that is, servers that are under the control of a Deployment Manager. Before version 5.0.6, this case was only supported through manual installation steps. Starting with version 5.0.6, a large part of the installation can be performed through Installation Manager. \n\nHow does it work?\n\n\nYou have to run the Worklight Server installer, through Installation Manager, on the machine where the Deployment Manager is running. Note the following points.\n\n\n 1. In the installer panel where you specify the database type, don't select Apache Derby. Worklight supports Apache Derby only in “embedded” mode, and this choice is incompatible with deployment through WAS ND. \n 2. In the installer panel where you specify the WAS installation directory, select the Deployment Manager profile. \n 3. Warning! If you run the installer on the machine where the Deployment Manager is running and select an application server profile and then a single managed server, you will get a warning and at the end things will not work, because the Deployment Manager overwrites the configuration of that server. \n 4. Warning! If you run the installer on a different machine and select an application server profile and then a single managed server, you will not get a warning but nevertheless things will not work, for the same reason. \n 5. After selecting the profile, pick a scope, that is, the type of set of target servers. The available scopes are: * Cell: This will install Worklight Server into all application servers of the cell. \n * Cluster: You specify the name of a cluster, and this will install Worklight Server into all application server of the cluster. \n * Node (excluding clusters): You specify the name of a node, and this will install Worklight Server into all application servers of the node that are not in some cluster. \n * Server: You specify the name of a server (not in a cluster), and this will install Worklight Server into the specified server.\n \n \n 6. After running the installer, you have to restart those target servers that were running. This is documented in the documentation section “Completing the installation”, at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_completing_the_installation.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_completing_the_installation.html].\n\n\nThe installation will not affect servers outside the specified set of servers. The JDBC providers, JDBC datasources, and shared libraries are defined with the specified scope. The entities which have a cell-wide scope (the applications and, for DB2, the authentication alias) have a suffix in their name that makes them unique. So, you can install Worklight Server in different configurations, or even different versions of Worklight Server, in different clusters of the same cell. \n\nNote: The “Test connection” button for the JDBC datasources in the WAS administration console of the Deployment Manager may not work. This is normal, since the JDBC driver is installed only in the specified set of application servers. \n\nAdditional Configuration Needed \n\nConfiguration of the data sources \n\nYou need to turn off transactions on the Worklight data source, otherwise you may see non-fatal exceptions in the WAS SystemOut.log, such as: * \n * \n\n\nYou do this in the WAS administration console, Resources > JDBC > Data sources > Worklight database > WebSphere Application Server data source properties, by enabling the “Non-transactional data source” checkbox. Configuration of the public URL \n\nWhen you use a HTTP server in the front end, there is a single public URL for the entire set of servers. Customization is needed: \n\n * For the Worklight console, in the worklight.properties file in the worklight.war file. See documentation section “Configuring the IBM Worklight Server location” at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fr_configuring_the_ibm_worklight_server_location.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fr_configuring_the_ibm_worklight_server_location.html], \n * In the application-descriptor.xml file of each app, set the <worklightServerRootURL> element, and redeploy the app. \n * For Application Center, set the JVM system properties ibm.appcenter.proxy.host, ibm.appcenter.proxy.port, ibm.appcenter.proxy.protocol. See documentation section “Configuring the endpoint of the application resources (JVM server custom properties)” at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fappcenter%2Ft_ac_endpoint_wasfull.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fappcenter%2Ft_ac_endpoint_wasfull.html]. In the WAS administration console, you find these JVM system properties settings at Server > Server Types > Websphere application servers > server name > Java and Process Management > Process definition > Java Virtual Machine > Custom Properties.\n\n\nAdding Another Server \n\nWhen you add another server to a cluster with Worklight server installed, you need to manually repeat the configuration of the following: * JVM system properties worklight.home, android.aapt.dir, ibm.appcenter.proxy.host, ibm.appcenter.proxy.port, ibm.appcenter.proxy.protocol, \n * Web container custom property com.ibm.ws.webcontainer.invokeflushafterservice.\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Mobile- Speech and Enterprise Access IBM Mobile Foundation Installation AIX, HP-UX, Linux, Solaris, Windows 5.0.6 Consumer, Enterprise", "JDBC; JDBC Adapter; JDBC driver; Isolate; Adapter for JDBC TECHNOTE (FAQ)\n\nQUESTION\n What is the recommended approach to establish connections with different JDBC driver versions on the same database vendor through WebSphere Adapter for JDBC in an application? Note these specific database versions from the same database vendor may be the same or different. For example, both Oracle 9 and Oracle 11 JDBC driver versions coexists and are also used to connect to either Oracle 9i database or Oracle 11g in an application with a WebSphere Adapter for JDBC. \n\nANSWER\nThere are two recommendations to use WebSphere Adapter for JDBC in above scenario. \n\n1. In WebSphere Process Server version 6.2 and prior version, you can not use different JDBC drivers in one application. You have to define an application by using \"databaseURL\" mode with embedded adapter to connect to one database such as Oracle 9i. And define the other application by using \"databaseURL\" mode with embedded adapter to connect to the other database such as Oracle 11g to use different JDBC driver. \n\n2. In WebSphere Process Server version 7.0 and later version, you can achieve the requirement in one application by using standalone adapter and two data sources with different database version (JDBC drivers). The property \"Isolate this resource provider\" of data source must be enabled when defining the JDBC providers. You can refer to the attached document to implement the solution. \n\nIsolation.zip [/support/docview.wss?uid=swg21454021&aid=2] [/support/docview.wss?uid=swg21454021&aid=1]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The setting defaultRowPrefetch is used to help increase the performance of queries to Oracle databases and we sometimes find customers who want to enable this feature for Oracle database connections to increase the prefetched rows. \n\nOracle JDBC drivers have a feature built in as an extension that allows you to set the number of rows that are prefetched while the full result set is being formulated. This is to reduce the number of trips back and forth to the database. \n\n\nSYMPTOM\nIf defaultRowPrefetch is set as a custom property on the datasource, this will not work as the defaultRowPrefetch is not a datasource property but a property on the connection itself .\n\n\nCAUSE\ndefaultRowPrefetch is a property of the connection and not of the datasource\n\nENVIRONMENT\nWebSphere Application Server using an Oracle JDBC driver\n\nDIAGNOSING THE PROBLEM\nCustomer sets this property and does not see it work. This may result in longer times to getting the full result set and more round trips to the database.\n\nRESOLVING THE PROBLEM\nThe Oracle defaultRowPrefetch can be set in an attempt to speed up queries to a database that return multiple rows. But, it cannot be set as a custom property in a datasource. Please see below:\n\nThe way to set this connection property is as follows:. \n\n\n\n\nYou cannot set defaultRowPrefetch as a JVM property. It would have to be named \noracle.jdbc.defaultRowPrefetch for that to work. You can only use this property \nby loading it into a Properties object in the code and then calling \ngetConnection with the Properties object.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WebSphere Application Server does not support data encryption for data sources using the Oracle JDBC Thin driver. \n\nCAUSE\nThe Oracle Advanced Security (OAS) option enables data encryption. Both Oracle JDBC OCI Thin and Thick support some of the features of OAS. This support has been available since Oracle 8.1.6 and onwards.\nThe OAS parameters for data encryption are:\n\noracle.net.encryption_client\noracle.net.encryption_types_client\noracle.net.crypto_checksum_client\noracle.net.crypto_checksum_types_client\n\nWhen using the Oracle JDBC Thin driver, Oracle offers encryption in the oracle.net package. The parameters are set through the Java™ properties object, which can be used in opening database connection; only the DriverManager has the getConnection interface that allows the properties object to be passed to the getConnection.\n\nWebSphere Application Server Connection Manager uses the OracleConnectionPoolDataSource for the data source implementation. This OracleConnectionPoolDataSource does have the interface getConnection (URL, prop). It is now possible to pass the connection parameters to the Oracle driver. For information on how to set these parameters see the technote, Using Oracle JDBC driver specific properties through a datasource. [http://www-01.ibm.com/support/docview.wss?uid=swg21197705]\n\n\n\nRESOLVING THE PROBLEM\n \n\n 1. Use the Oracle JDBC OCI driver. The parameters can be enabled in the SQLNET.ORA file (Oracle Network client's configuration file on the WebSphere Application Server system). \n \n \n 2. A second option is to configure the above parameters as a custom property on the data source using the procedure described in technote Using Oracle JDBC driver specific properties through a datasource. [http://www-01.ibm.com/support/docview.wss?uid=swg21197705]\n\n\nHere is an example \n\nName: connectionProperties \nValue: oracle.net.encryption_client=REQUESTED;oracle.net.encryption_types_client=RC4_40;oracle.net.crypto_checksum_client=REQUESTED;oracle.net.crypto_checksum_types_client=MD5 \n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * This APAR describes the issues that customers encountered with\n IBM WebSphere Application Server Version 7.0.These issues were\n resolved as information center updates in January, 2010.\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: This APAR lists provides a cumulative list *\n * of the documentation issues for January *\n * 2010 that affect users of IBM WebSphere *\n * Application Server Version 7.0. *\n ****************************************************************\n * PROBLEM DESCRIPTION: The Information Centers for WebSphere *\n * Application Server Version 7.0 need *\n * to be updated to address inaccurate, *\n * imprecise, or vague information. In *\n * addition, the information centers *\n * need to include customer enhancement *\n * requests for January 2010 problem *\n * management records (PMR). *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n See the Problem Conclusion section for a description of the\n issue, which was described in a customer PMR, and the\n documentation change or changes that addressed the issue.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Note: We update our information centers monthly. The following\n Version 7.0 modifications will be available in the January\n 2010 update to the Information Centers. To access the\n latest on-line documentation, go to the product library page\n at http://www.ibm.com/software/webservers/appserv/library and\n select the version and product that is appropriate for your\n WebSphere Application Server environment.\n The modified documentation will be available in the January\n 2010 update to the Information Centers.\n \n The following Version 7.0 issues will be addressed:\n \n ID: PM03896\n Problem: You can configure a timeout for connection validation\n by the Java Database Connectivity (JDBC) driver through a\n data source custom property in the data source configuration\n panels of the administrative console. By default, connection\n validation is disabled. When you save the configuration for\n the data source, the administrative console supplies only the\n option that is selected. In the case of an Oracle data\n source, the Validation by JDBC Driver selection item in the\n administrative console is disabled unless the\n validateNewConnectionTimeout property is added to the custom\n properties for the WebSphere Application Server data source.\n \n The Information Center for WebSphere Application Server does\n not include information on this relationship. It might be\n confusing that the \"Validation by JDBC Driver\" option in the\n administrative console is disabled when an Oracle data source\n is used.\n \n Resolution: The \"Configuring connection validation timeout\"\n and \"WebSphere Application Server data source properties\"\n topics will include a note to indicate that the\n validateNewConnectionTimeout property is required for an\n Oracle data source. Both topics will include the following note:\n \n Avoid Trouble: For an Oracle data source, Validation by JDBC\n Driver displays on the administrative console only after the\n validateNewConnectionTimeout property is added to the custom\n properties of WebSphere Application Server data source\n properties. The validateNewConnectionTimeout property is used\n for JDBC 4.0 driver validation and can be specified using the\n administrative console.\n \n ------------\n ID: 633356\n Problem: When you use the MapEnvEntryForWebMod option for the\n AdminApp object install, installInteractive, edit,\n editInteractive, update, and updateInteractive commands using\n wsadmin scripting, you need to be aware of using \"null\" in the\n description. The MapEnvEntryForWebMod option edits the\n env-entry value of the Web module and you can use this option\n to edit the value of env-entry in the web.xml file. If you\n leave the description as \"null\" after running the default\n bindings, WASX7017E and WASX7111E exceptions occur. You must\n change the description to \"*\" to avoid the exceptions. The\n Information Center for WebSphere Application Server does not\n describe this issue.\n \n Resolution: The \"Options for the AdminApp object install,\n installInteractive, edit, editInteractive, update, and\n updateInteractive commands using wsadmin scripting\" topic\n will be updated. Specifically, the MapEnvEntryForWebMod\n information will be updated to add a note about using a \"null\"\n value for the description. The following note will be added:\n \n Avoid Trouble: After running the default bindings, change the\n null value to * before you run this task. The * value is the\n wildcard value that lets any description be a match. If you\n leave the value as null, WASX7017E and WASX7111E exceptions\n will occur when you run the MapEnvEntryForWebMod task.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM03896\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE APP S\n \n \n * REPORTED COMPONENT ID\n 5724J0800\n \n \n * REPORTED RELEASE\n 700\n \n \n * STATUS\n CLOSED DOC\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2009-12-18\n \n \n * CLOSED DATE\n 2009-12-31\n \n \n * LAST MODIFIED DATE\n 2010-01-13\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS" ]

[ [ "2a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "2b", " The setting defaultRowPrefetch is used to help increase the performance of queries to Oracle databases and we sometimes find customers who want to enable this feature for Oracle database connections to increase the prefetched rows." ], [ "2c", "Oracle JDBC drivers have a feature built in as an extension that allows you to set the number of rows that are prefetched while the full result set is being formulated." ], [ "2d", "This is to reduce the number of trips back and forth to the database. SYMPTOM" ], [ "2e", "If defaultRowPrefetch is set as a custom property on the datasource, this will not work as the defaultRowPrefetch is not a datasource property but a property on the connection itself . CAUSE" ], [ "2f", "defaultRowPrefetch is a property of the connection and not of the datasource ENVIRONMENT" ], [ "2g", "WebSphere Application Server using an Oracle JDBC driver" ], [ "2h", "DIAGNOSING THE PROBLEM" ], [ "2i", "Customer sets this property and does not see it work." ], [ "2j", "This may result in longer times to getting the full result set and more round trips to the database." ], [ "2k", "RESOLVING THE PROBLEM" ], [ "2l", "The Oracle defaultRowPrefetch can be set in an attempt to speed up queries to a database that return multiple rows." ], [ "2m", "But, it cannot be set as a custom property in a datasource." ], [ "2n", "Please see below:" ], [ "2o", "The way to set this connection property is as follows:." ], [ "2p", "You cannot set defaultRowPrefetch as a JVM property." ], [ "2q", "It would have to be named" ], [ "2r", "oracle.jdbc.defaultRowPrefetch for that to work." ], [ "2s", "You can only use this property" ], [ "2t", "by loading it into a Properties object in the code and then calling" ], [ "2u", "getConnection with the Properties object." ] ]

[ "2e", "2h", "2l", "2u", "3j", "3m", "3p" ]

[ "IMF50 PRODUCT DOCUMENTATION\n\nABSTRACT\n This document explains how to install Worklight Server 5.0.6 into a set of WebSphere Application Server Network Deployment (WAS ND) servers. \n\nCONTENT\nFor a general description of the installation process, see the documentation chapter at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_installation.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_installation.html]. \n\nInstallation into an unmanaged server (that is, a server which is not under the control of a Deployment Manager) works exactly like in version 5.0.5: In Installation Manager, in the panel where you specify the WAS installation directory, you select the “application server” profile and then the specific server. When Installation Manager is done, you need to restart the WAS server.\n\nThe rest of this document deals with installing into a set of managed servers, that is, servers that are under the control of a Deployment Manager. Before version 5.0.6, this case was only supported through manual installation steps. Starting with version 5.0.6, a large part of the installation can be performed through Installation Manager. \n\nHow does it work?\n\n\nYou have to run the Worklight Server installer, through Installation Manager, on the machine where the Deployment Manager is running. Note the following points.\n\n\n 1. In the installer panel where you specify the database type, don't select Apache Derby. Worklight supports Apache Derby only in “embedded” mode, and this choice is incompatible with deployment through WAS ND. \n 2. In the installer panel where you specify the WAS installation directory, select the Deployment Manager profile. \n 3. Warning! If you run the installer on the machine where the Deployment Manager is running and select an application server profile and then a single managed server, you will get a warning and at the end things will not work, because the Deployment Manager overwrites the configuration of that server. \n 4. Warning! If you run the installer on a different machine and select an application server profile and then a single managed server, you will not get a warning but nevertheless things will not work, for the same reason. \n 5. After selecting the profile, pick a scope, that is, the type of set of target servers. The available scopes are: * Cell: This will install Worklight Server into all application servers of the cell. \n * Cluster: You specify the name of a cluster, and this will install Worklight Server into all application server of the cluster. \n * Node (excluding clusters): You specify the name of a node, and this will install Worklight Server into all application servers of the node that are not in some cluster. \n * Server: You specify the name of a server (not in a cluster), and this will install Worklight Server into the specified server.\n \n \n 6. After running the installer, you have to restart those target servers that were running. This is documented in the documentation section “Completing the installation”, at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_completing_the_installation.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_completing_the_installation.html].\n\n\nThe installation will not affect servers outside the specified set of servers. The JDBC providers, JDBC datasources, and shared libraries are defined with the specified scope. The entities which have a cell-wide scope (the applications and, for DB2, the authentication alias) have a suffix in their name that makes them unique. So, you can install Worklight Server in different configurations, or even different versions of Worklight Server, in different clusters of the same cell. \n\nNote: The “Test connection” button for the JDBC datasources in the WAS administration console of the Deployment Manager may not work. This is normal, since the JDBC driver is installed only in the specified set of application servers. \n\nAdditional Configuration Needed \n\nConfiguration of the data sources \n\nYou need to turn off transactions on the Worklight data source, otherwise you may see non-fatal exceptions in the WAS SystemOut.log, such as: * \n * \n\n\nYou do this in the WAS administration console, Resources > JDBC > Data sources > Worklight database > WebSphere Application Server data source properties, by enabling the “Non-transactional data source” checkbox. Configuration of the public URL \n\nWhen you use a HTTP server in the front end, there is a single public URL for the entire set of servers. Customization is needed: \n\n * For the Worklight console, in the worklight.properties file in the worklight.war file. See documentation section “Configuring the IBM Worklight Server location” at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fr_configuring_the_ibm_worklight_server_location.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fr_configuring_the_ibm_worklight_server_location.html], \n * In the application-descriptor.xml file of each app, set the <worklightServerRootURL> element, and redeploy the app. \n * For Application Center, set the JVM system properties ibm.appcenter.proxy.host, ibm.appcenter.proxy.port, ibm.appcenter.proxy.protocol. See documentation section “Configuring the endpoint of the application resources (JVM server custom properties)” at http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fappcenter%2Ft_ac_endpoint_wasfull.html [http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fappcenter%2Ft_ac_endpoint_wasfull.html]. In the WAS administration console, you find these JVM system properties settings at Server > Server Types > Websphere application servers > server name > Java and Process Management > Process definition > Java Virtual Machine > Custom Properties.\n\n\nAdding Another Server \n\nWhen you add another server to a cluster with Worklight server installed, you need to manually repeat the configuration of the following: * JVM system properties worklight.home, android.aapt.dir, ibm.appcenter.proxy.host, ibm.appcenter.proxy.port, ibm.appcenter.proxy.protocol, \n * Web container custom property com.ibm.ws.webcontainer.invokeflushafterservice.\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Mobile- Speech and Enterprise Access IBM Mobile Foundation Installation AIX, HP-UX, Linux, Solaris, Windows 5.0.6 Consumer, Enterprise", "JDBC; JDBC Adapter; JDBC driver; Isolate; Adapter for JDBC TECHNOTE (FAQ)\n\nQUESTION\n What is the recommended approach to establish connections with different JDBC driver versions on the same database vendor through WebSphere Adapter for JDBC in an application? Note these specific database versions from the same database vendor may be the same or different. For example, both Oracle 9 and Oracle 11 JDBC driver versions coexists and are also used to connect to either Oracle 9i database or Oracle 11g in an application with a WebSphere Adapter for JDBC. \n\nANSWER\nThere are two recommendations to use WebSphere Adapter for JDBC in above scenario. \n\n1. In WebSphere Process Server version 6.2 and prior version, you can not use different JDBC drivers in one application. You have to define an application by using \"databaseURL\" mode with embedded adapter to connect to one database such as Oracle 9i. And define the other application by using \"databaseURL\" mode with embedded adapter to connect to the other database such as Oracle 11g to use different JDBC driver. \n\n2. In WebSphere Process Server version 7.0 and later version, you can achieve the requirement in one application by using standalone adapter and two data sources with different database version (JDBC drivers). The property \"Isolate this resource provider\" of data source must be enabled when defining the JDBC providers. You can refer to the attached document to implement the solution. \n\nIsolation.zip [/support/docview.wss?uid=swg21454021&aid=2] [/support/docview.wss?uid=swg21454021&aid=1]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The setting defaultRowPrefetch is used to help increase the performance of queries to Oracle databases and we sometimes find customers who want to enable this feature for Oracle database connections to increase the prefetched rows. \n\nOracle JDBC drivers have a feature built in as an extension that allows you to set the number of rows that are prefetched while the full result set is being formulated. This is to reduce the number of trips back and forth to the database. \n\n\nSYMPTOM\nIf defaultRowPrefetch is set as a custom property on the datasource, this will not work as the defaultRowPrefetch is not a datasource property but a property on the connection itself .\n\n\nCAUSE\ndefaultRowPrefetch is a property of the connection and not of the datasource\n\nENVIRONMENT\nWebSphere Application Server using an Oracle JDBC driver\n\nDIAGNOSING THE PROBLEM\nCustomer sets this property and does not see it work. This may result in longer times to getting the full result set and more round trips to the database.\n\nRESOLVING THE PROBLEM\nThe Oracle defaultRowPrefetch can be set in an attempt to speed up queries to a database that return multiple rows. But, it cannot be set as a custom property in a datasource. Please see below:\n\nThe way to set this connection property is as follows:. \n\n\n\n\nYou cannot set defaultRowPrefetch as a JVM property. It would have to be named \noracle.jdbc.defaultRowPrefetch for that to work. You can only use this property \nby loading it into a Properties object in the code and then calling \ngetConnection with the Properties object.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WebSphere Application Server does not support data encryption for data sources using the Oracle JDBC Thin driver. \n\nCAUSE\nThe Oracle Advanced Security (OAS) option enables data encryption. Both Oracle JDBC OCI Thin and Thick support some of the features of OAS. This support has been available since Oracle 8.1.6 and onwards.\nThe OAS parameters for data encryption are:\n\noracle.net.encryption_client\noracle.net.encryption_types_client\noracle.net.crypto_checksum_client\noracle.net.crypto_checksum_types_client\n\nWhen using the Oracle JDBC Thin driver, Oracle offers encryption in the oracle.net package. The parameters are set through the Java™ properties object, which can be used in opening database connection; only the DriverManager has the getConnection interface that allows the properties object to be passed to the getConnection.\n\nWebSphere Application Server Connection Manager uses the OracleConnectionPoolDataSource for the data source implementation. This OracleConnectionPoolDataSource does have the interface getConnection (URL, prop). It is now possible to pass the connection parameters to the Oracle driver. For information on how to set these parameters see the technote, Using Oracle JDBC driver specific properties through a datasource. [http://www-01.ibm.com/support/docview.wss?uid=swg21197705]\n\n\n\nRESOLVING THE PROBLEM\n \n\n 1. Use the Oracle JDBC OCI driver. The parameters can be enabled in the SQLNET.ORA file (Oracle Network client's configuration file on the WebSphere Application Server system). \n \n \n 2. A second option is to configure the above parameters as a custom property on the data source using the procedure described in technote Using Oracle JDBC driver specific properties through a datasource. [http://www-01.ibm.com/support/docview.wss?uid=swg21197705]\n\n\nHere is an example \n\nName: connectionProperties \nValue: oracle.net.encryption_client=REQUESTED;oracle.net.encryption_types_client=RC4_40;oracle.net.crypto_checksum_client=REQUESTED;oracle.net.crypto_checksum_types_client=MD5 \n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * This APAR describes the issues that customers encountered with\n IBM WebSphere Application Server Version 7.0.These issues were\n resolved as information center updates in January, 2010.\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: This APAR lists provides a cumulative list *\n * of the documentation issues for January *\n * 2010 that affect users of IBM WebSphere *\n * Application Server Version 7.0. *\n ****************************************************************\n * PROBLEM DESCRIPTION: The Information Centers for WebSphere *\n * Application Server Version 7.0 need *\n * to be updated to address inaccurate, *\n * imprecise, or vague information. In *\n * addition, the information centers *\n * need to include customer enhancement *\n * requests for January 2010 problem *\n * management records (PMR). *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n See the Problem Conclusion section for a description of the\n issue, which was described in a customer PMR, and the\n documentation change or changes that addressed the issue.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Note: We update our information centers monthly. The following\n Version 7.0 modifications will be available in the January\n 2010 update to the Information Centers. To access the\n latest on-line documentation, go to the product library page\n at http://www.ibm.com/software/webservers/appserv/library and\n select the version and product that is appropriate for your\n WebSphere Application Server environment.\n The modified documentation will be available in the January\n 2010 update to the Information Centers.\n \n The following Version 7.0 issues will be addressed:\n \n ID: PM03896\n Problem: You can configure a timeout for connection validation\n by the Java Database Connectivity (JDBC) driver through a\n data source custom property in the data source configuration\n panels of the administrative console. By default, connection\n validation is disabled. When you save the configuration for\n the data source, the administrative console supplies only the\n option that is selected. In the case of an Oracle data\n source, the Validation by JDBC Driver selection item in the\n administrative console is disabled unless the\n validateNewConnectionTimeout property is added to the custom\n properties for the WebSphere Application Server data source.\n \n The Information Center for WebSphere Application Server does\n not include information on this relationship. It might be\n confusing that the \"Validation by JDBC Driver\" option in the\n administrative console is disabled when an Oracle data source\n is used.\n \n Resolution: The \"Configuring connection validation timeout\"\n and \"WebSphere Application Server data source properties\"\n topics will include a note to indicate that the\n validateNewConnectionTimeout property is required for an\n Oracle data source. Both topics will include the following note:\n \n Avoid Trouble: For an Oracle data source, Validation by JDBC\n Driver displays on the administrative console only after the\n validateNewConnectionTimeout property is added to the custom\n properties of WebSphere Application Server data source\n properties. The validateNewConnectionTimeout property is used\n for JDBC 4.0 driver validation and can be specified using the\n administrative console.\n \n ------------\n ID: 633356\n Problem: When you use the MapEnvEntryForWebMod option for the\n AdminApp object install, installInteractive, edit,\n editInteractive, update, and updateInteractive commands using\n wsadmin scripting, you need to be aware of using \"null\" in the\n description. The MapEnvEntryForWebMod option edits the\n env-entry value of the Web module and you can use this option\n to edit the value of env-entry in the web.xml file. If you\n leave the description as \"null\" after running the default\n bindings, WASX7017E and WASX7111E exceptions occur. You must\n change the description to \"*\" to avoid the exceptions. The\n Information Center for WebSphere Application Server does not\n describe this issue.\n \n Resolution: The \"Options for the AdminApp object install,\n installInteractive, edit, editInteractive, update, and\n updateInteractive commands using wsadmin scripting\" topic\n will be updated. Specifically, the MapEnvEntryForWebMod\n information will be updated to add a note about using a \"null\"\n value for the description. The following note will be added:\n \n Avoid Trouble: After running the default bindings, change the\n null value to * before you run this task. The * value is the\n wildcard value that lets any description be a match. If you\n leave the value as null, WASX7017E and WASX7111E exceptions\n will occur when you run the MapEnvEntryForWebMod task.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM03896\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE APP S\n \n \n * REPORTED COMPONENT ID\n 5724J0800\n \n \n * REPORTED RELEASE\n 700\n \n \n * STATUS\n CLOSED DOC\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2009-12-18\n \n \n * CLOSED DATE\n 2009-12-31\n \n \n * LAST MODIFIED DATE\n 2010-01-13\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS" ]

[ [ "3a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " WebSphere Application Server does not support data encryption for data sources using the Oracle JDBC Thin driver. CAUSE" ], [ "3c", "The Oracle Advanced Security (OAS) option enables data encryption." ], [ "3d", "Both Oracle JDBC OCI Thin and Thick support some of the features of OAS." ], [ "3e", "This support has been available since Oracle 8.1.6 and onwards." ], [ "3f", "The OAS parameters for data encryption are: oracle.net.encryption_client oracle.net.encryption_types_client oracle.net.crypto_checksum_client oracle.net.crypto_checksum_types_client" ], [ "3g", "When using the Oracle JDBC Thin driver, Oracle offers encryption in the oracle.net package." ], [ "3h", "The parameters are set through the Java™ properties object, which can be used in opening database connection; only the DriverManager has the getConnection interface that allows the properties object to be passed to the getConnection." ], [ "3i", "WebSphere Application Server Connection Manager uses the OracleConnectionPoolDataSource for the data source implementation." ], [ "3j", "This OracleConnectionPoolDataSource does have the interface getConnection (URL, prop)." ], [ "3k", "It is now possible to pass the connection parameters to the Oracle driver." ], [ "3l", "For information on how to set these parameters see the technote, Using Oracle JDBC driver specific properties through a datasource. [http://www-01.ibm.com/support/docview.wss?uid=swg21197705]" ], [ "3m", "RESOLVING THE PROBLEM 1." ], [ "3n", "Use the Oracle JDBC OCI driver." ], [ "3o", "The parameters can be enabled in the SQLNET.ORA file (Oracle Network client's configuration file on the WebSphere Application Server system). 2." ], [ "3p", "A second option is to configure the above parameters as a custom property on the data source using the procedure described in technote Using Oracle JDBC driver specific properties through a datasource. [http://www-01.ibm.com/support/docview.wss?uid=swg21197705]" ], [ "3q", "Here is an example Name: connectionProperties Value: oracle.net.encryption_client=REQUESTED;oracle.net.encryption_types_client=RC4_40;oracle.net.crypto_checksum_client=REQUESTED;oracle.net.crypto_checksum_types_client=MD5" ], [ "3r", "Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ] ]

[ "2e", "2h", "2l", "2u", "3j", "3m", "3p" ]

[ "Netcool; Omnibus; rename; renaming; object; server TECHNOTE (FAQ)\n\nQUESTION\n How can I rename an existing object server? \n\nANSWER\nFollow below steps to rename an existing Object Server name. Suppose you want to rename NCOMS to BCOMS.\n\n1. Define the new Object Server name (BCOMS), hostname and port in the $NCHOME/etc/omni.dat file. \n\n2. Generate the interface files by running $NCHOME/bin/nco_igen command. \n\n * \n\n\n3. Create the new Object Server name with the $OMNIHOME/bin/nco_dbinit command. This \nwill create a default object server database and props file. * \n\n\n4. Update the new Object Server props file ($OMNIHOME/etc/BCOMS.props) based on the props file for existing object server (NCOMS). \n\n5. Backup existing object server using below command from nco_sql command. This will create two tab files (master_store.tab, and table_store.tab) in /tmp dir. * \n * \n * \n * \n * \n\n\n6. Make sure newly created object server (BCOMS) is stopped. \n\n7. Copy above two tab files to $OMNIHOME/db/BCOMS/ directory. \n\n8. Start up the new object server (BCOMS) using nco_objserv command. If it's using the same port as the old object server then you need to shutdown the old one first. \n\nAfter renaming the object server you may need to modify configuration files for other applications using the object server. Here are a few examples: \n\n1. For probes, you need to change the Server property to the new Object Server name and restart them. \n\n2. For Webtop/Webgui, you need to change the data source definition file below if the port is different, but that uses hostname/IP only, not the Object Server name. After this restart TIP.<TIP_HOME>/profiles/TIPProfile/etc/webtop/datasources/ncwDataSourceDefinitions.xml", "type mismatch; nco_osreport; fail over; fail back TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n On probe failover to the Backup Object Server, no events are inserted. The probe and Object Server log display Type Mismatch errors. \n\nSYMPTOM\n \n2013-07-30T08:21:38: Error: E-OBX-102-016: Language command from \nprobe@hostname failed. Type mismatch for column on \nline 1 of statement \\'insert into alerts.status values ( \\'10.10.10.10 \ndialCtlPeerCfgEntry.1212.29 Peer Call Status 2 IETF-DIAL-CONTROL-MIB \nMTTrapd Probe on hostname 2\\',0,\\'10.10.10.10\\', \n\\'10.10.10.10\\',\\'MTTrapd Probe on hostname\\',\\'IETF-\nDIA...\\' at or near \\'NmosEntityId\\' \n2013-07-30T08:21:38: Error: E-OBX-102-018: Failed to resolve parsed \nlanguage command. (-636:Type mismatch for column) \n2013-07-30T08:21:38: Error: E-OBX-102-016: Language command from \nprobe@hostname failed. Type mismatch \n\n\n\nRESOLVING THE PROBLEM\nThere are fields which are ordered differently between the Object Servers. For automatic probe failover and failback, the ordinal position of the fields in the alerts.status table must be identical.\n\nIt won't be possible just to delete/recreate or re-order the fields manually, deleting any columns also deletes any objects that reference those columns such as triggers or tools. Instead, it would be best if \nthe Backup Object Server could be recreated and cloned off the Primary Object Server. You would first need to ensure there were no custom triggers which exist only on the Backup Object Server or it would be overwritten. Here are the typical steps for cloning the Primary Object Server. \n\n1) Shutdown the Backup Object Server and the bi-directional failover Object Server gateway. Backup the Backup Object Server database files in $OMNIHOME/db/ just in case. \n2) On the Primary Object Server, run nco_osreport with the -dbinit option, this will create several sql files which should be copied to the Backup Object Server \n3) On the Backup Object Server, recreate the Object Server with the command \n\n$NCHOME/omnibus/bin/nco_dbinit -server CNCOMS_BAK \n-systemfile system.sql -applicationfile application.sql -alertsdata \n-alertsdatafile alertsdata.sql -desktopfile desktop.sql -automationfile \nautomation.sql -securityfile security.sql -force \n\nThe -force option is needed at the end to overwrite the current Object Server. \n\n4) Start the Backup Object Server and set properties BackupObjectServer to TRUE and ActingPrimary to FALSE. Ensure the primary_only trigger group is disabled. \n5) Start the bi-directional Object Server failover gateway. \n\nThese steps only work on Omnibus 7.3.1 and later since nco_osreport was not available in previous versions.", "MustGather; objectserver; backup TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Steps to create a backup of the ObjectServer database for troubleshooting. \n\nRESOLVING THE PROBLEM\nProvide the following information: \n\n[/support/docview.wss?uid=swg21631606&amp;aid=1][/support/docview.wss?uid=swg21631606&amp;aid=2]\n\n1. Create a temporary directory\n\nmkdir /tmp/backup \n\n2. Use nco_sql to obtain a backup\n\n./nco_sql -server NCOMS \nPassword: \n1> alter system backup '/tmp/backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that /tmp/backup contains *.tab files.\n\n4. Compressed /tmp/backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so.\n\n[/support/docview.wss?uid=swg21631606&amp;aid=3]\n\n1. Create a temporary directory\n\nmkdir c:\\tmp\\backup \n\n2. Use nco_sql to obtain a backup\n\nisql -S NCOMS -U root \nPassword: \n1> alter system backup 'c:\\tmp\\backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that c:\\tmp\\backup contains *.tab files.\n\n4. Compressed c:\\tmp\\backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so.", "PI event forwarding ; Predictive Insights anomaly ; PI Integration WHITE PAPER\n\nABSTRACT\n User would like to see PI events in AEL on more than one Omnibus deployments across the network \n\nCONTENT\nUse following steps to implement PI event forwarding simultaneously to more than one ObjectServer. \n\nNaming convention : \nFirst AEL host : PI Omnibus server_name_PI \nSecond AEL host : NOC Omnibus: server_name_NOC \nPI probe host : PI_probe\nNote : These instructions are only for forwarding events to the second instance of the object server/AEL and not the full functionality for view PI charts in the second instance of AEL for view such as ServiceDiagnosis \n\n\nPart: 1\nSteps on PI Omnibus ObjectServer (OS) server:\n\nStep1.1 \nConfigure on Omnibus PI OS server omni.dat with second NOC OS name \nNote : In case if second OS server name are the same make unique alias name \nTypical location of omni.dat on PI OS host /opt/IBM/tivoli/netcool/etc \n\nAs user that installed OS for example scadmin edit omni.dat \n$vi omni.dat\n[NCOMS]\n{\nPrimary: server_name_PI 4100\n}\n[NCO_PA]\n{\nPrimary: server_name_PI 4200\n\n# second NOC OS \n[NCOMS_NOC ]\n{\nPrimary: server_name_NOC 4100\n\n} \n[NCO_PA_NOC]\n{\nPrimary: server_name_NOC 4200\n\n} \n\n\nStep :1.2/ \nInterface file on PI OS server_name_PI \nGenerate the Omnibus Interface File on PI Omnibus server as scadmin using nco_igen Typically located on PI Omnibus server /opt/IBM/tivoli/netcool/bin \n$nco_igen \n\nStep 1.3/\n\nCopy newly created file “interfaces.linux2x86” to the PI probe server “PI_probe” as user that installed PI for example scadmin \n\nTypical location on PI_probe server /opt/IBM/scanalytics/analytics/probe/etc\n\nNote : this steps MUST be done before probe restart of PI probe \n\nPart 2. \nSteps on PI_probe host :\n\nStep 2.1 /\nThe configuration of the stdin-tasp.rules files on PI_probe system \nAs user that installed PI for example scadmin add two statement at the start of the rules file, \nThat typically located in /opt/IBM/scanalytics/analytics/probe/omnibus/probes/linux2x86\n\nDefaultAlerts = registertarget ( \"NCOMS\", \"\", \"alerts.status\" )\nDuplicatedAlerts = registertarget (\"NCOMS_NOC\", \"\", \"alerts.status\")\n:\n:\nAnd this statement must be the last line at the end of file \ngenevent(DuplicatedAlerts) \n\nStep 2.2/\nRun nco_p_syntax script located on Omnibus Server server_name _PI to make sure that syntax is correct \n\n/opt/IBM/tivoli/netcool/omnibus/platform/linux2x86/probes64/nco_p_syntax\nMake backup of original file stdin-tasp.rules \n$cp stdin-tasp.rules stdin-tasp.rules .orig\n\nReplace original file stdin-tasp.rules on PI_host with new stdin-tasp.rules. \n\nStep 2.3/\nIn order to load changes in probe rules files run on PI_probe server command \nto find PID or running probe $ps –ef | grep nco_p_std\nSample output : \n[scadmin@severname taspa linux2x86]$ ps -ef | grep nco_p\nscadmin 2253414 2252857 0 Oct07 ? 00:00:36 /opt/IBM/scanalytics/analytics/probe/omnibus/probes/linux2x86/nco_p_stdin -name GrangerDetectionTopic2FwProbe -propsfile /opt/IBM/scanalytics/analytics//probe/omnibus/probes/linux2x86/taspprobe.props -processescapes\nscadmin 2263796 2263194 0 Oct07 ? 00:02:38 /opt/IBM/scanalytics/analytics/probe/omnibus/probes/linux2x86/nco_p_stdin -name GrangerDetectionTopic1FwProbe -propsfile /opt/IBM/scanalytics/analytics//probe/omnibus/probes/linux2x86/taspprobe.props –processescapes\n\n\nStep 2.4/\nUse kill –HUP <PID> for probe to re-read and reload new rules \n\nOr restart streams /opt/IBM/scanalytics/analytics/bin\n$stop.sh \n$start .sh \nIf restart was done using stop.sh \n\nStep 2.5/\nRestart extraction with out providing startime or endtime \n$ admin.sh run_extractor_instance \n\nAfter this step events that will be generated on PI_probe server will be forwarded to server_name NOC and simultaneously will be displayed in PI Omnibus AEL and NOC Omnibus AEL", "failed; storage system; processing loop; Japanese; 日本語 TECHNOTE(トラブルシューティング)\n\n問題(概要)\n ストレージ・システムの開始に失敗しましました。 \n\n症状\nObject Server を起動できず、以下のエラーがログファイルに見つかります。 \n\nError: E-OBJ-102-020: Failed to start the storage system. (2:No such file or directory)\nError: E-IPC-005-001: OpenServer - Error: 16334/10/0: SRV_START イベントにより srv_run がアボートされました。\nError: E-STK-102-014: [nstk]: BOB: Failed to start server processing loop. (-19:General failure)\n\n\n解決方法\n$OMNIHOME/bin にディレクトリを変更後、新たなDBを生成させるように nco_dbinit -server BOB を実行します。 \n\nこの実行が成功したら、BOBという名前の Object Server を起動できるようになります。" ]

[ [ "0a", "Netcool; Omnibus; rename; renaming; object; server TECHNOTE (FAQ) QUESTION" ], [ "0b", " How can I rename an existing object server? ANSWER" ], [ "0c", "Follow below steps to rename an existing Object Server name." ], [ "0d", "Suppose you want to rename NCOMS to BCOMS. 1." ], [ "0e", "Define the new Object Server name (BCOMS), hostname and port in the $NCHOME/etc/omni.dat file. 2." ], [ "0f", "Generate the interface files by running $NCHOME/bin/nco_igen command. * 3." ], [ "0g", "Create the new Object Server name with the $OMNIHOME/bin/nco_dbinit command. This" ], [ "0h", "will create a default object server database and props file. * 4." ], [ "0i", "Update the new Object Server props file ($OMNIHOME/etc/BCOMS.props) based on the props file for existing object server (NCOMS). 5." ], [ "0j", "Backup existing object server using below command from nco_sql command." ], [ "0k", "This will create two tab files (master_store.tab, and table_store.tab) in /tmp dir. * * * * * 6." ], [ "0l", "Make sure newly created object server (BCOMS) is stopped. 7." ], [ "0m", "Copy above two tab files to $OMNIHOME/db/BCOMS/ directory. 8." ], [ "0n", "Start up the new object server (BCOMS) using nco_objserv command." ], [ "0o", "If it's using the same port as the old object server then you need to shutdown the old one first." ], [ "0p", "After renaming the object server you may need to modify configuration files for other applications using the object server." ], [ "0q", "Here are a few examples: 1." ], [ "0r", "For probes, you need to change the Server property to the new Object Server name and restart them. 2." ], [ "0s", "For Webtop/Webgui, you need to change the data source definition file below if the port is different, but that uses hostname/IP only, not the Object Server name." ], [ "0t", "After this restart TIP.<TIP_HOME>/profiles/TIPProfile/etc/webtop/datasources/ncwDataSourceDefinitions.xml" ] ]

[ "0c", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0n", "0p", "0q", "0r", "0s", "0t", "2b", "2e", "2f", "2h", "2j", "2k" ]

[ "Netcool; Omnibus; rename; renaming; object; server TECHNOTE (FAQ)\n\nQUESTION\n How can I rename an existing object server? \n\nANSWER\nFollow below steps to rename an existing Object Server name. Suppose you want to rename NCOMS to BCOMS.\n\n1. Define the new Object Server name (BCOMS), hostname and port in the $NCHOME/etc/omni.dat file. \n\n2. Generate the interface files by running $NCHOME/bin/nco_igen command. \n\n * \n\n\n3. Create the new Object Server name with the $OMNIHOME/bin/nco_dbinit command. This \nwill create a default object server database and props file. * \n\n\n4. Update the new Object Server props file ($OMNIHOME/etc/BCOMS.props) based on the props file for existing object server (NCOMS). \n\n5. Backup existing object server using below command from nco_sql command. This will create two tab files (master_store.tab, and table_store.tab) in /tmp dir. * \n * \n * \n * \n * \n\n\n6. Make sure newly created object server (BCOMS) is stopped. \n\n7. Copy above two tab files to $OMNIHOME/db/BCOMS/ directory. \n\n8. Start up the new object server (BCOMS) using nco_objserv command. If it's using the same port as the old object server then you need to shutdown the old one first. \n\nAfter renaming the object server you may need to modify configuration files for other applications using the object server. Here are a few examples: \n\n1. For probes, you need to change the Server property to the new Object Server name and restart them. \n\n2. For Webtop/Webgui, you need to change the data source definition file below if the port is different, but that uses hostname/IP only, not the Object Server name. After this restart TIP.<TIP_HOME>/profiles/TIPProfile/etc/webtop/datasources/ncwDataSourceDefinitions.xml", "type mismatch; nco_osreport; fail over; fail back TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n On probe failover to the Backup Object Server, no events are inserted. The probe and Object Server log display Type Mismatch errors. \n\nSYMPTOM\n \n2013-07-30T08:21:38: Error: E-OBX-102-016: Language command from \nprobe@hostname failed. Type mismatch for column on \nline 1 of statement \\'insert into alerts.status values ( \\'10.10.10.10 \ndialCtlPeerCfgEntry.1212.29 Peer Call Status 2 IETF-DIAL-CONTROL-MIB \nMTTrapd Probe on hostname 2\\',0,\\'10.10.10.10\\', \n\\'10.10.10.10\\',\\'MTTrapd Probe on hostname\\',\\'IETF-\nDIA...\\' at or near \\'NmosEntityId\\' \n2013-07-30T08:21:38: Error: E-OBX-102-018: Failed to resolve parsed \nlanguage command. (-636:Type mismatch for column) \n2013-07-30T08:21:38: Error: E-OBX-102-016: Language command from \nprobe@hostname failed. Type mismatch \n\n\n\nRESOLVING THE PROBLEM\nThere are fields which are ordered differently between the Object Servers. For automatic probe failover and failback, the ordinal position of the fields in the alerts.status table must be identical.\n\nIt won't be possible just to delete/recreate or re-order the fields manually, deleting any columns also deletes any objects that reference those columns such as triggers or tools. Instead, it would be best if \nthe Backup Object Server could be recreated and cloned off the Primary Object Server. You would first need to ensure there were no custom triggers which exist only on the Backup Object Server or it would be overwritten. Here are the typical steps for cloning the Primary Object Server. \n\n1) Shutdown the Backup Object Server and the bi-directional failover Object Server gateway. Backup the Backup Object Server database files in $OMNIHOME/db/ just in case. \n2) On the Primary Object Server, run nco_osreport with the -dbinit option, this will create several sql files which should be copied to the Backup Object Server \n3) On the Backup Object Server, recreate the Object Server with the command \n\n$NCHOME/omnibus/bin/nco_dbinit -server CNCOMS_BAK \n-systemfile system.sql -applicationfile application.sql -alertsdata \n-alertsdatafile alertsdata.sql -desktopfile desktop.sql -automationfile \nautomation.sql -securityfile security.sql -force \n\nThe -force option is needed at the end to overwrite the current Object Server. \n\n4) Start the Backup Object Server and set properties BackupObjectServer to TRUE and ActingPrimary to FALSE. Ensure the primary_only trigger group is disabled. \n5) Start the bi-directional Object Server failover gateway. \n\nThese steps only work on Omnibus 7.3.1 and later since nco_osreport was not available in previous versions.", "MustGather; objectserver; backup TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Steps to create a backup of the ObjectServer database for troubleshooting. \n\nRESOLVING THE PROBLEM\nProvide the following information: \n\n[/support/docview.wss?uid=swg21631606&amp;aid=1][/support/docview.wss?uid=swg21631606&amp;aid=2]\n\n1. Create a temporary directory\n\nmkdir /tmp/backup \n\n2. Use nco_sql to obtain a backup\n\n./nco_sql -server NCOMS \nPassword: \n1> alter system backup '/tmp/backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that /tmp/backup contains *.tab files.\n\n4. Compressed /tmp/backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so.\n\n[/support/docview.wss?uid=swg21631606&amp;aid=3]\n\n1. Create a temporary directory\n\nmkdir c:\\tmp\\backup \n\n2. Use nco_sql to obtain a backup\n\nisql -S NCOMS -U root \nPassword: \n1> alter system backup 'c:\\tmp\\backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that c:\\tmp\\backup contains *.tab files.\n\n4. Compressed c:\\tmp\\backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so.", "PI event forwarding ; Predictive Insights anomaly ; PI Integration WHITE PAPER\n\nABSTRACT\n User would like to see PI events in AEL on more than one Omnibus deployments across the network \n\nCONTENT\nUse following steps to implement PI event forwarding simultaneously to more than one ObjectServer. \n\nNaming convention : \nFirst AEL host : PI Omnibus server_name_PI \nSecond AEL host : NOC Omnibus: server_name_NOC \nPI probe host : PI_probe\nNote : These instructions are only for forwarding events to the second instance of the object server/AEL and not the full functionality for view PI charts in the second instance of AEL for view such as ServiceDiagnosis \n\n\nPart: 1\nSteps on PI Omnibus ObjectServer (OS) server:\n\nStep1.1 \nConfigure on Omnibus PI OS server omni.dat with second NOC OS name \nNote : In case if second OS server name are the same make unique alias name \nTypical location of omni.dat on PI OS host /opt/IBM/tivoli/netcool/etc \n\nAs user that installed OS for example scadmin edit omni.dat \n$vi omni.dat\n[NCOMS]\n{\nPrimary: server_name_PI 4100\n}\n[NCO_PA]\n{\nPrimary: server_name_PI 4200\n\n# second NOC OS \n[NCOMS_NOC ]\n{\nPrimary: server_name_NOC 4100\n\n} \n[NCO_PA_NOC]\n{\nPrimary: server_name_NOC 4200\n\n} \n\n\nStep :1.2/ \nInterface file on PI OS server_name_PI \nGenerate the Omnibus Interface File on PI Omnibus server as scadmin using nco_igen Typically located on PI Omnibus server /opt/IBM/tivoli/netcool/bin \n$nco_igen \n\nStep 1.3/\n\nCopy newly created file “interfaces.linux2x86” to the PI probe server “PI_probe” as user that installed PI for example scadmin \n\nTypical location on PI_probe server /opt/IBM/scanalytics/analytics/probe/etc\n\nNote : this steps MUST be done before probe restart of PI probe \n\nPart 2. \nSteps on PI_probe host :\n\nStep 2.1 /\nThe configuration of the stdin-tasp.rules files on PI_probe system \nAs user that installed PI for example scadmin add two statement at the start of the rules file, \nThat typically located in /opt/IBM/scanalytics/analytics/probe/omnibus/probes/linux2x86\n\nDefaultAlerts = registertarget ( \"NCOMS\", \"\", \"alerts.status\" )\nDuplicatedAlerts = registertarget (\"NCOMS_NOC\", \"\", \"alerts.status\")\n:\n:\nAnd this statement must be the last line at the end of file \ngenevent(DuplicatedAlerts) \n\nStep 2.2/\nRun nco_p_syntax script located on Omnibus Server server_name _PI to make sure that syntax is correct \n\n/opt/IBM/tivoli/netcool/omnibus/platform/linux2x86/probes64/nco_p_syntax\nMake backup of original file stdin-tasp.rules \n$cp stdin-tasp.rules stdin-tasp.rules .orig\n\nReplace original file stdin-tasp.rules on PI_host with new stdin-tasp.rules. \n\nStep 2.3/\nIn order to load changes in probe rules files run on PI_probe server command \nto find PID or running probe $ps –ef | grep nco_p_std\nSample output : \n[scadmin@severname taspa linux2x86]$ ps -ef | grep nco_p\nscadmin 2253414 2252857 0 Oct07 ? 00:00:36 /opt/IBM/scanalytics/analytics/probe/omnibus/probes/linux2x86/nco_p_stdin -name GrangerDetectionTopic2FwProbe -propsfile /opt/IBM/scanalytics/analytics//probe/omnibus/probes/linux2x86/taspprobe.props -processescapes\nscadmin 2263796 2263194 0 Oct07 ? 00:02:38 /opt/IBM/scanalytics/analytics/probe/omnibus/probes/linux2x86/nco_p_stdin -name GrangerDetectionTopic1FwProbe -propsfile /opt/IBM/scanalytics/analytics//probe/omnibus/probes/linux2x86/taspprobe.props –processescapes\n\n\nStep 2.4/\nUse kill –HUP <PID> for probe to re-read and reload new rules \n\nOr restart streams /opt/IBM/scanalytics/analytics/bin\n$stop.sh \n$start .sh \nIf restart was done using stop.sh \n\nStep 2.5/\nRestart extraction with out providing startime or endtime \n$ admin.sh run_extractor_instance \n\nAfter this step events that will be generated on PI_probe server will be forwarded to server_name NOC and simultaneously will be displayed in PI Omnibus AEL and NOC Omnibus AEL", "failed; storage system; processing loop; Japanese; 日本語 TECHNOTE(トラブルシューティング)\n\n問題(概要)\n ストレージ・システムの開始に失敗しましました。 \n\n症状\nObject Server を起動できず、以下のエラーがログファイルに見つかります。 \n\nError: E-OBJ-102-020: Failed to start the storage system. (2:No such file or directory)\nError: E-IPC-005-001: OpenServer - Error: 16334/10/0: SRV_START イベントにより srv_run がアボートされました。\nError: E-STK-102-014: [nstk]: BOB: Failed to start server processing loop. (-19:General failure)\n\n\n解決方法\n$OMNIHOME/bin にディレクトリを変更後、新たなDBを生成させるように nco_dbinit -server BOB を実行します。 \n\nこの実行が成功したら、BOBという名前の Object Server を起動できるようになります。" ]

[ [ "2a", "MustGather; objectserver; backup TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "2b", " Steps to create a backup of the ObjectServer database for troubleshooting." ], [ "2c", "RESOLVING THE PROBLEM" ], [ "2d", "Provide the following information: [/support/docview.wss?uid=swg21631606&amp;aid=1][/support/docview.wss?uid=swg21631606&amp;aid=2] 1." ], [ "2e", "Create a temporary directory mkdir /tmp/backup 2." ], [ "2f", "Use nco_sql to obtain a backup" ], [ "2g", "./nco_sql -server NCOMS Password:" ], [ "2h", "1> alter system backup '/tmp/backup'; 2> go" ], [ "2i", "(0 rows affected) 1> quit 3." ], [ "2j", "Verify that /tmp/backup contains *.tab files. 4. Compressed /tmp/backup 5." ], [ "2k", "Copy of ObjectServers properties file (i.e. NCOMS.props) 6." ], [ "2l", "If you can provide the root password, do so. [/support/docview.wss?uid=swg21631606&amp;aid=3] 1." ], [ "2m", "Create a temporary directory mkdir c:\\tmp\\backup 2." ], [ "2n", "Use nco_sql to obtain a backup" ], [ "2o", "isql -S NCOMS -U root Password:" ], [ "2p", "1> alter system backup 'c:\\tmp\\backup'; 2> go" ], [ "2q", "(0 rows affected) 1> quit 3." ], [ "2r", "Verify that c:\\tmp\\backup contains *.tab files. 4. Compressed c:\\tmp\\backup 5." ], [ "2s", "Copy of ObjectServers properties file (i.e. NCOMS.props) 6." ], [ "2t", "If you can provide the root password, do so." ] ]

[ "0c", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0n", "0p", "0q", "0r", "0s", "0t", "2b", "2e", "2f", "2h", "2j", "2k" ]

[ "MustGatherDocument; MustGather; Mustgather; Mustgather; mustgether: must gather; WebSphere; process; server; LDAP; integration; problem; authentication; user; registry TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are having a Lightweight Directory Access Protocol (LDAP) integration problem in WebSphere Process Server. You would like to know what documentation you must collect (MustGather) so that the WebSphere Process Server Support team can diagnose your problem. If you gather this documentation before contacting support, it will expedite the troubleshooting process, and save you time. \n\nRESOLVING THE PROBLEM\n\nLDAP configuration problems can have one of the following causes: \n\n * The distinguished name (DN) is not in the access control list (ACL), so some LDAP queries cannot be performed. \n * The DN was locked out of LDAP because of too many failed login attempts. \n * The DN password is not valid; it might have been changed. \n * The LDAP server might not allow anonymous queries. \n * The default filter that is defined in WebSphere Application Server might not be compatible with your settings (for example, objectclass=someObjectClass is not defined) \n * The firewall does not allow communication on the port. \n * The LDAP server is set to use a nonstandard port (standard ports: 389 and 636 (SSL) ). \n * The LDAP administrator ID is used as the server ID, but the administrator is not defined as a regular user.\n\n\nThese problems are only some of the possible reasons for LDAP configuration problems. The best and fastest way to debug the problem is to use the ldapsearch utility. This utility is similar to what WebSphere Process Server uses to query the LDAP server, but it is used on the command line. The ldapsearch utility bypasses WebSphere Process Server, and allows you to see what is returned from the query, which is normally hidden by WebSphere Process Server. On UNIX- based systems, ldapsearch is a native tool. For Microsoft Windows systems, you can download a corresponding version from the Using ldapsearch to debug LDAP configuration problems [http://www.ibm.com/support/docview.wss?uid=swg21113384] document. The method for using ldapsearch is to use the same configuration settings that you have defined in the WebSphere Process Server Administrative console under Security > Global security > User registries > LDAP settings. See the following tables for descriptions of the settings and properties. \n\n \n\nSetting Description Server user ID This setting is the short name of the ID that is queried from the LDAP server. Server user password This setting is the server user ID password in the LDAP server. Directory type This setting is a predefined list of supported LDAP servers. Selecting the proper directory updates the filters that are defined in Advanced properties. You can change these values. Host This setting is the host name of the LDAP server. This name can be a short name, long name, or IP address. Port This setting is the port value, which has a default value of 389. Base distinguished name (baseDN) This setting is the query starting location in your LDAP tree. Bind distinguished name (bindDN) This setting is the fully qualified DN that has the authority to \"bind\" to the LDAP server and perform the requested queries. Some LDAP servers allow anonymous queries, so the bindDN and bind password might not be required. Bind password This setting is the BindDN password. \n\nLDAP Advanced Properties Description User filter This property is the string that is used to query the LDAP server. User ID map This property is the definition of what is displayed in WebSphere from the resulting query. \nYou can use the following command to query the directory server: ldapsearch -h host-p port-b \"baseDN\" -D bindDN-w bind_password\"user_filter\" \n\nWith Tivoli Directory Server, using the -w option with a question mark ( ? ) prompts you for bind_password so that the password does not show in the shell history. The password security mechanism for your version of ldapsearch and your LDAP server might differ. \n\nFollowing is a short example of using ldapsearch:\nC:\\>ldapsearch -h petunia -p 389 -b \"o=ibm,c=us\" uid=test\ncn=test,o=ibm,c=us\nsn=test\nobjectclass=top\nobjectclass=organizationalPerson\nobjectclass=ePerson\nobjectclass=person\nobjectclass=inetOrgPerson\nuid=test\ncn=test \n\n\nThe search should return one result. If there is not a result or more than one result is returned, modify the user_filter and the filters that are used in WebSphere Process Server. \n\n\nCollecting general information\nSend IBM Support the relevant information, which is documented in the Collecting troubleshooting data for WebSphere Process Server for Version 6 [http://www.ibm.com/support/docview.wss?uid=swg21239895] document.\n\nCollecting LDAP-specific information\nSubmit the following LDAP-specific information to IBM Support:. Follow the instructions in Exchanging Information with IBM technical support technote. [http://www.ibm.com/software/support/exchangeinfo.html] \n\n * Output of the ldapsearch query for your environment, including the same settings (baseDN, bindDN, bind password, and so on) that are defined in WebSphere Process Server. \n * If you use Secure Sockets Layer (SSL) encryption but you do not experience problems when you do not use SSL, generate new certificates using passwords that you can share. Then, try again and send the certificates with passwords to IBM Support. Also, specify if you use server authentication, client authentication, or both. \n * Package the following directory: WPS_install/profiles/profile_name/logs/server_name. \n * Screen captures of the LDAP configuration parameters from the administrative console: * Security > Global security \n * Security > Global security > LDAP \n * Security > Global security > LDAP > Advanced Lightweight Directory Access Protocol (LDAP) user registry settings \n If the search filter is not fully visible, copy the search string for User Filter and Group Filter. \n * Security > Global security > LDAP > Custom properties\n \n \n\n * \n * Resources > Staff plug-in provider > LDAP Staff Plugin Provider Resources > Staff plug-in provider > LDAP Staff Plugin Provider > Custom properties Resources > Staff plug-in provider > LDAP Staff Plugin Provider > Staff plug-in configuration\n If the default LDAP Staff Plugin Configuration sample is not used, also submit the XSL file that you use. Resources > Staff plug-in provider > LDAP Staff Plugin Provider > Staff plug-in configuration > LDAP Staff Plugin Configuration sample (or the corresponding XSL file) Resources > Staff plug-in provider > LDAP Staff Plugin Provider > Staff plug-in configuration > LDAP Staff Plugin Configuration sample > Custom properties (or the corresponding XSL file) Project interchange (PI) file that uses the LDAP staff plug-in provider. Describe in detail how to deploy and configure the application so that the problem can be reproduced.\n \n \n * \n * ,\n * \n * WebSphere Process Server\n * \n\nRELATED INFORMATION\n#Troubleshooting Guide [http://www.ibm.com/support/docview.wss?uid=swg27008779]\nRecommended Fixes [http://www.ibm.com/support/docview.wss?uid=swg27006649]\n\n\n \n\nPRODUCT ALIAS/SYNONYM\n WPS", "Federated Repository; bind user; bind password; ADMN0022E; LDAP 49; Helper file; wp-update-federated-ldap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After you configured multiple Federated Repositories in your WebSphere Portal security, sometimes you may have to change the bind user ID and/or password. For example, due to company password policy, the password must be changed every 90 days. \n\nRESOLVING THE PROBLEM\nThe ConfigEngine task \"wp-update-federated-ldap\" can be used for this purpose. For purposes of updating the LDAP bind user password, normally, you only need to specify/change the following three parameters in wkplc.properties, \n\n * federated.ldap.id= // this parameter specifies which LDAP repository you want to update \n * federated.ldap.bindDN= // specify the full distinguished name of the bind user \n * federated.ldap.bindPassword= // specify the NEW password of the bind user.\n\n\nIt is also highly recommended to verify other parameters in the wkplc.properties and make sure they are correct. A full list of these parameters is presented at the end of this technote. \n\n \n\nAfter making sure the values of three required parameters are set, please, and, optionally checking the other parameters are still valid, issue the following command, \n\nConfigEngine.sh wp-update-federated-ldap \n\n \n\nIf WasUserid and WasPassword are not set in wkplc.properties, you have to specify them on command line. \n\nNote: This configuration task makes no changes to the LDAP itself, it only updates the WebSphere Application Server and WebSphere Portal configurations. \n\n \n\nSome considerations \n\n1. The configuration task \"wp-update-federated-ldap\" reads the three parameters specified above, and, all of the other parameters from wkplc.properties, and commits the values of those parameters into the configuration. Therefore, If multiple LDAPs were configured in the Federated Repositories, be sure the rest of the parameters are verified and correctly set for the LDAP that is being updated, because the last added LDAP may not be the one you are trying to update here. Due to this reason, it's strongly recommended to use individual helper files for each LDAP, so they will not interfere with each other during configuration and later updates. \n\n2. Let's call the LDAP repository the primary LDAP where WAS primary administrative user resides. If the bind password of the primary LDAP is to be updated using the procedure in this technote, conduct the procedure to change the bind password before the actual user's password is changed in the LDAP. Otherwise, the task may fail with WebSphere error ADMN0022E and LDAP error code 49. \n\n3. The function of resetting the bind user ID and password can also be done by \"updateIdMgrLDAPServer\" in IdMgrRepositoryConfig using wsadmin tool in WebSphere Application Server. See the link in reference below. \n\n \n\nOther Parameters to be checked: \n\n * federated.ldap.referral \n * federated.ldap.authentication \n * federated.ldap.sslEnabled \n * federated.ldap.sslConfiguration \n * federated.ldap.certificateMapMode \n * federated.ldap.certificateFilter \n * federated.ldap.connectionPool \n * federated.ldap.connectTimeout \n * federated.ldap.derefAliases \n * federated.ldap.ldapServerType \n * federated.ldap.port \n * federated.ldap.supportSorting \n * federated.ldap.supportPaging \n * federated.ldap.supportTransactions \n * federated.ldap.isExtIdUnique \n * federated.ldap.supportExternalName \n * federated.ldap.translateRDN \n * federated.ldap.searchTimeLimit \n * federated.ldap.searchCountLimit \n * federated.ldap.searchCountLimit \n * federated.ldap.searchPageSize \n * federated.ldap.returnToPrimaryServer \n * federated.ldap.primaryServerQueryTimeInterval\n\nRELATED INFORMATION\n updateIdMgrLDAPServer [http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.iseries.doc/info/iseriesnd/ae/rxml_atidmgrrepositoryconfig.html]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * AFFECTED URLs:\n V7\n http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Updating_the_stand [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Updating_the_stand]\n alone_LDAP_user_registry_on_Windows_wp7\n .\n V6.1\n http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?to\n pic=/com.ibm.wp.ent.doc_v615/security/win_update_saldap.html [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/index.jsp?topic=/com.ibm.wp.ent.doc_v615/security/win_update_saldap.html]\n .\n TEXT READS:\n After configuring and using the standalone LDAP user registry,\n you may find that your LDAP user registry is not working exactly\n as you would like. You can easily update the LDAP user registry\n and make the necessary changes. For example, you can change your\n LDAP Bind password.\n .\n TEXT SHOULD READ:\n After configuring and using the standalone LDAP user registry,\n you may find that your LDAP user registry is not working exactly\n as you would like. You can easily update the LDAP user registry\n and make the necessary changes. For example, you can change your\n LDAP Bind password. However, note that such a task will remove\n any attribute mappings that you have added since you previously\n enabled/updated the standalone LDAP user registry. Thus, you\n will need to re-run the mapping steps as described on the <OS>:\n Mapping attributes section.\n \n \n \n \n \n\nLOCAL FIX\n * Refer to the above\n \n \n \n \n \n\nPROBLEM SUMMARY\n * This is planned to be changed in the product documentation.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This is planned to be changed in the product documentation.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM36484\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 700\n \n \n * STATUS\n CLOSED DOC\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2011-04-11\n \n \n * CLOSED DATE\n 2011-11-03\n \n \n * LAST MODIFIED DATE\n 2011-11-03\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS", "ldapsearch TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to use ldapsearch to debug LDAP configuration problems with IBM® WebSphere® Application Server? \n\nRESOLVING THE PROBLEM\nThere are many things which may prevent your LDAP configuration from working properly. \nDN = Distinguished Name\nACL = Access Control List\n\n· DN not in ACL and therefore cannot perform certain ldap queries\n· DN was locked out of ldap due to too may failed login attempts\n· DN password may have been changed\n· LDAP server may not allow anonymous queries\n· Default filter defined in Application Server may not fit customers' settings.(i.e. no objectclass=someObjectClass defined)\n· Firewall not allowing communication on port\n· LDAP set to use nonstandard port of 389\n· LDAP administrator ID used for Server ID but the administrator's ID is not defined as a regular user\n\nFor these and numerous other possible configuration problems the best way to quickly debug the problem is to do an ldapsearch. Ldapsearch is a utility similar to what Application Server uses to query the ldap server but is used on the command line. This removes Application Server from the picture and allows you to see what is being returned from the query, normally hidden by Application Server.\n\nThe idea is use the same configuration settings, on the command line, as you have defined in Application Server’s Administrative console > Security > user Registries > LDAP settings.\n\n\n\nSecurity Server ID Short name of the ID which is queried from LDAP. Security Server Password ID’s password in LDAP Directory Type Predefined list of supported LDAP servers. Selecting the proper Directory updates the filters defined under the Advanced properties. These can be changed. Host Hostname of LDAP server. Can be short name, long name, or IP address. Port 389 is the default LDAP port Base Distinguished Name\n(BaseDN) Query starting location in your LDAP tree Bind Distinguished Name\n(BindDN) Fully qualified DN which has the authority to “bind” to your LDAP server and preform the requested queries. Some LDAP servers allow for anonymous queries so no bind DN and bind password may be required Bind Password Bind DN’s password. \nLDAP advanced properties User Filter The string used to query the LDAP server. User ID Map Defines what gets displayed in WebSphere from resulting query. \nldapsearch –h <Host> -p <Port> -b “<BaseDN>” –D <BindDN> -w <Bind Password> “<User Filter>” \n\nNote: The “%v” in the <User Filter> gets replaced by the <Security Server ID> \nFor example, instead of \"(&(cn= %v)(objectclass=ePerson))\" use \"(&(cn= bob)(objectclass=ePerson))\" \n\nExample ldapsearch queries \nC:\\> ldapsearch -h petunia -p 389 -b \"o=ibm,c=us\" uid=test \ncn=test,o=ibm,c=us \nsn=test \nobjectclass=top \nobjectclass=organizationalPerson \nobjectclass=ePerson \nobjectclass=person \nobjectclass=inetOrgPerson \nuid=test \ncn=test \n\nC:\\> ldapsearch -h petunia -p 389 -b \"o=ibm,c=us\" \"(&(uid=test)(objectclass=ePerson))\" \ncn=test,o=ibm,c=us \nsn=test \nobjectclass=top \nobjectclass=organizationalPerson \nobjectclass=ePerson \nobjectclass=person \nobjectclass=inetOrgPerson \nuid=test \ncn=test \n\nLdapsearch queries which would cause an exception for Application Server: \n\nThe following would fail in Application Server because the search filter is looking for an objectclass of “XYZ” but there is no “XYZ” objectclass defined LDAP. This results in an empty return string. \n\nC:\\> ldapsearch -h petunia -p 389 -b \"o=ibm,c=us\" \"(&(uid=test)(objectclass=XYZ))\" \n\nThe following search would fail in Application Server because 2 DN’s are returned instead of 1. Application Server will only authenticate using a single DN. If the query was uid=test instead of cn=test, then only one DN would have been returned. \n\nC:\\> ldapsearch -h petunia -p 389 -b \"o=ibm,c=us\" \"(&(cn=test)(objectclass=ePerson))\" \ncn=test,o=ibm,c=us \nsn=test \nobjectclass=top \nobjectclass=organizationalPerson \nobjectclass=ePerson \nobjectclass=person \nobjectclass=inetOrgPerson \nuid=test \ncn=test \n\ncn=test,ou=Larry's Group,ou=Austin,o=ibm,c=us \nsn=User \nobjectclass=top \nobjectclass=organizationalPerson \nobjectclass=ePerson \nobjectclass=person \nobjectclass=inetOrgPerson \ncn=Test \n\nAlso: See LDAPQuery [http://www.ibm.com/support/docview.wss?uid=swg21648889] web application tool ldapsearch.zip [/support/docview.wss?uid=swg21113384&aid=2] [/support/docview.wss?uid=swg21113384&aid=1]\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "change; user; password; fem; directory service; bootstrapconfig; bootstrap user TECHNOTE (FAQ)\n\nQUESTION\n How do you change the user and/or password for Directory Service Account used by the Content Engine? \n\nANSWER\nThe Directory Service user account and password are normally used in two product components: FileNet Enterprise Manager (FEM), and the application server. A coordinated update procedure should be followed when there is a need to change the user account and/or password. This procedure applies to FileNet Content Engine 4.x and above. \n\n * \n * Note: \n * \n * \n\n\nIf the same user account is also used as the CE Bootstrap user, the corresponding user in the BootstrapConfig.properties needs to change as well. For changing the GCD admin user/password in BootstrapConfig.properties specifically, refer to this documentation: \nhttp://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_change_bootstrap_pwd.htm [http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_change_bootstrap_pwd.htm] \n\n\n1. Launch FEM and the application server's administrative console. \na. Login to FEM using the Directory Service account. \nb. Login to the application server administrative console with an administrator account. \n\nImportant: Do not close above two applications until you have completed step 5 below. \n\n\n2. Make LDAP account changes: \na. Change the password for an existing account on the LDAP server - Using LDAP interface, change the password for the CE Directory Service account. \nOR \nb. Create a new user account on the LDAP server for the CE Directory Service account. \n\n\n3. Add new user (if applicable), to FEM \nIf the bind user is also the CE admin user, then the bind user will need to be added to all the existing objects in the P8 domain. Please read Update object store with new users and groups [http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp?topic=/com.ibm.p8.doc/admin/security/sec_how_update_os.htm] for instructions \n\n\n4. Change Directory Configuration bind user in FEM \nUsing FEM (step 1a above), go to Domain properties > Directory Configuration > Select Directory Configuration > click on the Modify button > General Tab: \na. Modify the Directory Service User with new user's full distinguish name (DN) \nb. Click on Change password check box > change to a new password > click OK. \n\nAt this point you will be presented a dialog box with following message: \n“These changes require the application server to be restarted. Please restart the application server to incorporate these changes” \n\nclick OK > click OK \n\nImportant: Do not restart the application server until you have completed step 5 below. \n\n\n5. Change the user in the application server's directory configuration \n\n- For Websphere, in the WebSphere Administrative Console, go to Global Security > click on Configure under User Account Repository > Modify Bind Distinguished Name (DN) > Modify Bind Password > click OK and Save changes \n\n- For WebLogic go to Security Realms > myrealm > Providers > ldap provider and click on \"Provider Specific\" tab in WebLogic Admin Console. Change \"Principal\" and \"Credential\". \n\n- For JBoss go to <JBoss Home>\\server\\<CE Server>\\conf directory and edit \"login-config.xml\". \nFind \"FileNet\" application-policy and in login module change bindDN/bindCredential. \n\n\n6. Changing the CE Bootstrap user \n\nFor CE 4.5.x and above: \na. In the Configure Bootstrap Properties task, set the Bootstrap Operation property to Modify Existing. \nb. Confirm that the Bootstrapped EAR file property contains the path to the bootstrap file you need to edit. \nc. Change the Bootstrap user password. Use Configuration Manager's features to save and run the task. \nd. Run Configuration Manager's Deploy Application. \n\nFor CE 4.0: \nNote: This step is needed only if the GCD user name is the same as the Directory Service account. Note that the example below is for a Windows environment. \n\n- For WebSphere \na. Open command prompt window, go to folder where EAR file reside (it differs depending on CE version). For example, in CE 4.5.1, go to \"<CE Home> \\ tools \\ configure \\ profiles \\ <profile> \\ ear\" \nb. Backup Engine-ws.ear \nc. Execute the command below: \n\njava –jar “c:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar” –e Engine-ws.ear --username <username> --password <password> \n\nd. Since the Engine-ws.ear file has been deployed in the WebSphere's installedApps path, the Bootstrap file need to be copied to the path manually. Extract the props.jar file from the ear file by utility such as Winzip, copy the props.jar file to theinstalledApps location - “<WebSphere Home>\\ AppServer\\ profiles \\ <profile name> \\ InstalledApps \\<serverNodecell> \\ FileNetEngine.ear \\ APP-INF \\ lib \\\" \n\nNote that an alternative to copying the props.jar file is to uninstall and re-install the updated ear file in WebSphere. \n\n- For WebLogic \na. Open command prompt window, go to folder - \"<WebLogic home> \\ user_projects \\ domains \\ <domain> \\ servers \" \nb. Backup FileNetEngine.ear \nc. Execute the command below: \n\njava –jar “c:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar” –e Engine-wl.ear --username <username> --password <password> \n\n- For JBoss \na. Open command prompt window, go to folder - \"<JBoss Home> \\ server \\ <server> \\ deploy \\\" \nb. Backup FileNetEngine.ear \nc. Execute the command below: \n\njava –jar “c:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar” –e Engine-jb.ear --username <username> --password <password> \n\n\n7. Remove cached files in the application server \n- Close FileNet Enterprise Manager (Step 1a) \n- Close Administrative Console (Step 1b) \n- Stop the application server \n- Remove the cached FileNetEngine directory in the application server. \nFor example, the default windows path on Websphere 6.0 is \n\"C:\\program files\\Websphere\\AppServer\\profiles\\<profile name>\\temp\\<server node>\\ \n<server>\\FileNetEngine\" \n\n\n8. Restart the application server, and login to FEM using the new user and password. \n\n\n9. Troubleshooting \n\nIf CE fails to start due to mistakes in the above procedures, you may not be able to redo the change through these procedures because FEM will fail to run. \nIn this case, you can do the following: \n\n- Back out the change made to the GCD database in step 3 by deleting the latest row in the FNGCD table. \n- Back out the change made to the application server in step 4 by redoing the procedure with the previous user. \n- Back out the change made to the BootstrapConfig.properties file's GCD user by using the backup EAR file \n- Restart the application server, and login to FEM using the previous user." ]

[ [ "1a", "Federated Repository; bind user; bind password; ADMN0022E; LDAP 49; Helper file; wp-update-federated-ldap TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "1b", " After you configured multiple Federated Repositories in your WebSphere Portal security, sometimes you may have to change the bind user ID and/or password." ], [ "1c", "For example, due to company password policy, the password must be changed every 90 days." ], [ "1d", "RESOLVING THE PROBLEM" ], [ "1e", "The ConfigEngine task \"wp-update-federated-ldap\" can be used for this purpose." ], [ "1f", "For purposes of updating the LDAP bind user password, normally, you only need to specify/change the following three parameters in wkplc.properties," ], [ "1g", " * federated.ldap.id= // this parameter specifies which LDAP repository you want to update" ], [ "1h", " * federated.ldap.bindDN= // specify the full distinguished name of the bind user" ], [ "1i", " * federated.ldap.bindPassword= // specify the NEW password of the bind user." ], [ "1j", "It is also highly recommended to verify other parameters in the wkplc.properties and make sure they are correct." ], [ "1k", "A full list of these parameters is presented at the end of this technote." ], [ "1l", "After making sure the values of three required parameters are set, please, and, optionally checking the other parameters are still valid, issue the following command, ConfigEngine.sh wp-update-federated-ldap" ], [ "1m", "If WasUserid and WasPassword are not set in wkplc.properties, you have to specify them on command line." ], [ "1n", "Note: This configuration task makes no changes to the LDAP itself, it only updates the WebSphere Application Server and WebSphere Portal configurations. Some considerations 1." ], [ "1o", "The configuration task \"wp-update-federated-ldap\" reads the three parameters specified above, and, all of the other parameters from wkplc.properties, and commits the values of those parameters into the configuration." ], [ "1p", "Therefore, If multiple LDAPs were configured in the Federated Repositories, be sure the rest of the parameters are verified and correctly set for the LDAP that is being updated, because the last added LDAP may not be the one you are trying to update here." ], [ "1q", "Due to this reason, it's strongly recommended to use individual helper files for each LDAP, so they will not interfere with each other during configuration and later updates. 2." ], [ "1r", "Let's call the LDAP repository the primary LDAP where WAS primary administrative user resides." ], [ "1s", "If the bind password of the primary LDAP is to be updated using the procedure in this technote, conduct the procedure to change the bind password before the actual user's password is changed in the LDAP." ], [ "1t", "Otherwise, the task may fail with WebSphere error ADMN0022E and LDAP error code 49. 3." ], [ "1u", "The function of resetting the bind user ID and password can also be done by \"updateIdMgrLDAPServer\" in IdMgrRepositoryConfig using wsadmin tool in WebSphere Application Server." ], [ "1v", "See the link in reference below." ], [ "1w", "Other Parameters to be checked:" ], [ "1x", " * federated.ldap.referral" ], [ "1y", " * federated.ldap.authentication" ], [ "1z", " * federated.ldap.sslEnabled" ], [ "1aa", " * federated.ldap.sslConfiguration" ], [ "1ab", " * federated.ldap.certificateMapMode" ], [ "1ac", " * federated.ldap.certificateFilter" ], [ "1ad", " * federated.ldap.connectionPool" ], [ "1ae", " * federated.ldap.connectTimeout" ], [ "1af", " * federated.ldap.derefAliases" ], [ "1ag", " * federated.ldap.ldapServerType" ], [ "1ah", " * federated.ldap.port" ], [ "1ai", " * federated.ldap.supportSorting" ], [ "1aj", " * federated.ldap.supportPaging" ], [ "1ak", " * federated.ldap.supportTransactions" ], [ "1al", " * federated.ldap.isExtIdUnique" ], [ "1am", " * federated.ldap.supportExternalName" ], [ "1an", " * federated.ldap.translateRDN" ], [ "1ao", " * federated.ldap.searchTimeLimit" ], [ "1ap", " * federated.ldap.searchCountLimit" ], [ "1aq", " * federated.ldap.searchCountLimit" ], [ "1ar", " * federated.ldap.searchPageSize" ], [ "1as", " * federated.ldap.returnToPrimaryServer" ], [ "1at", " * federated.ldap.primaryServerQueryTimeInterval RELATED INFORMATION" ], [ "1au", " updateIdMgrLDAPServer [http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.iseries.doc/info/iseriesnd/ae/rxml_atidmgrrepositoryconfig.html]" ], [ "1av", "Cross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1" ] ]

[ "1b", "1c", "1e", "1f", "1g", "1h", "1i", "1l", "1m", "1s", "1t", "1u" ]

[ " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS FIXED IF NEXT.\n \n \n \n\nERROR DESCRIPTION\n * In WLE 7.2 when running optimizer/simulation 'Instance Duration\n Trend' diagram is blank and is not reflecting any data. It works\n just fine for the same simple process in WLE 7.1.\n \n \n I have used the export of the process that was provided by the\n customer, running many (around 40) instances, completing them,\n sending definitions etc. Nothing helps and no error, the same\n way 'Instance Duration Histogram' is reflecting data just fine.\n \n The issue easily reproduces with simple BPD running an 'Ad-hoc\n simulation' via 'Start new simulation for the current process\n only' button.\n \n The screenshots can be found here:\n \n \n https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7 [https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7]\n 60/support_files/opt_1.jpg\n \n \n https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7 [https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7]\n 60/support_files/opt_2.jpg\n \n To compare, the same process running in WLE 7.1:\n \n \n https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7 [https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7]\n 60/support_files/opt_7.1.jpg\n \n \n \n \n \n\nLOCAL FIX\n * Currently, there is no fix\n \n \n \n \n \n\nPROBLEM SUMMARY\n * In WLE 7.2 when running optimizer/simulation\n 'Instance Duration\n Trend' diagram is blank and is not reflecting any data. It works\n just fine for the same simple process in WLE 7.1.\n \n \n I have used the export of the process that was provided by the\n customer, running many (around 40) instances, completing them,\n sending definitions etc. Nothing helps and no error, the same\n way 'Instance Duration Histogram' is reflecting data just fine.\n \n The issue easily reproduces with simple BPD running an 'Ad-hoc\n simulation' via 'Start new simulation for the current process\n only' button.\n \n The screenshots can be found here:\n \n \n https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7 [https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7]\n 60/support_files/opt_1.jpg\n \n \n https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7 [https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7]\n 60/support_files/opt_2.jpg\n \n To compare, the same process running in WLE 7.1:\n \n \n https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7 [https://ecurep.mainz.de.ibm.com/aexfiles/pmr/4/4/44072%2C600%2C7]\n 60/support_files/opt_7.1.jpg\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC75996\n \n \n * REPORTED COMPONENT NAME\n WS LOMBARDI EDI\n \n \n * REPORTED COMPONENT ID\n 5725A0900\n \n \n * REPORTED RELEASE\n 720\n \n \n * STATUS\n CLOSED FIN\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2011-04-27\n \n \n * CLOSED DATE\n 2011-07-13\n \n \n * LAST MODIFIED DATE\n 2011-07-13\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS\n * R720 PSY\n UP", " FIXES ARE AVAILABLE\nVersion 8.5 Refresh Pack 5 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24037683]\nDownload Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24037734]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When starting a BPD (with snapshot id or without) the process\n is started with the incorrect versioning context. This causes\n instance migration to not be possible if the BPD of interest is\n located inside a toolkit.\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ABSTRACT ? INCORRECT ROOT VERSIONING CONTEXT USED WHEN STARTING\n BPD FROM TOOLKIT\n ERROR DESCRIPTION - If an exposed BPD from a toolkit is started\n using Portal or REST API, the active instances are not counted\n in the Process Admin Console ? Installed Apps section.\n \n PRODUCTS AFFECTED\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express\n \n LOCAL FIX - N/A\n \n \n PROBLEM SUMMARY ? When starting an exposed BPD from Process\n Portal or REST API (ie.\n https://localhost:9443/rest/bpm/wle/v1/process?action=start&bpdI\n d=<bpd_id>&snapshotId=<snapshot_id>), [https://localhost:9443/rest/bpm/wle/v1/process?action=start&bpdId=<bpd_id>&snapshotId=<snapshot_id>),] if the BPD resides in a\n toolkit, Process Admin Console's ?Installed Apps? page will not\n show these active instances as part of the instance counter\n displayed under the snapshot name.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * PROBLEM CONCLUSION ?\n A fix is available for IBM BPM v8.0.1.2 to properly start the\n BPD in the correct versioning context, allowing the instance to\n be visible in the Process Admin Console.\n \n On Fix Central (http://www.ibm.com/support/fixcentral), search\n for JR50141:\n 1.Select IBM Business Process Manager with your edition from the\n product selector, the installed version to the fix pack level,\n and your platform, and then click Continue.\n 2.Select APAR or SPR, enter JR50141, and click Continue.\n When you download fix packages, ensure that you also download\n the readme file for each fix. Review each readme file for\n additional installation instructions and information about the\n fix.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n JR50141\n \n \n * REPORTED COMPONENT NAME\n BPM STANDARD\n \n \n * REPORTED COMPONENT ID\n 5725C9500\n \n \n * REPORTED RELEASE\n 801\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2014-05-02\n \n \n * CLOSED DATE\n 2014-07-18\n \n \n * LAST MODIFIED DATE\n 2014-07-18\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n BPM STANDARD\n \n \n * FIXED COMPONENT ID\n 5725C9500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R801 PSY\n UP", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your system is running slowly and you can not tell why. This article lists tools and techniques to diagnose performance problems including heap and CPU utilization problems. \n\nRESOLVING THE PROBLEM\nThere are a number of tools you can use to get to the root cause of the problem \n\n * Enable Java™ GC logging [https://www.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tprf_tuneclassicjvm.html] \n * GC Viewer [https://www.ibm.com/developerworks/java/jdk/tools/gcmv/] (A tool to read GC Logs) \n * Java thread dumps [https://www.ibm.com/developerworks/community/blogs/e8206aad-10e2-4c49-b00c-fee572815374/entry/Java_Core_Debugging_using_IBM_Thread_and_Monitor_Dump_Analyzer_for_Java?lang=en] - creating and viewing \n * Heap dump analysis tool [https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=4544bafe-c7a2-455f-9d43-eb866ea60091] \n * The Event Manager Monitor \n * The Process Monitor\n\n\nWhat should you do first? \n\n [http://yourhost:yourport/teamworks]A Teamworks administrator's first stop should be the Event Manager and the Process Monitor. Both are available on the web at http://yourhost:yourport/teamworks. Start with the Event Manager. Look for any long running tasks that are in an executing state. There are a number of tasks that can show up there and the type of task gives a hint to the problem. BPDNotification and DBNotification are tasks in the Business Process Definition Engine. These should generally execute in a small amount of time. SystemTask and UCATask are generally services. If these are long running then the associated services are likely \"stuck.\" If you see items rapidly popping up and being completed, you might be in a loop that is moving between the BPD Engine and the Service Engine. For instance, you might have a System Lane task that is getting an error. If you have a catch exception on that System Lane Activity that loops back to itself, then the system task fails, you go back to the Business Process Definition (BPD) Engine in the catch, then immediately back to the Service Engine to fail again.\n\nThe Process Monitor tells you if you have a service or a business process definition in a loop. If you go there, you will see a list of active services and processes. Active services and processes are jobs that are currently running and consuming CPU. You can click them to find out which service or business process definition is currently involved and then find out what step or steps you are stuck in.\n\nIf you find a loop in the Process Monitor or Service Monitor, it is pretty likely that the loop is what is causing CPU and memory usage. If you do not find a loop, you need to look elsewhere.\n\nThe next thing you should do is gather thread dumps. See the links previously listed for information on how to gather them. For the thread dumps, you should gather at least 5 thread dumps that are at least 1 minute apart. You do that because you will want to see what threads are moving and which are stuck. The thread dumps might provide you with what you need. For example, if most of the threads are waiting on the database, you have a hint that maybe there is a database problem. \n\nWhat if you are running low on Heap?\nAt a high level, when you run low of Java memory (heap space) your CPU will suddenly spike and your application will stop responding. This scenario is because Java garbage collection is expensive when you are running low on memory and it can block the other threads in the JVM and prevent them from moving. One possibility for running out of heap is a process that is running in a loop. You should have already ruled that out in the process monitor step listed previously so now we need heap dumps. You can use heap dumps to see what was in memory when you saw the problem. Analyzing heap dumps is a difficult task so you will probably need to open a ticket with your application server vendor and with IBM support to get assistance. IBM heap dumps take massive machines for analysis so you will need to contact IBM to get assistance if you are running a JVM.\n\nGarbage collection logging can also be useful. Garbage collection log files give you the ability to graph memory utilization over time. This can be helpful to spot trends. For instance, if the heap grows slowly you might have a leak. If it spikes every day at 3 PM, you might have a user running a report that is consuming too much memory. The previous links can help you enable garbage collecting logging on your JVM. The Garbage Collection Viewer is a great tool to view the data from these log files graphically.\n\n \n\nHISTORICAL NUMBER\n 432", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When you open a process instance which is migrated from an old snapshot in the Process Admin Console, the error CWTBG0047E appears. \n\nSYMPTOM\nOpening a BPD in the Process Admin Console causes the following error message to appear: \n\n\"CWTBG0047E:Process 'BPD.XXX-XXX-XXX-XXX-XXX' does not exist; it might have been deleted in the meantime\"\n\n[/support/docview.wss?uid=swg21675156&aid=1] [/support/docview.wss?uid=swg21675156&aid=1] \n\n \n\nThere is no error message that indicates the instance migration failure in SystemOut.log: \n\n\n[4/8/14 15:16:01:975 CST] 0000219f wle I Migrated instances of Process App 'TestMigration' from snapshot 'Test1' to snapshot 'Test3'. No token policy file was used to handle possible orphan tokens.\n[4/8/14 15:17:11:720 CST] 0000a8d0 wle_security I CWLLG1088I: Initializing session is done for user admin\n\n\nCAUSE\nThe error message indicates that the BPD from which the migrated instance is created has been deleted in new snapshot.\n\n\n\nRESOLVING THE PROBLEM\nYou need to pay attention to orphaned tokens if there are process deletions during instance migration. \n\nRefer to the IBM Business Process Manager product documentation [http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r5m0/index.jsp?topic=%2Fcom.ibm.wbpm.admin.doc%2Ftopics%2Freleasing_installing_procs_E.html] for information on migrating instances.\n\nYou can use policy files to handle the orphaned tokens, or use the REST API -> Move Token command to manually move the token after the migration.\n\nPolicy files provide an automated way to move tokens after instance migration. The administrative user needs to determine whether there are orphaned tokens that need to be moved. If there are no orphaned tokens, policy files are not needed. \n\nThe message in SystemOut.log is an indication that no policy files were used. Orphaned tokens must be moved or deleted using policy files or the REST API commands.\n\nYou can refer to the IBM Business Process Manager product documentation [http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0mx/index.jsp?topic=%2Fcom.ibm.wbpm.admin.doc%2Ftopics%2Fmigrating_instances_pac.html] for information on how to use policy files during instance migration.\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Business Process Definition (BPD) AIX, Linux, Solaris, Windows 8.5.0.1, 8.5, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0 Business Integration IBM Business Process Manager Express Business Process Definition (BPD) Linux, Windows 8.5.0.1, 8.5, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0 \nHISTORICAL NUMBER\n 08526\n999\n760", " DIRECT LINKS TO FIXES\nbpm.8570.cf2016.06.delta.repository.2of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.06.delta.repository.2of2&source=SAR]\nbpm.8570.cf2016.06.delta.repository.1of2 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FIBM+Business+Process+Manager+Standard&fixids=bpm.8570.cf2016.06.delta.repository.1of2&source=SAR]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS FIXED IF NEXT.\n \n \n \n\nERROR DESCRIPTION\n * tw.system.model.findProcess incorrectly uses the TIP snapshot\n context on Process Server. This would be the expected behavior\n on Process Center but for process server it should use the\n default snapshot's context.\n \n If you then use methods like startNew it can create an instance\n in the wrong snapshot context. The instances will show up as the\n TIP snapshot in the Process Inspector.\n \n \n \n \n \n\nLOCAL FIX\n * Use the findProcessByName method of a TWProcessAppSnapshot\n object to lookup the BPD.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ERROR DESCRIPTION -\n Using the Javascript API TWProcess.startNew() will create a\n process instance with the flag TIP set to ?T? in the database.\n \n \n PRODUCTS AFFECTED\n IBM Business Process Manager (BPM) Advanced\n IBM BPM Standard\n IBM BPM Express\n \n LOCAL FIX -\n None\n \n \n PROBLEM SUMMARY\n The following is an example of the effected Javascript API:\n tw.system.model.findProcess(\"25.31bde955-a01a-41e7-9f44-f4ce9e99\n 0426\",\"2066.be55f902-d944-40b0-a264-94fb6b15cade\").startNew(null\n );\n \n The instances created will have the TIP flag set to ?T?(true)\n even when the BPD context used to start the instance is from a\n named snapshot.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n JR54948\n \n \n * REPORTED COMPONENT NAME\n BPM ADVANCED\n \n \n * REPORTED COMPONENT ID\n 5725C9400\n \n \n * REPORTED RELEASE\n 856\n \n \n * STATUS\n CLOSED FIN\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2015-12-09\n \n \n * CLOSED DATE\n 2016-02-01\n \n \n * LAST MODIFIED DATE\n 2016-02-01\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS\n * R856 PSY\n UP" ]

[ [ "1a", " FIXES ARE AVAILABLE" ], [ "1b", "Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24037683]" ], [ "1c", "Download Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24037734] SUBSCRIBE" ], [ "1d", "You can track all active APARs for this component. APAR STATUS" ], [ "1e", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "1f", " * When starting a BPD (with snapshot id or without) the process" ], [ "1g", " is started with the incorrect versioning context. This causes" ], [ "1h", " instance migration to not be possible if the BPD of interest is" ], [ "1i", " located inside a toolkit. LOCAL FIX" ], [ "1j", " * n/a PROBLEM SUMMARY" ], [ "1k", " * ABSTRACT ?" ], [ "1l", "INCORRECT ROOT VERSIONING CONTEXT USED WHEN STARTING" ], [ "1m", " BPD FROM TOOLKIT" ], [ "1n", " ERROR DESCRIPTION - If an exposed BPD from a toolkit is started" ], [ "1o", " using Portal or REST API, the active instances are not counted" ], [ "1p", " in the Process Admin Console ?" ], [ "1q", "Installed Apps section." ], [ "1r", " PRODUCTS AFFECTED" ], [ "1s", " IBM Business Process Manager (BPM) Advanced" ], [ "1t", " IBM BPM Standard" ], [ "1u", " IBM BPM Express" ], [ "1v", " LOCAL FIX - N/A" ], [ "1w", " PROBLEM SUMMARY ?" ], [ "1x", "When starting an exposed BPD from Process" ], [ "1y", " Portal or REST API (ie." ], [ "1z", " https://localhost:9443/rest/bpm/wle/v1/process?action=start&bpdI" ], [ "1aa", " d=<bpd_id>&snapshotId=<snapshot_id>), [https://localhost:9443/rest/bpm/wle/v1/process?action=start&bpdId=<bpd_id>&snapshotId=<snapshot_id>),] if the BPD resides in a" ], [ "1ab", " toolkit, Process Admin Console's ?Installed Apps?" ], [ "1ac", "page will not" ], [ "1ad", " show these active instances as part of the instance counter" ], [ "1ae", " displayed under the snapshot name. PROBLEM CONCLUSION" ], [ "1af", " * PROBLEM CONCLUSION ?" ], [ "1ag", " A fix is available for IBM BPM v8.0.1.2 to properly start the" ], [ "1ah", " BPD in the correct versioning context, allowing the instance to" ], [ "1ai", " be visible in the Process Admin Console." ], [ "1aj", " On Fix Central (http://www.ibm.com/support/fixcentral), search" ], [ "1ak", " for JR50141:" ], [ "1al", " 1.Select IBM Business Process Manager with your edition from the" ], [ "1am", " product selector, the installed version to the fix pack level," ], [ "1an", " and your platform, and then click Continue." ], [ "1ao", " 2.Select APAR or SPR, enter JR50141, and click Continue." ], [ "1ap", " When you download fix packages, ensure that you also download" ], [ "1aq", " the readme file for each fix." ], [ "1ar", "Review each readme file for" ], [ "1as", " additional installation instructions and information about the" ], [ "1at", " fix. TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "1au", " * APAR NUMBER" ], [ "1av", " JR50141" ], [ "1aw", " * REPORTED COMPONENT NAME" ], [ "1ax", " BPM STANDARD" ], [ "1ay", " * REPORTED COMPONENT ID" ], [ "1az", " 5725C9500" ], [ "1ba", " * REPORTED RELEASE" ], [ "1bb", " 801" ], [ "1bc", " * STATUS" ], [ "1bd", " CLOSED PER" ], [ "1be", " * PE" ], [ "1bf", " NoPE" ], [ "1bg", " * HIPER" ], [ "1bh", " NoHIPER" ], [ "1bi", " * SPECIAL ATTENTION" ], [ "1bj", " NoSpecatt" ], [ "1bk", " * SUBMITTED DATE" ], [ "1bl", " 2014-05-02" ], [ "1bm", " * CLOSED DATE" ], [ "1bn", " 2014-07-18" ], [ "1bo", " * LAST MODIFIED DATE" ], [ "1bp", " 2014-07-18" ], [ "1bq", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "1br", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "1bs", " * FIXED COMPONENT NAME" ], [ "1bt", " BPM STANDARD" ], [ "1bu", " * FIXED COMPONENT ID" ], [ "1bv", " 5725C9500" ], [ "1bw", "APPLICABLE COMPONENT LEVELS" ], [ "1bx", " * R801 PSY" ], [ "1by", " UP" ] ]

[ "1e", "1f", "1g", "1h", "1o", "1ah", "1ai", "1ao", "1ap", "1aq" ]

[ " NEWS\n\nABSTRACT\n WebSphere Message Broker V8.0 for WebSphere MQ V8 \n\nCONTENT\nWebsphere Message Broker V7\nWebSphere MQ V8 is not supported for use with Websphere Message Broker V7\n\nWebsphere Message Broker V8 - Runtime\n\nWebSphere MQ V8 is supported from Websphere Message Broker V8.0.0.4 onwards and the following steps will need to be taken in order for this to work:\n\n\nApply APAR IT03599 \n\nJRE Update\n\nDue to the fact that the WebSphere MQ V8 client JARs were built using Java 7, APAR IT03599 must be applied. This APAR package can be accessed by contacting IBM service and\ncontains a Java™ 7 JRE that can be used with an existing WebSphere Message Broker V8.0.0.4.\n\nThe APAR can be applied using the fix installer shipped with the package. This installer copies the Java 7 JRE to a new directory in the install path, alongside the Java 6 JRE. In order for the Java 7 JRE to be loaded at runtime the MQSI_JREPATH environment variable must be updated to point to the Java 7 JRE. This change can be made in the mqsiprofile script to ensure that changes are persisted across different user sessions. Detailed instructions for this process can be found in the APAR readme.\n\n\nIDPWOS Authentication\n\nFor a new WebSphere MQ Version 8.0 installation, the CONNAUTH CHCKLOCL attribute is set to OPTIONAL. This means that user IDs and passwords are not required, but if they are provided they must be a valid pair, or they will be rejected.\n\nCurrently, the Websphere Message Broker and IBM Integration Toolkits only pass a Username to MQ, and therefore due to the new default, a MQRC 2035 (MQRC_NOT_AUTHORIZED) error will be seen when trying to connect to a Broker using a WebSphere MQ V8 Queue Manager using the CMP.\n\nThe APAR IT03599 includes a new ConfigManagerProxy.jar that will allow all the mqsi commands to work without error. \n\n\n\n\nWebsphere Message Broker V8 – Clients\n\n\nClients that make use of CMP such as Message Broker Toolkit will face the same issue with the IDPWOS Authentication described above. Therefore in order for them to work with WebSphere MQ V8 the following 'runmqsc' commands can be run to disable the new IDPWOS Authentication that is enabled by default in MQ8:\n\nALTER AUTHINFO(SYSTEM.DEFAULT.AUTHINFO.IDPWOS) AUTHTYPE(IDPWOS) CHCKCLNT(NONE) \n\nREFRESH SECURITY TYPE(CONNAUTH) \n\nThese commands remove the optional requirement for Username and Password authentication when connecting to the Queue Manager locally and then refresh the Authentication Service so the changes are picked up.\n\nNote:\nFor runmqsc usage instructions see IBM Knowledge Center page:\nhttp://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ref.adm.doc/q083460_.htm [http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ref.adm.doc/q083460_.htm]\n\nIf you want to run using the default MQ Security settings with the Websphere Message Broker Toolkit or Explorer then you should contact IBM service to request APAR IT03599 which can be applied to the Toolkit and Explorer so that they can work with the new MQ Defaults. The Toolkit and Explorer have been enhanced to optionally use a userid and password for the connection so you can connect remotely. The Message Broker API has two new methods to set the userid and password when using a Java application based on the Message Broker API.\nFor example,\nMQBrokerConnectionParameters bcp =\nnew MQBrokerConnectionParameters(host, port, qmgr);\nbcp.setConnectionUserid(\"myuser\");\nbcp.setConnectionPassword(\"mypassword\");\n\n\n\n\nWebSphere Message Broker Explorer V8\n\nThe Message Broker Explorer plugins are only supported with MQ Explorer versions 7.0.1, 7.1 or 7.5. \n\nAdministering MQ v8 brokers using Message Broker Explorer with MQ Explorer versions 7.0.1, 7.1 or 7.5 is supported with APAR IT03599 applied.", "z/os DIRECT LINKS TO FIXES\n7.1.1-TIV-TDI-FP0008 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Directory+Integrator&fixids=7.1.1-TIV-TDI-FP0008&source=SAR]\n7.1.1-TIV-TDI-FP0003 [http://www-01.ibm.com/support/docview.wss?uid=swg24035743]\n7.1.1-TIV-TDI-FP0004 [http://www-01.ibm.com/support/docview.wss?uid=swg24038511]\n7.1.1-TIV-TDI-FP0005 [http://www-01.ibm.com/support/docview.wss?uid=swg24040693]\n7.1.1-TIV-TDI-FP0006 [http://www-01.ibm.com/support/docview.wss?uid=swg24043146]\n7.1.1-TIV-TDI-FP0007 [http://www-01.ibm.com/support/docview.wss?uid=swg24044377]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Description:\n \n Customer is using TDI 7.0 Password Plugin.\n \n Customer explained that they have a local MQ on each domain\n controller\n (Windows 2008 R2.)\n The local MQ is only used for the password plugin. Despite\n this, we are\n seeing errors in the proxy.log saying that the address is\n already in\n use.\n \n Every few days they see an error in the proxy.log like:\n \n [2/23/12 6:32 PM] {JMSStore} INFO: CTGDKN214I An exception\n occurred while sending password update message. The exception\n will be\n ignored.\n com.ibm.msg.client.jms.DetailedIllegalStateException:\n JMSWMQ0018: Failed\n to connect to queue manager '' with connection mode 'Client' and\n host\n name 'sovpdc1(1425)'. Check the queue manager is started and if\n running\n in client mode, check there is a listener running. Please see\n the linked\n exception for more information.\n at\n com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(\n Reason.j\n ava:496)\n ....\n Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call\n failed\n with compcode '2' ('MQCC_FAILED') reason '2059'\n ('MQRC_Q_MGR_NOT_AVAILABLE').\n at\n com.ibm.msg.client.wmq.common.internal.Reason.createException(Re\n ason.jav\n a:223)\n ... 12 more\n Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2059;AMQ9204:\n Connection to host 'sovpdc1(1425)' rejected.\n [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2059;AMQ9248: The\n program could\n not bind to a 'TCP' socket.\n [1=Socket.bind,3=TCP,4=1,5=java.net.BindException[Address\n already in\n use:\n NET_Bind]]],3=sovpdc1(1425),5=RemoteTCPConnection.connnectUsingL\n ocalAddr\n ess]\n \n this is the plugin.log\n \n INFO: 480: Thu Feb 23 18:32:03 2012: : Entering PasswordFilter\n INFO: 480: Thu Feb 23 18:32:03 2012: : User: OWENSEL\n INFO: 480: Thu Feb 23 18:32:03 2012: : FullName: owensel\n INFO: 480: Thu Feb 23 18:32:03 2012: : SetOperation = 0\n INFO: 480: Thu Feb 23 18:32:03 2012: : Exiting PasswordFilter\n INFO: 480: Thu Feb 23 18:32:03 2012: : Entering\n PasswordChangeNotify\n INFO: 480: Thu Feb 23 18:32:03 2012: : User: OWENSEL\n INFO: 480: Thu Feb 23 18:32:03 2012: : Relative ID (RID) of the\n user:\n 61434\n ERROR: 480: Thu Feb 23 18:32:03 2012: : The proxy response\n represents\n error.\n ERROR: 480: Thu Feb 23 18:32:03 2012: : Could not synchronize\n password\n for user 'OWENSEL': PWPROXY_ERROR_PROTOCOL_PASSWORD_OP_FAILED\n INFO: 480: Thu Feb 23 18:32:03 2012: : Exiting\n PasswordChangeNotify\n \n So the local MQ is telling the TDI Password Plugin that the\n host/port is\n already in use, even though MQ is only being used for the TDI\n Password\n Plugin.\n \n Engineering has provided a JAR file which should provide more\n logging\n information.\n \n Steps to Duplicate: This cannot be duplicated on command.\n \n Desired Behavior: The customer would like to determine the cause\n and\n prevent the error from MQ.\n \n Environment: TDI 7.0, Windows 2008 R2, MQ 7.0.1.3\n \n \n \n \n \n\nLOCAL FIX\n * 1679\n \n \n \n \n \n\nPROBLEM SUMMARY\n * MQ related error messages should not be seen in the logs. The\n error occurs because of dynamic port changes while communicating\n with MQ.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This is a bug in the TDI code and has been fixed. The official\n fix would be made available in 7.1.1-TIV-TDI-FP0003.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IO17880\n \n \n * REPORTED COMPONENT NAME\n ITDI MULTIPLATF\n \n \n * REPORTED COMPONENT ID\n 5724D9960\n \n \n * REPORTED RELEASE\n 711\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2013-01-09\n \n \n * CLOSED DATE\n 2013-01-09\n \n \n * LAST MODIFIED DATE\n 2013-01-09\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n IO17673 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO17673]\n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n ITDI MULTIPLATF\n \n \n * FIXED COMPONENT ID\n 5724D9960\n \n \n\nAPPLICABLE COMPONENT LEVELS", "CWSJY0003W JMSWMQ1107 DetailedJMSException J2CA0206W TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You notice CWSJY0003W messages with detailed exception message JMSWMQ1107 appear just after an Activation Specification has reconnected to WebSphere MQ. \n\nSYMPTOM\nWhen you use the WebSphere MQ messaging provider in WebSphere Application Server Version 7.x, you see the following warning messages in the application server's SystemOut.log file immediately after an Activation Specification has reconnected to WebSphere MQ: \n\nCWSJY0003W: ActivationSpec '<name>' reconnected successfully.\nJ2CA0206W: A connection error occurred. To help determine the problem,\nenable the Diagnose Connection Usage option on the Connection\nFactory or Data Source.\nJ2CA0056I: The Connection Manager received a fatal connection error from\nthe Resource Adaptor for resource <connection factory>. The\nexception which was received is : com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ1107: A problem with\nthis connection has occurred: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN'). \nCWSJY0003W: An exception has been delivered to the connections exception\nlistener: \nMessage : com.ibm.msg.client.jms.DetailedJMSException:\nJMSWMQ1107: A problem with this connection has occurred. An\nerror has occurred with the WebSphere MQ JMS connection. Use the\nlinked exception to determine the cause of this error.\nClass : class com.ibm.msg.client.jms.DetailedJMSException\nStack : com.ibm.msg.client.wmq.common.internal.Reason.\nreasonToException(Reason.java:601)\n: com.ibm.msg.client.wmq.common.internal.Reason.\ncreateException(Reason.java:219)\n: com.ibm.msg.client.wmq.internal.WMQSession.\ndisconnect(WMQSession.java:719)\n: com.ibm.msg.client.wmq.internal.WMQSession.\nclose(WMQSession.java:678)\n: com.ibm.msg.client.jms.internal.JmsSessionImpl.\nclose(JmsSessionImpl.java:439)\n: com.ibm.msg.client.jms.internal.JmsConnectionImpl.\nclose(JmsConnectionImpl.java:273)\n: com.ibm.mq.jms.MQConnection.close(MQConnection.java:93)\n: com.ibm.ejs.jms.JMSManagedConnection.\ndestroy(JMSManagedConnection.java:1118)\n: com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1852)\n: com.ibm.ejs.j2c.FreePool.\ncleanupAndDestroyMCWrapper(FreePool.java:738)\n: com.ibm.ejs.j2c.FreePool.getFreeConnection(FreePool.java:886)\n<stack trace truncated>\nCaused by [1] --> Message : com.ibm.mq.MQException: JMSCMQ0001:\nWebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason\n'2009' ('MQRC_CONNECTION_BROKEN').\nClass : class com.ibm.mq.MQException\nStack : com.ibm.msg.client.wmq.common.internal.Reason.\ncreateException(Reason.java:206)\n: com.ibm.msg.client.wmq.internal.WMQSession.\ndisconnect(WMQSession.java:719)\n: com.ibm.msg.client.wmq.internal.WMQSession.\nclose(WMQSession.java:678)\n: com.ibm.msg.client.jms.internal.JmsSessionImpl.\nclose(JmsSessionImpl.java:439)\n: com.ibm.msg.client.jms.internal.JmsConnectionImpl.\nclose(JmsConnectionImpl.java:273)\n: com.ibm.mq.jms.MQConnection.close(MQConnection.java:93)\n: com.ibm.ejs.jms.JMSManagedConnection.\ndestroy(JMSManagedConnection.java:1118)\n: com.ibm.ejs.j2c.MCWrapper.destroy(MCWrapper.java:1852)\n: com.ibm.ejs.j2c.FreePool.\ncleanupAndDestroyMCWrapper(FreePool.java:738)\n: com.ibm.ejs.j2c.FreePool.getFreeConnection(FreePool.java:886)\n<stack trace truncated>\n\n\nRESOLVING THE PROBLEM\nThe warning messages that appear in the SystemOut.log file immediately after the message:\n\nCWSJY0003W: ActivationSpec '<name>' reconnected successfully.\n\nare for connections that were in the application server's connection pool when the original connection error was detected. They are the result of the way the application server's connection pool works, and not an application issue. The messages can be safely ignored. \n\nThere is a connection pool for every connection factory defined in the application server, which is used for outbound messaging (for example, when applications running inside of WebSphere Application Server send messages to WebSphere MQ). When the connection being used by the Activation Specification is broken, the Activation Specification is stopped and restarted automatically - this ensures that a new connection to WebSphere MQ is established. \n\nAs part of this processing, any outbound connections to the same queue manager in the connection pool are closed off using WebSphere MQ API calls. However, as the connections to the queue manager have been broken, these API calls cannot complete successfully which results in the J2CA0206W, J2CA0056I and CWSJY0003W messages appearing in the SystemOut.log file.", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This article covers the most common reasons why an application running in WebSphere Application Server receives a 2035 MQRC_NOT_AUTHORIZED error when connecting to MQ as a client over a network. Quick steps to work around the MQRC_NOT_AUTHORIZED errors during development are provided in the 'Resolving the problem' section, as well as considerations for implementing security in production environments. A summary is also provided of behavior for outbound scenarios with container-managed and component-managed security, as well as inbound behavior for listener ports and activiation specifications \n\nSYMPTOM\nJMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')\n\n\nCAUSE\nThe two most likely reasons why the connection is refused by MQ are as follows: \n\n 1. The user identifier passed across the client connection from the application server to MQ is not known on the server where the MQ queue manager is running, is not authorised to connect to MQ, or is longer than 12 characters and has been truncated.\n We discuss how this user identifier is obtained and passed over the connection in more detail below.\n For queue managers running on Windows, the following error might be seen in the MQ error logs for this scenario:\n AMQ8075: Authorization failed because the SID for entity 'wasuser' cannot be obtained.\n For UNIX no entry in the MQ error logs would be seen by default.\n See technote MQS_REPORT_NOAUTH environment variable can be used to better diagnose return code 2035 [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg21299319] for details of enabling error log entries on all platforms. \n 2. The user identifier passed across the client connection from the application server to MQ is a member of the 'mqm' group on the server hosting the MQ queue manager, and a Channel Authentication Record (CHLAUTH) exists that blocks administrative access to the queue manager. WebSphere MQ configures a CHLAUTH record by default in WebSphere MQ Version 7.1 and later that blocks all MQ admins from connecting as a client to the queue manager.\n The following error in the MQ error logs would be seen for this scenario:\n AMQ9777: Channel was blocked\n\nSee the Error logs on Windows, UNIX and Linux systems [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.tro.doc/q039560_.htm] section of the MQ Information Center for the location of the MQ error logs. \nDIAGNOSING THE PROBLEM\nTo understand the cause of the MQRC_NOT_AUTHORIZED reason code, you need to understand what username (and password) is being used by MQ to authorise the application server. \n\nPlease note that WebSphere MQ V7.5 and earlier does not provide any out-of-the box password authentication system for client connections.\nPassword authentication is provided out of the box in IBM MQ V8.0. More details on the new IBM MQ V8.0 security features are available in this presentation [https://www.slideshare.net/MoragHughson/websphere-mq-v8-security-deep-dive]. \n\nFor WebSphere MQ V7.5 and earlier, this means that while the understanding provided in this technote over how usernames/passwords are passed from the application server to MQ is helpful for development environments, solving the security requirements of production environments usually also requires one of the following approaches: \n\n * Mutual SSL/TLS authentication.\n MQ provides out-of-the-box features to authenticate a remotely attaching client using the digital certificate they provide for SSL/TLS transport security. For example by configuring an SSLPEER rule on the SVRCONN channel to match the Distinguished Name in the certificate of the WebSphere Application Server, and establishing trust in the issuer of that certificate. \n * A custom, or 3rd party supplied, WebSphere MQ Security Exit\n A security exit can be written for MQ that performs username and password authentication against a repository, such as the local operating system on the MQ server, or an LDAP repository.\n When using a security exit for authentication it is important that SSL/TLS transport security is still configured, to ensure passwords are not sent in plain text.\n\n\nMCA user ID (MCAUSER) configured on the Server Connection (SVRCONN) channel If an MCAUSER is configured on the SVRCONN channel that the application server is using to connect, and no security exit or mapping Channel Authentication Record is installed, then this overrides the username provided by the application server. \n\nIt is common practice for many customers to set an MCAUSER on every SVRCONN channel, and use mutual SSL/TLS authentication exclusively for authentication. \n\nDefault behaviour when no credentials are supplied in the application server \n\nIf no credentials are supplied by the application on the createConnection call, and neither of the component managed or container managed security systems described below are configured, then WebSphere Application Server provides a blank username to MQ. This causes MQ to authorise the client based on the userid that the MQ listener is running under. In the majority of cases this is 'mqm' on UNIX/Linux systems and 'MUSR_MQADMIN' on Windows. \n\nAs these are administrative MQ users, they will be blocked by default in WebSphere MQ V7.1 and higher, with a AMQ9777 error logged in the error logs of the queue manager. \n\nContainer-managed security for outbound connections \n\nThe recommended way to configure the username and password passed to MQ by the application server for outbound connections, is to use container-managed security. Outbound connections are those created using a Connection Factory, rather than a Listener Port or Activation Specification. \n\nUsernames of 12 characters or less are passed to MQ by the appliaction server. Usernames longer than 12 characters in length will be truncated, either during authorisation (on UNIX), or in the MQMD of messages that are sent. \n\nContainer-managed security means that the deployment descriptor, or EJB 3.0 annotations, of the application declare a resource reference with authentication type set to Container. \n\nThen when the application looks up the Connection Factory in JNDI, it does so indirectly via the resource reference. For example an EJB 2.1 application would perform a JNDI lookup as follows, where \"jms/MyResourceRef\" has been declared as a resource reference in the deployment descriptor: \n\nConnectionFactory myCF = (ConnectionFactory)ctx.lookup(\"java:comp/env/jms/MyResourceRef\") \n\nAn EJB 3.0 application might declare an annotated object property on the bean as follows:\n@Resource(name = \"jms/MyResourceRef\", \nauthenticationType = AuthenticationType.CONTAINER)\nprivate javax.jms.ConnectionFactory myCF; \n\nWhen the application is deployed by an administrator, they bind this authentication alias to an actual Connection Factory that has been created in JNDI, and assign it a J2C authentication alias on deployment. \n\nIt is the username and password contained in this authentication alias that is then passed to MQ/JMS by the application server when the application connects. This approach puts the administrator in control of which username and password is used by each application, and prevents a different application from looking up the connection factory in JNDI directly to connect with the same username and password. \n\nA default container-managed authentication alias can be supplied on the configuration panels in the administrative console for MQ connection factories. This default will only be used in the case that an application uses a resource reference configured for container-managed security, but the administrator has not bound it to an authentication alias during deployment. A screen shot is provided below:\n[/support/docview.wss?uid=swg21636093&aid=1] [/support/docview.wss?uid=swg21636093&aid=1] \n\nDefault component-managed authentication alias for outbound connections \n\nFor cases where it is impractical to change the application to use container-managed security, or to change it to supply a username and password directly on the createConnection call, it is possible to supply a default. \n\nThis default is called the \"component-managed authentication alias\" and cannot be configured via the administrative console (since WebSphere Application Server Version 7.0 when it was removed from the panels MQ connection factories). The below scripting samples show how to configure it using wsadmin: \n\n * JACL:\n wsadmin>set cell [ $AdminConfig getid \"/Cell:mycell\" ]\n \n mycell(cells/mycell|cell.xml#Cell_1)\n \n wsadmin>$AdminTask listWMQConnectionFactories $cell\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)\n \n wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) \n * Jython:\n wsadmin>cell = AdminConfig.getid(\"/Cell:mycell\")\n \n wsadmin>AdminTask.listWMQConnectionFactories(cell)\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n \n wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', \"-componentAuthAlias myalias\")\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n\n\nAuthentication alias for inbound MDB connections using an activation specification For inbound connections using an activation specification an authentication alias can be specified by the administrator when deploying the application, or a default authentication alias can be specified on the activation specification via the administrative console. \n\nAuthentication alias for inbound MDB connections using a listener port \n\nFor inbound connections using a listener port, the value specified in the \"Container-managed authentication alias\" setting of the connection factory (seen in the above screenshot) is used. \n\nOn zOS, first the \"Container-managed authentication alias\" is checked and used if set, then the \"Component-managed authentication alias\" is checked and used it set.\n\n\nRESOLVING THE PROBLEM\nThe simplest steps to resolve the 2035 MQRC_NOT_AUTHORIZED errors in a development environment, where full transport security is not required, are as follows: \n\n 1. Choose a user that you want WebSphere Application Server to be authenticated as. Typically the user chosen should have authority relevant to the context of the operations required by the application running in WebSphere Application Server and no more. For example, 'mqm' or other super user is not appropriate. \n 2. If this user is an MQ administrative user, then relax the Channel Authentication Record (CHLAUTH) security in MQ V7.1 or higher, so that administrative connections are not blocked on the SVRCONN channel you wish to use. An example MQSC command to do this for a SVRCONN channel called 'WAS.CLIENTS' is provided as follows:\n SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY) \n 3. Configure the SVRCONN channel to set the MCA user ID (MCAUSER) to the user you have chosen. An example MQSC command to configure a SVRCONN channel to use 'myuser' as the MCA user ID is provided as follows:\n ALTER CHL('WAS.CLIENTS') CHLTYPE(SVRCONN) MCAUSER('myuser')\n\n\nThe following additional considerations are important for production environments: For all production environments where transport security is required, SSL/TLS security must be configured between the application server and MQ. \n\nIn order to configure SSL/TLS transport security, you must establish the appropriate trust between the MQ queue manager and WebSphere Application Server. The application server, who initiates the SSL/TLS handshake, must always be configured to trust the certificate provided by the MQ queue manager . If the application server is configured to send a certificate to the MQ queue manager, then the queue manager must also be configured to trust it. \n\nIf trust is not correctly configured on both sides, you will encounter 2393 MQRC_SSL_INITIALIZATION_ERROR reason codes after enabling SSL/TLS on the connection. \n\nIf you do not have a security exit that performs username and password authentication, then you should configure mutual SSL/TLS authentication on your Server Connection channel to cause the queue manager to require a trusted certificate is provided by the application server. To do this you set \"SSL Authentication\" to \"Required\" in the MQ Explorer or SSLCAUTH(REQUIRED) via MQSC. \n\nIf you do have a security exit that performs username and password authentication installed in your MQ server, then configure your application to supply a username and password for validation by that security exit. The details of how to configure the username and password passed to MQ by the application server are described above in the \"Diagnosing the problem\" section. \n\nAll Server Connection channels that do not have SSL/TLS security applied should be disabled. Example MQSC commands to disable the SYSTEM.DEF.SVRCONN channel are provided as follows (these assume no user exists on the MQ server called 'NOAUTH'):\nALTER CHL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('NOAUTH')\nSTOP CHL(SYSTEM.DEF.SVRCONN) \n\nDetails of how to configure the private certificate and trust of a MQ queue manager, and to enable SSL security on a Server Connection channel, see the following locations in the MQ information center: \n\n * To configure the certificates and trust of the MQ queue manager see the following topic:\n Configuring SSL on queue managers [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.explorer.doc%2Fe_ssl_channels.htm] \n * To configure the Server Connection channel, used by applications running in the application server to connect to MQ, see the following topic:\n Configuring SSL channels [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.explorer.doc/e_ssl_channels.htm]\n\n\nDetails of how you configure trust within WebSphere Application Server, and whether the application server sends a certificate to MQ for authentication, are in the following locations in the WebSphere Application Server information center: * To create or modify an SSL Configuration containing the appropriate SSL/TLS configuration for connecting to MQ, see the following topic:\n SSL configurations [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-dist&topic=csec_sslconfigs]\n Note that MQ requires you specify a matching Cipher Suite / Cipher Spec on both sides of the connection, as it checks the negotiated Cipher Suite matches the SSLCIPH setting on the channel after the handshake is complete. As a result the WebSphere Application Server SSL Configuration should be configured to contain only the Cipher Suite that matches the SSLCIPH setting on the Server Connection channel. See the following topic in the MQ information center for details of matching pairs:\n CipherSuite and CipherSpec name mappings for connections to a WebSphere® MQ queue manager [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.msc.doc/xms_csecure_mapping_wmq.html] \n * To enable SSL/TLS on a client connection, and choose which SSL Configuration to use, see the \"Use SSL to secure communication with Websphere MQ\", \"Centrally managed\" and \"Specific configuration\" sections of the following topics on Connection Factories and Activation Specifications\n WebSphere MQ messaging provider connection factory settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pjcfm]\n WebSphere MQ messaging provider activation specification settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pasm]\n\n \n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server for z/OS Java Messaging Service (JMS) z/OS, OS/390 8.5, 8.0, 7.0 Business Integration WebSphere Business Monitor AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.5.1, 7.5, 7.0 Advanced, Basic Business Integration WebSphere Message Broker Environment AIX, HP-UX, Linux, Solaris, Windows, z/OS 9.0, 8.0, 7.0 Business Integration WebSphere MQ Clients AIX, HP-UX, IBM i, Linux, Windows 8.0, 7.5, 7.1, 7.0", " A FIX IS AVAILABLE\nFix Pack 7.1.0.3 for WebSphere MQ V7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24035405]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * An IBM WebSphere MQ JMS client in ASF mode encounters the\n following exception when attempting to handle a poison message\n from a managed queue:\n \n [9/27/12 16:33:37:341 BST] 00000024 SibMessage W [:]\n CWSJY0003W: JMSCC0110: An exception '\n Message :\n com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ0030:\n 'MQOPEN' failed for destination\n 'SYSTEM.MANAGED.DURABLE.1234567890' when handling a poison\n message.\n When requeuing a poison message, 'MQOPEN' failed when called for\n the destination 'SYSTEM.MANAGED.DURABLE.1234567890'.\n Please see the linked exception for more information on the\n failures and/or warnings.\n Class : class\n com.ibm.msg.client.jms.DetailedJMSSecurityException\n Stack :\n com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(\n Reason.java:516)\n :\n com.ibm.msg.client.wmq.common.internal.Reason.createException(Re\n ason.java:216)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison.checkJmqiCallSuccess(W\n MQPoison.java:1372)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison.access$2400(WMQPoison.\n java:79)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison$DestinationAttrs.<init\n >(WMQPoison.java:1460)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison$DestinationAttrs.<init\n >(WMQPoison.java:1424)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison$DestinationAttrs.<init\n >(WMQPoison.java:1416)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison.<init>(WMQPoison.java:\n 174)\n :\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialisePois\n on(WMQConsumerShadow.java:1315)\n :\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQCons\n umerShadow.java:1462)\n :\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQCons\n umerShadow.java:1354)\n :\n com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.receive(WM\n QSyncConsumerShadow.java:360)\n :\n com.ibm.msg.client.wmq.internal.WMQSession.loadMessageReference(\n WMQSession.java:1277)\n :\n com.ibm.msg.client.jms.internal.JmsSessionImpl.consume(JmsSessio\n nImpl.java:3098)\n :\n com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImp\n l.java:2739)\n :\n com.ibm.mq.jms.MQSession.run(MQSession.java:950)\n :\n com.ibm.mq.connector.inbound.ASFWorkImpl.doDelivery(ASFWorkImpl.\n java:88)\n :\n com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkIm\n pl.java:216)\n :\n com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399)\n :\n com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)\n Caused by [1] --> Message : com.ibm.mq.MQException:\n JMSCMQ0001: WebSphere MQ call failed with compcode '2'\n ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').\n Class : class com.ibm.mq.MQException\n Stack :\n com.ibm.msg.client.wmq.common.internal.Reason.createException(Re\n ason.java:204)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison.checkJmqiCallSuccess(W\n MQPoison.java:1372)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison.access$2400(WMQPoison.\n java:79)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison$DestinationAttrs.<init\n >(WMQPoison.java:1460)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison$DestinationAttrs.<init\n >(WMQPoison.java:1424)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison$DestinationAttrs.<init\n >(WMQPoison.java:1416)\n :\n com.ibm.msg.client.wmq.internal.WMQPoison.<init>(WMQPoison.java:\n 174)\n :\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.initialisePois\n on(WMQConsumerShadow.java:1315)\n :\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQCons\n umerShadow.java:1462)\n :\n com.ibm.msg.client.wmq.internal.WMQConsumerShadow.getMsg(WMQCons\n umerShadow.java:1354)\n :\n com.ibm.msg.client.wmq.internal.WMQSyncConsumerShadow.receive(WM\n QSyncConsumerShadow.java:360)\n :\n com.ibm.msg.client.wmq.internal.WMQSession.loadMessageReference(\n WMQSession.java:1277)\n :\n com.ibm.msg.client.jms.internal.JmsSessionImpl.consume(JmsSessio\n nImpl.java:3098)\n :\n com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImp\n l.java:2739)\n :\n com.ibm.mq.jms.MQSession.run(MQSession.java:950)\n :\n com.ibm.mq.connector.inbound.ASFWorkImpl.doDelivery(ASFWorkImpl.\n java:88)\n :\n com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkIm\n pl.java:216)\n :\n com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399)\n :\n com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)\n ' was caught while processing a message for delivery to a\n message driven bean.\n \n \n \n \n \n\nLOCAL FIX\n * To work around this issue the 'INQ' authority must be granted to\n the user attempting to access the reported queue, in this\n example it would be SYSTEM.MANAGED.DURABLE.1234567890.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n All users of the v7.1 or v7.5 WebSphere MQ classes for JMS\n client in ASF mode who create durable subscriptions with managed\n queues.\n \n Platforms affected:\n All Distributed (iSeries, all Unix and Windows) +Java\n ****************************************************************\n PROBLEM SUMMARY:\n Because the durable subscription was backed by a managed queue,\n the internal representation within the WebSphere MQ classes for\n JMS client was as a queue. As a result of this an MQOPEN was\n attempted against the managed queue during poison message\n handling with the INQ option. This should not occur for\n subscriptions.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The code has been altered to ensure that a managed queue is not\n treated as a local queue when handling poison messages, instead\n the durable subscription is still treated as a subscription.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n v7.1\n Platform Fix Pack 7.1.0.3\n -------- --------------------\n Windows 7.1.0.3\n AIX 7.1.0.3\n HP-UX (Itanium) 7.1.0.3\n Solaris (SPARC) 7.1.0.3\n Solaris (x86-64) 7.1.0.3\n iSeries 7.1.0.3\n Linux (x86) 7.1.0.3\n Linux (x86-64) 7.1.0.3\n Linux (zSeries) 7.1.0.3\n Linux (Power) 7.1.0.3\n \n Platform v7.5\n -------- --------------------\n Multiplatforms 7.5.0.1\n \n The latest available maintenance can be obtained from\n 'WebSphere MQ Recommended Fixes'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037]\n \n If the maintenance level is not yet available information on\n its planned availability can be found in 'WebSphere MQ\n Planned Maintenance Release Dates'\n http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 [http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309]\n ---------------------------------------------------------------\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC89347\n \n \n * REPORTED COMPONENT NAME\n WMQ WINDOWS V7\n \n \n * REPORTED COMPONENT ID\n 5724H7220\n \n \n * REPORTED RELEASE\n 710\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2013-01-03\n \n \n * CLOSED DATE\n 2013-01-07\n \n \n * LAST MODIFIED DATE\n 2013-01-07\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WMQ WINDOWS V7\n \n \n * FIXED COMPONENT ID\n 5724H7220\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R710 PSY\n UP" ]

[ [ "3a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "3b", " This article covers the most common reasons why an application running in WebSphere Application Server receives a 2035 MQRC_NOT_AUTHORIZED error when connecting to MQ as a client over a network." ], [ "3c", "Quick steps to work around the MQRC_NOT_AUTHORIZED errors during development are provided in the 'Resolving the problem' section, as well as considerations for implementing security in production environments." ], [ "3d", "A summary is also provided of behavior for outbound scenarios with container-managed and component-managed security, as well as inbound behavior for listener ports and activiation specifications SYMPTOM" ], [ "3e", "JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED') CAUSE" ], [ "3f", "The two most likely reasons why the connection is refused by MQ are as follows: 1." ], [ "3g", "The user identifier passed across the client connection from the application server to MQ is not known on the server where the MQ queue manager is running, is not authorised to connect to MQ, or is longer than 12 characters and has been truncated." ], [ "3h", " We discuss how this user identifier is obtained and passed over the connection in more detail below." ], [ "3i", " For queue managers running on Windows, the following error might be seen in the MQ error logs for this scenario:" ], [ "3j", " AMQ8075: Authorization failed because the SID for entity 'wasuser' cannot be obtained." ], [ "3k", " For UNIX no entry in the MQ error logs would be seen by default." ], [ "3l", " See technote MQS_REPORT_NOAUTH environment variable can be used to better diagnose return code 2035 [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg21299319] for details of enabling error log entries on all platforms. 2." ], [ "3m", "The user identifier passed across the client connection from the application server to MQ is a member of the 'mqm' group on the server hosting the MQ queue manager, and a Channel Authentication Record (CHLAUTH) exists that blocks administrative access to the queue manager." ], [ "3n", "WebSphere MQ configures a CHLAUTH record by default in WebSphere MQ Version 7.1 and later that blocks all MQ admins from connecting as a client to the queue manager." ], [ "3o", " The following error in the MQ error logs would be seen for this scenario:" ], [ "3p", " AMQ9777: Channel was blocked" ], [ "3q", "See the Error logs on Windows, UNIX and Linux systems [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.tro.doc/q039560_.htm] section of the MQ Information Center for the location of the MQ error logs." ], [ "3r", "DIAGNOSING THE PROBLEM" ], [ "3s", "To understand the cause of the MQRC_NOT_AUTHORIZED reason code, you need to understand what username (and password) is being used by MQ to authorise the application server." ], [ "3t", "Please note that WebSphere MQ V7.5 and earlier does not provide any out-of-the box password authentication system for client connections." ], [ "3u", "Password authentication is provided out of the box in IBM MQ V8.0." ], [ "3v", "More details on the new IBM MQ V8.0 security features are available in this presentation [https://www.slideshare.net/MoragHughson/websphere-mq-v8-security-deep-dive]." ], [ "3w", "For WebSphere MQ V7.5 and earlier, this means that while the understanding provided in this technote over how usernames/passwords are passed from the application server to MQ is helpful for development environments, solving the security requirements of production environments usually also requires one of the following approaches:" ], [ "3x", " * Mutual SSL/TLS authentication." ], [ "3y", " MQ provides out-of-the-box features to authenticate a remotely attaching client using the digital certificate they provide for SSL/TLS transport security." ], [ "3z", "For example by configuring an SSLPEER rule on the SVRCONN channel to match the Distinguished Name in the certificate of the WebSphere Application Server, and establishing trust in the issuer of that certificate." ], [ "3aa", " * A custom, or 3rd party supplied, WebSphere MQ Security Exit" ], [ "3ab", " A security exit can be written for MQ that performs username and password authentication against a repository, such as the local operating system on the MQ server, or an LDAP repository." ], [ "3ac", " When using a security exit for authentication it is important that SSL/TLS transport security is still configured, to ensure passwords are not sent in plain text." ], [ "3ad", "MCA user ID (MCAUSER) configured on the Server Connection (SVRCONN) channel If an MCAUSER is configured on the SVRCONN channel that the application server is using to connect, and no security exit or mapping Channel Authentication Record is installed, then this overrides the username provided by the application server." ], [ "3ae", "It is common practice for many customers to set an MCAUSER on every SVRCONN channel, and use mutual SSL/TLS authentication exclusively for authentication." ], [ "3af", "Default behaviour when no credentials are supplied in the application server" ], [ "3ag", "If no credentials are supplied by the application on the createConnection call, and neither of the component managed or container managed security systems described below are configured, then WebSphere Application Server provides a blank username to MQ." ], [ "3ah", "This causes MQ to authorise the client based on the userid that the MQ listener is running under." ], [ "3ai", "In the majority of cases this is 'mqm' on UNIX/Linux systems and 'MUSR_MQADMIN' on Windows." ], [ "3aj", "As these are administrative MQ users, they will be blocked by default in WebSphere MQ V7.1 and higher, with a AMQ9777 error logged in the error logs of the queue manager." ], [ "3ak", "Container-managed security for outbound connections" ], [ "3al", "The recommended way to configure the username and password passed to MQ by the application server for outbound connections, is to use container-managed security." ], [ "3am", "Outbound connections are those created using a Connection Factory, rather than a Listener Port or Activation Specification." ], [ "3an", "Usernames of 12 characters or less are passed to MQ by the appliaction server." ], [ "3ao", "Usernames longer than 12 characters in length will be truncated, either during authorisation (on UNIX), or in the MQMD of messages that are sent." ], [ "3ap", "Container-managed security means that the deployment descriptor, or EJB 3.0 annotations, of the application declare a resource reference with authentication type set to Container." ], [ "3aq", "Then when the application looks up the Connection Factory in JNDI, it does so indirectly via the resource reference." ], [ "3ar", "For example an EJB 2.1 application would perform a JNDI lookup as follows, where \"jms/MyResourceRef\" has been declared as a resource reference in the deployment descriptor:" ], [ "3as", "ConnectionFactory myCF = (ConnectionFactory)ctx.lookup(\"java:comp/env/jms/MyResourceRef\")" ], [ "3at", "An EJB 3.0 application might declare an annotated object property on the bean as follows:" ], [ "3au", "@Resource(name = \"jms/MyResourceRef\"," ], [ "3av", "authenticationType = AuthenticationType.CONTAINER)" ], [ "3aw", "private javax.jms.ConnectionFactory myCF;" ], [ "3ax", "When the application is deployed by an administrator, they bind this authentication alias to an actual Connection Factory that has been created in JNDI, and assign it a J2C authentication alias on deployment." ], [ "3ay", "It is the username and password contained in this authentication alias that is then passed to MQ/JMS by the application server when the application connects." ], [ "3az", "This approach puts the administrator in control of which username and password is used by each application, and prevents a different application from looking up the connection factory in JNDI directly to connect with the same username and password." ], [ "3ba", "A default container-managed authentication alias can be supplied on the configuration panels in the administrative console for MQ connection factories." ], [ "3bb", "This default will only be used in the case that an application uses a resource reference configured for container-managed security, but the administrator has not bound it to an authentication alias during deployment." ], [ "3bc", "A screen shot is provided below: [/support/docview.wss?uid=swg21636093&aid=1] [/support/docview.wss?uid=swg21636093&aid=1]" ], [ "3bd", "Default component-managed authentication alias for outbound connections" ], [ "3be", "For cases where it is impractical to change the application to use container-managed security, or to change it to supply a username and password directly on the createConnection call, it is possible to supply a default." ], [ "3bf", "This default is called the \"component-managed authentication alias\" and cannot be configured via the administrative console (since WebSphere Application Server Version 7.0 when it was removed from the panels MQ connection factories)." ], [ "3bg", "The below scripting samples show how to configure it using wsadmin:" ], [ "3bh", " * JACL:" ], [ "3bi", " wsadmin>set cell [ $AdminConfig getid \"/Cell:mycell\" ]" ], [ "3bj", " mycell(cells/mycell|cell.xml#Cell_1)" ], [ "3bk", " wsadmin>$AdminTask listWMQConnectionFactories $cell" ], [ "3bl", " MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)" ], [ "3bm", " wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }" ], [ "3bn", " MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)" ], [ "3bo", " * Jython:" ], [ "3bp", " wsadmin>cell = AdminConfig.getid(\"/Cell:mycell\")" ], [ "3bq", " wsadmin>AdminTask.listWMQConnectionFactories(cell)" ], [ "3br", " 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'" ], [ "3bs", " wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', \"-componentAuthAlias myalias\")" ], [ "3bt", " 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'" ], [ "3bu", "Authentication alias for inbound MDB connections using an activation specification For inbound connections using an activation specification an authentication alias can be specified by the administrator when deploying the application, or a default authentication alias can be specified on the activation specification via the administrative console." ], [ "3bv", "Authentication alias for inbound MDB connections using a listener port" ], [ "3bw", "For inbound connections using a listener port, the value specified in the \"Container-managed authentication alias\" setting of the connection factory (seen in the above screenshot) is used." ], [ "3bx", "On zOS, first the \"Container-managed authentication alias\" is checked and used if set, then the \"Component-managed authentication alias\" is checked and used it set." ], [ "3by", "RESOLVING THE PROBLEM" ], [ "3bz", "The simplest steps to resolve the 2035 MQRC_NOT_AUTHORIZED errors in a development environment, where full transport security is not required, are as follows: 1." ], [ "3ca", "Choose a user that you want WebSphere Application Server to be authenticated as." ], [ "3cb", "Typically the user chosen should have authority relevant to the context of the operations required by the application running in WebSphere Application Server and no more." ], [ "3cc", "For example, 'mqm' or other super user is not appropriate. 2." ], [ "3cd", "If this user is an MQ administrative user, then relax the Channel Authentication Record (CHLAUTH) security in MQ V7.1 or higher, so that administrative connections are not blocked on the SVRCONN channel you wish to use." ], [ "3ce", "An example MQSC command to do this for a SVRCONN channel called 'WAS.CLIENTS' is provided as follows:" ], [ "3cf", " SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY) 3." ], [ "3cg", "Configure the SVRCONN channel to set the MCA user ID (MCAUSER) to the user you have chosen." ], [ "3ch", "An example MQSC command to configure a SVRCONN channel to use 'myuser' as the MCA user ID is provided as follows:" ], [ "3ci", " ALTER CHL('WAS.CLIENTS') CHLTYPE(SVRCONN) MCAUSER('myuser')" ], [ "3cj", "The following additional considerations are important for production environments: For all production environments where transport security is required, SSL/TLS security must be configured between the application server and MQ." ], [ "3ck", "In order to configure SSL/TLS transport security, you must establish the appropriate trust between the MQ queue manager and WebSphere Application Server." ], [ "3cl", "The application server, who initiates the SSL/TLS handshake, must always be configured to trust the certificate provided by the MQ queue manager ." ], [ "3cm", "If the application server is configured to send a certificate to the MQ queue manager, then the queue manager must also be configured to trust it." ], [ "3cn", "If trust is not correctly configured on both sides, you will encounter 2393 MQRC_SSL_INITIALIZATION_ERROR reason codes after enabling SSL/TLS on the connection." ], [ "3co", "If you do not have a security exit that performs username and password authentication, then you should configure mutual SSL/TLS authentication on your Server Connection channel to cause the queue manager to require a trusted certificate is provided by the application server." ], [ "3cp", "To do this you set \"SSL Authentication\" to \"Required\" in the MQ Explorer or SSLCAUTH(REQUIRED) via MQSC." ], [ "3cq", "If you do have a security exit that performs username and password authentication installed in your MQ server, then configure your application to supply a username and password for validation by that security exit." ], [ "3cr", "The details of how to configure the username and password passed to MQ by the application server are described above in the \"Diagnosing the problem\" section." ], [ "3cs", "All Server Connection channels that do not have SSL/TLS security applied should be disabled." ], [ "3ct", "Example MQSC commands to disable the SYSTEM.DEF.SVRCONN channel are provided as follows (these assume no user exists on the MQ server called 'NOAUTH'):" ], [ "3cu", "ALTER CHL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('NOAUTH') STOP CHL(SYSTEM.DEF.SVRCONN)" ], [ "3cv", "Details of how to configure the private certificate and trust of a MQ queue manager, and to enable SSL security on a Server Connection channel, see the following locations in the MQ information center:" ], [ "3cw", " * To configure the certificates and trust of the MQ queue manager see the following topic:" ], [ "3cx", " Configuring SSL on queue managers [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.explorer.doc%2Fe_ssl_channels.htm]" ], [ "3cy", " * To configure the Server Connection channel, used by applications running in the application server to connect to MQ, see the following topic:" ], [ "3cz", " Configuring SSL channels [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.explorer.doc/e_ssl_channels.htm]" ], [ "3da", "Details of how you configure trust within WebSphere Application Server, and whether the application server sends a certificate to MQ for authentication, are in the following locations in the WebSphere Application Server information center: * To create or modify an SSL Configuration containing the appropriate SSL/TLS configuration for connecting to MQ, see the following topic:" ], [ "3db", " SSL configurations [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-dist&topic=csec_sslconfigs]" ], [ "3dc", " Note that MQ requires you specify a matching Cipher Suite / Cipher Spec on both sides of the connection, as it checks the negotiated Cipher Suite matches the SSLCIPH setting on the channel after the handshake is complete." ], [ "3dd", "As a result the WebSphere Application Server SSL Configuration should be configured to contain only the Cipher Suite that matches the SSLCIPH setting on the Server Connection channel." ], [ "3de", "See the following topic in the MQ information center for details of matching pairs:" ], [ "3df", " CipherSuite and CipherSpec name mappings for connections to a WebSphere® MQ queue manager [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.msc.doc/xms_csecure_mapping_wmq.html]" ], [ "3dg", " * To enable SSL/TLS on a client connection, and choose which SSL Configuration to use, see the \"Use SSL to secure communication with Websphere MQ\", \"Centrally managed\" and \"Specific configuration\" sections of the following topics on Connection Factories and Activation Specifications" ], [ "3dh", " WebSphere MQ messaging provider connection factory settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pjcfm]" ], [ "3di", " WebSphere MQ messaging provider activation specification settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pasm]" ], [ "3dj", "Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server for z/OS Java Messaging Service (JMS) z/OS, OS/390 8.5, 8.0, 7.0 Business Integration WebSphere Business Monitor AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.5.1, 7.5, 7.0 Advanced, Basic Business Integration WebSphere Message Broker Environment AIX, HP-UX, Linux, Solaris, Windows, z/OS 9.0, 8.0, 7.0 Business Integration WebSphere MQ Clients AIX, HP-UX, IBM i, Linux, Windows 8.0, 7.5, 7.1, 7.0" ] ]

[ "3b", "3e", "3g", "3h", "3s", "3w", "3y", "3z", "3aa", "3ab", "3ac", "3af", "3ag", "3ah", "3aj" ]

[ "AIX 6.1; AIX61Cert; AIX71Cert TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you run the launchpad.sh command on IBM AIX Version 6.1 or 7.1, it might not bring up a launchpad console that you can use to install IBM WebSphere Application Server Version 6.0 or Version 6.1. \n\nCAUSE\nShell security enhancements in AIX Version 6.1 cause some commands to produce results that are different from those produced in earlier versions of AIX, including a command that is processed when you run the launchpad.sh command. Because of a difference in the processing of the 'typeset +r LOGNAME' command, the launchpad.sh command fails to produce a console window for installing WebSphere Application Server Version 6.0 or Version 6.1.\n\nRESOLVING THE PROBLEM\nFor WebSphere Application Server Version 6.0, run the ./install command instead of the ./launchpad.sh command. \n\nFor WebSphere Application Server Version 6.1, use one of the following solutions to solve the issue: \n\n * Obtain the WebSphere Application Server V6.1 for AIX 5L V5 installation images from the IBM Passport Advantage site as downloads or through ordering the physical media. Those images, which were updated on January 16, 2009, contain a fix for this launchpad issue. \n * Run the ./install command instead of the ./launchpad.sh command if you are still using the original installation images from 2006 and not the January 2009 images. \n * Use the launchpad to facilitate the installation of WebSphere Application Server Version 6.1 if you are using the original 2006 images. To use this solution, complete the following steps: 1. Extract the WebSphere Application Server installation image to a location on your AIX Version 6.1 or 7.1 system disk. \n 2. Install the bash rpm on your AIX system if it is not already installed. \n \n You can download the bash rpm from the following Web site: http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html [http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html]. \n 3. Download and unzip the attached launchpad_v2.0_fixpack18.zip file to a new directory of your choice on your AIX system.\n \n launchpad_v2.0_fixpack18.zip [/support/docview.wss?uid=swg21288640&aid=2] [/support/docview.wss?uid=swg21288640&aid=1] \n 4. Change to the launchpad_v2.0_fixpack18 subdirectory that contains the launchpad.sh command file and issue the following commands:\n \n chmod +x *.sh\n chmod +x launchpad/*.sh\n chmod +x launchpad/content/*\n chmod +x /usr/sbin/bootinfo \n \n Note: The last chmod command is only needed if a nonroot user will be installing WebSphere Application Server Version 6.1. \n 5. From here, copy all the files in this directory over the top of your existing launchpad installation.\n \n cp -r * your_directory/disk1/ \n 6. Go to the WebSphere Application Server Version 6.1 installation-image directory and run the ./launchpad.sh command. \n \n You should now see a launchpad console that you can use to install WebSphere Application Server Version 6.1.", "ITCAM compat-libstdc++ libstdc++ libraries silent_MS_linux.bin launchpad.sh errors TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nPROBLEM(ABSTRACT)\n Using the DC or MS 'launchpad.sh' script results in the following error message:\n./setup_MS_lin.bin: line 1926: warning: here-document at line 1926 \ndelimited by end-of-file (wanted `/dev/null') \n\nSYMPTOM\nThe following error is seen running when doing either 'launchpad.sh' or 'silent_MS_linux.bin': \n\n Initializing InstallShield Wizard........ \nLaunching InstallShield Wizard........ \n\n./setup_MS_lin.bin: line 1926: warning: here-document at line 1926 \ndelimited by end-of-file (wanted `/dev/null') \n\nThe installer is unable to run in graphical mode. Try running the \ninstaller with the -console for -silent flag.\n\n\nCAUSE\nMissing Linux system libraries.\n\n\nENVIRONMENT\nLinux - RHEL6.x and RHEL7.x 64-bit versions.\n\n\n\nRESOLVING THE PROBLEM\nThis error messag is seen because of some missing Linux libraries. Usually what's missing are the compat-libstdc++ or libstdc++ libraries. Usually the 32-bit version is missing. Use the commands shown below to verify you have them installed, otherwise contact your Linux system administrator and installt these required libraries. \n\n\n[/support/docview.wss?uid=swg21985630&aid=1] [/support/docview.wss?uid=swg21985630&aid=1]\n[/support/docview.wss?uid=swg21985630&aid=2] [/support/docview.wss?uid=swg21985630&aid=2]\n\n \n\nPRODUCT ALIAS/SYNONYM\n ITCAM4AD ITCAMfAD ITCAM for App Diagnostics", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Using SPSS data transformation procedures, I have tried to replicate the values for the discriminant scores that SPSS saved to my data file. The results I got were not identical to the scores calculated by the DISCRIMINANT procedure. Can you show me how to correctly compute discriminant scores? \n\nRESOLVING THE PROBLEM\nThe usual mistake that people make when they first try to do this is that they multiply the values from the table entitled Standardized Discriminant Function Coefficients by standardized values of the predictors. In so doing, they use the DESCRIPTIVES procedure to compute standardized variables (i.e., z-scores). The z-scores produced by DESCRIPTIVES have been standardized by the sample total standard deviations. The sample total standard deviations are computed for each variable using all of the cases in the file and ignoring group membership. What DISCRIMINANT does is to standardize by the pooled within-groups standard deviations. \n\nPooled within-groups standard deviations are calculated by pooling the variance estimates from each level of the grouping variable. The pooled within-groups variance estimates are the mean square error terms (MSE) from individual one-way ANOVAs. The square roots of these MSE values are the pooled within-groups standard deviations. Hence, to compute a z-score based upon the pooled-within groups standard deviation, we need a COMPUTE statement of the following form.\n\nLet ZPOOLED equal the z-score based upon the pooled standard deviation.\nLet X be the name of the predictor. \nLet MSE equal the mean square error terms from a one-way ANOVA with the predictor as the dependent variable. \nLet MEANX equal the mean value of X computed using all of the cases to be used in the analysis.\n\nAn SPSS COMPUTE statement for calculating ZPOOLED is as follows.\n\nCOMPUTE zpooled = (x - meanx) / SQRT(mse).\n\nYou can get all of the values you need to compute the discriminant scores yourself from output produced by DISCRIMINANT. The annotated command file below shows how to do this for a small sample data file.\n_________________________\n\n* The following commands read in a sample data file with two groups and two predictors .\n\nDATA LIST FREE\n/ group x y .\nBEGIN DATA\n1 1 3 \n1 2 2\n1 2 4\n1 3 3\n1 2 2\n2 3 5\n2 2 5\n2 3 4\n2 3 4\n2 4 3\nEND DATA.\nFORMATS group x y (F1.0) .\n\n* The following commands run the DISCRIMINANT analysis.\n* Note that we have used the SCORE keyword with the SAVE subcommand, which saves the discriminant scores computed by the procedure into a variable named DIS1_1. \n* We have also used the MEAN and COV keywords with the STATISTICS subcommand to request the printing of the means and the pooled-within groups covariance matrix.\n\nDISCRIMINANT\n/GROUPS=group(1 2)\n/VARIABLES=x y\n/ANALYSIS ALL\n/SAVE=SCORES\n/PRIORS EQUAL\n/STATISTICS=MEAN COV\n/CLASSIFY=NONMISSING POOLED .\n\n* The MEANS we need to compute ZPOOLED values for X and Y are shown in the rows identified as Total at the bottom of the output table entitled Group Statistics.\n* The mean values are 2.5 and 3.5 for X and Y, respectively.\n* The MSE values we need for X and Y may be read from the diagonal of the output table entitled Pooled Within-Groups Matrices.\n* The MSE values are .5 and .7 for X and Y, respectively.\n* The following COMPUTE statements create the two sets of z-scores standardized by the pooled within-qroups standard deviation.\n\nCOMPUTE zpooledx = (x - 2.5000000) / SQRT(.5000000) .\nCOMPUTE zpooledy = (y - 3.5000000) / SQRT(.7000000) .\n\n* The coefficients we need for the single set of standardized discriminant scores are given in the output table entitled Standardized Canonical Discriminant Function Coefficients.\n* The values are 0.8975670 and 0.9608713, for x and y, respectively.\n* The final COMPUTE statement (followed by a FORMATS and an EXECUTE command) saves a new variable called SCORE with values that are identical to those for DIS1_1.\n\nCOMPUTE score = (0.8975670 * zpooledx) + (0.9608713 * zpooledy) .\nFORMATS score (F7.5) .\nEXECUTE .\n_________________________ \n\nNote that the discriminant scores can also be computed by applying the raw or unstandardized discriminant function coefficients, including the constant for each function, to the raw predictor variable values.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\n\n \n\nHISTORICAL NUMBER\n 26270", "install error missing launchpad.sh manually manual installing TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The installation of Tivoli Integrated Portal component fails when IBM Security Role and Policy Modeler is not installed using the launchpad.sh script. \n\nSYMPTOM\nThe installation XML log file shows this error: \n\n<class>com.ibm.security.modeling.installer.middleware.panels.TipPanel.15</class>\n<method>widgetSelected</method>\n<message> Exception occured while :/tmp/TIP_Path_for_Rapm_Installer.txt (No such file or directory)</message>\n\n\nCAUSE\nThe launchpad.sh script creates the file \"TIP_Path_for_Rapm_Installer.txt\". If launchpad.sh is not used to start the installer, this file will not exist and the installation will fail.\n\n\nRESOLVING THE PROBLEM\nThere are two options to resolve this problem: \n\n1. If launchpad.sh will not run due to it not finding a supported browser, please refer to the linked technote below for details on how to update the launchpad.sh script to work with later versions of Firefox. \n\n \n\n2. If launchpad.sh still doesn't work, or fails for some other reason, then you can create the file manually. Before running the RaPM installer, use these steps to create the text file:\na. touch /tmp/TIP_Path_for_Rapm_Installer.txt\nb. Using a text editor, e.g. vi, open that file to add this line:\n\nTIPLocation=<Temp directory where you extracted the installer file>/disk1//\n\nc. Save and close the file\nd. Start the Installation Manager to install RaPM\n\nRELATED INFORMATION\n Update launchpad.sh for newer Firefox versions [http://www.ibm.com/support/docview.wss?uid=swg21619200]\n\n\n \n\nPRODUCT ALIAS/SYNONYM\n enrole itim tim isim rapm", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Sometimes I get an error message in SPSS that says \"A sharing violation has occurred while accessing <path and filename>\" whenever I try to read a file from another application, such as MS Excel, or I get a message that says \n\n\"Error 1216: A file cannot be opened. Probable causes are an attempt to open a read-only file for output, a directory which is too full, an invalid file specification, the specification of a nonexistent disk, etc. This command not executed.\" When I try to open the file from MS Word. \n\nWhy can't I read my data? \n\nRESOLVING THE PROBLEM\nApplications like MS Excel or MS Word will not allow SPSS for Windows to read a file if that same file is open in the other application. The solution is to close the file out of that other application before opening the file in SPSS\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\n\n\n \n\nHISTORICAL NUMBER\n 19660" ]

[ [ "1a", "ITCAM compat-libstdc++ libstdc++ libraries silent_MS_linux.bin launchpad.sh errors TECHNOTE (TROUBLESHOOTING)" ], [ "1b", "THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):" ], [ "1c", " US English PROBLEM(ABSTRACT)" ], [ "1d", " Using the DC or MS 'launchpad.sh' script results in the following error message:" ], [ "1e", "./setup_MS_lin.bin: line 1926: warning: here-document at line 1926" ], [ "1f", "delimited by end-of-file (wanted `/dev/null') SYMPTOM" ], [ "1g", "The following error is seen running when doing either 'launchpad.sh' or 'silent_MS_linux.bin':" ], [ "1h", " Initializing InstallShield Wizard........" ], [ "1i", "Launching InstallShield Wizard........" ], [ "1j", "./setup_MS_lin.bin: line 1926: warning: here-document at line 1926" ], [ "1k", "delimited by end-of-file (wanted `/dev/null')" ], [ "1l", "The installer is unable to run in graphical mode." ], [ "1m", "Try running the" ], [ "1n", "installer with the -console for -silent flag. CAUSE" ], [ "1o", "Missing Linux system libraries. ENVIRONMENT" ], [ "1p", "Linux - RHEL6.x and RHEL7.x 64-bit versions." ], [ "1q", "RESOLVING THE PROBLEM" ], [ "1r", "This error messag is seen because of some missing Linux libraries." ], [ "1s", "Usually what's missing are the compat-libstdc++ or libstdc++ libraries." ], [ "1t", "Usually the 32-bit version is missing." ], [ "1u", "Use the commands shown below to verify you have them installed, otherwise contact your Linux system administrator and installt these required libraries. [/support/docview.wss?uid=swg21985630&aid=1] [/support/docview.wss?uid=swg21985630&aid=1] [/support/docview.wss?uid=swg21985630&aid=2] [/support/docview.wss?uid=swg21985630&aid=2] PRODUCT ALIAS/SYNONYM" ], [ "1v", " ITCAM4AD ITCAMfAD ITCAM for App Diagnostics" ] ]

[ "1d", "1e", "1f", "1g", "1h", "1i", "1j", "1k", "1l", "1m", "1n", "1o", "1p", "1q", "1r", "1s", "1t", "1u" ]

[ "wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server. WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows.\n\nNotice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory.\nReference:\nUsing the WASServiceHelper utility to create Windows services for application servers\nhttps://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html]\n\nSee DeveloperWorks article for detailed information: (Link at the bottom of this document) \n\nSYMPTOM\nCreating and removing a WebSphere service in Windows is confusing and error prone.\n\n\nCAUSE\nThis application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\n\n\n\n 1. Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors.\n\n\n[/support/docview.wss?uid=swg21397335&amp;aid=1] Flash demonstration [http://public.dhe.ibm.com/software/websphere/appserv/support/tutorials/wasservicecmd.swf] \n\nNote: This also creates an entry in the WASServiceCmd.log in the current directory which contains the actual WASService.exe command used to create the service. \n\nExample of a log entry: \n\n[Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add \"Deployment Mgr01\" -serverName \"dmgr\" \n-profilePath \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\"\n-logRoot \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\"\n-logFile \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\\WS_startdmgr.log\" -encodeParams -stopArgs \"-username vanno -password ****** \" \n-startType manual \n-restart false WASServicecmd.zip [/support/docview.wss?uid=swg21397335&aid=3] [/support/docview.wss?uid=swg21397335&aid=2] \n\nNotice: Some browsers are having trouble downloading this file and getting docview.wss instead. Download this file, then rename the file with a \".zip\" extension (for example, docview.zip or WASServiceCmd.zip). You can now access the utility. \nSee DeveloperWorks article for more information: \nThe Support Authority: Take the confusion (and errors) out of creating Windows services for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/techjournal/1005_supauth/1005_supauth.html] \n\n\nSee TroubleShooting: WebSphere Application Server (Windows Services) problems for V6.0, V6.1 and V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21232884] if you are still having a problem with Windows services.", " FIXES ARE AVAILABLE\nInfoSphere Information Server, Version 11.3 for Microsoft Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24037518]\nInfoSphere Information Server, Version 11.3 for AIX [http://www-01.ibm.com/support/docview.wss?uid=swg24037780]\nInfoSphere Information Server, Version 11.3 for Linux [http://www-01.ibm.com/support/docview.wss?uid=swg24037781]\nIBM InfoSphere Information Server Enterprise Edition V11.3 for Windows [http://www-01.ibm.com/support/docview.wss?uid=swg24037840]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Customers running Information Server in a Clustered WebSphere\n Environment run into several errors while running the Patch\n Installer. The error is caused by timeout issues during a\n ripplestart\n \n In the System Out logs we see messages like the following\n NodeAgent A ADML0000I: The server initialization is\n complete. The process ID is: 16251, server name is:\n ServerNode01_01\n AdminHelper A ADMN1000I: An attempt is made to launch\n ServerNode01_02 on node ServerNode01. (User ID =\n ASBRealm/wsinfosphere)\n \n Thread \"SoapConnectorThreadPool : 0\" (00000083) has been\n active for 665451 milliseconds and may be hung.\n \n in the deployment manager logs we may see\n [8/6/13 17:05:58:396 UTC] 00000109 Cluster E WWLM0058E:\n Cluster member ServerNode01_04 did not start properly.\n javax.management.JMRuntimeException: ADMN0034E: The service is\n unable to obtain a valid administrative client to connect\n process \"ServerNode01\" from process \"dmgr\", because of\n exception:\n com.ibm.websphere.management.exception.ConnectorException:\n ADMC0009E: The system failed to make the SOAP RPC call: invoke\n \n \n \n \n \n\nLOCAL FIX\n * Customer has to reduce the number of running app servers to\n apply a patch or a fixpack.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Patch install runs forever in a large clustered environment if\n it takes more than 30 minutes to restart the cluster (each\n cluster node is sequentially stopped and started). The\n Deployment manager monitoring the startup, times out after 30\n minutes, and never indicates that the cluster finally started.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * In JR46053 [http://www-01.ibm.com/support/docview.wss?uid=swg1JR46053] to start the cluster we stop and start each cluster\n member sequentially. This can take a long time to go through all\n nodes, the 30 minute dmgr timeout could occur, and the patch\n install fails. The fix was to just do a start, and not use\n ripplestart.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n JR47768\n \n \n * REPORTED COMPONENT NAME\n INFO SRVR PLATF\n \n \n * REPORTED COMPONENT ID\n 5724Q3612\n \n \n * REPORTED RELEASE\n 910\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2013-09-13\n \n \n * CLOSED DATE\n 2014-04-10\n \n \n * LAST MODIFIED DATE\n 2014-04-10\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n INFO SRVR PLATF\n \n \n * FIXED COMPONENT ID\n 5724Q3612\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R912 PSY\n UP", "WebSphere Partner Gateway; MustGather; MustGatherDocument; MustGatherReadFirstDocument; startserver; stopserver TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Collecting data for problems with the start and stop of IBM WebSphere Partner Gateway (WPG) application servers, deployment manager or node agent. Gathering this MustGather information before calling IBM support will help expedite problem analysis. \n\nRESOLVING THE PROBLEM\n\nThis section instructs the items of documentation required by the IBM WPG support team to diagnose the problems, if an WPG application server, deployment manager (bcgdmgr) or nodeagent is not able to start or stop.\n\n\n\n\nFirstly, please fill up the following form with inquired information, copy and paste to the PMR description:\n(For instruction on how to get the these information, refer to WPG ReadFirst Technote [http://www.ibm.com/support/docview.wss?rs=2310&uid=swg21281975].)\n * Operating system, version and patch level: WPG version and fixpack level: Database, version and fixpack level: WAS (or WAS ND) fixpack level: WPG Topology (Simple/Simple Distributed/Full Distributed?): \n\nSecondly, please select from below for the area which reports start/stop problem. Then collect and upload MustGather data to the PMR: \n\nWPG SERVER\n \n\nIf an WPG application server (for example: bcgmas, bcgserver, bcgconsole..) is not able to start or stop, please take the below steps to collect required data.\n\n1. Backup and purge the logs under the following locations:\n\n\n * <bcghub>/wasND/Profiles/<bcgprofile>/logs/server_name\n * \n * <bcghub>/wasND/Profiles/<bcgprofile>/logs/ffdc \n\n\n\n2. Modify the file server.xml under the following location: \n * <bcghub>/wasND/Profiles/<bcgprofile>/config/cells/\n * \n * cell_name/nodes/node_name/servers/server_name\n * \n * \n * \n * \n * \n * \n * \n * \n * 1). Change the trace string \n From: \n startupTraceSpecification=\" *=info\" \n To: \n startupTraceSpecification=\" *=info:com.ibm.ws.*=all\" \n \n 2). Change the following string: \n From: \n maxNumberOfBackupFiles=\" 1\" \n To: \n maxNumberOfBackupFiles=\" 10\" \n \n 3). Save the changes. \n * \n\n\n3. Log in as WPG admin user (by default, it is 'bcguser'), go to the directory <bcghub>/wasND/Profiles/<bcgprofile>/bin, then run \"startServer servername -trace\" command. (This will log trace to the startServer.log file) NOTE: Similarly, if the Application Server does not stop when issuing the command: stopServer server_name, then please follow the same procedure documented above for collecting trace document, running the command stopServer in place of startServer. (This will log trace to the stoptServer.log file)\n\nIn case the stopServer command hangs and does not create stopServer.log file, the following actions should be followed, so as to capture the thread dumps:\n1. Execute kill -3 on the processid of the server. \n2. Execute for four times at 1 minute intervals. \n(This will write a thread dump to the nativestderr.log, which may help IBM Support to determine what the threads might be hanging.) \n4. When observe problem recurrence, run the WAS Collector tool [http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_runct.html] (collector script) under the following location:\n\n\n * \n * HUB\n * \n * \n * \n * \n * \n * \n * DMGR\n * \n * \n * \n * \n * \n * \n\n\n\n5. Follow the instruction to send the collected data to IBM Support [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852]. \n\n\n\n\n[/support/docview.wss?uid=swg21452561&amp;aid=1] Back to Top \n\n\nWPG BCGDMGR \n \n\nIn a distributed topology, if WPG deployment manager process (i.e. bcgdmgr) is not able to start or stop, please take the below steps to collect required data.\n\n1. Backup and purge the logs under the following locations: \n\n * <bcghub-dmgr>/wasND/Profiles/bcgdmgr/logs/bcgdmgr\n * \n * <bcghub-dmgr>/wasND/Profiles/bcgdmgr/logs/ffdc\n\n\n\n2. Modify the file server.xml under the following location: * <bcghub-dmgr>/wasND/Profiles/bcgdmgr/config/cells/\n wpgCell/nodes/node_name/servers/bcgdmgr\n * \n * 1). Change the trace string * \n * \n * \n * *=info\n * \n * \n * \n * \n * \n * *=info:com.ibm.ws.*=all\n * \n \n \n 2). Change the following string: * \n * \n * \n * 1\n * \n * \n * \n * \n * \n * 10\n * \n \n \n 3). Save the changes. \n * \n\n\n3. Log in as WPG admin user (by default, it is 'bcguser'), go to the directory <bcghub-dmgr>/wasND/Profiles/bcgdmgr/bin, then run \"startServer bcgdmgr -trace\" command. (This will log trace to the startServer.log file) NOTE: Similarly, if the deployment manager does not stop when issuing the command: stopServer bcgdmgr. Then please follow the same procedure documented above for collecting trace documents, running the command stopServer in place of startServer. (This will log trace to the stoptServer.log file)\n\nIn case the stopServer command hangs and does not create stopServer.log file, the following actions should be followed, so as to capture the thread dumps:\n1. Execute kill -3 on the processid of the server. \n2. Execute for four times at 1 minute intervals. \n(This will write a thread dump to the nativestderr.log, which may help IBM Support to determine what the threads might be hanging.) \n4. When observe problem [http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_runct.html]recurrence, run the WAS Collector tool [http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_runct.html] on WPG DMGR machine:\n<bcghub-dmgr>/wasND/Profiles/bcgdmgr/bin/<collector script>\n\n\n * \n\n\n\n5. Follow the instruction to send the collected data to IBM Support [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852]. \n\n\n\n\n[/support/docview.wss?uid=swg21452561&amp;aid=2] Back to Top \n\n\nWPG NODEAGENT\n \n\nIn a distributed topology, if nodeagent process is not able to start or stop, please take the below steps to collect required data.\n\n1. Backup and purge the logs under the following locations: \n\n * <bcghub>/wasND/Profiles/bcgprofile/logs/nodeagent\n * \n * <bcghub>/wasND/Profiles/bcgprofile/logs/ffdc\n\n\n\n2. Modify the file server.xml under the following location: * <bcghub>/wasND/Profiles/bcgprofile/config/cells/\n wpgCell/nodes/node_name/servers/nodeagent\n * \n * 1). Change the trace statement * \n * \n * \n * *=info\n * \n * \n * \n * \n * \n * *=info\n * :com.ibm.ws.*=all\n * \n \n \n 2). Change the following string: * \n * \n * \n * 1\n * \n * \n * \n * \n * \n * 10\n * \n \n \n 3). Save the changes. \n * \n\n\n3. Log in as WPG admin user (by default, it is 'bcguser'), go to the directory <bcghub>/wasND/Profiles/bcgprofile/bin, then run \"startNode -trace\" command. \n(This will log trace to the startServer.log file) [/support/docview.wss?uid=swg21452561&amp;aid=3] NOTE: Similarly, if the nodeagent process does not stop when issuing the command: stopNode. Follow the same procedure documented above for collecting trace documents, running the command stopNode in place of startNode. (This will log trace to the stoptServer.log file)\n\nIn case the stopNode command hangs and does not create stopServer.log file, the following actions should be followed, so as to capture the thread dumps:\n1. Execute kill -3 on the processid of the server. \n2. Execute for four times at 1 minute intervals. \n(This will write a thread dump to the nativestderr.log, which may help IBM Support to determine what the threads might be hanging.) \n4. When observe problem [http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_runct.html]recurrence, run the WAS Collector tool [http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_runct.html] on WPG HUB machine:\n<bcghub>/wasND/Profiles/bcgprofile/bin/<collector script>\n\n\n * \n\n\n\n5. Follow the instruction to send the collected data to IBM Support [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852]. \n\n\n\n\n[/support/docview.wss?uid=swg21452561&amp;aid=4] Back to Top \n\n\n\nRelated information \n\n * MustGather: Read first for WebSphere Partner Gateway [http://www.ibm.com/support/docview.wss?rs=2310&uid=swg21281975] \n * MustGather: Application Server, dmgr, and nodeagent start and stop problems [http://www-01.ibm.com/support/docview.wss?rs=180&context=SSCMPDZ&q1=MustGatherDocument&uid=swg21201014] [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852] [http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.wpg.entadv.doc/Troubleshooting/overview.html] \n * Troubleshooting Guide [http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.wpg.entadv.doc/Troubleshooting/overview.html] \n * Indexed collection of WPG Technotes [http://www-01.ibm.com/support/docview.wss?uid=swg27016406] \n * Searching solutions by using IBM Knowledge bases [http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.wpg.entadv.doc/Troubleshooting/Searching_knowledgebases.html] \n \n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Partner Gateway Advanced Edition AIX, HP-UX, Linux, Solaris, Windows 6.2.1, 6.2, 6.1.1.1, 6.1 Advanced \nPRODUCT ALIAS/SYNONYM\n WPG\nWebSphere Partner Gateway", "MXServer; NodeAgent; \"MXServer and NodeAgent processes\"; start; stop; srm71relnotes SRM TSRM TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Creating JMS activation specifications for continuous inbound queues might not take effect. \n\nSYMPTOM\nThe reader of the Service Request Manager 7.1 information center (and Installation Guide (PDF)) is not told which specific processes to stop and restart when creating JMS activation specifications for continuous inbound queues.\n\n\nRESOLVING THE PROBLEM\n \n\nThe following information is updated for the Service Request Manager 7.1 information center (and Installation Guide (PDF)):\n\n\nThe information in the Service Request Manager 7.1 information center for \"Creating JMS activation specification for continuous inbound queue (CQIN)\" (under \"Advanced installation topics\", then \"Installing base services with middleware configuration\", then \"Manually configuring JMS queues\", then \"Creating JMS activation specification for continuous inbound queue (CQIN)\") (also see page 192 of the Installation Guide (PDF)), steps 7 and 8 are updated to correctly read:\n\n\n7. Stop the MXServer and Node Agent processes.\n\n(instead of \"Ensure to stop all IBM-related processes and daemons.\")\n\nSee the below topics for specific information to stop these services.\n\n\n8. Restart the MXServer and Node Agent processes for the update to take effect.\n\n(instead of \"You must now restart these processes for the update to take effect..\")\n\nFor information on how to start these services, see \"Starting middleware on Windows\" in the Service Request Manager 7.1 information center under \"Installing\", then \"Installing the product\", then \"Installing middleware\", then \"Starting middleware on Windows\" (Installation Guide (PDF) page 62) (or \"Starting middleware on AIX and Linux\" (Installation Guide (PDF) page 63)). \n\n\n-----------------------------------------------------------------------------------------------\n\n\nStopping middleware on Windows \n\nTo stop the Node Agent or MXServer process, complete the following steps, as needed:\n\n\n 1. Log in as a user with administrative permissions. \n 2. Stop the desired servers by executing the following scripts:\n\n\nStop Node \n\n<WAS_HOME>\\profiles\\ctgAppSvr01\\bin\\stopNode.bat \n\nAt the Login at Target Server screen in the User Identity and User Password fields, enter the user and password of the administrative user able to stop the Node Agent service (server). \n\nAfter positive validation of the credentials, the Node Agent service will be stopped. \n\n\nStop MXServer \n\n<WAS_HOME>\\profiles\\ctgAppSrv01\\bin\\stopServer.bat MXServer -username <username> -password <password> \n\nIf the username and password are not specified in the command line, for example: \n<WAS_HOME>\\profiles\\ctgAppSrv01\\bin\\stopServer.bat MXServer \nthen at the Login at Target Server screen in the User Identity and User Password fields, enter the user and password of the administrative user able to stop the MXServer service (server). \n\n\n\nStopping middleware on AIX and Linux \n\nTo stop the Node Agent or MXServer process, complete the following steps, as needed: \n 1. Log in as a user with administrative permissions. \n 2. Stop the desired servers by executing the following scripts:\n\n\nStop Node \n\n<WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.sh \n\n\nStop MXServer \n\n<WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh MXServer -username <username> -password <password> \n\n\n----------------------------------------------------------------------------------------------- \n\n\nAdditional information about starting and stopping services can be found on the WebSphere Information Center at: \nftp://public.dhe.ibm.com/software/webserver/appserv/library/v61/wasv610base_admin.pdf [ftp://public.dhe.ibm.com/software/webserver/appserv/library/v61/wasv610base_admin.pdf] . \n \n\nPRODUCT ALIAS/SYNONYM\n SRM TSRM", "bpm; monitor; licensing; IBM License Metric Too; ilmt TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If IBM Business Monitor, IBM Business Process Manager (BPM) Advanced, or IBM Business Process Manager (BPM) Standard is installed on a machine and only a Deployment Manager (DMGR) node is created, the IBM License Metric Tool (ILMT) will count the Monitor and BPM processor value units (PVU). The licensing inventory software has no way to distinguish between a Monitor/BPM DMGR installation and a Monitor/BPM node installation.\n\nThe ILMT count of these nodes is counter to the licensing of IBM Business Monitor, IBM Business Process Manager (BPM) Advanced, or IBM Business Process Manager (BPM) Standard. These program profiles can be used in an existing WAS DMGR, on a remote server, without counting toward entitlement. \n\nRESOLVING THE PROBLEM\nTo exclude items from their PVU calculations in the ILMT:\n\n\n1. Follow steps 1-3 in http://pic.dhe.ibm.com/infocenter/tivihelp/v53r1/index.jsp?topic=%2Fcom.ibm.lmt75.doc%2Fcom.ibm.license.mgmt.tutorials.doc%2Fl_excluding_instance.html [http://pic.dhe.ibm.com/infocenter/tivihelp/v53r1/index.jsp?topic=%2Fcom.ibm.lmt75.doc%2Fcom.ibm.license.mgmt.tutorials.doc%2Fl_excluding_instance.html]\n\n2. In step 4 \"Select a reason for the exclusion from the drop-down list\", select \"Other\" and use the following statement in the field:\n\nLicensing term related to DMGR:\n\nComponents not used for Establishing Required Entitlements\n\nWhen determining the number of entitlements required for Licensee's installation or use of the Program, the installation or use of the following Program components are not taken into consideration. In other words, Licensee may install and use the following Program components, under the license terms, but these components are not used to determine the number of entitlements required for the Program.\n\nAll components of the Program when used only for augmenting an existing, compatible Deployment Manager (\"DMGR\") profile and supporting the remote administration and network deployment of the Program. \n\n3. Click Exclude.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced General AIX, Linux, Linux zSeries, Solaris, Windows, z/OS 8.5.5, 8.5.0.1, 8.5, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1 Business Integration IBM Business Process Manager Standard General AIX, Linux, Linux zSeries, Solaris, Windows 8.5.5, 8.5.0.1, 8.5, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1 Business Integration WebSphere Enterprise Service Bus General AIX, HP-UX, i5/OS, Linux, Linux iSeries, Linux pSeries, Linux xSeries, Linux zSeries, Solaris, Windows, z/OS 7.5.1.2, 7.5.1.1, 7.5.1 \nPRODUCT ALIAS/SYNONYM\n BPM\nMonitor\nWESB" ]

[ [ "0a", "wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server." ], [ "0c", "WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows." ], [ "0d", "Notice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory. Reference:" ], [ "0e", "Using the WASServiceHelper utility to create Windows services for application servers https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html]" ], [ "0f", "See DeveloperWorks article for detailed information: (Link at the bottom of this document) SYMPTOM" ], [ "0g", "Creating and removing a WebSphere service in Windows is confusing and error prone. CAUSE" ], [ "0h", "This application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly. ENVIRONMENT Windows" ], [ "0i", "RESOLVING THE PROBLEM 1." ], [ "0j", "Place the WASServiceCmd.exe utility in the following directory:" ], [ "0k", " install_root\\bin 2." ], [ "0l", "Launch the command from the command line. 3." ], [ "0m", "The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters." ], [ "0n", "This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors." ], [ "0o", "[/support/docview.wss?uid=swg21397335&amp;aid=1] Flash demonstration [http://public.dhe.ibm.com/software/websphere/appserv/support/tutorials/wasservicecmd.swf]" ], [ "0p", "Note: This also creates an entry in the WASServiceCmd.log in the current directory which contains the actual WASService.exe command used to create the service." ], [ "0q", "Example of a log entry:" ], [ "0r", "[Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add \"Deployment Mgr01\" -serverName \"dmgr\"" ], [ "0s", "-profilePath \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\"" ], [ "0t", "-logRoot \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\"" ], [ "0u", "-logFile \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\\WS_startdmgr.log\" -encodeParams -stopArgs \"-username vanno -password ****** \" -startType manual" ], [ "0v", "-restart false WASServicecmd.zip [/support/docview.wss?uid=swg21397335&aid=3] [/support/docview.wss?uid=swg21397335&aid=2]" ], [ "0w", "Notice: Some browsers are having trouble downloading this file and getting docview.wss instead." ], [ "0x", "Download this file, then rename the file with a \".zip\" extension (for example, docview.zip or WASServiceCmd.zip)." ], [ "0y", "You can now access the utility." ], [ "0z", "See DeveloperWorks article for more information:" ], [ "0aa", "The Support Authority: Take the confusion (and errors) out of creating Windows services for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/techjournal/1005_supauth/1005_supauth.html]" ], [ "0ab", "See TroubleShooting: WebSphere Application Server (Windows Services) problems for V6.0, V6.1 and V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21232884] if you are still having a problem with Windows services." ] ]

[ "0b", "0c", "0d", "0e", "0j", "0k", "0l", "0m", "0n", "0p", "0s", "0t", "0u" ]

[ " FIXES ARE AVAILABLE\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When a Java program creates an embedded Liberty server it can\n specify the location for Liberty output files using the\n setUserDir() and setOutputDir() API calls on the ServerBuilder\n object. For example:\n .\n ServerBuilder builder = new ServerBuilder();\n builder.setUserDir(userDir);\n builder.setOutputDir(outputDir);\n .\n While most output files are written to the locations specified\n using the API, a single .cache file is incorrectly written\n under the Liberty server directory tree.\n \n \n \n \n \n\nLOCAL FIX\n * A workaround would be to set the WLP_OUTPUT_DIR and WLP_USER_DIR\n variables as system environment variables before starting the\n Liberty server; that is before the application that starts the\n server is run.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Liberty Profile using embedded *\n * Liberty servers *\n ****************************************************************\n * PROBLEM DESCRIPTION: A file named \".cache\" is written to the *\n * Liberty installation directory tree *\n * rather than the user-specified output *\n * directory. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The problem only occurs when the Liberty server is created\n programmatically. If the Liberty server is started directly\n from a command line the problem does not occur.\n Java example of starting an embedded server:\n ServerBuilder builder = new ServerBuilder();\n builder.setUserDir(userDir);\n builder.setOutputDir(outputDir);\n Server server = builder.build();\n server.start(new String[0]).get();\n The values set by the APIs \"setUserDir\" and \"setOutputDir\" are\n not being respected. The code that writes the \".cache\" file is\n checking environment variables WLP_OUTPUT_DIR and WLP_USER_DIR,\n which are not set when the Liberty server is started\n programmatically. Since the variables are not set, the \".cache\"\n file is written to the default location, which is\n \"wlp/usr/servers/<SERVER NAME>/workarea/platform/bundle/.cache\"\n When starting the server from the command line, the environment\n variables can be specified in the server.env file. However,\n specifying these variables in server.env has no effect on a\n server that is created programmatically.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The code that writes the \".cache\" file has been modified. If\n the WLP_OUTPUT_DIR and WLP_USER_DIR environment variables are\n not set, the code will use values specified using the APIs:\n \n \n serverBuilder.setUserDir()\n \n serverBuilder.setOutputDir(outputDir)\n \n This means you may set\n the system environment variables to override the settings\n created by the API calls.\n \n The fix for this APAR is currently\n targeted for inclusion in fix pack 8.5.5.5. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI20344\n \n \n * REPORTED COMPONENT NAME\n WAS LIBERTY COR\n \n \n * REPORTED COMPONENT ID\n 5725L2900\n \n \n * REPORTED RELEASE\n 855\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2014-06-18\n \n \n * CLOSED DATE\n 2014-10-15\n \n \n * LAST MODIFIED DATE\n 2014-10-15\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WAS LIBERTY COR\n \n \n * FIXED COMPONENT ID\n 5725L2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R855 PSY\n UP", "xulrunner; mozilla_five_home TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to launch the IBM Security AppScan Source for Analysis or AppScan Source for Development (Eclipse plug-in) user interface result in an empty white box or not showing anything. \n\nSYMPTOM\nAfter entering login credentials, you may see a blank white box appear or you may not see anything happen. In either case, the UI does not launch as expected.\n\n\nCAUSE\nThe underlying Eclipse version that AppScan Source is built on or installed to is incompatible with XULRunner version 1.9.2.26-2 or later.\n\nENVIRONMENT\nThis problem is typically seen on RHEL 5.8 and RHEL 6.3, but it can occur on any version of RHEL with a newer version of XULRunner.\n\nRESOLVING THE PROBLEM\nResolution for AppScan Source for Analysis version 8.6.x or earlier, and for AppScan Source for Development installed to Eclipse version 3.6 or earlier:\n\n\n * \n * \n * https://developer.mozilla.org/en-US/docs/XULRunner_1.8.0.4_Release_Notes\n * \n * \n * Set MOZILLA_FIVE_HOME to the XULRunner installation location. Update LD_LIBRARY_PATH to append (or pre-pend) $MOZILLA_FIVE_HOME. \n * \n * \n\n\nResolution for AppScan Source for Analysis Version 8.7.x, and for AppScan Source for Development installed to Eclipse Version 3.7 or later: \n * \n * yum install webkitgtk.i686\n * \n * \n * \n * \n * \n * Set MOZILLA_FIVE_HOME to the XULRunner installation location. Update LD_LIBRARY_PATH to append (or pre-pend) $MOZILLA_FIVE_HOME. \n\nResolution for Eclipse 32-bit using a 32-bit JDK on RHEL 5.8 crashing when launched from the UI menu. \n * \n *", "WASPatternsV1RNotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The IBM Installation Manager repository does not contain the required offerings to run your WebSphere Application Server Patterns configuration. \n\nRESOLVING THE PROBLEM\nYou must download the required offerings for WebSphere Application Server Patterns from Fix Central to the IBM Installation Manager repository. \n\nIBM WebSphere Application Server Patterns supports IBM WebSphere Application Server Version 8.0.0.9 and 8.5.5.2. \n\nThe following tables contain the supported WebSphere Application Server offerings and additional features that the software components can install. \n\n \n\n * WebSphere Application Server 8.5.5.x software components and fix pack offerings\n * \n * WebSphere Application Server 8.5.5.x additional features\n * \n * WebSphere Application Server 8.0.0.x software components and fix pack offerings\n * \n * WebSphere Application Server 8.0.0.x additional features\n\n\nWebSphere Application Server 8.5.5.x software components and fix pack offerings \n\nThe Software component column indicates what package should be downloaded from the IBM Fix Central download site. To determine the offerings that you need to download based on the fix pack you require, see Recommended fixes for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27004980]. \n\n \n\nSoftware component Fix pack offering Deployment manager WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Custom nodes WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Job manager WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Administrative agents WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile IBM HTTP Servers Supplements V8.5.5.x local repository compressed files containing Application Client, Web server plug-ins, Pluggable Application Client, IBM HTTP Server, Java SDK On demand routers WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Stand-alone server WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Liberty controller WebSphere Application Server V8.5.5.x Liberty Profile Runtime for Network Deployment Liberty host WebSphere Application Server V8.5.5.x Liberty Profile Runtime for Network Deployment Liberty profile server WebSphere Application Server V8.5.5.x Liberty Profile Runtime for Network Deployment \nWebSphere Application Server 8.5.5.x additional features \nThe following software components can install additional functionality. If these features are needed, additional offerings must be added to the Installation Manager repository. \nAlso see: * Recommended fixes for WebSphere eXtreme Scale [http://www-01.ibm.com/support/docview.wss?uid=swg27018991] \n * Feature packs by version for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg27008534#was80]\n\nAdditional features Fix pack offering IBM WebSphere eXtreme Scale Client WebSphere eXtreme Scale Client for WebSphere Application Server Version 8.0 Java SDK v6 IBM WebSphere SDK Java Technology Edition (Default) V6.0.x.0 for Liberty Profile Java SDK v7.0 IBM WebSphere SDK Java Technology Edition (Optional) V7.0.x.0 for Full Profile and Liberty Profile Java SDK v7.1 IBM WebSphere SDK Java Technology Edition (Optional) V7.1.x.0 for Full Profile and Liberty Profile Web 2.0 and Mobile Toolkit v1.1 IBM Websphere Application Server Web 2.0 and Mobile Toolkit V1.1.0.x WebSphere Customization Toolbox WebSphere Customization Toolbox V8.5.5.3 local repository compressed files \nWebSphere Application Server 8.0.0.x software components and fix pack offerings The Software component column indicates what package should be downloaded from the IBM Fix Central download site. To determine the offerings that you need to download based on the fix pack you require, see Recommended fixes for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27004980].\n\n\n\nSoftware component Fix pack offering Deployment manager WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Application Server V8.0.0.9 local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Custom nodes WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Application Server V8.0.0.9 local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Job manager WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Administrative agents WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK IBM HTTP Servers Supplements V8.0.0.x local repository compressed files containing Application Client, Web server plug-ins, Pluggable Application Client, IBM HTTP Server, Java SDK On demand routers WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Stand-alone server WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK \nWebSphere Application Server 8.0.0.x additional features \nThe following software components can install additional functionality. If these features are needed, additional offerings must be added to the Installation Manager repository. \nAlso see: * Recommended fixes for WebSphere eXtreme Scale [http://www-01.ibm.com/support/docview.wss?uid=swg27018991] \n * Feature packs by version for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg27008534#was80]\n\nAdditional features Fix pack offering IBM WebSphere eXtreme Scale Client WebSphere eXtreme Scale Client for WebSphere Application Server Version 8.0 Web 2.0 and Mobile Feature pack WebSphere Application Server Version 6.1, 7.0, and 8.0 Feature Pack for Web 2.0 and Mobile WebSphere Customization Toolbox WebSphere Customization Toolbox V8.0.0.x local repository ZIP File", "JVMTI; profiling; Liberty TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Java JVMTI profiling analysis types are not showing up in the Profiling on Server dialog when profiling on WebSphere Application Server Liberty Profile if none of the WebSphere Application Server 7.0/8.0/8.5 Development tools install option is selected during Rational Application Developer v9.5 installation. \n\nSYMPTOM\nWhen profiling on WebSphere Application Server Liberty Profile, only Health Center Data Collector is showing up as option in the Profile on Server dialog. That is, none of the JVMTI Java Profiling options such as Execution Time Analysis, Memory Analysis, Thread Analysis is showing up as available profiling analysis type to be selected.\n\n\n [/support/docview.wss?uid=swg21967031&aid=1] [/support/docview.wss?uid=swg21967031&aid=1]\n\n\nThis problem only occurs when none of the WebSphere Application Server 7.0/8.0/8.5 Development tools install option are selected, but WebSphere Application Server v8.5 Liberty Profile Tools option is selected during Rational Application Developer v9.5 installation. \n\n\nCAUSE\nThe plugins providing the profile on server function is not installed when none of the WebSphere Application Server 7.0/8.0/8.5 Development tools install option are selected, but the WebSphere Application Server v8.5 Liberty Profile Tools option is selected. \n\n[/support/docview.wss?uid=swg21967031&amp;aid=2]\n\n\n\nRESOLVING THE PROBLEM\nIf you select the WebSphere Application Server v8.5 Liberty Profile Tools option during your product installation and you plan to profile on WAS Liberty Profile, you can resolve the problem by selecting one of the WebSphere Application Server 7.0/8.0/8.5 – Development tools install option during the Rational Application Developer installation process.", " PRODUCT DOCUMENTATION\n\nABSTRACT\n A list of the latest available IBM SDKs, Java Technology Edition for WebSphere Liberty using archives and Installation Manager. \n\n\nCONTENT\nAnnouncement: \n\n\nJava SE 7 support ends in September 2019. See removal notice [http://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/rwlp_remfeat.html].\n\nUse SDKs for specific installation method.\n\nArchive Install \n\n * IBM SDK, Java™ Technology Edition, Version 8.0 for WebSphere Liberty using archive [http://www.ibm.com/support/docview.wss?uid=swg24043502][/support/docview.wss?uid=swg27049903&amp;aid=1] \n\nInstallation Manager Install * IBM SDK, Java™ Technology Edition, Version 8.0 for WebSphere Liberty using IM[/support/docview.wss?uid=swg27049903&aid=2] [http://www.ibm.com/support/docview.wss?uid=swg24042430] IBM SDK, Java™ Technology Edition, Version 7.1 for WebSphere Liberty using IM [http://www.ibm.com/support/docview.wss?uid=swg24042440][/support/docview.wss?uid=swg27049903&amp;aid=3] \n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ]

[ [ "0a", " FIXES ARE AVAILABLE" ], [ "0b", "8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]" ], [ "0c", "8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]" ], [ "0d", "8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]" ], [ "0e", "8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]" ], [ "0f", "8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]" ], [ "0g", "8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]" ], [ "0h", "8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]" ], [ "0i", "8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]" ], [ "0j", "8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479] SUBSCRIBE" ], [ "0k", "You can track all active APARs for this component. APAR STATUS" ], [ "0l", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "0m", " * When a Java program creates an embedded Liberty server it can" ], [ "0n", " specify the location for Liberty output files using the" ], [ "0o", " setUserDir() and setOutputDir() API calls on the ServerBuilder" ], [ "0p", " object. For example:" ], [ "0q", " ." ], [ "0r", " ServerBuilder builder = new ServerBuilder();" ], [ "0s", " builder.setUserDir(userDir);" ], [ "0t", " builder.setOutputDir(outputDir);" ], [ "0u", " ." ], [ "0v", " While most output files are written to the locations specified" ], [ "0w", " using the API, a single .cache file is incorrectly written" ], [ "0x", " under the Liberty server directory tree. LOCAL FIX" ], [ "0y", " * A workaround would be to set the WLP_OUTPUT_DIR and WLP_USER_DIR" ], [ "0z", " variables as system environment variables before starting the" ], [ "0aa", " Liberty server; that is before the application that starts the" ], [ "0ab", " server is run. PROBLEM SUMMARY" ], [ "0ac", " * ****************************************************************" ], [ "0ad", " * USERS AFFECTED: All users of IBM WebSphere Application *" ], [ "0ae", " * Server Liberty Profile using embedded *" ], [ "0af", " * Liberty servers *" ], [ "0ag", " ****************************************************************" ], [ "0ah", " * PROBLEM DESCRIPTION: A file named \".cache\" is written to the *" ], [ "0ai", " * Liberty installation directory tree *" ], [ "0aj", " * rather than the user-specified output *" ], [ "0ak", " * directory. *" ], [ "0al", " ****************************************************************" ], [ "0am", " * RECOMMENDATION: *" ], [ "0an", " ****************************************************************" ], [ "0ao", " The problem only occurs when the Liberty server is created" ], [ "0ap", " programmatically." ], [ "0aq", "If the Liberty server is started directly" ], [ "0ar", " from a command line the problem does not occur." ], [ "0as", " Java example of starting an embedded server:" ], [ "0at", " ServerBuilder builder = new ServerBuilder();" ], [ "0au", " builder.setUserDir(userDir);" ], [ "0av", " builder.setOutputDir(outputDir);" ], [ "0aw", " Server server = builder.build();" ], [ "0ax", " server.start(new String[0]).get();" ], [ "0ay", " The values set by the APIs \"setUserDir\" and \"setOutputDir\" are" ], [ "0az", " not being respected." ], [ "0ba", "The code that writes the \".cache\" file is" ], [ "0bb", " checking environment variables WLP_OUTPUT_DIR and WLP_USER_DIR," ], [ "0bc", " which are not set when the Liberty server is started" ], [ "0bd", " programmatically." ], [ "0be", "Since the variables are not set, the \".cache\"" ], [ "0bf", " file is written to the default location, which is" ], [ "0bg", " \"wlp/usr/servers/<SERVER NAME>/workarea/platform/bundle/.cache\"" ], [ "0bh", " When starting the server from the command line, the environment" ], [ "0bi", " variables can be specified in the server.env file. However," ], [ "0bj", " specifying these variables in server.env has no effect on a" ], [ "0bk", " server that is created programmatically. PROBLEM CONCLUSION" ], [ "0bl", " * The code that writes the \".cache\" file has been modified. If" ], [ "0bm", " the WLP_OUTPUT_DIR and WLP_USER_DIR environment variables are" ], [ "0bn", " not set, the code will use values specified using the APIs:" ], [ "0bo", " serverBuilder.setUserDir()" ], [ "0bp", " serverBuilder.setOutputDir(outputDir)" ], [ "0bq", " This means you may set" ], [ "0br", " the system environment variables to override the settings" ], [ "0bs", " created by the API calls." ], [ "0bt", " The fix for this APAR is currently" ], [ "0bu", " targeted for inclusion in fix pack 8.5.5.5." ], [ "0bv", "Please refer to the" ], [ "0bw", " Recommended Updates page for delivery information:" ], [ "0bx", " http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980] TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "0by", " * APAR NUMBER" ], [ "0bz", " PI20344" ], [ "0ca", " * REPORTED COMPONENT NAME" ], [ "0cb", " WAS LIBERTY COR" ], [ "0cc", " * REPORTED COMPONENT ID" ], [ "0cd", " 5725L2900" ], [ "0ce", " * REPORTED RELEASE" ], [ "0cf", " 855" ], [ "0cg", " * STATUS" ], [ "0ch", " CLOSED PER" ], [ "0ci", " * PE" ], [ "0cj", " NoPE" ], [ "0ck", " * HIPER" ], [ "0cl", " NoHIPER" ], [ "0cm", " * SPECIAL ATTENTION" ], [ "0cn", " NoSpecatt / Xsystem" ], [ "0co", " * SUBMITTED DATE" ], [ "0cp", " 2014-06-18" ], [ "0cq", " * CLOSED DATE" ], [ "0cr", " 2014-10-15" ], [ "0cs", " * LAST MODIFIED DATE" ], [ "0ct", " 2014-10-15" ], [ "0cu", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "0cv", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING: FIX INFORMATION" ], [ "0cw", " * FIXED COMPONENT NAME" ], [ "0cx", " WAS LIBERTY COR" ], [ "0cy", " * FIXED COMPONENT ID" ], [ "0cz", " 5725L2900" ], [ "0da", "APPLICABLE COMPONENT LEVELS" ], [ "0db", " * R855 PSY" ], [ "0dc", " UP" ] ]

[ "0f", "4f", "4g" ]

[ " FIXES ARE AVAILABLE\n8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24039425]\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When a Java program creates an embedded Liberty server it can\n specify the location for Liberty output files using the\n setUserDir() and setOutputDir() API calls on the ServerBuilder\n object. For example:\n .\n ServerBuilder builder = new ServerBuilder();\n builder.setUserDir(userDir);\n builder.setOutputDir(outputDir);\n .\n While most output files are written to the locations specified\n using the API, a single .cache file is incorrectly written\n under the Liberty server directory tree.\n \n \n \n \n \n\nLOCAL FIX\n * A workaround would be to set the WLP_OUTPUT_DIR and WLP_USER_DIR\n variables as system environment variables before starting the\n Liberty server; that is before the application that starts the\n server is run.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Liberty Profile using embedded *\n * Liberty servers *\n ****************************************************************\n * PROBLEM DESCRIPTION: A file named \".cache\" is written to the *\n * Liberty installation directory tree *\n * rather than the user-specified output *\n * directory. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The problem only occurs when the Liberty server is created\n programmatically. If the Liberty server is started directly\n from a command line the problem does not occur.\n Java example of starting an embedded server:\n ServerBuilder builder = new ServerBuilder();\n builder.setUserDir(userDir);\n builder.setOutputDir(outputDir);\n Server server = builder.build();\n server.start(new String[0]).get();\n The values set by the APIs \"setUserDir\" and \"setOutputDir\" are\n not being respected. The code that writes the \".cache\" file is\n checking environment variables WLP_OUTPUT_DIR and WLP_USER_DIR,\n which are not set when the Liberty server is started\n programmatically. Since the variables are not set, the \".cache\"\n file is written to the default location, which is\n \"wlp/usr/servers/<SERVER NAME>/workarea/platform/bundle/.cache\"\n When starting the server from the command line, the environment\n variables can be specified in the server.env file. However,\n specifying these variables in server.env has no effect on a\n server that is created programmatically.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The code that writes the \".cache\" file has been modified. If\n the WLP_OUTPUT_DIR and WLP_USER_DIR environment variables are\n not set, the code will use values specified using the APIs:\n \n \n serverBuilder.setUserDir()\n \n serverBuilder.setOutputDir(outputDir)\n \n This means you may set\n the system environment variables to override the settings\n created by the API calls.\n \n The fix for this APAR is currently\n targeted for inclusion in fix pack 8.5.5.5. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI20344\n \n \n * REPORTED COMPONENT NAME\n WAS LIBERTY COR\n \n \n * REPORTED COMPONENT ID\n 5725L2900\n \n \n * REPORTED RELEASE\n 855\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2014-06-18\n \n \n * CLOSED DATE\n 2014-10-15\n \n \n * LAST MODIFIED DATE\n 2014-10-15\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WAS LIBERTY COR\n \n \n * FIXED COMPONENT ID\n 5725L2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R855 PSY\n UP", "xulrunner; mozilla_five_home TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to launch the IBM Security AppScan Source for Analysis or AppScan Source for Development (Eclipse plug-in) user interface result in an empty white box or not showing anything. \n\nSYMPTOM\nAfter entering login credentials, you may see a blank white box appear or you may not see anything happen. In either case, the UI does not launch as expected.\n\n\nCAUSE\nThe underlying Eclipse version that AppScan Source is built on or installed to is incompatible with XULRunner version 1.9.2.26-2 or later.\n\nENVIRONMENT\nThis problem is typically seen on RHEL 5.8 and RHEL 6.3, but it can occur on any version of RHEL with a newer version of XULRunner.\n\nRESOLVING THE PROBLEM\nResolution for AppScan Source for Analysis version 8.6.x or earlier, and for AppScan Source for Development installed to Eclipse version 3.6 or earlier:\n\n\n * \n * \n * https://developer.mozilla.org/en-US/docs/XULRunner_1.8.0.4_Release_Notes\n * \n * \n * Set MOZILLA_FIVE_HOME to the XULRunner installation location. Update LD_LIBRARY_PATH to append (or pre-pend) $MOZILLA_FIVE_HOME. \n * \n * \n\n\nResolution for AppScan Source for Analysis Version 8.7.x, and for AppScan Source for Development installed to Eclipse Version 3.7 or later: \n * \n * yum install webkitgtk.i686\n * \n * \n * \n * \n * \n * Set MOZILLA_FIVE_HOME to the XULRunner installation location. Update LD_LIBRARY_PATH to append (or pre-pend) $MOZILLA_FIVE_HOME. \n\nResolution for Eclipse 32-bit using a 32-bit JDK on RHEL 5.8 crashing when launched from the UI menu. \n * \n *", "WASPatternsV1RNotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The IBM Installation Manager repository does not contain the required offerings to run your WebSphere Application Server Patterns configuration. \n\nRESOLVING THE PROBLEM\nYou must download the required offerings for WebSphere Application Server Patterns from Fix Central to the IBM Installation Manager repository. \n\nIBM WebSphere Application Server Patterns supports IBM WebSphere Application Server Version 8.0.0.9 and 8.5.5.2. \n\nThe following tables contain the supported WebSphere Application Server offerings and additional features that the software components can install. \n\n \n\n * WebSphere Application Server 8.5.5.x software components and fix pack offerings\n * \n * WebSphere Application Server 8.5.5.x additional features\n * \n * WebSphere Application Server 8.0.0.x software components and fix pack offerings\n * \n * WebSphere Application Server 8.0.0.x additional features\n\n\nWebSphere Application Server 8.5.5.x software components and fix pack offerings \n\nThe Software component column indicates what package should be downloaded from the IBM Fix Central download site. To determine the offerings that you need to download based on the fix pack you require, see Recommended fixes for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27004980]. \n\n \n\nSoftware component Fix pack offering Deployment manager WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Custom nodes WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Job manager WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Administrative agents WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile IBM HTTP Servers Supplements V8.5.5.x local repository compressed files containing Application Client, Web server plug-ins, Pluggable Application Client, IBM HTTP Server, Java SDK On demand routers WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Stand-alone server WebSphere Application Server V8.5.5.x local repository compressed files containing Base, Developers, ND, NDDMZ, Java SDK for Full Profile Liberty controller WebSphere Application Server V8.5.5.x Liberty Profile Runtime for Network Deployment Liberty host WebSphere Application Server V8.5.5.x Liberty Profile Runtime for Network Deployment Liberty profile server WebSphere Application Server V8.5.5.x Liberty Profile Runtime for Network Deployment \nWebSphere Application Server 8.5.5.x additional features \nThe following software components can install additional functionality. If these features are needed, additional offerings must be added to the Installation Manager repository. \nAlso see: * Recommended fixes for WebSphere eXtreme Scale [http://www-01.ibm.com/support/docview.wss?uid=swg27018991] \n * Feature packs by version for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg27008534#was80]\n\nAdditional features Fix pack offering IBM WebSphere eXtreme Scale Client WebSphere eXtreme Scale Client for WebSphere Application Server Version 8.0 Java SDK v6 IBM WebSphere SDK Java Technology Edition (Default) V6.0.x.0 for Liberty Profile Java SDK v7.0 IBM WebSphere SDK Java Technology Edition (Optional) V7.0.x.0 for Full Profile and Liberty Profile Java SDK v7.1 IBM WebSphere SDK Java Technology Edition (Optional) V7.1.x.0 for Full Profile and Liberty Profile Web 2.0 and Mobile Toolkit v1.1 IBM Websphere Application Server Web 2.0 and Mobile Toolkit V1.1.0.x WebSphere Customization Toolbox WebSphere Customization Toolbox V8.5.5.3 local repository compressed files \nWebSphere Application Server 8.0.0.x software components and fix pack offerings The Software component column indicates what package should be downloaded from the IBM Fix Central download site. To determine the offerings that you need to download based on the fix pack you require, see Recommended fixes for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27004980].\n\n\n\nSoftware component Fix pack offering Deployment manager WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Application Server V8.0.0.9 local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Custom nodes WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Application Server V8.0.0.9 local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Job manager WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Administrative agents WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK IBM HTTP Servers Supplements V8.0.0.x local repository compressed files containing Application Client, Web server plug-ins, Pluggable Application Client, IBM HTTP Server, Java SDK On demand routers WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK Stand-alone server WebSphere Application Server V8.0.0.x local repository compressed files containing Base, Express, Developers, ND, NDDMZ, Java SDK \nWebSphere Application Server 8.0.0.x additional features \nThe following software components can install additional functionality. If these features are needed, additional offerings must be added to the Installation Manager repository. \nAlso see: * Recommended fixes for WebSphere eXtreme Scale [http://www-01.ibm.com/support/docview.wss?uid=swg27018991] \n * Feature packs by version for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg27008534#was80]\n\nAdditional features Fix pack offering IBM WebSphere eXtreme Scale Client WebSphere eXtreme Scale Client for WebSphere Application Server Version 8.0 Web 2.0 and Mobile Feature pack WebSphere Application Server Version 6.1, 7.0, and 8.0 Feature Pack for Web 2.0 and Mobile WebSphere Customization Toolbox WebSphere Customization Toolbox V8.0.0.x local repository ZIP File", "JVMTI; profiling; Liberty TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Java JVMTI profiling analysis types are not showing up in the Profiling on Server dialog when profiling on WebSphere Application Server Liberty Profile if none of the WebSphere Application Server 7.0/8.0/8.5 Development tools install option is selected during Rational Application Developer v9.5 installation. \n\nSYMPTOM\nWhen profiling on WebSphere Application Server Liberty Profile, only Health Center Data Collector is showing up as option in the Profile on Server dialog. That is, none of the JVMTI Java Profiling options such as Execution Time Analysis, Memory Analysis, Thread Analysis is showing up as available profiling analysis type to be selected.\n\n\n [/support/docview.wss?uid=swg21967031&aid=1] [/support/docview.wss?uid=swg21967031&aid=1]\n\n\nThis problem only occurs when none of the WebSphere Application Server 7.0/8.0/8.5 Development tools install option are selected, but WebSphere Application Server v8.5 Liberty Profile Tools option is selected during Rational Application Developer v9.5 installation. \n\n\nCAUSE\nThe plugins providing the profile on server function is not installed when none of the WebSphere Application Server 7.0/8.0/8.5 Development tools install option are selected, but the WebSphere Application Server v8.5 Liberty Profile Tools option is selected. \n\n[/support/docview.wss?uid=swg21967031&amp;aid=2]\n\n\n\nRESOLVING THE PROBLEM\nIf you select the WebSphere Application Server v8.5 Liberty Profile Tools option during your product installation and you plan to profile on WAS Liberty Profile, you can resolve the problem by selecting one of the WebSphere Application Server 7.0/8.0/8.5 – Development tools install option during the Rational Application Developer installation process.", " PRODUCT DOCUMENTATION\n\nABSTRACT\n A list of the latest available IBM SDKs, Java Technology Edition for WebSphere Liberty using archives and Installation Manager. \n\n\nCONTENT\nAnnouncement: \n\n\nJava SE 7 support ends in September 2019. See removal notice [http://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/rwlp_remfeat.html].\n\nUse SDKs for specific installation method.\n\nArchive Install \n\n * IBM SDK, Java™ Technology Edition, Version 8.0 for WebSphere Liberty using archive [http://www.ibm.com/support/docview.wss?uid=swg24043502][/support/docview.wss?uid=swg27049903&amp;aid=1] \n\nInstallation Manager Install * IBM SDK, Java™ Technology Edition, Version 8.0 for WebSphere Liberty using IM[/support/docview.wss?uid=swg27049903&aid=2] [http://www.ibm.com/support/docview.wss?uid=swg24042430] IBM SDK, Java™ Technology Edition, Version 7.1 for WebSphere Liberty using IM [http://www.ibm.com/support/docview.wss?uid=swg24042440][/support/docview.wss?uid=swg27049903&amp;aid=3] \n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ]

[ [ "4a", " PRODUCT DOCUMENTATION ABSTRACT" ], [ "4b", " A list of the latest available IBM SDKs, Java Technology Edition for WebSphere Liberty using archives and Installation Manager. CONTENT Announcement:" ], [ "4c", "Java SE 7 support ends in September 2019." ], [ "4d", "See removal notice [http://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/rwlp_remfeat.html]." ], [ "4e", "Use SDKs for specific installation method. Archive Install" ], [ "4f", " * IBM SDK, Java™ Technology Edition, Version 8.0 for WebSphere Liberty using archive [http://www.ibm.com/support/docview.wss?uid=swg24043502][/support/docview.wss?uid=swg27049903&amp;aid=1]" ], [ "4g", "Installation Manager Install * IBM SDK, Java™ Technology Edition, Version 8.0 for WebSphere Liberty using IM[/support/docview.wss?uid=swg27049903&aid=2] [http://www.ibm.com/support/docview.wss?uid=swg24042430] IBM SDK, Java™ Technology Edition, Version 7.1 for WebSphere Liberty using IM [http://www.ibm.com/support/docview.wss?uid=swg24042440][/support/docview.wss?uid=swg27049903&amp;aid=3]" ], [ "4h", "Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ] ]

[ "0f", "4f", "4g" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n MustGather notes for SCO / ICO to OpenStack engagement \n\nRESOLVING THE PROBLEM\n \n\nMustGather Recommendations for SCO / ICO to OpenStack Engagement \n\n========================================================================\nInformation/Logs needed by OpenStack\n\nI. Top Level Info\n\n- What exact version/SP of SCO / ICO (i.e. 2.4.0.1), and what LA level?\n\n- If SCO 2.3.x, what version of SCE is in use?\n- Hypervisor type and version (i.e. VMWare vCenter 5.5) ?\n\nII. MustGather Data (logs and configuration files)\n\nNote: If you have been asked to enable debug and recreate the \nproblem, please skip to section III and return here to gather \nand send all the data.\n\nPlease use the QMGCOLLECT.sh script to gather the required data.\n\nThis picture shows option 1 selected which is [/support/docview.wss?uid=nas8N1020620&amp;aid=1]\n\nThe QMGCOLLECT.sh script is provided with instructions here:\n\nhttp://www-01.ibm.com/support/docview.wss?uid=nas8N1020618 [http://www-01.ibm.com/support/docview.wss?uid=nas8N1020618]\n\n\nIII. Recreation and Logs\n\n1. OpenStack Config files. Edit these to enable extra logging.\n\n/etc/nova/nova.conf\n/etc/nova/smartcloud.conf\n/etc/cinder/cinder.conf\n/etc/neutron/neutron.conf\n/etc/glance/glance.conf\n/etc/keystone/keystone.conf\n\nIn each file, set these lines:\n\ndebug = true\nverbose = true\n\n2. Restart the OpenStack services\n3. Recreate the issue (if possible).\nIf possible use nova boot to recreate the error. See the following: \nhttp://www-01.ibm.com/support/docview.wss?uid=swg21697917 [http://www-01.ibm.com/support/docview.wss?uid=swg21697917]\nNote the following:\n- The date/time of the recreation (start and end if it's a long\nrecreate)\n- Information that can be used to identify the failure.\n- The VM name, hostname, IP address for deploy/delete failures\n- UUID of the instance and Name in the Cloud VS name in the GUI\n4. Gather the data, return to Section II above.\n5. If managing PowerVC, use QMGCOLLECT.sh option 2 (shown above) to \ngather powervc-diag data. Alternatively, run /usr/bin/powervc-diag\non the PowerVC system and upload the logs.\n\n6. Screen shots are helpful, if there is a visible failure of some sort.\n\n\nSend any/all data you collected. QMGCOLLECT.sh option 8 should help \nwith data upload, however if that does not work try one of the methods here:\nhttp://www-05.ibm.com/de/support/ecurep/send.html [http://www-05.ibm.com/de/support/ecurep/send.html]\n\n========================================================================\n\nUseful commands (Reference):\n\nRetrieving the SCE version on the Region Server\ntelnet localhost 7777 --> version\n\nRestarting the OpenStack Services\nservice qpidd start/stop/status/restart\nservice openstack-smartcloud start/stop/status/restart\nservice openstack-cinder-scheduler start/stop/status/restart\nservice openstack-cinder-volume start/stop/status/restart\nservice openstack-cinder-api start/stop/status/restart\nservice openstack-glance-registry start/stop/status/restart\nservice openstack-glance-api start/stop/status/restart\nservice openstack-nova-api start/stop/status/restart\nservice openstack-nova-cert start/stop/status/restart\nservice openstack-nova-consoleauth start/stop/status/restart\nservice openstack-nova-scheduler start/stop/status/restart\nservice openstack-nova-conductor start/stop/status/restart\nservice openstack-nova-novncproxy start/stop/status/restart\nservice openstack-nova-network start/stop/status/restart\nservice vilProxy start/stop/status/restart\n\nRestarting SCE\nservice sce start /stop/status/restart\n\nRestarting PowerVC\n/opt/ibm/powervc/bin/powervc-services start/stop/status/restart", " FLASH (ALERT)\n\nABSTRACT\n Cloud Orchestrator (ICO) continues to be a strategic solution for IBM \n\nCONTENT\nIBM Cloud Orchestrator continues to be a strategic solution for IBM in Hybrid Cloud management and will continue to be actively developed. Future IBM Cloud Orchestrator releases will enable management of external OpenStack environments which are compliant with the RefStack certification, providing more choices and flexibility to clients to select their preferred OpenStack vendor. The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below).\nIBM Cloud Orchestrator (ICO) and IBM Cloud Manager with OpenStack (ICMO) will continue to be supported until Sept 2020.\n\nReference: ICMO End of Market announcement:\nhttp://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en]", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Does 2.4.0.1 support RHEL7 images?\n \n VMware driver that comes with OpenStack (Icehouse) does not\n check or restrict the guest OS. As ICO 2.4 leverages the\n OpenStack Vmware driver, you can deploy the RHEL 7 image.\n \n Another clarification which needs to be made is in regards to\n ext3/ext4 versus xfs for the image.\n \n \n \n \n \n\nLOCAL FIX\n * n/a\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Does 2.4.0.1 support RHEL7 images?\n \n VMware driver that comes with OpenStack (Icehouse) does not\n check or restrict the guest OS. As ICO 2.4 leverages the\n OpenStack Vmware driver, you can deploy the RHEL 7 image.\n \n Another clarification which needs to be made is in regards to\n ext3/ext4 versus xfs for the image.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The Documentation will be updated in ICO 2.4.0.4\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n ZZ00462\n \n \n * REPORTED COMPONENT NAME\n SMRTCLOUD ORCHS\n \n \n * REPORTED COMPONENT ID\n 5725H2800\n \n \n * REPORTED RELEASE\n 240\n \n \n * STATUS\n CLOSED DOC\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2015-08-24\n \n \n * CLOSED DATE\n 2016-06-29\n \n \n * LAST MODIFIED DATE\n 2016-06-29\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS", " SECURITY BULLETIN\n\nSUMMARY\n A security vulenrability has been identified in Open vSwitch that is used by IBM Cloud Manager with OpenStack. IBM Cloud Manager with OpenStack has addressed the applicable CVE. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-2074 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2074]\nDESCRIPTION: Open vSwitch is vulnerable to a buffer overflow, caused by improper bounds checking by MPLS labels in an OVS internal data structure. By sending specially-crafted MPLS packets, a remote attacker could overflow a buffer and execute arbitrary code on the system or cause a denial of service.\nCVSS Base Score: 7.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/111822 [https://exchange.xforce.ibmcloud.com/vulnerabilities/111822] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Cloud Manager with OpenStack 4.3.0 through 4.3.0.8 Interim Fix 1 \n\nREMEDIATION/FIXES\n \n\nProduct VRMF Remediation/First Fix IBM Cloud Manager with OpenStack 4.3 through 4.3.0.8 Interim Fix 1 Upgrade to IBM Cloud Manager with OpenStack 4.3 fix pack 9:\n[https://www-945.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FOther+software%2FCloud+Manager+with+Openstack&fixids=4.3.0.7-IBM-CMWO-FP07&source=SAR&function=fixId&parent=ibm/Other%20software] [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FCloud+Manager+with+Openstack&fixids=4.3.0.8-IBM-CMWO-IF001&source=SAR]http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FOther+software%2FCloud+Manager+with+Openstack&fixids=4.3.0.9-IBM-CMWO-FP09&source=SAR [https://www.ibm.com/support/fixcentral/swg/selectFixes?product=ibm%2FOther+software%2FCloud+Manager+with+Openstack&fixids=4.3.0.9-IBM-CMWO-FP09&source=SAR&function=fixId&parent=ibm/Other%20software] \nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 14 December 2017: Original Version Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.", " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS DOCUMENTATION ERROR.\n \n \n \n\nERROR DESCRIPTION\n * OpenStack is designed to power off any VM which is\n listed as powered off via it's database, if a VM is\n powered on OUTSIDE the Openstack interface the next\n sync state will find the VM in an incorrect state\n and power it off.\n .\n IBM is working to disable this feature of OpenStack.\n .\n This was documented for IBM products that consume openstack such\n as PowerVC and ICM:\n .\n http://www-01.ibm.com/support/docview.wss?uid=nas8N1020558\n http://www-01.ibm.com/support/docview.wss?uid=nas8N1020669 [http://www-01.ibm.com/support/docview.wss?uid=nas8N1020558http://www-01.ibm.com/support/docview.wss?uid=nas8N1020669]\n .\n Workaround:\n Update the nova.conf file, add :\n .\n sync_power_state_interval=-1\n .\n restart the OpenStack host OS (the Regin Server OS).\n .\n We need to document this on ICO.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ***********************************************************\n * USERS AFFECTED: All users of IBM Cloud Orchestrator 2.4\n ***********************************************************\n * PROBLEM DESCRIPTION:\n OpenStack powers off VMs that are powered on\n outside the OpenStack interface\n ***********************************************************\n * RECOMMENDATION:\n Review the next update of the IBM Knowledge Center for\n IBM Cloud Orchestrator V2.4 Fix Pack 4 when available\n ***********************************************************\n \n The documentation changes can also be found in the\n Conclusion section below.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The following section in IBM Cloud Orchestrator\n Knowledge Center has been updated:\n \"Configuring OpenStack\"\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n ZZ00430\n \n \n * REPORTED COMPONENT NAME\n SMRTCLOUD ORCHS\n \n \n * REPORTED COMPONENT ID\n 5725H2800\n \n \n * REPORTED RELEASE\n 240\n \n \n * STATUS\n CLOSED DOC\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2015-06-19\n \n \n * CLOSED DATE\n 2016-03-29\n \n \n * LAST MODIFIED DATE\n 2016-03-29\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n\nAPPLICABLE COMPONENT LEVELS" ]

[ [ "1a", " FLASH (ALERT) ABSTRACT" ], [ "1b", " Cloud Orchestrator (ICO) continues to be a strategic solution for IBM CONTENT" ], [ "1c", "IBM Cloud Orchestrator continues to be a strategic solution for IBM in Hybrid Cloud management and will continue to be actively developed." ], [ "1d", "Future IBM Cloud Orchestrator releases will enable management of external OpenStack environments which are compliant with the RefStack certification, providing more choices and flexibility to clients to select their preferred OpenStack vendor." ], [ "1e", "The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below)." ], [ "1f", "IBM Cloud Orchestrator (ICO) and IBM Cloud Manager with OpenStack (ICMO) will continue to be supported until Sept 2020." ], [ "1g", "Reference: ICMO End of Market announcement: http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS916-062/index.html&lang=en&request_locale=en]" ] ]

[ "1b", "1c", "1d", "1e" ]

[ " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager \n\nSYMPTOM\nAfter entering configuration information in FEM Fixed Content Device Wizard the following error is received: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). \n\n \n\nError in the p8_server_error.log: \n\n\n2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.\ncom.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)\n\n\nCAUSE\nChanges made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded. \n\n\nENVIRONMENT\nIBM Websphere\n\n\n\nDIAGNOSING THE PROBLEM\nFollowing error is received when \"Test Connection\" is clicked: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).\n\n\nRESOLVING THE PROBLEM\nAfter making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine \nHISTORICAL NUMBER\n 41550\n180\n000", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Intermittently when viewing documents stored in ECM Centera the retrieval fails via FileNet Content Engine \n\nSYMPTOM\nWhen viewing documents, intermittently, users receive the following error. If the error is received a second attempt may succeed. On occasion the document is retrieved but pages may be missing. For example a five page document is retrieved but only the first four pages display. \n\nThe stack trace error is as follows: \n\nGetting document content has failed.<br>com.filenet.api.exception.EngineRuntimeException;Fixed Content Provider open operation failed. Provider: [com.filenet.engine.content.fcprovider.centera.CenteraFCP(21)]SeqN[0] Referral: [version(hex)=10001; checksum(hex)=170a; mode=1; flags=0;contentID={<GUID>}; clipID=<CLIPID>;numContentElements=2;Tag[0]=>ceSeqNum[1];][Code=null]...Object Reference [DOCUMENT:1]ID\"{<GUID>}\" in ObjectStore \"{<OS GUID>}\";OMFC/Document/GetContent//CONTENT_FCP_OPERATION_FAILED_ON_OPEN\n\n\nCAUSE\nThis is a known Centera Device issue:\n\nCause: \n\nInternal memory leak. The memory leak results in a consumption rate of approximately 2.0 to 2.5 megabytes (MB) per day and affects only Gen4/Gen4LP nodes running CentraStar version 4.1.0-3343-0-0 or CentraStar version 4.1.1-3610-0-0. After a period of six to nine months of system uptime has elapsed at these microcode revisions, users may report incidents of application performance and/or nodes within the cluster will reboot in order to release Slab memory for internal and external operations.\n\nWorkaround: \n\nReboot the Linix platform on each affected node to release the amount of slab memory actively being consumed.\n\nPermanent Fix: \n\nTwo CentraStar patches have been made generally available (GA) in order to resolve the memory leak; CentraStar 4.1.0p1 (4.1.0-3672-1-0) and CentraStar 4.1.1p1 (4.1.1-3673-1-0).\n\n\n\nENVIRONMENT\nSpecific to a Linux\\Centera environment\n\n\n\nDIAGNOSING THE PROBLEM\nUsers intermittently receive the following stack trace error or the full document is not downloaded. \n\n Getting document content has failed.<br>com.filenet.api.exception.EngineRuntimeException;Fixed Content Provider open operation failed. Provider: [com.filenet.engine.content.fcprovider.centera.CenteraFCP(21)]SeqN[0] Referral: [version(hex)=10001; checksum(hex)=170a; mode=1; flags=0;contentID={<GUID>}; clipID=<CLIPID>;numContentElements=2;Tag[0]=>ceSeqNum[1];][Code=null]...Object Reference [DOCUMENT:1]ID\"{<GUID>}\" in ObjectStore \"{<OS GUID>}\";OMFC/Document/GetContent//CONTENT_FCP_OPERATION_FAILED_ON_OPEN\n\n\nRESOLVING THE PROBLEM\n \n\n * Short term resolution is to reboot the Linux platform on each affected node.\n \n * Long term resolution is to apply the following CentraStar patches 4.1.0 Patch 1 (4.1.0-3672-1-00 and 4.1.1 patch (4.1.1-3673-1-0)\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Content Manager", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Intermittendly and very rarely workflow subscriptions fails to execute, but are usually successful on the 2nd try. \n\nSYMPTOM\nIn the Content Platform Engine (CPE) Error Logs, following error can be observed:\nEVNT FNRCV0006E - ERROR Exception in method onEvent() of handler filenet.pe.ce.wfeventhandler.WorkflowEventActionHandler com.filenet.api.exception.EngineRuntimeException: FNRCV0006E: EVENT_HANDLER_THREW: An exception occurred in the event handler. Message was: Failed to get a JAAS subject.\n\n\n\nCAUSE\nThe cause for the problem is unknown.\n\n\nRESOLVING THE PROBLEM\nSet the option \n-Dcom.filenet.engine.init.BGThreadsAsBootstrapId=true on the Java Runtime environment where\nthe CPE server is running.\n\nCPE performs asynchronous tasks with a pool of background threads. By default, those threads are started with no particular security context. If a security context is needed, the background task would provide it.\n\nIf \"com.filenet.engine.init.BGThreadsAsBootstrapId\" is set to true, those threads are started with a security context that uses a JAAS Subject based on the CPE bootstrap credentials. In that case, even if a background task does not create a security context, the bootstrap security context should still be active.\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet P8 Platform Process Engine Windows, AIX, HP-UX, Linux, Solaris 5.2.1", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n With FileNet Deployment Manager (FDM), for FileNET Content Platform Engine (CPE), you can export a document class and it's associated property templates. For example, going from a Development (source) environment to a Production (target) environment. \n\nWith versions prior to CPE 5.2.1, An Administrator, using FileNet Enterprise Manager (FEM), could create a single database index on a property template in order to improve database performance.\n\nWhen importing the document class and it's associated property templates, FDM does not carry over or retain the single index creation on the property template, which could cause database performance problems on the target environment. \n\nSYMPTOM\nPossible database related performance problems with CPE on the target server.\n\n\nCAUSE\nFDM does not carry over or retain a database index associated with a property template. \n\nDIAGNOSING THE PROBLEM\nSudden performance problems on the target environment after exporting a Document Class from one FileNET P8 server to P8 another.\n\nRESOLVING THE PROBLEM\nIf exporting a document class from a source environment, then importing it into the target environment, where there are certain property templates that are indexed in the database, the process of re-creating the same indexes have to be performed on the target environment after importing the document class.\n\nThe recommendation is to use Administration Console Content Engine (ACCE) to perform the index creation on the target server, this way the metadata stays consistent with the database. \n\n\nWith the release of CPE 5.2.1, improvements were made to the creation of database indexes. Prior to CPE version 5.2.1, a given property definitions column could be indexed by setting the corresponding ColumnDefinition's \"IsSingleIndexed\" property to True. This property, however was deprecated in version 5.2.1, the property was replaced with a much richer set of functionality that enables multi-column index creation. As a result, the TableDefinition class was enhanced with an object valued list property named IndexDefinitions. A CmIndexDefinition is then comprised of a set of CmIndexedColumn objects. ACCE has been extended with this functionality via a new Table Definitions node under the current Data Design node. \n\n[/support/docview.wss?uid=swg21702759&aid=1] [/support/docview.wss?uid=swg21702759&aid=1]\n\nReferences\nhttp://www-01.ibm.com/support/knowledgecenter/api/content/nl/en-us/SSGLW6_5.2.1/com.ibm.p8.relnotes.doc/wn_cpe_dev.htm [http://www-01.ibm.com/support/knowledgecenter/api/content/nl/en-us/SSGLW6_5.2.1/com.ibm.p8.relnotes.doc/wn_cpe_dev.htm]\n\nhttp://www-01.ibm.com/support/knowledgecenter/SSGLW6_5.2.1/com.ibm.p8.ce.dev.prop.doc/props_CmIndexDefinition.htm [http://www-01.ibm.com/support/knowledgecenter/SSGLW6_5.2.1/com.ibm.p8.ce.dev.prop.doc/props_CmIndexDefinition.htm]", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When attempting to configure a Centera fixed content device in FileNet Content Engine Enterprise Manager (FEM) a Failed to open Pool to Centera device error is encountered. \n\nCAUSE\nThe default port 3218 was only open for TCP.\n\nDIAGNOSING THE PROBLEM\nThe FEM Test Connection Error: \n\n\n * \n * \n \n * File = .\\FnFCSMgr.cpp, Line = 359, Rev. = $Revision: 1.20 $\n * The [connect] operation on the fixed content provider \n * [com.filenet.engine.content.fcprovider.centera.CenteraFCP(13)] failed. \n * content device. Adaptor: \n * The fixed content provider could not establish a connection to the fixed \n * [com.filenet.engine.content.fcprovider.centera.CenteraAdaptor]. Failed \n * to open Pool to Centera device. no primary cluster found. \n\n\nThe corresponding error in the SystemOut.log file: \n\n \n\n * [\n * MM/DD/YY H:MM:SS:772 EDT] 0000004a LocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method \"executeChanges\" on bean \"BeanId(FileNetEngine#Engine-ejb-ws.jar#EngineCore, null)\". Exception data: com.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [connect] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={\n * \n * at com.filenet.engine.content.fcprovider.centera.CenteraFCP.connect(CenteraFCP.java:223)\n * \n * at com.filenet.engine.content.fcprovider.BaseFixedContentProvider.adminConnect(BaseFixedContentProvider.java:73)\n * \n * at com.filenet.engine.content.FixedContentProviderCache.getProviderForCreate(FixedContentProviderCache.java:144)\n * \n * at com.filenet.engine.persist.FixedContentDevicePersister.validateProperties(FixedContentDevicePersister.java:170)\n * \n * ...\n * \n * ...\n * \n * Caused by: com.filenet.api.exception.EngineRuntimeException: FNRCC0074E: CONTENT_FCP_CONNECTION_FAILED: The fixed content provider could not establish a connection to the fixed content device. Adaptor: [com.filenet.engine.content.fcprovider.centera.CenteraAdaptor]. failedBatchItem=0\n * \n * at com.filenet.engine.content.fcprovider.centera.CenteraAdaptor.openPool(CenteraAdaptor.java:219)\n * \n * at com.filenet.engine.content.fcprovider.centera.CenteraFCP.connect(CenteraFCP.java:216)\n * \n * ... 49 more\n * \n * Caused by: com.filenet.api.exception.EngineRuntimeException: FNRCC0064E: CONTENT_FCP_CENTERA_OPEN_POOL_FAILED: Failed to open Pool to Centera device. failedBatchItem=0\n * \n * at com.filenet.engine.content.fcprovider.centera.CenteraPoolCache.createNewPool(CenteraPoolCache.java:326)\n * \n * at com.filenet.engine.content.fcprovider.centera.CenteraPoolCache.openPool(CenteraPoolCache.java:94)\n * \n * at com.filenet.engine.content.fcprovider.centera.CenteraAdaptor.openPool(CenteraAdaptor.java:215)\n * \n * ... 50 more\n * \n * Caused by: com.filepool.fplibrary.FPLibraryException: no primary cluster found failedBatchItem=0\n * \n * at com.filepool.fplibrary.FPPool.<init>(Unknown Source)\n * \n * at com.filenet.engine.content.fcprovider.centera.CenteraPoolCache.createNewPool(CenteraPoolCache.java:323)\n * \n * ... 52 more\n\n\nRESOLVING THE PROBLEM\nOpen TCP and UDP in the firewall for the default port 3218 from the Content Engine to the Centera Pool IP addresses" ]

[ [ "0a", " TECHNOTE (TROUBLESHOOTING) PROBLEM(ABSTRACT)" ], [ "0b", " Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager SYMPTOM" ], [ "0c", "After entering configuration information in FEM Fixed Content Device Wizard the following error is received:" ], [ "0d", "File = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $" ], [ "0e", "The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed." ], [ "0f", "FPLibrary (Not found in java.library.path)." ], [ "0g", "Error in the p8_server_error.log:" ], [ "0h", "2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed." ], [ "0i", "com.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={" ], [ "0j", "Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0" ], [ "0k", "Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) CAUSE" ], [ "0l", "Changes made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script." ], [ "0m", "The WAS Content Engine instance was restarted from within the WAS console and not from the command line." ], [ "0n", "In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized ." ], [ "0o", "This caused the CenteraSDK path to not be loaded. ENVIRONMENT IBM Websphere" ], [ "0p", "DIAGNOSING THE PROBLEM" ], [ "0q", "Following error is received when \"Test Connection\" is clicked:" ], [ "0r", "File = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $" ], [ "0s", "The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed." ], [ "0t", "FPLibrary (Not found in java.library.path)." ], [ "0u", "RESOLVING THE PROBLEM" ], [ "0v", "After making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected." ], [ "0w", "Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine HISTORICAL NUMBER 41550 180 000" ] ]

[ "0a", "0b", "0c", "0d", "0e", "0f", "0g", "0h", "0i", "0j", "0k", "0l", "0m", "0n", "0o", "0p", "0q", "0r", "0s", "0t", "0u", "0v", "0w" ]

[ " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Using SORTUPBY function in a IBM transformation Extender\n (ITX) V9.0.0.2 map rule does not encounter an error as expected.\n The map completes successfully but there is no output created.\n \n SORTUPBY is a new feature in ITX 9.0.0.3.\n \n \n \n \n \n\nLOCAL FIX\n * ITXCQ - ITX00058959\n GK / GK\n Circumvention: None\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Users Affected:\n IBM Transformation Extender customers who compile maps in\n release X and try to run them in a release earlier than X.\n \n \n Problem Description:\n If a map encounters an unknown \"opcode\" in a rule, it was just\n returning NONE for that opcode.\n \n Platforms Affected:\n All\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The code has been changed to set a \"map must be recompiled\"\n return code and abort the map.\n \n Applies to:\n 9.0.0.3\n \n Fixed in the next service packs and releases.\n \n To obtain the fix for this APAR:\n \n To see if the next service pack or product release is available,\n check the IBM Transformation Extender Downloads page:\n http://www.ibm.com/support/entry/portal/product/other_software/t [http://www.ibm.com/support/entry/portal/product/other_software/t]\n ransformation_extender\n \n If the service pack or product release is available, download it\n from Fix Central:\n http://www.ibm.com/support/fixcentral/ [http://www.ibm.com/support/fixcentral/]\n \n If the service pack or product release is not available and you\n require the APAR fix immediately, request a Limited Availability\n Interim Fix (LAIF) by opening a PMR:\n http://www.ibm.com/support/servicerequest/Home.action [http://www.ibm.com/support/servicerequest/Home.action]\n \n Prior to version 9.0.0, IBM Transformation Extender was called\n IBM WebSphere Transformation Extender.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI99127\n \n \n * REPORTED COMPONENT NAME\n ITX\n \n \n * REPORTED COMPONENT ID\n 5724Q2300\n \n \n * REPORTED RELEASE\n 900\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2018-06-13\n \n \n * CLOSED DATE\n 2018-07-26\n \n \n * LAST MODIFIED DATE\n 2018-07-30\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n ITX\n \n \n * FIXED COMPONENT ID\n 5724Q2300\n \n \n\nAPPLICABLE COMPONENT LEVELS", " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 'Adapter not found' using the IBM Transformation Extender (ITX)/WebSphere Transformation Extender (WTX) Soap adapter on Sterling Integrator. \n\nSYMPTOM\n'Adapter not found' using the ITX Soap adapter on Sterling Integrator.\n\n\nCAUSE\nSterling Integrator is unable to locate the SOAP JAR files needed to run the ITX/WTX map.\n\nENVIRONMENT\nRunning a ITX/WTX map using the ITX/WTX Soap adapter on Sterling Integrator.\n\nDIAGNOSING THE PROBLEM\nThe JNI log contains the following errors :\n\nERROR: Unable to retrieve classloaderinfo for jni env: 0x7bf9ee00, class: \n\n*ERR: in _mjpiWTXLogCallback (-2)\n\n*ERR: Function failed (-3) in dtxjpiGetConfig()\n\n\n\n\n\nRESOLVING THE PROBLEM\nAdd the following jar files to the external section of the ITX Dtx.ini file. \n\ndtxpi.jar, m4soap.jar, and xds4j.jar\n\nFor Example :\n\nIf ITX was installed in C:\\IBM\\WebSphere Transformation Extender 9.0.0 on windows.\n\nYou would add the following to the dtx.ini file.\n\n[External Jar Files] \njar1=C:\\IBM\\WebSphere Transformation Extender 9.0.0\\m4soap.jar \njar2=C:\\IBM\\WebSphere Transformation Extender 9.0.0\\dtxpi.jar \njar3=C:\\IBM\\WebSphere Transformation Extender 9.0.0\\xds4j.jar", "B2B; Sterling; ITX; email adapter; SSL; SSLINIT; GSK_ATTRIBUTE_INVALID_ID; m4gskssl; failed initialization TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Calling map with ITX EMAIL target fails from SI / SPE \n\nSYMPTOM\nFollowing error seen from ITX Email adapter trace file:\n\n[WSAStart: SSL library load succeeded. Loaded library = m4gskssl] \n\nThe m4gskssl module loaded, but failed initialization. The m4gskssl\nmodule's log file, as set in the dtx.ini file, can be viewed for \nfurther details. \n\n[WSAStart: SSL library init failed. Loaded library = m4gskssl] \n\nwtxsslclient.log file shows the following:\n\nSSLINIT Error: SSL library init failed.\nReason: CVE settings were NOT properly set, check log for further \ndetails: 701 (GSK_ATTRIBUTE_INVALID_ID). \n\n\nCAUSE\nCertain GSKit environment variable needed to be in place to successfully be loaded.\n\nDIAGNOSING THE PROBLEM\nEnable ITX_SSL_TRACE_FILE in the problematic environment variable to produce a wtxsslclient.log file.\nRunning ps ewwww <pid> with pid being noapp as that is the SI WTX map execution process, will show the environment variable that is being loaded by noapp.\n\nEnable -T+ in the problematic email rule to produce an ITX Email adapter trace file call m4email.mtr\n\nRESOLVING THE PROBLEM\nAdd following environment variable to SI: \n\n1. Change directory to <si_install_dir>/bin \n2. Back up and Edit tmp.sh.in file \n3. Add entry below to the end of file and save the file \n... \nfi \n} \nexport GSK_STRICTCHECK_CBCPADBYTES=GSK_TRUE \nexport GSK_STRICTCHECK_CBCPADBYTES_SSL=GSK_TRUE \nexport GSK_VACCINATE=GSK_TRUE \n~ \n\n4. Run <si_install_dir>/bin/hardstop.sh \n5. Run <si_install_dir>/bin/setupfiles.sh \n6. Ensure that the following lines \n\nGSK_STRICTCHECK_CBCPADBYTES=GSK_TRUE \nGSK_STRICTCHECK_CBCPADBYTES_SSL=GSK_TRUE \nGSK_VACCINATE=GSK_TRUE \n\nare seen in the environment variable displayed from the following run: \n\nPlease run the ps ewwww <pid> \n\nThe pid should be for the \nnoapp.NoAppServer as that is the SI WTX \nmap execution process.", "z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * The IBM Transformation Extender (ITX) z.OS Batch Command Server\n may ABEND when a top level map calls a sub map with a RUN()\n function, and that sub map has output cards defined to use\n the SINK adapter.\n \n CEE3204S The system detected a protection exception (System\n Completion\n Code=0C4).\n From compile unit\n WINMVS7:/scm/builds/9.0.0.1/source/64/os390/mvs/mvs.c at entry\n point\n addMercfile at statement 2782 at\n compile unit offset +000000001A3DA8F8 at entry offset\n +0000000000000480 at address 000000001A3DA8F8.\n \n \n \n \n \n\nLOCAL FIX\n * WTXRTC - 60394\n PB / PB\n No known workaround\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM Transformation Extender *\n * (ITX) V9.0.0 *\n ****************************************************************\n * PROBLEM DESCRIPTION: ABEND USING ITX 9.0.0.1 ON Z/OS BATCH *\n * WHERE TO TOP LEVEL MAP CALLS A SUB *\n * MAP WITH A RUN() FUNCTION AND SUB MAP *\n * USING SINK *\n ****************************************************************\n * RECOMMENDATION: Apply this maintenance *\n ****************************************************************\n ABEND USING ITX 9.0.0.1 ON Z/OS BATCH WHERE TO TOP LEVEL MAP\n CALLS A SUB MAP WITH A RUN() FUNCTION AND SUB MAP USING SINK\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI78956\n \n \n * REPORTED COMPONENT NAME\n TX Z/OS\n \n \n * REPORTED COMPONENT ID\n 5655R9900\n \n \n * REPORTED RELEASE\n 900\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2017-03-28\n \n \n * CLOSED DATE\n 2017-03-29\n \n \n * LAST MODIFIED DATE\n 2017-04-04\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n PI78873 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI78873]\n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n UI45997\n \n \n\nMODULES/MACROS\n * DTXLQ22 DTXLX22 DTX55DAG DTX55DAN DTX55DAX\n DTX55ING DTX55INN DTX55INX DTX55UCG DTX55UCN DTX55UCX\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n TX Z/OS\n \n \n * FIXED COMPONENT ID\n 5655R9900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY UI45997 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI45997]\n UP17/03/31 P F703\n \n \n\nFIX IS AVAILABLE\n * SELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", " SUBSCRIBE TO THIS APAR\nBy subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.\n\nNotify me when this APAR changes.\n\nNotify me when an APAR for this component changes.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * When testing the size of input parameters to a custom function\n in ITX, it may be observed that the length is double the\n expected length if the item being passed in is a string literal.\n \n Example, the following two rules where the object 'Input1'\n contains \"HelloWorld\" the same result is expected.\n \n =MyLib->SomeFunction(\"HelloWorld\")\n =MyLib->SomeFunction(Input1)\n \n Instead the following result is seen:\n \n 20,HelloWorld <- the length being incorrectly displayed X2\n 10,HelloWorld\n \n \n \n \n \n\nLOCAL FIX\n * WTXRTC - 60179\n PB / PB\n Circumvention: The size could be passed in as an additional\n parameter, but this brings additional overhead.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Users Affected:\n IBM Transformation Extender customers who use TX external\n functions\n \n Problem Description:\n When using TX external map functions, some parameters may not\n have the correct lengths.\n \n Platforms Affected:\n All\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fixed issue in CallExternalFuncProc to adjust the lengths after\n being converted to native.\n \n Applies to:\n 8.4.1.4, 9.0.0.1\n \n Fixed in the next service packs and releases.\n \n To obtain the fix for this APAR:\n \n To see if the next service pack or product release is available,\n check the IBM Transformation Extender Downloads page:\n http://www.ibm.com/support/entry/portal/product/other_software/t [http://www.ibm.com/support/entry/portal/product/other_software/t]\n ransformation_extender\n \n If the service pack or product release is available, download it\n from Fix Central:\n http://www.ibm.com/support/fixcentral/ [http://www.ibm.com/support/fixcentral/]\n \n If the service pack or product release is not available and you\n require the APAR fix immediately, request a Limited Availability\n Interim Fix (LAIF) by opening a PMR:\n http://www.ibm.com/support/servicerequest/Home.action [http://www.ibm.com/support/servicerequest/Home.action]\n \n Prior to version 9.0.0, IBM Transformation Extender was called\n IBM WebSphere Transformation Extender.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI76808\n \n \n * REPORTED COMPONENT NAME\n ITX\n \n \n * REPORTED COMPONENT ID\n 5724Q2300\n \n \n * REPORTED RELEASE\n 900\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2017-02-20\n \n \n * CLOSED DATE\n 2017-03-31\n \n \n * LAST MODIFIED DATE\n 2017-09-20\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n ITX\n \n \n * FIXED COMPONENT ID\n 5724Q2300\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R900 PSY\n UP" ]

[ [ "3a", "z/os A FIX IS AVAILABLE" ], [ "3b", "Obtain the fix for this APAR. SUBSCRIBE" ], [ "3c", "You can track all active APARs for this component. APAR STATUS" ], [ "3d", " * CLOSED AS PROGRAM ERROR. ERROR DESCRIPTION" ], [ "3e", " * The IBM Transformation Extender (ITX) z.OS Batch Command Server" ], [ "3f", " may ABEND when a top level map calls a sub map with a RUN()" ], [ "3g", " function, and that sub map has output cards defined to use" ], [ "3h", " the SINK adapter." ], [ "3i", " CEE3204S The system detected a protection exception (System" ], [ "3j", " Completion" ], [ "3k", " Code=0C4)." ], [ "3l", " From compile unit" ], [ "3m", " WINMVS7:/scm/builds/9.0.0.1/source/64/os390/mvs/mvs.c at entry" ], [ "3n", " point" ], [ "3o", " addMercfile at statement 2782 at" ], [ "3p", " compile unit offset +000000001A3DA8F8 at entry offset" ], [ "3q", " +0000000000000480 at address 000000001A3DA8F8. LOCAL FIX" ], [ "3r", " * WTXRTC - 60394" ], [ "3s", " PB / PB" ], [ "3t", " No known workaround PROBLEM SUMMARY" ], [ "3u", " * ****************************************************************" ], [ "3v", " * USERS AFFECTED: All users of IBM Transformation Extender *" ], [ "3w", " * (ITX) V9.0.0 *" ], [ "3x", " ****************************************************************" ], [ "3y", " * PROBLEM DESCRIPTION: ABEND USING ITX 9.0.0.1 ON Z/OS BATCH *" ], [ "3z", " * WHERE TO TOP LEVEL MAP CALLS A SUB *" ], [ "3aa", " * MAP WITH A RUN() FUNCTION AND SUB MAP *" ], [ "3ab", " * USING SINK *" ], [ "3ac", " ****************************************************************" ], [ "3ad", " * RECOMMENDATION: Apply this maintenance *" ], [ "3ae", " ****************************************************************" ], [ "3af", " ABEND USING ITX 9.0.0.1 ON Z/OS BATCH WHERE TO TOP LEVEL MAP" ], [ "3ag", " CALLS A SUB MAP WITH A RUN() FUNCTION AND SUB MAP USING SINK PROBLEM CONCLUSION TEMPORARY FIX COMMENTS APAR INFORMATION" ], [ "3ah", " * APAR NUMBER" ], [ "3ai", " PI78956" ], [ "3aj", " * REPORTED COMPONENT NAME" ], [ "3ak", " TX Z/OS" ], [ "3al", " * REPORTED COMPONENT ID" ], [ "3am", " 5655R9900" ], [ "3an", " * REPORTED RELEASE" ], [ "3ao", " 900" ], [ "3ap", " * STATUS" ], [ "3aq", " CLOSED PER" ], [ "3ar", " * PE" ], [ "3as", " NoPE" ], [ "3at", " * HIPER" ], [ "3au", " NoHIPER" ], [ "3av", " * SPECIAL ATTENTION" ], [ "3aw", " NoSpecatt / Xsystem" ], [ "3ax", " * SUBMITTED DATE" ], [ "3ay", " 2017-03-28" ], [ "3az", " * CLOSED DATE" ], [ "3ba", " 2017-03-29" ], [ "3bb", " * LAST MODIFIED DATE" ], [ "3bc", " 2017-04-04" ], [ "3bd", " * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:" ], [ "3be", " PI78873 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI78873]" ], [ "3bf", " * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:" ], [ "3bg", " UI45997 MODULES/MACROS" ], [ "3bh", " * DTXLQ22 DTXLX22 DTX55DAG DTX55DAN DTX55DAX" ], [ "3bi", " DTX55ING DTX55INN DTX55INX DTX55UCG DTX55UCN DTX55UCX FIX INFORMATION" ], [ "3bj", " * FIXED COMPONENT NAME" ], [ "3bk", " TX Z/OS" ], [ "3bl", " * FIXED COMPONENT ID" ], [ "3bm", " 5655R9900" ], [ "3bn", "APPLICABLE COMPONENT LEVELS" ], [ "3bo", " * R900 PSY UI45997 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI45997]" ], [ "3bp", " UP17/03/31 P F703" ], [ "3bq", "FIX IS AVAILABLE" ], [ "3br", " * SELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL." ], [ "3bs", "YOU WILL BE REQUIRED TO SIGN IN." ], [ "3bt", "DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES." ] ]

[ "3e", "3f", "3g", "3h", "3i", "3j", "3k", "3l", "3m", "3n", "3o", "3p", "3q", "3r", "3s", "3t", "3u", "3v", "3w", "3x", "3y", "3z", "3aa", "3ab", "3ac", "3ad", "3ae", "3af", "3ag" ]