\n
\n\n\n\n
\nomnibus web gui; login; dash; migration
\n\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n \n\n
Question
\nIn the course of migration from Web GUI 7.x to 8.1 I plan to run old and new installations side by side on the same machine. How can I avoid sessions logging each other out?
\nCause
\n\n
\n It is possible to run multiple Web GUI installations of different versions on the same machine using different ports, but if you then try to run sessions to each installation from the same browser using the default configuration, the one session will log the other session out.
\nAnswer
\n\n
\n Here are three options:
\nOption 1 - Rename the session cookie in DASH (WAS 8.0):
https://www-01.ibm.com/support/knowledgecenter/SSYJ99_8.0.0/admin/http_sessn_cookie.html?lang=en
Option 2 - Configure Single Sign-on between the two installations:
http://www-01.ibm.com/support/knowledgecenter/SSTPTP_1.3.0/com.ibm.netcool_ops.doc_1.3.0/omn_nmip/task/nnm_noi_configuresinglesignon.html
Option 3 - Use separate browsers for the two installations for the period of time that they run side-by-side (e.g. IE for one and FF for the other)
\n \n
\n ",
+ "title": "IBM Running Web GUI browser sessions side by side - United States",
+ "text": "omnibus web gui; login; dash; migration TECHNOTE (FAQ)\n\nQUESTION\n In the course of migration from Web GUI 7.x to 8.1 I plan to run old and new installations side by side on the same machine. How can I avoid sessions logging each other out? \n\nCAUSE\nIt is possible to run multiple Web GUI installations of different versions on the same machine using different ports, but if you then try to run sessions to each installation from the same browser using the default configuration, the one session will log the other session out.\n\nANSWER\nHere are three options: \n\nOption 1 - Rename the session cookie in DASH (WAS 8.0):\nhttps://www-01.ibm.com/support/knowledgecenter/SSYJ99_8.0.0/admin/http_sessn_cookie.html?lang=en [https://www-01.ibm.com/support/knowledgecenter/SSYJ99_8.0.0/admin/http_sessn_cookie.html?lang=en]\n\nOption 2 - Configure Single Sign-on between the two installations:\nhttp://www-01.ibm.com/support/knowledgecenter/SSTPTP_1.3.0/com.ibm.netcool_ops.doc_1.3.0/omn_nmip/task/nnm_noi_configuresinglesignon.html [http://www-01.ibm.com/support/knowledgecenter/SSTPTP_1.3.0/com.ibm.netcool_ops.doc_1.3.0/omn_nmip/task/nnm_noi_configuresinglesignon.html]\n\nOption 3 - Use separate browsers for the two installations for the period of time that they run side-by-side (e.g. IE for one and FF for the other)",
+ "metadata": {
+ "sourceDocumentId": "swg21975908",
+ "date": "2016-02-22",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21975908"
+ }
+ },
+ "swg21590082": {
+ "id": "swg21590082",
+ "content": "
\n
",
+ "title": "IBM Migrating RuleApps - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n How do I migrate the database that contains the RuleApps deployed to Rule Execution Server from one version to another? \n\nCAUSE\nThe data structure has undergone some refactoring between JRules V6.7 and V7.0. \n\nFor instance, the RULESET_RESOURCES table for storing ruleset has been modified: in V6.7, the ruleset archive was split into several parts for storage but in V7.0 and later, it is stored as a CLOB. \n\nThere is no change between V7.X versions. \n\nAs a conclusion, you cannot reuse the Rule Execution Server V6.7 database tables directly with Rule Execution Server V7.1. \n\n\nANSWER\nIf you are migrating between V7.X versions, you can reuse the Rule Execution Server database schema directly with the new version. \n\n \n\nIf you are migrating from V6.X, you must proceed in two steps: \n\n 1. Set up a new Rule Execution Server database schema and create the Rule Execution Server V7.1 tables as explained in the documentation at WebSphere ILOG JRules BRMS V7.1: Java EE add-ons [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/topic/com.ibm.websphere.ilog.jrules.install.doc/Content/Business_Rules/Documentation/_pubskel/JRules_Application_Servers/ps_Installing_JRules_IC.html] > Installing on \n\n
\n\n \n \n
\n
\n
\nTechnote (FAQ)
\n \n
\n
\n
\n \n
Question
\nHow do I migrate the database that contains the RuleApps deployed to Rule Execution Server from one version to another?
\nCause
\n\n
\n The data structure has undergone some refactoring between JRules V6.7 and V7.0.
\nFor instance, the RULESET_RESOURCES table for storing ruleset has been modified: in V6.7, the ruleset archive was split into several parts for storage but in V7.0 and later, it is stored as a CLOB.
\nThere is no change between V7.X versions.
\nAs a conclusion, you cannot reuse the Rule Execution Server V6.7 database tables directly with Rule Execution Server V7.1.
\n\n
Answer
\n\n
\n Option 1\n : Using \n Rule Execution Server \n Ant tasks \n
\n Option 2: Using \n the \n Rule Execution Server\n \n management console \n
\n
For more information on the managed XOM feature, see section \n Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server Deploying Java XOMs of the documentation."\n
\n If you are migrating between V7.X versions, you can reuse the Rule Execution Server database schema directly with the new version.
\n\n
If you are migrating from V6.X, you must proceed in two steps:
\n- \n
- Set up a new Rule Execution Server database schema and create the Rule Execution Server V7.1 tables as explained in the documentation at WebSphere ILOG JRules BRMS V7.1: Java EE add-ons > Installing on <your application server> > Installing Rule Execution Server > Installing Rule Execution Server on <your application server>. \n
- Migrate the V6.7 RuleApps to Rule Execution Server V7.1 in one of the following ways: \n
\n Option 1\n : Using \n Rule Execution Server \n Ant tasks \n
- \n
- Use the JRules V6.7 res-fetch-all Ant task to back up all your RuleApps to a single RuleApp archive. Or use the JRules 6.7 res-fetch Ant task to back up a specific RuleApp. \n
- Install and configure Rule Execution Server V7.1 according to the installation documentation on your server and using the new database schema. \n
- Deploy the RuleApp archive to the new Rule Execution Server by running the JRules V7.1 res-deploy Ant task. \n
\n Option 2: Using \n the \n Rule Execution Server\n \n management console \n
- \n
- From the Rule Execution Server V6.7 console, click the Server Info tab and click Backup RuleApps to back up all the deployed RuleApps. A JAR archive file containing all the RuleApps is generated. \n
- Install and configure Rule Execution Server V7.1 according to the installation documentation on your server and using the new database schema. \n
- Access the Rule Execution Server V7.1 console, click the Server Info tab and click Restore RuleApps to restore the RuleApp. \n
\n
If you are migrating from V7.1 to V7.5/V8.X, no ruleApp migration is needed, you can reuse the database. However, if you want to use the new managed XOM feature introduced in V7.5, you need to extend the database to include the XOM repository. You will do so either :
\n- \n
- through the Installation Settings Wizard that you will be prompted when accessing the new Rule Execution Server console, \n
- or by running the xomrepository_<DatabaseName>.sql script found in directory <ODM_75/8X_installDir>/executionserver/databases on the existing database schema. \n
For more information on the managed XOM feature, see section \n Decision Server Rules V7.5 > Managing business rule execution in Rule Execution Server Deploying Java XOMs of the documentation."\n
Related information
\nMigrating between JRules/WODM versions
Migrating a Rule Project to JRules v7.0 and v7.1
Migrating to Rule Team Server v7.0 and v7.1
\n
\n \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Integration | \nIBM Decision Server | \nMaintenance | \nPlatform Independent | \n7.5 | \nAll Editions | \n
\n
\n
\n \n \n\n
\n\n\n\n
\nrtc; hang; troubleshoot; infinite loop; terminate; compare; snapshot; workspace; scm; scm.exe; scm.ini; netstat; java; jvm; javacore
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n
\n \n
Problem(Abstract)
\nIf you launch the scm.exe command in IBM Rational Team Concert, you will observe that the command never terminates.
\nSymptom
\n\n
\n
\n
\n
The contents of \n
\n
\n
After you do this, launch the hanging operation, for example: \n
\n
\n
\n
In the same command window where the above command is running, type:\n
\n
\n
This sends a signal to the JVM and it writes the following:\n
\n
\n
The output indicates that the following files were created: \n
\n
\n
\n You invoke a comparison, for example you compare a Workspace and a Snapshot, with a command line like the following:
\n
C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse>scm compare -u userName -P password -r https://localhost:9443/jazz workspace "MyWorkspace" snapshot "Snapshot1" -I f
The command then never terminates: it hangs indefinitely.
Perform the following steps to capture log data to be used to troubleshoot the hanging behavior:
1. Open the file scm.ini, typically located in:
C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\scm.ini
The contents of the file look like the following:
\n \n \n
\n
\n -vm | \n
\n
\n
2. Change directory to the parent folder of java.exe.
From that directory, run java -version and save the output in a text file.
The output will indicate if the JVM is an IBM JVM.
\n
\n
3. The Steps 3-5 are only applicable to the IBM JVM.
\nIf you are using another JVM, then you will need to consult the documentation supplied by its vendor.
\nOpen scm.ini and add the following parameters, each on a separate line, starting after the line that contains vmargs:
\n \n \n
\n
\n -Xdump:java+system:events=user-verbose:gc -Xverbosegclog:verbosegc.%Y%m%d.%H%M%S.%pid.txt | \n
\n
The contents of \n
scm.ini should then look like this:\n \n
\n
\n \n \n
\n
\n -vmC:\\Program Files\\IBM\\TeamConcert\\jdk\\jre/bin/java.exe --launcher.suppressErrors -data @noDefault -vmargs -Xdump:java+system:events=user -verbose:gc -Xverbosegclog:verbosegc.%Y%m%d.%H%M%S.%pid.txt -Xmx512m -Xshareclasses -Xquickstart -Dosgi.requiredJavaVersion=1.5 | \n
After you do this, launch the hanging operation, for example: \n
\n
\n
C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse>scm compare -u userName -P password -r https://localhost:9443/jazz workspace "MyWorkspace" snapshot "Snapshot1" -I f\n \n
In the same command window where the above command is running, type:\n
\n
CTRL+BREAK\n \n
This sends a signal to the JVM and it writes the following:\n
\n
JVMDUMP006I Processing dump event "user", detail "" - please wait.
JVMDUMP032I JVM requested System dump using
'C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\core.20111018.121358.3896.0001.dmp'
in response to an event
C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse>JVMDUMP010I System dump written to C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\core.20111018.121358.3896.0001.dmp JVMDUMP032I JVM requested Java dump using
'C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\javacore.20111018.121358.3896.0002.txt'
in response to an event
JVMDUMP010I Java dump written to
C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\javacore.20111018.121358.3896.0002.txt
JVMDUMP013I Processed dump event "user", detail "".
/Project1/src/com/Class3.java
/Project1/src/com/If1.java \n \n
The output indicates that the following files were created: \n
\n
\n \n \n
\n
\n | File Name | \nPurpose | \n
verbosegc.20111018.122106.3848.txt | \n Verbose Garbage Collector log. | \n
javacore.20111018.121358.3896.0002.txt | \n Text file thatcontains the list of all threads. | \n
core.20111018.121358.3896.0001.dmp | \n System core dump. | \n
\n
\n
4. For an IBM JDK versions 1.6 and lower, you must process the system core dump with the jextract utility before submitting it to support.
This is the syntax of the jextract command:
<installroot>/jre/bin/jextract [corefile]
The jextract command produces a jar file.
5. Repeat the steps 3-4 a few times at a distance of a few minutes.
6. Collect the out output of the command:
netstat -an > netstat.log
7. Configure Command Line Interface tracing as discussed in the following article: Default logging for CLI
\n
Resolving the problem
\n\n
\n Submit the following artifacts to IBM Rational Client Support for investigation:
\n- \n
- Output of
java -version\n - Verbose Garbage Collector Log \n
javacorefiles \n corefile (processed withjextract) \n - Output of the
netstat -ancommand \n - Provide the output of the Command Line interface trace. \n
\n
Related information
\nIBM JDK Diagnosis
Source control command line reference
\n \n
\n \n
\n \n \n",
+ "title": "IBM MUSTGATHER: Troubleshooting hangs of the scm.exe application - United States",
+ "text": "rtc; hang; troubleshoot; infinite loop; terminate; compare; snapshot; workspace; scm; scm.exe; scm.ini; netstat; java; jvm; javacore TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you launch the scm.exe command in IBM Rational Team Concert, you will observe that the command never terminates. \n\nSYMPTOM\nYou invoke a comparison, for example you compare a Workspace and a Snapshot, with a command line like the following: \n\n \nC:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse>scm compare -u userName -P password -r https://localhost:9443/jazzworkspace \"MyWorkspace\" snapshot \"Snapshot1\" -I f \n\nThe command then never terminates: it hangs indefinitely. \n\nPerform the following steps to capture log data to be used to troubleshoot the hanging behavior:\n\n1. Open the file scm.ini, typically located in: \n\n \nC:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\scm.ini\n\n\nThe contents of the file look like the following:\n\n\n-vm\nC:\\Program Files\\IBM\\TeamConcert\\jdk\\jre/bin/java.exe\n--launcher.suppressErrors\n-data\n@noDefault \n-vmargs\n-Xmx512m\n-Xshareclasses\n-Xquickstart\n-Dosgi.requiredJavaVersion=1.5 \n\n2. Change directory to the parent folder of java.exe. \n\nFrom that directory, run java -version and save the output in a text file. \n\nThe output will indicate if the JVM is an IBM JVM. \n\n \n\n \n\n3. The Steps 3-5 are only applicable to the IBM JVM. \n\nIf you are using another JVM, then you will need to consult the documentation supplied by its vendor. \n\nOpenscm.ini and add the following parameters, each on a separate line, starting after the line that contains vmargs: \n\n-Xdump:java+system:events=user\n-verbose:gc\n-Xverbosegclog:verbosegc.%Y%m%d.%H%M%S.%pid.txt \n\nThe contents of scm.ini should then look like this: \n\n-vm\nC:\\Program Files\\IBM\\TeamConcert\\jdk\\jre/bin/java.exe \n--launcher.suppressErrors \n-data\n@noDefault\n-vmargs \n-Xdump:java+system:events=user\n-verbose:gc \n-Xverbosegclog:verbosegc.%Y%m%d.%H%M%S.%pid.txt\n-Xmx512m\n-Xshareclasses\n-Xquickstart\n-Dosgi.requiredJavaVersion=1.5 \nAfter you do this, launch the hanging operation, for example: \n\nC:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse>scm compare -u userName -P password -r https://localhost:9443/jazzworkspace \"MyWorkspace\" snapshot \"Snapshot1\" -I f \n\nIn the same command window where the above command is running, type: \nCTRL+BREAK \n\nThis sends a signal to the JVM and it writes the following: \nJVMDUMP006I Processing dump event \"user\", detail \"\" - please wait.\n\nJVMDUMP032I JVM requested System dump using \n'C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\core.20111018.121358.3896.0001.dmp' \nin response to an event\n\nC:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse>JVMDUMP010I System dump written to C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\core.20111018.121358.3896.0001.dmp JVMDUMP032I JVM requested Java dump using \n'C:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\javacore.20111018.121358.3896.0002.txt' \nin response to an event\n\nJVMDUMP010I Java dump written to \nC:\\Program Files\\IBM\\TeamConcert\\scmtools\\eclipse\\javacore.20111018.121358.3896.0002.txt \nJVMDUMP013I Processed dump event \"user\", detail \"\".\n\n/Project1/src/com/Class3.java\n/Project1/src/com/If1.java \n\nThe output indicates that the following files were created: \nFile Name Purpose verbosegc.20111018.122106.3848.txt Verbose Garbage Collector log. javacore.20111018.121358.3896.0002.txt Text file thatcontains the list of all threads. core.20111018.121358.3896.0001.dmp System core dump. \n \n\n4. For an IBM JDK versions 1.6 and lower, you must process the system core dump with the jextract utility before submitting it to support. \n\nThis is the syntax of the jextract command: \n\n
\n
",
+ "title": "IBM LO76551: NOTES2.EXE IS CRASHING ON 'OS.COINTERNETSETFEATUREENABLED' NATIVE METHOD - United States",
+ "text": " 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 * Notes Client 8.5.2 is crashing due to JVM on process\n OS.CoInternetSetFeatureEnabled native method\n \n Analysis\n ======\n \n Host Name : 0296COMP202\n User Name : albadmin\n Date : Wed Aug 07 14:55:27 2013\n Windows Dir : C:\\WINDOWS\n Arguments : \"C:\\Program Files\\lotus\\notes\\nsd.exe\"\n -dumpandkill -termstatus 1 -dlgopts showwait -wctpid 2472\n -wctexitcode 8096 -panicdirect -crashpid 3316 -crashtid 748\n -runtime 300\n NSD Version : 8.5.24.1271 (Release 8.5.2FP4)\n OS Version : Windows/XP 5.1 [32-bit] (Build 2600),\n PlatID=2, Service Pack 2, v.2096 (2 Processors)\n Build time : Fri Nov 18 03:08:35 2011\n Latest file mod : Thu Sep 29 08:27:40 2011\n Notes Core Version : Release 8.5.2 (32-bit client)\n Notes Standard Version : 8.5.2_20100811.1131\n Keyview Version : 10.8.0.0\n \n \n ############################################################\n ### thread 9/11: [ NLNOTES: 0cf4: 02ec]\n ### FP=0x042ce350, PC=0x77ccfc24, SP=0x042ce2ec\n ### stkbase=0x042d0000, total stksize=262144, used stksize=7444\n ############################################################\n [ 1] 0x77ccfc24 ntdll.KiFastSystemCallRet+0\n (468,493e0,0,42ce8d8)\n [ 2] 0x77e61d20 kernel32.WaitForSingleObject+18\n (468,493e0,0,42ceaf4)\n @[ 3] 0x6020d66d nnotes.OSRunExternalScript@8+1309 (12c,1)\n @[ 4] 0x6020daef nnotes.FRTerminateWindowsResources+975\n (1,1010,1,0)\n @[ 5] 0x6020df18 nnotes.OSFaultCleanupExt@24+984\n (1046a68,1010,0,0,0,42cee1c)\n @[ 6] 0x6020df9a nnotes.OSFaultCleanup@12+26 (0,1010,0)\n @[ 7] 0x60219844 nnotes.OSNTUnhandledExceptionFilter@4+276\n (42cfe54)\n @[ 8] 0x601daf5d nnotes.Panic@4+589 (42cfe6c)\n @[ 9] 0x601db034 nnotes.OSWCTPanicShutdown+84\n (9a8,1fa0,1732ee8,17357f0)\n @[10] 0x636bf3cc nnotesws.WCTShutdownThread+220\n (9a8,138200,77cd1c91,0)\n @[11] 0x6015584f nnotes.ThreadWrapper@4+175 (0)\n [12] 0x77e7344a kernel32.ExitThread+1643 (0,0,0,0)\n \n Start Time = 08/07/2013 02:55:09 PM\n Crash Time = 08/07/2013 02:55:27 PM\n Console Log Enabled = 1\n Console Position = 503\n Error Message = PANIC: The notes2 process (pid=2472) exited\n unexpectedly.\n \n NULL\n ----------------------------------------------------------------\n --------\n 0SECTION TITLE subcomponent dump routine\n NULL ===============================\n 1TISIGINFO Dump Event \"gpf\" (00002000) received\n 1TIDATETIME Date: 2013/08/07 at 16:30:27\n NULL\n ----------------------------------------------------------------\n --------\n 1XHEXCPCODE J9Generic_Signal_Number: 00000004\n 1XHEXCPCODE ExceptionCode: C0000005\n 1XHEXCPCODE ExceptionAddress: 00000020\n 1XHEXCPCODE ContextFlags: 0001003F\n 1XHEXCPCODE Handler1: 7FEFA090\n 1XHEXCPCODE Handler2: 7FECBE40\n 1XHEXCPCODE InaccessibleAddress: 00000020\n NULL\n 1XHEXCPMODULE Module: C:\\Program\n Files\\lotus\\notes\\framework\\rcp\\eclipse\\plugins\\com.ibm.rcp.base\n _6.2.2.20111108-2230\\win32\\x86\\notes2.exe\n 1XHEXCPMODULE Module_base_address: 00000000\n 1XHEXCPMODULE Offset_in_DLL: 00000020\n \n \n 1XMCURTHDINFO Current thread\n NULL ----------------------\n 3XMTHREADINFO \"main\" J9VMThread:0x00210900,\n j9thread_t:0x00B35444, java/lang/Thread:0x00C53A50, state:R,\n prio=6\n 3XMTHREADINFO1 (native thread ID:0x958, native\n priority:0x6, native policy:UNKNOWN)\n 3XMTHREADINFO3 Java callstack:\n 4XESTACKTRACE at\n org/eclipse/swt/internal/win32/OS.CoInternetSetFeatureEnabled(Na\n tive Method)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * This APAR is closed as FIN. We have deferred the fix to a\n future release.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n * This APAR is associated with SPR# DAGL9AD9RZ.\n This APAR is closed as FIN. We have deferred the fix to a\n future release.\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n LO76551\n \n \n * REPORTED COMPONENT NAME\n DOMINO SERVER\n \n \n * REPORTED COMPONENT ID\n 5724E6200\n \n \n * REPORTED RELEASE\n 852\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 2013-08-08\n \n \n * CLOSED DATE\n 2016-08-18\n \n \n * LAST MODIFIED DATE\n 2016-08-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\nAPPLICABLE COMPONENT LEVELS\n * R852 PSN\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1LO76551",
+ "date": "2016-08-18",
+ "productName": "IBM Domino",
+ "productId": "SSKTMJ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1LO76551"
+ }
+ },
+ "swg1LO68156": {
+ "id": "swg1LO68156",
+ "content": "\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as fixed if next.
\n
Error description
\n- \n
- \n \n
Notes Client 8.5.2 is crashing due to JVM on process\nOS.CoInternetSetFeatureEnabled native method\n\nAnalysis\n======\n\nHost Name : 0296COMP202\nUser Name : albadmin\nDate : Wed Aug 07 14:55:27 2013\nWindows Dir : C:\\WINDOWS\nArguments : "C:\\Program Files\\lotus\\notes\\nsd.exe"\n-dumpandkill -termstatus 1 -dlgopts showwait -wctpid 2472\n-wctexitcode 8096 -panicdirect -crashpid 3316 -crashtid 748\n-runtime 300\nNSD Version : 8.5.24.1271 (Release 8.5.2FP4)\nOS Version : Windows/XP 5.1 [32-bit] (Build 2600),\nPlatID=2, Service Pack 2, v.2096 (2 Processors)\nBuild time : Fri Nov 18 03:08:35 2011\nLatest file mod : Thu Sep 29 08:27:40 2011\nNotes Core Version : Release 8.5.2 (32-bit client)\nNotes Standard Version : 8.5.2_20100811.1131\nKeyview Version : 10.8.0.0\n\n\n############################################################\n### thread 9/11: [ NLNOTES: 0cf4: 02ec]\n### FP=0x042ce350, PC=0x77ccfc24, SP=0x042ce2ec\n### stkbase=0x042d0000, total stksize=262144, used stksize=7444\n############################################################\n [ 1] 0x77ccfc24 ntdll.KiFastSystemCallRet+0\n(468,493e0,0,42ce8d8)\n [ 2] 0x77e61d20 kernel32.WaitForSingleObject+18\n(468,493e0,0,42ceaf4)\n@[ 3] 0x6020d66d nnotes.OSRunExternalScript@8+1309 (12c,1)\n@[ 4] 0x6020daef nnotes.FRTerminateWindowsResources+975\n(1,1010,1,0)\n@[ 5] 0x6020df18 nnotes.OSFaultCleanupExt@24+984\n(1046a68,1010,0,0,0,42cee1c)\n@[ 6] 0x6020df9a nnotes.OSFaultCleanup@12+26 (0,1010,0)\n@[ 7] 0x60219844 nnotes.OSNTUnhandledExceptionFilter@4+276\n(42cfe54)\n@[ 8] 0x601daf5d nnotes.Panic@4+589 (42cfe6c)\n@[ 9] 0x601db034 nnotes.OSWCTPanicShutdown+84\n(9a8,1fa0,1732ee8,17357f0)\n@[10] 0x636bf3cc nnotesws.WCTShutdownThread+220\n(9a8,138200,77cd1c91,0)\n@[11] 0x6015584f nnotes.ThreadWrapper@4+175 (0)\n [12] 0x77e7344a kernel32.ExitThread+1643 (0,0,0,0)\n\n Start Time = 08/07/2013 02:55:09 PM\n Crash Time = 08/07/2013 02:55:27 PM\n Console Log Enabled = 1\n Console Position = 503\n Error Message = PANIC: The notes2 process (pid=2472) exited\nunexpectedly.\n\nNULL\n----------------------------------------------------------------\n--------\n0SECTION TITLE subcomponent dump routine\nNULL ===============================\n1TISIGINFO Dump Event "gpf" (00002000) received\n1TIDATETIME Date: 2013/08/07 at 16:30:27\nNULL\n----------------------------------------------------------------\n--------\n1XHEXCPCODE J9Generic_Signal_Number: 00000004\n1XHEXCPCODE ExceptionCode: C0000005\n1XHEXCPCODE ExceptionAddress: 00000020\n1XHEXCPCODE ContextFlags: 0001003F\n1XHEXCPCODE Handler1: 7FEFA090\n1XHEXCPCODE Handler2: 7FECBE40\n1XHEXCPCODE InaccessibleAddress: 00000020\nNULL\n1XHEXCPMODULE Module: C:\\Program\nFiles\\lotus\\notes\\framework\\rcp\\eclipse\\plugins\\com.ibm.rcp.base\n_6.2.2.20111108-2230\\win32\\x86\\notes2.exe\n1XHEXCPMODULE Module_base_address: 00000000\n1XHEXCPMODULE Offset_in_DLL: 00000020\n\n\n 1XMCURTHDINFO Current thread\nNULL ----------------------\n3XMTHREADINFO "main" J9VMThread:0x00210900,\nj9thread_t:0x00B35444, java/lang/Thread:0x00C53A50, state:R,\nprio=6\n3XMTHREADINFO1 (native thread ID:0x958, native\npriority:0x6, native policy:UNKNOWN)\n3XMTHREADINFO3 Java callstack:\n4XESTACKTRACE at\norg/eclipse/swt/internal/win32/OS.CoInternetSetFeatureEnabled(Na\ntive Method)\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
This APAR is closed as FIN. We have deferred the fix to a\n future release.\n
\n \n
Problem conclusion
\n- \n
Temporary fix
\n- \n
Comments
\n- \n
- \n \n
This APAR is associated with SPR# DAGL9AD9RZ.\nThis APAR is closed as FIN. We have deferred the fix to a\n future release.\n
\n \n
APAR Information
\n \n
\n - \n
APAR number
LO76551
\n Reported component name
DOMINO SERVER
\n Reported component ID
5724E6200
\n Reported release
852
\n Status
CLOSED FIN
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt / Xsystem
\n Submitted date
2013-08-08
\n Closed date
2016-08-18
\n Last modified date
2016-08-18
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
R852 PSN
UP
\n
\n
\n
\n
",
+ "title": "IBM LO68156: NOTES2.EXE EXITED UNEXPECTEDLY IN J9JIT24.DLL - United States",
+ "text": " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS RETURNED (APAR CANNOT BE RESOLVED WITHOUT ADDITIONAL INFO FROM IBM OR CUSTOMER.)\n \n \n \n\nERROR DESCRIPTION\n * Notes2.exe of a specific PC crashed repeatedly in j9jit24.dll.\n The steps to reproduce is unknown.\n \n Java Core\n \n 0SECTION GPINFO subcomponent dump routine\n NULL ================================\n 2XHOSLEVEL OS Level : Windows 7 6.1 build 7601\n Service Pack 1\n 2XHCPUS Processors -\n 3XHCPUARCH Architecture : x86\n 3XHNUMCPUS How Many : 4\n 3XHNUMASUP NUMA is either not supported or has been\n disabled by user\n NULL\n 1XHEXCPCODE J9Generic_Signal_Number: 00000004\n 1XHEXCPCODE ExceptionCode: C0000005\n 1XHEXCPCODE ExceptionAddress: 7F824310\n 1XHEXCPCODE ContextFlags: 0001007F\n 1XHEXCPCODE Handler1: 7FEFA090\n 1XHEXCPCODE Handler2: 7FECBE40\n 1XHEXCPCODE InaccessibleAddress: 00000010\n NULL\n 1XHEXCPMODULE Module: C:\\Program\n Files\\IBM\\Lotus\\Notes\\jvm\\bin\\j9jit24.dll\n 1XHEXCPMODULE Module_base_address: 7F820000\n 1XHEXCPMODULE Offset_in_DLL: 00004310\n NULL\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n * This APAR is associated with SPR# ANIA8SFHPY.\n The record was returned to the person who created it for more\n information.\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n LO68156\n \n \n * REPORTED COMPONENT NAME\n NOTES CLIENT\n \n \n * REPORTED COMPONENT ID\n 5724E6255\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED RET\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 2012-03-16\n \n \n * CLOSED DATE\n 2012-07-11\n \n \n * LAST MODIFIED DATE\n 2012-07-11\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",
+ "metadata": {
+ "sourceDocumentId": "swg1LO68156",
+ "date": "2012-07-11",
+ "productName": "IBM Notes",
+ "productId": "SSKTWP",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1LO68156"
+ }
+ },
+ "swg22009907": {
+ "id": "swg22009907",
+ "content": "\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)
\n
Error description
\n- \n
- \n \n
Notes2.exe of a specific PC crashed repeatedly in j9jit24.dll.\nThe steps to reproduce is unknown.\n\nJava Core\n\n0SECTION GPINFO subcomponent dump routine\nNULL ================================\n2XHOSLEVEL OS Level : Windows 7 6.1 build 7601\nService Pack 1\n2XHCPUS Processors -\n3XHCPUARCH Architecture : x86\n3XHNUMCPUS How Many : 4\n3XHNUMASUP NUMA is either not supported or has been\ndisabled by user\nNULL\n1XHEXCPCODE J9Generic_Signal_Number: 00000004\n1XHEXCPCODE ExceptionCode: C0000005\n1XHEXCPCODE ExceptionAddress: 7F824310\n1XHEXCPCODE ContextFlags: 0001007F\n1XHEXCPCODE Handler1: 7FEFA090\n1XHEXCPCODE Handler2: 7FECBE40\n1XHEXCPCODE InaccessibleAddress: 00000010\nNULL\n1XHEXCPMODULE Module: C:\\Program\nFiles\\IBM\\Lotus\\Notes\\jvm\\bin\\j9jit24.dll\n1XHEXCPMODULE Module_base_address: 7F820000\n1XHEXCPMODULE Offset_in_DLL: 00004310\nNULL\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
Problem conclusion
\n- \n
Temporary fix
\n- \n
Comments
\n- \n
- \n \n
This APAR is associated with SPR# ANIA8SFHPY.\nThe record was returned to the person who created it for more\n information.\n
\n \n
APAR Information
\n \n
\n - \n
APAR number
LO68156
\n Reported component name
NOTES CLIENT
\n Reported component ID
5724E6255
\n Reported release
850
\n Status
CLOSED RET
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2012-03-16
\n Closed date
2012-07-11
\n Last modified date
2012-07-11
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
\n
\n
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n \n\n
Question
\nA failover occurred in a N3001-001 and I need to confirm the status of the virtual SPU's
\nCause
\n\n
\n After a host fail over how NPS became un-reachable to users
\nAnswer
\n\n
\n \n
Please run the nzvm command as root as shown below. The output should show the current status
of the virtual spu's
root@minimako-host2 ~]# /nz/kit/bin/adm/nzvm status
WARNING: Waiting for the permission to go
spu0101 on ha1 [Running]
spu0101 disks (33) [OK]
spu0102 on ha2 [Running]
spu0102 disks (33) [OK]
Export HA1->HA2 (16/16) [OK]
Export HA2->HA1 (16/16) [OK]
\n \n
\n ",
+ "title": "IBM How to verify the status of virtual SPU's in N3001-001 (Mako Lite) - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n A failover occurred in a N3001-001 and I need to confirm the status of the virtual SPU's \n\nCAUSE\nAfter a host fail over how NPS became un-reachable to users\n\nANSWER\n \n\nPlease run the nzvm command as root as shown below. The output should show the current status \nof the virtual spu's\n\nroot@minimako-host2 ~]# /nz/kit/bin/adm/nzvm status\nWARNING: Waiting for the permission to go\nspu0101 on ha1 [Running]\nspu0101 disks (33) [OK]\nspu0102 on ha2 [Running]\nspu0102 disks (33) [OK]\nExport HA1->HA2 (16/16) [OK]\nExport HA2->HA1 (16/16) [OK]",
+ "metadata": {
+ "sourceDocumentId": "swg22009907",
+ "date": "2017-10-23",
+ "productName": "PureData System for Analytics",
+ "productId": "SSULQD",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg22009907"
+ }
+ },
+ "swg27036220": {
+ "id": "swg27036220",
+ "content": "
\n
",
+ "title": "IBM Cognos Disclosure Management Version 10.2: Installation requirements - United States",
+ "text": " PRODUCT DOCUMENTATION\n\nABSTRACT\n This document provides further information on client requirements, application server requirements, and database server requirements for installing Cognos Disclosure Management. \n\nCONTENT\nThe Cognos Disclosure Management client\n\n\nClient computers for IBM Cognos Disclosure Management must meet operating system, software, hardware, and access requirements. \n\nOperating system requirements for the Cognos Disclosure Management client \n\nAt a minimum, each computer where the client is installed must be using Microsoft Windows XP Professional operating system with Service Pack 2, or later, installed. However, Windows 7 64-bit is the recommended operating system. \n\nThe Cognos Disclosure Management client can be installed on 32-bit or 64-bit operating systems. \n\nSoftware requirements for the Cognos Disclosure Management client \n\nEnsure that the computer on which you install a client meets the following software requirements: \n\n * Microsoft Office 2003 with the Microsoft Office Compatibility Pack, Microsoft Office 2007, and Microsoft Office 2010 are supported in their native mode. If an object is created in a later version of Microsoft Office, and a user with an earlier version opens the object, the object opens in Program Compatibility mode\n\n\nImportant: It is recommended that all users run the same Windows and Microsoft Office platforms, including the latest service packs. If some users use different versions of Microsoft Office, users of Microsoft Office 2003 must install the Office Compatibility Pack. \n\nNormal font style and size should be consistent across end-user client computers. It is recommended that all users apply the same screen resolution and default font size for Microsoft Excel, Microsoft Word and Microsoft PowerPoint. These settings should remain consistent across all end-user client computers. \n * Microsoft .NET Framework 4 \n * Adobe Reader Version 9 or Adobe Acrobat Version 9, or later, must be installed\n\n\nOptional software installations for the Cognos Disclosure Management client \n\nYou can install the following compatible software: \n * IBM Cognos TM1 10.1.1 (the TM1 Perspectives add-in for Microsoft Excel) \n * IBM Cognos for Microsoft Office 10.1.1 \n * IBM Cognos Analysis for Microsoft Excel 10.1.1 \n * IBM Cognos Controller (the add-in for Microsoft Excel) \n * Oracle Hyperion Financial Management (HFM) Smart View Runtime Client\n\n\nImportant: Ensure that port 443 is used for communication between the Cognos Disclosure Management client and the Cognos Disclosure Management server. \n\nHardware requirements for the Cognos Disclosure Management client \n\nThere are different hardware requirements for different operating systems. \n\nWindows 7 \n * At least 10 GB of free disk space \n * A minimum of 2 CPU is required, but 4 CPU is recommended \n * A minimum of 4 GB RAM is required \n * A minimum processor speed of 2.4 GHz is required\n\n\nWindows XP * At least 10 GB of free disk space \n * A minimum of 1 CPU is required, but 2 CPU is recommended \n * A minimum of 2 GB RAM is required, but 3 GB RAM is recommended \n * A minimum processor speed of 2.4 GHz is required\n\n\nImportant: A gigabyte internet card (and LAN connection) needs to exist between the application and database servers. \n\nCognos Disclosure Management application server and database requirements \n\nEnsure that your application server and database meet the operating system and software requirements. The Cognos Disclosure Management database will be created during the server installation. \n\nOperating system requirements for the application server \n\nThe application server must be running the 64-bit Microsoft Windows Server 2003 operating system, or later. Windows Server 2008 R2 is recommended. \n\nYou cannot install the Cognos Disclosure Management server on a 32-bit computer. \n\nHardware requirements for the application and database server \n\nEnsure that the computer on which you install the server components meets the following hardware requirements: \n * A minimum of 4 CPU cores \n * A minimum of 8 GB RAM \n * A minimum processor speed of 2.4GHz\n\n\nSoftware requirements for the application server \n\nEnsure that the computer on which you install the server components meets the following software requirements: \n * Microsoft Internet Information Services (IIS) Version 6.0, or later, must be installed and running \n * Microsoft .NET Framework 4 software must be installed \n * Microsoft Visual C++ 2008 SP1 Redistributable Package. If this is not already installed, the installation wizard will download and install the package \n * Microsoft Visual C++ 2010 Redistributable Package. If this is not already installed, the installation wizard will download and install the package\n\n\nData source connectivity requirements for the application server \n * If you have installed TM1 Perspectives, you will require the TM1 Runtime client 64-bit, Version 10.1 \n * Microsoft Analysis Services ADOMD.NET 2005 or 2008 \n * If you use Oracle Essbase software, connectivity and installation of the correct Oracle Essbase Runtime client software is required: * Oracle Instant Client Oracle Data Provider for .NET \n \n \n * The DB2 relational source requires installation of the DB2 ADO.NET client Runtime component \n * TCP/IP connectivity with OLAP database environment, if applicable \n * TCP/IP connectivity to the Cognos Disclosure Management database server\n\n\nSSL certificate requirement for the application server \n\nCognos Disclosure Management requires the secure sockets layer (SSL) to be enabled on your web/application server. Ensure that you have acquired a SSL certificate from a recognized certificate authority. \n\nDatabase server requirements \n\nMicrosoft SQL Server 2005 or 2008. Microsoft SQL Server 2008 is recommended. The SQL Server edition should be Standard or Enterprise. SQL Server can be either 32-bit or 64-bit. \n\nYou must use the 64-bit version of the Microsoft SQL Server Native Client. The 64-bit native client works with both the 32-bit and 64-bit versions of Microsoft SQL Server. \n\nFor your database, 50 GB free disk space is recommended for future database growth. This does not take into account other databases and their respective growth. \n\nCITRIX server requirements \n\nIf you are using a CITRIX server, ensure it meets the software and hardware requirements described below. \n\nSoftware requirements for the CITRIX server \n\nEnsure that the computer on which you install the CITRIX server meets the following software requirements: \n * CITRIX XenApp Versions 4.5, 5.0, 5.5, 6 or 6.5 \n * Windows Server 2003, or later. Windows Server 2008 R2 is recommended \n * Microsoft .NET Framework 4 software must be installed \n * Adobe Reader Version 9 or Adobe Acrobat Version 9, or later, must be installed \n * IBM Cognos TM1 10.1.1 (the TM1 Perspectives add-in for Microsoft Excel) \n * IBM Cognos for Microsoft Office 10.1.1 \n * IBM Cognos Analysis for Microsoft Excel 10.1.1 \n * IBM Cognos Controller (the add-in for Microsoft Excel)\n\n\nHardware requirements for the CITRIX server \n\nEnsure that the computer on which you install the CITRIX server meets the following hardware requirements: \n * At least 10 GB of free disk space, but 15 GB of free disk space is recommended for temporary files \n * A minimum of 4 CPU is required, but 8 CPU is recommended \n * A minimum of 8 GB RAM is required, but 16 GB RAM is recommended \n * A minimum processor speed of 2.4 GHz is required",
+ "metadata": {
+ "sourceDocumentId": "swg27036220",
+ "date": "2012-11-30",
+ "productName": "Cognos Disclosure Management",
+ "productId": "SSQK59",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg27036220"
+ }
+ },
+ "swg1IV47288": {
+ "id": "swg1IV47288",
+ "content": "\n\n
\n\n \n \n
\nProduct documentation
\n \n
\n
\n
\n \n
Abstract
\nThis document provides further information on client requirements, application server requirements, and database server requirements for installing Cognos Disclosure Management.
\nContent
\n\n
\n Important: It is recommended that all users run the same Windows and Microsoft Office platforms, including the latest service packs. If some users use different versions of Microsoft Office, users of Microsoft Office 2003 must install the Office Compatibility Pack.\n
\n
Normal font style and size should be consistent across end-user client computers. It is recommended that all users apply the same screen resolution and default font size for Microsoft Excel, Microsoft Word and Microsoft PowerPoint. These settings should remain consistent across all end-user client computers.\n
\n
\n Optional software installations for the Cognos Disclosure Management client\n
\n
You can install the following compatible software:\n
\n
\n Important: Ensure that port 443 is used for communication between the Cognos Disclosure Management client and the Cognos Disclosure Management server.\n
\n
\n Hardware requirements for the Cognos Disclosure Management client\n
\n
There are different hardware requirements for different operating systems.\n
\n
\n Windows 7\n
\n
\n Windows XP \n
\n Important: A gigabyte internet card (and LAN connection) needs to exist between the application and database servers.\n
\n
\n Cognos Disclosure Management application server and database requirements\n
\n
Ensure that your application server and database meet the operating system and software requirements. The Cognos Disclosure Management database will be created during the server installation.\n
\n
\n Operating system requirements for the application server\n
\n
The application server must be running the 64-bit Microsoft Windows Server 2003 operating system, or later. Windows Server 2008 R2 is recommended.\n
\n
You cannot install the Cognos Disclosure Management server on a 32-bit computer.\n
\n
\n Hardware requirements for the application and database server\n
\n
Ensure that the computer on which you install the server components meets the following hardware requirements:\n
\n
\n Software requirements for the application server\n
\n
Ensure that the computer on which you install the server components meets the following software requirements:\n
\n
\n Data source connectivity requirements for the application server\n
\n
\n SSL certificate requirement for the application server\n
\n
Cognos Disclosure Management requires the secure sockets layer (SSL) to be enabled on your web/application server. Ensure that you have acquired a SSL certificate from a recognized certificate authority.\n
\n
\n Database server requirements\n
\n
Microsoft SQL Server 2005 or 2008. Microsoft SQL Server 2008 is recommended. The SQL Server edition should be Standard or Enterprise. SQL Server can be either 32-bit or 64-bit. \n
\n
You must use the 64-bit version of the Microsoft SQL Server Native Client. The 64-bit native client works with both the 32-bit and 64-bit versions of Microsoft SQL Server.\n
\n
For your database, 50 GB free disk space is recommended for future database growth. This does not take into account other databases and their respective growth.\n
\n
\n CITRIX server requirements\n
\n
If you are using a CITRIX server, ensure it meets the software and hardware requirements described below.\n
\n
\n Software requirements for the CITRIX server\n
\n
Ensure that the computer on which you install the CITRIX server meets the following software requirements:\n
\n
\n Hardware \n requirements for the CITRIX server\n
\n
Ensure that the computer on which you install the CITRIX server meets the following hardware requirements:\n
\n
\n The Cognos Disclosure Management client
Client computers for IBM Cognos Disclosure Management must meet operating system, software, hardware, and access requirements.
\nOperating system requirements for the Cognos Disclosure Management client
\nAt a minimum, each computer where the client is installed must be using Microsoft Windows XP Professional operating system with Service Pack 2, or later, installed. However, Windows 7 64-bit is the recommended operating system.
\nThe Cognos Disclosure Management client can be installed on 32-bit or 64-bit operating systems.
\nSoftware requirements for the Cognos Disclosure Management client
\nEnsure that the computer on which you install a client meets the following software requirements:
\n- \n
- Microsoft Office 2003 with the Microsoft Office Compatibility Pack, Microsoft Office 2007, and Microsoft Office 2010 are supported in their native mode. If an object is created in a later version of Microsoft Office, and a user with an earlier version opens the object, the object opens in Program Compatibility mode \n
\n Important: It is recommended that all users run the same Windows and Microsoft Office platforms, including the latest service packs. If some users use different versions of Microsoft Office, users of Microsoft Office 2003 must install the Office Compatibility Pack.\n
\n
Normal font style and size should be consistent across end-user client computers. It is recommended that all users apply the same screen resolution and default font size for Microsoft Excel, Microsoft Word and Microsoft PowerPoint. These settings should remain consistent across all end-user client computers.\n
\n
- \n
- Microsoft .NET Framework 4 \n
- Adobe Reader Version 9 or Adobe Acrobat Version 9, or later, must be installed \n
\n Optional software installations for the Cognos Disclosure Management client\n
\n
You can install the following compatible software:\n
\n
- \n
- IBM Cognos TM1 10.1.1 (the TM1 Perspectives add-in for Microsoft Excel) \n
- IBM Cognos for Microsoft Office 10.1.1 \n
- IBM Cognos Analysis for Microsoft Excel 10.1.1 \n
- IBM Cognos Controller (the add-in for Microsoft Excel) \n
- Oracle Hyperion Financial Management (HFM) Smart View Runtime Client \n
\n Important: Ensure that port 443 is used for communication between the Cognos Disclosure Management client and the Cognos Disclosure Management server.\n
\n
\n Hardware requirements for the Cognos Disclosure Management client\n
\n
There are different hardware requirements for different operating systems.\n
\n
\n Windows 7\n
\n
- \n
- At least 10 GB of free disk space \n
- A minimum of 2 CPU is required, but 4 CPU is recommended \n
- A minimum of 4 GB RAM is required \n
- A minimum processor speed of 2.4 GHz is required \n
\n Windows XP \n
- \n
- At least 10 GB of free disk space \n
- A minimum of 1 CPU is required, but 2 CPU is recommended \n
- A minimum of 2 GB RAM is required, but 3 GB RAM is recommended \n
- A minimum processor speed of 2.4 GHz is required \n
\n Important: A gigabyte internet card (and LAN connection) needs to exist between the application and database servers.\n
\n
\n Cognos Disclosure Management application server and database requirements\n
\n
Ensure that your application server and database meet the operating system and software requirements. The Cognos Disclosure Management database will be created during the server installation.\n
\n
\n Operating system requirements for the application server\n
\n
The application server must be running the 64-bit Microsoft Windows Server 2003 operating system, or later. Windows Server 2008 R2 is recommended.\n
\n
You cannot install the Cognos Disclosure Management server on a 32-bit computer.\n
\n
\n Hardware requirements for the application and database server\n
\n
Ensure that the computer on which you install the server components meets the following hardware requirements:\n
\n
- \n
- A minimum of 4 CPU cores \n
- A minimum of 8 GB RAM \n
- A minimum processor speed of 2.4GHz \n
\n Software requirements for the application server\n
\n
Ensure that the computer on which you install the server components meets the following software requirements:\n
\n
- \n
- Microsoft Internet Information Services (IIS) Version 6.0, or later, must be installed and running \n
- Microsoft .NET Framework 4 software must be installed \n
- Microsoft Visual C++ 2008 SP1 Redistributable Package. If this is not already installed, the installation wizard will download and install the package \n
- Microsoft Visual C++ 2010 Redistributable Package. If this is not already installed, the installation wizard will download and install the package \n
\n Data source connectivity requirements for the application server\n
\n
- \n
- If you have installed TM1 Perspectives, you will require the TM1 Runtime client 64-bit, Version 10.1 \n
- Microsoft Analysis Services ADOMD.NET 2005 or 2008 \n
- If you use Oracle Essbase software, connectivity and installation of the correct Oracle Essbase Runtime client software is required: \n
- \n
- Oracle Instant Client \n
- Oracle Data Provider for .NET \n
- \n
\n - The DB2 relational source requires installation of the DB2 ADO.NET client Runtime component \n
- TCP/IP connectivity with OLAP database environment, if applicable \n
- TCP/IP connectivity to the Cognos Disclosure Management database server \n
\n SSL certificate requirement for the application server\n
\n
Cognos Disclosure Management requires the secure sockets layer (SSL) to be enabled on your web/application server. Ensure that you have acquired a SSL certificate from a recognized certificate authority.\n
\n
\n Database server requirements\n
\n
Microsoft SQL Server 2005 or 2008. Microsoft SQL Server 2008 is recommended. The SQL Server edition should be Standard or Enterprise. SQL Server can be either 32-bit or 64-bit. \n
\n
You must use the 64-bit version of the Microsoft SQL Server Native Client. The 64-bit native client works with both the 32-bit and 64-bit versions of Microsoft SQL Server.\n
\n
For your database, 50 GB free disk space is recommended for future database growth. This does not take into account other databases and their respective growth.\n
\n
\n CITRIX server requirements\n
\n
If you are using a CITRIX server, ensure it meets the software and hardware requirements described below.\n
\n
\n Software requirements for the CITRIX server\n
\n
Ensure that the computer on which you install the CITRIX server meets the following software requirements:\n
\n
- \n
- CITRIX XenApp Versions 4.5, 5.0, 5.5, 6 or 6.5 \n
- Windows Server 2003, or later. Windows Server 2008 R2 is recommended \n
- Microsoft .NET Framework 4 software must be installed \n
- Adobe Reader Version 9 or Adobe Acrobat Version 9, or later, must be installed \n
- IBM Cognos TM1 10.1.1 (the TM1 Perspectives add-in for Microsoft Excel) \n
- IBM Cognos for Microsoft Office 10.1.1 \n
- IBM Cognos Analysis for Microsoft Excel 10.1.1 \n
- IBM Cognos Controller (the add-in for Microsoft Excel) \n
\n Hardware \n requirements for the CITRIX server\n
\n
Ensure that the computer on which you install the CITRIX server meets the following hardware requirements:\n
\n
- \n
- At least 10 GB of free disk space, but 15 GB of free disk space is recommended for temporary files \n
- A minimum of 4 CPU is required, but 8 CPU is recommended \n
- A minimum of 8 GB RAM is required, but 16 GB RAM is recommended \n
- A minimum processor speed of 2.4 GHz is required \n
\n
\n \n
\n \n
\n \n
\n \n \n\n
",
+ "title": "IBM IV47288: SERVICE PROVIDER SCRIPT 7110_118 NEEDS TO CHECK FOR AN EXISTING MENU OPTION BEFORE THE INSERT. - United States",
+ "text": " 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 * Error during Service Provider Upgrade\n \n \n -- Product: IBM Maximo for Service Providers script updatedb\n process\n starts...\n -- Calling the class :\n psdi.serviceprovider.en.V7110_118 Thu Jan 10 00:53:21 EST 2013\n --\n ----------------------------------------------------------------\n ---\n insert into maxmenu (menutype, moduleapp, elementtype,\n keyvalue,\n position, subposition, tabdisplay, maxmenuid, visible) values\n ('APPMENU','PLUSPWO','OPTION','VIEWSTHIST',112,70,'MAIN',\n nextval for\n maxmenuseq, 1);\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\n One or\n more values in the INSERT statement, UPDATE statement, or\n foreign key\n update caused by a DELETE statement are not valid because the\n primary\n key, unique constraint or unique index identified by \"2\"\n constrains\n table \"MAXIMO.MAXMENU\" from having duplicate values for the\n index key..\n \n \n Error:\n \n -- Product: IBM Maximo for Service Providers\n -- Error running file: V7110_118\n -- UPDATEDBFILE:V7110_118.class\n -- Script: Error\n java.lang.Exception: One or more values in the INSERT\n statement,\n UPDATE statement, or foreign key update caused by a DELETE\n statement are\n not valid because the primary key, unique constraint or unique\n index\n identified by \"2\" constrains table \"MAXIMO.MAXMENU\" from having\n duplicate values for the index key.. SQLCODE=-803,\n SQLSTATE=23505,\n DRIVER=4.11.69\n at psdi.tools.UpdateDB.runScriptClass(Unknown Source)\n at psdi.tools.UpdateDB.runScripts(Unknown Source)\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.loadScriptInfo(Unknown Source)\n at psdi.tools.UpdateDB.main(Unknown Source)\n \n java.lang.Exception: DATABASE Script UPDATE COMPLETED WITH\n ERROR.\n CHECK ERRORS IN UPDATE LOG FILE -Updatedb20130109235109.log\n One or more values in the INSERT statement, UPDATE\n statement, or\n foreign key update caused by a DELETE statement are not valid\n because\n the primary key, unique constraint or unique index identified by\n \"2\"\n constrains table \"MAXIMO.MAXMENU\" from having duplicate values\n for the\n index key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.11.69\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.loadScriptInfo(Unknown Source)\n at psdi.tools.UpdateDB.main(Unknown Source)\n \n \n \n \n \n\nLOCAL FIX\n * Delete the existing entry and re-run the updatedb.\n \n \n SQL: delete from maxmenu where menutype='APPMENU' and\n moduleapp='PLUSPWO' and elementtype='OPTION' and\n keyvalue='VIEWSTHIST';\n commit;\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * Service Provider 7.1.1.0 *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * SERVICE PROVIDER SCRIPT 7110_118 NEEDS TO CHECK FOR AN *\n * EXISTINGMENU OPTION BEFORE THE INSERT. *\n ****************************************************************\n * RECOMMENDATION: *\n * No *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * It happens to a low number of customer.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV47288\n \n \n * REPORTED COMPONENT NAME\n SERVICE PROVIDE\n \n \n * REPORTED COMPONENT ID\n 5724R46SV\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\n \n \n * SUBMITTED DATE\n 2013-08-20\n \n \n * CLOSED DATE\n 2013-08-22\n \n \n * LAST MODIFIED DATE\n 2013-08-22\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 SERVICE PROVIDE\n \n \n * FIXED COMPONENT ID\n 5724R46SV\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R711 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1IV47288",
+ "date": "2013-08-22",
+ "productName": "Maximo Asset Management",
+ "productId": "SSLKT6",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1IV47288"
+ }
+ },
+ "swg21276540": {
+ "id": "swg21276540",
+ "content": "\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
Error during Service Provider Upgrade\n\n\n -- Product: IBM Maximo for Service Providers script updatedb\nprocess\nstarts...\n -- Calling the class :\npsdi.serviceprovider.en.V7110_118 Thu Jan 10 00:53:21 EST 2013\n --\n----------------------------------------------------------------\n---\n insert into maxmenu (menutype, moduleapp, elementtype,\nkeyvalue,\nposition, subposition, tabdisplay, maxmenuid, visible) values\n('APPMENU','PLUSPWO','OPTION','VIEWSTHIST',112,70,'MAIN',\nnextval for\nmaxmenuseq, 1);\n com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:\nOne or\nmore values in the INSERT statement, UPDATE statement, or\nforeign key\nupdate caused by a DELETE statement are not valid because the\nprimary\nkey, unique constraint or unique index identified by "2"\nconstrains\ntable "MAXIMO.MAXMENU" from having duplicate values for the\nindex key..\n\n\nError:\n\n -- Product: IBM Maximo for Service Providers\n -- Error running file: V7110_118\n -- UPDATEDBFILE:V7110_118.class\n -- Script: Error\n java.lang.Exception: One or more values in the INSERT\nstatement,\nUPDATE statement, or foreign key update caused by a DELETE\nstatement are\nnot valid because the primary key, unique constraint or unique\nindex\nidentified by "2" constrains table "MAXIMO.MAXMENU" from having\nduplicate values for the index key.. SQLCODE=-803,\nSQLSTATE=23505,\nDRIVER=4.11.69\n at psdi.tools.UpdateDB.runScriptClass(Unknown Source)\n at psdi.tools.UpdateDB.runScripts(Unknown Source)\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.loadScriptInfo(Unknown Source)\n at psdi.tools.UpdateDB.main(Unknown Source)\n\n java.lang.Exception: DATABASE Script UPDATE COMPLETED WITH\nERROR.\nCHECK ERRORS IN UPDATE LOG FILE -Updatedb20130109235109.log\n One or more values in the INSERT statement, UPDATE\nstatement, or\nforeign key update caused by a DELETE statement are not valid\nbecause\nthe primary key, unique constraint or unique index identified by\n"2"\nconstrains table "MAXIMO.MAXMENU" from having duplicate values\nfor the\nindex key.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.11.69\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.startProcess(Unknown Source)\n at psdi.tools.UpdateDB.loadScriptInfo(Unknown Source)\n at psdi.tools.UpdateDB.main(Unknown Source)\n\n \n
Local fix
\n- \n
- \n \n
Delete the existing entry and re-run the updatedb.\n\n\n SQL: delete from maxmenu where menutype='APPMENU' and\nmoduleapp='PLUSPWO' and elementtype='OPTION' and\nkeyvalue='VIEWSTHIST';\ncommit;\n
\n \n
Problem summary
\n- \n
- \n \n
****************************************************************\n* USERS AFFECTED: *\n* Service Provider 7.1.1.0 *\n****************************************************************\n* PROBLEM DESCRIPTION: *\n* SERVICE PROVIDER SCRIPT 7110_118 NEEDS TO CHECK FOR AN *\n* EXISTINGMENU OPTION BEFORE THE INSERT. *\n****************************************************************\n* RECOMMENDATION: *\n* No *\n****************************************************************\n
\n \n
Problem conclusion
\n- \n
- \n \n
It happens to a low number of customer.\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
IV47288
\n Reported component name
SERVICE PROVIDE
\n Reported component ID
5724R46SV
\n Reported release
711
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2013-08-20
\n Closed date
2013-08-22
\n Last modified date
2013-08-22
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
SERVICE PROVIDE
\n Fixed component ID
5724R46SV
\n
Applicable component levels
\n- \n
R711 PSY
UP
\n
\n
\n
\n
",
+ "title": "IBM HPII Err <0,0,1026>- Can't execute cmd 'move \\Y D:\\fnsw_loc\\bin\\20050110fn.e - United States",
+ "text": "PANAGON IDM IMAGE SERVICES TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n HPII Err <0,0,1026>- Can't execute cmd 'move \\Y D:\\fnsw_loc\\bin\\20050110fn.e \n\nRESOLVING THE PROBLEM\nHPII Err <0,0,1026>\n- Can't execute cmd 'move \\Y D:\\fnsw_loc\\bin\\20050110fn.eod i:\\eob > null:'\n- HPII Error document does not contain any page. This resolution applies to all versions of HPII and Microsoft SQL on a Windows 2000 environment.\n\nHPII would not process any jobs. Error 0,0,126 in HPII imp file.\n\n2005/01/11 01:00:14 \n\n
\nPANAGON IDM IMAGE SERVICES
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n \n \n\n
Problem(Abstract)
\nHPII Err <0,0,1026>- Can't execute cmd 'move \\Y D:\\fnsw_loc\\bin\\20050110fn.e
\nResolving the problem
\n\n
\n HPII Err <0,0,1026>
- Can't execute cmd 'move \\Y D:\\fnsw_loc\\bin\\20050110fn.eod i:\\eob > null:'
- HPII Error document does not contain any page. This resolution applies to all versions of HPII and Microsoft SQL on a Windows 2000 environment.
HPII would not process any jobs. Error 0,0,126 in HPII imp file.
2005/01/11 01:00:14 <fnsw> (003916)
Terminate received. Waiting for active children to finish
--- 2005/01/11 01:00:14 <fnsw> (003916) Err <0,0,1026>
- Can't execute cmd 'move \\Y D:\\fnsw_loc\\bin\\20050110fn.eod i:\\eob > null:'
- HPII Err: Can't exec command
When analyzing the IMS error logs the following error is listed.
2005/01/11 04:36:57.671 121,7,9002 <fnsw> dtp_tran (2288.3108.85 0x8f0.c24) ... [OPERATOR INTERVENTION]
MS SQL Server Msg No:9002, State:6, Severity:17, Message: The log file for database 'indexdb' is full. Back up the transaction log for the database to free up some log space.
2005/01/11 04:36:57.671 121,7,9002 <fnsw> dtp_tran (2288.3108.85 0x8f0.c24) ...
INX_create: GDB_exec_error on doc_id 20847018
2005/01/11 04:36:57.671 121,7,9002 <fnsw> dtp_tran (2288.3108.85 0x8f0.c24) ...
INSERT INTO doctaba(f_docnumber, f_docclassnumber, f_entrydate, f_lastaccess, f_annotationflag, f_archivedate, f_purgedate, f_deletedate, f_retentbase, f_retentdisp, f_retentoffset, f_pages, f_accessrights, f_doctype, f_docformat, f_doclocation,a40,a33,a3
2005/01/11 04:36:57.671 121,7,9002 <fnsw> dtp_tran (2288.3108.85 0x8f0.c24) ... [OPERATOR INTERVENTION]
MS SQL Server Msg No:9002, State:6, Severity:17, Message: The log file for database 'indexdb' is full. Back up the transaction log for the database to free up some log space.
2005/01/11 04:36:57.686 121,7,9002 <fnsw> dtp_tran (2288.3108.85 0x8f0.c24) ...
INX_create: GDB_exec_error on doc_id 20847019
2005/01/11 04:36:57.686 121,7,9002 <fnsw> dtp_tran (2288.3108.85 0x8f0.c24) ...
INSERT INTO doctaba(f_docnumber, f_docclassnumber, f_entrydate, f_lastaccess, f_annotationflag, f_archivedate, f_purgedate, f_deletedate, f_retentbase, f_retentdisp, f_retentoffset, f_pages, f_accessrights, f_doctype, f_docformat, f_doclocation,a40,a33,a3
2005/01/11 04:36:57.686 121,7,9002 <fnsw> dtp_tran (2288.3108.85 0x8f0.c24) ... [OPERATOR INTERVENTION]
MS SQL Server Msg No:9002, State:6, Severity:17, Message: The log file for database 'indexdb' is full. Back up the transaction log for the database to free up some log space.
============== Problem / Solution:
The problem is with the Miscrosoft SQL database, the transaction log is full. Customer needs to contact Microsoft so they can help the customer truncate the SQL database. After truncating the SQL database, restart HPII and then the jobs will process.
-end
\n \n
\n Historical Number
\n10011491
\nProduct Alias/Synonym
\nIDM SERVICES
\n\n
\n\n\n\n
\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n \n
Problem(Abstract)
\nAfter installing Decision Center and Decision Server, I try to access the Decision Center and Rule Execution Server (RES) consoles, and get a 'Page not found' error
\nResolving the problem
\n\n
\n \n
1. From the application server console, check if the application EAR files for the Decision Center and the RES Management are deployed and have been started.
\n2. From the application server administration console, check the HTTP port number. Make sure you use this port number to access the console. For example, by default, the HTTP port number for WebSphere Application Server is 9080, but it might be configured to 9081 for the profile on which the ODM application is installed.
\n3. Check that the HTTP port is not being used by another process. If it is, stop the other process and try to access the console again.
4. Examine the server logs. If they contain the following exception:
com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E:
[Servlet Error]-[/moduleVersion/versioninfo.jsp]:
com.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E: Exception
caught while translating /moduleVersion/versioninfo.jsp:
java.lang.reflect.InvocationTargetException at
com.ibm.ws.jsp.translator.JspTranslator.processVisitors(JspTranslator.java:139) at
com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJsp(JspTranslatorUtil.java:254) at
com.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJspAndCompile(JspTranslatorUtil.java:121) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:548)
Ensure that the <WAS_install>/temp and <WAS_profile>/temp directories have sufficient read and write privileges for the non-root user. If possible, grant the user full access to the entire application server installation directory. Note that on Windows, you can check if you have the required privileges by right-clicking on the folder, choosing Properties, and going to the Security tab.
Also ensure there are no JSP files which were compiled by another user in the above-mentioned directories.
This error could also be due to the APAR PI09545, in which case apply the appropriate fix.
\n
5. Ensure there are no firewall settings which are preventing access to the Decision Center or Rule Execution Server consoles.
\n6. Ensure that the Class loader order property is set to Classes loaded with local class loader first (parent last), for the ILOG Rule Execution Server Console module of the Rule Execution Server EAR. See Step 17 of the documentation at
Operational Decision Manager V8.5.1 > Configuring > Configuring Operational Decision Manager on WebSphere Application Server > Configuring Rule Execution Server on WebSphere Application Server
7. Ensure that the Class loader order property is set to Classes loaded with local class loader first (parent last), for the teamserver module of the Decision Center EAR. See Step 5 of the documentation at
Operational Decision Manager V8.5.1 > Configuring > Configuring Operational Decision Manager on WebSphere Application Server > Configuring the Decision Center consoles on WebSphere Application Server > Configuring the Decision Center consoles on WebSphere Application Server for distributed platforms > Step 4: Deploying the Decision Center EAR file
8. Examine the server logs (including FFDC logs if working with WebSphere Application Server) and address any additional errors such as authentication errors.
9. After making the above changes, restart the server and try to access the console for the Decision Center and/or the Rule Execution Server again.
\n
\n \n
\n
\n \n \n",
+ "title": "IBM Cannot access Decision Center or Rule Execution Server console (ODM) - United States",
+ "text": " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After installing Decision Center and Decision Server, I try to access the Decision Center and Rule Execution Server (RES) consoles, and get a 'Page not found' error \n\nRESOLVING THE PROBLEM\n \n\n1. From the application server console, check if the application EAR files for the Decision Center and the RES Management are deployed and have been started. \n\n2. From the application server administration console, check the HTTP port number. Make sure you use this port number to access the console. For example, by default, the HTTP port number for WebSphere Application Server is 9080, but it might be configured to 9081 for the profile on which the ODM application is installed. \n\n3. Check that the HTTP port is not being used [http://www.ibm.com/support/docview.wss?uid=swg21264632] by another process. If it is, stop the other process and try to access the console again.\n\n4. Examine the server logs. If they contain the following exception:\n\ncom.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: \n[Servlet Error]-[/moduleVersion/versioninfo.jsp]: \ncom.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E: Exception \ncaught while translating /moduleVersion/versioninfo.jsp: \njava.lang.reflect.InvocationTargetException at \ncom.ibm.ws.jsp.translator.JspTranslator.processVisitors(JspTranslator.java:139) at \ncom.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJsp(JspTranslatorUtil.java:254) at \ncom.ibm.ws.jsp.translator.utils.JspTranslatorUtil.translateJspAndCompile(JspTranslatorUtil.java:121) at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.translateJsp(AbstractJSPExtensionServletWrapper.java:548) \n\nEnsure that the
\n
",
+ "title": "IBM IC60317: DEVICE SERVER FAILS TO START WHEN SHA256 ENCRYPTION IS ACTIVE ON AIX - United States",
+ "text": "AIX 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 * The TPC Device Server will not start when the password\n encryption on AIX is set to use the Secured\n Hash Algorithm with a 256 bit key (SHA256). The failure occurs\n when Websphere attempts to\n authenticate the user and password. A javacore dump occurs\n within the libUnixRegistryImpl.so library for the native call\n ntv_basicAuthenticate. Although the problem occurs within\n Websphere, the changes required to resolve this within Websphere\n need to be included in the installation of TPC\n .\n from javacore:\n \"...\n NULL\n ----------------------------------------------------------------\n --------\n 0SECTION TITLE subcomponent dump routine\n NULL ===============================\n 1TISIGINFO Dump Event \"gpf\" (00002000) received\n 1TIDATETIME Date: 2009/03/04 at 07:41:49\n 1TIFILENAME Javacore filename:\n /opt/IBM/TPC/device/apps/was/profiles/deviceServer/javacore.2009\n 0304.074137.1290454.0003.txt\n NULL\n ----------------------------------------------------------------\n --------\n 0SECTION GPINFO subcomponent dump routine\n NULL ================================\n 2XHOSLEVEL OS Level : AIX 5.3\n 2XHCPUS Processors -\n 3XHCPUARCH Architecture : ppc\n 3XHNUMCPUS How Many : 8\n NULL\n 1XHEXCPCODE J9Generic_Signal_Number: 00000004\n 1XHEXCPCODE Signal_Number: 0000000B\n 1XHEXCPCODE Error_Value: 00000000\n 1XHEXCPCODE Signal_Code: 00000033\n 1XHEXCPCODE Handler1: F0B60A18\n 1XHEXCPCODE Handler2: F0B5BA80\n NULL\n 1XHEXCPMODULE Module:\n /opt/IBM/TPC/device/apps/was/bin/libUnixRegistryImpl.so\n 1XHEXCPMODULE Module_base_address: D0A1D000\n NULL\n \n DB2 Version used for Server: n/a\n The defect is against component: 5608TC300\n Server/Manager build/release: 3.3.x.x\n Agent build/release (TPC-R): n/a\n Server/Manager (OS): AIX 5.1, 5.3, 6.1\n Agent (OS): n/a\n \n \n This problem has also surfaced (with the same javacore for\n DeviceServer's WebSphere Application Server) when trying to log\n into the TPC 4.2.x web GUI, resulting in a generic \"Status: 12\"\n internal error pop up message and the javacore file. Other\n users can still log into the web GUI successfully (after\n restarting the device server) if they have not had a loadable\n password algorithm (LPA) applied to them.\n \n \n \n \n \n\nLOCAL FIX\n * The workaround is to change the password encryption on AIX from\n ssha256 to another encryption algoithm. No loadable password\n algorithm should be used.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * The root cause of this problem is with the WebSphere Application\n Server product. APAR PK83991 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK83991] is tracking it with the WebSphere\n team. Fixes provided for that APAR can be applied to\n TotalStorage Productivity Center when available. TotalStorage\n Productivity Center will pick up the fixes when available in a\n later release.\n \n This problem applies to Tivoli Storage Productivity\n Center 4.2.x and earlier releases. LPA should not be used with\n them.\n \n This problem does not occur with Tivoli Storage Productivity\n Center 5.1 and later.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n * Apply APAR PK83991 [http://www-01.ibm.com/support/docview.wss?uid=swg1PK83991] fix when available.\n Turn off LPA (loadable password algorithm).\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IC60317\n \n \n * REPORTED COMPONENT NAME\n TPC FOR DATA\n \n \n * REPORTED COMPONENT ID\n 5608TC300\n \n \n * REPORTED RELEASE\n 33A\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 2009-03-11\n \n \n * CLOSED DATE\n 2009-04-28\n \n \n * LAST MODIFIED DATE\n 2012-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\n * R33A PSY\n UP\n \n \n * R41A PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1IC60317",
+ "date": "2012-08-24",
+ "productName": "Tivoli Storage Productivity Center for Data",
+ "productId": "SS8JB5",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1IC60317"
+ }
+ },
+ "swg21453711": {
+ "id": "swg21453711",
+ "content": "\n\n
\n
\n
\nAIX
\n\n \n \n
\n \n
\nAPAR status
\n- \n
Closed as fixed if next.
\n
Error description
\n- \n
- \n \n
The TPC Device Server will not start when the password\nencryption on AIX is set to use the Secured\nHash Algorithm with a 256 bit key (SHA256). The failure occurs\nwhen Websphere attempts to\nauthenticate the user and password. A javacore dump occurs\nwithin the libUnixRegistryImpl.so library for the native call\nntv_basicAuthenticate. Although the problem occurs within\nWebsphere, the changes required to resolve this within Websphere\nneed to be included in the installation of TPC\n.\nfrom javacore:\n"...\nNULL\n----------------------------------------------------------------\n--------\n0SECTION TITLE subcomponent dump routine\nNULL ===============================\n1TISIGINFO Dump Event "gpf" (00002000) received\n1TIDATETIME Date: 2009/03/04 at 07:41:49\n1TIFILENAME Javacore filename:\n/opt/IBM/TPC/device/apps/was/profiles/deviceServer/javacore.2009\n0304.074137.1290454.0003.txt\nNULL\n----------------------------------------------------------------\n--------\n0SECTION GPINFO subcomponent dump routine\nNULL ================================\n2XHOSLEVEL OS Level : AIX 5.3\n2XHCPUS Processors -\n3XHCPUARCH Architecture : ppc\n3XHNUMCPUS How Many : 8\nNULL\n1XHEXCPCODE J9Generic_Signal_Number: 00000004\n1XHEXCPCODE Signal_Number: 0000000B\n1XHEXCPCODE Error_Value: 00000000\n1XHEXCPCODE Signal_Code: 00000033\n1XHEXCPCODE Handler1: F0B60A18\n1XHEXCPCODE Handler2: F0B5BA80\nNULL\n1XHEXCPMODULE Module:\n/opt/IBM/TPC/device/apps/was/bin/libUnixRegistryImpl.so\n1XHEXCPMODULE Module_base_address: D0A1D000\nNULL\n\nDB2 Version used for Server: n/a\nThe defect is against component: 5608TC300\nServer/Manager build/release: 3.3.x.x\nAgent build/release (TPC-R): n/a\nServer/Manager (OS): AIX 5.1, 5.3, 6.1\nAgent (OS): n/a\n\n\nThis problem has also surfaced (with the same javacore for\nDeviceServer's WebSphere Application Server) when trying to log\ninto the TPC 4.2.x web GUI, resulting in a generic "Status: 12"\ninternal error pop up message and the javacore file. Other\nusers can still log into the web GUI successfully (after\nrestarting the device server) if they have not had a loadable\npassword algorithm (LPA) applied to them.\n
\n \n
Local fix
\n- \n
- \n \n
The workaround is to change the password encryption on AIX from\nssha256 to another encryption algoithm. No loadable password\nalgorithm should be used.\n
\n \n
Problem summary
\n- \n
- \n \n
The root cause of this problem is with the WebSphere Application\nServer product. APAR PK83991 is tracking it with the WebSphere\nteam. Fixes provided for that APAR can be applied to\nTotalStorage Productivity Center when available. TotalStorage\nProductivity Center will pick up the fixes when available in a\nlater release.\n\nThis problem applies to Tivoli Storage Productivity\nCenter 4.2.x and earlier releases. LPA should not be used with\nthem.\n\nThis problem does not occur with Tivoli Storage Productivity\nCenter 5.1 and later.\n
\n \n
Problem conclusion
\n- \n
Temporary fix
\n- \n
- \n \n
Apply APAR PK83991 fix when available.\nTurn off LPA (loadable password algorithm).\n
\n \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
IC60317
\n Reported component name
TPC FOR DATA
\n Reported component ID
5608TC300
\n Reported release
33A
\n Status
CLOSED FIN
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2009-03-11
\n Closed date
2009-04-28
\n Last modified date
2012-08-24
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
R33A PSY
UP
\n R41A PSY
UP
\n
\n
\n
\n
\n\n\n\n
\nCollect; troubleshooting; data; BIP2066E; deploy; MustGather
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\n WebSphere Message Broker (WMB) and IBM Integration Bus (IIB) will issue a BIP2066E error message on deployment if the execution group fails to respond.
This MustGather document explains how to troubleshoot this problem by yourself, how to generate diagnostic data when the problem is happening, how to collect the available data from your system, and how share that data with IBM support.
Symptom
\n\n
\n Your Integration Node (broker) fails to respond to a deployment request that was issued by using either the WMB/IIB Toolkit, the Explorer plugin, or the mqsideploy command. You might see a deployment hang/timeout, or BIP2066E errors in the message log.
\n\n
Environment
\n\n
\n These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, Solaris or Windows systems.
Return to the WMB / IIB MustGather index for other problems.
Resolving the problem
\n\n
\n
\n
\n
\n
\n \n
\n
\n \n
A BIP2066E message indicates that a response was not received from your execution group within the time period specified in the ConfigurationChangeTimeout parameter. \n
The default setting for deployment timeouts is 5 minutes (300 seconds), so increase this value only if the timeout was manually reduced to a lower value.\n
\n
\n
Many broker commands, including starting, stopping, and creating objects are considered deployment actions. \n
You may see a BIP2066E error in the message log even if you did not use the mqsideploy command.\n
\n
\n
\n
\n
\n A BIP2066E message indicates that a response was not received from your execution group within the time period specified in the ConfigurationChangeTimeout parameter. \n
The default setting for deployment timeouts is 5 minutes (300 seconds), so increase this value only if the timeout was manually reduced to a lower value.\n
\n
\n
Many broker commands, including starting, stopping, and creating objects are considered deployment actions. \n
You may see a BIP2066E error in the message log even if you did not use the mqsideploy command.\n
\n
\n
\n
\n
Does one specific mqsi command timeout, or do multiple mqsi commands timeout?
Do even non-deployment commands, such as mqsilist or mqsiservice, timeout?
Can you re-create the problem from a different deployment method?
- \n
- mqsideploy \n
- Toolkit \n
- Explorer \n
Are messages backing up on any of the SYSTEM.BROKER.* queues?
Do these messages continue to appear when the Broker are stopped?
\n
\n \n
\n
\n \n
\n
\n
\n
\n \n
- \n
- Error logs \n
- \n
- On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.
See: Configuring the syslog daemon \n - On Window systems, the local error log is the Windows Application Event Log. You can find the Event Viewer from the Windows Control Panel.
See: Windows: Viewing the local error log \n
\n - On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.
- Traces
a) In your broker environment, SET or EXPORT the environment variables
\n- \n
- 'MQSI_SHOW_DEPLOY=1' \n
- 'MQSI_DEPLOY_PROGRESS=1' \n
b) Restart the broker components to pick up the change to the environment.
c) Output of command mqsidc
d) Capture a deploy trace \n - General Broker information \n
- \n
- Record the WebSphere Message Broker version, release, and maintenance level.
This can be captured using the command 'mqsiservice -v'. \n - Record the operating system version, release, and maintenance level. \n
- Record the version, release, and maintenance level of any related products and components for the problematic application. \n
- Collect the broker's environment.
\n- \n
- env (UNIX) \n
- set (Windows) \n
\n - Collect the Standard Output/Error logs.
On UNIX and Linux systems, WMB writes information to both 'stdout' and 'stderr' files.
On Window systems, WMB writes information to a 'console.out' file.
These files are located under the Message Broker workpath.
See: Standard System Logs \n
\n - Record the WebSphere Message Broker version, release, and maintenance level.
\n
\n
\n
\n
\n
\n \n
\n
\n \n
\n
\n
\n \n
- \n
- Use IBM Service Request to open or view a problem record with IBM. \n
- Send your data to IBM for further analysis. \n
\n
\n
\n
Please see the IBM Software Support Handbook for more information on working with IBM support.
Related information
\n Deploy trace instructions
submitting documentation to IBM
\n \n
\n Product Alias/Synonym
\nWMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI \n \n
\n",
+ "title": "IBM WMB/IIB MustGather: problems with deployment timeouts - United States",
+ "text": "Collect; troubleshooting; data; BIP2066E; deploy; MustGather TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WebSphere Message Broker (WMB) and IBM Integration Bus (IIB) will issue a BIP2066E error message on deployment if the execution group fails to respond.\n\nThis MustGather document explains how to troubleshoot this problem by yourself, how to generate diagnostic data when the problem is happening, how to collect the available data from your system, and how share that data with IBM support. \n\nSYMPTOM\nYour Integration Node (broker) fails to respond to a deployment request that was issued by using either the WMB/IIB Toolkit, the Explorer plugin, or the mqsideploy command. You might see a deployment hang/timeout, or BIP2066E errors in the message log.\n\n\nENVIRONMENT\nThese instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, Solaris or Windows systems.\nReturn to the WMB / IIB MustGather index [http://www.ibm.com/support/docview.wss?uid=swg21209857] for other problems. \n\nRESOLVING THE PROBLEM\n\n\n\nSTEP 1: SELF-GUIDED TROUBLESHOOTING\n\nA BIP2066E message indicates that a response was not received from your execution group within the time period specified in the ConfigurationChangeTimeout parameter. \nThe default setting for deployment timeouts is 5 minutes (300 seconds), so increase this value only if the timeout was manually reduced to a lower value. \n\n\nMany broker commands, including starting, stopping, and creating objects are considered deployment actions. \nYou may see a BIP2066E error in the message log even if you did not use the mqsideploy command. \n\n\n\nDoes one specific mqsi command timeout, or do multiple mqsi commands timeout?\nDo even non-deployment commands, such as mqsilist or mqsiservice, timeout?\nCan you re-create the problem from a different deployment method? \n\n * mqsideploy\n * Toolkit\n * Explorer\n\nAre messages backing up on any of the SYSTEM.BROKER.* queues?\nDo these messages continue to appear when the Broker are stopped?\n\n\n\n\nSTEP 2: COLLECT DATA\n\n 1. Error logs * On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.\n See: Configuring the syslog daemon [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an04230_.htm]\n * On Window systems, the local error log is the Windows Application Event Log. You can find the Event Viewer from the Windows Control Panel.\n See: Windows: Viewing the local error log [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an04090_.htm]\n \n \n 2. \n 3. Traces \n a) In your broker environment, SET or EXPORT the environment variables \n \n * 'MQSI_SHOW_DEPLOY=1'\n * 'MQSI_DEPLOY_PROGRESS=1'\n \n b) Restart the broker components to pick up the change to the environment.\n c) Output of command mqsidc\n d) Capture a deploy trace [http://www.ibm.com/support/docview.wss?uid=swg21177049]\n \n \n 4. \n 5. General Broker information * Record the WebSphere Message Broker version, release, and maintenance level.\n This can be captured using the command 'mqsiservice -v'.\n * Record the operating system version, release, and maintenance level.\n * Record the version, release, and maintenance level of any related products and components for the problematic application.\n * Collect the broker's environment.\n * env (UNIX)\n * set (Windows)\n \n \n * Collect the Standard Output/Error logs.\n On UNIX and Linux systems, WMB writes information to both 'stdout' and 'stderr' files.\n On Window systems, WMB writes information to a 'console.out' file.\n These files are located under the Message Broker workpath.\n See: Standard System Logs [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/au14165_.htm]\n \n \n\n\n\nSTEP 3: SUBMIT DATA TO IBM\n\n * Use IBM Service Request [http://www.ibm.com/support/servicerequest/] to open or view a problem record with IBM.\n * Send your data to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217] for further analysis.\n\n\n\n\nPlease see the IBM Software Support Handbook [http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html] for more information on working with IBM support.\n\n\n\nBack to top\n\nRELATED INFORMATION\n Deploy trace instructions [http://www.ibm.com/support/docview.wss?uid=swg21177049]\nsubmitting documentation to IBM [http://www.ibm.com/support/docview.wss?uid=swg21392217]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI",
+ "metadata": {
+ "sourceDocumentId": "swg21453711",
+ "date": "2018-05-03",
+ "productName": "IBM Integration Bus",
+ "productId": "SSNQK6",
+ "canonicalUrl": "https://www-304.ibm.com/support/docview.wss?uid=swg21453711"
+ }
+ },
+ "swg24037227": {
+ "id": "swg24037227",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\n
\nDownloadable files
\n \n
\n
\n \n
Abstract
\nThis cumulative fix pack updates Operational Decision Manager V8.0.1 to V8.0.1.2.
\nDownload Description
\n\n
Installing by using IBM Installation Manager: \n
Installing by using the Installation Manager command line: \n
\n Applying the fix pack\n
After you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack. \n
\n
\n Warning: \n
If you have installed interim fixes for Operational Decision Manager V8.0.1, you must uninstall the fixes before you can install this fix pack. You must also stop the Operational Decision Manager sample server for this installation. If you do not uninstall the fixes and stop the server, the installation of the fix pack will fail. If you attempt to install the fix pack without uninstalling the interim fixes, the installer will uninstall the interim fixes before it fails. In this case, stop the sample server and restart the installation.\n
\n
Additional information:\n
- \n Fix List for IBM Operational Decision Manager\n
\n This fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.0.1 can download this fix pack.
\nHow to install the fix pack
If you are not installing both components, skip the instructions regarding Decision Center or Decision Server.
- \n
- Download 8.0.1-WS-ODM_DC-<OS>-FP002.zip, and extract its files. (Change <OS> to match your platform: WIN32, AIX, HPUX, LINUX, OS400, SOLARIS, or ZOS.) \n
- Extract the archive to a new folder, named WDC. \n
- Download 8.0.1-WS-ODM_DS-<OS>-FP002.zip, and extract its files. (Change <OS> to match your platform: WIN32, AIX, HPUX, LINUX, OS400, SOLARIS, or ZOS.) \n
- Extract the archive to a new folder, named WDS. \n
Installing by using IBM Installation Manager: \n
- \n
- Launch IBM Installation Manager. \n
- In the toolbar menu, open File > Preferences and do the following: \n
- Select repositories. \n
- Click Add Repository. \n
- Browse to the extracted folder WDC\\updates. \n
- Select the file repository.config. \n
- Click Add Repository. \n
- Browse to the extracted folder WDS\\updates. \n
- Select the file repository.config. \n
- Make sure both repositories are checked in the repository list Apply, and click OK to close. \n
- Click Update to update your installation. \n
- Follow the instructions in the installation manager to complete the installation. \n
Installing by using the Installation Manager command line: \n
- \n
- Locate the imcl command under <IM installation>/eclipse/tools. \n
- Run the command imcl updateAll -repositories WDC/updates,WDS/updates -acceptLicense. \n
- \n
- Use the option -installDirectory <install path of ODM 8.0.1> to update a specific installation. \n
- If you update only Decision Server or Decision Center, specify the repository accordingly. \n
\n
\n Applying the fix pack\n
After you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack. \n
\n
\n Warning: \n
If you have installed interim fixes for Operational Decision Manager V8.0.1, you must uninstall the fixes before you can install this fix pack. You must also stop the Operational Decision Manager sample server for this installation. If you do not uninstall the fixes and stop the server, the installation of the fix pack will fail. If you attempt to install the fix pack without uninstalling the interim fixes, the installer will uninstall the interim fixes before it fails. In this case, stop the sample server and restart the installation.\n
\n
Additional information:\n
- \n Fix List for IBM Operational Decision Manager\n
Prerequisites
\n\n
\n Operational Decision Manager V8.0.1
\n \n
\n \n \n \n
\n
\n | URL | \nLANGUAGE | \nSIZE(Bytes) | \n
|---|---|---|
| ODM Decision Center 8.0.1.2 Linux | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Center 8.0.1.2 AIX | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Center 8.0.1.2 HPUX | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Center 8.0.1.2 OS/400 | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Center 8.0.1.2 Solaris | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Center 8.0.1.2 Linux zSeries | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Center 8.0.1.2 Windows | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Server 8.0.1.2 Linux | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Server 8.0.1.2 AIX | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Server 8.0.1.2 HPUX | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Server 8.0.1.2 OS/400 | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Server 8.0.1.2 Solaris | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Server 8.0.1.2 Linux zSeries | \nLanguage Independent | \n4000000000 | \n
| ODM Decision Server 8.0.1.2 Windows | \nLanguage Independent | \n4000000000 | \n
\n
\n
\n
\n \n \n \n
\n \n
\n
\n \n
\n \n
\n Problems (APARS) fixed
Problems (APARS) fixed
\n
",
+ "title": "IBM Operational Decision Manager V8.0.1.2 Fix Pack - United States",
+ "text": " DOWNLOADABLE FILES\n\nABSTRACT\n This cumulative fix pack updates Operational Decision Manager V8.0.1 to V8.0.1.2. \n\nDOWNLOAD DESCRIPTION\nThis fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.0.1 can download this fix pack. \n\nHow to install the fix pack\nIf you are not installing both components, skip the instructions regarding Decision Center or Decision Server.\n\n\n 1. Download 8.0.1-WS-ODM_DC-
\n
",
+ "title": "IBM Database errors XAER_NOTA and XA_RBTIMEOUT in WebSphere Portal SystemOut.log - United States",
+ "text": "XAER_NOTA ; XA_RBTIMEOUT; DSRA0302E; DB2 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAfter performing a database-transfer to DB2 the Portal SystemOut.log begins showing these errors....XAER_NOTA and XA_RBTIMEOUT. Portal will start successfully, but after some time these errors begin.\n\nSYMPTOM\nThe SystemOut.log shows the following....\n\n[11/6/14 3:01:31:123 CST] 00000052 FfdcProvider W\ncom.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident\nemitted on\n/opt/IBM/WebSphere/wp_profile/logs/ffdc/WebSphere_Portal_9ab993c8_14.11.\n06_03.01.28.4128871970635691679074.txt\ncom.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.rollback 524\n[11/6/14 3:01:31:123 CST] 00000052 WSRdbXaResour E DSRA0304E:\nXAException occurred. XAException contents and details are: \"\".\n[11/6/14 3:01:31:131 CST] 00000052 WSRdbXaResour E DSRA0302E:\nXAException occurred. Error code is: XAER_NOTA (-4). Exception is:\n[jcc][t4][2041][12326][4.8.86] Error executing XAResource.rollback().\nServer returned XAER_NOTA. ERRORCODE=-4203, SQLSTATE=null\n[11/6/14 3:01:31:742 CST] 00000052 FfdcProvider W\ncom.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident\nemitted on\n/opt/IBM/WebSphere/wp_profile/logs/ffdc/WebSphere_Portal_9ab993c8_14.11.\n06_03.01.31.1328120650145706319182.txt\ncom.ibm.ejs.j2c.XATransactionWrapper.rollback 755\n[11/6/14 3:01:31:742 CST] 00000052 XATransaction E J2CA0027E: An\nexception occurred while invoking rollback on an XA Resource Adapter\nfrom DataSource jdbc/wpdbDS_jcr, within transaction ID {XidImpl:\nformatId(57415344), gtrid_length(36), bqual_length(54),\ndata(000001498455d602000000010a9c2fac93c96cd67827c5280449053f45c26243b63\n12533000001498455d602000000010a9c2fac93c96cd67827c5280449053f45c26243b63\n12533000000010000000000000000000000000001)} : com.ibm.db2.jcc.am.hp:\n[jcc][t4][2041][12326][4.8.86] Error executing XAResource.rollback().\nServer returned XAER_NOTA. ERRORCODE=-4203, SQLSTATE=null\nat com.ibm.db2.jcc.am.gd.c(gd.java:453)\nat com.ibm.db2.jcc.t4.cc.b(cc.java:2733)\nat com.ibm.db2.jcc.t4.dc.b(dc.java:1540)\nat com.ibm.db2.jcc.t4.dc.a(dc.java:1320)\nat com.ibm.db2.jcc.t4.dc.a(dc.java:1315)\nat com.ibm.db2.jcc.t4.dc.rollback(dc.java:1304)\nat\ncom.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.rollback(WSRdbXaResourceImp\nl.java:1336)\nat\ncom.ibm.ejs.j2c.XATransactionWrapper.rollback(XATransactionWrapper.java:\n1315)\n\n....\n\nCaused by: com.ibm.db2.jcc.am.hp: [jcc][t4][2041][12326][4.8.86] Error\nexecuting XAResource.end(). Server returned XA_RBTIMEOUT.\nERRORCODE=-4203, SQLSTATE=null\nat com.ibm.db2.jcc.am.gd.c(gd.java:453)\nat com.ibm.db2.jcc.t4.cc.b(cc.java:2733)\nat com.ibm.db2.jcc.t4.dc.b(dc.java:1514)\n... 88 more\n\n\nCAUSE\nIn this case the problem was because the DB2 Server was hitting a transaction timeout\n\nENVIRONMENT\nWebSphere Portal 8.0x\nAIX\nDB2\n\nDIAGNOSING THE PROBLEM\nReview the SystemOut.log after startup\n\nRESOLVING THE PROBLEM\n1) Increase the transaction timeout on the Portal server via the DMGR console to 20 minutes (a value of 1200)\n\n\nTo increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 1200 seconds or greater) using the instructions in the Related information section below.\n\n2) Increase the WCM transaction timeout on the Portal server via the DMGR console to 20 minutes (a value of 1200)\n\nTo increase the WCM transaction timeout add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider:\nName: wcm.transaction.timeout\nValue: 1200 (for example)\nNote: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.\n\nRELATED INFORMATION\n Transaction Settings [http://www-01.ibm.com/support/knowledgecenter/#!/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/tjta_settlog.html?cp=SSAW57_8.0.0%2F1-3-9-6-2-0]",
+ "metadata": {
+ "sourceDocumentId": "swg21690310",
+ "date": "2015-11-23",
+ "productName": "WebSphere Portal",
+ "productId": "SSHRKX",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21690310"
+ }
+ },
+ "swg1JR51223": {
+ "id": "swg1JR51223",
+ "content": "\n\n
\nXAER_NOTA ; XA_RBTIMEOUT; DSRA0302E; DB2
\n\n\n \n \n
\n \n
\n Technote (troubleshooting)
\n \n
\n
\n
\n \n
Problem
\n\n
\n After performing a database-transfer to DB2 the Portal SystemOut.log begins showing these errors....XAER_NOTA and XA_RBTIMEOUT. Portal will start successfully, but after some time these errors begin.
\nSymptom
\n\n
\n The SystemOut.log shows the following....
[11/6/14 3:01:31:123 CST] 00000052 FfdcProvider W
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident
emitted on
/opt/IBM/WebSphere/wp_profile/logs/ffdc/WebSphere_Portal_9ab993c8_14.11.
06_03.01.28.4128871970635691679074.txt
com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.rollback 524
[11/6/14 3:01:31:123 CST] 00000052 WSRdbXaResour E DSRA0304E:
XAException occurred. XAException contents and details are: "".
[11/6/14 3:01:31:131 CST] 00000052 WSRdbXaResour E DSRA0302E:
XAException occurred. Error code is: XAER_NOTA (-4). Exception is:
[jcc][t4][2041][12326][4.8.86] Error executing XAResource.rollback().
Server returned XAER_NOTA. ERRORCODE=-4203, SQLSTATE=null
[11/6/14 3:01:31:742 CST] 00000052 FfdcProvider W
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident
emitted on
/opt/IBM/WebSphere/wp_profile/logs/ffdc/WebSphere_Portal_9ab993c8_14.11.
06_03.01.31.1328120650145706319182.txt
com.ibm.ejs.j2c.XATransactionWrapper.rollback 755
[11/6/14 3:01:31:742 CST] 00000052 XATransaction E J2CA0027E: An
exception occurred while invoking rollback on an XA Resource Adapter
from DataSource jdbc/wpdbDS_jcr, within transaction ID {XidImpl:
formatId(57415344), gtrid_length(36), bqual_length(54),
data(000001498455d602000000010a9c2fac93c96cd67827c5280449053f45c26243b63
12533000001498455d602000000010a9c2fac93c96cd67827c5280449053f45c26243b63
12533000000010000000000000000000000000001)} : com.ibm.db2.jcc.am.hp:
[jcc][t4][2041][12326][4.8.86] Error executing XAResource.rollback().
Server returned XAER_NOTA. ERRORCODE=-4203, SQLSTATE=null
at com.ibm.db2.jcc.am.gd.c(gd.java:453)
at com.ibm.db2.jcc.t4.cc.b(cc.java:2733)
at com.ibm.db2.jcc.t4.dc.b(dc.java:1540)
at com.ibm.db2.jcc.t4.dc.a(dc.java:1320)
at com.ibm.db2.jcc.t4.dc.a(dc.java:1315)
at com.ibm.db2.jcc.t4.dc.rollback(dc.java:1304)
at
com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.rollback(WSRdbXaResourceImp
l.java:1336)
at
com.ibm.ejs.j2c.XATransactionWrapper.rollback(XATransactionWrapper.java:
1315)
....
Caused by: com.ibm.db2.jcc.am.hp: [jcc][t4][2041][12326][4.8.86] Error
executing XAResource.end(). Server returned XA_RBTIMEOUT.
ERRORCODE=-4203, SQLSTATE=null
at com.ibm.db2.jcc.am.gd.c(gd.java:453)
at com.ibm.db2.jcc.t4.cc.b(cc.java:2733)
at com.ibm.db2.jcc.t4.dc.b(dc.java:1514)
... 88 more
\n
Cause
\n\n
\n In this case the problem was because the DB2 Server was hitting a transaction timeout
\nEnvironment
\n\n
\n WebSphere Portal 8.0x
AIX
DB2
Diagnosing the problem
\n\n
\n Review the SystemOut.log after startup
\nResolving the problem
\n\n
\n 1) Increase the transaction timeout on the Portal server via the DMGR console to 20 minutes (a value of 1200)
To increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 1200 seconds or greater) using the instructions in the Related information section below.
2) Increase the WCM transaction timeout on the Portal server via the DMGR console to 20 minutes (a value of 1200)
To increase the WCM transaction timeout add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider:
Name: wcm.transaction.timeout
Value: 1200 (for example)
Note: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.
Related information
\n \n\n \n
\n \n
\n \n \n\n
",
+ "title": "IBM JR51223: FILE DESCRIPTOR LEAKS ON BPM.LOCK FILE - United States",
+ "text": " FIXES ARE AVAILABLE\nVersion 8.5 Refresh Pack 6 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24039185]\nVersion 8.5.0 Fix Pack 2 for the IBM Business Process Manager products [http://www-01.ibm.com/support/docview.wss?uid=swg24040683]\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 you use IBM Business Process Manager (BPM), you might\n receive the following error messages in the log files:\n \n \n java.net.SocketException: Too many open files\n \n java.io.IOException: Signals that an I/O exception of some sort\n has occurred. Reason: Too many open files\n \n Java? virtual machine (JVM) is trying to get a handle on the\n ?IBM/BPM/profiles/\n\n
\n
\n
\n \n
\n \nFixes are available
\n \n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
When you use IBM Business Process Manager (BPM), you might\nreceive the following error messages in the log files:\n\n\njava.net.SocketException: Too many open files\n\njava.io.IOException: Signals that an I/O exception of some sort\nhas occurred. Reason: Too many open files\n\nJava? virtual machine (JVM) is trying to get a handle on the\n?IBM/BPM/profiles/<profileName>/searchIndex/artifact/<clusterNam\ne>\\bpm.lock file.\n\nDepending on what IBM BPM was trying to do at the time, various\nother error messages might occur that are related to too many\nfiles being open in the JVM.\n\nPRODUCTS AFFECTED:\nIBM Business Process Manager (BPM) Advanced\nIBM BPM Standard\nIBM BPM Express\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
File descriptor leaks on the bpm.lock file causes an error about\n there being too many files open.\n
\n \n
Problem conclusion
\n- \n
- \n \n
A fix is available for IBM BPM V8.5.0.1 and V8.5.5.0 that\nensures only one cluster member has write access to the index\ndirectory at a time.\n\nOn Fix Central (http://www.ibm.com/support/fixcentral), search\nfor JR51223:\n\n1. Select IBM Business Process Manager with your edition from\nthe product selector, the installed version to the fix pack\nlevel, and your platform, and then click Continue.\n2. Select APAR or SPR, enter JR51223, and click Continue.\n\nWhen you download fix packages, ensure that you also download\nthe readme file for each fix. Review each readme file for\nadditional installation instructions and information about the\nfix.\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
JR51223
\n Reported component name
BPM ADVANCED
\n Reported component ID
5725C9400
\n Reported release
850
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2014-09-09
\n Closed date
2014-10-08
\n Last modified date
2014-10-08
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
BPM ADVANCED
\n Fixed component ID
5725C9400
\n
Applicable component levels
\n- \n
R850 PSY
UP
\n
\n
\n
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n
Question
\nHow do I run nzbackup on a database name with mixed case characters?
\nAnswer
\n\n
\n To run /nz/kit/bin/nzbackup on a database that has both upper and lowercase characters, the -db argument needs to escape the <database> value as shown below:
\n- \n
\n nzbackup -db "\\\\"Your Database\\\\"" \n
\n
\n \n
\n
\n \n \nHistorical Number
\nNZ494652
\n",
+ "title": "IBM nzbackup on mixed case database name - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n How do I run nzbackup on a database name with mixed case characters? \n\nANSWER\nTo run /nz/kit/bin/nzbackup on a database that has both upper and lowercase characters, the -db argument needs to escape the
\n
\n\n\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
When using the version 6.1 of the Update Installer (UPDI)\nto update WebSphere 6.0.2.x with a Fix Pack that includes\nmodifySetupCmdLineForRemoveUSER_INSTALL_ROOTCheck.ant,\nthe update process returns a status of PARTIALSUCCESS.\n
\n \n
Local fix
\n- \n
- \n \n
Use version 6.0.x of the UpdateInstaller to install the\nfix pack rather than than version 6.1.x of the\nUpdateInstaller.\n
\n \n
Problem summary
\n- \n
- \n \n
****************************************************************\n* USERS AFFECTED: Users updating a version 6.0.2.x Websphere *\n* Application Server using Update Installer *\n* Version 6.1. *\n* *\n* *\n****************************************************************\n* PROBLEM DESCRIPTION: When using Update Installer (UPDI) *\n* V6.1, to update WebSphere 6.0.2.x an *\n* underlying ANT script fails. *\n****************************************************************\n* RECOMMENDATION: Update Installer V6.0.x can be used rather *\n* than V6.1 or a fixpack including an *\n* updated version of this file can *\n* be used. *\n****************************************************************\nWhen using Update Installer(UPDI)V6.1 with fixpacks containing\nAPAR PK10233, the update is not successful due to\nan incompatibility with an underlying ANT script, and\nthe version of ANT used with UPDI V6.1.\n
\n \n
Problem conclusion
\n- \n
- \n \n
The updated ANT script is now compatible with both version 6.0\nand version 6.1 of the Update Installer.\nThis fix is targetted for fixpack 6.0.2.11.\nPlease refer to the recommended updates page for delivery\ninformation:\nhttp://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PK25100
\n Reported component name
WEBSPH APP SERV
\n Reported component ID
5724J0800
\n Reported release
60I
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2006-05-16
\n Closed date
2006-06-07
\n Last modified date
2006-06-07
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Modules/Macros
\n- \n
- \n \n
INSTALL\n
\n \n
Fix information
\n- \n
Fixed component name
WEBSPH APP SERV
\n Fixed component ID
5724J0800
\n
Applicable component levels
\n- \n
R60A PSY
UP
\n R60H PSY
UP
\n R60I PSY
UP
\n R60P PSY
UP
\n R60S PSY
UP
\n R60W PSY
UP
\n R60Z PSY
UP
\n R61A PSN
UP
\n R61H PSN
UP
\n R61I PSN
UP
\n R61P PSN
UP
\n R61S PSN
UP
\n R61W PSN
UP
\n R61Z PSN
UP
\n
\n
\n
",
+ "title": "IBM PK25100: UPDATEINSTALLER V6.1 RETURNS A PARTIALSUCCESS WHEN UPDATING WITH 6.0.2.X FIX PACK. - United States",
+ "text": " 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 * When using the version 6.1 of the Update Installer (UPDI)\n to update WebSphere 6.0.2.x with a Fix Pack that includes\n modifySetupCmdLineForRemoveUSER_INSTALL_ROOTCheck.ant,\n the update process returns a status of PARTIALSUCCESS.\n \n \n \n \n \n\nLOCAL FIX\n * Use version 6.0.x of the UpdateInstaller to install the\n fix pack rather than than version 6.1.x of the\n UpdateInstaller.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: Users updating a version 6.0.2.x Websphere *\n * Application Server using Update Installer *\n * Version 6.1. *\n * *\n * *\n ****************************************************************\n * PROBLEM DESCRIPTION: When using Update Installer (UPDI) *\n * V6.1, to update WebSphere 6.0.2.x an *\n * underlying ANT script fails. *\n ****************************************************************\n * RECOMMENDATION: Update Installer V6.0.x can be used rather *\n * than V6.1 or a fixpack including an *\n * updated version of this file can *\n * be used. *\n ****************************************************************\n When using Update Installer(UPDI)V6.1 with fixpacks containing\n APAR PK10233, the update is not successful due to\n an incompatibility with an underlying ANT script, and\n the version of ANT used with UPDI V6.1.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The updated ANT script is now compatible with both version 6.0\n and version 6.1 of the Update Installer.\n This fix is targetted for fixpack 6.0.2.11.\n Please refer to the recommended updates page for delivery\n 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 PK25100\n \n \n * REPORTED COMPONENT NAME\n WEBSPH APP SERV\n \n \n * REPORTED COMPONENT ID\n 5724J0800\n \n \n * REPORTED RELEASE\n 60I\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 2006-05-16\n \n \n * CLOSED DATE\n 2006-06-07\n \n \n * LAST MODIFIED DATE\n 2006-06-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\nMODULES/MACROS\n * INSTALL\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBSPH APP SERV\n \n \n * FIXED COMPONENT ID\n 5724J0800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R60A PSY\n UP\n \n \n * R60H PSY\n UP\n \n \n * R60I PSY\n UP\n \n \n * R60P PSY\n UP\n \n \n * R60S PSY\n UP\n \n \n * R60W PSY\n UP\n \n \n * R60Z PSY\n UP\n \n \n * R61A PSN\n UP\n \n \n * R61H PSN\n UP\n \n \n * R61I PSN\n UP\n \n \n * R61P PSN\n UP\n \n \n * R61S PSN\n UP\n \n \n * R61W PSN\n UP\n \n \n * R61Z PSN\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1PK25100",
+ "date": "2006-06-07",
+ "productName": "WebSphere Application Server",
+ "productId": "SSEQTP",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PK25100"
+ }
+ },
+ "swg21412061": {
+ "id": "swg21412061",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n
Question
\nHow do I export and import private keys between the same or different Hardware Security Module (HSM) enabled IBM WebSphere DataPower SOA Appliance?
\nAnswer
\n\n
Each HSM has a special key inside of it, the key-wrapping key, that is used to encrypt exported private keys (and to decrypt imported private keys). If the goal is to restore exported keys to the same appliance, then you don't need to worry about \n hsm-clone-kwk, red keys, or the \n hsm-domain parameter. That is because the key-wrapping key at import time will already match the key-wrapping key at export time (since the HSM device is the same). \n
\n HSM-enabled DataPower appliances support the export of private keys using the crypto-export command. For key export to work, various conditions must be met:
\n- \n
- HSMs must be initialized and in the same key sharing domain on exporting and importing machines \n
- The private key in question must be marked exportable at keygen time (see keygen's exportable option) \n
- HSMs on exporting and importing machines must share internal key-wrapping keys (see hsm-clone-kwk command). A key-wrapping key is a key that encrypts another key. \n
Each HSM has a special key inside of it, the key-wrapping key, that is used to encrypt exported private keys (and to decrypt imported private keys). If the goal is to restore exported keys to the same appliance, then you don't need to worry about \n hsm-clone-kwk, red keys, or the \n hsm-domain parameter. That is because the key-wrapping key at import time will already match the key-wrapping key at export time (since the HSM device is the same). \n
If the goal is to move exported keys from one appliance to another one, then all of the steps in this section must be followed :-
\nFirst, the two HSMs in question must be both be initialized and in the same key sharing domain. This means that they must both be initialized in the same mode (both in Security Level 2 or both in Security Level 3). In Security Level 2 mode, they must have used the same hsm-domain parameter during hsm-reinit (this parameter has a default value that is the same on all appliances). In Security Level 3 mode, they must have used the same red PED key during hsm-reinit (and the second initialization must not have overwritten the key value from the first initialization).
\nSecond, the key to be exported must be exportable. The exportability of keys is immutable. It is determined at keygen time, and it is controlled by that command's exportable parameter. If a key was created outside of the appliance (not using keygen), then it is always considered exportable.
\nFinally, before the crypto-export crypto-import sequence, the key-wrapping keys must be synchronized using the hsm-clone-kwk command. This command must be run four times: once on the source HSM appliance (with the key-wrapping key you are copying), once on the destination HSM appliance, once again on the source HSM appliance, and once again on the destination HSM appliance. Each time the command is run, it will need the output file from the previous step (as the input to the current step) which must be moved manually (usually with the copy command).
\nOnce all of this has been done, then private keys may move from system to system with crypto-export and crypto-import.
\nNote that the non-HSM appliance can export keys immediately at keygen time, but never at a later time.
\nFor additional information refer to the online Info Center and search for "PIN entry device".
Note: You will need to sign into the documentation portal with your IBM Registration ID and password.
\n
\n \n
\n
\n \n \n",
+ "title": "IBM How to export and import keys from an HSM-enabled IBM WebSphere DataPower SOA Appliance - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n How do I export and import private keys between the same or different Hardware Security Module (HSM) enabled IBM WebSphere DataPower SOA Appliance? \n\nANSWER\nHSM-enabled DataPower appliances support the export of private keys using the crypto-export command. For key export to work, various conditions must be met: \n\n * HSMs must be initialized and in the same key sharing domain on exporting and importing machines \n * The private key in question must be marked exportable at keygen time (see keygen's exportable option) \n * HSMs on exporting and importing machines must share internal key-wrapping keys (see hsm-clone-kwk command). A key-wrapping key is a key that encrypts another key.\n\n\nEach HSM has a special key inside of it, the key-wrapping key, that is used to encrypt exported private keys (and to decrypt imported private keys). If the goal is to restore exported keys to the same appliance, then you don't need to worry about hsm-clone-kwk, red keys, or the hsm-domain parameter. That is because the key-wrapping key at import time will already match the key-wrapping key at export time (since the HSM device is the same). If the goal is to move exported keys from one appliance to another one, then all of the steps in this section must be followed :- \n\nFirst, the two HSMs in question must be both be initialized and in the same key sharing domain. This means that they must both be initialized in the same mode (both in Security Level 2 or both in Security Level 3). In Security Level 2 mode, they must have used the same hsm-domain parameter during hsm-reinit (this parameter has a default value that is the same on all appliances). In Security Level 3 mode, they must have used the same red PED key during hsm-reinit (and the second initialization must not have overwritten the key value from the first initialization). \n\nSecond, the key to be exported must be exportable. The exportability of keys is immutable. It is determined at keygen time, and it is controlled by that command's exportable parameter. If a key was created outside of the appliance (not using keygen), then it is always considered exportable. \n\nFinally, before the crypto-export crypto-import sequence, the key-wrapping keys must be synchronized using the hsm-clone-kwk command. This command must be run four times: once on the source HSM appliance (with the key-wrapping key you are copying), once on the destination HSM appliance, once again on the source HSM appliance, and once again on the destination HSM appliance. Each time the command is run, it will need the output file from the previous step (as the input to the current step) which must be moved manually (usually with the copy command). \n\nOnce all of this has been done, then private keys may move from system to system with crypto-export and crypto-import. \n\nNote that the non-HSM appliance can export keys immediately at keygen time, but never at a later time. \n\nFor additional information refer to the online Info Center [http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m2/index.jsp?topic=%2Fxi50%2Fwelcome.htm] and search for \"PIN entry device\".\n\nNote: You will need to sign into the documentation portal with your IBM Registration ID and password.",
+ "metadata": {
+ "sourceDocumentId": "swg21412061",
+ "date": "2009-11-24",
+ "productName": "IBM DataPower Gateways",
+ "productId": "SS9H2Y",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21412061"
+ }
+ },
+ "swg21477472": {
+ "id": "swg21477472",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n\n
Question
\n I would like to perform a network install with my IBM SPSS Software.
The install documents provided on the CD do not provide a set of step by step instructions. How do I perform a network installation?
Answer
\n\n
\n
Given you have a network authorization code please follow the instructions below to assist in Network install of IBM SPSS software.
REM : IBM SPSS Statistics has been used as example in below procedure.
1) Decide on a machine that you wish to be the host server (Sentinel RMS LM) to which other machines will connect for license verification. Generally, you will want this machine to be a high-availability machine 24x7. The software does not require heavy processing.
2) Install Sentinel RMS License manager as a separate program apart from the application (IBM SPSS Statistics, IBM SPSS Modeler,...).
1. Open and explore the DVD and browse to the directory Windows\\Administration\\Licensing\\NetworkLicenseManager.
2. Run the Setup executable (setup.exe).
3. After Sentinel RMS is installed you may add the Authorization/License code
via Network License Manager Licensing:
- Select one of the following :
o License my product now
o Enable for temporary usage
via a DOS CMD shell :
with the command 'spssactivator' or 'licenseactivator' [authorizationcode or licensecode].
This command should be executed in the WinNT subdirectory of the Sentinel RMS LM installation directory.
Once the Sentinel RMS LM is successfully installed, licensed and running (it is a windows service) you may now install the clients. Please note that it is a requirement to restart the Sentinel License Manager service whenever changes (either addition or removal of licenses) are made. Otherwise, these changes will not be displayed within the Sentinel RMS Administration tool.
To install the clients, please follow the steps below:
1. When prompted for install options choose "Network"
2. Use the IP address or Name of the Host Machine containing the Sentinel LM installation.
Your clients should now have IBM SPSS Statistics/Modeler installed and connected to the License host.
Related information
\n Need more help? Our Modeler forum is Live!
Need more help? Our Licensing forum is Live!
\n
\n \n
\n
\n \n \n Historical Number
\n60852
\n",
+ "title": "IBM How to perform a Network install including the Sentinel License Manager and SPSS or Modeler Clients? - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n I would like to perform a network install with my IBM SPSS Software. \nThe install documents provided on the CD do not provide a set of step by step instructions. How do I perform a network installation? \n\nANSWER\n\nGiven you have a network authorization code please follow the instructions below to assist in Network install of IBM SPSS software.\n\nREM : IBM SPSS Statistics has been used as example in below procedure. \n\n1) Decide on a machine that you wish to be the host server (Sentinel RMS LM) to which other machines will connect for license verification. Generally, you will want this machine to be a high-availability machine 24x7. The software does not require heavy processing.\n\n2) Install Sentinel RMS License manager as a separate program apart from the application (IBM SPSS Statistics, IBM SPSS Modeler,...). \n1. Open and explore the DVD and browse to the directory Windows\\Administration\\Licensing\\NetworkLicenseManager.\n2. Run the Setup executable (setup.exe).\n3. After Sentinel RMS is installed you may add the Authorization/License code \nvia Network License Manager Licensing:\n- Select one of the following :\no License my product now\no Enable for temporary usage\nvia a DOS CMD shell :\nwith the command 'spssactivator' or 'licenseactivator' [authorizationcode or licensecode].\nThis command should be executed in the WinNT subdirectory of the Sentinel RMS LM installation directory.\n\nOnce the Sentinel RMS LM is successfully installed, licensed and running (it is a windows service) you may now install the clients. Please note that it is a requirement to restart the Sentinel License Manager service whenever changes (either addition or removal of licenses) are made. Otherwise, these changes will not be displayed within the Sentinel RMS Administration tool.\nTo install the clients, please follow the steps below:\n1. When prompted for install options choose \"Network\"\n2. Use the IP address or Name of the Host Machine containing the Sentinel LM installation.\n\nYour clients should now have IBM SPSS Statistics/Modeler installed and connected to the License host.\n\n\n\n\nRELATED INFORMATION\n Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\n\n\n \n\nHISTORICAL NUMBER\n 60852",
+ "metadata": {
+ "sourceDocumentId": "swg21477472",
+ "date": "2016-09-07",
+ "productName": "SPSS Modeler",
+ "productId": "SS3RA7",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21477472"
+ }
+ },
+ "swg1PM75611": {
+ "id": "swg1PM75611",
+ "content": "
\n
",
+ "title": "IBM PM75611: CELLSEXCEPTION INVALID FORMULA ERROR WHEN ACCESSING OBJECTS - United States",
+ "text": " 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 * The following error is encountered after upgrading from\n 6.6.0.467 to 6.7.0.222 and converting the objects to Office 2007\n using the Office Conversion Utility:??Type:\n CellsException?Message: Invalid formula:?Stack Trace: at\n ??.?.?(?, String , String , Int32 , ??)? at ??.?.?(?, ??)?\n at ??.?.?(?, ??)? at ??.?.??[1](?, ??, [1]?)? at ??.?.??(?,\n ??, [1]?, Boolean )? at ??.?.??(?, ??, [1]?, Boolean )? at\n ??.??.??(?, WorksheetCollection , Cell , Int32 , Int32 , Int32 ,\n ??, [1]?, Boolean )? at ??.??.??(Cell , String , Int32 , Int32\n )? at Aspose.Cells.Cell.SetArrayFormula(String arrayFormula,\n Int32?rowNumber, Int32 columnNumber)? at\n ?.???.??(XmlTextReader , Row , Int32 , Int32 )? at\n ?.???.[1]?(XmlTextReader , Int32 )? at ?.???.?(XmlTextReader\n )? at ?.???.Read(XmlTextReader )? at ?.???.??(???, String )?\n at ?.???.?(???, String )? at ?.???.??()? at ?.???.Read()?\n at ?.???.(Workbook )? at Aspose.Cells.Workbook.??(Stream ,\n LoadOptions , Boolean )? at Aspose.Cells.Workbook.??(String ,\n LoadOptions )? at Aspose.Cells.Workbook..ctor(String file)?\n at\n Clarity.FSR.Office.ExcelWrapper.GetWorkbookFromFile(String?fileN\n ame)?\n at Clarity.FSR.Office.ExcelWrapper.GetWorkbook(String\n binaryString)? at\n Clarity.FSR.UI.g.RefreshExcelObject(Application& myExcel,\n String?XmlData, Boolean Silence, CADesignDS ds, Boolean&\n OlapErr, Boolean&?ExcelErr, Boolean& RefreshHFM, Boolean\n bWillRefreshData, Int32?iOriginalReportId, Int32 objectId,\n Boolean calledOnRollover, Exception&?accountReconException,\n QueryVars queryVariables,?FSRRefreshErrorCollection\n errorCollection, String objectName)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshExcelO\n bject_Refre?shWorkbook(Int32\n objectId, String objectName, String xmlData,\n Boolean?willRefreshData, Int32 reportId, Boolean&\n willRefreshHFM,?FSRRefreshErrorCollection errorCollection)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.GetRefreshedE\n xcelContent?(Hashtable\n disconnectedSharedObjects, Boolean willUpdateNoteId,\n Int32?objectId, ObjectRow objectRow, String\n xmlData,?FSRRefreshErrorCollection errorCollection,\n ObjectDataSourceInfo?dataSourceInfo)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshExcelO\n bject(IEnum?erable`1\n objectsToRefresh, Hashtable disconnectedSharedObjects,\n Boolean?willUpdateNoteId, FSRRefreshErrorCollection\n errorCollection)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.LoadAndRefres\n hObjects(IE?numerable`1\n objectsToRefresh, Hashtable disconnectedSharedObjects,?Boolean\n willUpdateNoteId, FSRRefreshErrorCollection errorCollection)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.ProcessNative\n Objects_Ref?resh(List`1\n nativeObjects, IEnumerable`1?sourceVariablesInSharedObjects,\n Boolean willUpdateNoteId,?FSRRefreshErrorCollection\n errorCollection)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.ProcessNative\n Objects(Lis?t`1\n nativeObjects, List`1 allSharedObjects,\n List`1?preprocessedSharedObjects, Boolean\n willUpdateNoteId,?FSRRefreshErrorCollection errorCollection)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshForRep\n ortGenerati?onOrRollover(Int32\n reportId, Int32 customGroupId, List`1?selectedObjects, Boolean\n printableObjectsOnly,?FSRRefreshErrorCollection\n errorCollections)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshForRep\n ortGenerati?onOrRollover(List`1\n selectedObjects, FSRRefreshErrorCollection?errorCollections)?\n at?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshForRep\n ortGenerati?onOrRollover(FSRRefreshErrorCollection\n errorCollection)? at\n Clarity.FSR.UI.Forms.LayoutForm.ValidateLogic(Boolean\n RefreshAll,?String selectedObjectsToValidate, Boolean\n isForGeneratingReport)? at\n Clarity.FSR.UI.Forms.LayoutForm.GenerateEntireReport(String?sOut\n putType,\n String PrintOption, Boolean Snapshot, String\n Comment,?ExternalXmlConsumptionApplication xmlConsumer, String\n sFilePath, Int32?iCustomizedGroup, List`1 macro, Boolean\n OpenWhenDone)? at\n Clarity.FSR.UI.Forms.LayoutForm.mnuWhole_Click(Object\n sender,?EventArgs e)? at\n System.Windows.Forms.MenuItem.OnClick(EventArgs e)? at\n System.Windows.Forms.MenuItem.MenuItemData.Execute()? at\n System.Windows.Forms.Command.Invoke()? at\n System.Windows.Forms.Command.DispatchID(Int32 id)? at\n System.Windows.Forms.Control.WmCommand(Message& m)? at\n System.Windows.Forms.Control.WndProc(Message& m)? at\n DevExpress.XtraEditors.Container.EditorContainer.WndProc(Message\n &?m)?\n \n at?System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Me\n ssage&\n m)? at\n System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message\n &?m)?\n at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd,\n Int32?msg, IntPtr wparam, IntPtr lparam)??Operating System:\n Windows 7 (Microsoft Windows NT 6.1.7601 Service\n Pack?1)?Platform: Win32NT?CLR Version:\n 2.0.50727.5456?.NET Framework: .NET Framework 4.0?Working Set:\n 164.07 MB?Physical Memory: 3.14 GB?FSR Version:\n 6.6.1.0 (6.7.0.222)?FSR DB Version: 6.7.0.37?Excel Version:\n 12.0?Word Version: 12.0??This error occurs on some excel\n objects. ??This error Occurs in the following Report:?Entity\n Name: CN?Report Name: Q3 2012 Quarterly Review?Custom Group:\n Quarterly??\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * All Users *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * See error description. *\n ****************************************************************\n * RECOMMENDATION: *\n * Fixed in FSR 6.6.1 FP2 *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Code Fix\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM75611\n \n \n * REPORTED COMPONENT NAME\n COGNOS FSR\n \n \n * REPORTED COMPONENT ID\n 5725D3400\n \n \n * REPORTED RELEASE\n 660\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 2012-10-22\n \n \n * CLOSED DATE\n 2013-07-05\n \n \n * LAST MODIFIED DATE\n 2013-07-05\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 COGNOS FSR\n \n \n * FIXED COMPONENT ID\n 5725D3400\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R661 PSN\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1PM75611",
+ "date": "2013-07-05",
+ "productName": "Cognos Financial Statement Reporting",
+ "productId": "SSJSTG",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PM75611"
+ }
+ },
+ "swg1PM86992": {
+ "id": "swg1PM86992",
+ "content": "\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
The following error is encountered after upgrading from\n6.6.0.467 to 6.7.0.222 and converting the objects to Office 2007\nusing the Office Conversion Utility:??Type:\nCellsException?Message: Invalid formula:?Stack Trace: at\n??.?.?(?, String , String , Int32 , ??)? at ??.?.?(?, ??)?\nat ??.?.?(?, ??)? at ??.?.??[1](?, ??, [1]?)? at ??.?.??(?,\n??, [1]?, Boolean )? at ??.?.??(?, ??, [1]?, Boolean )? at\n??.??.??(?, WorksheetCollection , Cell , Int32 , Int32 , Int32 ,\n??, [1]?, Boolean )? at ??.??.??(Cell , String , Int32 , Int32\n)? at Aspose.Cells.Cell.SetArrayFormula(String arrayFormula,\nInt32?rowNumber, Int32 columnNumber)? at\n?.???.??(XmlTextReader , Row , Int32 , Int32 )? at\n?.???.[1]?(XmlTextReader , Int32 )? at ?.???.?(XmlTextReader\n)? at ?.???.Read(XmlTextReader )? at ?.???.??(???, String )?\n at ?.???.?(???, String )? at ?.???.??()? at ?.???.Read()?\n at ?.???.(Workbook )? at Aspose.Cells.Workbook.??(Stream ,\nLoadOptions , Boolean )? at Aspose.Cells.Workbook.??(String ,\nLoadOptions )? at Aspose.Cells.Workbook..ctor(String file)?\nat\nClarity.FSR.Office.ExcelWrapper.GetWorkbookFromFile(String?fileN\name)?\n at Clarity.FSR.Office.ExcelWrapper.GetWorkbook(String\nbinaryString)? at\nClarity.FSR.UI.g.RefreshExcelObject(Application& myExcel,\nString?XmlData, Boolean Silence, CADesignDS ds, Boolean&\nOlapErr, Boolean&?ExcelErr, Boolean& RefreshHFM, Boolean\nbWillRefreshData, Int32?iOriginalReportId, Int32 objectId,\nBoolean calledOnRollover, Exception&?accountReconException,\nQueryVars queryVariables,?FSRRefreshErrorCollection\nerrorCollection, String objectName)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshExcelO\nbject_Refre?shWorkbook(Int32\nobjectId, String objectName, String xmlData,\nBoolean?willRefreshData, Int32 reportId, Boolean&\nwillRefreshHFM,?FSRRefreshErrorCollection errorCollection)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.GetRefreshedE\nxcelContent?(Hashtable\ndisconnectedSharedObjects, Boolean willUpdateNoteId,\nInt32?objectId, ObjectRow objectRow, String\nxmlData,?FSRRefreshErrorCollection errorCollection,\nObjectDataSourceInfo?dataSourceInfo)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshExcelO\nbject(IEnum?erable`1\nobjectsToRefresh, Hashtable disconnectedSharedObjects,\nBoolean?willUpdateNoteId, FSRRefreshErrorCollection\nerrorCollection)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.LoadAndRefres\nhObjects(IE?numerable`1\nobjectsToRefresh, Hashtable disconnectedSharedObjects,?Boolean\nwillUpdateNoteId, FSRRefreshErrorCollection errorCollection)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.ProcessNative\nObjects_Ref?resh(List`1\nnativeObjects, IEnumerable`1?sourceVariablesInSharedObjects,\nBoolean willUpdateNoteId,?FSRRefreshErrorCollection\nerrorCollection)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.ProcessNative\nObjects(Lis?t`1\nnativeObjects, List`1 allSharedObjects,\nList`1?preprocessedSharedObjects, Boolean\nwillUpdateNoteId,?FSRRefreshErrorCollection errorCollection)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshForRep\nortGenerati?onOrRollover(Int32\nreportId, Int32 customGroupId, List`1?selectedObjects, Boolean\nprintableObjectsOnly,?FSRRefreshErrorCollection\nerrorCollections)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshForRep\nortGenerati?onOrRollover(List`1\nselectedObjects, FSRRefreshErrorCollection?errorCollections)?\nat?Clarity.FSR.UI.Generation.LegacyReportRefresher.RefreshForRep\nortGenerati?onOrRollover(FSRRefreshErrorCollection\nerrorCollection)? at\nClarity.FSR.UI.Forms.LayoutForm.ValidateLogic(Boolean\nRefreshAll,?String selectedObjectsToValidate, Boolean\nisForGeneratingReport)? at\nClarity.FSR.UI.Forms.LayoutForm.GenerateEntireReport(String?sOut\nputType,\nString PrintOption, Boolean Snapshot, String\nComment,?ExternalXmlConsumptionApplication xmlConsumer, String\nsFilePath, Int32?iCustomizedGroup, List`1 macro, Boolean\nOpenWhenDone)? at\nClarity.FSR.UI.Forms.LayoutForm.mnuWhole_Click(Object\nsender,?EventArgs e)? at\nSystem.Windows.Forms.MenuItem.OnClick(EventArgs e)? at\nSystem.Windows.Forms.MenuItem.MenuItemData.Execute()? at\nSystem.Windows.Forms.Command.Invoke()? at\nSystem.Windows.Forms.Command.DispatchID(Int32 id)? at\nSystem.Windows.Forms.Control.WmCommand(Message& m)? at\nSystem.Windows.Forms.Control.WndProc(Message& m)? at\nDevExpress.XtraEditors.Container.EditorContainer.WndProc(Message\n&?m)?\n\nat?System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Me\nssage&\nm)? at\nSystem.Windows.Forms.Control.ControlNativeWindow.WndProc(Message\n&?m)?\n at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd,\nInt32?msg, IntPtr wparam, IntPtr lparam)??Operating System:\nWindows 7 (Microsoft Windows NT 6.1.7601 Service\nPack?1)?Platform: Win32NT?CLR Version:\n2.0.50727.5456?.NET Framework: .NET Framework 4.0?Working Set:\n 164.07 MB?Physical Memory: 3.14 GB?FSR Version:\n6.6.1.0 (6.7.0.222)?FSR DB Version: 6.7.0.37?Excel Version:\n12.0?Word Version: 12.0??This error occurs on some excel\nobjects. ??This error Occurs in the following Report:?Entity\nName: CN?Report Name: Q3 2012 Quarterly Review?Custom Group:\nQuarterly??\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
****************************************************************\n* USERS AFFECTED: *\n* All Users *\n****************************************************************\n* PROBLEM DESCRIPTION: *\n* See error description. *\n****************************************************************\n* RECOMMENDATION: *\n* Fixed in FSR 6.6.1 FP2 *\n****************************************************************\n
\n \n
Problem conclusion
\n- \n
- \n \n
Code Fix\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PM75611
\n Reported component name
COGNOS FSR
\n Reported component ID
5725D3400
\n Reported release
660
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2012-10-22
\n Closed date
2013-07-05
\n Last modified date
2013-07-05
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
COGNOS FSR
\n Fixed component ID
5725D3400
\n
Applicable component levels
\n- \n
R661 PSN
UP
\n
\n
\n
\n
\n\n\n\n
\n
\n
\nz/os
\n\n \n
\n \nA fix is available
\n \n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
CICS joblog(s) shows abends occurred as follows:\n\nDFHSM0001 AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'09F0' IN MODULE DFHSMGF.\nDFHAP0002 A SEVERE ERROR (CODE X'0595') HAS OCCURRED IN MODULE\n DFHAPXM.\nDFHAP0001 AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'01C0' IN MODULE DFHMRXM\nDFHAP0001 AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'029A' IN MODULE DFHMRXM.\n.\nThe last DFHAP0001 is repeated until the region is terminated.\n.\nA user transid is being attached. The SM0001 and AP0002 are\nrelated to a getmain for the task's TCA. The program check 0C4\nin DFHSMGF causes the getmain to fail so we do NOT have a TCA\nfor this task. The KE stack shows an abend in DFHDSKE, the stack\nis corrupt. A Segentry forward pointer has been overlayed (the\ncause is unknown). DFHMRXM is entered to perform recovery.\nWhen entering DFHMRXM it assumes that the TASENTRY has a valid\nTCA at offset 0028. However, this isn't the case, because of the\nabend in DFHSMGF, there is no TCA. RegC is loaded from the\nTASENTRY with 00000000. causing an abend 0C4 at offset x'1C0'.\n.\nThe recovery routine in DFHMRXM (RECOVERY_ROUTINE), issues the\nmessage but then returns to the mainline code at MRXM_RETURN\nwhere it uses RegC, again, assuming it contains the TCA.\nIt now abends at offset X'029A'.\nWe drive the recovery routine in DFHMRXM (RECOVERY_ROUTINE)\nand a tight loop occurs around the abend and its recovery.\n
\n \n
Local fix
\n- \n
- \n \n
Prevent abend SM0001\n
\n \n
Problem summary
\n- \n
- \n \n
****************************************************************\n* USERS AFFECTED: All. *\n****************************************************************\n* PROBLEM DESCRIPTION: Recursive abend in DFHMRXM causes CICS *\n* to crash. *\n****************************************************************\n* RECOMMENDATION: *\n****************************************************************\nIn the reported problem, 2 CICS systems ( SYSA and SYSB ) were\nconnected via IRC. The transaction routing program ( DFHRTE )\nwas activated by CRTE on SYSA so a transaction entered on SYSA\nwas routed to SYSB. When SYSB received the request, DFHAPXM\nwas driven for transaction attach and in doing so, attempted\nto GETMAIN a TCA. The GETMAIN failed but a codepath exists\nwhereby processing continued and DFHMRXM was driven to notify\nthe primary client that the transaction would wait forever.\nDFHMRXM abended ( because of no TCA ) and its recovery routine\nwas driven. Control returned to DFHMRXM mainline logic where\nthe abend sequence was repeated. SYSB was in a recursive abend\nsituation.\n
\n \n
Problem conclusion
\n- \n
- \n \n
DFHXMTA has been modified to not call DFHMRXM in the\naforementioned scenario.\n
\n \n
Temporary fix
\n- \n
- \n \n
*********\n * HIPER *\n *********\nFIX AVAILABLE BY PTF ONLY\n
\n \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PM86992
\n Reported component name
CICSTS V3 Z/OS
\n Reported component ID
5655M1500
\n Reported release
500
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
YesHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2013-04-15
\n Closed date
2013-09-09
\n Last modified date
2013-10-03
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
PM93389 UK97399
\n
Modules/Macros
\n- \n
- \n \n
DFHXMTA\n
\n \n
Fix information
\n- \n
Fixed component name
CICSTS V3 Z/OS
\n Fixed component ID
5655M1500
\n
Applicable component levels
\n- \n
R500 PSY UK97399
UP13/09/21 P F309
\n
Fix is available
\n- \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.
\n
\n
\n
",
+ "title": "IBM PM86992: TIGHT LOOP IN DFHMRXM AFTER ABEND IN DFHSMGF - United States",
+ "text": "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 * CICS joblog(s) shows abends occurred as follows:\n \n DFHSM0001 AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'09F0' IN MODULE DFHSMGF.\n DFHAP0002 A SEVERE ERROR (CODE X'0595') HAS OCCURRED IN MODULE\n DFHAPXM.\n DFHAP0001 AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'01C0' IN MODULE DFHMRXM\n DFHAP0001 AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'029A' IN MODULE DFHMRXM.\n .\n The last DFHAP0001 is repeated until the region is terminated.\n .\n A user transid is being attached. The SM0001 and AP0002 are\n related to a getmain for the task's TCA. The program check 0C4\n in DFHSMGF causes the getmain to fail so we do NOT have a TCA\n for this task. The KE stack shows an abend in DFHDSKE, the stack\n is corrupt. A Segentry forward pointer has been overlayed (the\n cause is unknown). DFHMRXM is entered to perform recovery.\n When entering DFHMRXM it assumes that the TASENTRY has a valid\n TCA at offset 0028. However, this isn't the case, because of the\n abend in DFHSMGF, there is no TCA. RegC is loaded from the\n TASENTRY with 00000000. causing an abend 0C4 at offset x'1C0'.\n .\n The recovery routine in DFHMRXM (RECOVERY_ROUTINE), issues the\n message but then returns to the mainline code at MRXM_RETURN\n where it uses RegC, again, assuming it contains the TCA.\n It now abends at offset X'029A'.\n We drive the recovery routine in DFHMRXM (RECOVERY_ROUTINE)\n and a tight loop occurs around the abend and its recovery.\n \n \n \n \n \n\nLOCAL FIX\n * Prevent abend SM0001\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All. *\n ****************************************************************\n * PROBLEM DESCRIPTION: Recursive abend in DFHMRXM causes CICS *\n * to crash. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n In the reported problem, 2 CICS systems ( SYSA and SYSB ) were\n connected via IRC. The transaction routing program ( DFHRTE )\n was activated by CRTE on SYSA so a transaction entered on SYSA\n was routed to SYSB. When SYSB received the request, DFHAPXM\n was driven for transaction attach and in doing so, attempted\n to GETMAIN a TCA. The GETMAIN failed but a codepath exists\n whereby processing continued and DFHMRXM was driven to notify\n the primary client that the transaction would wait forever.\n DFHMRXM abended ( because of no TCA ) and its recovery routine\n was driven. Control returned to DFHMRXM mainline logic where\n the abend sequence was repeated. SYSB was in a recursive abend\n situation.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * DFHXMTA has been modified to not call DFHMRXM in the\n aforementioned scenario.\n \n \n \n \n \n\nTEMPORARY FIX\n * *********\n * HIPER *\n *********\n FIX AVAILABLE BY PTF ONLY\n \n \n \n \n \n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM86992\n \n \n * REPORTED COMPONENT NAME\n CICSTS V3 Z/OS\n \n \n * REPORTED COMPONENT ID\n 5655M1500\n \n \n * REPORTED RELEASE\n 500\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n YesHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2013-04-15\n \n \n * CLOSED DATE\n 2013-09-09\n \n \n * LAST MODIFIED DATE\n 2013-10-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 PM93389 [http://www-01.ibm.com/support/docview.wss?uid=swg1PM93389] UK97399\n \n \n\nMODULES/MACROS\n * DFHXMTA\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CICSTS V3 Z/OS\n \n \n * FIXED COMPONENT ID\n 5655M1500\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R500 PSY UK97399 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UK97399]\n UP13/09/21 P F309\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.",
+ "metadata": {
+ "sourceDocumentId": "swg1PM86992",
+ "date": "2013-10-03",
+ "productName": "CICS Transaction Server",
+ "productId": "SSGMGV,SWG90",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PM86992"
+ }
+ },
+ "swg1PI87161": {
+ "id": "swg1PI87161",
+ "content": "
\n
",
+ "title": "IBM PI87161: CONFIGURATION OPTION TO PREVENT EMAIL ACTION FROM ADDING CURRENT VIRTUAL PORTAL CONTEXT PATH TO GENERATED URLS - United States",
+ "text": " A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 and V9.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * Email actions currently uses the value of the configuration\n property wcm.authoringui.url as the base URL for any generated\n links.\n \n By default, the base URL will be modified to include the current\n virtual portal context path if applicable.\n \n To prevent the email action from adding the current virtual\n portal context path to the generated URL, add the following\n configuration property to the WCM WCMConfigService resource\n environment provider within WAS.\n wcm.email.url.includeCurrentVirtualPortalContext=false\n \n \n \n \n \n\nLOCAL FIX\n * None available\n \n \n \n \n \n\nPROBLEM SUMMARY\n * Email actions currently uses the value of the configuration\n property wcm.authoringui.url as the base URL for any generated\n links.\n \n By default, the base URL will be modified to include the current\n virtual portal context path if applicable.\n \n To prevent the email action from adding the current virtual\n portal context path to the generated URL, add the following\n configuration property to the WCM WCMConfigService resource\n environment provider within WAS.\n wcm.email.url.includeCurrentVirtualPortalContext=false\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A code fix for this issue is integrated into the WebSphere\n Portal & WCM Combined Cumulative Fix 15 (PI83476) for Portal 8.5\n and 9.0 available from Fix Central:\n \n http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent\n =ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al]\n l&platform=All&function=aparId&apars=PI83476\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI87161\n \n \n * REPORTED COMPONENT NAME\n LOTUS WEB CONT\n \n \n * REPORTED COMPONENT ID\n 5724I2900\n \n \n * REPORTED RELEASE\n 850\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-09-12\n \n \n * CLOSED DATE\n 2017-12-11\n \n \n * LAST MODIFIED DATE\n 2017-12-11\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 LOTUS WEB CONT\n \n \n * FIXED COMPONENT ID\n 5724I2900\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1PI87161",
+ "date": "2017-12-11",
+ "productName": "IBM Web Content Manager",
+ "productId": "SS3JLV",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PI87161"
+ }
+ },
+ "swg21567897": {
+ "id": "swg21567897",
+ "content": "\n\n\n
\n \n
\nA fix is available
\n \n \n
\n\n\n
\n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
Email actions currently uses the value of the configuration\nproperty wcm.authoringui.url as the base URL for any generated\nlinks.\n\nBy default, the base URL will be modified to include the current\nvirtual portal context path if applicable.\n\nTo prevent the email action from adding the current virtual\nportal context path to the generated URL, add the following\nconfiguration property to the WCM WCMConfigService resource\nenvironment provider within WAS.\nwcm.email.url.includeCurrentVirtualPortalContext=false\n
\n \n
Local fix
\n- \n
- \n \n
None available\n
\n \n
Problem summary
\n- \n
- \n \n
Email actions currently uses the value of the configuration\nproperty wcm.authoringui.url as the base URL for any generated\nlinks.\n\nBy default, the base URL will be modified to include the current\nvirtual portal context path if applicable.\n\nTo prevent the email action from adding the current virtual\nportal context path to the generated URL, add the following\nconfiguration property to the WCM WCMConfigService resource\nenvironment provider within WAS.\nwcm.email.url.includeCurrentVirtualPortalContext=false\n
\n \n
Problem conclusion
\n- \n
- \n \n
A code fix for this issue is integrated into the WebSphere\nPortal & WCM Combined Cumulative Fix 15 (PI83476) for Portal 8.5\nand 9.0 available from Fix Central:\n\nhttp://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent\n=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al\nl&platform=All&function=aparId&apars=PI83476\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PI87161
\n Reported component name
LOTUS WEB CONT
\n Reported component ID
5724I2900
\n Reported release
850
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt / Xsystem
\n Submitted date
2017-09-12
\n Closed date
2017-12-11
\n Last modified date
2017-12-11
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
LOTUS WEB CONT
\n Fixed component ID
5724I2900
\n
Applicable component levels
\n- \n
R850 PSY
UP
\n
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n \n\n
Question
\nWhy do I receive a 'Password:' prompt when running nzstart -i?
\nAnswer
\n\n
\n This document applies to NPS 4.5 and later.
If you run the nzstart -I command, you may be prompted for a "Password:" and see output similar to the following:
nzstart -i
(startupsvr) Info: NZ-00022: --- program 'startupsvr' (24644) starting on host 'nps01' ... ---
(startupsvr) Info: NZ-00307: starting the system, restart = no
(startupsvr) Info: NZ-00313: running onStart: 'prepareForStart'
(startupsvr) Info: NZ-00312: invoking program: 'sessionmgr', restart type = 'this'
(sessionmgr) Info: NZ-00022: --- program 'sessionmgr' (25222) starting on host 'nps01' ... ---
(startupsvr) Info: NZ-00312: invoking program: 'initvrels', restart type = 'none'
Password:
The "Password:" prompt is occurring as a result of the initvrels process calling /nz/kit/bin/adm/nzauth. This script is used to copy LDAP configuration files, regardless of whether LDAP is configured or not. Since the LDAP files reside under /etc (specifically as, /etc/ldap.conf and /etc/pam.d/netezza_nps), root access is need to access these files.
\n\n
Normally, the nz user and thus nzstart can access these files as a result of the following lines in the /etc/sudoers file:
\n# NPS setup -- do not edit below this line -- initarp
nz ALL = NOPASSWD: /usr/local/sbin/nzinitarp
nz ALL = NOPASSWD: /nzlocal/scripts/rpc/spapwr.sh
nz ALL = NOPASSWD: /nz/kit/bin/adm/nzauth
nz ALL = NOPASSWD: /sbin/clustat
If this line is commented out, or not present in the /etc/sudoers file, then you will be prompted for "Password:" when running nzstart.
\nThe resolution is to correctly define the /etc/sudoers as described above.
\n\n \n
\n Historical Number
\nNZ914210
\n",
+ "title": "IBM nzstart command requires password - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n Why do I receive a 'Password:' prompt when running nzstart -i? \n\nANSWER\nThis document applies to NPS 4.5 and later. \nIf you run the nzstart -I command, you may be prompted for a \"Password:\" and see output similar to the following: \n\n \n\nnzstart -i\n\n\n(startupsvr) Info: NZ-00022: --- program 'startupsvr' (24644) starting on host 'nps01' ... ---\n(startupsvr) Info: NZ-00307: starting the system, restart = no\n(startupsvr) Info: NZ-00313: running onStart: 'prepareForStart'\n(startupsvr) Info: NZ-00312: invoking program: 'sessionmgr', restart type = 'this'\n\n\n(sessionmgr) Info: NZ-00022: --- program 'sessionmgr' (25222) starting on host 'nps01' ... ---\n(startupsvr) Info: NZ-00312: invoking program: 'initvrels', restart type = 'none'\nPassword: \n\nThe \"Password:\" prompt is occurring as a result of the initvrels process calling /nz/kit/bin/adm/nzauth. This script is used to copy LDAP configuration files, regardless of whether LDAP is configured or not. Since the LDAP files reside under /etc (specifically as, /etc/ldap.conf and /etc/pam.d/netezza_nps), root access is need to access these files. \n\n \n\nNormally, the nz user and thus nzstart can access these files as a result of the following lines in the /etc/sudoers file: \n\n# NPS setup -- do not edit below this line -- initarp\nnz ALL = NOPASSWD: /usr/local/sbin/nzinitarp\nnz ALL = NOPASSWD: /nzlocal/scripts/rpc/spapwr.sh\nnz ALL = NOPASSWD: /nz/kit/bin/adm/nzauth\nnz ALL = NOPASSWD: /sbin/clustat \n\nIf this line is commented out, or not present in the /etc/sudoers file, then you will be prompted for \"Password:\" when running nzstart. \n\nThe resolution is to correctly define the /etc/sudoers as described above. \n\n\n\nHISTORICAL NUMBER\n NZ914210",
+ "metadata": {
+ "sourceDocumentId": "swg21567897",
+ "date": "2012-06-12",
+ "productName": "PureData System for Analytics",
+ "productId": "SSULQD",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21567897"
+ }
+ },
+ "swg21421563": {
+ "id": "swg21421563",
+ "content": "
\n
\n\n\n\n
\nrelease notice; downloads; nco-g-file; Gateway for Flat File
\n\n\n \n \n
\nNews
\n \n
\n
\n \n
Abstract
\nA new version of the Netcool/OMNIbus Flat File Writer Gateway will be available to download from February 19, 2010.
\nContent
\n\n
\n \n
This is a rewritten version of the Netcool/OMNIbus Flat File Writer Gateway.
\nYou can download the installation package from the IBM Passport Advantage website:
www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm
To obtain this new package, search for the part number that corresponds to your operating system as shown in the table below. You can also search for the package by name, or by operating system.
\n\n \n \n
\n
\n \n | Part number | \nOperating System | \n
| CZC4WEN | \nAIX | \n
| CZC4XEN | \nHP-UX PA-RISC | \n
| CZC4ZEN | \nHP-UX Itanium | \n
| CZC50EN | \nLinux | \n
| CZC4YEN | \nLinux for zSeries | \n
| CZC51EN | \nSolaris | \n
| CZC52EN | \nWindows | \n
\n
\n \n
\n
\n \n \n",
+ "title": "IBM Netcool/OMNIbus Integrations Release Notice - nco-g-file-3_0 - United States",
+ "text": "release notice; downloads; nco-g-file; Gateway for Flat File NEWS\n\nABSTRACT\n A new version of the Netcool/OMNIbus Flat File Writer Gateway will be available to download from February 19, 2010. \n\nCONTENT\n \n\nThis is a rewritten version of the Netcool/OMNIbus Flat File Writer Gateway.\n\nYou can download the installation package from the IBM Passport Advantage website: \nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nTo obtain this new package, search for the part number that corresponds to your operating system as shown in the table below. You can also search for the package by name, or by operating system.\n\nPart number Operating System CZC4WEN AIX CZC4XEN HP-UX PA-RISC CZC4ZEN HP-UX Itanium CZC50EN Linux CZC4YEN Linux for zSeries CZC51EN Solaris CZC52EN Windows",
+ "metadata": {
+ "sourceDocumentId": "swg21421563",
+ "date": "2015-01-29",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21421563"
+ }
+ },
+ "swg21689794": {
+ "id": "swg21689794",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n \n\n
Question
\nIf you telnet to RPC, you can get the outlet status. You can get the same information by using ibm_rpc command.
\nAnswer
\n\n
\n Run the following command as NZ user:
/nz/kit/share/nzhealthcheck/devmgrs/bin/adm/ibm_rpc --loc=rack1.rpc1 --status
rpc1: Lower Left
rpc2: Lower Right
rpc3: Upper Left
rpc4: Upper Right
Sample output:
[nz@host1]$ /nz/kit/share/nzhealthcheck/devmgrs/bin/adm/ibm_rpc --loc=rack1.rpc2 --status
<?xml version="1.0" encoding="UTF-8"?>
<device-info version="2">
<reporting-component hw-type="rpc" pos="lr" rack-id="1" ret-code="0" ret-desc="success">
<device-inventory>
<device hw-type="rpc" pos="lr" rack-id="1">
<device hw-type="outlet" name="SPA01 SPA-DE07 right" slot="1" status="on"/>
<device hw-type="outlet" name="SPA01 SPA-DE08 right" slot="2" status="on"/>
<device hw-type="outlet" name="SPA01 SPA-DE09 right" slot="3" status="on"/>
<device hw-type="outlet" name="SPA01 SPA-DE10 right" slot="4" status="on"/>
<device hw-type="outlet" name="SPA01 SPA-DE11 right" slot="5" status="on"/>
<device hw-type="outlet" name="SPA01 SPA-DE12 right" slot="6" status="on"/>
<device hw-type="outlet" name="host1" slot="7" status="on"/>
<device hw-type="outlet" name="host2" slot="8" status="on"/>
</device>
</device-inventory>
</reporting-component>
</device-info>
[nz@host1]$
\n \n
\n ",
+ "title": "IBM PureData for Analytics - How to check RPC status without doing telnet to RPCs - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n If you telnet to RPC, you can get the outlet status. You can get the same information by using ibm_rpc command. \n\nANSWER\nRun the following command as NZ user:\n/nz/kit/share/nzhealthcheck/devmgrs/bin/adm/ibm_rpc --loc=rack1.rpc1 --status\n\nrpc1: Lower Left\nrpc2: Lower Right\nrpc3: Upper Left\nrpc4: Upper Right\n\nSample output:\n[nz@host1]$ /nz/kit/share/nzhealthcheck/devmgrs/bin/adm/ibm_rpc --loc=rack1.rpc2 --status\n\n
\n
",
+ "title": "IBM java.net.SocketException: Too many open files in system received in system log (SCI67669) - United States",
+ "text": "STERLINGPRI TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n java.net.SocketException: Too many open files in system received in system log (SCI67669) \n\nSYMPTOM\n\n\nERROR Got IOException in URL.send \njava.net.SocketException: Too many open files in system\n\n\nCAUSE\nThe maximum number of allowed file descriptors is not high enough.\n\nRESOLVING THE PROBLEM\n\n\nThe allowable file descriptors for the Gentran Integration Suite (GIS) user must be increased.? Per session, this can be done with ulimit. By default, most linux systems are only set to 1024 per user.? A permanent way to make this change (and our recommended method) is to edit /etc/security/limits.conf, giving the GIS user 8192 for the soft limit.\n\n\nMore information about system-wide file descriptor settings:\n\n\nThe? /proc/sys/fs/file-nr will show the number of allocated file descriptors, the number of file descriptors used, and the maximum number of file descriptors .\nThe /proc/sys/fs/inode-nr will show the number of descriptors left.\n\n \n\nHISTORICAL NUMBER\n PRI6676 \n\nPRODUCT ALIAS/SYNONYM\n \n\nFact\n\n\nGentran Integration Suite\n? Release 3.1 \nRed Hat Linux AS 2.1 \n\nSCI67669",
+ "metadata": {
+ "sourceDocumentId": "swg21547126",
+ "date": "2011-10-07",
+ "productName": "Sterling B2B Integrator",
+ "productId": "SS3JSW",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21547126"
+ }
+ },
+ "swg21519038": {
+ "id": "swg21519038",
+ "content": "\n\n
\nSTERLINGPRI
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\njava.net.SocketException: Too many open files in system received in system log (SCI67669)
\nSymptom
\n\n \n
\n ERROR Got IOException in URL.send
java.net.SocketException: Too many open files in system
\n
Cause
\n\n
\n The maximum number of allowed file descriptors is not high enough.
\nResolving the problem
\n\n \n
\n
\n
\n The allowable file descriptors for the Gentran Integration Suite (GIS) user must be increased.? Per session, this can be done with ulimit. By default, most linux systems are only set to 1024 per user.? A permanent way to make this change (and our recommended method) is to edit /etc/security/limits.conf, giving the GIS user 8192 for the soft limit.
\n\n
More information about system-wide file descriptor settings:
\n\n
The? /proc/sys/fs/file-nr will show the number of allocated file descriptors, the number of file descriptors used, and the maximum number of file descriptors .
The /proc/sys/fs/inode-nr will show the number of descriptors left.
\n
\n \n
\n
\n \n \nHistorical Number
\nPRI6676
\nProduct Alias/Synonym
\n\n
Fact
\n
Gentran Integration Suite
? Release 3.1
Red Hat Linux AS 2.1
SCI67669
\n
",
+ "title": "IBM dbverify does not work with default Oracle character set WE8MSWIN1252 on Windows. - United States",
+ "text": "Database Performance;Mapping; Translation;Operating Environment; STERLINGFAQ TECHNOTE (FAQ)\n\nQUESTION\n dbverify does not work with default Oracle character set WE8MSWIN1252 on Windows. \n\nANSWER\n\n\n 1. \n 2. Does Sterling MCF 8.x support using Oracle default character set i.e. WE8MSWIN1252? Why?\n \n No. WE8MSWIN1252 is not a Unicode character set and has limitations in storing some of the multilingual characters. For Ex: Japanese, German etc. Third party vendor Oracle recommends using the Unicode character set as of Oracle version 9i.\n \n \n 3. \n 4. Which is the recommended character set for Sterling MCF 8.x version and why? \n \n AL32UTF-8 or the UTF-16 character set is recommended. Reference: Installation_Guide.pdf -> Section entitled \"Installing Oracle (UNIX/Linux).\"\n AL32UTF-8 is a global character set. It can be used to store all the Unicode characters and the number of bytes used to store each of the character is relatively less (1-4 bytes).\n \n \n 5. \n 6. When Oracle is installed on Windows XP, default character set provided for new database is WE8MSWIN1252. Does this mean we should not install Oracle in Windows XP at all?\n \n We can definitely install Oracle on Windows XP. When the user creates a new database, the default character set needs to be changed accordingly. Kindly refer to Section entitled \"Installing Oracle (Windows)\" from the MCF Installation_Guide.pdf for more information.\n \n \n 7. \n 8. Is dbverify dependent on the character set? If yes, why?\n \n Yes. dbverify generates DDL\u2019s based on how Oracle stores the characters in the database. Alter statements are generated based on the number of bytes occupied. dbverify is designed to identify and generate the differences depending on the character set used.\n \n \n 9. \n 10. Is it mandatory for customers to switch to recommended character sets in case of any issues?\n \n Yes. Sterling Commerce product documentation provides the system requirements and specific details about setting up third-party application. This means that the Sterling product has been thoroughly tested and certified by our QA team with these parameters.\n \n \n 11. \n 12. Do we have to re-install the database if tables have already been created?\n \n It is not required to reinstall the database. Using the Database Configuration Assistant tool provided by Oracle, create a new database and create new users and schema as per the recommended character sets mentioned in the product documentation. Run the database scripts available in the MCF \n\n
\nDatabase Performance;Mapping; Translation;Operating Environment; STERLINGFAQ
\n\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n \n\n
Question
\ndbverify does not work with default Oracle character set WE8MSWIN1252 on Windows.
\nAnswer
\n\n \n
\n - \n \n
- Does Sterling MCF 8.x support using Oracle default character set i.e. WE8MSWIN1252? Why?
</ span>
No. WE8MSWIN1252 is not a Unicode character set and has limitations in storing some of the multilingual characters. For Ex: Japanese, German etc. Third party vendor Oracle recommends using the Unicode character set as of Oracle version 9i.
</ span>
\n - Which is the recommended character set for Sterling MCF 8.x version and why?
AL32UTF-8 or the UTF-16 character set is recommended. Reference: Installation_Guide.pdf -> Section entitled "Installing Oracle (UNIX/Linux)."
AL32UTF-8 is a global character set. It can be used to store all the Unicode characters and the number of bytes used to store each of the character is relatively less (1-4 bytes).
\n - When Oracle is installed on Windows XP, default character set provided for new database is WE8MSWIN1252. Does this mean we should not install Oracle in Windows XP at all?
</ span>
We can definitely install Oracle on Windows XP. When the user creates a new database, the default character set needs to be changed accordingly. Kindly refer to Section entitled "Installing Oracle (Windows)" from the MCF Installation_Guide.pdf for more information.
\n - Is dbverify dependent on the character set? If yes, why?
Yes. dbverify generates DDL’s based on how Oracle stores the characters in the database. Alter statements are generated based on the number of bytes occupied. dbverify is designed to identify and generate the differences depending on the character set used.
\n - Is it mandatory for customers to switch to recommended character sets in case of any issues?
Yes. Sterling Commerce product documentation provides the system requirements and specific details about setting up third-party application. This means that the Sterling product has been thoroughly tested and certified by our QA team with these parameters.
\n - Do we have to re-install the database if tables have already been created?
It is not required to reinstall the database. Using the Database Configuration Assistant tool provided by Oracle, create a new database and create new users and schema as per the recommended character sets mentioned in the product documentation. Run the database scripts available in the MCF <INSTALL_DIR>/database folder to create the tables, indices, etc. that get generated when the product is installed for the first time. We can also use a database export/import option feature if required.
Creating a new database and new schema/user is a one time set-up and it is always good to be on the recommended and supported versions by Sterling. This will help prevent encountering any unknown problems with dbverify not generating the differences or generating incorrect differences, and save time in rounds of simulation and debugging.
\n - How to find which character set is used in the database?
Run the query: select * from nls_database_parameters; Check for the value in the parameter NLS_CHARACTERSET. \n
\n \n
\n Historical Number
\nFAQ3547
\n\n
\n\n\n\n
\nWS-Policy Multi-Protocol Gateway xs xg xi xb xm
\n\n\n \n \n
\n
\n
\nTechnote (FAQ)
\n \n
\n
\n
\n \n
Question
\nThe Multi-Protocol Gateway supports several options for request and response type. What settings do I choose to properly handle message requests and responses when I want to enforce WS-MediationPolicy or my own custom policy domain? How do I ensure that messages that do not match a modeled endpoint (such as, the endpoint that is specified in the WebSphere Service Registry and Repository REST Service Endpoint object) are rejected properly?
\nCause
\n\n
Additionally, the Multi-Protocol Gateway Policy (Processing Policy) must be configured properly to ensure that messages that do not match a modeled endpoint are rejected by the gateway. This configuration ensures that messages, which are not intended to pass to the back end, are rejected.\n
\n
For more information about how to properly reject messages with a DataPower appliance processing policy, see technote 1640935 \n How to define the default behavior when no processing policy rules match.\n
\n The Multi-Protocol Gateway has options to specify the traffic type that originates from the server and from the client. When the request or response type is specified as SOAP, XML, or JSON, optimization can be applied to manage the messages of the specific content-type. If the request or response type is specified as non-XML (in the CLI, this is "preprocessed") or pass through (in the CLI, this is "unprocessed"), then special message handling optimization cannot be applied.
\nAdditionally, the Multi-Protocol Gateway Policy (Processing Policy) must be configured properly to ensure that messages that do not match a modeled endpoint are rejected by the gateway. This configuration ensures that messages, which are not intended to pass to the back end, are rejected.\n
\n
For more information about how to properly reject messages with a DataPower appliance processing policy, see technote 1640935 \n How to define the default behavior when no processing policy rules match.\n
\n
Answer
\n\n
\n When the request or response type is JSON: \n
\n When the request or response types are not SOAP, XML or JSON (for example, text or binary): \n
For policy enforcement, the type of "Pass through" (unprocessed) for request or response is not recommended. With this setting, policy enforcement is bypassed on messages that do not contain a body (HTTP GET, HEAD, DELETE). Using this type can lead to unexpected results.\n
\n The Multi-Protocol Gateway must be configured to properly handle the message request and message response.
\n
When the request or response type is SOAP or XML:
- \n
- Set the Request Type and Response Type properties for the Multi-Protocol Gateway (SOAP/XML) \n
- Use default-accept-service-providers as the Multi-Protocol Gateway Processing Policy, or create your own Processing Policy with a "match-all" request rule that contains a filter action that references store:///filter-accept-service-providers.xsl. \n
- For WS-MediationPolicy, the ExecuteXSL and ValidateMessage behaviors apply to XML and SOAP messages only \n
\n When the request or response type is JSON: \n
- \n
- Set the Request Type and Response Type properties for the Multi-Protocol Gateway (JSON) \n
- Use default-accept-service-providers as the Processing Policy for the Multi-Protocol Gateway, or create your own Processing Policy with a "match-all" request rule that contains a filter action that references store:///filter-accept-service-providers.xsl, and uses NULL for the Input and Output contexts. \n
- For WS-MediationPolicy, the ExecuteXSL and ValidateMessage behaviors cannot be applied to a JSON message \n
\n When the request or response types are not SOAP, XML or JSON (for example, text or binary): \n
- \n
- Set the Request Type and Response Type properties for the Multi-Protocol Gateway (Non-XML) \n
- The default-accept-service-providers Processing Policy cannot be used as-is. Create your own Processing Policy and ensure that the policy contains a "match-all" request rule that contains a filter action that references store:///filter-accept-service-providers.xsl, and uses NULL for the Input and Output contexts. Ensure that the processing rules created for the processing policy has the Non-XML Processing property set to on. (This option is available only in the Object view for the processing rule, which can be found by typing Processing Rule in the Search field.) \n
- For WS-MediationPolicy, the ExecuteXSL and ValidateMessage behaviors apply to XML messages only and cause an XML schema validation failure for non-XML messages. \n
For policy enforcement, the type of "Pass through" (unprocessed) for request or response is not recommended. With this setting, policy enforcement is bypassed on messages that do not contain a body (HTTP GET, HEAD, DELETE). Using this type can lead to unexpected results.\n
\n
\n \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Integration | \nWebSphere DataPower Integration Appliance XI52 | \n\n | \n | 6.0.0, 6.0.1 | \n\n |
| Business Integration | \nWebSphere DataPower B2B Appliance XB62 | \n\n | \n | 6.0.0, 6.0.1 | \n\n |
| Business Integration | \nWebSphere DataPower Service Gateway XG45 | \n\n | \n | 6.0.0, 6.0.1 | \n\n |
\n
\n
\n \n \n",
+ "title": "IBM Enforcing WS-Policy in the Multi-Protocol Gateway - United States",
+ "text": "WS-Policy Multi-Protocol Gateway xs xg xi xb xm TECHNOTE (FAQ)\n\nQUESTION\n The Multi-Protocol Gateway supports several options for request and response type. What settings do I choose to properly handle message requests and responses when I want to enforce WS-MediationPolicy or my own custom policy domain? How do I ensure that messages that do not match a modeled endpoint (such as, the endpoint that is specified in the WebSphere Service Registry and Repository REST Service Endpoint object) are rejected properly? \n\nCAUSE\nThe Multi-Protocol Gateway has options to specify the traffic type that originates from the server and from the client. When the request or response type is specified as SOAP, XML, or JSON, optimization can be applied to manage the messages of the specific content-type. If the request or response type is specified as non-XML (in the CLI, this is \"preprocessed\") or pass through (in the CLI, this is \"unprocessed\"), then special message handling optimization cannot be applied. \n\n\nAdditionally, the Multi-Protocol Gateway Policy (Processing Policy) must be configured properly to ensure that messages that do not match a modeled endpoint are rejected by the gateway. This configuration ensures that messages, which are not intended to pass to the back end, are rejected. \n\nFor more information about how to properly reject messages with a DataPower appliance processing policy, see technote 1640935 How to define the default behavior when no processing policy rules match. [http://www.ibm.com/support/docview.wss?uid=swg21640935] \nANSWER\nThe Multi-Protocol Gateway must be configured to properly handle the message request and message response. \n\n\nWhen the request or response type is SOAP or XML: \n\n * Set the Request Type and Response Type properties for the Multi-Protocol Gateway (SOAP/XML) \n * Use default-accept-service-providers as the Multi-Protocol Gateway Processing Policy, or create your own Processing Policy with a \"match-all\" request rule that contains a filter action that references store:///filter-accept-service-providers.xsl. \n * For WS-MediationPolicy, the ExecuteXSL and ValidateMessage behaviors apply to XML and SOAP messages only\n\n\nWhen the request or response type is JSON: * Set the Request Type and Response Type properties for the Multi-Protocol Gateway (JSON) \n * Use default-accept-service-providers as the Processing Policy for the Multi-Protocol Gateway, or create your own Processing Policy with a \"match-all\" request rule that contains a filter action that references store:///filter-accept-service-providers.xsl, and uses NULL for the Input and Output contexts. \n * For WS-MediationPolicy, the ExecuteXSL and ValidateMessage behaviors cannot be applied to a JSON message\n\n\nWhen the request or response types are not SOAP, XML or JSON (for example, text or binary): * Set the Request Type and Response Type properties for the Multi-Protocol Gateway (Non-XML) \n * The default-accept-service-providers Processing Policy cannot be used as-is. Create your own Processing Policy and ensure that the policy contains a \"match-all\" request rule that contains a filter action that references store:///filter-accept-service-providers.xsl, and uses NULL for the Input and Output contexts. Ensure that the processing rules created for the processing policy has the Non-XML Processing property set to on. (This option is available only in the Object view for the processing rule, which can be found by typing Processing Rule in the Search field.) \n * For WS-MediationPolicy, the ExecuteXSL and ValidateMessage behaviors apply to XML messages only and cause an XML schema validation failure for non-XML messages. \n\n\nFor policy enforcement, the type of \"Pass through\" (unprocessed) for request or response is not recommended. With this setting, policy enforcement is bypassed on messages that do not contain a body (HTTP GET, HEAD, DELETE). Using this type can lead to unexpected results. \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI52 6.0.0, 6.0.1 Business Integration WebSphere DataPower B2B Appliance XB62 6.0.0, 6.0.1 Business Integration WebSphere DataPower Service Gateway XG45 6.0.0, 6.0.1",
+ "metadata": {
+ "sourceDocumentId": "swg21642721",
+ "date": "2014-03-19",
+ "productName": "IBM DataPower Gateways",
+ "productId": "SS9H2Y,SSHT9H,SSHTED,SSNR47",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21642721"
+ }
+ },
+ "swg24041725": {
+ "id": "swg24041725",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nDownloadable files
\n \n
\n
\n
\n
\n
\n
\n \n \n\n
Abstract
\nThis cumulative fix pack updates Operational Decision Manager V8.8.0 to V8.8.0.1.
\nDownload Description
\n\n
\n Installing with the Installation Manager command line: \n
\n Applying the fix pack\n
After you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack.\n
\n This fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.8.0 can use this fix pack.
How to install the fix pack
For each Operational Decision Manager component that you use:
- \n
- Download its file in the following table.
Change <OS> to match your platform: AIX, HPUX, LIN_PPC, LIN_S390, LIN_X86, OS400, SOL_SPARC, SOL_X86, and WIN. \n - Extract the contents of the download file to a new folder. Use the corresponding folder name in the table. \n
- If you use WebSphere Application Server, download the profile templates for your component. \n
\n \n \n
\n
\n Installing with IBM Installation Manager: \n | Component | \nDownload file | \nFolder name (InstallDir) | \nNote | \n
| Decision Server Insights | \n8.8.0-WS-ODM_DSI-<OS>-FP001.zip | \nDSI | \nOnly available for Linux (LIN) and Windows (WIN). | \n
| Decision Center | \n8.8.0-WS-ODM_DC-<OS>-FP001.zip | \nWDC | \nFor Windows and Linux, use <install path of ODM 8.8.0>/jdk/bin/jar xf to extract files in the WDC directory. | \n
| Decision Server Rules | \n8.8.0-WS-ODM_DSR-<OS>-FP001.zip | \nDSR | \n|
| Decision Server Events | \n8.8.0-WS-ODM_DSE-<OS>-FP001.zip | \nDSE | \n|
| Decision Center profile templates for WebSphere Application Server | \n8.8.0-WS-ODM_PTDC-FP001.zip | \nWDC_PT | \n|
| Decision Server Rules profile templates for WebSphere Application Server | \n8.8.0-WS-ODM_PTR-FP001.zip | \nDSR_PT | \n|
| Decision Server Events profile templates for WebSphere Application Server | \n8.8.0-WS-ODM_PTE-FP001.zip | \nDSE_PT | \n
- \n
- Launch IBM Installation Manager. \n
- Open File > Preferences > Repositories. \n
- For each component that you use:
a. Click Add Repository.
b. Browse to the extracted folder <InstallDir>/updates.
c. Select the repository.config file. \n - Make sure the repositories are selected in Repositories. \n
- Click Apply to save your changes, and click OK to close Repositories. \n
- Click Update to update your installation. \n
- Follow the instructions in the installation manager to complete the installation. \n
\n Installing with the Installation Manager command line: \n
- \n
- Locate the imcl command under <IM installation>/eclipse/tools. \n
- Run the command imcl updateAll -repositories WDC/updates, DSR/updates, DSE/updates -acceptLicense. \n
- \n
- Use the option -installDirectory <install path of ODM 8.8.0> to update a specific installation. \n
- If you update only one component, specify the repository accordingly. \n
\n Applying the fix pack\n
After you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack.\n
Download package
\n\n \n
\n \n
Problems solved
\n \n
\n \n \n
\n
\n | Download | \nRELEASE DATE | \nLANGUAGE | \nSIZE(Bytes) | \nDownload Options What is Fix Central(FC)? What is DD? | \n
|---|---|---|---|---|
| ODM 8.8.0.1 AIX | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 HPUX | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Linux PPC | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Linux x86 | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Linux zSeries | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 OS/400 | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Solaris 32-bit SPARC | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Solaris 64-bit SPARC | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Solaris 32-bit x86 | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Solaris 64-bit x86 | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.0.1 Windows | \n25 Feb 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Integration | \nIBM Operational Decision Manager Advanced | \n\n | \n | \n | \n |
| Business Integration | \nIBM Operational Decision Manager Express | \n\n | \n | \n | \n |
| Business Integration | \nIBM Operational Decision Manager for z/OS | \n\n | \n | \n | \n |
\n
\n
Problems (APARS) fixed
Problems (APARS) fixed
\n
",
+ "title": "IBM Operational Decision Manager V8.8.0.1 Fix Pack - United States",
+ "text": " DOWNLOADABLE FILES\n\nABSTRACT\n This cumulative fix pack updates Operational Decision Manager V8.8.0 to V8.8.0.1. \n\nDOWNLOAD DESCRIPTION\nThis fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.8.0 can use this fix pack.\n\n\nHow to install the fix pack\nFor each Operational Decision Manager component that you use: \n\n 1. Download its file in the following table. \n Change
\n
",
+ "title": "IBM Installing embeded WAS Refresh Pack2, embeded-WAS Fixpack13 and Java SDK Fixpack11 from WPG 6.0 Fixpack5 or above on AIX - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n When performing HUB installation from WebSphere Partner Gateway 6.0 Fixpack 5 or above failure of embeded WebSphere Application Server (WAS) Refresh Pack2, embeded-WAS Fixpack13 and Java SDK Fixpack11 may occur.\n\n\nCAUSE\nIn this particular incident the /tmp directory did not have enough diskspace to install embeded WAS Refresh Pack2 during WPG 6.0 Fixpack HUB installation, error below from \n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n
\n \n
Question
\n When performing HUB installation from WebSphere Partner Gateway 6.0 Fixpack 5 or above failure of embeded WebSphere Application Server (WAS) Refresh Pack2, embeded-WAS Fixpack13 and Java SDK Fixpack11 may occur.
Cause
\n\n
\n In this particular incident the /tmp directory did not have enough diskspace to install embeded WAS Refresh Pack2 during WPG 6.0 Fixpack HUB installation, error below from <WPG installed dir>/was/logs/update/6.0-WS-WASEmbeded-AIX-RP0000002.install:
(Feb 21, 2008 3:29:53 PM), UpdateInstaller,
com.ibm.ws.install.ni.ismp.actions.MaintenancePrereqCheckAction, err,
CWUPI0025E:
There is insufficient free disk space on the system:
/opt/wpg/was:
Required: 400 MB
Available: 905 MB
/tmp:
Required: 250 MB
Available: 246 MB
Ensure there is enough free disk space on all required filesystems and retry the operation.
When Refresh Pack2 installed failed the installation of Fixpack 13 and Java SDK FP 11 failed also, because they require embeded WAS to be at v6.0.2 or above.
\n
Answer
\n\n
\n Resolve the problem that caused the installation failure review the install logs located <WPG Installed dir>/was/logs/update/.
\nFollow these steps to install embeded WAS Support Pack2, embeded-WAS Fixpack13 and Java SDK Fixpack11 on AIX:
1) Stop all WPG servers,i.e. bcgconsole, bcgreceiver and bcgdocmgr
Installation of embeded WAS Refresh Pack2 (6.0.2)
2) Login in as root user. To run this maintenance pack you need to be logged on a root/Administrator else it does not allow you to proceed with the installation.
3) Copy the folder updateInstaller from Fixpack installer/embedWAS/Refreshpack to the same Installroot location as your WAS directory which is being used by WPG hub. e.g. If WPG hub is installed in \\opt\\IBM\\bcghub then copy "Fixpack installer/embedWAS/Refreshpack/updateinstaller"
to \\opt\\IBM\\bcghub\\was.
4) Run the Update Installer(update) present under this updateInstaller folder to launch the GUI
Note: If installing remotely or from command line use "./update -console" or "./update -silent"
5) Click Next to continue on the Welcome panel.
6) Make sure the directory name listed for the product installation is correct and click Next
7) Select the 'Install maintenance package' radio button and click Next
8) Make sure the path listed points to the proper Refresh Pack to be applied to the product(should be the .pak file present under \\opt\\IBM\\bcghub\\was\\updateinstaller\\maintenance) and click Next
9) Click Next to begin copying the JRE to the updateinstaller directory.
10) Click Relaunch to restart the Update Installer with the JRE copied to the updateinstaller directory.
11) The path to the maintenance package is displayed.
Note: The wizard will remember all values from the previous launch. Click Next to continue
12) Click Next to begin applying the Refresh Pack
13) Click Finish when the Refresh Pack application is complete
14) Delete the updateinstaller directory (e.g. \\opt\\IBM\\bcghub\\was\\updateinstaller).
15) Now go to \\opt\\IBM\\bcghub\\was\\bin and check the version of the WAS installed. You can do this by giving the command ./versionInfo.sh. The version should be 6.0.2 Installation of embeded-WAS Fixpack 13 (6.0.2.13)
16) Copy the folder updateInstaller from Fixpack_installer/embedWAS/Fixpack to the same Installroot location as your WAS directory which is being used by WPG hub. e.g. If WPG hub is installed in \\opt\\IBM\\bcghub then copy "Fixpack_installer/embedWAS/Fixpack/updateinstaller" to \\opt\\IBM\\bcghub\\was.
17) Run the Update Installer(update) present under this updateInstaller folder to launch the GUI
Note: If installing remotely or from command line use "./update -console" or "./update -silent"
18) Click Next to continue on the Welcome panel.
19) Make sure the directory name listed for the product installation is correct (should be the .pak file present under \\opt\\IBM\\bcghub\\was\\updateinstaller\\maintenance) and click Next
20) Select the 'Install maintenance package' radio button and click Next
21) Make sure the path listed points to the proper Fix Pack to be applied to the product and click Next
22) Click Next to begin copying the JRE to the updateinstaller directory.
23) Click Relaunch to restart the Update Installer with the JRE copied to the updateinstaller directory.
24) The path to the maintenance package is displayed.
Note: The wizard will remember all values from the previous launch. Click Next to continue
25) Click Next to begin applying the Fix Pack
26) Click Finish when the Fix Pack application is complete
27) Delete the updateinstaller directory (e.g. \\opt\\IBM\\bcghub\\was\\updateinstaller).
28) Now go to \\opt\\IBM\\bcghub\\was\\bin and check the version of the WAS installed. You can do this by giving the command ./versionInfo.sh. The version should be 6.0.2.13 Installation of Java SDK Fixpack11
29) Copy the folder updateInstaller from Fixpack_installer/embedWAS/JDKFixpack
to the same Installroot location as your WAS directory which is being used by WPG hub. e.g. If WPG hub is installed in \\opt\\IBM\\bcghub then copy "Fixpack_installer/embedWAS/JDKFixpack/updateinstaller" to \\opt\\IBM\\bcghub\\was.
30) Run the Update Installer(update.exe) present under this updateInstaller folder to launch the GUI
Note: If installing remotely or from command line use "./update -console" or "./update -silent"
31) Click Next to continue on the Welcome panel.
32) Make sure the directory name listed for the product installation is correct(should be the .pak file present under \\opt\\IBM\\bcghub\\was\\updateinstaller\\maintenance) and click Next
33) Select the 'Install maintenance package' radio button and click Next
34) Make sure the path listed points to the proper Fix Pack to be applied to the product and click Next
35) Click Next to begin copying the JRE to the updateinstaller directory.
36) Click Relaunch to restart the Update Installer with the JRE copied to the updateinstaller directory.
37) The path to the maintenance package is displayed.
Note: The wizard will remember all values from the previous launch. Click Next to continue
38) Click Next to begin applying the JDK Fix Pack
39) Click Finish when the Fix Pack application is complete
40) Delete the updateinstaller directory (e.g. \\opt\\IBM\\bcghub\\was\\updateinstaller).
41) Now go to \\opt\\IBM\\bcghub\\was\\java\\bin and check the version of the JDK installed. You can do this by giving the command ./java -version
The version should be:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM build cxia32142-20060421 (SR5) (JIT enabled: jitc))
42) Now you would need to change the user permissions from root to bcguser. Since we ran the maintenance pack as root some of the folders user permission's would have been updated to root. We would need to revert this back to bcguser. You can do this by going to the /WAS folder, eg. /opt/IBM/bcghub/was and run the command chown -R bcguser:bcggroup *
This will change the user permission's of all the folders under WAS to bcguser.
43) Start the servers.
\n
\n \n
\n
\n \n \n\n
",
+ "title": "IBM Omnifind 9.1.0 crashes on search when there is an increased load - United States",
+ "text": "Omnifind 9.1.0; heapdump; Out of Memory; REST API TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n \"Out of Memory\" errors are thrown when the system load increases, both in search requests and indexed documents. The search is performed on a custom application using a REST API. \n\nSYMPTOM\nThe increased load will cause the REST API to return zero results.\n\n\nJavacore log files show the following Out Of Memory Error:\n\n0SECTION TITLE subcomponent dump routine\n\nNULL ===============================\n\n1TISIGINFO Dump Event \"systhrow\" (00040000) Detail \"java/lang/OutOfMemoryError\" received \n1TIDATETIME Date: 2015/11/16 at 13:07:25\n1TIFILENAME Javacore filename: /collections/esdata/logs/javacore.20151116.130720.8175.0009.txt\n1TIREQFLAGS Request Flags: 0x81 (exclusive+preempt)\n1TIPREPSTATE Prep State: 0x4 (exclusive_vm_access)\n\nbase of process ID ( 8175 ) via ccl_doctribicap1_0.log file the failing session is col_normativa.searcher.node1\n\nother javacore files also show that the issue is with col_normativa.searcher.node1 session:\n\nNov 16, 2015 12:57:10 PM com.ibm.es.ccl.server.responders.sys.SessionAttachMessageHandler doMessage\nINFO: Session \"col_normativa.searcher.node1\" was attached PID=8175\n\n\n\nCAUSE\nHeapdump size is too small to cope with the increased load and is causing the errors.\n\n\nDIAGNOSING THE PROBLEM\nAnalyse the Javacore log files for the above error.\n\n\n\nRESOLVING THE PROBLEM\n \n\n * Increase a max_heap for this session according to col_normativa_config.ini config files:\n \n session4.hard_max_heap=10,8192\n session4.id=col_normativa.searcher.node1\n session4.max_heap=2048\n session4.nodeid=node1\n \n Good practice will be to increase max_heap for col_normativa.searcher.node2 from 1536 to 3096 as well. Try to keep both those numbers the same:\n session5.id=col_normativa.searcher.node2\n session5.max_heap=1536\n \n System requires sufficient RAM to cope with this increased heap size.\n \n * After increasing max_heap you need to restart OmniFind (all nodes):\n esadmin system stopall\n esadmin system startall\n \n * Also another suggestion is to install the latest Fix Pack for IBM Omnifind.",
+ "metadata": {
+ "sourceDocumentId": "swg21971901",
+ "date": "2016-12-07",
+ "productName": "OmniFind Enterprise Edition",
+ "productId": "SS5SQ7",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21971901"
+ }
+ },
+ "swg21508058": {
+ "id": "swg21508058",
+ "content": "\n\n
\nOmnifind 9.1.0; heapdump; Out of Memory; REST API
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n
\n \n \n\n
Problem(Abstract)
\n"Out of Memory" errors are thrown when the system load increases, both in search requests and indexed documents. The search is performed on a custom application using a REST API.
\nSymptom
\n\n
\n The increased load will cause the REST API to return zero results.
Javacore log files show the following Out Of Memory Error:
0SECTION TITLE subcomponent dump routine
NULL ===============================
1TISIGINFO Dump Event "systhrow" (00040000) Detail "java/lang/OutOfMemoryError" received
1TIDATETIME Date: 2015/11/16 at 13:07:25
1TIFILENAME Javacore filename: /collections/esdata/logs/javacore.20151116.130720.8175.0009.txt
1TIREQFLAGS Request Flags: 0x81 (exclusive+preempt)
1TIPREPSTATE Prep State: 0x4 (exclusive_vm_access)
base of process ID ( 8175 ) via ccl_doctribicap1_0.log file the failing session is col_normativa.searcher.node1
other javacore files also show that the issue is with col_normativa.searcher.node1 session:
Nov 16, 2015 12:57:10 PM com.ibm.es.ccl.server.responders.sys.SessionAttachMessageHandler doMessage
INFO: Session "col_normativa.searcher.node1" was attached PID=8175
\n
Cause
\n\n
\n Heapdump size is too small to cope with the increased load and is causing the errors.
\n\n
Diagnosing the problem
\n\n
\n \n Analyse the Javacore log files for the above error.
\nResolving the problem
\n\n
\n \n
- \n
- Increase a max_heap for this session according to col_normativa_config.ini config files:
session4.hard_max_heap=10,8192
session4.id=col_normativa.searcher.node1
session4.max_heap=2048
session4.nodeid=node1
Good practice will be to increase max_heap for col_normativa.searcher.node2 from 1536 to 3096 as well. Try to keep both those numbers the same:
session5.id=col_normativa.searcher.node2
session5.max_heap=1536
System requires sufficient RAM to cope with this increased heap size.
\n - After increasing max_heap you need to restart OmniFind (all nodes):
esadmin system stopall
esadmin system startall
\n - Also another suggestion is to install the latest Fix Pack for IBM Omnifind. \n
\n \n
\n \n
\n\n\n\n
\nTPAESCCD; omnibus; netcool; language; en; english
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\nGetting above error when you try to create ticket in Netcool/Omnibus Gateway for TSRM
\nSymptom
\n\n
\n You are not able to create ticket in SCCD using Netcool/Omnibus Gateway for TSRM
\n\n
Resolving the problem
\n\n
\n In later version of Netcool/Omnibus Gateway for TSRM (e.g. 7.3), Netcool/Omnibus Gateway for TSRM does not use TDI to integrate with SCCD. By default, it is using language code EN. If you have other language code, e.g ZH (Chinese Simplified), you have to configure as followed :-
1. Stop all the OMNIBUS processes using the commands:
/etc/init.d/nco stop and /etc/init.d/webgui stop.
2. Stop all the IMPACT processes using the command: /etc/init.d/impact stop.
3. Backup your /IBM/tivoli/netcool/omnibus/etc/GAT_TSRM.props
(a) Edit GAT_TSRM.props and add/uncomment following line (e.g) :-
Gate.TSRM.Language : 'ZH'
4. Backup your /IBM/tivoli/netcool/omnibus/gates/tsrm/query.xml.template
(a) Edit query.xml.template (e.g) :-
baseLanguage="ZH"
transLanguage="ZH"
5. Restart all the OMNIBUS processes using the commands:
/etc/init.d/nco start and /etc/init.d/webgui start.
6. Restart all the IMPACT process using the command:
/etc/init.d/impact start.
After this, you will not get error 'BMXAA4102E Language code EN not used' and able to create ticket in SCCD using Netcool/Omnibus Gateway for TSRM
\n\n
\n \n
\n
\n \n \n",
+ "title": "IBM BMXAA4102E Language code EN not used - United States",
+ "text": "TPAESCCD; omnibus; netcool; language; en; english TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Getting above error when you try to create ticket in Netcool/Omnibus Gateway for TSRM \n\nSYMPTOM\nYou are not able to create ticket in SCCD using Netcool/Omnibus Gateway for TSRM\n\n\nRESOLVING THE PROBLEM\nIn later version of Netcool/Omnibus Gateway for TSRM (e.g. 7.3), Netcool/Omnibus Gateway for TSRM does not use TDI to integrate with SCCD. By default, it is using language code EN. If you have other language code, e.g ZH (Chinese Simplified), you have to configure as followed :-\n1. Stop all the OMNIBUS processes using the commands: \n/etc/init.d/nco stop and /etc/init.d/webgui stop.\n2. Stop all the IMPACT processes using the command: /etc/init.d/impact stop.\n3. Backup your /IBM/tivoli/netcool/omnibus/etc/GAT_TSRM.props \n(a) Edit GAT_TSRM.props and add/uncomment following line (e.g) :- \nGate.TSRM.Language : 'ZH' \n4. Backup your /IBM/tivoli/netcool/omnibus/gates/tsrm/query.xml.template\n(a) Edit query.xml.template (e.g) :-\nbaseLanguage=\"ZH\" \ntransLanguage=\"ZH\"\n5. Restart all the OMNIBUS processes using the commands:\n/etc/init.d/nco start and /etc/init.d/webgui start. \n6. Restart all the IMPACT process using the command:\n/etc/init.d/impact start. \n\nAfter this, you will not get error 'BMXAA4102E Language code EN not used' and able to create ticket in SCCD using Netcool/Omnibus Gateway for TSRM",
+ "metadata": {
+ "sourceDocumentId": "swg21508058",
+ "date": "2011-08-10",
+ "productName": "Control Desk",
+ "productId": "SSWT9A",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21508058"
+ }
+ },
+ "swg21423793": {
+ "id": "swg21423793",
+ "content": "
\n
",
+ "title": "IBM \"-2147467259:The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value\" when running Shareholding and Investment reports - United States",
+ "text": " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User clicks \"Group - Reports - Shareholdings and Investments\". User chooses values/parameters, and clicks 'Preview'. User receives error message.\n\nNOTE: Typically the errors only occur when running the reports for certain compinations of parameters (e.g. selecting specific 'bad' companies).\n\nA similar error message occurs when user runs \"Group - Reconcile - Investment Elimination Template\". \n\nSYMPTOM\nShareholdings and Investments \n\nError\n-2147467259:The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.\n\n\n * Investment Elimination Template\n\nScreen: \nIBM Cognos 8 Controller \nUnhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. \n\nSystem.Web.Services.Protocols.SoapException: Server was unable to process request. ---> \nSystem.Runtime.InteropServices.COMException (0x80040E07): The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value. \n<....> \n[Details] [Continue] [Quit] \n\nEvent Log:\nEvent Type: Warning\nEvent Source: Cognos Controller\nEvent Category: None\nEvent ID: 0\nDate: 04/07/2012\nTime: 09:05:25\nUser: N/A\nComputer: SERVERNAME\nDescription:\nError occured at 04/07/2012 09:05:25 in IBM Cognos 8 Controller, Error No=5, Source=FrangoDirect.RepRecSharesAndInvD.ReconcileInvestments#ControllerProxyClient.frmRepReconcileInvestments.IFormStandardReport_CreateReportData:FrangoClient.clsStandardReports.CreateReport:FrangoClient.clsStandardReports.CreateReports, Description=System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Runtime.InteropServices.COMException (0x80040E07): The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.\nat FrReportB.RepRecSharesAndInvClass.ReconcileInvestmentsCRN(String sGuid, String sUser, String sAcqCurr, Int16 iReport, String sConsType, String sCompanyGroup, Int32 lNumLevels, String sAct, String sPeriod, Boolean bSort, Int32 lLocale, Object sXmlDoc)\nat Cognos.Controller.Proxy.CCRWS.RepRecSharesAndInv_ReconcileInvestmentsCRN(String sGuid, String sUser, String sAcqCurr, Int16 iReport, String sConsType, String sCompanyGroup, Int32 lNumLevels, String sAct, String sPeriod, Boolean bSort, Int32 lLocale, Object sXmlDoc)\n--- End of inner exception stack trace ---, HelpFile= HelpContext=0\n\nCAUSE\nInvalid entries/data inside the Controller application database. \n\n \nMore Information:\nOn one real-life customer case, the problem was caused by invalid data inside the database tables \"xacqmain\" and \"xacqamount\", which relate to the Acquisition register. In that case, they contained some rows which contained values for date (such as 20050231, 20070431, 20050931) which were not valid.\n\n\nRESOLVING THE PROBLEM\nContact IBM Support for assistance in modifying your Controller database in order to correct the invalid data.",
+ "metadata": {
+ "sourceDocumentId": "swg21423793",
+ "date": "2012-07-04",
+ "productName": "Cognos Controller",
+ "productId": "SS9S6B",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21423793"
+ }
+ },
+ "swg21674709": {
+ "id": "swg21674709",
+ "content": "\n\n
\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\n User clicks "Group - Reports - Shareholdings and Investments". User chooses values/parameters, and clicks 'Preview'. User receives error message.
NOTE: Typically the errors only occur when running the reports for certain compinations of parameters (e.g. selecting specific 'bad' companies).
A similar error message occurs when user runs "Group - Reconcile - Investment Elimination Template".
Symptom
\n\n
IBM Cognos 8 Controller\n
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.\n
\n
System.Web.Services.Protocols.SoapException: Server was unable to process request. --->\n
System.Runtime.InteropServices.COMException \n (0x80040E07): The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.\n
<....>\n
[Details] [Continue] [Quit] \n
\n Shareholdings and Investments
\nError
-2147467259:The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.
- \n
- Investment Elimination Template \n
IBM Cognos 8 Controller\n
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.\n
\n
System.Web.Services.Protocols.SoapException: Server was unable to process request. --->\n
System.Runtime.InteropServices.COMException \n (0x80040E07): The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.\n
<....>\n
[Details] [Continue] [Quit] \n
\n
Event Log:
Event Type: Warning
Event Source: Cognos Controller
Event Category: None
Event ID: 0
Date: 04/07/2012
Time: 09:05:25
User: N/A
Computer: SERVERNAME
Description:
Error occured at 04/07/2012 09:05:25 in IBM Cognos 8 Controller, Error No=5, Source=FrangoDirect.RepRecSharesAndInvD.ReconcileInvestments#ControllerProxyClient.frmRepReconcileInvestments.IFormStandardReport_CreateReportData:FrangoClient.clsStandardReports.CreateReport:FrangoClient.clsStandardReports.CreateReports, Description=System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Runtime.InteropServices.COMException (0x80040E07): The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.
at FrReportB.RepRecSharesAndInvClass.ReconcileInvestmentsCRN(String sGuid, String sUser, String sAcqCurr, Int16 iReport, String sConsType, String sCompanyGroup, Int32 lNumLevels, String sAct, String sPeriod, Boolean bSort, Int32 lLocale, Object sXmlDoc)
at Cognos.Controller.Proxy.CCRWS.RepRecSharesAndInv_ReconcileInvestmentsCRN(String sGuid, String sUser, String sAcqCurr, Int16 iReport, String sConsType, String sCompanyGroup, Int32 lNumLevels, String sAct, String sPeriod, Boolean bSort, Int32 lLocale, Object sXmlDoc)
--- End of inner exception stack trace ---, HelpFile= HelpContext=0
Cause
\n\n
\n Invalid entries/data inside the Controller application database.
\n
More Information:
On one real-life customer case, the problem was caused by invalid data inside the database tables "xacqmain" and "xacqamount", which relate to the Acquisition register. In that case, they contained some rows which contained values for date (such as 20050231, 20070431, 20050931) which were not valid.
\n
Resolving the problem
\n\n
\n \n Contact IBM Support for assistance in modifying your Controller database in order to correct the invalid data.
\n\n \n
\n \n
\n \n \n\n
\n\n\n\n
\nrelease notice; downloads; Gateway for Tivoli EIF; nco-g-tivoli-eif
\n\n\n \n \n
\nNews
\n \n
\n
\n \n
Abstract
\nThe Installation Manager version of the Netcool/OMNIbus Gateway for Tivoli EIF will be available to download from June 12, 2014.
\nContent
\n\n
\n \n
You can download this package from the IBM Passport Advantage website:
\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm
\nNetcool/OMNIbus V8.1
\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for both Linux and AIX. These are the only Operating Systems that are currently supported. To obtain this new package, use the Find by part number field to search for part number: CIZZ5EN
\nNetcool/OMNIbus V7.3.0, 7.3.1, or 7.4.0
\nIf you are running Netcool/OMNIbus V7.3.0, 7.3.1, or 7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.
\n\n \n \n
\n
\n | Part number | \nOperating System | \n
| CIDW2EN | \nAIX | \n
| CIRZ6EN | \nHP-UX PA-RISC | \n
| CIRZ7EN | \nHP-UX Itanium | \n
| CIDW3EN | \nLinux | \n
| CIDW0EN | \nLinux for zSeries | \n
| CIRZ5EN | \nSolaris | \n
| CIDW4EN | \nWindows | \n
Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.
\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:
\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html
\n \n\n
\n \n
\n
\n \n \n",
+ "title": "IBM Netcool/OMNIbus Integrations Release Notice - Netcool/OMNIbus Gateway for Tivoli EIF (nco-g-tivoli-eif-4_0) - United States",
+ "text": "release notice; downloads; Gateway for Tivoli EIF; nco-g-tivoli-eif NEWS\n\nABSTRACT\n The Installation Manager version of the Netcool/OMNIbus Gateway for Tivoli EIF will be available to download from June 12, 2014. \n\nCONTENT\n \n\nYou can download this package from the IBM Passport Advantage website:\n\nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nNetcool/OMNIbus V8.1\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for both Linux and AIX. These are the only Operating Systems that are currently supported. To obtain this new package, use the Find by part number field to search for part number: CIZZ5EN\n\nNetcool/OMNIbus V7.3.0, 7.3.1, or 7.4.0\n\nIf you are running Netcool/OMNIbus V7.3.0, 7.3.1, or 7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CIDW2EN AIX CIRZ6EN HP-UX PA-RISC CIRZ7EN HP-UX Itanium CIDW3EN Linux CIDW0EN Linux for zSeries CIRZ5EN Solaris CIDW4EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]",
+ "metadata": {
+ "sourceDocumentId": "swg21674709",
+ "date": "2015-01-29",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21674709"
+ }
+ },
+ "swg21698831": {
+ "id": "swg21698831",
+ "content": "
\n
\n\n\n\n
\nCVE-2015-0138
\n\n\n \n \n
\nSecurity Bulletin
\n \n
\n
\n\n
Summary
\nThe “FREAK: Factoring Attack on RSA-EXPORT keys" TLS/SSL client and server vulnerability affects IBM WebSphere Application Server Versions 6.1, 7, 8, 8.5, and 8.5.5 that are used by IBM Rational ClearCase.
\nVulnerability Details
\n\n
\n Please consult the Security Bulletin: Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) for vulnerability details and information about fixes.
\nCVEID: CVE-2015-0138
DESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers.
This vulnerability is also known as the FREAK attack.
\nCVSS Base Score: 4.3
CVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)
Affected Products and Versions
\n\n
\n Security Bulletin: Vulnerabilities in GSKit affect IBM Rational ClearCase (CVE-2015-0138)\n
\n Security Bulletin: Vulnerabilities in OpenSSL affect Rational ClearCase (CVE-2014-3570, CVE-2014-3572, CVE-2015-0204)\n
\n Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Rational ClearCase (CVE-2015-0138, CVE-2014-6593, CVE-2015-0383, CVE-2015-0410)\n
\n IBM Rational ClearCase, CCRC WAN server/CM Server component.
\nVersions 8.0.0.x, 8.0.1.x:
\n- \n
This vulnerability only applies to the CCRC WAN server component, not to other parts of IBM Rational ClearCase. In addition, this vulnerability only applies if one of these conditions apply: \n
- \n
(a) You have installed CCRC WAN server into an existing profile, and that profile supports a non-default set of ciphers \n
(b) You modified the set of supported ciphers in the WAS profile that was created during installation of ClearCase
\n- \n
This vulnerability only applies to the CM server component, not to other parts of IBM Rational ClearCase. \n
In addition, this vulnerability only applies if you modified the ClearCase WAS profile by changing its list of supported ciphers.
\n\n Security Bulletin: Vulnerabilities in GSKit affect IBM Rational ClearCase (CVE-2015-0138)\n
\n Security Bulletin: Vulnerabilities in OpenSSL affect Rational ClearCase (CVE-2014-3570, CVE-2014-3572, CVE-2015-0204)\n
\n Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Rational ClearCase (CVE-2015-0138, CVE-2014-6593, CVE-2015-0383, CVE-2015-0410)\n
Remediation/Fixes
\n\n
You should verify applying this fix does not cause any compatibility issues.\n
\n Review the security bulletin referenced above and apply the relevant fixes to your WAS installation and WAS profiles used for ClearCase.
\n \n \n
\n
\n | \n \n Affected Versions\n | \n \n \n Applying the fix\n | \n
| 7.1.0.x, 7.1.1.x, and 7.1.2.x | \nDocument 1390803 explains how to update WebSphere Application Server for ClearCase CM Servers at release 7.1.x. Consult those instructions when applying the fix. | \n
| 8.0.0.x 8.0.1.x | \n Apply the appropriate WebSphere Application Server fix directly to your CCRC WAN server host. No ClearCase-specific steps are necessary. | \n
You should verify applying this fix does not cause any compatibility issues.\n
Get Notified about Future Security Bulletins
\nSubscribe to My Notifications to be notified of important product support alerts like this.
\nImportant note
\n \n
\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.
\nReferences
\n \nRelated information
\n \nChange History
\n * 2 April 2015: Original copy published.
* 17 April 2015: updated to cross-reference related fixes.
*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.
\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.
\n\n
\n \n
\n
\n \n \n ",
+ "title": "IBM Security Bulletin: A security vulnerability has been identified in IBM WebSphere Application Server shipped with IBM Rational ClearCase (CVE-2015-0138) - United States",
+ "text": "CVE-2015-0138 SECURITY BULLETIN\n\nSUMMARY\n The \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS/SSL client and server vulnerability affects IBM WebSphere Application Server Versions 6.1, 7, 8, 8.5, and 8.5.5 that are used by IBM Rational ClearCase. \n\nVULNERABILITY DETAILS\nPlease consult the Security Bulletin: Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21698613] for vulnerability details and information about fixes. \n\nCVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. \n\nThis vulnerability is also known as the FREAK attack. \n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [http://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Rational ClearCase, CCRC WAN server/CM Server component. \n\nVersions 8.0.0.x, 8.0.1.x: \n\n * \n * \n * \n (a) You have installed CCRC WAN server into an existing profile, and that profile supports a non-default set of ciphers (b) You modified the set of supported ciphers in the WAS profile that was created during installation of ClearCase\n \n \n\nVersions 7.1.x.x: * \n * \n * In addition, this vulnerability only applies if you modified the ClearCase WAS profile by changing its list of supported ciphers.\n\nNote: other components of ClearCase are subject to the \"FREAK\" attack, as disclosed in the following security bulletins: \nSecurity Bulletin: Vulnerabilities in GSKit affect IBM Rational ClearCase (CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21698750] \nSecurity Bulletin: Vulnerabilities in OpenSSL affect Rational ClearCase (CVE-2014-3570, CVE-2014-3572, CVE-2015-0204) [http://www.ibm.com/support/docview.wss?uid=swg21694288] \nSecurity Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Rational ClearCase (CVE-2015-0138, CVE-2014-6593, CVE-2015-0383, CVE-2015-0410) [http://www.ibm.com/support/docview.wss?uid=swg21698749] REMEDIATION/FIXES\nReview the security bulletin referenced above and apply the relevant fixes to your WAS installation and WAS profiles used for ClearCase.\n\n\n\nAffected Versions Applying the fix 7.1.0.x, 7.1.1.x, and 7.1.2.x Document 1390803 [http://www.ibm.com/support/docview.wss?uid=swg21390803] explains how to update WebSphere Application Server for ClearCase CM Servers at release 7.1.x. Consult those instructions when applying the fix. 8.0.0.x\n8.0.1.x Apply the appropriate WebSphere Application Server fix directly to your CCRC WAN server host. No ClearCase-specific steps are necessary. \nYou should verify applying this fix does not cause any compatibility issues. GET 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\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www-03.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED 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] CHANGE HISTORY\n * 2 April 2015: Original copy published.\n* 17 April 2015: updated to cross-reference related fixes. \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.",
+ "metadata": {
+ "sourceDocumentId": "swg21698831",
+ "date": "2015-04-17",
+ "productName": "Rational ClearCase",
+ "productId": "SSSH27",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21698831"
+ }
+ },
+ "swg21482869": {
+ "id": "swg21482869",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n
\n
\n
\n\n
Question
\n When running an IBM SPSS product License Authorization Wizard the following error presents:
authorization failed the server was unable to establish communication with the data base
end of transaction one or more codes failed
What is causing this problem and how do I correct it?
Cause
\n\n
\n The IBM SPSS product host computer does not have network access to the IBM SPSS licensing servers.
This is normally due to internet communication restrictions (firewall settings) in the local environment where the product host computer is located.
\n
Answer
\n\n
\n If the error presents on a single installation, the simplest approach is license the product via email. This option will automatically appear in the License Authorization Wizard when the error presents.
If the error presents on multiple products, then the best solution is to create an exception in all firewalls between the affected host machines and the internet domain of the IBM SPSS licensing servers:
lm.spss.com
\nRelated information
\n Need more help? Our Statistics forum is Live!
\n
\n \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Analytics | \nSPSS Amos | \n\n | \n | \n | \n |
| Business Analytics | \nSPSS Modeler | \n\n | \n | \n | \n |
| Business Analytics | \nSPSS Text Analytics for Surveys | \n\n | \n | \n | \n |
\n
\n
\n \n \n Historical Number
\n81448
\n",
+ "title": "IBM What can I do about the message 'authorization failed the server was unable to establish communication with the data base - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n When running an IBM SPSS product License Authorization Wizard the following error presents: \n\nauthorization failed the server was unable to establish communication with the data base\nend of transaction one or more codes failed\n\nWhat is causing this problem and how do I correct it? \n\nCAUSE\nThe IBM SPSS product host computer does not have network access to the IBM SPSS licensing servers. \nThis is normally due to internet communication restrictions (firewall settings) in the local environment where the product host computer is located.\n\n\nANSWER\nIf the error presents on a single installation, the simplest approach is license the product via email. This option will automatically appear in the License Authorization Wizard when the error presents.\n\nIf the error presents on multiple products, then the best solution is to create an exception in all firewalls between the affected host machines and the internet domain of the IBM SPSS licensing servers: \n\nlm.spss.com\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\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Business Analytics SPSS Modeler Business Analytics SPSS Text Analytics for Surveys \nHISTORICAL NUMBER\n 81448",
+ "metadata": {
+ "sourceDocumentId": "swg21482869",
+ "date": "2016-11-02",
+ "productName": "SPSS Statistics",
+ "productId": "SSLVMB,SS6A7K,SSLVC7,SS3RA7",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21482869"
+ }
+ },
+ "swg21664767": {
+ "id": "swg21664767",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\n
\nTechnote (FAQ)
\n \n
\n
\n \n
Question
\nWhat is the best practice for upgrading or migrating to a new machine for TFIM?
\nAnswer
\n\n
\n The best practice is to use a two-system method. This procedure is written toward the use case where the Point Of Contact is WebSEAL. This procedure is written to ensure that the any customizations made to TFIM, such as STS modules, pages, and the hostnames used to access the machine will continue to work. In a normal production environment, TFIM is only installed on the deployment manager, and then pushed to the nodes later as part of the domain create and runtime config.
- \n
- The first step is to back up the configuration of your existing environment. This will be used to restore the configuration in the new server. \n
- \n
- Select Tivoli Federated Identity Manager -> Domain Management -> Import and Export Configuration. \n
- Select the appropriate domain. \n
- Click Export Configuration. \n
- When prompted, specify the location where you want to save the exported configuration JAR file. Make a note of this files location. \n
- Click OK. \n
\n - On the new server install a new copy of WebSphere, you can use this opportunity to change WebSphere versions to a currently supported version \n
- \n
- Create the desired server profiles, and apply recommended WebSphere FixPack level. For more information on the current WebSphere FixPack level, see the following
Recommended fixes for WebSphere Application Server \n - If using IHS you may install that now as well. \n
\n - Create the desired server profiles, and apply recommended WebSphere FixPack level. For more information on the current WebSphere FixPack level, see the following
- Restart the Dmgr and do not log into ISC before attempting a TFIM product install. \n
- On the new server install TFIM. When you are given the option to use an existing version of WebSphere Application Server, select Yes for both the management service and console. If you are using a cluster enter the information for the new Dmgr or if using a stand alone WebSphere profile provide the values you set in that profile. \n
- Download the latest WebSphere update installer version 7.0.0.x 32 bit (Issues have been reported with 7.0.0.31). As of April 2016 we recommend the use of WAS UI 7.0.0.29 if you have not applied POODLE fixes to WebSphere and 7.0.0.41 if you have applied POODLE fixes and WebSphere is only using the TLS protocol. To avoid some WebSphere authorization issues we recommend you temporarily disable global security on the Dmgr. Please note that even if you are using WebSphere 8.0 or higher you still need to use the WebSphere 7 UI to apply TFIM FixPacks. This will not cause a problem with the IBM Installation Manager used to install WebSphere versions 8.0 and above. The IBM Installation Manager will continue to be used to apply WebSphere FixPacks for 8.0 and above. The UI 7 is only for TFIM patches. \n
- Optionally you may chose to create the TFIM domain now or after applying the FixPack \n
- If you logged into ISC after installing TFIM and in general before applying any TFIM FixPacks we recommend you restart the Dmgr and install the FixPack before anyone logs into ISC, this is needed before you attempt the FP install to avoid any locked files. \n
- If WAS is not running as the same account you are using to run the Update Installer ensure that groups are set correctly to allow access. In any case, ensure the umask is set to at least 022. \n
- Apply the latest TFIM FixPack from FixCentral
Quick link to TFIM FixPacks on FixCentral
NOTE: If a domain is not created before application of Tivoli Federated Identity Manager fix pack, the fix pack installation completes successfully with a "Partially Successful" message. You can safely ignore this error. If you get any other errors, do not close the Update Installer with Ctrl-C use the finish buttons so that the Update Installer can finish and clean up. \n - Create and deploy a domain. \n
- \n
- Log on to the WebSphere Application Server administrative console. \n
- Select Tivoli Federated Identity Manager > Domains. \n
- Click Create to create a domain. The Domain creation wizard prompts you for domain information. \n
- Verify that the Tivoli Access Manager domain properties that you entered are correct. \n
- In the Create Domain Complete panel, select the Make this domain the active management domain check box to make the domain active. \n
- Select Tivoli Federated Identity Manager > Domain Management > Runtime Node Management.
Note: If the following error shows, you can ignore it and continue with the next step:
FBTCON166E: An error was encountered while retrieving environmental settings. Check the environmental settings and try again. \n - Click Deploy Runtime. \n
- Select each runtime in the table. \n
- Click Configure. \n
\n - Copy any existing custom plugins you have written, migrating them if needed into the new servers to the <TFIM install dir>/plugins, for example the /opt/IBM/FIM/plugins directory
If you are migrating from TFIM 6.1.1 you will need to update any plugins before you can use them in newer versions of TFIM. Please see the following for more detail:
Developing a custom Java module \n - Copy any changed pages from the old machine to the new machines <TFIM install dir>/pages directory \n
- From the WebSphere Application Server administrative console, select Tivoli Federated Identity Manager > Domain Management > Runtime Node Management. \n
- Click both the Publish Plug-ins and Publish Pages buttons you can dismiss the message about loading the configuration for the moment. \n
- Import the configuration that you exported from the old machine \n
- \n
- From the WebSphere Application Server administrative console, select Tivoli Federated Identity Manager > Domain Management > Import and Export Configuration > Import Configuration to import the configuration archive. \n
- Select the domain into which you want to import the configuration archive. \n
- Click the Browse button under Configuration Archive and select the previously exported JAR file in step 1. \n
- Click Import Configuration. \n
\n - Review your configuration to ensure that the importing process completed successfully. \n
- From the WAS console goto the WAS System administration tab on the left and click Nodes select the nodes and click full resynchronize. Give this a few moments to complete. \n
- Go back to Runtime Node Management and click on the "Load configuration changes to Tivoli Federated Identity Manager runtime" button if present from previous steps, if you dismissed this dialog in previous in step 13 you can click on the Reload Configurations button both buttons perform the same function. \n
- Then there are additional steps that may need to be done if upgrading such as the following:
If you are using the alias service you MUST migrate the aliases to the new 6.2.2. format. This will update the live data in LDAP but both versions of TFIM will be able to use it:
Upgrading LDAP aliases for FIM 6.2.2 \n - After you have done that you may optionally covert the aliases to the longer form. This step is not required, but recommended:
Migrating SAML 2.0 alias service entries \n - If you are calling Java modules in your XSL rules:
Making Java calls made from XSL work after upgrading \n - Update your database schema if needed for RBA and OTP. \n
- You may now test the new ENV by pointing the WebSEAL to the new server. No changes are required in the TFIM config as the URL that that client accesses is through WebSEAL. \n
- When you are satisfied that the new environment is working as expected you may proceed to uninstall the previous version of Tivoli Federated Identity Manager. \n
\n
\n \n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Security | \nTivoli Federated Identity Manager Business Gateway | \n\n | AIX, HP-UX, Linux, Solaris, Windows | \n6.0, 6.1.1, 6.1, 6.2, 6.2.1, 6.2.2, Version Independent | \nAll Editions | \n
\n
\n
\n \n \n",
+ "title": "IBM Best practice for upgrading or migrating Tivoli Federated Identity Manager - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n What is the best practice for upgrading or migrating to a new machine for TFIM? \n\nANSWER\nThe best practice is to use a two-system method. This procedure is written toward the use case where the Point Of Contact is WebSEAL. This procedure is written to ensure that the any customizations made to TFIM, such as STS modules, pages, and the hostnames used to access the machine will continue to work. In a normal production environment, TFIM is only installed on the deployment manager, and then pushed to the nodes later as part of the domain create and runtime config.\n\n\n 1. The first step is to back up the configuration of your existing environment. This will be used to restore the configuration in the new server. 1. Select Tivoli Federated Identity Manager -> Domain Management -> Import and Export Configuration. \n 2. Select the appropriate domain. \n 3. Click Export Configuration. \n 4. When prompted, specify the location where you want to save the exported configuration JAR file. Make a note of this files location. \n 5. Click OK.\n \n \n 2. On the new server install a new copy of WebSphere, you can use this opportunity to change WebSphere versions to a currently supported version 1. Create the desired server profiles, and apply recommended WebSphere FixPack level. For more information on the current WebSphere FixPack level, see the following\n Recommended fixes for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg27004980] \n 2. If using IHS you may install that now as well.\n \n \n 3. Restart the Dmgr and do not log into ISC before attempting a TFIM product install. \n 4. On the new server install TFIM. When you are given the option to use an existing version of WebSphere Application Server, select Yes for both the management service and console. If you are using a cluster enter the information for the new Dmgr or if using a stand alone WebSphere profile provide the values you set in that profile. \n 5. Download the latest WebSphere update installer version 7.0.0.x 32 bit (Issues have been reported with 7.0.0.31). As of April 2016 we recommend the use of WAS UI 7.0.0.29 if you have not applied POODLE fixes to WebSphere and 7.0.0.41 if you have applied POODLE fixes and WebSphere is only using the TLS protocol. To avoid some WebSphere authorization issues we recommend you temporarily disable global security on the Dmgr. Please note that even if you are using WebSphere 8.0 or higher you still need to use the WebSphere 7 UI to apply TFIM FixPacks. This will not cause a problem with the IBM Installation Manager used to install WebSphere versions 8.0 and above. The IBM Installation Manager will continue to be used to apply WebSphere FixPacks for 8.0 and above. The UI 7 is only for TFIM patches. \n 6. Optionally you may chose to create the TFIM domain now or after applying the FixPack \n 7. If you logged into ISC after installing TFIM and in general before applying any TFIM FixPacks we recommend you restart the Dmgr and install the FixPack before anyone logs into ISC, this is needed before you attempt the FP install to avoid any locked files. \n 8. If WAS is not running as the same account you are using to run the Update Installer ensure that groups are set correctly to allow access. In any case, ensure the umask is set to at least 022. \n 9. Apply the latest TFIM FixPack from FixCentral\n Quick link to TFIM FixPacks on FixCentral [http://www-933.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/IBM+Tivoli+Federated+Identity+Manager&release=6.2.2&platform=All&function=all&source=fc] \n NOTE: If a domain is not created before application of Tivoli Federated Identity Manager fix pack, the fix pack installation completes successfully with a \"Partially Successful\" message. You can safely ignore this error. If you get any other errors, do not close the Update Installer with Ctrl-C use the finish buttons so that the Update Installer can finish and clean up. \n 10. Create and deploy a domain. 1. Log on to the WebSphere Application Server administrative console. \n 2. Select Tivoli Federated Identity Manager > Domains. \n 3. Click Create to create a domain. The Domain creation wizard prompts you for domain information. \n 4. Verify that the Tivoli Access Manager domain properties that you entered are correct. \n 5. In the Create Domain Complete panel, select the Make this domain the active management domain check box to make the domain active. \n 6. Select Tivoli Federated Identity Manager > Domain Management > Runtime Node Management.\n Note: If the following error shows, you can ignore it and continue with the next step:\n FBTCON166E: An error was encountered while retrieving environmental settings. Check the environmental settings and try again. \n 7. Click Deploy Runtime. \n 8. Select each runtime in the table. \n 9. Click Configure.\n \n \n 11. Copy any existing custom plugins you have written, migrating them if needed into the new servers to the
\n
",
+ "title": "IBM Too many open files - United States",
+ "text": "ASISslCert; Too many open files TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n SI would start but after a few minutes of processing the schedules stopped running and the UI became unresponsive . Database connections were working (dump_info.sh worked). \n\nSYMPTOM\nbizIntel.log: \n\nERROR 000000000000 GLOBAL_SCOPE \n\n
\nASISslCert; Too many open files
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n
\n
\n \n
Problem(Abstract)
\nSI would start but after a few minutes of processing the schedules stopped running and the UI became unresponsive . Database connections were working (dump_info.sh worked).
\nSymptom
\n\n
\n bizIntel.log:
\nERROR 000000000000 GLOBAL_SCOPE <BIResourceMonitorEventListener-240520790> [BIResourceMonitorEventListener] : Error in socket connection on : http://<server>:<port> Connection refused
noapp.log:
ALL 000000000000 GLOBAL_SCOPE FROMLOGSYS: java.io.FileNotFoundException: /si50/install/logs/system.log.D20120414.T112557 (Too many open files)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:205)
at java.io.FileOutputStream.<init>(FileOutputStream.java:96)
at com.sterlingcommerce.woodstock.util.frame.log.ServerLog.open(ServerLog.java:192)
at com.sterlingcommerce.woodstock.util.frame.log.ServerLog.rotateLog(ServerLog.java:259)
at com.sterlingcommerce.woodstock.util.frame.log.ServerLog.write(ServerLog.java:323)
at com.sterlingcommerce.woodstock.util.frame.logex.SCIAppender.append(SCIAppender.java:128)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
at org.apache.log4j.Category.callAppenders(Category.java:203)
at org.apache.log4j.Category.forcedLog(Category.java:388)
at com.yantra.yfc.log.YFCLogCategory.lowLevelLog(YFCLogCategory.java:546)
at com.yantra.yfc.log.YFCLogCategory.error(YFCLogCategory.java:437)
at com.sterlingcommerce.woodstock.util.frame.log.Logger.logError(Logger.java:801)
at com.sterlingcommerce.security.kcapi.PrivateKeyInfo.getInstanceByName(PrivateKeyInfo.java:1002)
at com.sterlingcommerce.security.jsseimpl.SCIX509KeyManagerImpl.getPrivateKey(SCIX509KeyManagerImpl.java:97)
at com.ibm.jsse2.mc$a_.getPrivateKey(mc$a_.java:8)
at com.ibm.jsse2.mc.getPrivateKey(mc.java:6)
at com.ibm.jsse2.fb.a(fb.java:20)
at com.ibm.jsse2.fb.a(fb.java:361)
at com.ibm.jsse2.hc.a(hc.java:48)
at com.ibm.jsse2.hc.accept(hc.java:44)
at org.mortbay.jetty.security.SslSocketConnector.accept(SslSocketConnector.java:170)
at com.sterlingcommerce.woodstock.noapp.ssl.SCISslSocketConnector.accept(SCISslSocketConnector.java:90)
at org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:537)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
servicesctl.log:
ERROR 000410020322 SERVICES.SERVICES_CONTROLLER.ERR_getAdapter21 getAdapter
ERROR 000000000000 GLOBAL_SCOPE [1334424900295] Exception creating connection to: <IP address>; nested exception is:
java.net.SocketException: Too many open files
system.log:
ERROR 000000000000 GLOBAL_SCOPE Error: Could not find PrivateKeyInfo with name ASISslCert
Cause
\n\n
\n ASISslCert was deleted from the Sterling Integrator System certificates store - 'Trading Partner > Digital Certificates > System'. This certificate is used for baseport+1 SSL socket connections.
\n
sslCert=ASISslCert
noapp.properties_platform_ifcresources_ext
noapp.properties_platform_ifcresources_ext.in
\n
Environment
\n\n
\n \n Sterling Integrator 5.x
\nDiagnosing the problem
\n\n
\n "lsof -u <SI user>" results:
\n90% of the output looked liked this:
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
java <noapp pid> <SI user> 616u sock 0,5 18557 can't identify protocol
"Type=sock" and "Name=can't identify protocol" represent connections that can occur if you create a socket but never connect() or bind() with it.
\n
Resolving the problem
\n\n
\n Restored database from backup
\n
Another solution (temporary workaround until the database restore can be completed) would be to add the "sslCert=" parameter to customer_overrides.properties but reference another System certificate name:
Example:
noapp.sslCert=<new name>
Next step for this change to take effect would be to simply restart SI .
**The newly referenced System certificate name must exist in the System store**
**The following certificates are very important to SI and should not be deleted without exporting first:**
B2BHttp
OpsKey
OpsDrv
UIKey
doccrypto
DefDBCrypt
ASISslCert
\n
\n \n
\n \n
\n \n \n\n
\n\n\n\n
\n0403-027 The parameter list is too long; SecureMain; KCI1343E; 0403-027
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n
\n \n
Problem(Abstract)
\nAgent install fails during secureMain and generates an error - /usr/bin/chmod: 0403-027 The parameter list is too long
\nSymptom
\n\n
\n The itmsecure_<timestamp>.log shows the below error
/Tivoli/itm/bin/secureLock[134]: /usr/bin/chmod: 0403-027 The parameter list is too long.
KCI1343E secureMain completed with errors. For more information, check
the log file /Tivoli/itm/logs/itmsecure_062012135428.log.
\n
Cause
\n\n
\n The real cause for this error is:
\n
The system has exceeded the AIX ARG_MAX value: 0403-027 The parameter list is too long. This AIX value can be increased with smitty.
The maximum size, in 4KB blocks, that the ARG/ENV list is allowed when running exec subroutines. This prevents exec subroutines from failing if the argument list is too long. You can specify a value in the range of 6 through 1024. The default value is 6. Specifying a higher value may constrain system memory resources. This change takes affect immediately and is preserved over boot."
\n
Environment
\n\n
\n \n AIX any version
\nResolving the problem
\n\n
\n To resolve the issue increase the ARG_MAX value
To check the value use the below command :
lsattr -E -l sys0 -a ncargs
To change the value use the below command. You can change the value to 32, or increase to few more than the original value.
chdev -l sys0 -a ncargs='32' (default is 6)
\n
\n \n
\n
\n \n \n",
+ "title": "IBM SecureMain fails with error KCI1343E - United States",
+ "text": "0403-027 The parameter list is too long; SecureMain; KCI1343E; 0403-027 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Agent install fails during secureMain and generates an error - /usr/bin/chmod: 0403-027 The parameter list is too long \n\nSYMPTOM\nThe itmsecure_
\n
",
+ "title": "IBM Determining whether to use Common Criteria Mode at initialization - United States",
+ "text": "EAL4 common criteria cc-mode cc normal mode TECHNOTE (FAQ)\n\nQUESTION\n What is Common Criteria Mode and under which scenarios would I want to choose it? \n\nANSWER\nDefinition: Common Criteria (CC mode) mode puts the IBM WebSphere DataPower appliance in a mode that enforces a set of policies required to pass the Common Criteria security testing criteria (EAL4). \n\n\n\n\nWhat it covers: Common Criteria mode forces several settings to specific values. These values are required by CC mode and will be enforced at reboot if changed. It also affects audit log policies and includes a group of default rules and actions. In addition, a DataPower appliance in CC mode is only certified for EAL4 with the HTTP over an XML Firewall. Any other uses, including even WebGUI and SSH access, are not EAL4 certified. Please note, although this option exists in all versions listed on this page, it is only officially certified for the versions listed at the link found in the More Information section. \n\nWhen it should be used: If you are unsure whether you should use Common Criteria mode, then you most likely should not. In general, it is only used when a specific authority requires the appliance to be EAL4 certified. If this is not a specific requirement for your use of the appliance, normal mode should be used. You should not use CC mode to simply be 'more secure' as it enforces far reaching limitations on the appliance. \n\nHow it is turned on/off: Because of the secure nature of CC mode, it can only be turned on or off at initialization of the appliance. This means that changing the value requires a complete re-initialization of the appliance. At initialization, you will be prompted to use either Normal Mode or Common Criteria Mode. \n\nIf you have already defined your mode on a running system and would like to change it and keep your configuration, the best method is to make a complete export of the appliance before re-initializing the appliance. Then, you will have to configure your network interfaces manually, import the backup, and then manually re-add your encryption keys.\n\nHow to determine if it is on/off:\nTo determine if it's on or off, navigate to Administration -> Device (Heading) -> System Settings in the left hand navigation panel. If it's on, the value for \"Product Mode\" will be Common Criteria. If it's off, the value will be Normal.\n\n\nMore Information: More information regarding the IBM WebSphere DataPower Appliances Common Criteria certification can be found at the following web link:\nValidated Product - DataPower XS40 XML Security Gateway and X150 Appliance on Firewall v3.6 [http://www.niap-ccevs.org/cc-scheme/st/vid10020/].\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower XML Security Gateway XS40 Not Applicable Firmware 3.7.3, 3.7.2, 3.7.1, 3.6.1 Edition Independent Business Integration WebSphere DataPower SOA Appliances General Firmware 3.7.3, 3.7.2, 3.7.1, 3.6.1, 3.6 Edition Independent",
+ "metadata": {
+ "sourceDocumentId": "swg21388551",
+ "date": "2010-01-04",
+ "productName": "WebSphere DataPower Integration Appliance XI50",
+ "productId": "SS6L4E,SS6L5J",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21388551"
+ }
+ },
+ "swg1PK93166": {
+ "id": "swg1PK93166",
+ "content": "\n\n
\nEAL4 common criteria cc-mode cc normal mode
\n\n\n \n \n
\n
\n
\nTechnote (FAQ)
\n \n
\n
\n \n
Question
\nWhat is Common Criteria Mode and under which scenarios would I want to choose it?
\nAnswer
\n\n
\n Definition: Common Criteria (CC mode) mode puts the IBM WebSphere DataPower appliance in a mode that enforces a set of policies required to pass the Common Criteria security testing criteria (EAL4).
\n
What it covers: Common Criteria mode forces several settings to specific values. These values are required by CC mode and will be enforced at reboot if changed. It also affects audit log policies and includes a group of default rules and actions. In addition, a DataPower appliance in CC mode is only certified for EAL4 with the HTTP over an XML Firewall. Any other uses, including even WebGUI and SSH access, are not EAL4 certified. Please note, although this option exists in all versions listed on this page, it is only officially certified for the versions listed at the link found in the More Information section.
\nWhen it should be used: If you are unsure whether you should use Common Criteria mode, then you most likely should not. In general, it is only used when a specific authority requires the appliance to be EAL4 certified. If this is not a specific requirement for your use of the appliance, normal mode should be used. You should not use CC mode to simply be 'more secure' as it enforces far reaching limitations on the appliance.
\nHow it is turned on/off: Because of the secure nature of CC mode, it can only be turned on or off at initialization of the appliance. This means that changing the value requires a complete re-initialization of the appliance. At initialization, you will be prompted to use either Normal Mode or Common Criteria Mode.
\nIf you have already defined your mode on a running system and would like to change it and keep your configuration, the best method is to make a complete export of the appliance before re-initializing the appliance. Then, you will have to configure your network interfaces manually, import the backup, and then manually re-add your encryption keys.
How to determine if it is on/off:
To determine if it's on or off, navigate to Administration -> Device (Heading) -> System Settings in the left hand navigation panel. If it's on, the value for "Product Mode" will be Common Criteria. If it's off, the value will be Normal.
More Information: More information regarding the IBM WebSphere DataPower Appliances Common Criteria certification can be found at the following web link:
Validated Product - DataPower XS40 XML Security Gateway and X150 Appliance on Firewall v3.6.
\n
\n \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Integration | \nWebSphere DataPower XML Security Gateway XS40 | \nNot Applicable | \nFirmware | \n3.7.3, 3.7.2, 3.7.1, 3.6.1 | \nEdition Independent | \n
| Business Integration | \nWebSphere DataPower SOA Appliances | \nGeneral | \nFirmware | \n3.7.3, 3.7.2, 3.7.1, 3.6.1, 3.6 | \nEdition Independent | \n
\n
\n
\n \n \n\n
",
+ "title": "IBM PK93166: Fix that Portal UI is unavailable when customization domain is u navailable - United States",
+ "text": " FIXES ARE AVAILABLE\n6.1.0.3 Download: WebSphere Portal and WCM V6.1 fix pack 3, 6.1.5 feature pack [http://www-01.ibm.com/support/docview.wss?uid=swg24025054]\n6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24026394]\n6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24027475]\n6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24030970]\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 * If the customization domain is unavailable the Portal UI is\n currently also unavailable. WebSphere Portal should still run\n if the customization domain is unavailable.\n \n \n Tracing with:\n \n com.ibm.wps.engine.*=all:com.ibm.wps.ac.*=all:com.ibm.wps.datast\n ore.*=all\n \n can help identify the problem. The trace.log will contain\n errors like:\n \n ... DataStoreCont E com.ibm.wps.datastore.impl.DataStoreContext\n handleException EJPDB0001E: Error occurred during database\n access. Last SQL statement is [SELECT OID, CREATED, MODIFIED,\n RES_TYPE, EXTERNAL_OID, EXTERNAL_UID, PARENT_OID, OWNER_TYPE,\n OWNER_UID, INHERITANCE, PROPAGATION, EXTERNALIZED, IS_PRIVATE,\n NAME, IS_LEAF FROM customization.PROT_RES WHERE (OWNER_UID = ?\n AND RES_TYPE = ?)].\n \n com.ibm.wps.datastore.domains.DomainUnavailableException:\n EJPDB0101E: Database domain [Domain: cust] is currently\n unavailable.\n at\n com.ibm.wps.datastore.impl.DataStoreContext.handleException(Data\n StoreContext.java:315)\n ...\n at\n com.ibm.wps.ac.impl.AccessControlImpl.checkEntitlements(AccessCo\n ntrolImpl.java:119)\n ...\n Caused by: com.ibm.websphere.ce.cm.ObjectClosedException:\n DSRA9110E: Connection is closed.\n ...\n ... AccessControl < com.ibm.wps.ac.impl.AccessControlImpl\n [Domain: cust].checkEntitlements RETURN null\n ...\n ... WPRenderPhase 2 com.ibm.wps.engine.phases.WPRenderPhase\n getThemeTemplate(aState, aStateManager) Navigation selection\n model: \n ...\n \n\n
\n
\n
\n \n
\n \nFixes are available
\n \n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
If the customization domain is unavailable the Portal UI is\ncurrently also unavailable. WebSphere Portal should still run\nif the customization domain is unavailable.\n\n\nTracing with:\n\ncom.ibm.wps.engine.*=all:com.ibm.wps.ac.*=all:com.ibm.wps.datast\nore.*=all\n\ncan help identify the problem. The trace.log will contain\nerrors like:\n\n... DataStoreCont E com.ibm.wps.datastore.impl.DataStoreContext\nhandleException EJPDB0001E: Error occurred during database\naccess. Last SQL statement is [SELECT OID, CREATED, MODIFIED,\nRES_TYPE, EXTERNAL_OID, EXTERNAL_UID, PARENT_OID, OWNER_TYPE,\nOWNER_UID, INHERITANCE, PROPAGATION, EXTERNALIZED, IS_PRIVATE,\nNAME, IS_LEAF FROM customization.PROT_RES WHERE (OWNER_UID = ?\nAND RES_TYPE = ?)].\n\ncom.ibm.wps.datastore.domains.DomainUnavailableException:\nEJPDB0101E: Database domain [Domain: cust] is currently\nunavailable.\n at\ncom.ibm.wps.datastore.impl.DataStoreContext.handleException(Data\nStoreContext.java:315)\n...\n at\ncom.ibm.wps.ac.impl.AccessControlImpl.checkEntitlements(AccessCo\nntrolImpl.java:119)\n...\nCaused by: com.ibm.websphere.ce.cm.ObjectClosedException:\nDSRA9110E: Connection is closed.\n...\n... AccessControl < com.ibm.wps.ac.impl.AccessControlImpl\n[Domain: cust].checkEntitlements RETURN null\n...\n... WPRenderPhase 2 com.ibm.wps.engine.phases.WPRenderPhase\ngetThemeTemplate(aState, aStateManager) Navigation selection\nmodel: <?xml version="1.0" encoding="UTF-8"?>\n...\n<selectedNode value="null"/>\n...\n... Servlet E com.ibm.wps.engine.Servlet handleException\nEJPEJ0069E: URL parsing problem, URL= http://...\n... Servlet 1 com.ibm.wps.engine.Servlet handleException\nAn exception occurred while processing the request.\n\ncom.ibm.portal.state.phases.exceptions.PhaseException:EJPEI0105E\n: An error occurred during the rendering in phase\ncom.ibm.wps.engine.phases.WPRenderPhase@153b153b.\n...\nCaused by: java.lang.NullPointerException\n at\ncom.ibm.wps.engine.phases.WPRenderPhase.getThemeTemplate(WPRende\nrPhase.java:128)\n\n\n\nThe exact cause of the database communications failure may\ndiffer from this example, but the results will be the same.\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
If the customization domain is unavailable the Portal UI is\ncurrently also unavailable. WebSphere Portal should still run\nif the customization domain is unavailable.\n
\n \n
Problem conclusion
\n- \n
- \n \n
The DomainUnavailableExection is caught now for the\ncustomization domain in the ContenModel and related classes.\n\nManual Steps:\n None\n\nFailing Module(s):\n Engine: Tags & Commands\n\nAffected Users:\n All users\n\nVersion Information:\n Portal Version(s): 6.0.1.5\n Pre-Requisite(s): PK89122\n Co-Requisite(s): ---\n\n Portal Version(s): 6.0.1.6\n Pre-Requisite(s): PK89122\n Co-Requisite(s): ---\n\n Portal Version(s): 6.1.0.1\n Pre-Requisite(s): PK84208 PK86209\n Co-Requisite(s): ---\n\n Portal Version(s): 6.1.0.2\n Pre-Requisite(s): PK86209\n Co-Requisite(s): ---\n\nPlatform Specific:\n This fix applies to all platforms.\n\nA fix is available from Fix Central:\n\nhttp://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde\nr?apar=PK93166&productid=WebSphere%20Portal&brandid=5\n\nYou may need to type or paste the complete address into your Web\nbrowser.\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PK93166
\n Reported component name
WEBSPHERE PORTA
\n Reported component ID
5724E7600
\n Reported release
61A
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2009-08-05
\n Closed date
2009-10-07
\n Last modified date
2010-01-28
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
WEBSPHERE PORTA
\n Fixed component ID
5724E7600
\n
Applicable component levels
\n- \n
R60J PSY
UP
\n R60K PSY
UP
\n R61A PSY
UP
\n R61B PSY
UP
\n
\n
\n
\n
",
+ "title": "IBM Update of an Oracle table fails with OCIStmtExecute errcode=12899 - United States",
+ "text": " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When executing an insert or update operation on a table in a Unicode Oracle instance containing a 'CHAR' column with IBM WebSphere Transformation Extender (WTX), the following error may be observed:\n\n\n\nError returned by OCIStmtExecute, errcode=12899\n\nORA-12899: value too large for column \"SUPPORT\".\"TEST6\".\"COL2\" (actual: 4, maximum: 1) \n\nSYMPTOM\nThe insert or update operation fails. The following error will be seen in an adapter trace:\n\nError returned by OCIStmtExecute, errcode=12899\nORA-12899: value too large for column \"SUPPORT\".\"TEST6\".\"COL2\" (actual: 4, maximum: 1)\n\n\nCAUSE\nThis issue is due to the way the WTX database adapter handles the update of 'CHAR' columns. By default, the 'CHAR' columns are padded with spaces to their exact byte size. For Oracle databases with a native encoding, this does not pose any issues.\n\nHowever, for Oracle databases that store data in a multi-byte UTF8 encoding (e.g. NLS_CHARACTERSET = AL32UTF8), a 'CHAR' column will have multiple bytes for each character defined. So the WTX database adapter would fill any remaining bytes with a pad (normally a space, ' ') character. \n\nWhen using a type tree encoding of UTF8-32, then all bytes are filled automatically, which in turn prevents any further padding. However, when using a native type tree encoding, not all the bytes are filled, which in turn triggers the WTX database adapter to pad the 'CHAR' column with spaces, which in turn triggers the Oracle error message of too many characters being provided for the column (e.g. Error returned by OCIStmtExecute, errcode=12899 ORA-12899: value too large for column).\n\nTo disable this padding functionality, the following environment variable can be set:\n\nTX_DB_PAD_CHAR=0\n\nENVIRONMENT\nAll WTX execution environments accessing an Oracle instance with NLS_CHARACTERSET = AL32UTF8\n\nDIAGNOSING THE PROBLEM\nActivate the database trace with the additional adapter command -T, and view the adapter trace, which will contain:\n\nError returned by OCIStmtExecute, errcode=12899\nORA-12899: value too large for column \"SUPPORT\".\"TEST6\".\"COL2\" (actual: 4, maximum: 1)\n\nRESOLVING THE PROBLEM\nTo disable the WTX default column padding functionality, the following environment variable can be set:\n\nTX_DB_PAD_CHAR=0",
+ "metadata": {
+ "sourceDocumentId": "swg21678024",
+ "date": "2015-03-06",
+ "productName": "Transformation Extender",
+ "productId": "SSVSD8",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21678024"
+ }
+ },
+ "nas8N1020586": {
+ "id": "nas8N1020586",
+ "content": "\n\n
\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\n When executing an insert or update operation on a table in a Unicode Oracle instance containing a 'CHAR' column with IBM WebSphere Transformation Extender (WTX), the following error may be observed:
Error returned by OCIStmtExecute, errcode=12899
ORA-12899: value too large for column "SUPPORT"."TEST6"."COL2" (actual: 4, maximum: 1)
Symptom
\n\n
\n The insert or update operation fails. The following error will be seen in an adapter trace:
Error returned by OCIStmtExecute, errcode=12899
ORA-12899: value too large for column "SUPPORT"."TEST6"."COL2" (actual: 4, maximum: 1)
\n
Cause
\n\n
\n This issue is due to the way the WTX database adapter handles the update of 'CHAR' columns. By default, the 'CHAR' columns are padded with spaces to their exact byte size. For Oracle databases with a native encoding, this does not pose any issues.
However, for Oracle databases that store data in a multi-byte UTF8 encoding (e.g. NLS_CHARACTERSET = AL32UTF8), a 'CHAR' column will have multiple bytes for each character defined. So the WTX database adapter would fill any remaining bytes with a pad (normally a space, ' ') character.
When using a type tree encoding of UTF8-32, then all bytes are filled automatically, which in turn prevents any further padding. However, when using a native type tree encoding, not all the bytes are filled, which in turn triggers the WTX database adapter to pad the 'CHAR' column with spaces, which in turn triggers the Oracle error message of too many characters being provided for the column (e.g. Error returned by OCIStmtExecute, errcode=12899 ORA-12899: value too large for column).
To disable this padding functionality, the following environment variable can be set:
TX_DB_PAD_CHAR=0
Environment
\n\n
\n All WTX execution environments accessing an Oracle instance with NLS_CHARACTERSET = AL32UTF8
\nDiagnosing the problem
\n\n
\n Activate the database trace with the additional adapter command -T, and view the adapter trace, which will contain:
Error returned by OCIStmtExecute, errcode=12899
ORA-12899: value too large for column "SUPPORT"."TEST6"."COL2" (actual: 4, maximum: 1)
Resolving the problem
\n\n
\n To disable the WTX default column padding functionality, the following environment variable can be set:
TX_DB_PAD_CHAR=0
\n
\n \n
\n
\n \n \n\n
",
+ "title": "IBM Message CWWKZ0002E occurs with IBM WebSphere Application Server (WAS) Liberty v8.5.5 - United States",
+ "text": "WAS; Liberty; application; install; CWWKZ0002E; UTF-16; UTF-8; javax.xml.stream.XMLStreamException; com.ibm.ws.javaee.ddmodel.DDParser$ParseException; com.ibm.wsspi.adaptable.module.UnableToAdaptException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When attempting to deploy and start a new web application, the IBM WebSphere Application Server v8.5.5 Liberty server throws a CWWKZ0002E message during start up indicating an exception occurred when starting the application. \n\nSYMPTOM\nCWWKZ0002E: An exception occurred while starting the application records. The exception message was: com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax.xml.stream.XMLStreamException\n\n\nCAUSE\nWEB-INF/web.xml file in the JEE Web Application WAR file is encoded with UTF-16, which is not supported by IBM WAS Liberty. Only UTF-8 encoding is supported.\n\nENVIRONMENT\nIBM i OS, IBM WebSphere Application Server v8.5.5 Liberty\n\nDIAGNOSING THE PROBLEM\nReview the wlp/usr/servers/J\n\n
\nWAS; Liberty; application; install; CWWKZ0002E; UTF-16; UTF-8; javax.xml.stream.XMLStreamException; com.ibm.ws.javaee.ddmodel.DDParser$ParseException; com.ibm.wsspi.adaptable.module.UnableToAdaptException
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n
\n
\n\n
Problem(Abstract)
\nWhen attempting to deploy and start a new web application, the IBM WebSphere Application Server v8.5.5 Liberty server throws a CWWKZ0002E message during start up indicating an exception occurred when starting the application.
\nSymptom
\n\n
\n CWWKZ0002E: An exception occurred while starting the application records. The exception message was: com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax.xml.stream.XMLStreamException
\n\n
Cause
\n\n
\n WEB-INF/web.xml file in the JEE Web Application WAR file is encoded with UTF-16, which is not supported by IBM WAS Liberty. Only UTF-8 encoding is supported.
\nEnvironment
\n\n
\n IBM i OS, IBM WebSphere Application Server v8.5.5 Liberty
\nDiagnosing the problem
\n\n
\n Review the wlp/usr/servers/J<server>/logs/messages.log log file for the CWWKZ0002E message. Obtain the WAR file being deployed/started to the WAS Liberty server. Review the encoding of the WEB-INF/web.xml file in the application WAR file to see if it is encoded with UTF-16
\nResolving the problem
\n\n
\n In this example, here are the following messages logged to the messages.log file indicating a problem starting the "records" application. NOTE: This applies to any application name using an UTF-16 encoded web.xml file.
Errors in the messages.log file:
Errors in the messages.log file:
2/18/15 14:02:22:355 CST] 0000004b com.ibm.ws.app.manager.AppMessageHelper I CWWKZ0018I: Starting application records.
[2/18/15 14:02:23:174 CST] 0000004b com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: "javax.xml.stream.XMLStreamException com.ibm.ws.javaee.ddmodel.DDParser 351" at ffdc_15.02.18_14.02.23.0.log
[2/18/15 14:02:23:335 CST] 0000004b com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: "com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax.xml.stream.XMLStreamException com.ibm.ws.app.manager.war.internal.WARApplicationHandlerImpl 96" at ffdc_15.02.18_14.02.23.1.log
[2/18/15 14:02:23:337 CST] 0000004b om.ibm.ws.app.manager.war.internal.WARApplicationHandlerImpl E CWWKZ0106E: Could not start web application records.
[2/18/15 14:02:23:345 CST] 0000004b com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: "com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax.xml.stream.XMLStreamException com.ibm.ws.app.manager.internal.statemachine.StartAction$1 applicationStartFail" at ffdc_15.02.18_14.02.23.2.log
[2/18/15 14:02:23:346 CST] 0000004b com.ibm.ws.app.manager.AppMessageHelper E CWWKZ0002E: An exception occurred while starting the application records. The exception message was: com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax.xml.stream.XMLStreamException
An FFDC log shows the following stack trace of the exception.
Stack Dump = com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax...
Stack Dump = com.ibm.wsspi.adaptable.module.UnableToAdaptException: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax.xml.stream.XMLStreamException
at com.ibm.ws.javaee.ddmodel.web.WebAppAdapter.adapt(WebAppAdapter.java:43)
at com.ibm.ws.javaee.ddmodel.web.WebAppAdapter.adapt(WebAppAdapter.java:26)
at com.ibm.ws.adaptable.module.internal.AdapterFactoryServiceImpl.adapt(AdapterFactoryServiceImpl.java:189)
at com.ibm.ws.adaptable.module.internal.AdaptableContainerImpl.adapt(AdaptableContainerImpl.java:171)
at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase$ModuleContainerInfo.<init>(DeployedAppInfoBase.java:132)
at com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase$WebModuleContainerInfo.<init>(DeployedAppInfoBase.java:212)
at com.ibm.ws.app.manager.war.internal.WARDeployedAppInfo.<init>(WARDeployedAppInfo.java:57)
at com.ibm.ws.app.manager.war.internal.WARDeployedAppInfoFactoryImpl.createDeployedAppInfo(WARDeployedAppInfoFactoryImpl.java:121)
at com.ibm.ws.app.manager.war.internal.WARDeployedAppInfoFactoryImpl.createDeployedAppInfo(WARDeployedAppInfoFactoryImpl.java:39)
at com.ibm.ws.app.manager.war.internal.WARApplicationHandlerImpl.install(WARApplicationHandlerImpl.java:95)
at com.ibm.ws.app.manager.internal.statemachine.StartAction.execute(StartAction.java:134)
at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.enterState(ApplicationStateMachineImpl.java:1277)
at com.ibm.ws.app.manager.internal.statemachine.ApplicationStateMachineImpl.run(ApplicationStateMachineImpl.java:876)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:761)
Caused by: com.ibm.ws.javaee.ddmodel.DDParser$ParseException: javax.xml.stream.XMLStreamException
at com.ibm.ws.javaee.ddmodel.DDParser.createXMLStreamReader(DDParser.java:352)
at com.ibm.ws.javaee.ddmodel.DDParser.parseRootElement(DDParser.java:472)
at com.ibm.ws.javaee.ddmodel.web.WebAppAdapter$WebAppDDParser.parse(WebAppAdapter.java:56)
at com.ibm.ws.javaee.ddmodel.web.WebAppAdapter.adapt(WebAppAdapter.java:39)
... 15 more
Caused by: javax.xml.stream.XMLStreamException
at com.ibm.xml.xlxp.api.stax.msg.StAXMessageProvider.throwXMLStreamException(StAXMessageProvider.java:64)
at com.ibm.xml.xlxp.api.stax.XMLStreamReaderImpl.setDocumentEntity(XMLStreamReaderImpl.java:378)
at com.ibm.xml.xlxp.api.stax.XMLInputFactoryImpl.createXMLStreamReader(XMLInputFactoryImpl.java:1332)
at com.ibm.xml.xlxp.api.stax.XMLInputFactoryImpl.createXMLStreamReaderInternal(XMLInputFactoryImpl.java:1424)
at com.ibm.xml.xlxp.api.stax.XMLInputFactoryImpl.createXMLStreamReader(XMLInputFactoryImpl.java:1486)
at com.ibm.ws.javaee.ddmodel.DDParser.createXMLStreamReader(DDParser.java:350)
... 18 more
It was found the above exceptions were occurring because the WAR application being deployed/started had a WEB-INF/web.xml file encoded as UTF-16. Currently, the IBM WebSphere Application Server Liberty product does not support UTF-16 encoded web.xml files. The IBM WAS Liberty product only supports UTF-8 encoded web.xml files. To resolve the issue, the WAR file was rebuilt with a web.xml file encoded for UTF-8.
\n\n
\n \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Operating System | \nIBM i 7.2 | \n\n | \n | \n | \n |
| Operating System | \nIBM i 7.1 | \n\n | \n | \n | \n |
| Operating System | \nIBM i 6.1 | \n\n | \n | \n | \n |
| Operating System | \nIBM i 7.3 | \n\n | \n | \n | \n |
\n
\n
\n \n \n \n
\n\n\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
It has been observed in some customer environments that\nHostcontext can run out of available file handles due to code\nrelating to nva.conf\n\nRepetitive messages similar to the following might be visible\nin /var/log/qradar.log when this issue is occurring:\n\n[hostcontext.hostcontext] [ProcessMonitor] java.io.IOException:\nerror=24, Too many open files\n
\n \n
Local fix
\n- \n
- \n \n
No workaround available.\n
\n \n
Problem summary
\n- \n
- \n \n
This issue was resolved with QRadar/QRM/QVM/QRIF 7.2.8 Patch 7\n
\n \n
Problem conclusion
\n- \n
- \n \n
This issue was resolved with QRadar/QRM/QVM/QRIF 7.2.8 Patch 7\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
IV94782
\n Reported component name
QRADAR SOFTWARE
\n Reported component ID
5725QRDSW
\n Reported release
720
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt / Xsystem
\n Submitted date
2017-04-04
\n Closed date
2017-06-07
\n Last modified date
2017-06-07
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
QRADAR SOFTWARE
\n Fixed component ID
5725QRDSW
\n
Applicable component levels
\n- \n
R728 PSY
UP
\n
\n
\n
",
+ "title": "IBM IV94782: QRADAR LOGGING REPORTS HOSTCONTEXT '...TOO MANY OPEN FILES' MESSAGES - United States",
+ "text": " 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 * It has been observed in some customer environments that\n Hostcontext can run out of available file handles due to code\n relating to nva.conf\n \n Repetitive messages similar to the following might be visible\n in /var/log/qradar.log when this issue is occurring:\n \n [hostcontext.hostcontext] [ProcessMonitor] java.io.IOException:\n error=24, Too many open files\n \n \n \n \n \n\nLOCAL FIX\n * No workaround available.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * This issue was resolved with QRadar/QRM/QVM/QRIF 7.2.8 Patch 7\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This issue was resolved with QRadar/QRM/QVM/QRIF 7.2.8 Patch 7\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV94782\n \n \n * REPORTED COMPONENT NAME\n QRADAR SOFTWARE\n \n \n * REPORTED COMPONENT ID\n 5725QRDSW\n \n \n * REPORTED RELEASE\n 720\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-04-04\n \n \n * CLOSED DATE\n 2017-06-07\n \n \n * LAST MODIFIED DATE\n 2017-06-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 QRADAR SOFTWARE\n \n \n * FIXED COMPONENT ID\n 5725QRDSW\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R728 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1IV94782",
+ "date": "2017-06-07",
+ "productName": "IBM QRadar SIEM",
+ "productId": "SSBQAC",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1IV94782"
+ }
+ },
+ "swg21381128": {
+ "id": "swg21381128",
+ "content": "
\n
",
+ "title": "IBM JCR Troubleshooting: Exception with JCR PAC tables SQLCODE: -803, SQLSTATE: 23505 - United States",
+ "text": "Exception with JCR PAC tables SQLCODE: -803; SQLSTATE: 23505 TECHNOTE (FAQ)\n\nQUESTION\nIn IBM Web Content Management (WCM), you experience an exception error in the Java\u2122 Content Repository (JCR) Portal Access Control (PAC) tables with SQLCODE: -803, SQLSTATE: 23505. \n\nSample exception error:\ncom.ibm.wps.util.DataBackendException:\nEJPDB0099E: Error occurred during database access. Last SQL statement is [INSERT INTO JCR.PROT_RES (OID, CREATED, MODIFIED, RES_TYPE, EXTERNAL_OID, EXTERNAL_UID, PARENT_OID, OWNER_TYPE, OWNER_UID, INHERITANCE, PROPAGATION, EXTERNALIZED, IS_PRIVATE, NAME, IS_LEAF) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]. Transaction has status [STATUS_ACTIVE].\ncom.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 6;JCR.PROT_RES\n\n\nCAUSE\nDuplicate row in the PROT_RES table.\n\n\nANSWER\nThere are occasional scenarios in which the PAC data is not completely removed from the database when content is removed from either WCM or Personalization. When this occurs to the point of stopping a current function, the data must cleaned up with the following methods: \n\n\nWARNING:\nThe queries/process below are ok to use on Portal 6.1.x or 7.x but should NEVER be used for Portal 8.x or 8.5.x. It will wipe out ALL wcm roles for those versions, not just the stale entries. \n\nNOTE: ALWAYS backup the database before making any SQL updates of this type.\n\nDB2:\n\n\n * \n * \n * \n * \n\n\nOracle: * \n * \n * \n * \n * \n * \n * \n * \n * You must have a Java 1.5 JVM installed (note that this should be available via WebSphere). Since this application connects directly to the database, you must stop the Portal server while running this application. We recommend executing the application with a maximum amount of virtual memory available. This reduces the chance of running out of memory when processing large amounts of data. \n * \n * Usage: \n * \n * \n * \n * \n * Instructions:\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n
\nException with JCR PAC tables SQLCODE: -803; SQLSTATE: 23505
\n\n\n \n \n
\n \n
\n Technote (FAQ)
\n \n
\n
\n
\n
\n \n
Question
\n\n
\n In IBM Web Content Management (WCM), you experience an exception error in the Java™ Content Repository (JCR) Portal Access Control (PAC) tables with SQLCODE: -803, SQLSTATE: 23505.
\nSample exception error:
com.ibm.wps.util.DataBackendException:
EJPDB0099E: Error occurred during database access. Last SQL statement is [INSERT INTO JCR.PROT_RES (OID, CREATED, MODIFIED, RES_TYPE, EXTERNAL_OID, EXTERNAL_UID, PARENT_OID, OWNER_TYPE, OWNER_UID, INHERITANCE, PROPAGATION, EXTERNALIZED, IS_PRIVATE, NAME, IS_LEAF) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]. Transaction has status [STATUS_ACTIVE].
com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -803, SQLSTATE: 23505, SQLERRMC: 6;JCR.PROT_RES
\n
Cause
\n\n
\n Duplicate row in the PROT_RES table.
\n\n
Answer
\n\n
\n Oracle: \n
\n There are occasional scenarios in which the PAC data is not completely removed from the database when content is removed from either WCM or Personalization. When this occurs to the point of stopping a current function, the data must cleaned up with the following methods:
\n
WARNING:
The queries/process below are ok to use on Portal 6.1.x or 7.x but should NEVER be used for Portal 8.x or 8.5.x. It will wipe out ALL wcm roles for those versions, not just the stale entries.
NOTE: ALWAYS backup the database before making any SQL updates of this type.
DB2:
- \n
* SELECT COUNT(*) FROM schema.PROT_RES WHERE RES_TYPE IN (7003, 46, 51, 49, 48, 52) AND EXTERNAL_UID NOT IN (SELECT UUID FROM schema.ICMSTJCRWSNODES)\n
* DELETE FROM schema.PROT_RES WHERE RES_TYPE IN (7003, 46, 51, 49, 48, 52) AND EXTERNAL_UID NOT IN (SELECT UUID FROM schema.ICMSTJCRWSNODES)\n
\n Oracle: \n
- \n A utility has been provided to clean up the table when using an Oracle database in the Attachments section below. Attached is a Java application that removes the unused entries from the PROT_RES table. This application directly connects to the database and queries both the PROT_RES and the ICMSTJCRWSNODES tables, listing the differences between the two tables. \n
- You must have a Java 1.5 JVM installed (note that this should be available via WebSphere). \n
- Since this application connects directly to the database, you must stop the Portal server while running this application. \n
- We recommend executing the application with a maximum amount of virtual memory available. This reduces the chance of running out of memory when processing large amounts of data. \n
\n
When this application is executed in update mode, it also removes the unused entries from the PROT_RES table.\n
\n
Because this application runs from the command-line, it has the following requirements:\n
\n
- \n
\n Usage: \n
java com.ibm.jcr.db.pac.ProtResCleaner -db icmPropertiesFile [-update]\n
\n
\n Instructions:\n
1. Download the dbapplications.jar file (in the Attachments section below) to your file system.\n
\n
2. Stop all Portal servers that are connected to the database.\n
\n
3. Back up the database.\n
\n
4. Open a command prompt and set the following classpath: \n
\n
- \n <oracle-lib>/ojdbc14.jar;\n <applications-loc>/dbapplications.jar,\n
\n
where \n <oracle-lib> is the location of the Oracle Java libraries and\n <applications-loc> is the location on the file system where you downloaded the dbapplications.jar file.\n
\n
\n
- \n jcr.database.type\n
jcr.database.name\n
jcr.database.userid\n
jcr.database.password\n
jcr.database.schema\n
jcr.database.driver\n
jcr.database.drivertype\n
jcr.database.hostname\n
jcr.database.port \n
\n
- \n java -Xmx1500m com.ibm.jcr.db.pac.ProtResCleaner -db \n <PortalServer>/jcr/lib/com/ibm/icm/icm.properties\n
\n
NOTE: You may change the value of "-Xmx1500m" as needed. Increase this value if you encounter an Out Of Memory error or decrease this value if you get an error that Java cannot create the virtual machine. \n
\n
\n
8. Execute the application in update mode. Save the output to a new file: \n
- \n java -Xmx1500m com.ibm.jcr.db.pac.ProtResCleaner -db \n <PortalServer>/jcr/lib/com/ibm/icm/icm.properties \n -update \n
9. Restart the Portal server. \n
\n
Contact IBM Support if you encounter any problems in executing the above steps.\n
\n
\n NOTE: This duplicate exception can be prevented by applying PK78517.\n
\n
\n \n
\n \n \n\n
\n\n\n\n
\n
\n
\n \n
\n \nFixes are available
\n \n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
WebSphere MQ managed .NET application reports\nMQRC_CONNECTION_BROKEN error during disconnect. The following\nerror is reported in the event viewer:\n\nMQRC_CONNECTION_BROKEN\nEventWatcher\\Match Message In\nat IBM.WMQ.MQQueueManager.Disconnect()\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
****************************************************************\nUSERS AFFECTED:\nWebSphere MQ managed .NET applications.\n\nPlatforms affected:\nWindows\n\n****************************************************************\nPROBLEM SUMMARY:\nWebSphere MQ managed .NET application intermittently reports\nMQRC_CONNECTION_BROKEN error during disconnect with the\nfollowing exception.\n\nSystem.Net.Sockets.SocketException\nMessage: An invalid argument was supplied\nStackTrace:\nat System.Net.Sockets.Socket.Shutdown(SocketShutdown how)\nat IBM.WMQ.MQTCPConnection.CloseSocket()\nat IBM.WMQ.MQFAPConnection.Close(MQTSH tshc)\nat IBM.WMQ.MQFAPConnection.Disconnect()\nat IBM.WMQ.MQFAP.Disconnect(Int32 hConn, Int32& compCode,\nInt32& reason)\nat IBM.WMQ.Nmqi.ManagedNmqiMQ.MQDISC(Phconn phconn, Int32&\npCompCode, Int32& pReason)\n\nThis was because the System.Net.Sockets.Socket.Shutdown invoked\nwhile closing the socket was intermittently reporting\nSocketException.\n
\n \n
Problem conclusion
\n- \n
- \n \n
System.Net.Sockets.Socket.Shutdown invoked while closing the\nsocket intermittently reports SocketException. The WebSphere MQ\n.NET code is modified to ignore this exception and proceed\ntowards closing the socket.\n\n---------------------------------------------------------------\nThe fix is targeted for delivery in the following PTFs:\n\n v7.0\nPlatform Fix Pack 7.0.1.11\n-------- --------------------\nWindows 7.0.1.11\n\n v7.1\nPlatform Fix Pack 7.1.0.3\n-------- --------------------\nWindows 7.1.0.3\n\nPlatform v7.5\n-------- --------------------\nMultiplatforms 7.5.0.2\n\nThe latest available maintenance can be obtained from\n'WebSphere MQ Recommended Fixes'\nhttp://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037\n\nIf the maintenance level is not yet available information on\nits planned availability can be found in 'WebSphere MQ\nPlanned Maintenance Release Dates'\nhttp://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309\n---------------------------------------------------------------\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
IC88165
\n Reported component name
WMQ WINDOWS V7
\n Reported component ID
5724H7220
\n Reported release
701
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2012-11-12
\n Closed date
2013-01-31
\n Last modified date
2013-01-31
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
WMQ WINDOWS V7
\n Fixed component ID
5724H7220
\n
Applicable component levels
\n- \n
R701 PSY
UP
\n
\n
\n
",
+ "title": "IBM IC88165: WEBSPHERE MQ REPORTS MQRC_CONNECTION_BROKEN ERROR DURING CLIENT DISCONNECT - United States",
+ "text": " FIXES ARE AVAILABLE\nWebSphere MQ V7.5 Fix Pack 7.5.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24035286]\nFix Pack 7.1.0.3 for WebSphere MQ V7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24035405]\nWebSphere MQ V7.0 Fix Pack 7.0.1.11 [http://www-01.ibm.com/support/docview.wss?uid=swg24035750]\nWebSphere MQ v7.5.0.2 Hypervisor for RHEL [http://www-01.ibm.com/support/docview.wss?uid=swg24036533]\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 * WebSphere MQ managed .NET application reports\n MQRC_CONNECTION_BROKEN error during disconnect. The following\n error is reported in the event viewer:\n \n MQRC_CONNECTION_BROKEN\n EventWatcher\\Match Message In\n at IBM.WMQ.MQQueueManager.Disconnect()\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n WebSphere MQ managed .NET applications.\n \n Platforms affected:\n Windows\n \n ****************************************************************\n PROBLEM SUMMARY:\n WebSphere MQ managed .NET application intermittently reports\n MQRC_CONNECTION_BROKEN error during disconnect with the\n following exception.\n \n System.Net.Sockets.SocketException\n Message: An invalid argument was supplied\n StackTrace:\n at System.Net.Sockets.Socket.Shutdown(SocketShutdown how)\n at IBM.WMQ.MQTCPConnection.CloseSocket()\n at IBM.WMQ.MQFAPConnection.Close(MQTSH tshc)\n at IBM.WMQ.MQFAPConnection.Disconnect()\n at IBM.WMQ.MQFAP.Disconnect(Int32 hConn, Int32& compCode,\n Int32& reason)\n at IBM.WMQ.Nmqi.ManagedNmqiMQ.MQDISC(Phconn phconn, Int32&\n pCompCode, Int32& pReason)\n \n This was because the System.Net.Sockets.Socket.Shutdown invoked\n while closing the socket was intermittently reporting\n SocketException.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * System.Net.Sockets.Socket.Shutdown invoked while closing the\n socket intermittently reports SocketException. The WebSphere MQ\n .NET code is modified to ignore this exception and proceed\n towards closing the socket.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n v7.0\n Platform Fix Pack 7.0.1.11\n -------- --------------------\n Windows 7.0.1.11\n \n v7.1\n Platform Fix Pack 7.1.0.3\n -------- --------------------\n Windows 7.1.0.3\n \n Platform v7.5\n -------- --------------------\n Multiplatforms 7.5.0.2\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 IC88165\n \n \n * REPORTED COMPONENT NAME\n WMQ WINDOWS V7\n \n \n * REPORTED COMPONENT ID\n 5724H7220\n \n \n * REPORTED RELEASE\n 701\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 2012-11-12\n \n \n * CLOSED DATE\n 2013-01-31\n \n \n * LAST MODIFIED DATE\n 2013-01-31\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 * R701 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1IC88165",
+ "date": "2013-01-31",
+ "productName": "WebSphere MQ",
+ "productId": "SSFKSJ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1IC88165"
+ }
+ },
+ "swg21418121": {
+ "id": "swg21418121",
+ "content": "
\n
\n\n\n\n
\nPI projectinterchange save saveas winzip
\n\n\n \n \n
\n
\n
\nTechnote (troubleshooting)
\n \n
\n
\n \n
Problem(Abstract)
\nHow to export an IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) message flow as a .zip file?
\nResolving the problem
\n\n
Your project files will be exported to the .zip file and location that you specified.\n
\n A .zip file of workspace objects was commonly referred to as a "Project Interchange" file.
To export your WMB/IIB projects as a .zip file, start in the Toolkit:
- \n
- Select File -> Export. (The Export menu opens.) \n
- Select Other -> Project Interchange, and then click Next. (The Export Project Interchange Information window opens.) \n
- Select the projects that you want to export, enter a name for your .zip file, and then click Finish.
Please include all subflows, message sets, and java projects that are dependencies for your project(s). \n
Your project files will be exported to the .zip file and location that you specified.\n
\n
\n \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Integration | \nIBM Integration Bus | \nToolkit | \nLinux, Windows | \n9.0 | \n\n |
\n
\n
\n \n \nProduct Alias/Synonym
\nWMBT WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI
\n",
+ "title": "IBM Exporting your Applications and message flow projects as a .zip file from the WebSphere Message Broker or IBM Integration Bus Toolkit - United States",
+ "text": "PI projectinterchange save saveas winzip TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to export an IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) message flow as a .zip file? \n\nRESOLVING THE PROBLEM\nA .zip file of workspace objects was commonly referred to as a \"Project Interchange\" file.\nTo export your WMB/IIB projects as a .zip file, start in the Toolkit: \n\n 1. Select File -> Export. (The Export menu opens.) \n 2. Select Other -> Project Interchange, and then click Next. (The Export Project Interchange Information window opens.) \n 3. Select the projects that you want to export, enter a name for your .zip file, and then click Finish.\n Please include all subflows, message sets, and java projects that are dependencies for your project(s).\n\n\nYour project files will be exported to the .zip file and location that you specified. \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Toolkit Linux, Windows 9.0 \nPRODUCT ALIAS/SYNONYM\n WMBT WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI",
+ "metadata": {
+ "sourceDocumentId": "swg21418121",
+ "date": "2014-12-16",
+ "productName": "WebSphere Message Broker",
+ "productId": "SSKM8N,SSNQK6",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21418121"
+ }
+ },
+ "nas8N1014746": {
+ "id": "nas8N1014746",
+ "content": "
\n
",
+ "title": "IBM Print an LPAR Configuration (Pre V7 HMC) - United States",
+ "text": "CONFIG; HMC; LPAR; PRINT TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document provides a process to print the partition profile configurations of a partitioned system. \n\nRESOLVING THE PROBLEM\nUse the following process to print the partition profile configurations of a partitioned system. \n\nRequirements \n\no HMC level 5.2.0 or newer o WebSM loaded on a network PC that also has access to a printer \nThe first thing that you need is a system plan entry. If one does not already exist or if you do not know if it is current, use either Task I or Task IA to \ngenerate a system plan. If you have a current existing system plan, skip to Task II. \n\n[/support/docview.wss?uid=nas8N1014746&aid=1] Task I: Generating a current system plan (command line) 1 On the HMC bring up the restricted shell.\n\nN.B. If you're connecting to the HMC with an SSH client like Putty, proceed to step 5. 2 Right-click on the desk top. 3 Select Terminals. 4 Select rshterm. 5 In the restricted shell, type the following command:\n\nmksysplan -f \n\n
\nCONFIG; HMC; LPAR; PRINT
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n \n \n\n
Problem(Abstract)
\nThis document provides a process to print the partition profile configurations of a partitioned system.
\nResolving the problem
\n\n
The first thing that you need is a system plan entry. If one does not already exist or if you do not know if it is current, use either Task I or Task IA to\n
generate a system plan. If you have a current existing system plan, skip to Task II. \n
\n
\n
\n Use the following process to print the partition profile configurations of a partitioned system.
\nRequirements
\n\n \n \n
\n
\n | o | \nHMC level 5.2.0 or newer | \n
| o | \nWebSM loaded on a network PC that also has access to a printer | \n
The first thing that you need is a system plan entry. If one does not already exist or if you do not know if it is current, use either Task I or Task IA to\n
generate a system plan. If you have a current existing system plan, skip to Task II. \n
\n
\n
\n \n \n
\n
\n | Task I: Generating a current system plan (command line) | \n|
| 1 | \nOn the HMC bring up the restricted shell. N.B. If you're connecting to the HMC with an SSH client like Putty, proceed to step 5. | \n
| 2 | \nRight-click on the desk top. | \n
| 3 | \nSelect Terminals. | \n
| 4 | \nSelect rshterm. | \n
| 5 | \nIn the restricted shell, type the following command: mksysplan -f <some filename>.sysplan -m <managed system’s name> -d <a description> Examples: mksysplan -f sampletestplan.sysplan -m samplesystem -d plan to print mksysplan -f sysplan.sysplan -m 9406-570*3413556 -d "New 570 system plan for 11/4/05" | \n
| Task IA: Generating a current system plan (GUI) | \n|
| 1 | \nFrom either the local HMC or a WebSM session, | \n
| 2 | \nIn the Navigation Area, expand the managed system and select System Plans. | \n
| 3 | \nSelect Manage Syststem Plans in the task area. | \n
| 4 | \nFrom the button row along the bottom of the dialog, select Create. | \n
| 5 | \nVerify that the selected managed system is correct and change if required. Give the system plan a name and description. Click Create. | \n
| 6 | \nWhen the completion dialog is posted, click OK. | \n
| 7 | \nClick Cancel to close the Manage System Plans dialog. | \n
| Task II: Displaying the system plan | \n|
| 1 | \nBring up a WebSM session on the network PC. | \n
| 2 | \nOn the Navigation side, go to System Plans. | \n
| 3 | \nOn the context side, select Manage System Plans. | \n
| 4 | \nRight-click on the current existing plan or the one created in Step 5. | \n
| 5 | \nSelect the view button. | \n
| 6 | \nA Web browser window will open with a System Plan Viewer screen that requires you to log in. Use the same login ID and password that were used to log on the HMC. | \n
| 7 | \nA screen that has the configuration will be displayed. To print the system plan, select Print from the upper right or select File > Print from the browser menu. | \n
\n \n
\n Historical Number
\n428344602
\n\n
\n\n\n\n
\n
\n
\nz/os
\n\n \n \n
\n \n
\nAPAR status
\n- \n
Closed as fixed if next.
\n
Error description
\n- \n
- \n \n
You are running CICS Transaction Server 4.2 and receive the\nfollowing messages after an earlier abend in DFHTFXM's\nrecovery routine:\nDFHXM0001 An abend (code ---/AKEA) has occurred at\n at offset X'1206' in module DFHXMTA.\nDFHAP0001 An abend (code 0C4/AKEA) has occurred at\n offset X'07EA' in module DFHAPEX.\nDFHAP0001 An abend (code 0C4/AKEA) has occurred at\n offset X'07E6' in module DFHAPEX.\n.\nThis AP0001 error repeats until you receive:\nDFHKE0303 A RECURSIVE ABEND HAS BEEN DETECTED BY THE KERNEL\n DOMAIN.\nDFHKE1800 ABNORMAL TERMINATION OF CICS IS COMPLETE.\n.\nDFHXMTA's recovery routine was driven and calls routine\nCLEAN_UP_TXN. This zeros out the TXN from the TASENTRY, which\nis later referenced by DFHAPEX leading to the OC4.\n\n\nAdditional Symptom(s) Search Keyword(s): KIXREVDAM\nCQRY CICS Crash Crashes\nIn another case the following message was also issued:\nDFHME0118 AN ERROR HAS OCCURRED WHEN CALLING THE MESSAGE USER\n EXIT FOR MESSAGE DFHME0116\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
****************************************************************\n* USERS AFFECTED: All CICS users *\n****************************************************************\n* PROBLEM DESCRIPTION: Recursive DFHAP0001 abends in DFHAPEX *\n* eventually leading to CICS crashing *\n* with DFHKE1800 *\n****************************************************************\n* RECOMMENDATION: *\n****************************************************************\nA CQRY task is running, it encounters an ATNI abend in its\ninitialization stage of the task when binding the transaction's\nterminal client. The DFHTFXM's recovery routine is entered to\nhandle the ATNI abend, however a program check occurs in the\nrecovery routine. So DFHTFXM's recovery is entered again.\nThe abend processing causes the abend percolated to an upper\nstack, which is owned by DFHXMTA. DFHXMTA's recovery routine is\nentered and it completes cleaning the task's transaction token.\nAfter that, DFHXMTA issues an XM0001 message and DFHAPEX is\ndriven as part of the dump processing because XDUREQ is active.\nDFHAPEX is trying to pass some parameter to the exit but 0C4\noccurs because the transaction token has been cleared. DFHAPEX\nabends and DFHAPEX is driven again but the same situation\noccurs. Finally the recursive abends in DFHAPEX lead to CICS\ncrashing with DFHKE1800.\nkeyword: msgDFHKE1800\n
\n \n
Problem conclusion
\n- \n
Temporary fix
\n- \n
Comments
\n- \n
- \n \n
This APAR is being closed FIN with concurrence from the\nsubmitting customer. This means that a fix to this APAR is\nexpected to be delivered from IBM in a release which is being\ndeveloped at the time that the APAR was closed.\nThe latest release of the product to exit development at the\ntime this APAR was closed was:\n CICS Transaction Server for z/OS V4.2.\nSPA57872 SPA 57872\n
\n \n
APAR Information
\n \n
\n - \n
APAR number
PM71370
\n Reported component name
CICS TS Z/OS V4
\n Reported component ID
5655S9700
\n Reported release
700
\n Status
CLOSED FIN
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2012-08-22
\n Closed date
2012-09-19
\n Last modified date
2012-09-19
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
R700 PSY
UP
\n
\n
\n
",
+ "title": "IBM PM71370: RECURSIVE DFHAP0001 ABENDS IN DFHAPEX EVENTUALLY LEADING TO CICS CRASHING WITH DFHKE1800 - United States",
+ "text": "z/os 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 * You are running CICS Transaction Server 4.2 and receive the\n following messages after an earlier abend in DFHTFXM's\n recovery routine:\n DFHXM0001 An abend (code ---/AKEA) has occurred at\n at offset X'1206' in module DFHXMTA.\n DFHAP0001 An abend (code 0C4/AKEA) has occurred at\n offset X'07EA' in module DFHAPEX.\n DFHAP0001 An abend (code 0C4/AKEA) has occurred at\n offset X'07E6' in module DFHAPEX.\n .\n This AP0001 error repeats until you receive:\n DFHKE0303 A RECURSIVE ABEND HAS BEEN DETECTED BY THE KERNEL\n DOMAIN.\n DFHKE1800 ABNORMAL TERMINATION OF CICS IS COMPLETE.\n .\n DFHXMTA's recovery routine was driven and calls routine\n CLEAN_UP_TXN. This zeros out the TXN from the TASENTRY, which\n is later referenced by DFHAPEX leading to the OC4.\n \n \n Additional Symptom(s) Search Keyword(s): KIXREVDAM\n CQRY CICS Crash Crashes\n In another case the following message was also issued:\n DFHME0118 AN ERROR HAS OCCURRED WHEN CALLING THE MESSAGE USER\n EXIT FOR MESSAGE DFHME0116\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All CICS users *\n ****************************************************************\n * PROBLEM DESCRIPTION: Recursive DFHAP0001 abends in DFHAPEX *\n * eventually leading to CICS crashing *\n * with DFHKE1800 *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A CQRY task is running, it encounters an ATNI abend in its\n initialization stage of the task when binding the transaction's\n terminal client. The DFHTFXM's recovery routine is entered to\n handle the ATNI abend, however a program check occurs in the\n recovery routine. So DFHTFXM's recovery is entered again.\n The abend processing causes the abend percolated to an upper\n stack, which is owned by DFHXMTA. DFHXMTA's recovery routine is\n entered and it completes cleaning the task's transaction token.\n After that, DFHXMTA issues an XM0001 message and DFHAPEX is\n driven as part of the dump processing because XDUREQ is active.\n DFHAPEX is trying to pass some parameter to the exit but 0C4\n occurs because the transaction token has been cleared. DFHAPEX\n abends and DFHAPEX is driven again but the same situation\n occurs. Finally the recursive abends in DFHAPEX lead to CICS\n crashing with DFHKE1800.\n keyword: msgDFHKE1800\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n * This APAR is being closed FIN with concurrence from the\n submitting customer. This means that a fix to this APAR is\n expected to be delivered from IBM in a release which is being\n developed at the time that the APAR was closed.\n The latest release of the product to exit development at the\n time this APAR was closed was:\n CICS Transaction Server for z/OS V4.2.\n SPA57872 SPA 57872\n \n \n \n \n \n\nAPAR INFORMATION\n * APAR NUMBER\n PM71370\n \n \n * REPORTED COMPONENT NAME\n CICS TS Z/OS V4\n \n \n * REPORTED COMPONENT ID\n 5655S9700\n \n \n * REPORTED RELEASE\n 700\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 2012-08-22\n \n \n * CLOSED DATE\n 2012-09-19\n \n \n * LAST MODIFIED DATE\n 2012-09-19\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 * R700 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1PM71370",
+ "date": "2012-09-19",
+ "productName": "CICS Transaction Server",
+ "productId": "SSGMGV,SWG90",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PM71370"
+ }
+ },
+ "swg21299781": {
+ "id": "swg21299781",
+ "content": "
\n
\n\n\n\n
\nExtensions MBFE; TX MustGatherDocument MustGather; MustGathers; Must Gather; Collect Troubleshooting Data; MustGatherDocument; Collecting; Trouble; Shooting
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n \n\n
Problem(Abstract)
\n You are experiencing problems with Adapters in WebSphere Message Broker (WMB) or IBM Integration Bus (IIB).
This mustgather document explains how to troubleshoot this problem by yourself, how to generate diagnostic data when the problem is happening, how to collect the available data from your system, and how to share that data with IBM support.
Environment
\n\n
\n These instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.
Return to the WebSphere Message Broker MustGather index for other systems.
Resolving the problem
\n\n
\n
\n
\n
\n
\n \n
\n
\n \n
\n
\n
\n
\n \n
- \n
- Consider Using the Test Client in trace and debug mode. \n
- A user level trace is intended to assist users with understanding how their ESQL is processed.
It will also show a high level view of the message flow behavior. \n - Check for known issues:
WebSphere Adapter nodesTransport and connectivity samples
Resolving problems when developing message flows with WebSphere Adapter nodes
Integrating WMB with SAP
WebSphere Message Broker support site
\n
\n
\n
\n
\n
\n
\n \n
\n
\n \n
\n
\n
\n
\n \n
- \n
- mqsidc
See: mqsidc usage instructions
\n- \n
- This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, and IIB 9.0. \n
- When running the tool, select the option for 'Broker Collector', when prompted. \n
\n - Project Interchange files for the problematic flow/set/ESQL/model
\n- \n
- You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.
See: Backing up the Toolkit Workspace \n
\n - You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.
- Refer to Adapter troubleshooting MustGathers \n
- Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces can be used to gain a better understanding of the problem. \n
- \n
- A user level trace is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior. \n
- A service level trace is intended to be provided to IBM Support to assist in the diagnosis of your issue. \n
- RFC traces:
Steps to enable and collect the RFC Traces:
1. Launch the Adapter Connection Wizard ,and proceed to the 'Service Generation and Deployment Configuration' window. In the SAP RFC trace configuration section:
-Set the RFCTraceOn property to 'true'
-Set the RFC Trace Level property to '8' , which outputs verbose debug messages, full
execution path, info messages, errors and warnings
-Set the Folder for RFC trace files property to the directory location where the RFC Traces
are created
* Alternatively, these properties may also be set on SAPConnection configurable service using mqsichangeproperties command or MB Explorer, which would require a broker/execution group restart.
For example: mqsichangeproperties <broker> -c SAPConnection -o Template -n RFCTraceOn -v true
2. Recreate the issue.
3. Collect the RFC trace files generated.
Note: The trace files are created in the directory where the adapter process has been started by default. The trace file has a .trc file extension and the file name will start with the letters rfc followed by a unique identifier. For example, rfc03912_02220.trc. \n
\n - General Broker information
If the mqsidc tool was not run, then capture this information manually \n- \n
- Record the WebSphere Message Broker version, release, and maintenance level.
This can be captured using the command 'mqsiservice -v'.. \n - Record the operating system version, release, and maintenance level. \n
- Record the version, release, and maintenance level of any related products and components for the problematic application. \n
- Collect the local error log. On UNIX and Linux systems, the local error log is the syslog. The location of your syslog is configured in the syslog daemon.
See: Configuring the syslog daemon \n - Collect the Standard Output/Error logs.
WMB writes information to both STDOUT and STDERR. These files are located under the Message Broker workpath.
See: Standard System Logs \n
\n - Record the WebSphere Message Broker version, release, and maintenance level.
\n
\n
\n
\n
\n
ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!
When sending data to IBM, be sure to update your PMR or send a note with the following information:
- \n
- Tell us what errors you saw, where you saw them, and what time they happened
- Let us know if you made any changes to WebSphere Message Broker or the system before the problem
- Share any other observations which you think will help us to better understand the problem \n
\n
\n \n
\n
\n \n
\n
\n
\n \n
- \n
- Use IBM Service Request to open or view a problem record with IBM. \n
- Send your data to IBM for further analysis. \n
\n
\n
\n
Please see the IBM Software Support Handbook for more information on working with IBM support.
\n \n
\n \n \n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Integration | \nIBM Integration Bus | \n\n | AIX, HP-UX, Linux, Solaris | \n10.0, 9.0 | \nAll Editions | \n
\n
Product Alias/Synonym
\nWMBFE MBFE WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI
\n",
+ "title": "IBM WMB/IIB MustGather: Problems with Adapters on UNIX and Linux - United States",
+ "text": "Extensions MBFE; TX MustGatherDocument MustGather; MustGathers; Must Gather; Collect Troubleshooting Data; MustGatherDocument; Collecting; Trouble; Shooting TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are experiencing problems with Adapters in WebSphere Message Broker (WMB) or IBM Integration Bus (IIB).\nThis mustgather document explains how to troubleshoot this problem by yourself, how to generate diagnostic data when the problem is happening, how to collect the available data from your system, and how to share that data with IBM support.\n\n\nENVIRONMENT\nThese instructions are for WebSphere Message Broker or IBM Integration Bus on AIX, HP-UX, Linux, and Solaris systems.\nReturn to the WebSphere Message Broker MustGather index [http://www-01.ibm.com/support/docview.wss?uid=swg21209857] for other systems.\n\nRESOLVING THE PROBLEM\n\n\n\nSTEP 1: SELF-GUIDED TROUBLESHOOTING\n\n 1. Consider Using the Test Client in trace and debug mode [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/af52260_.htm].\n 2. \n 3. A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed.\n It will also show a high level view of the message flow behavior.\n 4. \n 5. Check for known issues:\n WebSphere Adapter nodes [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/ac37160_.htm] Transport and connectivity samples [https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ax20230_.htm]\n Resolving problems when developing message flows with WebSphere Adapter nodes [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/au16538_.htm]\n Integrating WMB with SAP [http://www-01.ibm.com/support/docview.wss?uid=swg27018476&aid=1]\n [http://www.ibm.com/software/htp/cics/tserver/support/]WebSphere Message Broker support site [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Message_Broker]\n \n \n \n\n\n\nSTEP 2: COLLECT DATA\n\n 1. mqsidc\n See: mqsidc usage instructions [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bu46010_.htm]\n * This command line tool is only available for WMB 7.0.0.5+, WMB 8.0.0.1+, and IIB 9.0.\n * When running the tool, select the option for 'Broker Collector', when prompted.\n \n \n 2. \n 3. Project Interchange files for the problematic flow/set/ESQL/model\n * You can export your Message Flow and Message Set project(s) into an archive file for easy transmission to IBM Support.\n See: Backing up the Toolkit Workspace [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/an27100_.htm] \n \n \n 4. \n 5. Refer to Adapter troubleshooting MustGathers [http://www-01.ibm.com/support/docview.wss?uid=swg21438193] \n 6. Traces If the problem occurs during a runtime test or with the Toolkit test facility, WMB execution group traces [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321] can be used to gain a better understanding of the problem. * A user level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#1] is intended to assist users with understanding how their ESQL is processed. It will also show a high level view of the message flow behavior.\n * A service level trace [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177321#2] is intended to be provided to IBM Support to assist in the diagnosis of your issue.\n * RFC traces:\n Steps to enable and collect the RFC Traces:\n 1. Launch the Adapter Connection Wizard ,and proceed to the 'Service Generation and Deployment Configuration' window. In the SAP RFC trace configuration section:\n -Set the RFCTraceOn property to 'true' \n -Set the RFC Trace Level property to '8' , which outputs verbose debug messages, full \n execution path, info messages, errors and warnings\n -Set the Folder for RFC trace files property to the directory location where the RFC Traces\n are created\n * Alternatively, these properties may also be set on SAPConnection configurable service [https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bn28742_.htm] using mqsichangeproperties command or MB Explorer, which would require a broker/execution group restart. \n For example: mqsichangeproperties
\n
",
+ "title": "IBM PM07677: NEW SITE WIZARD TEMPLATES NOT DEPLOYING THE WCM HIDDEN PAGE IN NEW VIRTUAL PORTALS. - United States",
+ "text": " 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 * New Site Wizard templates not deploying the WCM hidden page in\n new virtual portals. This can introduce problems working with\n WCM on a virtual portal.\n \n \n Symptoms include:\n \n After creating a new site using the site wizard:\n \n If you are using inline editing in a virtual portal and click\n the insert image icon in the default RTE the popup does not come\n up correctly.\n \n The popup window will have several copies of the insert image\n dialog, one for every portlet on the calling page.\n \n \n \n \n \n\nLOCAL FIX\n * For existing virtual portal created with the new site wizard,\n use xmlaccess to export hidden WCM page from base portal and\n import into virtual portal.\n \n Hidden page is: com.ibm.wps.hiddenpage.wcm.Authoring_Portlet\n \n For new virtual portals created with the new site wizard:\n \n Update the xml in the template used to create the site, similar\n to:\n \n \n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
New Site Wizard templates not deploying the WCM hidden page in\nnew virtual portals. This can introduce problems working with\nWCM on a virtual portal.\n\n\nSymptoms include:\n\nAfter creating a new site using the site wizard:\n\nIf you are using inline editing in a virtual portal and click\nthe insert image icon in the default RTE the popup does not come\nup correctly.\n\nThe popup window will have several copies of the insert image\ndialog, one for every portlet on the calling page.\n
\n \n
Local fix
\n- \n
- \n \n
For existing virtual portal created with the new site wizard,\nuse xmlaccess to export hidden WCM page from base portal and\nimport into virtual portal.\n\nHidden page is: com.ibm.wps.hiddenpage.wcm.Authoring_Portlet\n\nFor new virtual portals created with the new site wizard:\n\nUpdate the xml in the template used to create the site, similar\nto:\n\n<content-node action="update" active="true"\nallportletsallowed="false"\ncontent-parentref="6_000000000000000000000000A0"\ncreate-type="explicit" domain="rel"\nobjectid="<value>" ordinal="3250"\ntype="page"\nuniquename="com.ibm.wps.hiddenpage.wcm.Authoring_Portlet">\n<supported-markup markup="html" update="set"/>\n<parameter name="com.ibm.portal.Hidden" type="string"\nupdate="set"><![CDATA[true]]></parameter>\n<access-control externalized="false" owner="undefined"\nprivate="false">\n<role actionset="Privileged User" update="set">\n<mapping subjectid="@VpUserGroup@" subjecttype="user_group"\nupdate="set"/>\n</role>\n</access-control>\n<component action="update" active="true" deletable="undefined"\ndomain="rel" modifiable="undefined"\nobjectid="<value>" ordinal="200"\norientation="H" type="container" width="undefined"/>\n</content-node>\n
\n \n
Problem summary
\n- \n
- \n \n
New Site Wizard templates not deploying the WCM hidden page in\nnew virtual portals. This can introduce problems working with\nWCM on a virtual portal.\n
\n \n
Problem conclusion
\n- \n
- \n \n
Added the hidden WCM Authoring page for inline editing in the\nDepartment Internet and Internet site templates.\n\nFailing Module(s):\n\n New Site Wizard\n\nAffected Users:\n WebSphere Portal Users working with WCM on a virtual portal.\n\nVersion Information:\n\n Portal Version(s): 6.1.0.x\n Pre-Requisite(s):\n Co-Requisite(s): ---\n\n\nPlatform Specific:\n This fix applies to all platforms.\n\nA fix is available from the IBM WebSphere Portal Business\nSolutions Catalog:\nhttp://www.ibm.com/software/brandcatalog/portal/portal/details?c\natalog.label=1WP1001N7\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PM07677
\n Reported component name
WEBSPHERE PORTA
\n Reported component ID
5724E7600
\n Reported release
61C
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2010-02-16
\n Closed date
2010-03-15
\n Last modified date
2010-03-15
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
WEBSPHERE PORTA
\n Fixed component ID
5724E7600
\n
Applicable component levels
\n- \n
R610 PSY
UP
\n R615 PSY
UP
\n R61A PSY
UP
\n R61B PSY
UP
\n R61C PSY
UP
\n
\n
\n
\n
",
+ "title": "IBM RAVE widgets unavailable after rolling back a Dashboard Application Services Hub Version 3.1.2 upgrade installation - United States",
+ "text": "jazzsm1120relnotes DASH TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Rolling back Dashboard Application Services Hub Version 3.1.2, which is delivered in Jazz for Service Management Version 1.1.2, to Dashboard Application Services Hub Version 3.1.1 removes the Data Visualization widgets, also known as Rapidly Adaptive Visualization Engine (RAVE) widgets, instead of redeploying the previous version of the widgets. \n\nSYMPTOM\nWhen you roll back, the RAVE widgets are no longer available in Dashboard Application Services Hub Version 3.1.1, which is delivered as part of Jazz for Service Management Version 1.1.1.\n\n\nCAUSE\nRAVE widgets were first made available in Dashboard Application Service Hub Version 3.1.1, so when users rolled back to the previous version, RAVE was correctly removed. This behavior was incorrectly maintained for the Version 3.1.2 rollback.\n\nRESOLVING THE PROBLEM\nThis issue will be resolved with the release of Dashboard Application Services Hub Version 3.1.2.1, which will be delivered in Jazz for Service Management 1.1.2.1.\n\n\nCurrently, if you roll back Version 3.1.2 to Version 3.1.1 and then upgrade to Version 3.1.2 again, the problem is resolved. \n\nAlternatively, if you do not want to upgrade to Version 3.1.2 after rolling back from Version 3.1.1, then to resolve the problem, do the following: \n\n 1. Extract the dash.ravewidget.war directory from JazzSM_HOME/ui/installableApps/iscapp.zip and place it in a temporary directory, for example, /tmp. \n 2. Stop the WebSphere Application Server instance associated with your Dashboard Application Services Hub environment: * At the command line, change to JazzSM_HOME/profile/bin and run the following command:\n ./stopServer.sh|bat server1 -username was_admin_userID -password was_admin_password\n \n \n 3. In the JazzSM_HOME/profile/bin directory, run the following command:\n ./wsadmin.sh|bat -conntype NONE -username was_admin_userID -password was_admin_password \n 4. At the wsadmin command line, use the following command to redeploy the RAVE component:\n $AdminApp update isc modulefile {-operation addupdate -contents /tmp/dash.ravewidget.war -contenturi dash.ravewidget.war -usedefaultbindings -contextroot /DASHRaveWidget -MapWebModToVH {{.* .* default_host}}} \n 5. Save your settings and quit from the wsadmin command line, as follows: 1. $AdminApp save \n 2. $AdminApp quit \n \n \n 6. Start the WebSphere Application Server instance associated with your Dashboard Application Services Hub environment: * At the command line, change to JazzSM_HOME/profile/bin and run the following command:\n ./startServer.sh|bat server1",
+ "metadata": {
+ "sourceDocumentId": "swg21960630",
+ "date": "2015-06-30",
+ "productName": "Tivoli Components Jazz for Service Management",
+ "productId": "SSRLR8",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21960630"
+ }
+ },
+ "swg24039916": {
+ "id": "swg24039916",
+ "content": "\n\n
\njazzsm1120relnotes DASH
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\nRolling back Dashboard Application Services Hub Version 3.1.2, which is delivered in Jazz for Service Management Version 1.1.2, to Dashboard Application Services Hub Version 3.1.1 removes the Data Visualization widgets, also known as Rapidly Adaptive Visualization Engine (RAVE) widgets, instead of redeploying the previous version of the widgets.
\nSymptom
\n\n
\n When you roll back, the RAVE widgets are no longer available in Dashboard Application Services Hub Version 3.1.1, which is delivered as part of Jazz for Service Management Version 1.1.1.
\n\n
Cause
\n\n
\n RAVE widgets were first made available in Dashboard Application Service Hub Version 3.1.1, so when users rolled back to the previous version, RAVE was correctly removed. This behavior was incorrectly maintained for the Version 3.1.2 rollback.
\nResolving the problem
\n\n
\n This issue will be resolved with the release of Dashboard Application Services Hub Version 3.1.2.1, which will be delivered in Jazz for Service Management 1.1.2.1.
Currently, if you roll back Version 3.1.2 to Version 3.1.1 and then upgrade to Version 3.1.2 again, the problem is resolved.
\nAlternatively, if you do not want to upgrade to Version 3.1.2 after rolling back from Version 3.1.1, then to resolve the problem, do the following:
\n- \n
- Extract the dash.ravewidget.war directory from JazzSM_HOME/ui/installableApps/iscapp.zip and place it in a temporary directory, for example, /tmp. \n
- Stop the WebSphere Application Server instance associated with your Dashboard Application Services Hub environment: \n
- \n
- At the command line, change to JazzSM_HOME/profile/bin and run the following command:
./stopServer.sh|bat server1 -username was_admin_userID -password was_admin_password \n
\n - At the command line, change to JazzSM_HOME/profile/bin and run the following command:
- In the JazzSM_HOME/profile/bin directory, run the following command:
./wsadmin.sh|bat -conntype NONE -username was_admin_userID -password was_admin_password \n - At the wsadmin command line, use the following command to redeploy the RAVE component:
$AdminApp update isc modulefile {-operation addupdate -contents /tmp/dash.ravewidget.war -contenturi dash.ravewidget.war -usedefaultbindings -contextroot /DASHRaveWidget -MapWebModToVH {{.* .* default_host}}} \n - Save your settings and quit from the wsadmin command line, as follows: \n
- \n
- $AdminApp save \n
- $AdminApp quit \n
\n - Start the WebSphere Application Server instance associated with your Dashboard Application Services Hub environment: \n
- \n
- At the command line, change to JazzSM_HOME/profile/bin and run the following command:
./startServer.sh|bat server1 \n
\n - At the command line, change to JazzSM_HOME/profile/bin and run the following command:
\n
\n \n
\n
\n \n \n\n
\n\n\n\n
\n\n \n \n
\nDownloadable files
\n \n
\n
\n
\n
\n \n \n\n
Abstract
\nThis cumulative fix pack updates Operational Decision Manager V8.8 or V8.8.1 to V8.8.1.1.
\nDownload Description
\n\n
\n Installing with the Installation Manager command line: \n
\n Applying the fix pack\n
After you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack.\n
\n This fix pack is entitled. Only customers who have Operational Decision Manager V8.8 or V8.8.1 can use this fix pack. You do not have to install the latest version to apply this fix pack.
How to install the fix pack
For each of your Operational Decision Manager components:
- \n
- Download its fix pack in the following table.
Select the file that corresponds with your operating system (<OS>): AIX, HPUX, LIN_PPC, LIN_S390, LIN_X86, OS400, SOL_SPARC, SOL_X86, and WIN. \n - Extract the contents of the download file to a new folder. Use the corresponding folder name in the table. \n
- If you use WebSphere Application Server, download the profile templates for your component. \n
\n \n \n
\n
\n Installing with IBM Installation Manager: \n | Component | \nDownload file | \nFolder name (InstallDir) | \nNote | \n
| Decision Server Insights | \n8.8.1-WS-ODM_DSI-<OS>-FP001.zip | \nDSI | \nOnly available for Linux (LIN) and Windows (WIN). | \n
| Decision Center | \n8.8.1-WS-ODM_DC-<OS>-FP001.zip | \nWDC | \nFor Windows and Linux, use <install path of ODM 8.8.1>/jdk/bin/jar xf to extract files in the WDC directory. | \n
| Decision Server Rules | \n8.8.1-WS-ODM_DSR-<OS>-FP001.zip | \nDSR | \n|
| Decision Server Events | \n8.8.1-WS-ODM_DSE-<OS>-FP001.zip | \nDSE | \n|
| Decision Center profile templates for WebSphere Application Server | \n8.8.1-WS-ODM_PTDC-FP001.zip | \nWDC_PT | \n|
| Decision Server Rules profile templates for WebSphere Application Server | \n8.8.1-WS-ODM_PTR-FP001.zip | \nDSR_PT | \n|
| Decision Server Events profile templates for WebSphere Application Server | \n8.8.1-WS-ODM_PTE-FP001.zip | \nDSE_PT | \n
- \n
- Launch IBM Installation Manager. \n
- Open File > Preferences > Repositories. \n
- For each component that you use:
a. Click Add Repository.
b. Browse to the extracted folder <InstallDir>/updates.
c. Select the repository.config file. \n - Make sure the repositories are selected in Repositories. \n
- Click Apply to save your changes, and click OK to close Repositories. \n
- Click Update to update your installation. \n
- Follow the instructions in the installation manager to complete the installation. \n
\n Installing with the Installation Manager command line: \n
- \n
- Locate the imcl command under <IM installation>/eclipse/tools. \n
- Run the command imcl updateAll -repositories WDC/updates, DSR/updates, DSE/updates -acceptLicense. \n
- \n
- Use the option -installDirectory <install path of ODM 8.8.1> to update a specific installation. \n
- If you update only one component, specify the repository accordingly. \n
\n Applying the fix pack\n
After you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack.\n
Download package
\n\n \n
\n \n
How critical is this fix?
\n \n
\n \n \n
\n
\n | Download | \nRELEASE DATE | \nLANGUAGE | \nSIZE(Bytes) | \nDownload Options What is Fix Central(FC)? What is DD? | \n
|---|---|---|---|---|
| ODM 8.8.1.1 AIX | \n23 Sep 2016 | \nLanguage Independent | \n400000000 | \nFC DD | \n
| ODM 8.8.1.1 HPUX | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Linux PPC | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Linux x86 | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Linux zSeries | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 OS/400 | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Solaris 32-bit SPARC | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Solaris 64-bit SPARC | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Solaris 32-bit x86 | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Solaris 64-bit x84 | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.1 Windows | \n23 Sep 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
\n
Problems (APARS) fixed
Problems (APARS) fixed
\n
",
+ "title": "IBM Operational Decision Manager V8.8.1.1 Fix Pack - United States",
+ "text": " DOWNLOADABLE FILES\n\nABSTRACT\n This cumulative fix pack updates Operational Decision Manager V8.8 or V8.8.1 to V8.8.1.1. \n\nDOWNLOAD DESCRIPTION\nThis fix pack is entitled. Only customers who have Operational Decision Manager V8.8 or V8.8.1 can use this fix pack. You do not have to install the latest version to apply this fix pack.\n\n\nHow to install the fix pack\nFor each of your Operational Decision Manager components: \n\n 1. Download its fix pack in the following table. \n Select the file that corresponds with your operating system (
\n
\n\n\n\n
\n\n \n \n
\nSecurity Bulletin
\n \n
\n
\n On-line Calculator v2\n
\n
\n
\n IBM Product Security Incident Response Blog\n
\n
\n
\n \n \n\n
Summary
\nThere are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server as a component of IBM Tivoli Network Performance Manager . These issues were disclosed as part of the IBM Java SDK updates in April 2015.
\nVulnerability Details
\n\n
\n CVE IDs: CVE-2015-0488 CVE-2015-0478 CVE-2015-0204 CVE-2015-2808 CVE-2015-1916 CVE-2015-0138
\nDESCRIPTION: This bulletin covers all applicable Java SE CVEs published by Oracle as part of their April 2015 Critical Patch Update and additional vulnerabilties which affect IBM SDK, Java Technology Edition. There are other advisories included in the IBM Java SDK but WebSphere Application Server is not vulnerable to them. You will need to evaluate your own code to determine if you are vulnerable. Please refer to the Reference section for more information on the advisories not applicable to WebSphere Application Server.
\nCVE-2015-0204 was fixed in IBM SDK, Java Technology Edition under CVE-2015-0138. Both CVEs are included in this advisory for completeness.
\nCVEID: CVE-2015-0488
DESCRIPTION: An unspecified vulnerability related to the JSSE component could allow a remote attacker to cause a denial of service.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102336 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)
CVEID: CVE-2015-0478
DESCRIPTION: An unspecified vulnerability related to the JCE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102339 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
CVEID: CVE-2015-0204
DESCRIPTION: A vulnerability in the OpenSSL ssl3_get_key_exchange function could allow a remote attacker to downgrade the security of certain TLS connections. An OpenSSL client accepts the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. This vulnerability is also known as the FREAK attack.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99707 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)
CVEID: CVE-2015-2808
DESCRIPTION: The RC4 algorithm, as used in the TLS protocol and SSL protocol, could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability to remotely expose account credentials without requiring an active man-in-the-middle session. Successful exploitation could allow an attacker to retrieve credit card data or other sensitive information. This vulnerability is commonly referred to as "Bar Mitzvah Attack".
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/101851 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)
CVEID: CVE-2015-1916
DESCRIPTION: Server applications which use the IBM Java Secure Socket Extension provider to accept SSL/TLS connections are vulnerable to a denial of service attack due to an unspecified vulnerability.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/101995 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)
CVEID: CVE-2015-0138
DESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. This vulnerability is also known as the FREAK attack.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100691 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)
Affected Products and Versions
\n\n
\n \n
\n \n \n
\n
\n | Affected Product and Version(s) | \nProduct and Version shipped as component | \n
| Tivoli Network Performance Manager 1.4 | \nBundled the Jazz for Service Management version 1.1.0.2, IBM WebSphere version 8.5.0.1 and the JRE from IBM SDK Java 2 Technology Edition Version 7. | \n
| Tivoli Network Performance Manager 1.3.3 | \nBundled the TIP version 2.1.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. | \n
| Tivoli Network Performance Manager 1.3.2 | \nBundled the TIP version 2.1.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. | \n
| Tivoli Network Performance Manager 1.3.1 | \nBundled the TIP version 2.1.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. | \n
Remediation/Fixes
\n\n
\n Download and apply interim fix based on your WebSphere version in Multiple vulnerabilities in IBM Java SDK affect WebSphere Application Server Apr 2015 CPU
\nGet Notified about Future Security Bulletins
\nSubscribe to My Notifications to be notified of important product support alerts like this.
\nReferences
\n Complete CVSS v2 Guide \n\n On-line Calculator v2\n
\n
\n
Related information
\n IBM Secure Engineering Web Portal \n\n IBM Product Security Incident Response Blog\n
\n
\n
Change History
\n19 May 2015: original document published
\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.
\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.
\n\n \n
\n ",
+ "title": "IBM Security Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affect WebSphere Application Server April 2015 CPU shipped with Tivoli Netcool Performance Manager - United States",
+ "text": " SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition that is shipped with IBM WebSphere Application Server as a component of IBM Tivoli Network Performance Manager . These issues were disclosed as part of the IBM Java SDK updates in April 2015. \n\nVULNERABILITY DETAILS\nCVE IDs:CVE-2015-0488 CVE-2015-0478 CVE-2015-0204 CVE-2015-2808 CVE-2015-1916 CVE-2015-0138 \n\nDESCRIPTION:This bulletin covers all applicable Java SE CVEs published by Oracle as part of their April 2015 Critical Patch Update and additional vulnerabilties which affect IBM SDK, Java Technology Edition. There are other advisories included in the IBM Java SDK but WebSphere Application Server is not vulnerable to them. You will need to evaluate your own code to determine if you are vulnerable. Please refer to the Reference section for more information on the advisories not applicable to WebSphere Application Server. \n\nCVE-2015-0204 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0204] was fixed in IBM SDK, Java Technology Edition under CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]. Both CVEs are included in this advisory for completeness. \n\nCVEID:CVE-2015-0488 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0488]\nDESCRIPTION:An unspecified vulnerability related to the JSSE component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/102336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/102336]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nCVEID:CVE-2015-0478 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0478]\nDESCRIPTION:An unspecified vulnerability related to the JCE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/102339 [https://exchange.xforce.ibmcloud.com/vulnerabilities/102339]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) \n\nCVEID:CVE-2015-0204 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0204]\nDESCRIPTION:A vulnerability in the OpenSSL ssl3_get_key_exchange function could allow a remote attacker to downgrade the security of certain TLS connections. An OpenSSL client accepts the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. This vulnerability is also known as the FREAK attack.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99707 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99707]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nCVEID:CVE-2015-2808 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2808]\nDESCRIPTION:The RC4 algorithm, as used in the TLS protocol and SSL protocol, could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability to remotely expose account credentials without requiring an active man-in-the-middle session. Successful exploitation could allow an attacker to retrieve credit card data or other sensitive information. This vulnerability is commonly referred to as \"Bar Mitzvah Attack\". \nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/101851 [https://exchange.xforce.ibmcloud.com/vulnerabilities/101851]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N) \n\nCVEID:CVE-2015-1916 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1916]\nDESCRIPTION:Server applications which use the IBM Java Secure Socket Extension provider to accept SSL/TLS connections are vulnerable to a denial of service attack due to an unspecified vulnerability.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/101995 [https://exchange.xforce.ibmcloud.com/vulnerabilities/101995]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nCVEID:CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION:A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. This vulnerability is also known as the FREAK attack.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/100691 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100691]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nAffected Product and Version(s) Product and Version shipped as component Tivoli Network Performance Manager 1.4 Bundled the Jazz for Service Management version 1.1.0.2, IBM WebSphere version 8.5.0.1 and the JRE from IBM SDK Java 2 Technology Edition Version 7. Tivoli Network Performance Manager 1.3.3 Bundled the TIP version 2.1.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. Tivoli Network Performance Manager 1.3.2 Bundled the TIP version 2.1.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. Tivoli Network Performance Manager 1.3.1 Bundled the TIP version 2.1.0.x, IBM WebSphere version 7.0.0.x and the JRE from IBM SDK Java 2 Technology Edition Version 6. REMEDIATION/FIXES\nDownload and apply interim fix based on your WebSphere version in Multiple vulnerabilities in IBM Java SDK affect WebSphere Application Server Apr 2015 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21902260]\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 v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \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 19 May 2015: original document 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.",
+ "metadata": {
+ "sourceDocumentId": "swg21903394",
+ "date": "2015-05-19",
+ "productName": "Tivoli Netcool Performance Manager",
+ "productId": "SSBNJ7",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21903394"
+ }
+ },
+ "swg1IC97587": {
+ "id": "swg1IC97587",
+ "content": "
\n
\n\n\n\n
\n
\n
\n \n
\n \nFixes are available
\n \n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
If the Queue manager ends, when the client application connects,\nan unhandled exception is thrown from MQCONNX.\n\nNmqiException thrown from GetQueueManagerInfo is not properly\nhandled by ManagedNmqiMQ.MQCONNX.\n\nThe .Net client trace shows:\n IBM.WMQ.Nmqi.NmqiException: Exception of type\n'IBM.WMQ.Nmqi.NmqiException' was thrown.\n at IBM.WMQ.Nmqi.NmqiTools.GetQueueManagerInfo\n(NmqiEnvironment env, NmqiMQ mq, Hconn hconn) in\n C:\\path\\to\\ NmqiTools.cs:line 1021\n at IBM.WMQ.Nmqi.ManagedHconn.UpdateHconn(NmqiMQ mqInstance,\nPhconn phconn) in\nC:\\path\\to\\ ManagedHconn.cs:line 354\n at IBM.WMQ.Nmqi.ManagedNmqiMQ.MQCONNX(String pQMgrName,\nMQConnectOptions pConnectOpts, Phconn phconn, Int32&\npCompCode, Int32& pReason) in C:\\path\\to\\ManagedNmqiMQ.cs:line\n769\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
****************************************************************\nUSERS AFFECTED:\nUsers of .NET applications connecting to the queue manager\nthrough managed/unmanaged/bindings mode\n\n\nPlatforms affected:\nWindows\n\n****************************************************************\nPROBLEM SUMMARY:\nWebSphere MQ .Net client code is not gracefully handling the\nNMQIException thrown to MQCONN(X) call. NMQIException can be\nthrown from NmqiTools.GetQueueManagerInfo if the queue manager\nends when the client connects.\n
\n \n
Problem conclusion
\n- \n
- \n \n
WebSphere MQ .Net client code has been modified such that the\nunhandled exception is handled gracefully in MQCONN(X) calls\nwhile connecting to the queue manager through\nmanaged/unmanaged/bindings mode. The NMQIException caught by\nMQCONN(X) will be re thrown has MQException to the application.\n\n---------------------------------------------------------------\nThe fix is targeted for delivery in the following PTFs:\n\nVersion Maintenance Level\nv7.0 7.0.1.12\nv7.1 7.1.0.5\nv7.5 7.5.0.4\n\nThe latest available maintenance can be obtained from\n'WebSphere MQ Recommended Fixes'\nhttp://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037\n\nIf the maintenance level is not yet available information on\nits planned availability can be found in 'WebSphere MQ\nPlanned Maintenance Release Dates'\nhttp://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309\n---------------------------------------------------------------\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
IC97587
\n Reported component name
WMQ WINDOWS V7
\n Reported component ID
5724H7220
\n Reported release
701
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2013-11-12
\n Closed date
2013-12-05
\n Last modified date
2013-12-05
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
WMQ WINDOWS V7
\n Fixed component ID
5724H7220
\n
Applicable component levels
\n- \n
R701 PSY
UP
\n
\n
\n
",
+ "title": "IBM IC97587: WEBSPHERE MQ .NET CLIENT APPLICATION REPORTS AN UNHANDLED NMQIEXCEPTION IN MANAGEDNMQIMQ.MQCONNX - United States",
+ "text": " FIXES ARE AVAILABLE\nWebSphere MQ V7.0 Fix Pack 7.0.1.12 [http://www-01.ibm.com/support/docview.wss?uid=swg24037169]\nFix Pack 7.1.0.5 for WebSphere MQ V7.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24037553]\nWebSphere MQ V7.5 Fix Pack 7.5.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24038252]\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 * If the Queue manager ends, when the client application connects,\n an unhandled exception is thrown from MQCONNX.\n \n NmqiException thrown from GetQueueManagerInfo is not properly\n handled by ManagedNmqiMQ.MQCONNX.\n \n The .Net client trace shows:\n IBM.WMQ.Nmqi.NmqiException: Exception of type\n 'IBM.WMQ.Nmqi.NmqiException' was thrown.\n at IBM.WMQ.Nmqi.NmqiTools.GetQueueManagerInfo\n (NmqiEnvironment env, NmqiMQ mq, Hconn hconn) in\n C:\\path\\to\\ NmqiTools.cs:line 1021\n at IBM.WMQ.Nmqi.ManagedHconn.UpdateHconn(NmqiMQ mqInstance,\n Phconn phconn) in\n C:\\path\\to\\ ManagedHconn.cs:line 354\n at IBM.WMQ.Nmqi.ManagedNmqiMQ.MQCONNX(String pQMgrName,\n MQConnectOptions pConnectOpts, Phconn phconn, Int32&\n pCompCode, Int32& pReason) in C:\\path\\to\\ManagedNmqiMQ.cs:line\n 769\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n USERS AFFECTED:\n Users of .NET applications connecting to the queue manager\n through managed/unmanaged/bindings mode\n \n \n Platforms affected:\n Windows\n \n ****************************************************************\n PROBLEM SUMMARY:\n WebSphere MQ .Net client code is not gracefully handling the\n NMQIException thrown to MQCONN(X) call. NMQIException can be\n thrown from NmqiTools.GetQueueManagerInfo if the queue manager\n ends when the client connects.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * WebSphere MQ .Net client code has been modified such that the\n unhandled exception is handled gracefully in MQCONN(X) calls\n while connecting to the queue manager through\n managed/unmanaged/bindings mode. The NMQIException caught by\n MQCONN(X) will be re thrown has MQException to the application.\n \n ---------------------------------------------------------------\n The fix is targeted for delivery in the following PTFs:\n \n Version Maintenance Level\n v7.0 7.0.1.12\n v7.1 7.1.0.5\n v7.5 7.5.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 IC97587\n \n \n * REPORTED COMPONENT NAME\n WMQ WINDOWS V7\n \n \n * REPORTED COMPONENT ID\n 5724H7220\n \n \n * REPORTED RELEASE\n 701\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-11-12\n \n \n * CLOSED DATE\n 2013-12-05\n \n \n * LAST MODIFIED DATE\n 2013-12-05\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 * R701 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1IC97587",
+ "date": "2013-12-05",
+ "productName": "WebSphere MQ",
+ "productId": "SSFKSJ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1IC97587"
+ }
+ },
+ "swg21483046": {
+ "id": "swg21483046",
+ "content": "
\n
",
+ "title": "IBM SPSS Text Analytics licensing error. How to determine I am using the correct authorization code? - United States",
+ "text": " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I licensed my SPSS product with a number of authorization codes, but I am still getting a license error when I start my product. How to determine the correct authorization code is being used if one of the following happened:\n\n1 - I applied an authorization code for a different product or an authorization code for a different version of my installed version of SPSS\n\n2 - Possibly an authorization code that is not set up properly because attempting to start my SPSS product I receive one of the following errors: \n\nSPSS Statistics:\nError # 7001\nThere is no license for SPSS for Windows.\nThis command not executed.\nSpecific symptom number: 18\n\nOr\n\nError # 2072 \nThere was an unanticipated problem with the license for this product. \nThis command not executed. \nSpecific symptom number: 4 \n\nAmos:\nNo valid license for Amos was found. (1, 18)\nOr\n\nNo valid license for Amos was found. (11,4)\n\nClementine / Modeler:\nNo license key found: Subcode 18 \n\nRESOLVING THE PROBLEM\nEach of our SPSS products come with a unique 20 character alpha-numeric code called an authorization code. These codes are specific not only to the product that needs to be installed, but the version of the product as well. Documentation that is provided by the SPSS sales department or your distributor defines what specific product and version your authorization code can be used for.\n\nIf you have any questions about your authorization code, please feel free to contact Client Care at tsmail@us.ibm.com\n\nRELATED INFORMATION\n Need more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\n\n\n \n\nHISTORICAL NUMBER\n 81980",
+ "metadata": {
+ "sourceDocumentId": "swg21483046",
+ "date": "2011-04-03",
+ "productName": "SPSS Text Analytics for Surveys",
+ "productId": "SS6A7K",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21483046"
+ }
+ },
+ "swg21632844": {
+ "id": "swg21632844",
+ "content": "\n\n
\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n\n
Problem(Abstract)
\n I licensed my SPSS product with a number of authorization codes, but I am still getting a license error when I start my product. How to determine the correct authorization code is being used if one of the following happened:
1 - I applied an authorization code for a different product or an authorization code for a different version of my installed version of SPSS
2 - Possibly an authorization code that is not set up properly because attempting to start my SPSS product I receive one of the following errors:
SPSS Statistics:
Error # 7001
There is no license for SPSS for Windows.
This command not executed.
Specific symptom number: 18
Or
Error # 2072
There was an unanticipated problem with the license for this product.
This command not executed.
Specific symptom number: 4
Amos:
No valid license for Amos was found. (1, 18)
Or
No valid license for Amos was found. (11,4)
Clementine / Modeler:
No license key found: Subcode 18
Resolving the problem
\n\n
\n Each of our SPSS products come with a unique 20 character alpha-numeric code called an authorization code. These codes are specific not only to the product that needs to be installed, but the version of the product as well. Documentation that is provided by the SPSS sales department or your distributor defines what specific product and version your authorization code can be used for.
If you have any questions about your authorization code, please feel free to contact Client Care at tsmail@us.ibm.com
Related information
\n Need more help? Our Licensing forum is Live!
\n
\n \n
\n
\n \n \n Historical Number
\n81980
\n\n
",
+ "title": "IBM Enabling tracing for the DASH service in Jazz for Service Management - United States",
+ "text": "DASHL2; DASHL2FAQ; DASHL2MUSTG; enable tracing TECHNOTE (FAQ)\n\nQUESTION\n What is the procedure to enable trace logging to troubleshoot DASH runtime issues/errors? \n\nCAUSE\nYou can use trace logging to assist in monitoring system performance and diagnosing problems. Since trace logs can be quite verbose and include many unrelated errors, resetting the logs and then reproducing the problem issue can reduce the time required for log analysis for specific issues.\n\nANSWER\nSteps to enable tracing: \n\n\nEnable trace logging. \n\n 1. Log into the DASH. After logging in navigate to Console Settings [/support/docview.wss?uid=swg21632844&aid=1] > Websphere Administrative Console. \n 2. Navigate to Troubleshooting -> Logs & Trace \n 3. Click on the Server1 -> Select Diagnostic Trace Service. Increase the Maximum Number of Historical Files from 1 to 10. \n 4. Click Apply, then select Change Log Detail Levels. \n 5. Click on Runtime tab to enable tracing for the DASH process that is currently running. Enabling tracing from the Runtime tab will keep tracing active until the next time the DASH server process is stopped. To make tracing persistent even after stopping and restarting the DASH server process click the Configuration tab instead. \n 6. Clear the trace string in the Groups box and replace it with the following:\n \n *=info: com.ibm.isc.*=all: com.ibm.isclite.*=all: com.ibm.iscportal.*=all: com.ibm.isclite.service.datastore.consoleproperties.*=INFO\n \n For the Connection manager (data provider related issues) you will want to enable all for the following components:\n \n *=info: com.ibm.isclite.rest.*=all:com.ibm.tivoli.conmgr.*=all \n 7. Click on the Apply button. \n 8. If you enabled tracing from the Configuration tab in step 4, then click the \"Save\" link that appears at the top of the page. (\"Save to master configuration\")\n\n\nOnce tracing is enabled, reproduce the DASH runtime issue. Note the time that the issue was reproduced so that the issue can be easily correlated with the trace log entries. \n\nRun the log collector program:\n\n\n 1. Change the directory to \n\n
\nDASHL2; DASHL2FAQ; DASHL2MUSTG; enable tracing
\n\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n
Question
\nWhat is the procedure to enable trace logging to troubleshoot DASH runtime issues/errors?
\nCause
\n\n
\n You can use trace logging to assist in monitoring system performance and diagnosing problems. Since trace logs can be quite verbose and include many unrelated errors, resetting the logs and then reproducing the problem issue can reduce the time required for log analysis for specific issues.
\nAnswer
\n\n
\n
and attach them to the associated Problem Management Record (PMR). Please include the time the issue was reproduced in the PMR update. \n
\n Steps to enable tracing:
Enable trace logging.
\n- \n
- Log into the DASH. After logging in navigate to Console Settings
> Websphere Administrative Console.
\n - Navigate to Troubleshooting -> Logs & Trace \n
- Click on the Server1 -> Select Diagnostic Trace Service. Increase the Maximum Number of Historical Files from 1 to 10. \n
- Click Apply, then select Change Log Detail Levels. \n
- Click on Runtime tab to enable tracing for the DASH process that is currently running. Enabling tracing from the Runtime tab will keep tracing active until the next time the DASH server process is stopped. To make tracing persistent even after stopping and restarting the DASH server process click the Configuration tab instead. \n
- Clear the trace string in the Groups box and replace it with the following:
*=info: com.ibm.isc.*=all: com.ibm.isclite.*=all: com.ibm.iscportal.*=all: com.ibm.isclite.service.datastore.consoleproperties.*=INFO
For the Connection manager (data provider related issues) you will want to enable all for the following components:
*=info: com.ibm.isclite.rest.*=all:com.ibm.tivoli.conmgr.*=all \n - Click on the Apply button. \n
- If you enabled tracing from the Configuration tab in step 4, then click the "Save" link that appears at the top of the page. ("Save to master configuration") \n
\n
Once tracing is enabled, reproduce the DASH runtime issue. Note the time that the issue was reproduced so that the issue can be easily correlated with the trace log entries.
\nRun the log collector program:
- \n
- Change the directory to <JazzSM Home>/ui/bin \n
- Run the following command:
./consoleLogCollector.sh or .bat
Send us the console_logs.zip file located in <JazzSM Home>/ui directory \n
and attach them to the associated Problem Management Record (PMR). Please include the time the issue was reproduced in the PMR update. \n
Please also provide the DASH version info:
<JazzSM Home>/ui/bin/consolecli.sh Version
Upload the resulting output file to the PMR
\n
\n \n
\n
\n \n \n\n
\n\n\n\n
\n
\n
\n \n
\n \nFixes are available
\n \n
\nFix packs for DataPower XML Security Gateway version 6.0
Fix packs for DataPower B2B Appliance version 6.0
Fix packs for DataPower Integration Appliance version 6.0
Fix packs for DataPower Low Latency Appliance version 6.0
Fix packs for DataPower Service Gateway version 6.0
Fix packs for DataPower Service Gateway version 6.0.1
Fix packs for DataPower B2B Appliance version 6.0.1
Fix packs for DataPower Integration Appliance version 6.0.1
Fix packs for DataPower Service Gateway version 7.0
Fix packs for DataPower B2B Appliance version 7.0
Fix packs for DataPower Integration Appliance version 7.0
\n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
Problem description:\nWhen attempting to create a checkpoint, the operation might take\ntoo long and time out. The WebGUI shows "Permission denied"\nerror. In the error log:\n\n20140610T174011Z [mgmt][error] : tid(1550207): Save Checkpoint -\n Error creating\n'Checkpoint-test-1'.\n20140610T174011Z [cli][error] : tid(32307809): Failed saving\ncheckpoint -\nPlease show logs for details..\n20140610T174011Z [cli][error] : tid(32307809): === Line 2: save\nchkpoint\n"Checkpint-test-1"\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
User might experience an error when creating a checkpoint in a\ndomain when the export takes longer than the allowed time.\n
\n \n
Problem conclusion
\n- \n
- \n \n
Fix is available in 5.0.0.17, 6.0.0.9, 6.0.1.5 and 7.0.0.2.\n\nFor a list of the latest fix packs available, please see:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21237631\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
IT02925
\n Reported component name
DATAPOWER
\n Reported component ID
DP1234567
\n Reported release
500
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2014-07-04
\n Closed date
2014-09-19
\n Last modified date
2014-09-26
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
DATAPOWER
\n Fixed component ID
DP1234567
\n
Applicable component levels
\n- \n
R500 PSY
UP
\n R600 PSY
UP
\n R601 PSY
UP
\n R700 PSY
UP
\n
\n
\n
",
+ "title": "IBM IT02925: CREATE CHECKPOINT OPERATION FAILS WITH OPERATION TIMEOUT DUE TO TOO MANY FILES IN CONFIGURATION - United States",
+ "text": " FIXES ARE AVAILABLE\nFix packs for DataPower XML Security Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034955]\nFix packs for DataPower B2B Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034956]\nFix packs for DataPower Integration Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034957]\nFix packs for DataPower Low Latency Appliance version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034958]\nFix packs for DataPower Service Gateway version 6.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24034959]\nFix packs for DataPower Service Gateway version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036407]\nFix packs for DataPower B2B Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036409]\nFix packs for DataPower Integration Appliance version 6.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg24036410]\nFix packs for DataPower Service Gateway version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037486]\nFix packs for DataPower B2B Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037487]\nFix packs for DataPower Integration Appliance version 7.0 [http://www-01.ibm.com/support/docview.wss?uid=swg24037488]\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 * Problem description:\n When attempting to create a checkpoint, the operation might take\n too long and time out. The WebGUI shows \"Permission denied\"\n error. In the error log:\n \n 20140610T174011Z [mgmt][error] : tid(1550207): Save Checkpoint -\n Error creating\n 'Checkpoint-test-1'.\n 20140610T174011Z [cli][error] : tid(32307809): Failed saving\n checkpoint -\n Please show logs for details..\n 20140610T174011Z [cli][error] : tid(32307809): === Line 2: save\n chkpoint\n \"Checkpint-test-1\"\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * User might experience an error when creating a checkpoint in a\n domain when the export takes longer than the allowed time.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fix is available in 5.0.0.17, 6.0.0.9, 6.0.1.5 and 7.0.0.2.\n \n For a list of the latest fix packs available, please see:\n http://www-01.ibm.com/support/docview.wss?uid=swg21237631 [http://www-01.ibm.com/support/docview.wss?uid=swg21237631]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IT02925\n \n \n * REPORTED COMPONENT NAME\n DATAPOWER\n \n \n * REPORTED COMPONENT ID\n DP1234567\n \n \n * REPORTED RELEASE\n 500\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-07-04\n \n \n * CLOSED DATE\n 2014-09-19\n \n \n * LAST MODIFIED DATE\n 2014-09-26\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 DATAPOWER\n \n \n * FIXED COMPONENT ID\n DP1234567\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R500 PSY\n UP\n \n \n * R600 PSY\n UP\n \n \n * R601 PSY\n UP\n \n \n * R700 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1IT02925",
+ "date": "2014-09-26",
+ "productName": "IBM DataPower Gateways",
+ "productId": "SS9H2Y",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1IT02925"
+ }
+ },
+ "swg24042247": {
+ "id": "swg24042247",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nDownloadable files
\n \n
\n
\n
\n
\n \n \n\n
Abstract
\nThis mod pack updates Operational Decision Manager V8.8.0 to V8.8.1.
\nDownload Description
\n\n
\n Installing with the Installation Manager command line: \n
\n Applying the mod pack\n
After you install the mod pack, you might have to do additional steps to apply the mod pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack.\n
\n This mod pack is entitled. Only customers who have purchased Operational Decision Manager V8.8.0 can use this mod pack.
How to install the mod pack
For each Operational Decision Manager component that you use:
- \n
- Download its file in the following table. Select the file for your operating system by changing <OS> to match your platform: AIX, HPUX, LIN_PPC, LIN_S390, LIN_X86, MAC, OS400, SOL_SPARC, SOL_X86, or WIN. \n
- Extract the contents of the downloaded file to a new folder. Use the corresponding folder name in the table. \n
- If you use WebSphere Application Server, download the profile templates for your component. \n
\n \n \n
\n
\n Installing with IBM Installation Manager: \n | Component | \nDownload file | \nFolder name (InstallDir) | \nNote | \n
| Decision Server Insights | \n8.8.0-WS-ODM_DSI-<OS>-RP001.zip | \nDSI | \nOnly available for Linux (LIN) and Windows (WIN). | \n
| Decision Center | \n8.8.0-WS-ODM_DC-<OS>-RP001.zip | \nWDC | \nFor Windows and Linux, use <install path of ODM 8.8.0>/jdk/bin/jar xf to extract files in the WDC directory. | \n
| Decision Server Rules | \n8.8.0-WS-ODM_DSR-<OS>-RP001.zip | \nDSR | \n|
| Decision Server Events | \n8.8.0-WS-ODM_DSE-<OS>-RP001.zip | \nDSE | \n|
| Decision Center profile templates for WebSphere Application Server | \n8.8.0-WS-ODM_PTDC-RP001.zip | \nWDC_PT | \n|
| Decision Server Rules profile templates for WebSphere Application Server | \n8.8.0-WS-ODM_PTR-RP001.zip | \nDSR_PT | \n|
| Decision Server Events profile templates for WebSphere Application Server | \n8.8.0-WS-ODM_PTE-RP001.zip | \nDSE_PT | \n
- \n
- Launch IBM Installation Manager. \n
- Open File > Preferences > Repositories. \n
- For each component that you use:
a. Click Add Repository.
b. Browse to the extracted folder <InstallDir>/updates.
c. Select the repository.config file. \n - Make sure the repositories are selected in Repositories. \n
- Click Apply to save your changes, and click OK to close Repositories. \n
- Click Update to update your installation. \n
- Follow the instructions in the installation manager to complete the installation. \n
\n Installing with the Installation Manager command line: \n
- \n
- Locate the imcl command under <IM installation>/eclipse/tools. \n
- Run the command imcl updateAll -repositories WDC/updates, DSR/updates, DSE/updates -acceptLicense. \n
- \n
- Use the option -installDirectory <install path of ODM 8.8.0> to update a specific installation. \n
- If you update only one component, specify the repository accordingly. \n
\n Applying the mod pack\n
After you install the mod pack, you might have to do additional steps to apply the mod pack in your environment. To complete the update, see \n When and how to apply a modification or fix pack.\n
Download package
\n\n \n
\n \n
Problems solved
\n \n
\n \n \n
\n
\n | Download | \nRELEASE DATE | \nLANGUAGE | \nSIZE(Bytes) | \nDownload Options What is Fix Central(FC)? What is DD? | \n
|---|---|---|---|---|
| ODM 8.8.1.0 AIX | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 HPUX | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Linux PPC | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Linux x86 | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Linux zSeries | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 OS/400 | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Solaris 32-bit SPARC | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Solaris 64-bit SPARC | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Solaris 32-bit x86 | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Solaris 64-bit x86 | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
| ODM 8.8.1.0 Windows | \n3 Jun 2016 | \nLanguage Independent | \n4000000000 | \nFC DD | \n
\n
Problems (APARS) fixed
Problems (APARS) fixed
\n
",
+ "title": "IBM Operational Decision Manager V8.8.1 Mod Pack - United States",
+ "text": " DOWNLOADABLE FILES\n\nABSTRACT\n This mod pack updates Operational Decision Manager V8.8.0 to V8.8.1. \n\nDOWNLOAD DESCRIPTION\nThis mod pack is entitled. Only customers who have purchased Operational Decision Manager V8.8.0 can use this mod pack.\n\n\nHow to install the mod pack\nFor each Operational Decision Manager component that you use: \n\n 1. Download its file in the following table. Select the file for your operating system by changing
\n
\n\n\n\n
\ninstall; webgui; prerequisite ; dashboard; 日本語
\n\n\n \n \n
\nTechnote(トラブルシューティング)
\n \n
\n
\n \n
問題(概要)
\n Web GUI のインストールを試行中、パッケージグループのインストール段階で以下のエラーメッセージを表示し、失敗します。
"IBM Dashboard Application Service Hubのバージョンが見つかりません。3.1.0.3以降のバージョンが必要です。"
解決方法
\n\n
\n
\n Web GUI のインストール文書は前提ソフトウェアが導入済みであることを前提に作られています。
\nWebGUI 8.1.0 に必要な前提ソフトウェアは WAS 8.5.01 及び Jazz for Service management 1.1.0.3 です。
\nLinux 及び AIX について必要なパーツ番号、インストールの順序の詳細は以下のようになります。
\n \nAIX
\n- \n
- IBM Tivoli Netcool OMNIbus 8.1 Core – AIX 64bit Multilingual (CN05GML ) \n
- 注: これをインストールしてなかったからといって Web GUI のインストールが完了しないわけではなく、Object Server がインストールされず、データソースの設定が出来ません。 \n
- IBM WebSphere Application Server V8.5.0.1 for Jazz for Service Management for AIX Multilingual (CIES5ML ) \n
- この手順の途中で Installation Manager はWAS 8.0.5 及び WAS 8.5.01 を表示しますが、WAS 8.5.0.1 を選択します。 \n
- Jazz for Service Management V1.1.0.3 for AIX Multilingual (CIXA1ML ) \n
- この手順の途中で Installation Manager はJazz Repository 内の２つの以下の必要なソフトウェアパッケージをリストします。これらの両方のパッケージはインストール対象として同時に選ぶ必要があります。 これらを順番にインストールしてはいけません。 \n
- Jazz for Service Management extension for IBM WebSphere 8.5 \n
- IBM Dashboard Application Services Hub 3.1.0.3 \n
- IBM Tivoli Netcool OMNIbus 8.1 WebGUI – AIX 64bit Multilingual (CN1FEML ) \n
- \n
- \n
- \n
- \n
\n
LINUX
\n- \n
- IBM Tivoli Netcool OMNIbus 8.1 Core – Linux 64bit Multilingual (CN05EML ) \n
- 注: これをインストールしてなかったからといって Web GUI のインストールが完了しないわけではなく、Object Server がインストールされず、データソースの設定が出来ません。 \n
- IBM WebSphere Application Server V8.5.0.1 for Jazz for Service Management for Linux Multilingual (CIES6ML ) \n
- class="ibm-alpha-list"> \n
- この手順の途中で Installation Manager はWAS 8.0.5 及び WAS 8.5.01 を表示しますが、WAS 8.5.0.1 を選択します。 \n
- Jazz for Service Management V1.1.0.3 for Linux Multilingual (CIXA2ML ) \n
- この手順の途中で Installation Manager はJazz Repository 内の２つの以下の必要なソフトウェアパッケージをリストします。これらの両方のパッケージはインストール対象として同時に選ぶ必要があります。 これらを順番にインストールしてはいけません。 \n
- Jazz for Service Management extension for IBM WebSphere 8.5 \n
- IBM Dashboard Application Services Hub 3.1.0.3 \n
- IBM Tivoli Netcool OMNIbus 8.1 WebGUI – Linux 64bit Multilingual (CN1FCML ) \n
- \n
- \n
- \n
- \n
\n
\n \n
\n
\n \n \n",
+ "title": "IBM Netcool Omnibus 8.1 Web GUI \u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u306b\u5931\u6557\u3057\u307e\u3059 - United States",
+ "text": "install; webgui; prerequisite ; dashboard; \u65e5\u672c\u8a9e TECHNOTE(\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0)\n\n\u554f\u984c(\u6982\u8981)\n Web GUI \u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3092\u8a66\u884c\u4e2d\u3001\u30d1\u30c3\u30b1\u30fc\u30b8\u30b0\u30eb\u30fc\u30d7\u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u6bb5\u968e\u3067\u4ee5\u4e0b\u306e\u30a8\u30e9\u30fc\u30e1\u30c3\u30bb\u30fc\u30b8\u3092\u8868\u793a\u3057\u3001\u5931\u6557\u3057\u307e\u3059\u3002\n\"IBM Dashboard Application Service Hub\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u304c\u898b\u3064\u304b\u308a\u307e\u305b\u3093\u30023.1.0.3\u4ee5\u964d\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u304c\u5fc5\u8981\u3067\u3059\u3002\" \n\n\u89e3\u6c7a\u65b9\u6cd5\nWeb GUI \u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u6587\u66f8\u306f\u524d\u63d0\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u304c\u5c0e\u5165\u6e08\u307f\u3067\u3042\u308b\u3053\u3068\u3092\u524d\u63d0\u306b\u4f5c\u3089\u308c\u3066\u3044\u307e\u3059\u3002 \n\nWebGUI 8.1.0 \u306b\u5fc5\u8981\u306a\u524d\u63d0\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u306f WAS 8.5.01 \u53ca\u3073 Jazz for Service management 1.1.0.3 \u3067\u3059\u3002 \n\nLinux \u53ca\u3073 AIX \u306b\u3064\u3044\u3066\u5fc5\u8981\u306a\u30d1\u30fc\u30c4\u756a\u53f7\u3001\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u306e\u9806\u5e8f\u306e\u8a73\u7d30\u306f\u4ee5\u4e0b\u306e\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002 \n\n\n\nAIX\n 1. IBM Tivoli Netcool OMNIbus 8.1 Core \u2013 AIX 64bit Multilingual (CN05GML )\n 2. \u6ce8: \u3053\u308c\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3057\u3066\u306a\u304b\u3063\u305f\u304b\u3089\u3068\u3044\u3063\u3066 Web GUI \u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u304c\u5b8c\u4e86\u3057\u306a\u3044\u308f\u3051\u3067\u306f\u306a\u304f\u3001Object Server \u304c\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u305a\u3001\u30c7\u30fc\u30bf\u30bd\u30fc\u30b9\u306e\u8a2d\u5b9a\u304c\u51fa\u6765\u307e\u305b\u3093\u3002 \n 3. IBM WebSphere Application Server V8.5.0.1 for Jazz for Service Management for AIX Multilingual (CIES5ML )\n 4. \u3053\u306e\u624b\u9806\u306e\u9014\u4e2d\u3067 Installation Manager \u306fWAS 8.0.5 \u53ca\u3073 WAS 8.5.01 \u3092\u8868\u793a\u3057\u307e\u3059\u304c\u3001WAS 8.5.0.1 \u3092\u9078\u629e\u3057\u307e\u3059\u3002 \n 5. Jazz for Service Management V1.1.0.3 for AIX Multilingual (CIXA1ML ) \n 6. \u3053\u306e\u624b\u9806\u306e\u9014\u4e2d\u3067 Installation Manager \u306fJazz Repository \u5185\u306e\uff12\u3064\u306e\u4ee5\u4e0b\u306e\u5fc5\u8981\u306a\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u30d1\u30c3\u30b1\u30fc\u30b8\u3092\u30ea\u30b9\u30c8\u3057\u307e\u3059\u3002\u3053\u308c\u3089\u306e\u4e21\u65b9\u306e\u30d1\u30c3\u30b1\u30fc\u30b8\u306f\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u5bfe\u8c61\u3068\u3057\u3066\u540c\u6642\u306b\u9078\u3076\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 \u3053\u308c\u3089\u3092\u9806\u756a\u306b\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3057\u3066\u306f\u3044\u3051\u307e\u305b\u3093\u3002 1. Jazz for Service Management extension for IBM WebSphere 8.5\n 2. IBM Dashboard Application Services Hub 3.1.0.3\n \n \n 7. IBM Tivoli Netcool OMNIbus 8.1 WebGUI \u2013 AIX 64bit Multilingual (CN1FEML ) \n\n\nLINUX\n 1. IBM Tivoli Netcool OMNIbus 8.1 Core \u2013 Linux 64bit Multilingual (CN05EML ) \n 2. \u6ce8: \u3053\u308c\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3057\u3066\u306a\u304b\u3063\u305f\u304b\u3089\u3068\u3044\u3063\u3066 Web GUI \u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u304c\u5b8c\u4e86\u3057\u306a\u3044\u308f\u3051\u3067\u306f\u306a\u304f\u3001Object Server \u304c\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u305a\u3001\u30c7\u30fc\u30bf\u30bd\u30fc\u30b9\u306e\u8a2d\u5b9a\u304c\u51fa\u6765\u307e\u305b\u3093\u3002 \n 3. IBM WebSphere Application Server V8.5.0.1 for Jazz for Service Management for Linux Multilingual (CIES6ML ) \n 4. class=\"ibm-alpha-list\"> \u3053\u306e\u624b\u9806\u306e\u9014\u4e2d\u3067 Installation Manager \u306fWAS 8.0.5 \u53ca\u3073 WAS 8.5.01 \u3092\u8868\u793a\u3057\u307e\u3059\u304c\u3001WAS 8.5.0.1 \u3092\u9078\u629e\u3057\u307e\u3059\u3002 \n 5. Jazz for Service Management V1.1.0.3 for Linux Multilingual (CIXA2ML )\n 6. \u3053\u306e\u624b\u9806\u306e\u9014\u4e2d\u3067 Installation Manager \u306fJazz Repository \u5185\u306e\uff12\u3064\u306e\u4ee5\u4e0b\u306e\u5fc5\u8981\u306a\u30bd\u30d5\u30c8\u30a6\u30a7\u30a2\u30d1\u30c3\u30b1\u30fc\u30b8\u3092\u30ea\u30b9\u30c8\u3057\u307e\u3059\u3002\u3053\u308c\u3089\u306e\u4e21\u65b9\u306e\u30d1\u30c3\u30b1\u30fc\u30b8\u306f\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u5bfe\u8c61\u3068\u3057\u3066\u540c\u6642\u306b\u9078\u3076\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 \u3053\u308c\u3089\u3092\u9806\u756a\u306b\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3057\u3066\u306f\u3044\u3051\u307e\u305b\u3093\u3002 1. Jazz for Service Management extension for IBM WebSphere 8.5\n 2. IBM Dashboard Application Services Hub 3.1.0.3\n \n \n 7. IBM Tivoli Netcool OMNIbus 8.1 WebGUI \u2013 Linux 64bit Multilingual (CN1FCML )",
+ "metadata": {
+ "sourceDocumentId": "swg21962250",
+ "date": "2016-05-09",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21962250"
+ }
+ },
+ "swg21475390": {
+ "id": "swg21475390",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n\n
Problem(Abstract)
\n IBM Statistics 19 will not install via MSI command line. I try to install version 19 on a Windows 32 bit machine via MSI. Therefore I copied the complete win32 folder from the DVD to C:\\temp folder because in this folder you can find the necessary MSI and other files needed to push the installation.
I open a command prompt and change the directory to C:\\temp\\win32 and run the following command according to the instructions in the SPSS License Administrator's Guide on page 4 in the Command Line Example:
MSIExec.exe /i "IBM SPSS Statistics 19.msi" /qn /L*v 19log.txt
After running the command the program was installed in the default directory C:\\Program Files\\IBM\\SPSS\\Statistics\\19. In the C:\\temp\\win32 the 19log.txt was also created and the text in the log confirms that the program was installed successfully.
However, the following error is returned when attempting to run the program:
"C:\\Program Files\\IBM\\SPSS\\Statistics\\19\\stats.exe
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem."
How to install IBM SPSS Statistics 19 on Windows via MSI?
This problem also appears when installing on a Windows 2003 server for a network license and try to start Statistics 19 on the server, I get the message:
"The application failed to initialize properly."
Resolving the problem
\n\n
\n This problem has been reported to SPSS Development - Workaround
\nAvailable
.
One possible cause of this problem is that the Microsoft Visual C++
redistributables the application requires did not execute and install
properly during installation of the Statistics application. You can run
them manually post-installation from here:
.
C:\\Program Files\\IBM\\SPSS\\Statistics\\19\\VC8\\Vcredist_x86.exe
C:\\Program Files\\IBM\\SPSS\\Statistics\\19\\VC9\\Vcredist_x86.exe
(the file names may be slightly different for 64-bit installations)
.
For Vista, Windows 7, or Server 2008 installations, be sure to
right-click and select Run As Administrator to properly execute the
installation of the redistributables.
Temporarily disable anti-virus, firewall and spyware software.
.
Once those installations complete, you should be able to launch the
application successfully.
.
If you would like to run the installation of the redistributables silent
you can create a batch file from the instructions below.
.
These are the commands used to create the batch files:
.
For 32bit Windows:
.
cd \\program files\\ibm\\spss\\statistics\\19\\vc8
msiexec -i "vcredist.msi" /qn
cd \\program files\\ibm\\spss\\statistics\\19\\vc9
vcredist_x86.exe /q:a /c:"VCREDI~1.EXE /q:a /c:""msiexec /i vc_red.msi
/qn"" "
.
For 64bit Windows:
.
cd \\program files\\ibm\\spss\\statistics\\19\\vc8
msiexec -i "vcredist.msi" /qn
cd \\program files\\ibm\\spss\\statistics\\19\\vc9
vcredist_x64.exe /q:a /c:"VCREDI~2.EXE /q:a /c:""msiexec /i vc_red.msi
/qn"" "
.
For more information please refer to:
http://blogs.msdn.com/b/astebner/archive/2007/02/07/update-regarding-silent-install-of-the-vc-8-0-runtime-vcredist-packages.aspx
VC9 (Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022) shipped
with SPSS 19 extracted files appear in root directory. Alternatively you
can use VC9 SP1 (Microsoft Visual C++ 2008 Redistributable - x86
9.0.30729.17) which is available at Microsoft.com
Related information
\n Need more help? Our Statistics forum is Live!
\n
\n \n
\n
\n \n \n Historical Number
\n91305
\n",
+ "title": "IBM Statistics 19 will not install via MSI command line, receive error: This application has failed to start because the application configuration is incorrect - United States",
+ "text": " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Statistics 19 will not install via MSI command line. I try to install version 19 on a Windows 32 bit machine via MSI. Therefore I copied the complete win32 folder from the DVD to C:\\temp folder because in this folder you can find the necessary MSI and other files needed to push the installation.\nI open a command prompt and change the directory to C:\\temp\\win32 and run the following command according to the instructions in the SPSS License Administrator's Guide on page 4 in the Command Line Example:\n\nMSIExec.exe /i \"IBM SPSS Statistics 19.msi\" /qn /L*v 19log.txt\n\nAfter running the command the program was installed in the default directory C:\\Program Files\\IBM\\SPSS\\Statistics\\19. In the C:\\temp\\win32 the 19log.txt was also created and the text in the log confirms that the program was installed successfully.\n\nHowever, the following error is returned when attempting to run the program:\n\n\"C:\\Program Files\\IBM\\SPSS\\Statistics\\19\\stats.exe\n\nThis application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.\"\n\nHow to install IBM SPSS Statistics 19 on Windows via MSI?\n\nThis problem also appears when installing on a Windows 2003 server for a network license and try to start Statistics 19 on the server, I get the message:\n\"The application failed to initialize properly.\" \n\nRESOLVING THE PROBLEM\nThis problem has been reported to SPSS Development - Workaround \n\nAvailable\n.\nOne possible cause of this problem is that the Microsoft Visual C++\nredistributables the application requires did not execute and install\nproperly during installation of the Statistics application. You can run\nthem manually post-installation from here:\n.\nC:\\Program Files\\IBM\\SPSS\\Statistics\\19\\VC8\\Vcredist_x86.exe\nC:\\Program Files\\IBM\\SPSS\\Statistics\\19\\VC9\\Vcredist_x86.exe\n(the file names may be slightly different for 64-bit installations)\n.\nFor Vista, Windows 7, or Server 2008 installations, be sure to\nright-click and select Run As Administrator to properly execute the\ninstallation of the redistributables.\nTemporarily disable anti-virus, firewall and spyware software.\n.\nOnce those installations complete, you should be able to launch the\napplication successfully.\n.\nIf you would like to run the installation of the redistributables silent\nyou can create a batch file from the instructions below.\n.\nThese are the commands used to create the batch files:\n.\nFor 32bit Windows:\n.\ncd \\program files\\ibm\\spss\\statistics\\19\\vc8\nmsiexec -i \"vcredist.msi\" /qn\ncd \\program files\\ibm\\spss\\statistics\\19\\vc9\nvcredist_x86.exe /q:a /c:\"VCREDI~1.EXE /q:a /c:\"\"msiexec /i vc_red.msi\n/qn\"\" \"\n.\nFor 64bit Windows:\n.\ncd \\program files\\ibm\\spss\\statistics\\19\\vc8\nmsiexec -i \"vcredist.msi\" /qn\ncd \\program files\\ibm\\spss\\statistics\\19\\vc9\nvcredist_x64.exe /q:a /c:\"VCREDI~2.EXE /q:a /c:\"\"msiexec /i vc_red.msi\n/qn\"\" \"\n.\nFor more information please refer to:\nhttp://blogs.msdn.com/b/astebner/archive/2007/02/07/update-regarding-silent-install-of-the-vc-8-0-runtime-vcredist-packages.aspx [http://blogs.msdn.com/b/astebner/archive/2007/02/07/update-regarding-silent-install-of-the-vc-8-0-runtime-vcredist-packages.aspx]\nVC9 (Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022) shipped\nwith SPSS 19 extracted files appear in root directory. Alternatively you\ncan use VC9 SP1 (Microsoft Visual C++ 2008 Redistributable - x86\n9.0.30729.17) which is available at Microsoft.com\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 91305",
+ "metadata": {
+ "sourceDocumentId": "swg21475390",
+ "date": "2016-12-02",
+ "productName": "SPSS Statistics",
+ "productId": "SSLVMB",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21475390"
+ }
+ },
+ "swg21679027": {
+ "id": "swg21679027",
+ "content": "
\n
",
+ "title": "IBM The Portal startup fails with these messages...\"UnsupportedClassVersionError\" and \"bad major version at offset=6\" - United States",
+ "text": "UnsupportedClassVersionError; bad major version; offset=6; startup TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n During the Portal startup the startup fails with these messages in the SystemOut.log...\"UnsupportedClassVersionError\" and \"bad major version at offset=6\" \n\nSYMPTOM\nThe SystemOut.log shows the following...\n\n[7/11/14 13:20:23:684 EDT] 0000001a Servlet E com.ibm.wps.engine.\nServlet init EJPFD0016E: Initialization of service failed.\njava.lang.\nUnsupportedClassVersionError:\n(com/ibm/wps/services/puma/PumaServiceImpl) bad major version at\noffset=6\nat java.lang.ClassLoader.defineClassImpl(Native Method)\nat java.lang.ClassLoader.defineClass(ClassLoader.java:267)\n\n\nCAUSE\nThis message can occur when component was compiled under a newer version of a JDK\nthan what the Portal JVM is running.\n\nIn this case, this specific issue was that the customer had placed a PUMA test fix they had received from IBM while working another problem in the PortalServer/shared/app directory. This fix was made for a higher version of Portal and therefore was complied on a high JDK version than what the customer was running.\n\nENVIRONMENT\nPortal 6.1x\nAIX\n\nDIAGNOSING THE PROBLEM\nReview the last Portal startup attempt in the SystemOut.log\n\nRESOLVING THE PROBLEM\nIn this case, the customer simply removed the test fix code from the PortalServer/shared/app directory and restarted Portal",
+ "metadata": {
+ "sourceDocumentId": "swg21679027",
+ "date": "2015-11-24",
+ "productName": "WebSphere Portal End of Support Products",
+ "productId": "SS8KYD",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21679027"
+ }
+ },
+ "swg1PK59516": {
+ "id": "swg1PK59516",
+ "content": "\n\n
\nUnsupportedClassVersionError; bad major version; offset=6; startup
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\nDuring the Portal startup the startup fails with these messages in the SystemOut.log..."UnsupportedClassVersionError" and "bad major version at offset=6"
\nSymptom
\n\n
\n The SystemOut.log shows the following...
[7/11/14 13:20:23:684 EDT] 0000001a Servlet E com.ibm.wps.engine.
Servlet init EJPFD0016E: Initialization of service failed.
java.lang.
UnsupportedClassVersionError:
(com/ibm/wps/services/puma/PumaServiceImpl) bad major version at
offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:267)
\n
Cause
\n\n
\n This message can occur when component was compiled under a newer version of a JDK
than what the Portal JVM is running.
In this case, this specific issue was that the customer had placed a PUMA test fix they had received from IBM while working another problem in the PortalServer/shared/app directory. This fix was made for a higher version of Portal and therefore was complied on a high JDK version than what the customer was running.
Environment
\n\n
\n Portal 6.1x
AIX
Diagnosing the problem
\n\n
\n Review the last Portal startup attempt in the SystemOut.log
\nResolving the problem
\n\n
\n In this case, the customer simply removed the test fix code from the PortalServer/shared/app directory and restarted Portal
\n\n
\n \n
\n
\n \n \n\n
\n\n\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
You activate dependency collection in your CICS TS v2.3 region\nfor MQ API requests and receive the following messages:\n.\nDFHAP0701 applid AN ABEND (CODE 0C4/AKEA) HAS OCCURRED IN EXIT\n PROGRAM CIUX63R1 AT EXIT POINT XRMIOUT.\nDFHAP0001 applid AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'000002C8' IN MODULE CIUX63R1.\nDFHME0116 applid\n(MODULE:DFHMEME) CICS SYMPTOM STRING FOR MESSAGE DFHAP0001 IS\nPIDS/5697E9300 LVLS/630 MS/DFHAP0001 RIDS/DFHSRP PTFS/UK05570\nAB/S00C4 AB/UAKEA RIDS/CIUX63R1 ADRS/000002C8\n.\nThe module name and offset may vary based on the release of\nCICS TS. The failure occurs due to CICS IA XRMIOUT GLUE\ninterpreting an MQ API DISC request as an OPEN request and\nattempting to process MQ API parameters for an OPEN which will\nnot exist resulting in the 0C4 abend.\n.\nCICS IA needs to detect and ignore an MQ API disconnect call.\n.\nAdditional Symptom(s) Search Keyword(s): R220 CIUX62R1 CIUX64R1\nCIUX65R1 CSQCTRUE CSQCSTUB MQOPEN DFHERM DFHUEH UEPTRUEP UEPHMSA\n DFHUEPARparm parmlist offset x'354' R2 R9 blanks x'40404040'\nMQFUNC2 MQ_OPEN STUB_DISC x'03010001' STUB_OPEN x'06010001'\nDFHRMCAL KIXREV\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
****************************************************************\n* USERS AFFECTED: All CICSIA V2 users collecting MQ resource *\n* information. *\n****************************************************************\n* PROBLEM DESCRIPTION: *\n* You activate dependency collection in *\n* your CICS TS v2.3 region for MQ API *\n* requests and receive the following *\n* messages: *\n* *\n* DFHAP0701 applid AN ABEND *\n* (CODE 0C4/AKEA) HAS OCCURRED IN EXIT *\n* PROGRAM CIUX63R1 AT EXIT POINT XRMIOUT. *\n* *\n* DFHAP0001 applid AN ABEND *\n* (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET *\n* X'000002C8' IN MODULE CIUX63R1. *\n* *\n* DFHME0116 applid *\n* (MODULE:DFHMEME) CICS SYMPTOM STRING *\n* FOR MESSAGE DFHAP0001 IS *\n* PIDS/5697E9300 LVLS/630 MS/DFHAP0001 *\n* RIDS/DFHSRP PTFS/UK05570 *\n* AB/S00C4 AB/UAKEA RIDS/CIUX63R1 *\n* ADRS/000002C8 *\n* *\n****************************************************************\n* RECOMMENDATION: Apply the PTF. *\n****************************************************************\nThe CIUXnnR1 XRMIOUT GLUE does not check the MQ function\ncode correctly hence an MQDISC is treated as an MQOPEN and an\nabend occurs.\n
\n \n
Problem conclusion
\n- \n
- \n \n
Processing of the MQ commands modified to ignore commands\nother than those supported by CICS:\nMQOPEN\nMQCLOSE\nMQPUT\nMQPUT1\nMQGET\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PK59516
\n Reported component name
CICS INTER ANAL
\n Reported component ID
5697J2300
\n Reported release
210
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2008-01-17
\n Closed date
2008-02-19
\n Last modified date
2008-03-04
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
UK33829 UK33830
\n
Modules/Macros
\n- \n
- \n \n
CIUX53R1 CIUX62R1 CIUX63R1 CIUX64R1 CIUX65R1\n
\n \n
Fix information
\n- \n
Fixed component name
CICS INTER ANAL
\n Fixed component ID
5697J2300
\n
Applicable component levels
\n- \n
R210 PSY UK33829
UP08/02/21 P F802
\n R220 PSY UK33830
UP08/02/21 P F802
\n
\n
\n
",
+ "title": "IBM PK59516: DFHAP0701 CIUX63R1 OFFSET X'2C8' OR X'354' MQOPEN MQDISC - United States",
+ "text": " 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 * You activate dependency collection in your CICS TS v2.3 region\n for MQ API requests and receive the following messages:\n .\n DFHAP0701 applid AN ABEND (CODE 0C4/AKEA) HAS OCCURRED IN EXIT\n PROGRAM CIUX63R1 AT EXIT POINT XRMIOUT.\n DFHAP0001 applid AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET\n X'000002C8' IN MODULE CIUX63R1.\n DFHME0116 applid\n (MODULE:DFHMEME) CICS SYMPTOM STRING FOR MESSAGE DFHAP0001 IS\n PIDS/5697E9300 LVLS/630 MS/DFHAP0001 RIDS/DFHSRP PTFS/UK05570\n AB/S00C4 AB/UAKEA RIDS/CIUX63R1 ADRS/000002C8\n .\n The module name and offset may vary based on the release of\n CICS TS. The failure occurs due to CICS IA XRMIOUT GLUE\n interpreting an MQ API DISC request as an OPEN request and\n attempting to process MQ API parameters for an OPEN which will\n not exist resulting in the 0C4 abend.\n .\n CICS IA needs to detect and ignore an MQ API disconnect call.\n .\n Additional Symptom(s) Search Keyword(s): R220 CIUX62R1 CIUX64R1\n CIUX65R1 CSQCTRUE CSQCSTUB MQOPEN DFHERM DFHUEH UEPTRUEP UEPHMSA\n DFHUEPARparm parmlist offset x'354' R2 R9 blanks x'40404040'\n MQFUNC2 MQ_OPEN STUB_DISC x'03010001' STUB_OPEN x'06010001'\n DFHRMCAL KIXREV\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All CICSIA V2 users collecting MQ resource *\n * information. *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * You activate dependency collection in *\n * your CICS TS v2.3 region for MQ API *\n * requests and receive the following *\n * messages: *\n * *\n * DFHAP0701 applid AN ABEND *\n * (CODE 0C4/AKEA) HAS OCCURRED IN EXIT *\n * PROGRAM CIUX63R1 AT EXIT POINT XRMIOUT. *\n * *\n * DFHAP0001 applid AN ABEND *\n * (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET *\n * X'000002C8' IN MODULE CIUX63R1. *\n * *\n * DFHME0116 applid *\n * (MODULE:DFHMEME) CICS SYMPTOM STRING *\n * FOR MESSAGE DFHAP0001 IS *\n * PIDS/5697E9300 LVLS/630 MS/DFHAP0001 *\n * RIDS/DFHSRP PTFS/UK05570 *\n * AB/S00C4 AB/UAKEA RIDS/CIUX63R1 *\n * ADRS/000002C8 *\n * *\n ****************************************************************\n * RECOMMENDATION: Apply the PTF. *\n ****************************************************************\n The CIUXnnR1 XRMIOUT GLUE does not check the MQ function\n code correctly hence an MQDISC is treated as an MQOPEN and an\n abend occurs.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Processing of the MQ commands modified to ignore commands\n other than those supported by CICS:\n MQOPEN\n MQCLOSE\n MQPUT\n MQPUT1\n MQGET\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK59516\n \n \n * REPORTED COMPONENT NAME\n CICS INTER ANAL\n \n \n * REPORTED COMPONENT ID\n 5697J2300\n \n \n * REPORTED RELEASE\n 210\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 2008-01-17\n \n \n * CLOSED DATE\n 2008-02-19\n \n \n * LAST MODIFIED DATE\n 2008-03-04\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 UK33829 UK33830\n \n \n\nMODULES/MACROS\n * CIUX53R1 CIUX62R1 CIUX63R1 CIUX64R1 CIUX65R1\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n CICS INTER ANAL\n \n \n * FIXED COMPONENT ID\n 5697J2300\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R210 PSY UK33829\n UP08/02/21 P F802\n \n \n * R220 PSY UK33830\n UP08/02/21 P F802",
+ "metadata": {
+ "sourceDocumentId": "swg1PK59516",
+ "date": "2008-03-04",
+ "productName": "CICS Interdependency Analyzer for z/OS",
+ "productId": "SSPPUS",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PK59516"
+ }
+ },
+ "swg21607248": {
+ "id": "swg21607248",
+ "content": "
\n
\n\n\n\n
\nDFHAP0001 S0C4 0C4 abend0C4 AKEA abendAKEA 'FFFF DFHERMSP MSGDFHAP0001 DFHRM0002 020C DFHRMUW MSGDFHRM0002 TM4N960 ASG_TMON ASG-TMON ; ASG TMON for CICS ; 5655S9700 R670 670 R700 700 HCI6700 5655-S97 5655S97 KIXINFO
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n \n
Problem(Abstract)
\nWhile your CICS Transaction Server for z/OS (CICS TS) region is running, you receive message DFHAP0001 0C4 AKEA (abend0C4 abendAKEA) at offset FFFF in DFHERMSP. This is followed by DFHRM0002 code 020C in DFHRMUW or DFHRM0002 code 020B in DFHRMUO. You are using ASG-TMON from ASG Software Solutions.
\nSymptom
\n\n
\n You see the following messages in the CICS log:
DFHAP0001 applid AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET X'FFFF' IN MODULE DFHERMSP
This is followed by one of these DFHRM0002 messages:
DFHRM0002 applid A SEVERE ERROR (CODE X'020C') HAS OCCURRED IN MODULE DFHRMUW
or
DFHRM0002 applid A SEVERE ERROR (CODE X'020B') HAS OCCURRED IN MODULE DFHRMUO
\n
Cause
\n\n
\n An ASG-TMON program TM4N960 running in 64-bit addressing mode used a 31-bit pointer that had the high order bit on.
\nDiagnosing the problem
\n\n
\n Reviewing the system dump of the DFHRM0002 you will see the following information for the 0C4 abend:
KE Domain Error Table Summary
ERR_NUM ERR_TIME KE_NUM ERROR TYPE ERR_CODE MODULE OFFSET
======= ======== ====== ========== ======== ====== ======
00000004 09:31:16 0082 PROGRAM_CHECK 0C4/AKEA UNKNOWN UNKNOWN
Error Number: 00000004
Program DFHERMSP was in control, but the PSW was elsewhere.
CICS Registers and PSW: 078D1001 80000000 00000000 00746156 IL: 6 IC: 38
64-BIT REGISTERS 0-15
00000000_19A9E000 00000000_1A35352C 00000000_00007000 40404040_0813D000
40404040_1A353360 40404040_0813DFFF 40404040_1B85C158 40404040_19C0A100
40404040_00000068 00000000_1A35352C 40404040_1A352ED8 40404040_19E43100
40404040_19E43100 40404040_1A353360 00000000_8813DFB8 00000000_00746150
Now, taking the PSW 00746156 and viewing this in IPCS browse mode you see the failing instruction is STORE MULTIPLE:
00746156 | EBEC D008 0024 | STMG R14,R12,X'8'(R13)
Since this has a interrupt code of 38 the reason for failure is due to the fact a program running in 64-bit addressing mode used a 31-bit pointer that had the high order bit on.
Backing up from the PSW I see it is currently executing in a TMON module TM4N960:
00746000 | .&>MODHEAD.A.670TM4N960 05/08/12 |
00746020 | @16.07.}............../&TH03422 |
00746040 | ............................ |
00746060
00746140 | {0......}.....1- |
00746160 | .o.-1.."..!.1..01.......TM4N960 |
00746180 | ........ASM 05/08/12 16.07 VERSI |
007461A0 | ON 033 MOD LEVEL 0000-020 LICENS |
007461C0 | ED MATERIALS COPYRIGHT 1990, 201 |
007461E0 | 1 BY ALLEN SYSTEMS GROUP, INC. |
00746200 | TH03422 ............ |
Resolving the problem
\n\n
\n Apply ASG-TMON fix TH03438. Contact ASG Software Solutions for additional information.
\n \n
\n \n
\n \n \nProduct Alias/Synonym
\nCICS/TS CICS TS CICS Transaction Server
\n",
+ "title": "IBM DFHAP0001 0C4 in DFHERMSP and DFHRM0002 with 020C in DFHRMUW or 020B in DFHRMUO when using ASG TMON - United States",
+ "text": "DFHAP0001 S0C4 0C4 abend0C4 AKEA abendAKEA 'FFFF DFHERMSP MSGDFHAP0001 DFHRM0002 020C DFHRMUW MSGDFHRM0002 TM4N960 ASG_TMON ASG-TMON ; ASG TMON for CICS ; 5655S9700 R670 670 R700 700 HCI6700 5655-S97 5655S97 KIXINFO TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n While your CICS Transaction Server for z/OS (CICS TS) region is running, you receive message DFHAP0001 0C4 AKEA (abend0C4 abendAKEA) at offset FFFF in DFHERMSP. This is followed by DFHRM0002 code 020C in DFHRMUW or DFHRM0002 code 020B in DFHRMUO. You are using ASG-TMON from ASG Software Solutions. \n\nSYMPTOM\nYou see the following messages in the CICS log:\nDFHAP0001 [http://pic.dhe.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.messages.doc/cics_mc/dfhap/AP0001.html]applid AN ABEND (CODE 0C4/AKEA) HAS OCCURRED AT OFFSET X'FFFF' IN MODULE DFHERMSP\n\nThis is followed by one of these DFHRM0002 messages:\nDFHRM0002 [http://pic.dhe.ibm.com/infocenter/cicsts/v4r2/topic/com.ibm.cics.ts.messages.doc/cics_mc/dfhrm/RM0002.html] applid A SEVERE ERROR (CODE X'020C') HAS OCCURRED IN MODULE DFHRMUW \nor\nDFHRM0002 applid A SEVERE ERROR (CODE X'020B') HAS OCCURRED IN MODULE DFHRMUO\n\n\nCAUSE\nAn ASG-TMON program TM4N960 running in 64-bit addressing mode used a 31-bit pointer that had the high order bit on.\n\nDIAGNOSING THE PROBLEM\nReviewing the system dump of the DFHRM0002 you will see the following information for the 0C4 abend:\n\nKE Domain Error Table Summary\n\nERR_NUM ERR_TIME KE_NUM ERROR TYPE ERR_CODE MODULE OFFSET\n======= ======== ====== ========== ======== ====== ======\n00000004 09:31:16 0082 PROGRAM_CHECK 0C4/AKEA UNKNOWN UNKNOWN\n\nError Number: 00000004\nProgram DFHERMSP was in control, but the PSW was elsewhere.\nCICS Registers and PSW: 078D1001 80000000 00000000 00746156 IL: 6 IC: 38\n\n64-BIT REGISTERS 0-15\n00000000_19A9E000 00000000_1A35352C 00000000_00007000 40404040_0813D000\n40404040_1A353360 40404040_0813DFFF 40404040_1B85C158 40404040_19C0A100\n40404040_00000068 00000000_1A35352C 40404040_1A352ED8 40404040_19E43100 \n40404040_19E43100 40404040_1A353360 00000000_8813DFB8 00000000_00746150 \n\nNow, taking the PSW 00746156 and viewing this in IPCS browse mode you see the failing instruction is STORE MULTIPLE: \n\n00746156 | EBEC D008 0024 | STMG R14,R12,X'8'(R13)\n\nSince this has a interrupt code of 38 the reason for failure is due to the fact a program running in 64-bit addressing mode used a 31-bit pointer that had the high order bit on. \n\nBacking up from the PSW I see it is currently executing in a TMON module TM4N960: \n\n00746000 | .&>MODHEAD.A.670TM4N960 05/08/12 |\n00746020 | @16.07.}............../&TH03422 | \n00746040 | ............................ |\n00746060\n00746140 | {0......}.....1- |\n00746160 | .o.-1..\"..!.1..01.......TM4N960 |\n00746180 | ........ASM 05/08/12 16.07 VERSI |\n007461A0 | ON 033 MOD LEVEL 0000-020 LICENS |\n007461C0 | ED MATERIALS COPYRIGHT 1990, 201 |\n007461E0 | 1 BY ALLEN SYSTEMS GROUP, INC. |\n00746200 | TH03422 ............ | \n\n\nRESOLVING THE PROBLEM\nApply ASG-TMON fix TH03438. Contact [/support/docview.wss?uid=swg21607248&aid=1] ASG Software Solutions [http://www.asg.com/] for additional information.\n\n\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server",
+ "metadata": {
+ "sourceDocumentId": "swg21607248",
+ "date": "2013-03-02",
+ "productName": "CICS Transaction Server",
+ "productId": "SSGMGV",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21607248"
+ }
+ },
+ "swg24026940": {
+ "id": "swg24026940",
+ "content": "
\n
\n\n\n\n
\nKeywords SCA; Feature Pack for SCA; SCA Feature Pack Fix Pack 1.0.1.5
\n\n\n \n \n
\n
\n
\n
\n
\n \n \n
\nDownloadable files
\n \n
\n
\n \n
Abstract
\nIBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA) Fix Pack 5 for distributed platforms, also known as SCA Feature Pack Fix Pack 1.0.1.5
\nDownload Description
\n\n
\n SCA Feature Pack Fix Pack 1.0.1.5 is now available for your download through FTP and DD links by going to the Download Package section of this document. The ZIP files in the download package section below can be used for setting up local repository to install SCA Fix Pack 1.0.1.5 using IBM Installation Manager.
WebSphere Application Server feature packs are a mechanism for providing major new application server function between product releases. By delivering new functions and support for industry standards between product releases, you can more quickly explore and implement new technologies within your business applications in today's rapidly changing business environments.
IBM® WebSphere® Application Server V7 Feature Pack for SCA delivers critical technology that enables adoption of key Service-Oriented Architecture (SOA) principles. As part of the larger SOA Foundation, which straddles all of IBM software brands, this offering delivers an integrated, open implementation of Service Component Architecture (SCA), a technology specified by IBM and other industry leaders through the Open SOA Collaboration (OSOA). For More details, visit the Information Center for SCA Feature Pack.
Change history
- \n
- 28 May 2010: Published for Fix Pack 5 (1.0.1.5) \n
Prerequisites
\n\n
\n
1. If you are going to use IBM Installation Manager to import an existing WebSphere Application Server Version 7.0 installation that contains Version 1.0.0.x of the Feature Pack for SCA and then update it to Version 1.0.1.0, first use the Update Installer to remove any fixes that have been applied to the 1.0.0.x level using the Update Installer.
2. Install WebSphere Application Server Version 7.0.0.7 or later.
3. Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site. You can then install IBM Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from the Web-based repositories.
4. If you are using local repository for your installation, IBM Installation Manager must point to SCA local import repository in order to apply any future maintenance. It is available for download from the Download package section of this document.
5. The operating system requirements for a feature pack are the same as for the application server installation. However, you need to ensure that you have enough free disk space to install the feature pack onto the application server installation.
\n \n \n
\n
\n | URL | \nLANGUAGE | \nSIZE(Bytes) | \n
|---|---|---|
| Detailed System Requirements | \nUS English | \n100 | \n
| IBM Installation Manager | \nUS English | \n100 | \n
\n
\n
\n Installation Instructions
\n\n
For detailed instructions on installing the feature pack on distributed operating systems using the GUI as well as instructions on using remote Web-based repositories and local repositories, you can visit \n Installing the feature pack on distributed operating systems using the GUI Link.\n
\n
\n Related Links\n
\n Download location for WebSphere Application Server Fix Pack 7.0.0.7\n
\n Download location for IBM Installation Manager\n
\n Download location for IBM Update Installer 7.0 for WebSphere\n
\n
\n Installing the SDO feature\n
The Feature Pack for SCA Version 1.0.1.0 and later has an optional feature--the Service Data Objects (SDO) feature. You can use IBM Installation Manager to install this feature. \n
If you continue the installation with the SDO feature selected and the Feature Pack for XML is not installed, you will receive an error message. If you install the SDO feature, you must use the manageProfiles command or the Profile Management Tool to augment an existing profile or create a new profile when this modification is finished to enable the functionality provided by the feature. \n
\n Perform the following tasks to install Feature Pack for SCA Version 1.0.1.5 on WebSphere Application Server Version 7.0.0.7 or later:
\n- \n
- Install WebSphere Application Server V7.0.
\n - Install WebSphere Application Server Fix Pack 7.0.0.7 or later using the Update Installer.
\n - Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site. Start IBM Installation Manager.
\n - Import WebSphere Application Server into Installation Manager. Make sure to stop all servers and applications on the WebSphere Application Server installation that is being imported.
\n - Install Feature Pack for SCA Version 1.0.1 using IBM Installation Manager. This can be done by using either Web-based Repository or Local Repository. Whenever possible, you should use the remote Web-based repositories so that you are accessing the most up-to-date WebSphere Application Server base-product import and feature pack installation files. The feature-pack version of Installation Manager is preconfigured to use both the local repositories (if they are set up) and the remote repositories.
\n - Install SCA Fix Pack 1.0.1.5 using Update option on IBM Installation Manager main page. This can also be done by using either Web-based Repository or Local Repository. \n
For detailed instructions on installing the feature pack on distributed operating systems using the GUI as well as instructions on using remote Web-based repositories and local repositories, you can visit \n Installing the feature pack on distributed operating systems using the GUI Link.\n
\n
\n Related Links\n
\n Download location for WebSphere Application Server Fix Pack 7.0.0.7\n
\n Download location for IBM Installation Manager\n
\n Download location for IBM Update Installer 7.0 for WebSphere\n
\n
\n Installing the SDO feature\n
The Feature Pack for SCA Version 1.0.1.0 and later has an optional feature--the Service Data Objects (SDO) feature. You can use IBM Installation Manager to install this feature. \n
Before you can install the SDO feature, you must have the Feature Pack for SCA Version 1.0.1.0 or later and the Feature Pack for XML installed on your system. Make sure that your Installation Manager preferences are pointing to the appropriate Web-based or local repositories containing the Feature Pack for SCA Version 1.0.1.0 or later product.
\nPerform this procedure to use IBM Installation Manager to install SDO feature:
\n- \n
- Stop all servers and applications on the WebSphere Application Server installation that is being modified.
\n - Start IBM Installation Manager.
\n - Click Modify.
\n - Select the package group to modify.
\n - Click Next. Note: If you are prompted to authenticate, use the IBM ID and password that you registered with on the program Web site.
\n - Expand IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA).
\n - Check the Service Data Objects checkbox to install the SDO feature. Note: This feature is optional, but it is selected by default. If you leave the SDO feature selected, you are required to install IBM WebSphere Application Server Version 7.0 Feature Pack for XML if it is not already installed. \n
If you continue the installation with the SDO feature selected and the Feature Pack for XML is not installed, you will receive an error message. If you install the SDO feature, you must use the manageProfiles command or the Profile Management Tool to augment an existing profile or create a new profile when this modification is finished to enable the functionality provided by the feature. \n
\n
For details on problems fixed in Fix Pack 5, refer to the Fix list for SCA Feature Pack 1.0.1 document.
\n\n \n \n
\n
\n | URL | \nLANGUAGE | \nSIZE(Bytes) | \n
|---|---|---|
| Fix List for SCA Feature Pack 1.0.1 | \nUS English | \n100 | \n
\n
\n
\n
\n \n Download package
\n\n \n
\n \n
\n \n \n
\n
\n | Download | \nRELEASE DATE | \nLANGUAGE | \nSIZE(Bytes) | \nDownload Options | \n
|---|---|---|---|---|
| SCA V1.0.1.5 local repository | \n05/28/2010 | \nUS English | \n6851855 | \nFTP | \n
| WAS 7.0 local import repository | \n06/17/2010 | \nUS English | \n7458626 | \nFTP | \n
| SCA V1.0 local import repository | \n04/29/2010 | \nUS English | \n1842351 | \nFTP | \n
\n
\n
\n \n
\n Technical support
\nContact 1-800-IBM-SERV (U.S. only) or visit the WebSphere Application Server Support site.
\n\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Application Servers | \nWebSphere Application Server | \n\n | AIX, HP-UX, Linux, Solaris, Windows | \n7.0 | \n\n |
\n
\n
\n \n \n \n
",
+ "title": "IBM 1.0.1.5: WebSphere Application Server V7 Feature Pack for SCA Fix Pack 1.0.1.5 - United States",
+ "text": "Keywords SCA; Feature Pack for SCA; SCA Feature Pack Fix Pack 1.0.1.5 DOWNLOADABLE FILES\n\nABSTRACT\n IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA) Fix Pack 5 for distributed platforms, also known as SCA Feature Pack Fix Pack 1.0.1.5 \n\nDOWNLOAD DESCRIPTION\nSCA Feature Pack Fix Pack 1.0.1.5 is now available for your download through FTP and DD links by going to the Download Package section of this document. The ZIP files in the download package section below can be used for setting up local repository to install SCA Fix Pack 1.0.1.5 using IBM Installation Manager.\n\nWebSphere Application Server feature packs are a mechanism for providing major new application server function between product releases. By delivering new functions and support for industry standards between product releases, you can more quickly explore and implement new technologies within your business applications in today's rapidly changing business environments. \n\nIBM\u00ae WebSphere\u00ae Application Server V7 Feature Pack for SCA [http://www-01.ibm.com/software/webservers/appserv/was/featurepacks/sca/] delivers critical technology that enables adoption of key Service-Oriented Architecture (SOA) principles. As part of the larger SOA Foundation, which straddles all of IBM software brands, this offering delivers an integrated, open implementation of Service Component Architecture (SCA), a technology specified by IBM and other industry leaders through the Open SOA Collaboration (OSOA). For More details, visit the Information Center for SCA Feature Pack. [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.soafep.multiplatform.doc/info/ae/ae/csca_overview.html]\n\nChange history \n\n * 28 May 2010: Published for Fix Pack 5 (1.0.1.5)\n\nPREREQUISITES\n\n1. If you are going to use IBM Installation Manager to import an existing WebSphere Application Server Version 7.0 installation that contains Version 1.0.0.x of the Feature Pack for SCA and then update it to Version 1.0.1.0, first use the Update Installer to remove any fixes that have been applied to the 1.0.0.x level using the Update Installer.\n\n\n2. Install WebSphere Application Server Version 7.0.0.7 or later.\n\n\n3. Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site [http://www.ibm.com/support/docview.wss?uid=swg24023498]. You can then install IBM Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from the Web-based repositories.\n\n\n4. If you are using local repository for your installation, IBM Installation Manager must point to SCA local import repository in order to apply any future maintenance. It is available for download from the Download package section of this document.\n\n\n5. The operating system requirements for a feature pack are the same as for the application server installation. However, you need to ensure that you have enough free disk space to install the feature pack onto the application server installation.\n\nURL LANGUAGE SIZE(Bytes) Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27006921] US English 100 IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg24023498] US English 100 \nINSTALLATION INSTRUCTIONS\nPerform the following tasks to install Feature Pack for SCA Version 1.0.1.5 on WebSphere Application Server Version 7.0.0.7 or later: \n\n 1. Install WebSphere Application Server V7.0. \n \n \n 2. Install WebSphere Application Server Fix Pack 7.0.0.7 [http://www.ibm.com/support/docview.wss?uid=swg24024582] or later using the Update Installer [http://www.ibm.com/support/docview.wss?uid=swg24020212]. \n \n \n 3. Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site [http://www.ibm.com/support/docview.wss?uid=swg24023498]. Start IBM Installation Manager.\n \n \n 4. Import WebSphere Application Server into Installation Manager. Make sure to stop all servers and applications on the WebSphere Application Server installation that is being imported. \n \n \n 5. Install Feature Pack for SCA Version 1.0.1 using IBM Installation Manager. This can be done by using either Web-based Repository or Local Repository. Whenever possible, you should use the remote Web-based repositories so that you are accessing the most up-to-date WebSphere Application Server base-product import and feature pack installation files. The feature-pack version of Installation Manager is preconfigured to use both the local repositories (if they are set up) and the remote repositories.\n \n \n 6. Install SCA Fix Pack 1.0.1.5 using Update option on IBM Installation Manager main page. This can also be done by using either Web-based Repository or Local Repository.\n\n\nFor detailed instructions on installing the feature pack on distributed operating systems using the GUI as well as instructions on using remote Web-based repositories and local repositories, you can visit Installing the feature pack on distributed operating systems using the GUI [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.installation.soafepnd.doc/info/ae/ae/tins_installfp.html] Link. \n\nRelated Links \nDownload location for WebSphere Application Server Fix Pack 7.0.0.7 [http://www.ibm.com/support/docview.wss?uid=swg24024582] \nDownload location for IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg24023498] \nDownload location for IBM Update Installer 7.0 for WebSphere [http://www.ibm.com/support/docview.wss?uid=swg24020212] \n\nInstalling the SDO feature \nThe Feature Pack for SCA Version 1.0.1.0 and later has an optional feature--the Service Data Objects (SDO) feature. You can use IBM Installation Manager to install this feature. Before you can install the SDO feature, you must have the Feature Pack for SCA Version 1.0.1.0 or later and the Feature Pack for XML [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/] installed on your system. Make sure that your Installation Manager preferences are pointing to the appropriate Web-based or local repositories containing the Feature Pack for SCA Version 1.0.1.0 or later product. \n\nPerform this procedure to use IBM Installation Manager to install SDO feature: \n\n 1. Stop all servers and applications on the WebSphere Application Server installation that is being modified. \n \n \n 2. Start IBM Installation Manager. \n \n \n 3. Click Modify. \n \n \n 4. Select the package group to modify. \n \n \n 5. Click Next. Note: If you are prompted to authenticate, use the IBM ID and password that you registered with on the program Web site.\n \n \n 6. Expand IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA). \n \n \n 7. Check the Service Data Objects checkbox to install the SDO feature. Note: This feature is optional, but it is selected by default. If you leave the SDO feature selected, you are required to install IBM WebSphere Application Server Version 7.0 Feature Pack for XML if it is not already installed. \n\n\nIf you continue the installation with the SDO feature selected and the Feature Pack for XML is not installed, you will receive an error message. If you install the SDO feature, you must use the manageProfiles command or the Profile Management Tool to augment an existing profile or create a new profile when this modification is finished to enable the functionality provided by the feature. \n\nFor details on problems fixed in Fix Pack 5, refer to the Fix list for SCA Feature Pack 1.0.1 [http://www.ibm.com/support/docview.wss?uid=swg27017704]document.\n\nURL LANGUAGE SIZE(Bytes) Fix List for SCA Feature Pack 1.0.1 [http://www.ibm.com/support/docview.wss?uid=swg27017704] US English 100 \nDOWNLOAD PACKAGE\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options SCA V1.0.1.5 local repository 05/28/2010 US English 6851855 FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/sca/service/1.0/fixpacks/sca.1.0.1.5.fp.zip] WAS 7.0 local import repository 06/17/2010 US English 7458626 FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip] SCA V1.0 local import repository 04/29/2010 US English 1842351 FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/sca/import/sca.1.0.import.zip] \nTECHNICAL SUPPORT\n Contact 1-800-IBM-SERV (U.S. only) or visit the WebSphere Application Server Support site [http://www.ibm.com/software/webservers/appserv/was/support/]. \n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server AIX, HP-UX, Linux, Solaris, Windows 7.0",
+ "metadata": {
+ "sourceDocumentId": "swg24026940",
+ "date": "2010-05-28",
+ "productName": "WebSphere Application Server V7 Feature Pack for Service Component Architecture",
+ "productId": "SSF2FJ,SSEQTP",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg24026940"
+ }
+ },
+ "swg21685183": {
+ "id": "swg21685183",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n \n\n
Question
\nWhy is sudo required in the PureData System for Analytics
\nCause
\n\n
\n Customer System Administrator a lot of times want to know why we require the use of sudo and specifically the lines mentioned below.
\nAnswer
\n\n
\n The script /nz/kit/bin/adm/nzauth is used to copy LDAP configuration files, regardless of whether LDAP is configured or not. Since the LDAP files reside under /etc (i.e. /etc/ldap.conf and /etc/pam.d/netezza_nps) root access is need to access these files. Normally, the nz user and thus nzstart can access these files as a result of the following lines in the /etc/sudoers:
# NPS setup -- do not edit below this line -- initarp
nz ALL = NOPASSWD: /usr/local/sbin/nzinitarp
nz ALL = NOPASSWD: /nzlocal/scripts/rpc/spapwr.sh
nz ALL = NOPASSWD: /nz/kit/bin/adm/nzauth
nz ALL = NOPASSWD: /sbin/clustat
\n \n
\n ",
+ "title": "IBM Sudo in the Pure Data System for Analytics Appliance - United States",
+ "text": " TECHNOTE (FAQ)\n\nQUESTION\n Why is sudo required in the PureData System for Analytics \n\nCAUSE\nCustomer System Administrator a lot of times want to know why we require the use of sudo and specifically the lines mentioned below.\n\nANSWER\nThe script /nz/kit/bin/adm/nzauth is used to copy LDAP configuration files, regardless of whether LDAP is configured or not. Since the LDAP files reside under /etc (i.e. /etc/ldap.conf and /etc/pam.d/netezza_nps) root access is need to access these files. Normally, the nz user and thus nzstart can access these files as a result of the following lines in the /etc/sudoers: \n\n\n# NPS setup -- do not edit below this line -- initarp\nnz ALL = NOPASSWD: /usr/local/sbin/nzinitarp\nnz ALL = NOPASSWD: /nzlocal/scripts/rpc/spapwr.sh\nnz ALL = NOPASSWD: /nz/kit/bin/adm/nzauth\nnz ALL = NOPASSWD: /sbin/clustat",
+ "metadata": {
+ "sourceDocumentId": "swg21685183",
+ "date": "2016-10-06",
+ "productName": "PureData System for Analytics",
+ "productId": "SSULQD",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21685183"
+ }
+ },
+ "swg21684196": {
+ "id": "swg21684196",
+ "content": "
\n
\n\n\n\n
\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n\n
Problem(Abstract)
\n I installed the IBM SPSS Statistics on my computer with Windows 8.
I was unable to resize the screen to see where to enter my license number.
Now when I open IBM SPSS Statistics it says it is unlicensed.
How do I enter my license number now that it has been installed on my computer?
Resolving the problem
\n\n
\n Use one of the methods below to decrease the size of the text and windows before activating IBM SPSS Statistics:
\n1. Enter the Display properties:
A) Right click an empty area of the desktop, and then click Personalize, then click Display to open the Display window
Or
B) Open the Control Panel (select icons view), and click on the Display icon.
2. To decrease the size of the text and windows, use the mouse pointer to move the slider bar to the left, and then click Apply.
3. To complete the changes, select Sign out now.
After restarting the computer, launch IBM SPSS Statistics License Authorization Wizard and enter your authorization code to obtain a license for this product.
Related information
\n Need more help? Our Statistics forum is Live!
Need more help? Our Licensing forum is Live!
\n
\n
\n
\n \n \n ",
+ "title": "IBM Could not enter authorization code in License Authorization Wizard - United States",
+ "text": " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n I installed the IBM SPSS Statistics on my computer with Windows 8. \nI was unable to resize the screen to see where to enter my license number.\nNow when I open IBM SPSS Statistics it says it is unlicensed. \n\nHow do I enter my license number now that it has been installed on my computer? \n\nRESOLVING THE PROBLEM\nUse one of the methods below to decrease the size of the text and windows before activating IBM SPSS Statistics: \n\n1. Enter the Display properties:\nA) Right click an empty area of the desktop, and then click Personalize, then click Display to open the Display window \nOr \nB) Open the Control Panel (select icons view), and click on the Display icon.\n\n2. To decrease the size of the text and windows, use the mouse pointer to move the slider bar to the left, and then click Apply.\n3. To complete the changes, select Sign out now.\n\nAfter restarting the computer, launch IBM SPSS Statistics License Authorization Wizard and enter your authorization code to obtain a license for this product.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\n\n\n[/support/docview.wss?uid=swg21684196&aid=1]\n[/support/docview.wss?uid=swg21684196&aid=2] [/support/docview.wss?uid=swg21684196&aid=2]\n[/support/docview.wss?uid=swg21684196&aid=3] [/support/docview.wss?uid=swg21684196&aid=3]",
+ "metadata": {
+ "sourceDocumentId": "swg21684196",
+ "date": "2016-09-07",
+ "productName": "SPSS Statistics",
+ "productId": "SSLVMB",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21684196"
+ }
+ },
+ "swg21625776": {
+ "id": "swg21625776",
+ "content": "
\n
\n\n\n\n
\nrelease note; downloads; nco-g-socket-java; Java Gateway for Socket
\n\n\n \n \n
\nNews
\n \n
\n
\n \n \n\n
Abstract
\nA new version of the Netcool/OMNIbus Socket Gateway will be available to download from August 6, 2015.
\nContent
\n\n
\n \n
You can access the latest version of the guide written for this gateway on the IBM Knowledge Center:
\n \nYou can download the installation package from the IBM Passport Advantage website:
www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm
Netcool/OMNIbus V8.1
\nThe Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems:
\nAIX, Linux, Solaris, Windows and zLinux.
\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this package, use the Find by part number field to search for part number: CN6I1EN
\nNetcool/OMNIbus V7.4.0
\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.
\n\n \n \n
\n
\n | Part number | \nOperating System | \n
| CN6GZEN | \nAIX | \n
| CN6H1EN | \nHPUX on Itanium | \n
| CN6H2EN | \nLinux | \n
| CN6H3EN | \nLinux for zSeries | \n
| CN6H4EN | \nSolaris | \n
| CN6H5EN | \nWindows | \n
Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.
\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:
\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html
\n \n\n \n
\n ",
+ "title": "IBM Netcool/OMNIbus Integrations Release Notice - Socket Gateway (nco-g-socket-java-2_0) - United States",
+ "text": "release note; downloads; nco-g-socket-java; Java Gateway for Socket NEWS\n\nABSTRACT\n A new version of the Netcool/OMNIbus Socket Gateway will be available to download from August 6, 2015. \n\nCONTENT\n \n\nYou can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html [http://www.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/gateways/socketjavagw/wip/concept/socketjavagw_instl_cnfgr_gateway.html]\n\nYou can download the installation package from the IBM Passport Advantage website: \nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nNetcool/OMNIbus V8.1\n\nThe Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems:\n\nAIX, Linux, Solaris, Windows and zLinux.\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this package, use the Find by part number field to search for part number: CN6I1EN\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CN6GZEN AIX CN6H1EN HPUX on Itanium CN6H2EN Linux CN6H3EN Linux for zSeries CN6H4EN Solaris CN6H5EN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]",
+ "metadata": {
+ "sourceDocumentId": "swg21625776",
+ "date": "2015-08-06",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21625776"
+ }
+ },
+ "swg24041052": {
+ "id": "swg24041052",
+ "content": "
\n
\n\n\n\n
\nSCA; Feature Pack for SCA; SCA Feature Pack Fix Pack 1.0.1.19
\n\n\n \n \n
\n
\n
\n
\n \n \n
\nDownloadable files
\n \n
\n
\n \n
Abstract
\nIBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA) Fix Pack 19 for distributed platforms, also known as SCA Feature Pack Fix Pack 1.0.1.19
\nDownload Description
\n\n
\n Known Issues \n
\n Change History \n
\n
\n SCA Feature Pack Fix Pack 1.0.1.19 is now available for your download through FTP and DD links by going to the Download Package section of this document. The ZIP files in the download package section below can be used for setting up local repository to install SCA Fix Pack 1.0.1.19 using IBM Installation Manager.
WebSphere Application Server feature packs are a mechanism for providing major new application server function between product releases. By delivering new functions and support for industry standards between product releases, you can more quickly explore and implement new technologies within your business applications in today's rapidly changing business environments.
IBM WebSphere Application Server V7 Feature Pack for SCA delivers critical technology that enables adoption of key Service-Oriented Architecture (SOA) principles. As part of the larger SOA Foundation, which straddles all of IBM software brands, this offering delivers an integrated, open implementation of Service Component Architecture (SCA), a technology specified by IBM and other industry leaders through the Open SOA Collaboration (OSOA). For More details, visit the Information Center for SCA Feature Pack.
Download Package
\n\n \n \n
\n
\n | \n \n Download\n | \n \n \n Language\n | \n \n \n Download options\n | \n
| \n \n SCA V1.0.1.19 local repository\n | \n \n \n US English\n | \n \n \n FTP\n | \n
| \n \n WAS 7.0 local import repository\n | \n \n \n US English\n | \n \n \n FTP\n | \n
| \n \n SCA V1.0 local import repository\n | \n \n \n US English\n | \n \n \n FTP\n | \n
\n Known Issues \n
- \n
- OSGi Application Blueprint Service registrations fail. For details visit this Link. \n
\n Change History \n
- \n
- Nov 2, 2015: Published for SCA Fix Pack 19 (1.0.1.19) \n
\n
Prerequisites
\n\n
\n
\n \n
- \n
- If you are going to use IBM Installation Manager to import an existing WebSphere Application Server Version 7.0 installation that contains Version 1.0.0.x of the Feature Pack for SCA and then update it to Version 1.0.1.0, first use the Update Installer to remove any fixes that have been applied to the 1.0.0.x level using the Update Installer.
\n - Install WebSphere Application Server Version 7.0.0.7 or later.
\n - Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site. You can then install IBM Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from the Web-based repositories.
\n - If you are using local repository for your installation, IBM Installation Manager must point to SCA local import repository in order to apply any future maintenance. It is available for download from the Download package section of this document.
\n - The operating system requirements for a feature pack are the same as for the application server installation. However, you need to ensure that you have enough free disk space to install the feature pack onto the application server installation. \n
\n
\n \n \n
\n
\n | URL | \nLANGUAGE | \nSIZE(Bytes) | \n
|---|---|---|
| Detailed System Requirements | \nUS English | \n100 | \n
| IBM Installation Manager | \nUS English | \n100 | \n
\n
\n
\n Installation Instructions
\n\n
For detailed instructions on installing the feature pack on distributed operating systems using the GUI as well as instructions on using remote Web-based repositories and local repositories, you can visit \n Installing the feature pack on distributed operating systems using the GUI Link.\n
\n
\n Related Links\n
\n Download location for WebSphere Application Server Fix Pack 7.0.0.7\n
\n Download location for IBM Installation Manager\n
\n Download location for IBM Update Installer 7.0 for WebSphere\n
\n
\n Installing the SDO feature\n
The Feature Pack for SCA Version 1.0.1.0 and later has an optional feature--the Service Data Objects (SDO) feature. You can use IBM Installation Manager to install this feature.\n
\n
Before you can install the SDO feature, you must have the Feature Pack for SCA Version 1.0.1.0 or later and the \n Feature Pack for XML installed on your system. Make sure that your Installation Manager preferences are pointing to the appropriate Web-based or local repositories containing the Feature Pack for SCA Version 1.0.1.0 or later product.\n
Perform this procedure to use IBM Installation Manager to install SDO feature: \n
If you continue the installation with the SDO feature selected and the Feature Pack for XML is not installed, you will receive an error message. If you install the SDO feature, you must use the manageProfiles command or the Profile Management Tool to augment an existing profile or create a new profile when this modification is finished to enable the functionality provided by the feature.\n
\n
For details on problems fixed in Fix Pack 17, refer to the \n Fix list for SCA Feature Pack 1.0.1 document.\n
\n
\n
\n Perform the following tasks to install Feature Pack for SCA Version 1.0.1.19 on WebSphere Application Server Version 7.0.0.7 or later:
- \n
- Install WebSphere Application Server V7.0.
\n - Install WebSphere Application Server Fix Pack 7.0.0.7 or later using the Update Installer.
\n - Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site. Start IBM Installation Manager.
\n - Import WebSphere Application Server into Installation Manager. Make sure to stop all servers and applications on the WebSphere Application Server installation that is being imported.
\n - Install Feature Pack for SCA Version 1.0.1 using IBM Installation Manager. This can be done by using either Web-based Repository or Local Repository. Whenever possible, you should use the remote Web-based repositories so that you are accessing the most up-to-date WebSphere Application Server base-product import and feature pack installation files. The feature-pack version of Installation Manager is preconfigured to use both the local repositories (if they are set up) and the remote repositories.
\n - Install SCA Fix Pack 1.0.1.19 using Update option on IBM Installation Manager main page. This can also be done by using either Web-based Repository or Local Repository. \n
For detailed instructions on installing the feature pack on distributed operating systems using the GUI as well as instructions on using remote Web-based repositories and local repositories, you can visit \n Installing the feature pack on distributed operating systems using the GUI Link.\n
\n
\n Related Links\n
\n Download location for WebSphere Application Server Fix Pack 7.0.0.7\n
\n Download location for IBM Installation Manager\n
\n Download location for IBM Update Installer 7.0 for WebSphere\n
\n
\n Installing the SDO feature\n
The Feature Pack for SCA Version 1.0.1.0 and later has an optional feature--the Service Data Objects (SDO) feature. You can use IBM Installation Manager to install this feature.\n
\n
Before you can install the SDO feature, you must have the Feature Pack for SCA Version 1.0.1.0 or later and the \n Feature Pack for XML installed on your system. Make sure that your Installation Manager preferences are pointing to the appropriate Web-based or local repositories containing the Feature Pack for SCA Version 1.0.1.0 or later product.\n
Perform this procedure to use IBM Installation Manager to install SDO feature: \n
- \n
- Stop all servers and applications on the WebSphere Application Server installation that is being modified.
\n - Start IBM Installation Manager.
\n - Click Modify.
\n - Select the package group to modify.
\n - Click Next. Note: If you are prompted to authenticate, use the IBM ID and password that you registered with on the program Web site.
\n - Expand IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA).
\n - Check the Service Data Objects checkbox to install the SDO feature. Note: This feature is optional, but it is selected by default. If you leave the SDO feature selected, you are required to install IBM WebSphere Application Server Version 7.0 Feature Pack for XML if it is not already installed. \n
If you continue the installation with the SDO feature selected and the Feature Pack for XML is not installed, you will receive an error message. If you install the SDO feature, you must use the manageProfiles command or the Profile Management Tool to augment an existing profile or create a new profile when this modification is finished to enable the functionality provided by the feature.\n
\n
For details on problems fixed in Fix Pack 17, refer to the \n Fix list for SCA Feature Pack 1.0.1 document.\n
\n
\n
\n \n \n
\n
\n | URL | \nLANGUAGE | \nSIZE(Bytes) | \n
|---|---|---|
| Fix List for SCA Feature Pack 1.0.1 | \nUS English | \n100 | \n
\n
\n
\n
\n \n \n \n
\n \n
\n
\n \n
\n Technical support
\nContact 1-800-IBM-SERV (U.S. only) or visit the WebSphere Application Server Support site.
\n\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Application Servers | \nWebSphere Application Server | \n\n | AIX, HP-UX, Linux, Solaris, Windows | \n7.0 | \n\n |
\n
\n
\n \n \n \n
",
+ "title": "IBM 1.0.1.19: WebSphere Application Server V7 Feature Pack for SCA Fix Pack 1.0.1.19 - United States",
+ "text": "SCA; Feature Pack for SCA; SCA Feature Pack Fix Pack 1.0.1.19 DOWNLOADABLE FILES\n\nABSTRACT\n IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA) Fix Pack 19 for distributed platforms, also known as SCA Feature Pack Fix Pack 1.0.1.19 \n\nDOWNLOAD DESCRIPTION\nSCA Feature Pack Fix Pack 1.0.1.19 is now available for your download through FTP and DD links by going to the Download Package section of this document. The ZIP files in the download package section below can be used for setting up local repository to install SCA Fix Pack 1.0.1.19 using IBM Installation Manager.\n\nWebSphere Application Server feature packs are a mechanism for providing major new application server function between product releases. By delivering new functions and support for industry standards between product releases, you can more quickly explore and implement new technologies within your business applications in today's rapidly changing business environments. \n\nIBM WebSphere Application Server V7 Feature Pack for SCA [http://www.ibm.com/software/webservers/appserv/was/featurepacks/sca/] delivers critical technology that enables adoption of key Service-Oriented Architecture (SOA) principles. As part of the larger SOA Foundation, which straddles all of IBM software brands, this offering delivers an integrated, open implementation of Service Component Architecture (SCA), a technology specified by IBM and other industry leaders through the Open SOA Collaboration (OSOA). For More details, visit the Information Center for SCA Feature Pack. [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.soafep.multiplatform.doc/info/ae/ae/csca_overview.html]\n\n\nDownload Package \n\nDownload Language Download options SCA V1.0.1.19 local repository US English FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/sca/service/1.0/fixpacks/sca.1.0.1.19.fp.zip] WAS 7.0 local import repository US English FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/was/import/was.7.0.import.zip] SCA V1.0 local import repository US English FTP [ftp://public.dhe.ibm.com/software/websphere/downloads/sca/import/sca.1.0.import.zip] \nKnown Issues * OSGi Application Blueprint Service registrations fail. For details visit this Link [http://www-01.ibm.com/support/docview.wss?uid=swg24033832].\n\n\nChange History * Nov 2, 2015: Published for SCA Fix Pack 19 (1.0.1.19)\n\n\nPREREQUISITES\n \n\n 1. If you are going to use IBM Installation Manager to import an existing WebSphere Application Server Version 7.0 installation that contains Version 1.0.0.x of the Feature Pack for SCA and then update it to Version 1.0.1.0, first use the Update Installer to remove any fixes that have been applied to the 1.0.0.x level using the Update Installer.\n \n \n 2. Install WebSphere Application Server Version 7.0.0.7 or later.\n \n \n 3. Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site [http://www.ibm.com/support/docview.wss?uid=swg24023498]. You can then install IBM Installation Manager on your local system and use it to import WebSphere Application Server Version 7.0 as well as to install the feature pack from the Web-based repositories.\n \n \n 4. If you are using local repository for your installation, IBM Installation Manager must point to SCA local import repository in order to apply any future maintenance. It is available for download from the Download package section of this document.\n \n \n 5. The operating system requirements for a feature pack are the same as for the application server installation. However, you need to ensure that you have enough free disk space to install the feature pack onto the application server installation.\n\n\nURL LANGUAGE SIZE(Bytes) Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27006921] US English 100 IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg24023498] US English 100 \nINSTALLATION INSTRUCTIONS\nPerform the following tasks to install Feature Pack for SCA Version 1.0.1.19 on WebSphere Application Server Version 7.0.0.7 or later:\n\n\n 1. Install WebSphere Application Server V7.0. \n \n \n 2. Install WebSphere Application Server Fix Pack 7.0.0.7 [http://www.ibm.com/support/docview.wss?uid=swg24024582] or later using the Update Installer [http://www.ibm.com/support/docview.wss?uid=swg24020212]. \n \n \n 3. Install IBM Installation Manager. You can download and unpack a compressed file containing the IBM Installation Manager appropriate for your operating system from the IBM Installation Manager Web site [http://www.ibm.com/support/docview.wss?uid=swg24023498]. Start IBM Installation Manager.\n \n \n 4. Import WebSphere Application Server into Installation Manager. Make sure to stop all servers and applications on the WebSphere Application Server installation that is being imported. \n \n \n 5. Install Feature Pack for SCA Version 1.0.1 using IBM Installation Manager. This can be done by using either Web-based Repository or Local Repository. Whenever possible, you should use the remote Web-based repositories so that you are accessing the most up-to-date WebSphere Application Server base-product import and feature pack installation files. The feature-pack version of Installation Manager is preconfigured to use both the local repositories (if they are set up) and the remote repositories.\n \n \n 6. Install SCA Fix Pack 1.0.1.19 using Update option on IBM Installation Manager main page. This can also be done by using either Web-based Repository or Local Repository.\n\n\nFor detailed instructions on installing the feature pack on distributed operating systems using the GUI as well as instructions on using remote Web-based repositories and local repositories, you can visit Installing the feature pack on distributed operating systems using the GUI [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.installation.soafepnd.doc/info/ae/ae/tins_installfp.html] Link. \n\nRelated Links \nDownload location for WebSphere Application Server Fix Pack 7.0.0.7 [http://www.ibm.com/support/docview.wss?uid=swg24024582] \nDownload location for IBM Installation Manager [http://www.ibm.com/support/docview.wss?uid=swg24023498] \nDownload location for IBM Update Installer 7.0 for WebSphere [http://www.ibm.com/support/docview.wss?uid=swg24020212] \n\nInstalling the SDO feature \nThe Feature Pack for SCA Version 1.0.1.0 and later has an optional feature--the Service Data Objects (SDO) feature. You can use IBM Installation Manager to install this feature. \n\nBefore you can install the SDO feature, you must have the Feature Pack for SCA Version 1.0.1.0 or later and the Feature Pack for XML [http://www.ibm.com/software/webservers/appserv/was/featurepacks/xml/] installed on your system. Make sure that your Installation Manager preferences are pointing to the appropriate Web-based or local repositories containing the Feature Pack for SCA Version 1.0.1.0 or later product. \nPerform this procedure to use IBM Installation Manager to install SDO feature: 1. Stop all servers and applications on the WebSphere Application Server installation that is being modified. \n \n \n 2. Start IBM Installation Manager. \n \n \n 3. Click Modify. \n \n \n 4. Select the package group to modify. \n \n \n 5. Click Next. Note: If you are prompted to authenticate, use the IBM ID and password that you registered with on the program Web site.\n \n \n 6. Expand IBM WebSphere Application Server V7 Feature Pack for Service Component Architecture (SCA). \n \n \n 7. Check the Service Data Objects checkbox to install the SDO feature. Note: This feature is optional, but it is selected by default. If you leave the SDO feature selected, you are required to install IBM WebSphere Application Server Version 7.0 Feature Pack for XML if it is not already installed. \n\n\nIf you continue the installation with the SDO feature selected and the Feature Pack for XML is not installed, you will receive an error message. If you install the SDO feature, you must use the manageProfiles command or the Profile Management Tool to augment an existing profile or create a new profile when this modification is finished to enable the functionality provided by the feature. \n\nFor details on problems fixed in Fix Pack 17, refer to the Fix list for SCA Feature Pack 1.0.1 [http://www.ibm.com/support/docview.wss?uid=swg27017704]document. \n\nURL LANGUAGE SIZE(Bytes) Fix List for SCA Feature Pack 1.0.1 [http://www.ibm.com/support/docview.wss?uid=swg27017704] US English 100 \n\n\n\n\n\nTECHNICAL SUPPORT\n Contact 1-800-IBM-SERV (U.S. only) or visit the WebSphere Application Server Support site [http://www.ibm.com/software/webservers/appserv/was/support/]. \n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server AIX, HP-UX, Linux, Solaris, Windows 7.0",
+ "metadata": {
+ "sourceDocumentId": "swg24041052",
+ "date": "2016-09-22",
+ "productName": "WebSphere Application Server V7 Feature Pack for Service Component Architecture",
+ "productId": "SSF2FJ,SSEQTP",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg24041052"
+ }
+ },
+ "swg1PI20969": {
+ "id": "swg1PI20969",
+ "content": "
\n
\n\n\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as program error.
\n
Error description
\n- \n
- \n \n
Microsoft Windows 7 IBM Rational Team Concert (RTC) Shell client\ntask tray icon is unresponsive and disappears after a few\nminutes.\n\nWhat steps will reproduce the problem?\n1. Install RTC Shell client 4.0.6\n2. Dismiss the startup dialog box.\n3. Right click on the RTC Shell client icon in the task tray.\n\nWhat is the expected output?\nThe startup dialog box closes. A context menu appears above the\nRTC Shell icon.The icon is responsive and does not disappear.\n\nWhat do you see instead?\nThe startup dialog does not close. No context menu appears. The\nicon is unresponsive and disappears after few minutes.\n\nOperations like setting a sandbox, switching from basic to\nadvanced mode or vice-versa from the RTC Shell Control Panel\npage do not complete.\n
\n \n
Local fix
\n- \n
- \n \n
There is no workaround available.\n\nFor more details visit jazz defect:\nhttps://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo\nrkItem/322205\n
\n \n
Problem summary
\n- \n
- \n \n
****************************************************************\n* USERS AFFECTED: *\n* RTC Shell *\n****************************************************************\n* PROBLEM DESCRIPTION: *\n* RTC Shell task tray icon is unresponsive and disappears *\n* after a few minutes *\n****************************************************************\n* RECOMMENDATION: *\n****************************************************************\n
\n \n
Problem conclusion
\n- \n
- \n \n
Fixed in RTC version 4.0.7\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PI20969
\n Reported component name
RATL TEAM CONCE
\n Reported component ID
5724V0400
\n Reported release
406
\n Status
CLOSED PER
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2014-06-27
\n Closed date
2014-09-29
\n Last modified date
2014-09-29
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Fixed component name
RATL TEAM CONCE
\n Fixed component ID
5724V0400
\n
Applicable component levels
\n- \n
R406 PSY
UP
\n
\n
\n
",
+ "title": "IBM PI20969: (WI 322205) WINDOWS 7 RTC SHELL CLIENT TASK TRAY ICON IS UNRESPONSIVE AND DISAPPEARS AFTER A FEW MINUTES - United States",
+ "text": " 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 * Microsoft Windows 7 IBM Rational Team Concert (RTC) Shell client\n task tray icon is unresponsive and disappears after a few\n minutes.\n \n What steps will reproduce the problem?\n 1. Install RTC Shell client 4.0.6\n 2. Dismiss the startup dialog box.\n 3. Right click on the RTC Shell client icon in the task tray.\n \n What is the expected output?\n The startup dialog box closes. A context menu appears above the\n RTC Shell icon.The icon is responsive and does not disappear.\n \n What do you see instead?\n The startup dialog does not close. No context menu appears. The\n icon is unresponsive and disappears after few minutes.\n \n Operations like setting a sandbox, switching from basic to\n advanced mode or vice-versa from the RTC Shell Control Panel\n page do not complete.\n \n \n \n \n \n\nLOCAL FIX\n * There is no workaround available.\n \n For more details visit jazz defect:\n https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.Wo]\n rkItem/322205\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: *\n * RTC Shell *\n ****************************************************************\n * PROBLEM DESCRIPTION: *\n * RTC Shell task tray icon is unresponsive and disappears *\n * after a few minutes *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Fixed in RTC version 4.0.7\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI20969\n \n \n * REPORTED COMPONENT NAME\n RATL TEAM CONCE\n \n \n * REPORTED COMPONENT ID\n 5724V0400\n \n \n * REPORTED RELEASE\n 406\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-06-27\n \n \n * CLOSED DATE\n 2014-09-29\n \n \n * LAST MODIFIED DATE\n 2014-09-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 * FIXED COMPONENT NAME\n RATL TEAM CONCE\n \n \n * FIXED COMPONENT ID\n 5724V0400\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R406 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1PI20969",
+ "date": "2014-09-29",
+ "productName": "Rational Team Concert",
+ "productId": "SSCP65",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PI20969"
+ }
+ },
+ "swg21685680": {
+ "id": "swg21685680",
+ "content": "
\n
",
+ "title": "IBM Base version of Portal 8.5 install fails noting a cumulative fix conflict during silent install - United States",
+ "text": "base install fails; CF conflict TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAttempts to install the Base version of Portal 8.5 using a response file fails as it notes that the cumulative fix fails as it requires the Base version\n\nSYMPTOM\nThe IBM Installation Manger throws the following exception:\n\nThis Cumulative Fix requires that IBM WebSphere Portal Server version 8.5.0.0 be previously installed. You must first install the base release and then update it with the Cumulative Fix. You cannot install\nthem at the same time.\n\n\nCAUSE\nThe class that triggers the message about not being able to install a CF is found in a plugin\nshipped with each install image: wp.im.wpcf.warning_8.5.0.\n\n
\nbase install fails; CF conflict
\n\n\n \n \n
\n \n
\n Technote (troubleshooting)
\n \n
\n
\n
\n \n
Problem
\n\n
\n Attempts to install the Base version of Portal 8.5 using a response file fails as it notes that the cumulative fix fails as it requires the Base version
\nSymptom
\n\n
\n The IBM Installation Manger throws the following exception:
This Cumulative Fix requires that IBM WebSphere Portal Server version 8.5.0.0 be previously installed. You must first install the base release and then update it with the Cumulative Fix. You cannot install
them at the same time.
\n
Cause
\n\n
\n The class that triggers the message about not being able to install a CF is found in a plugin
shipped with each install image: wp.im.wpcf.warning_8.5.0.<qualifier>.jar (The qualifier is different in each image and is based on the date the jar was built.) The version of this plugin shipped with CFs should trigger the message whereas the version shipped with the base v8.5 code should not. It seems like there is a conflict in this scenario where the wrong version of the plugin is getting loaded.
Environment
\n\n
\n WebSphere Portal 8.5
\nDiagnosing the problem
\n\n
\n To reproduce the issue:
1. install WAS/Portal
2. upgrade to CF01
3. rollback CF01
4. uninstall WAS/Portal
5. install WAS/Portal <-- this fails noting that you cant install CF without the base version of Portal but the response file has no mentionof the CF
Resolving the problem
\n\n
\n Installation Manager usually tries to install the latest available version of a product, so if the CF02 image is visible to Installation Manager at all, then that's what it will try to use.
A way to prevent this is to modify the response file to specifically point to the GM image. Change this line in wp85-server-and-wcm-install.xml:
<offering id="com.ibm.websphere.PORTAL.SERVER.v85" profile="IBM
WebSphere Portal Server V8.5" features="ce.install,portal.binary
,portal.profile" installFixes="none"/>
to:
<offering id="com.ibm.websphere.PORTAL.SERVER.v85" profile="IBM
WebSphere Portal Server V8.5" version="8.5.0.20140424_2155"
features="ce.install,portal.binary,portal.profile"
installFixes="none"/>
\n
in wp85-express-and-wcm-install.xml:
<offering id="com.ibm.websphere.PORTAL.EXPRESS.v85" profile="IBM
WebSphere Portal Express V8.5" features="ce.install,portal.binary
,portal.profile" installFixes="none"/>
to:
<offering id="com.ibm.websphere.PORTAL.EXPRESS.v85" profile="IBM
WebSphere Portal Express V8.5" version="8.5.0.20140424_2152"
features="ce.install,portal.binary,portal.profile"
installFixes="none"/>
\n \n
\n \n
\n \n \n\n
",
+ "title": "IBM Intermittent \"The ConnectionString property has not been initialized\" errors triggered by IIS AppPool recycling - United States",
+ "text": " TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User launches Controller. User successfully uses Controller functionality for some time. After a while, user receives error message. \n\nThe problem may appear to occur at random. It can potentially appear when performing any functionality. \n\nSYMPTOM\nThe exact error will vary depending on the function being used. Below is an example when running a standard report: \n\n[/support/docview.wss?uid=swg21973433&aid=1] [/support/docview.wss?uid=swg21973433&aid=1]\nStandard Error \n\nNumber: 5\nSource: FrangoDirect.AccountReportsD.CreateCodesRsCRN#System.Web.Services.frmAccountRep.CreateCodesRs\nDescription: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.ArgumentException: The ConnectionString property has not been initialized.\nat Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)\nat ControllerServerCommon.RaiseErrSrv.RaiseError(String sUser, Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)\nat FrMiscS.ConfigSet.ISet_SelectRecord(String sGuid, String sSelectCriterion, Array& vKey, String sUser, Int32 lLLocale)\nat Cognos.Controller.SEC.ControllerConfigData.GetRow(String sGuid, String sTyp1, String sTyp2, String sAnvid)\nat Cognos.Controller.SEC.ValidateSecurity..ctor(String sGuid, String sUser)\nat Cognos.Controller.SEC.ParameterValidator.GetValidateSecurity()\nat Cognos.Controller.SEC.ParameterValidator.IsMenuItemAllowed(String sMenus, String sReadWrite)\nat Cognos.Controller.Proxy.SoapExtension.ServerExtension.RightsValueObject.IsAllowed(SoapMessage& message, String& Guid, String& User, Int32& iError)\nat Cognos.Controller.Proxy.SoapExtension.ServerExtension.CheckAccessControl(SoapMessage& message)\nat Cognos.Controller.Proxy.SoapExtension.ServerExtension.ProcessMessage(SoapMessage message)\nat System.Web.Services.Protocols.SoapMessage.RunExtensions(SoapExtension[] extensions, Boolean throwOnException)\nat System.Web.Services.Protocols.SoapServerProtocol.CreateServerInstance()\nat System.Web.Services.Protocols.WebServiceHandler.Invoke()\nat System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()\n--- End of inner exception stack trace ---\nat Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)\nat Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)\nat Cognos.Controller.Forms.Form.frmAccountRep.CreateCodesRsCRN(XmlDocument& xmlDoc)\nat Cognos.Controller.Forms.Form.frmAccountRep.IFormStandardReport_CreateReportData(IStandardReport& cIStandardReport)\n\n\nCAUSE\nThere are several different possible causes for a similar error. \n\n * TIP: See separate IBM Technote #1963432 for more examples.\n\n\nThis Technote specifically relates to the scenario where the cause is a defect (reference APAR PI54534) in early versions of Controller 10.2.1. \n\nThis defect is triggered when both of the following are true: * \n * from within the main Controller client (CCR.EXE)\n * for example they have clicked \"Company - Data Entry - Reported Values\" or they have clicked 'Reports - Run' or they have clicked the green 'X' button (the 'Controller Link' button, which launches Excel) \n * \n\n\nMore Information on IIS Application Pool recycles \nBy default, IIS application pools are set to recycle every 1740 minutes (29 hours): \n[/support/docview.wss?uid=swg21973433&aid=2] [/support/docview.wss?uid=swg21973433&aid=2] \n\nThis means that the time (when the error occurs) will vary by 5 hours each day. \nENVIRONMENT\nEarly versions of Controller 10.2.1 (10.2.5100.95 to 10.2.5120.82 inclusive).\n\n\n\nDIAGNOSING THE PROBLEM\nInside the Microsoft Event Viewer 'System Log', there typically will be an event similar to this one: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * A worker process with process id of '1940' serving application pool '.NET 2.0' has requested a recycle because the worker process reached its allowed processing time limit. \n\n\nTIP: If the above entries do not appear (rare), this may be because your application pool is not configured to log its recycle events. \n\n * Therefore, some customers may benefit from ticking all the available boxes (when configuring their application pool - see steps inside 'Solution') as follows:\n\n[/support/docview.wss?uid=swg21973433&aid=3] [/support/docview.wss?uid=swg21973433&aid=3] \n[This will ensure that the Event Viewer gets an event recorded when the application pool recycles in the future]. \nRESOLVING THE PROBLEM\nFix: \n\nUpgrade to Controller 10.2.1 FP3 (10.2.5130.56) or later. \n\n \n\nWorkaround: \n\nModify the Controller application pool settings so that it does not recycle during the time period when users are using the system. \n\n \n\nSteps: \n\nThe following steps are based on Windows 2012. The steps may need to be varied slightly if using a different operating system. \n\n1. Logon to the Controller application server \n\n2. Launch 'Internet Information Services (IIS) Manager' \n\n3. Locate the application pool that is being used by Controller \n\n * TIP: By default it is called '.NET 2.0':\n\n[/support/docview.wss?uid=swg21973433&aid=4] [/support/docview.wss?uid=swg21973433&aid=4] \n\n4. Right-click on the relevant application pool, and choose 'Recycling':\n[/support/docview.wss?uid=swg21973433&aid=5] [/support/docview.wss?uid=swg21973433&aid=5]\n\n5. Change the setting so that it does not conflict with your users.\n\nExample #1\nIn one real-life customer case, the customer never had any users working on the system overnight. Therefore the solution was to: \n\n * Untick \"Regular time intervals\" \n * Tick \"Specific times\", and set to: 01:00\n\n[/support/docview.wss?uid=swg21973433&aid=6] [/support/docview.wss?uid=swg21973433&aid=6] \n\nExample #2 \nIn a different real-life customer case, the customer always had users working on the system overnight. * However, the server was always regularly automatically rebooted once a week (every Sunday morning), so the system was never running for more than 7 days.\n\n\nTherefore the solution was to: * Modify the value \"Regular time intervals\" to be 10080\n\n[/support/docview.wss?uid=swg21973433&aid=7] [/support/docview.wss?uid=swg21973433&aid=7] \n\n(In other words, the application pool would recycle after 7 days continuous use. Effectively, this means that it would never recycle.) \n\n6. Click 'Next' - 'Finish' (to save changes). RELATED INFORMATION\n 1963432 - ** Troubleshooting ** Intermittent \"The Conne [http://www.ibm.com/support/docview.wss?uid=swg21963432]\nAPAR PI54534 - INTERMITTENT \"THE CONNECTIONSTRING PROPE [http://www-01.ibm.com/support/docview.wss?uid=swg1PI54534]",
+ "metadata": {
+ "sourceDocumentId": "swg21973433",
+ "date": "2017-11-10",
+ "productName": "Cognos Controller",
+ "productId": "SS9S6B",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21973433"
+ }
+ },
+ "swg21572340": {
+ "id": "swg21572340",
+ "content": "\n\n
\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n
\n
\n \n \n\n
Problem(Abstract)
\n User launches Controller. User successfully uses Controller functionality for some time. After a while, user receives error message.
The problem may appear to occur at random. It can potentially appear when performing any functionality.
Symptom
\n\n
\n The exact error will vary depending on the function being used. Below is an example when running a standard report:
\n
Standard Error
Number: 5
Source: FrangoDirect.AccountReportsD.CreateCodesRsCRN#System.Web.Services.frmAccountRep.CreateCodesRs
Description: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.ArgumentException: The ConnectionString property has not been initialized.
at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)
at ControllerServerCommon.RaiseErrSrv.RaiseError(String sUser, Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)
at FrMiscS.ConfigSet.ISet_SelectRecord(String sGuid, String sSelectCriterion, Array& vKey, String sUser, Int32 lLLocale)
at Cognos.Controller.SEC.ControllerConfigData.GetRow(String sGuid, String sTyp1, String sTyp2, String sAnvid)
at Cognos.Controller.SEC.ValidateSecurity..ctor(String sGuid, String sUser)
at Cognos.Controller.SEC.ParameterValidator.GetValidateSecurity()
at Cognos.Controller.SEC.ParameterValidator.IsMenuItemAllowed(String sMenus, String sReadWrite)
at Cognos.Controller.Proxy.SoapExtension.ServerExtension.RightsValueObject.IsAllowed(SoapMessage& message, String& Guid, String& User, Int32& iError)
at Cognos.Controller.Proxy.SoapExtension.ServerExtension.CheckAccessControl(SoapMessage& message)
at Cognos.Controller.Proxy.SoapExtension.ServerExtension.ProcessMessage(SoapMessage message)
at System.Web.Services.Protocols.SoapMessage.RunExtensions(SoapExtension[] extensions, Boolean throwOnException)
at System.Web.Services.Protocols.SoapServerProtocol.CreateServerInstance()
at System.Web.Services.Protocols.WebServiceHandler.Invoke()
at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)
at Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)
at Cognos.Controller.Forms.Form.frmAccountRep.CreateCodesRsCRN(XmlDocument& xmlDoc)
at Cognos.Controller.Forms.Form.frmAccountRep.IFormStandardReport_CreateReportData(IStandardReport& cIStandardReport)
\n
Cause
\n\n
This Technote specifically relates to the scenario where the cause is a defect (reference APAR PI54534) in early versions of Controller 10.2.1.\n
\n
This defect is triggered when \n both of the following are true: \n
\n More Information on IIS Application Pool recycles\n
By default, IIS application pools are set to recycle every 1740 minutes (29 hours):\n
\n![](\"/support/docview.wss?uid=swg21973433&aid=2\")
\n
\n
This means that the time (when the error occurs) will vary by 5 hours each day.\n
\n There are several different possible causes for a similar error.
\n- \n
- TIP: See separate IBM Technote #1963432 for more examples. \n
This Technote specifically relates to the scenario where the cause is a defect (reference APAR PI54534) in early versions of Controller 10.2.1.\n
\n
This defect is triggered when \n both of the following are true: \n
- \n (1) The user has previously launched some Excel-related function\n from within the main Controller client (CCR.EXE) \n
- for example they have clicked "Company - Data Entry - Reported Values" \n
- or they have clicked 'Reports - Run' \n
- or they have clicked the green 'X' button (the 'Controller Link' button, which launches Excel) \n
- \n
\n More Information on IIS Application Pool recycles\n
By default, IIS application pools are set to recycle every 1740 minutes (29 hours):\n
\n
\n
This means that the time (when the error occurs) will vary by 5 hours each day.\n
\n
Environment
\n\n
\n \n Early versions of Controller 10.2.1 (10.2.5100.95 to 10.2.5120.82 inclusive).
\nDiagnosing the problem
\n\n
\n \n![](\"/support/docview.wss?uid=swg21973433&aid=3\")
\n
[This will ensure that the Event Viewer gets an event recorded when the application pool recycles in the future].\n
\n Inside the Microsoft Event Viewer 'System Log', there typically will be an event similar to this one:
\n- \n
Log Name: System\n
Source: Microsoft-Windows-WAS\n
Date: 11/12/2015 14:17:12\n
Event ID: 5074\n
Task Category: None\n
Level: Information\n
Keywords: Classic\n
User: N/A\n
Computer: SERVERNAME\n
Description:\n
\n A worker process with process id of '1940' serving application pool '.NET 2.0' has requested a recycle because the worker process reached its allowed processing time limit. \n
\n \n
TIP: If the above entries do not appear (rare), this may be because your application pool is not configured to log its recycle events.
\n- \n
- Therefore, some customers may benefit from ticking all the available boxes (when configuring their application pool - see steps inside 'Solution') as follows: \n
[This will ensure that the Event Viewer gets an event recorded when the application pool recycles in the future].\n
\n
Resolving the problem
\n\n ![](\"/support/docview.wss?uid=swg21973433&aid=4\")
\n ![](\"/support/docview.wss?uid=swg21973433&aid=6\")
\n
\n
\n Example #2\n
In a different real-life customer case, the customer always had users working on the system overnight. \n
Therefore the solution was to: \n![](\"/support/docview.wss?uid=swg21973433&aid=7\")
\n
\n
(In other words, the application pool would recycle \n after 7 days continuous use. Effectively, this means that it would never recycle.)\n
\n
6. Click 'Next' - 'Finish' (to save changes).\n
\n Fix:
\nUpgrade to Controller 10.2.1 FP3 (10.2.5130.56) or later.
\n\n
Workaround:
\nModify the Controller application pool settings so that it does not recycle during the time period when users are using the system.
\n\n
Steps:
\nThe following steps are based on Windows 2012. The steps may need to be varied slightly if using a different operating system.
\n1. Logon to the Controller application server
\n2. Launch 'Internet Information Services (IIS) Manager'
\n3. Locate the application pool that is being used by Controller
\n- \n
- TIP: By default it is called '.NET 2.0': \n
\n
4. Right-click on the relevant application pool, and choose 'Recycling':
5. Change the setting so that it does not conflict with your users.
Example #1
In one real-life customer case, the customer never had any users working on the system overnight. Therefore the solution was to:
- \n
- Untick "Regular time intervals" \n
- Tick "Specific times", and set to: 01:00 \n
\n
\n Example #2\n
In a different real-life customer case, the customer always had users working on the system overnight. \n
- \n
- However, the server was always regularly automatically rebooted once a week (every Sunday morning), so the system was never running for more than 7 days. \n
Therefore the solution was to: \n
- \n
- Modify the value "Regular time intervals" to be 10080 \n
\n
(In other words, the application pool would recycle \n after 7 days continuous use. Effectively, this means that it would never recycle.)\n
\n
6. Click 'Next' - 'Finish' (to save changes).\n
Related information
\n 1963432 - ** Troubleshooting ** Intermittent "The Conne
APAR PI54534 - INTERMITTENT "THE CONNECTIONSTRING PROPE
\n \n
\n \n
\n\n\n\n
\nrelease notice; downloads; Gateway for Amdocs CRM (nco-g-amdocscrm-2_0) for Solaris English; omnibus-solaris2-gateway-nco-g-amdocscrm-2_0.tar.gz
\n\n\n \n \n
\nNews
\n \n
\n
\n \n
Abstract
\nA new version of the Netcool/OMNIbus Gateway for Amdocs CRM (nco-g-amdocscrm-2_0) for Solaris English will be available to download from September 11, 2014.
\nContent
\n\n
\n \n
The Netcool/OMNIbus V8.1 version of this gateway has been repackaged to support additional Operating Systems. The gateway now supports the following Operating Systems:
\nSolaris
\nYou can download the installation package from the IBM Passport Advantage website:
www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm
You can access the latest version of the guide written for this gateway on the IBM Knowledge Center:
\n \nNetcool/OMNIbus V8.1
\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CN1JBEN
\nNetcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0
\nIf you are running Netcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.
\n\n \n \n
\n
\n | Part number | \nOperating System | \n
| CI4P2EN | \nSolaris | \n
Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.
\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:
\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html
\n \n\n
\n \n
\n
\n \n \n",
+ "title": "IBM Netcool/OMNIbus Integrations Release Notice - Netcool/OMNIbus Gateway for Amdocs CRM (nco-g-amdocscrm-2_0) for Solaris English - United States",
+ "text": "release notice; downloads; Gateway for Amdocs CRM (nco-g-amdocscrm-2_0) for Solaris English; omnibus-solaris2-gateway-nco-g-amdocscrm-2_0.tar.gz NEWS\n\nABSTRACT\n A new version of the Netcool/OMNIbus Gateway for Amdocs CRM (nco-g-amdocscrm-2_0) for Solaris English will be available to download from September 11, 2014. \n\nCONTENT\n \n\nThe Netcool/OMNIbus V8.1 version of this gateway has been repackaged to support additional Operating Systems. The gateway now supports the following Operating Systems:\n\nSolaris\n\nYou can download the installation package from the IBM Passport Advantage website: \nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nYou can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww-01.ibm.com/support/knowledgecenter/#!/SSSHTQ/omnibus/gateways/amdocstal/wip/concept/amdocsgw_intro.html [http://www-01.ibm.com/support/knowledgecenter/#!/SSSHTQ/omnibus/gateways/amdocstal/wip/concept/amdocsgw_intro.html]\n\nNetcool/OMNIbus V8.1\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CN1JBEN\n\nNetcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0\n\nIf you are running Netcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CI4P2EN Solaris Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]",
+ "metadata": {
+ "sourceDocumentId": "swg21572340",
+ "date": "2014-09-08",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21572340"
+ }
+ },
+ "swg1PM63850": {
+ "id": "swg1PM63850",
+ "content": "
\n
",
+ "title": "IBM PM63850: UNABLE TO SAVE REPORT ORA-01002 FETCH OUT OF SEQUENCE OCCURS - United States",
+ "text": " FIXES ARE AVAILABLE\n7.1.0.3-TIV-ITCAMAD-IF0001: ITCAM for Application Diagnostics V7.1 FP3 IF1 [http://www-01.ibm.com/support/docview.wss?uid=swg24032985]\n7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF4 [http://www-01.ibm.com/support/docview.wss?uid=swg24033735]\n7.1.0.3-TIV-ITCAMAD-IF0005: ITCAM for Application Diagnostics V7.1 FP3 IF5 [http://www-01.ibm.com/support/docview.wss?uid=swg24033938]\n7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF6 [http://www-01.ibm.com/support/docview.wss?uid=swg24034668]\n7.1.0.3-TIV-ITCAMAD-IF0008: ITCAM for Application Diagnostics V7.1 FP3 IF8 [http://www-01.ibm.com/support/docview.wss?uid=swg24037994]\n7.1.0-TIV-ITCAMAD-FP0004: ITCAM for Application Diagnostics V7.1 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24041705]\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 * Users Affected:\n \n ITCAM for WebSphere V6.1, Managing Server\n Customers using ITCAM database on Oracle, configured with Type 2\n Database driver on WebSphere Application Server.\n \n Problem Description:\n \n When saving a report through ITCAM VE console, when customer\n select 'Save' button on 'Save Report' panel, following error is\n displayed, and the report does\n \n not get saved:\n \"CYNVE0583E: An error occurred while saving the report\"\n \n SystemErr.log shows following exception when the trend report is\n being\n saved:\n \n [11/22/11 15:16:35:127 CST] 000005f5 SystemErr R\n java.sql.SQLException: ORA-01002: fetch out of sequence\n \n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError\n .java:112)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:6\n 76)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:6\n 02)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.T2CPreparedStatement.doDefineFetch(T2CPrepare\n dStateme\n nt.java:849)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.T2CPreparedStatement.executeForRows(T2CPrepar\n edStatem\n ent.java:768)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleSt\n atement.\n java:1072)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleSt\n atement.\n java:1154)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.OraclePreparedStatement.executeInternal(Oracl\n ePrepare\n dStatement.java:3370)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePr\n eparedSt\n atement.java:3415)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteQuer\n y(WSJdbc\n PreparedStatement.java:1033)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(W\n SJdbcPre\n paredStatement.java:683)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.cyanea.common.database.DbPreparedStatement.executeQuery(DbPr\n eparedSt\n atement.java:330)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.cyanea.common.database.SequenceGen.fetchNextSequenceBlock(Se\n quenceGe\n n.java:189)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.cyanea.common.database.SequenceGen.getNextKey(SequenceGen.ja\n va:142)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.cyanea.ve.report.ReportHelper.saveNew(ReportHelper.java:426)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.cyanea.ve.report.ReportTrendServlet.doPost(ReportTrendServle\n t.java:2\n 78)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.cyanea.ve.report.ReportTrendServlet.doGet(ReportTrendServlet\n .java:73\n )\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n ...\n ...\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand\n ler.java\n :751)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)\n [11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n ***********************\n * USERS AFFECTED: ITCAM for Application Diagnostics Managing\n Server UI (MSVE) Saved Report feature.\n \n A user may not be able to save a report if an Oracle database is\n used.\n \n \n ****************************************************************\n ***********************\n * PROBLEM DESCRIPTION: A user may not be able to save a report\n if an Oracle database is used.\n \n ****************************************************************\n ***********************\n * RECOMMENDATION: The fix is in ITCAM for Application\n Diagnostics 7.1 FP3 IF1 (7.1.0.3.1). Apply ITCAM for AD\n 7.1.0.3.1 when it is available.\n ****************************************************************\n ***********************\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PM63850\n \n \n * REPORTED COMPONENT NAME\n ITCAM WAS MGING\n \n \n * REPORTED COMPONENT ID\n 5724L62MS\n \n \n * REPORTED RELEASE\n 610\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 2012-05-03\n \n \n * CLOSED DATE\n 2012-06-29\n \n \n * LAST MODIFIED DATE\n 2012-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\n * R610 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1PM63850",
+ "date": "2012-06-29",
+ "productName": "Tivoli Composite Application Manager for WebSphere",
+ "productId": "SS3PGL",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PM63850"
+ }
+ },
+ "swg1HD62905": {
+ "id": "swg1HD62905",
+ "content": "\n\n
\n
\n
\n \n
\n \nFixes are available
\n \n
\n7.1.0.3-TIV-ITCAMAD-IF0001: ITCAM for Application Diagnostics V7.1 FP3 IF1
7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF4
7.1.0.3-TIV-ITCAMAD-IF0005: ITCAM for Application Diagnostics V7.1 FP3 IF5
7.1.0.3-TIV-ITCAMAD-IF0004: ITCAM for Application Diagnostics V7.1 FP3 IF6
7.1.0.3-TIV-ITCAMAD-IF0008: ITCAM for Application Diagnostics V7.1 FP3 IF8
7.1.0-TIV-ITCAMAD-FP0004: ITCAM for Application Diagnostics V7.1 Fix Pack 4
\n
\n \n
\nAPAR status
\n- \n
Closed as fixed if next.
\n
Error description
\n- \n
- \n \n
Users Affected:\n\nITCAM for WebSphere V6.1, Managing Server\nCustomers using ITCAM database on Oracle, configured with Type 2\nDatabase driver on WebSphere Application Server.\n\nProblem Description:\n\nWhen saving a report through ITCAM VE console, when customer\nselect 'Save' button on 'Save Report' panel, following error is\ndisplayed, and the report does\n\nnot get saved:\n "CYNVE0583E: An error occurred while saving the report"\n\nSystemErr.log shows following exception when the trend report is\nbeing\nsaved:\n\n[11/22/11 15:16:35:127 CST] 000005f5 SystemErr R\njava.sql.SQLException: ORA-01002: fetch out of sequence\n\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError\n.java:112)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:6\n76)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:6\n02)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.T2CPreparedStatement.doDefineFetch(T2CPrepare\ndStateme\nnt.java:849)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.T2CPreparedStatement.executeForRows(T2CPrepar\nedStatem\nent.java:768)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleSt\natement.\njava:1072)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleSt\natement.\njava:1154)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.OraclePreparedStatement.executeInternal(Oracl\nePrepare\ndStatement.java:3370)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\noracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePr\neparedSt\natement.java:3415)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteQuer\ny(WSJdbc\nPreparedStatement.java:1033)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(W\nSJdbcPre\nparedStatement.java:683)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.cyanea.common.database.DbPreparedStatement.executeQuery(DbPr\neparedSt\natement.java:330)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.cyanea.common.database.SequenceGen.fetchNextSequenceBlock(Se\nquenceGe\nn.java:189)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.cyanea.common.database.SequenceGen.getNextKey(SequenceGen.ja\nva:142)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.cyanea.ve.report.ReportHelper.saveNew(ReportHelper.java:426)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.cyanea.ve.report.ReportTrendServlet.doPost(ReportTrendServle\nt.java:2\n78)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.cyanea.ve.report.ReportTrendServlet.doGet(ReportTrendServlet\n.java:73\n)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\n...\n...\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand\nler.java\n:751)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)\n[11/22/11 15:16:35:128 CST] 000005f5 SystemErr R at\ncom.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
****************************************************************\n***********************\n* USERS AFFECTED: ITCAM for Application Diagnostics Managing\nServer UI (MSVE) Saved Report feature.\n\nA user may not be able to save a report if an Oracle database is\nused.\n\n\n****************************************************************\n***********************\n* PROBLEM DESCRIPTION: A user may not be able to save a report\nif an Oracle database is used.\n\n****************************************************************\n***********************\n* RECOMMENDATION: The fix is in ITCAM for Application\nDiagnostics 7.1 FP3 IF1 (7.1.0.3.1). Apply ITCAM for AD\n7.1.0.3.1 when it is available.\n****************************************************************\n***********************\n
\n \n
Problem conclusion
\n- \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PM63850
\n Reported component name
ITCAM WAS MGING
\n Reported component ID
5724L62MS
\n Reported release
610
\n Status
CLOSED FIN
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2012-05-03
\n Closed date
2012-06-29
\n Last modified date
2012-06-29
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
R610 PSY
UP
\n
\n
\n
\n
",
+ "title": "IBM HD62905: NEED DOCUMENTATION ON CATCSBPROXY LOG MESSAGES - United States",
+ "text": " SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PERMANENT RESTRICTION.\n \n \n \n\nERROR DESCRIPTION\n * NEED DOCUMENTATION ON CATCSBPROXY LOG\n MESSAGES\n .\n Scenario:\n We have implemented a gateway and proxy using\n CATCsbProxy.\n We receive messages in the log file and have not\n documentation as to what they mean and if we\n should be taking corrective action.\n One particular error was seen during a loss of\n service to 70 of our users.\n We need some documentation of what the following\n message mean and what we should be doing to\n eliminate them if possible.\n .\n 1. Write error on intranet socket of\n proxy_server:proxy_port: 03719-0000001034\n (Broken pipe)\n 2. Write command data failed on\n proxy_server:proxy_port: 05690-0000000000 (\n Socket is not connected ) socket 5\n 3. Write command data failed on\n proxy_server:proxy_port: 05690-0000000000 (\n Broken pipe ) socket 5\n 4. Open connection on proxy_server:proxy_port\n failed (Invalid argument)\n .\n It would be more helpful if error messages and\n suggestions for resolution were in the standard\n documentation for CATCsbProxy.\n These are the same type of messages that we\n have seen since R15 through R17.\n .\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * NEED DOCUMENTATION ON CATCSBPROXY LOG MESSAGES\n NEED DOCUMENTATION ON CATCSBPROXY LOG\n MESSAGES\n .\n Scenario:\n We have implemented a gateway and proxy using\n CATCsbProxy.\n We receive messages in the log file and have not\n documentation as to what they mean and if we\n should be taking corrective action.\n One particular error was seen during a loss of\n service to 70 of our users.\n We need some documentation of what the following\n message mean and what we should be doing to\n eliminate them if possible.\n .\n 1. Write error on intranet socket of\n proxy_server:proxy_port: 03719-0000001034\n (Broken pipe)\n 2. Write command data failed on\n proxy_server:proxy_port: 05690-0000000000 (\n Socket is not connected ) socket 5\n 3. Write command data failed on\n proxy_server:proxy_port: 05690-0000000000 (\n Broken pipe ) socket 5\n 4. Open connection on proxy_server:proxy_port\n failed (Invalid argument)\n .\n It would be more helpful if error messages and\n suggestions for resolution were in the standard\n documentation for CATCsbProxy.\n These are the same type of messages that we\n have seen since R15 through R17.\n .\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * THIS PROBLEM IS PERMANENT RESTRICTION IN\n ENOVIA\n .\n Restriction Explanation:\n Log messages quoted are very low level :\n CATCsbProxy relies on sockets, when\n these sockets are disconnected, there are write\n messages poping about this event. These\n messages are close to C language system calls and\n are intended for debug purpose by DS people in\n charge of the component. Since the PMR has no\n attached log file, we cannot either diagnostic a\n problem by inspecting such events occurences over\n time ; and even with a log, we'd need to know what\n kind of scenario led to such traces.\n .\n By-Pass\n While not documented and low-level, log messages\n are self-explanatory for network aware people: if\n there is an increase of messages related to sockets\n disconnection, then one such investigate what in\n the WAN between CATCsbProxy gateway and\n CATCsbProxy untunnel might cause so many\n disconnections. While the tunnel is made to support\n WAN conditions, too frequent disconnections lead to\n costly re-connection of socket - that's close to what\n happen with HTTP 1.0 proxies that do not quite\n support keep-alive.\n .\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n HD62905\n \n \n * REPORTED COMPONENT NAME\n ENOVIA V5 VPM A\n \n \n * REPORTED COMPONENT ID\n 569101400\n \n \n * REPORTED RELEASE\n 517\n \n \n * STATUS\n CLOSED PRS\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 2007-03-28\n \n \n * CLOSED DATE\n 2007-04-10\n \n \n * LAST MODIFIED DATE\n 2007-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\nAPPLICABLE COMPONENT LEVELS",
+ "metadata": {
+ "sourceDocumentId": "swg1HD62905",
+ "date": "2007-04-10",
+ "productName": "ENOVIA V5 VPM Discipline",
+ "productId": "SS7P2G",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1HD62905"
+ }
+ },
+ "swg27024037": {
+ "id": "swg27024037",
+ "content": "\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as Permanent restriction.
\n
Error description
\n- \n
- \n \n
NEED DOCUMENTATION ON CATCSBPROXY LOG\nMESSAGES\n.\nScenario:\nWe have implemented a gateway and proxy using\nCATCsbProxy.\nWe receive messages in the log file and have not\ndocumentation as to what they mean and if we\nshould be taking corrective action.\nOne particular error was seen during a loss of\nservice to 70 of our users.\nWe need some documentation of what the following\nmessage mean and what we should be doing to\neliminate them if possible.\n.\n1. Write error on intranet socket of\nproxy_server:proxy_port: 03719-0000001034\n(Broken pipe)\n2. Write command data failed on\nproxy_server:proxy_port: 05690-0000000000 (\nSocket is not connected ) socket 5\n3. Write command data failed on\nproxy_server:proxy_port: 05690-0000000000 (\nBroken pipe ) socket 5\n4. Open connection on proxy_server:proxy_port\nfailed (Invalid argument)\n.\nIt would be more helpful if error messages and\nsuggestions for resolution were in the standard\ndocumentation for CATCsbProxy.\nThese are the same type of messages that we\nhave seen since R15 through R17.\n.\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
NEED DOCUMENTATION ON CATCSBPROXY LOG MESSAGES\nNEED DOCUMENTATION ON CATCSBPROXY LOG\nMESSAGES\n.\nScenario:\nWe have implemented a gateway and proxy using\nCATCsbProxy.\nWe receive messages in the log file and have not\ndocumentation as to what they mean and if we\nshould be taking corrective action.\nOne particular error was seen during a loss of\nservice to 70 of our users.\nWe need some documentation of what the following\nmessage mean and what we should be doing to\neliminate them if possible.\n.\n1. Write error on intranet socket of\nproxy_server:proxy_port: 03719-0000001034\n(Broken pipe)\n2. Write command data failed on\nproxy_server:proxy_port: 05690-0000000000 (\nSocket is not connected ) socket 5\n3. Write command data failed on\nproxy_server:proxy_port: 05690-0000000000 (\nBroken pipe ) socket 5\n4. Open connection on proxy_server:proxy_port\nfailed (Invalid argument)\n.\nIt would be more helpful if error messages and\nsuggestions for resolution were in the standard\ndocumentation for CATCsbProxy.\nThese are the same type of messages that we\nhave seen since R15 through R17.\n.\n
\n \n
Problem conclusion
\n- \n
- \n \n
THIS PROBLEM IS PERMANENT RESTRICTION IN\nENOVIA\n.\nRestriction Explanation:\nLog messages quoted are very low level :\nCATCsbProxy relies on sockets, when\nthese sockets are disconnected, there are write\nmessages poping about this event. These\nmessages are close to C language system calls and\nare intended for debug purpose by DS people in\ncharge of the component. Since the PMR has no\nattached log file, we cannot either diagnostic a\nproblem by inspecting such events occurences over\ntime ; and even with a log, we'd need to know what\nkind of scenario led to such traces.\n.\nBy-Pass\nWhile not documented and low-level, log messages\nare self-explanatory for network aware people: if\nthere is an increase of messages related to sockets\ndisconnection, then one such investigate what in\nthe WAN between CATCsbProxy gateway and\nCATCsbProxy untunnel might cause so many\ndisconnections. While the tunnel is made to support\nWAN conditions, too frequent disconnections lead to\ncostly re-connection of socket - that's close to what\nhappen with HTTP 1.0 proxies that do not quite\nsupport keep-alive.\n.\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
HD62905
\n Reported component name
ENOVIA V5 VPM A
\n Reported component ID
569101400
\n Reported release
517
\n Status
CLOSED PRS
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2007-03-28
\n Closed date
2007-04-10
\n Last modified date
2007-04-10
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
\n
\n
\n
\n\n\n\n
\nwste_webcast; WSTE; Support Technical Exchange; education; presentation; webcast; STEwebcastDocument; Open Mic; Ask The Experts; installation
\n\n\n \n \n
\nWebcast
\n \n
\n
\n
\n \n
Abstract
\nThis Ask The Experts Session covers common questions and issues in the installation of WebSphere Application Server V8 and the included packages using installation manager. The session also answers questions regarding WebSphere Application Server V7 and V6.1, although the main focus is on the latest release.
\nContent
\n\n
\n
\n
\n Ask the Experts session\n
15 March 2012 - 11:00 a.m. - 12:00 p.m. EDT\n
\n
\n
Panel of Experts:\n
\n
\n
\n Ask the Experts sessions are conducted in a question and answer format. The table below provides a time index (minutes:seconds) to the recording and describes the questions or topics discussed. You can fast forward to any question using the time index, a table containing the panel of experts is also included.
To play or download the audio of this Ask the Experts session, see the Audio Section of this document.
See the Related Information Section of this document for a list of documents referenced during the presentation.
\n
\n
\n Ask the Experts session\n
15 March 2012 - 11:00 a.m. - 12:00 p.m. EDT\n
\n
\n
\n \n \n
\n
\n | Time | \nQuestions asked | \n
| 00:00 | \nSilence | \n
| 00:00 | \nGeneral introduction | \n
| 03:54 | \nTechnical introduction | \n
| 05:00 | \nI have installed a feature pack on WebSphere Application Server V8, what additional steps are required for my profile to use this? | \n
| 08:49 | \nCan WebSphere Application Server V8 be installed without Installation Manager? Once installed can I use Update Installer to apply fixpack? | \n
| 09:52 | \nMy production system cannot access www.ibm.com, how can I update my repositories in the Installation Manager? Do I need to copy repositories across all servers? | \n
| 12:56 | \nCan I install WebSphere Application Server V8 remotely? | \n
| 13:48 | \nI used to install silently using Update Installer in WebSphere Application Server V7, can I install silently using Installation Manager in V8? | \n
| 16:28 | \nIf there a reason why the Installation Manager is now being utilized over the Update Installer? | \n
| 19:13 | \nWith WebSphere Application Server V6.1 reaching the end of support in September I was wondering if there will be any kind of support beyond that point? | \n
| 21:30 | \nHow would I upgrade directly from WebSphere Application Server V6.1 to V8? | \n
| 23:35 | \nHow should the permissions be set when do perform an installation on a Linux or Unix box? | \n
| 26:40 | \nWhat is the difference between a local repository and a shared repository? How should I set up my repository if I have separate domains that are isolated? | \n
| 30:58 | \nWhat are the different options I have when migrating from WebSphere Application Server V6.1 to V8 (i.e. building from scratch)? | \n
| 32:30 | \nIs there any documentation on using the Installation Manager on WebSphere Application Server V8 which also shows the differences between this new installer vs the old installer? | \n
| 35:11 | \nI am currently using Jyphon and some Windows batch scripts to perform my install and post-installation configurations. Are there any significant changes in WebSphere Application Server V8 that will prevent these scripts from working? | \n
| 38:11 | \nI use aliases in all my installations and never any actual server names in any of the installation methods. Can you comment on this technique, and will this continue to work in WebSphere Application Server V8? | \n
| 41:43 | \nSome of my environments are secured by firewall, and I use secure copy to copy components of the repository to each target server as I need them. I then use my basic local repository technique when I do perform my install or update. What this means is that each server must have adequate space for repository. I'm currently considering a shared repository within each secured environment - is it expected that the size of the repository will increase significantly? | \n
| 44:53 | \nDo you have any comments on us running a single cluster that span across two data centers and two different states? | \n
| 47:35 | \nWe are running a BPM server on top of WAS V7.5.1 and we have about 12 cells in our environment. This makes it difficult for us to push changes to these cells, and what was suggested to us was the Rational Automation Framework. What are your stands on this as it relates to installing and maintaining all these different levels across different cells? | \n
| 50:17 | \nWe have a number of applications in a mix and match environment consisting of WAS V6.1 and V7.0. Is there any migration script we can run or migration path we can follow if we decide to move to WAS V8? | \n
| 53:38 | \nUsing Installation Manager can we record a custom WebSphere response file from the command line without using the graphical interface? | \n
| 57:35 | \nCan the Installation Manager be used on profiles as well? | \n
| 59:38 | \nWe currently have WAS V7.0 with several Fixpacks on it. Our process of installation is very automated with scripts. We also customize our profiles with Jypthon and other scripts. Will my old scripts continue to work after migrating to WAS V8? | \n
| 62:26 | \nIs there a way we can add an existing JVM to a new cluster group? | \n
| 64:30 | \nIs it possible to migrate a profile from one cluster group to another cluster group? | \n
| 66:19 | \nWhen installing WebSphere plug-ins I've noticed that the default location is now different than the default location in the previous version, which was in the web server directory. Is there any reason why the default location has changed, and is there a way we can change it to be installed under the HTTP server directory, similar to the previous version? | \n
| 69:12 | \nClosing remarks | \n
| 70:44 | \nEnd of Call | \n
Panel of Experts:\n
\n \n \n
\n
\n | Preston Law | \nWebSphere Application Server Level 2 Support | \n
| Joe Mertzlufft | \nWebSphere Application Server Level 2 Support | \n
| Vishavpal Shergill | \nWebSphere Application Server Level 2 Support | \n
| Mike Hill | \nWebSphere Application Server Level 2 Support | \n
| Gary Vacek | \nWebSphere Application Server Level 2 Support | \n
\n
\n
Presentation
\n\n
\n ![\"\"](\"http://www.ibm.com/i/v16/icons/weblecture.gif\"){kind=icon}
WSTE-03152012-AskTheExperts-InstallationWebSphereApplicationServer-Law.pdf
Get Adobe Reader to view PDF
Group Chat Transcript
The transcript of the group chat area for this Ask the Experts session is attached below. Throughout the presentation replay, you may hear the presenters posting additional resources and links to the group chat area. Please refer to the transcript below for these information:
WSTE-03152012-AskTheExperts-InstallationWebSphereApplicationServer-Law-GroupChat-Transcript.txt
Tips: For best viewing, right-click and select Save As to store the transcript on your local computer, and then open the transcript with a text reader.
\n
Audio
\n\n
\n \n ![\"\"](\"http://www.ibm.com/i/v16/icons/aud.gif\"){kind=icon}
To replay the recording of this 70 minutes conference call, click on Download Audio (8.0MB - audio in MP3 format). Right-click and select Save As to store the file on your local computer for later playback. Remember that you can fast forward to any question using the time index.
Related information
\n WebSphere Support Technical Exchange
Time Zone Converter
Augmentation rules and limitations for feature packs on
Installation Manager InfoCenter
WebSphere Application Server InfoCenter
Migrating product configurations with migration tools
How to download WebSphere Application Server V8.0 from
Installing the product
Command-line arguments for imcl
Managing Repositories for Installation of WebSphere App
Installing the product and additional software
Preparing the operating system for product installation
MustGather: Windows Services (WASService.exe) does not
Migrating cells across operating systems using the comm
Repository preferences
\n \n
\n \n
\n \n
\n \n \n",
+ "title": "IBM Ask the Experts Replay: Installation in WebSphere Application Server - United States",
+ "text": "wste_webcast; WSTE; Support Technical Exchange; education; presentation; webcast; STEwebcastDocument; Open Mic; Ask The Experts; installation WEBCAST\n\nABSTRACT\n This Ask The Experts Session covers common questions and issues in the installation of WebSphere Application Server V8 and the included packages using installation manager. The session also answers questions regarding WebSphere Application Server V7 and V6.1, although the main focus is on the latest release. \n\nCONTENT\nAsk the Experts sessions are conducted in a question and answer format. The table below provides a time index (minutes:seconds) to the recording and describes the questions or topics discussed. You can fast forward to any question using the time index, a table containing the panel of experts is also included.\n\n\nTo play or download the audio of this Ask the Experts session, see the Audio Section of this document.\n\nSee the Related Information Section of this document for a list of documents referenced during the presentation.\n\n\n\n\n\n\n\n\nAsk the Experts session \n15 March 2012 - 11:00 a.m. - 12:00 p.m. EDT \n\nTime Questions asked 00:00 Silence 00:00 General introduction 03:54 Technical introduction 05:00 I have installed a feature pack on WebSphere Application Server V8, what additional steps are required for my profile to use this? 08:49 Can WebSphere Application Server V8 be installed without Installation Manager? Once installed can I use Update Installer to apply fixpack? 09:52 My production system cannot access www.ibm.com, how can I update my repositories in the Installation Manager? Do I need to copy repositories across all servers? 12:56 Can I install WebSphere Application Server V8 remotely? 13:48 I used to install silently using Update Installer in WebSphere Application Server V7, can I install silently using Installation Manager in V8? 16:28 If there a reason why the Installation Manager is now being utilized over the Update Installer? 19:13 With WebSphere Application Server V6.1 reaching the end of support in September I was wondering if there will be any kind of support beyond that point? 21:30 How would I upgrade directly from WebSphere Application Server V6.1 to V8? 23:35 How should the permissions be set when do perform an installation on a Linux or Unix box? 26:40 What is the difference between a local repository and a shared repository? How should I set up my repository if I have separate domains that are isolated? 30:58 What are the different options I have when migrating from WebSphere Application Server V6.1 to V8 (i.e. building from scratch)? 32:30 Is there any documentation on using the Installation Manager on WebSphere Application Server V8 which also shows the differences between this new installer vs the old installer? 35:11 I am currently using Jyphon and some Windows batch scripts to perform my install and post-installation configurations. Are there any significant changes in WebSphere Application Server V8 that will prevent these scripts from working? 38:11 I use aliases in all my installations and never any actual server names in any of the installation methods. Can you comment on this technique, and will this continue to work in WebSphere Application Server V8? 41:43 Some of my environments are secured by firewall, and I use secure copy to copy components of the repository to each target server as I need them. I then use my basic local repository technique when I do perform my install or update. What this means is that each server must have adequate space for repository. I'm currently considering a shared repository within each secured environment - is it expected that the size of the repository will increase significantly? 44:53 Do you have any comments on us running a single cluster that span across two data centers and two different states? 47:35 We are running a BPM server on top of WAS V7.5.1 and we have about 12 cells in our environment. This makes it difficult for us to push changes to these cells, and what was suggested to us was the Rational Automation Framework. What are your stands on this as it relates to installing and maintaining all these different levels across different cells? 50:17 We have a number of applications in a mix and match environment consisting of WAS V6.1 and V7.0. Is there any migration script we can run or migration path we can follow if we decide to move to WAS V8? 53:38 Using Installation Manager can we record a custom WebSphere response file from the command line without using the graphical interface? 57:35 Can the Installation Manager be used on profiles as well? 59:38 We currently have WAS V7.0 with several Fixpacks on it. Our process of installation is very automated with scripts. We also customize our profiles with Jypthon and other scripts. Will my old scripts continue to work after migrating to WAS V8? 62:26 Is there a way we can add an existing JVM to a new cluster group? 64:30 Is it possible to migrate a profile from one cluster group to another cluster group? 66:19 When installing WebSphere plug-ins I've noticed that the default location is now different than the default location in the previous version, which was in the web server directory. Is there any reason why the default location has changed, and is there a way we can change it to be installed under the HTTP server directory, similar to the previous version? 69:12 Closing remarks 70:44 End of Call \nPanel of Experts: Preston Law WebSphere Application Server Level 2 Support Joe Mertzlufft WebSphere Application Server Level 2 Support Vishavpal Shergill WebSphere Application Server Level 2 Support Mike Hill WebSphere Application Server Level 2 Support Gary Vacek WebSphere Application Server Level 2 Support \n\nPRESENTATION\n[http://www.ibm.com/i/v16/icons/weblecture.gif]WSTE-03152012-AskTheExperts-InstallationWebSphereApplicationServer-Law.pdf [/support/docview.wss?uid=swg27024037&aid=2]WSTE-03152012-AskTheExperts-InstallationWebSphereApplicationServer-Law.pdf [/support/docview.wss?uid=swg27024037&aid=1]\n\nGet Adobe Reader [http://www.adobe.com/products/acrobat/readstep2.html] to view PDF\n\n\n\n\nGroup Chat Transcript\n\nThe transcript of the group chat area for this Ask the Experts session is attached below. Throughout the presentation replay, you may hear the presenters posting additional resources and links to the group chat area. Please refer to the transcript below for these information:\n\nWSTE-03152012-AskTheExperts-InstallationWebSphereApplicationServer-Law-GroupChat-Transcript.txt [/support/docview.wss?uid=swg27024037&aid=4]WSTE-03152012-AskTheExperts-InstallationWebSphereApplicationServer-Law-GroupChat-Transcript.txt [/support/docview.wss?uid=swg27024037&aid=3]\n\nTips: For best viewing, right-click and select Save As to store the transcript on your local computer, and then open the transcript with a text reader. \n\n\nAUDIO\n[http://www.ibm.com/i/v16/icons/aud.gif]To replay the recording of this 70 minutes conference call, click on Download Audio [http://public.dhe.ibm.com/software/websphere/techexchange/Mar-15-2012-Law.mp3] (8.0MB - audio in MP3 format). Right-click and select Save As to store the file on your local computer for later playback. Remember that you can fast forward to any question using the time index.\n\n\n\nRELATED INFORMATION\n WebSphere Support Technical Exchange [http://www.ibm.com/software/websphere/webcast]\nTime Zone Converter [http://www.timeanddate.com/worldclock/converter.html]\nAugmentation rules and limitations for feature packs on [http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.soafep.multiplatform.doc%2Finfo%2Fae%2Fae%2Frpro_augment.html]\nInstallation Manager InfoCenter [http://publib.boulder.ibm.com/infocenter/install/v1r2/index.jsp?topic=/com.ibm.cic.agent.ui.doc/topics/t_modify_install_pkg.html]\nWebSphere Application Server InfoCenter [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-dist&topic=tagt_hostname]\nMigrating product configurations with migration tools [http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/com.ibm.websphere.migration.nd.doc/info/ae/ae/tmig_tools.html]\nHow to download WebSphere Application Server V8.0 from [http://www-01.ibm.com/support/docview.wss?uid=swg27021159&wv=1]\nInstalling the product [http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.installation.nd.doc%2Finfo%2Fae%2Fae%2Ftins_install.html]\nCommand-line arguments for imcl [http://publib.boulder.ibm.com/infocenter/install/v1r5/index.jsp?topic=%2Fcom.ibm.cic.commandline.doc%2Ftopics%2Fr_tools_imcl.html]\nManaging Repositories for Installation of WebSphere App [http://www-01.ibm.com/support/docview.wss?uid=swg27023967]\nInstalling the product and additional software [http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_install.html]\nPreparing the operating system for product installation [http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_prepare.html]\nMustGather: Windows Services (WASService.exe) does not [http://www-01.ibm.com/support/docview.wss?uid=swg21195440]\nMigrating cells across operating systems using the comm [http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.migration.nd.doc/info/ae/ae/tmig_migrate_remote_commandline.html ]\nRepository preferences [http://publib.boulder.ibm.com/infocenter/install/v1r2/topic/com.ibm.cic.agent.ui.doc/topics/t_specifying_repository_locations.html]",
+ "metadata": {
+ "sourceDocumentId": "swg27024037",
+ "date": "2014-01-06",
+ "productName": "WebSphere Application Server",
+ "productId": "SSEQTP",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg27024037"
+ }
+ },
+ "swg1IV81778": {
+ "id": "swg1IV81778",
+ "content": "
\n
",
+ "title": "IBM IV81778: THE RESPONDED NUMBER OF NODES DOES NOT MATCH THE NUMBER OF NODES IN THE COLLECTION WHEN THERE ARE NEW NODES ADDED - United States",
+ "text": " 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 * The responded number of nodes does not match the number of nodes\n in the\n collection when there is/are new nodes added into the\n collection. There\n is no condition been set on the collection.\n \n Symptoms:\n \n 1. Open the 2 Event Viewers. One with \"Un-acknowledged\" filter\n and the\n other one \"Acknowledged\" filter.\n 2. Acknowledge a node in \"Un-acknowledged\" Event Viewer. This\n will\n acknowledged the node and the node suppose to be added into\n \"Acknowledged\" Event Viewer on next refresh.\n 3. On next refresh on \"Acknowledged\" Event Viewer, the total\n number of\n rows remain same, however the Severity summary did updated\n correctly.\n Ref: all_acknowledged.png\n \n \n \n Investigation:\n \n 1. The issue only start to occur after applied DASH Version:\n 3.1.2.1\n Build Number: cf011242.02, 201508201935 (201511301851) Build\n Date:\n 10/17/12, 8/20/15.\n 2. The behavior is working good on DASH Version: 3.1.2.1 Build\n Number:\n cf011242.02, 201508201935 Build Date: 10/17/12, 8/20/15\n 3. The \"filteredRows\" and \"numRows\" was returned as 10 while\n \"totalRows\" was correct at 11. This is puzzling since we does\n not\n impose any condition filtering on the collection. Full request\n and\n response below.\n \n \n \n \n \n\nLOCAL FIX\n * DASH development working on a test fix\n \n \n \n \n \n\nPROBLEM SUMMARY\n * The CURI code was using a too aggressive caching approach and\n was not accounting for cases where the dataset was being updated\n in terms of origin (root) nodes in the dataset. The fix will be\n included in the next release but will also be included in\n Cumulative Patch 5 for DASH 3.1.2.1, when available, at\n https://www.ibm.com/developerworks/community/wikis/home?lang=en# [https://www.ibm.com/developerworks/community/wikis/home?lang=en#]\n !/wiki/W8b1151be2b42_4819_998e_f7de7db7bfa2/page/Download%20Cumu\n lative%20Patches%20-%20UI%20Services%20%28DASH%29\n \n \n \n \n \n\nPROBLEM CONCLUSION\n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n IV81778\n \n \n * REPORTED COMPONENT NAME\n JAZZ SM TIP DAS\n \n \n * REPORTED COMPONENT ID\n 5724C04JD\n \n \n * REPORTED RELEASE\n 110\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 2016-02-23\n \n \n * CLOSED DATE\n 2016-03-22\n \n \n * LAST MODIFIED DATE\n 2016-03-22\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 * R110 PSY\n UP",
+ "metadata": {
+ "sourceDocumentId": "swg1IV81778",
+ "date": "2016-03-22",
+ "productName": "Tivoli Components Jazz for Service Management",
+ "productId": "SSRLR8",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1IV81778"
+ }
+ },
+ "swg21675814": {
+ "id": "swg21675814",
+ "content": "\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as fixed if next.
\n
Error description
\n- \n
- \n \n
The responded number of nodes does not match the number of nodes\nin the\ncollection when there is/are new nodes added into the\ncollection. There\nis no condition been set on the collection.\n\nSymptoms:\n\n1. Open the 2 Event Viewers. One with "Un-acknowledged" filter\nand the\nother one "Acknowledged" filter.\n2. Acknowledge a node in "Un-acknowledged" Event Viewer. This\nwill\nacknowledged the node and the node suppose to be added into\n"Acknowledged" Event Viewer on next refresh.\n3. On next refresh on "Acknowledged" Event Viewer, the total\nnumber of\nrows remain same, however the Severity summary did updated\ncorrectly.\nRef: all_acknowledged.png\n\n\n\nInvestigation:\n\n1. The issue only start to occur after applied DASH Version:\n3.1.2.1\nBuild Number: cf011242.02, 201508201935 (201511301851) Build\nDate:\n10/17/12, 8/20/15.\n2. The behavior is working good on DASH Version: 3.1.2.1 Build\nNumber:\ncf011242.02, 201508201935 Build Date: 10/17/12, 8/20/15\n3. The "filteredRows" and "numRows" was returned as 10 while\n"totalRows" was correct at 11. This is puzzling since we does\nnot\nimpose any condition filtering on the collection. Full request\nand\nresponse below.\n
\n \n
Local fix
\n- \n
- \n \n
DASH development working on a test fix\n
\n \n
Problem summary
\n- \n
- \n \n
The CURI code was using a too aggressive caching approach and\nwas not accounting for cases where the dataset was being updated\nin terms of origin (root) nodes in the dataset. The fix will be\nincluded in the next release but will also be included in\nCumulative Patch 5 for DASH 3.1.2.1, when available, at\nhttps://www.ibm.com/developerworks/community/wikis/home?lang=en#\n!/wiki/W8b1151be2b42_4819_998e_f7de7db7bfa2/page/Download%20Cumu\nlative%20Patches%20-%20UI%20Services%20%28DASH%29\n
\n \n
Problem conclusion
\n- \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
IV81778
\n Reported component name
JAZZ SM TIP DAS
\n Reported component ID
5724C04JD
\n Reported release
110
\n Status
CLOSED FIN
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt / Xsystem
\n Submitted date
2016-02-23
\n Closed date
2016-03-22
\n Last modified date
2016-03-22
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
R110 PSY
UP
\n
\n
\n
\n
",
+ "title": "IBM DASH TCTUI1003E An error has occurred communicating with the server - United States",
+ "text": "DASHL2 DASH TCTUI1003E An error has occurred communicating with the server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A User may get the error below when trying to create a page in DASH using the table widget for Web GUI data source. Error is displayed as soon as the data set is selected.\n\nTCTUI1003E An error has occurred communicating with the server \n\nSYMPTOM\nThere are no obvious errors in the DASH (Dashboard Application Services Hub) or Web GUI logs specific to this issue. No columns are shown in the optional settings of the table widget configuration panel after you select the data set.\n\n\nCAUSE\nThis issue can occur if a user has defined a custom AEL view in Web GUI but left the Label field empty for a view column. This label field is optional in Web GUI and can have any string including null. The table widget in DASH does not expect any empty values, so to avoid this issue make sure that label field is not empty. \n\nAn APAR was opened to fix this issue: IV61421. This APAR is fixed in JazzSM 1.1.2.1 so this technote is only applicable to earlier versions. \n\n\nRESOLVING THE PROBLEM\nTo resolve this issue make sure the Label field is not empty(blank).",
+ "metadata": {
+ "sourceDocumentId": "swg21675814",
+ "date": "2016-05-27",
+ "productName": "Tivoli Components Jazz for Service Management",
+ "productId": "SSRLR8",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21675814"
+ }
+ },
+ "swg21430823": {
+ "id": "swg21430823",
+ "content": "\n\n
\nDASHL2 DASH TCTUI1003E An error has occurred communicating with the server
\n\n\n \n \n
\nTechnote (troubleshooting)
\n \n
\n
\n
\n
\n \n
Problem(Abstract)
\n A User may get the error below when trying to create a page in DASH using the table widget for Web GUI data source. Error is displayed as soon as the data set is selected.
TCTUI1003E An error has occurred communicating with the server
Symptom
\n\n
\n There are no obvious errors in the DASH (Dashboard Application Services Hub) or Web GUI logs specific to this issue. No columns are shown in the optional settings of the table widget configuration panel after you select the data set.
\n\n
Cause
\n\n
\n This issue can occur if a user has defined a custom AEL view in Web GUI but left the Label field empty for a view column. This label field is optional in Web GUI and can have any string including null. The table widget in DASH does not expect any empty values, so to avoid this issue make sure that label field is not empty.
\nAn APAR was opened to fix this issue: IV61421. This APAR is fixed in JazzSM 1.1.2.1 so this technote is only applicable to earlier versions.
\n\n
Resolving the problem
\n\n
\n To resolve this issue make sure the Label field is not empty(blank).
\n\n
\n \n
\n
\n \n \n\n
",
+ "title": "IBM Error running the WCM task (update-wcm): XmlCommandException EJPXA0091E: The servletref attribute is required to create a portlet clone. - United States",
+ "text": "Error running the WCM task (update-wcm): XmlCommandException EJPXA0091E: The servletref attribute is required to create a portlet clone. TECHNOTE (FAQ)\n\nQUESTION\n Why do I get the an EJPXA0091E error when I run the update-wcm task? \n\nCAUSE\nIt appears that the Blurb Portlet, or some part of it, has been improperly or manually deleted from the Portal environment.\n\nANSWER\nThe BlurbPortlet is also called the Information Portlet. It is used on the Welcome, Getting Started, and many administration pages. It is not recommended to delete this application. \n\nTo recover from this, we have 2 recommendations. Please work through these recommendations in order. If the first recommendation is successful, there is no need to implement the second.\n\nFirst Recommendation: Update the Blurb portlet - \n\nWe have written a custom .xml file that should allow you to update/reinstall this application on your server. It is attached here and called updateBlurb.xml. Please place it in a temp folder, and run the following command on your server. The basic syntax for the command is as follows: \n\nxmlaccess -user user_ID-password password\n-url myhost:10040/wps/config\n-in input_file.xml -out result_file.xml\n\nThe XMLAccess command line client can be invoked by using the following shell scripts in the directory PortalServer_root/bin/\n\nPlease change the values in this example to match your environment. If you review the result_file.xml and observe that the update was 'result=ok', then attempt to run the ConfigEngine update-wcm task again.\n\nupdateBlurb.xml [/support/docview.wss?uid=swg21430823&aid=2] [/support/docview.wss?uid=swg21430823&aid=1]\n\nNOTE: Please update the URL path in the updateBlurb.xml file before running it. as it needs to contain the path to your InstallableApps folder.\n\n\n\n
\nError running the WCM task (update-wcm): XmlCommandException EJPXA0091E: The servletref attribute is required to create a portlet clone.
\n\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n
Question
\nWhy do I get the an EJPXA0091E error when I run the update-wcm task?
\nCause
\n\n
\n It appears that the Blurb Portlet, or some part of it, has been improperly or manually deleted from the Portal environment.
\nAnswer
\n\n
\n The BlurbPortlet is also called the Information Portlet. It is used on the Welcome, Getting Started, and many administration pages. It is not recommended to delete this application.
To recover from this, we have 2 recommendations. Please work through these recommendations in order. If the first recommendation is successful, there is no need to implement the second.
First Recommendation: Update the Blurb portlet -
We have written a custom .xml file that should allow you to update/reinstall this application on your server. It is attached here and called updateBlurb.xml. Please place it in a temp folder, and run the following command on your server. The basic syntax for the command is as follows:
xmlaccess -user user_ID -password password
-url myhost:10040/wps/config
-in input_file.xml -out result_file.xml
The XMLAccess command line client can be invoked by using the following shell scripts in the directory PortalServer_root/bin/
Please change the values in this example to match your environment. If you review the result_file.xml and observe that the update was 'result=ok', then attempt to run the ConfigEngine update-wcm task again.
NOTE: Please update the URL path in the updateBlurb.xml file before running it. as it needs to contain the path to your InstallableApps folder.
<url>file://localhost/<Path to PortalServer folder>/installableApps/Blurb.war</url>
Replace <Path to PortalServer> with your location:
Windows: C:/IBM/PortalServer
*nix: /opt/ibm/WebSphere/PortalServer
eg. <url>file://localhost//opt/ibm/WebSphere/PortalServer/installableApps/Blurb.war</url>
Second Recommendation - Skip update to the Blurb Portlet -
If you are not able to update the Blurb portlet, then please proceed with the following.
1. Navigate to /PortalServer/wcm/prereq.wcm/wcm/deploy/ on the affected node.
2. Make a backup of the existing DeployWcmAdminPortlets.xml file.
3. Copy the attached version of DeployWcmAdminPortlets.xml into this location.
4. Execute the ConfigEngine update-wcm task again.
NOTE: Please update the multiple URL paths in the DeployWcmAdminPortlets.xml file before replacing the file on the server.
This file has many paths to update, we recommend using a find/replace functionality of a text editor to make the changes to this file.
Replace <Path to PortalServer> with your location:
Windows: C:/IBM/PortalServer
*nix: /opt/ibm/WebSphere/PortalServer
eg. <url>file:////opt/ibm/WebSphere/PortalServer/installer/wp.config/config/templates/SetupPortal_ca.properties</url>
\n
\n \n
\n
\n \n \n\n
\n\n\n\n
\nrelease notice; download; Java Gateway for BMC Remedy; nco-g-bmc-remedy
\n\n\n \n \n
\nNews
\n \n
\n
\n \n
Abstract
\nA new version of the Netcool/OMNIbus Java Gateway for BMC Remedy will be available to download from August 6, 2015.
\nContent
\n\n
\n \n
You can access the latest version of the guide written for this gateway on the IBM Knowledge Center:
www-01.ibm.com/support/knowledgecenter/#!/SSSHTQ/omnibus/gateways/remedygw/wip/concept/bmc_remedy_intro.html
You can download the installation package from the IBM Passport Advantage website:
www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm
Netcool/OMNIbus V8.1
\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CN6I4EN
\nNote: The Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems: AIX, Linux, Solaris, and Windows.
\nNetcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0
\nIf you are running Netcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.
\n\n \n \n
\n
\n | Part number | \nOperating System | \n
| CN6HDEN | \nAIX | \n
| CN6HEEN | \nLinux | \n
| CN6HFEN | \nSolaris | \n
| CN6HGEN | \nWindows | \n
Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.
\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:
\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html
\n \n\n
\n \n
\n
\n \n \n",
+ "title": "IBM Netcool/OMNIbus Integrations Release Notice - Gateway for BMC Remedy (nco-g-bmc-remedy-3_0) - United States",
+ "text": "release notice; download; Java Gateway for BMC Remedy; nco-g-bmc-remedy NEWS\n\nABSTRACT\n A new version of the Netcool/OMNIbus Java Gateway for BMC Remedy will be available to download from August 6, 2015. \n\nCONTENT\n \n\nYou can access the latest version of the guide written for this gateway on the IBM Knowledge Center: \nwww-01.ibm.com/support/knowledgecenter/#!/SSSHTQ/omnibus/gateways/remedygw/wip/concept/bmc_remedy_intro.html [http://www-01.ibm.com/support/knowledgecenter/#!/SSSHTQ/omnibus/gateways/remedygw/wip/concept/bmc_remedy_intro.html]\n\nYou can download the installation package from the IBM Passport Advantage website: \nwww.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm [http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm]\n\nNetcool/OMNIbus V8.1\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CN6I4EN\n\n Note: The Netcool/OMNIbus V8.1 version of this gateway supports the following Operating Systems: AIX, Linux, Solaris, and Windows. \n\nNetcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0\n\nIf you are running Netcool/OMNIbus V7.3.0, 7.3.1 or 7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CN6HDEN AIX CN6HEEN Linux CN6HFEN Solaris CN6HGEN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]",
+ "metadata": {
+ "sourceDocumentId": "swg21687618",
+ "date": "2015-08-06",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21687618"
+ }
+ },
+ "swg1PK96497": {
+ "id": "swg1PK96497",
+ "content": "
\n
\n\n\n\n \n
\n
\n
\n \n
\n \n
\nAPAR status
\n- \n
Closed as documentation error.
\n
Error description
\n- \n
- \n \n
Doc Defect: Installation Guide does not clarify with Oracle inst\nallation character set AL32UTF8 requirement\n\nAs of Build Forge 7.1.1.1 installation guide, the Oracle databas\ne creation requirement for the character set is not appropriatly\n clarified.\n\nCurrently, the database character set requirement is listed unde\nr the installation guide as UTF-8.\nThis is listed under the 7.1.1.1 instalation guide under the fol\nlowing section.\n\nPre-installation Setup\n\nInternational data setup (p20)\np.\n[...]\n3. Configure databases to use the UTF-8 character set and fonts\nthat support international data. (p21)\n[...]\nOracle: Set the character set to UTF8 - Unicode 3.0 on the insta\nnce when you install it.\nIn the Database Configuration Assistant, the setting is made on\nthe Initialization Parameters\nstep on the Character Sets tab.\n\nDatabase Setup (p21)\n[...]\nConfigure support for the UTF-8 character set and an appropriate\n collation. Typically, support\nfor international data is specified when you create your databas\ne; international data support\ncannot be configured after database creation. You must install t\nhe fonts you intend to use to\ndisplay data. *Build Forge requires the use of international dat\na (UTF-8 character sets).*\n\nCustomer will generally set the Oracle database character set to\n UTF-8 as this character set is listed specificly in the install\nation guide and supports Unicode 3.0 as of Oracle Database relea\nse 8.1.7 and later.\n\n6 Supporting Multilingual Databases with Unicode\nhttp://download.oracle.com/docs/cd/B19306_01/server.102/b14225/c\nh6unicode.htm\n\nEnabling Multilingual Support with Unicode Databases\n\n[...]\nUTF8\n\nThe UTF8 character set encodes characters in one, two, or three\nbytes. It is for ASCII-based platforms.\n\nThe UTF8 character set has supported Unicode 3.0 since Oracle8i\nrelease 8.1.7 and will continue to support Unicode 3.0 in future\n releases of Oracle Database.\n\nThis defect is to specificly list the character set requirement\nfrom UTF-8 to AL32UTF8, as the initial specification is somewhat\n misleading.\n\nCustomer who configure their Oracle databases for character set\nUTF8 will recieve the following error message during the databas\ne test that is confusing.\n\nThis database is not created with the UTF8 character set.\n\nThe installation script is using the following query to obtain t\nhe Oracle database character set.\n\nSELECT SYS_CONTEXT('USERENV', 'LANGUAGE') FROM DUAL\n\nFrom this, the installer is searching for the AL32UTF8 listed at\n the end of this query.\nCustomer who has set their database to UTF8 will be left consufe\nd until they are informed of the AL32UTF8 requirement.\n\nAfter the database is recreated with AL32UTF8 character set, cus\ntomer can complete the installation as expected.\n
\n \n
Local fix
\n- \n
Problem summary
\n- \n
- \n \n
Missing documentation to specify the correct UTF-8 character\nencoding for Oracle.\n
\n \n
Problem conclusion
\n- \n
- \n \n
Added instructions for specifying AL32UTF8\n
\n \n
Temporary fix
\n- \n
Comments
\n- \n
APAR Information
\n \n
\n - \n
APAR number
PK96497
\n Reported component name
BUILD FORGE SE
\n Reported component ID
5724S2706
\n Reported release
711
\n Status
CLOSED DOC
\n PE
NoPE
\n HIPER
NoHIPER
\n Special Attention
NoSpecatt
\n Submitted date
2009-09-17
\n Closed date
2009-11-28
\n Last modified date
2009-11-28
\n
- \n
APAR is sysrouted FROM one or more of the following:
\n APAR is sysrouted TO one or more of the following:
\n
Fix information
\n- \n
Applicable component levels
\n- \n
\n
\n
",
+ "title": "IBM PK96497: Doc Defect: Installation Guide does not clarify with Oracle inst allation character set AL32UTF8 requirement - United States",
+ "text": " 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 * Doc Defect: Installation Guide does not clarify with Oracle inst\n allation character set AL32UTF8 requirement\n \n As of Build Forge 7.1.1.1 installation guide, the Oracle databas\n e creation requirement for the character set is not appropriatly\n clarified.\n \n Currently, the database character set requirement is listed unde\n r the installation guide as UTF-8.\n This is listed under the 7.1.1.1 instalation guide under the fol\n lowing section.\n \n Pre-installation Setup\n \n International data setup (p20)\n p.\n [...]\n 3. Configure databases to use the UTF-8 character set and fonts\n that support international data. (p21)\n [...]\n Oracle: Set the character set to UTF8 - Unicode 3.0 on the insta\n nce when you install it.\n In the Database Configuration Assistant, the setting is made on\n the Initialization Parameters\n step on the Character Sets tab.\n \n Database Setup (p21)\n [...]\n Configure support for the UTF-8 character set and an appropriate\n collation. Typically, support\n for international data is specified when you create your databas\n e; international data support\n cannot be configured after database creation. You must install t\n he fonts you intend to use to\n display data. *Build Forge requires the use of international dat\n a (UTF-8 character sets).*\n \n Customer will generally set the Oracle database character set to\n UTF-8 as this character set is listed specificly in the install\n ation guide and supports Unicode 3.0 as of Oracle Database relea\n se 8.1.7 and later.\n \n 6 Supporting Multilingual Databases with Unicode\n http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/c\n h6unicode.htm [http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch6unicode.htm]\n \n Enabling Multilingual Support with Unicode Databases\n \n [...]\n UTF8\n \n The UTF8 character set encodes characters in one, two, or three\n bytes. It is for ASCII-based platforms.\n \n The UTF8 character set has supported Unicode 3.0 since Oracle8i\n release 8.1.7 and will continue to support Unicode 3.0 in future\n releases of Oracle Database.\n \n This defect is to specificly list the character set requirement\n from UTF-8 to AL32UTF8, as the initial specification is somewhat\n misleading.\n \n Customer who configure their Oracle databases for character set\n UTF8 will recieve the following error message during the databas\n e test that is confusing.\n \n This database is not created with the UTF8 character set.\n \n The installation script is using the following query to obtain t\n he Oracle database character set.\n \n SELECT SYS_CONTEXT('USERENV', 'LANGUAGE') FROM DUAL\n \n From this, the installer is searching for the AL32UTF8 listed at\n the end of this query.\n Customer who has set their database to UTF8 will be left consufe\n d until they are informed of the AL32UTF8 requirement.\n \n After the database is recreated with AL32UTF8 character set, cus\n tomer can complete the installation as expected.\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * Missing documentation to specify the correct UTF-8 character\n encoding for Oracle.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Added instructions for specifying AL32UTF8\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PK96497\n \n \n * REPORTED COMPONENT NAME\n BUILD FORGE SE\n \n \n * REPORTED COMPONENT ID\n 5724S2706\n \n \n * REPORTED RELEASE\n 711\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-09-17\n \n \n * CLOSED DATE\n 2009-11-28\n \n \n * LAST MODIFIED DATE\n 2009-11-28\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",
+ "metadata": {
+ "sourceDocumentId": "swg1PK96497",
+ "date": "2009-11-28",
+ "productName": "Rational Build Forge",
+ "productId": "SSB2MV",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg1PK96497"
+ }
+ },
+ "swg21428959": {
+ "id": "swg21428959",
+ "content": "
\n
\n\n\n\n
\nnco_g_oracle; nco_g_jdbc; nco_g_odbc; nco_g_objserv_bi; nco_g_objserv_uni; Ipc.StackSize; inserts; gateway
\n\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n
Question
\n
Oracle Gateway : Why does the gateway keep exiting for large data resynchronisation?
Cause
\n\n
\n There is not enough memory allocated to the socket to send the data.
\nAnswer
\n\n
\n \n
This issue affects all gateways:-
\n\n
For large amounts of data inserts|updates the object server needs to have the Ipc.StackSize increased.
\nvi $NCHOME/etc/NCOMS.props
#Ipc.StackSize: 67584
# Increased for large data inserts - 4*standard
Ipc.StackSize: 524288
:wq
Netcool/OMNIbus v8.1 uses 262144 by default:
Ipc.StackSize: 262144
Therefore you should ensure that all components that use Ipc.StackSize have a value equal to or less than the Ipc.StackSize in the object server. In general Ipc.StackSize is set to a common value throughout the Netcool/OMNIbus system, to prevent issues.
Restart the object server for the Ipc.StackSize update to take affect.
The default Object server stack size can be between 65k to 262k by default, depending upon the version of Netcool/OMNIbus.
Increasing the stack size limits the number of connections that can be established to the Object Server, since each connection requires its own stack.
i.e. stacksize * number of clients connected = memory used
Maximum memory sizes for a 32-bit Object Server ranges from 2Gb to 3.5 Gb.
Therefore the current memory size of the Object Server needs to be measured and taken into account before increasing the Object Server's stack size property.
\n
\n \n
\n
\n \n \nProduct Alias/Synonym
\n nco-g-oracle
nco-g-jdbc
nco-g-odbc
",
+ "title": "IBM Oracle Gateway : Exits unexpectedly during large data insert - United States",
+ "text": "nco_g_oracle; nco_g_jdbc; nco_g_odbc; nco_g_objserv_bi; nco_g_objserv_uni; Ipc.StackSize; inserts; gateway TECHNOTE (FAQ)\n\nQUESTION\n \nOracle Gateway : Why does the gateway keep exiting for large data resynchronisation? \n\nCAUSE\nThere is not enough memory allocated to the socket to send the data.\n\nANSWER\n \n\nThis issue affects all gateways:- \n\n \n\nFor large amounts of data inserts|updates the object server needs to have the Ipc.StackSize increased. \n\nvi $NCHOME/etc/NCOMS.props\n#Ipc.StackSize: 67584\n# Increased for large data inserts - 4*standard\nIpc.StackSize: 524288\n:wq\n\nNetcool/OMNIbus v8.1 uses 262144 by default:\nIpc.StackSize: 262144\n\nTherefore you should ensure that all components that use Ipc.StackSize have a value equal to or less than the Ipc.StackSize in the object server. In general Ipc.StackSize is set to a common value throughout the Netcool/OMNIbus system, to prevent issues.\n\nRestart the object server for the Ipc.StackSize update to take affect.\n\nThe default Object server stack size can be between 65k to 262k by default, depending upon the version of Netcool/OMNIbus.\nIncreasing the stack size limits the number of connections that can be established to the Object Server, since each connection requires its own stack. \n\ni.e. stacksize * number of clients connected = memory used\n\nMaximum memory sizes for a 32-bit Object Server ranges from 2Gb to 3.5 Gb.\nTherefore the current memory size of the Object Server needs to be measured and taken into account before increasing the Object Server's stack size property.\n\n\n \n\nPRODUCT ALIAS/SYNONYM\n nco-g-oracle\nnco-g-jdbc\nnco-g-odbc",
+ "metadata": {
+ "sourceDocumentId": "swg21428959",
+ "date": "2010-05-09",
+ "productName": "Tivoli Netcool/OMNIbus",
+ "productId": "SSSHTQ",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21428959"
+ }
+ },
+ "swg21403259": {
+ "id": "swg21403259",
+ "content": "
\n
\n\n\n\n
\n1403259; RTC; deferred; operation; failed; duplicate; attribute; identifier; import; migration; Deferred operation failed; CRJAZ0651I Error rebuilding index; RN2.0.0.1; RN2.0
\n\n\n \n \n
\n
\nTechnote (troubleshooting)
\n \n
\n
\n \n
Problem(Abstract)
\nThis technote identifies an issue than can occur when migrating from IBM Rational Team Concert 1.0.x and 2.0.x..
\nSymptom
\n\n
\n The repotools -import command fails some errors found in the import log:
2009-08-27 08:16:57,893 Running post import for "com.ibm.team.workitem" component...
2009-08-27 08:17:15,934 Deferred operation failed
com.ibm.team.repository.common.InternalRepositoryException: Deferred operation failed
Caused by:
com.ibm.team.repository.common.TeamRepositoryException: Unknown origin
at com.ibm.team.repository.service.internal.RdbRepositoryDataMediator.wrapWithOrigin(RdbRepositoryDataMediator.java:1597)
at com.ibm.team.repository.service.internal.RdbRepositoryDataMediator.preCommitNotify(RdbRepositoryDataMediator.java:1557)
SQL Exception #1
SQL Message: [jcc][t4][102][10040][3.53.70] Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4228, SQLSTATE=null
SQL State: null
Error Code: -4228
SQL Exception #2
SQL Message: Error for batch element #137: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=10;MODEL.ATTRIBUTE, DRIVER=3.53.70
SQL State: 23505
Error Code: -803
Exception Details: CRJAZ0250I A violation of the constraint imposed by a unique index or a unique constraint occurred.
SQL Exception #3
SQL Message: Error for batch element #138: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=10;MODEL.ATTRIBUTE, DRIVER=3.53.70
SQL State: 23505
Error Code: -803
Exception Details: CRJAZ0250I A violation of the constraint imposed by a unique index or a unique constraint occurred.
Class: com.ibm.team.repository.service.internal.dataaccess.write2.Row
Item Handle: com.ibm.team.workitem.common.internal.model.impl.AttributeImpl@bd10bd1 (stateId: [UUID _DtQu8JM1Ed6WW456sAZV4A], itemId: [UUID _DtO5wZM1Ed6WW456sAZV4A], origin: <unset>, immutable: true) (contextId: [UUID _zn8l0EFyEd60OIXe2EZEvw], modified: 2009-08-27 14:11:35.903, workingCopy: <unset>) (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: null) (identifier: com.ibm.gbs.workitem.attribute.risk.title, attributeType: string, displayName: Title, builtIn: false, internal: false, fullTextKind: _meta, readOnly: false)
Caused by:
com.ibm.db2.jcc.b.rn: [jcc][t4][102][10040][3.53.70] Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4228, SQLSTATE=null
at com.ibm.db2.jcc.b.bd.a(bd.java:404)
Alternatively, the following error messages can be encountered:
2009-07-20 14:50:20,497 Rebuilding indices...
2009-07-20 14:50:30,307 com.ibm.team.repository.service.internal.db.util.JdbcDB$2: CRJAZ0577I Error preparing or executing statement => CREATE UNIQUE INDEX MODEL.UNIQUE_IDENTIFIER ON MODEL.ATTRIBUTE(PROJECT_AREA_ITEM_ID, IDENTIFIER)
2009-07-20 14:50:30,308 com.ibm.team.repository.service.internal.db.util.JdbcDB$2: CRJAZ0577I Error preparing or executing statement => CREATE UNIQUE INDEX MODEL.UNIQUE_IDENTIFIER ON MODEL.ATTRIBUTE(PROJECT_AREA_ITEM_ID, IDENTIFIER)
2009-07-20 14:50:30,784 CRJAZ0651I Error rebuilding index.
Then, the following error notice can be found in the resulting import log:
##############################################################################################
2009-08-27 14:15:46,418 ****** Migration Errors ******
2009-08-27 14:15:46,419 CRJAZ0656I **ERROR** Migration completed with errors. The imported database is in an inconsistent state and should not be used without further analysis.
Check the migration log "/opt/IBM/XXXXX/server/repotools_import.log" for details.
2009-08-27 14:15:46,419 ##############################################################################################
Cause
\n\n
\n The failure happens because there is a second attribute with the same id in the export file.
This error has no impact as the attribute was imported once, so it is there.
More details can be found in the jazz.net work item 88109
Diagnosing the problem
\n\n
\n - the import command fails during the migration from 1.X to 2.X
- the import does not early abort, it fails at the end
- "Deferred operation failed" error message can be found in the import log
Resolving the problem
\n\n
\n
\n To resolve this issue, upgrade RTC to the 2.0.0.1 version.
This is the version that includes the fix for jazz.net work item 88109
\n
\n \n
\n
\n Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki. | \n
|---|
\n
\n \n
\n \n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| \n | Rational Team Concert | \n\n | \n | \n | \n |
\n
\n
\n \n \n",
+ "title": "IBM repotools -import command fails due to duplicate attribute identifier - United States",
+ "text": "1403259; RTC; deferred; operation; failed; duplicate; attribute; identifier; import; migration; Deferred operation failed; CRJAZ0651I Error rebuilding index; RN2.0.0.1; RN2.0 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote identifies an issue than can occur when migrating from IBM Rational Team Concert 1.0.x and 2.0.x.. \n\nSYMPTOM\nThe repotools -import command fails some errors found in the import log:\n\n2009-08-27 08:16:57,893 Running post import for \"com.ibm.team.workitem\" component...\n2009-08-27 08:17:15,934 Deferred operation failed\ncom.ibm.team.repository.common.InternalRepositoryException: Deferred operation failed\n\nCaused by: \ncom.ibm.team.repository.common.TeamRepositoryException: Unknown origin\nat com.ibm.team.repository.service.internal.RdbRepositoryDataMediator.wrapWithOrigin(RdbRepositoryDataMediator.java:1597)\nat com.ibm.team.repository.service.internal.RdbRepositoryDataMediator.preCommitNotify(RdbRepositoryDataMediator.java:1557)\n\nSQL Exception #1\nSQL Message: [jcc][t4][102][10040][3.53.70] Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.\nUse getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4228, SQLSTATE=null\nSQL State: null\nError Code: -4228\nSQL Exception #2\nSQL Message: Error for batch element #137: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=10;MODEL.ATTRIBUTE, DRIVER=3.53.70\nSQL State: 23505\nError Code: -803\nException Details: CRJAZ0250I A violation of the constraint imposed by a unique index or a unique constraint occurred.\nSQL Exception #3\nSQL Message: Error for batch element #138: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=10;MODEL.ATTRIBUTE, DRIVER=3.53.70\nSQL State: 23505\nError Code: -803\nException Details: CRJAZ0250I A violation of the constraint imposed by a unique index or a unique constraint occurred.\nClass: com.ibm.team.repository.service.internal.dataaccess.write2.Row\nItem Handle: com.ibm.team.workitem.common.internal.model.impl.AttributeImpl@bd10bd1 (stateId: [UUID _DtQu8JM1Ed6WW456sAZV4A], itemId: [UUID _DtO5wZM1Ed6WW456sAZV4A], origin:
\n
\n\n\n\n
\nMQIINFO
\n\n\n \n \n
\n
\n
\nTechnote (troubleshooting)
\n \n
\n
\n \n
Problem(Abstract)
\nYour IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) message flow is corrupted, and you want to know if there is a way to recover or revert to a previous copy.
\nResolving the problem
\n\n
\n Each time you edit and save a file, a copy of it is saved. This allows you to compare your current file state to a previous state, or replace the file with a previous state. Each state in the local history is identified by the date and time the file was saved.
Therefore, if your message flow file becomes corrupted, instead of opening the file you should be able to use the message flow's resource option Replace With, and lose only the most recently unsaved changes.
To replace a Workbench resource with a state in the local history:
1. In the Navigator view, select the resource that you want to replace with a local history state.
2. Right-click the resource, select Replace with > Local History. The Replace from Local History page opens.
3. Select a state from the Local History list. The Text Compare editor opens.
4. Click the Select Next Change and Select Previous Change buttons to browse through the changes made between states in the local history and the Workbench resource.
5. Select the state you want to replace, and click Replace.
The online documentation has more details about using the local history feature. From the Message Brokers Toolkit choose the menu option Help -> Help Contents to access the Information Center. Search using the search argument "Working with local history".
\n
\n \n
\n
\n \n
\n
\n | Segment | \nProduct | \nComponent | \nPlatform | \nVersion | \nEdition | \n
|---|---|---|---|---|---|
| Business Integration | \nIBM Integration Bus | \nToolkit | \n\n | 9.0 | \nAll Editions | \n
\n
\n
\n \n \nHistorical Number
\n67242 7TD 000
\nProduct Alias/Synonym
\nWMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI
\n",
+ "title": "IBM Corrupted message flow recovery - United States",
+ "text": "MQIINFO TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) message flow is corrupted, and you want to know if there is a way to recover or revert to a previous copy. \n\nRESOLVING THE PROBLEM\nEach time you edit and save a file, a copy of it is saved. This allows you to compare your current file state to a previous state, or replace the file with a previous state. Each state in the local history is identified by the date and time the file was saved.\nTherefore, if your message flow file becomes corrupted, instead of opening the file you should be able to use the message flow's resource option Replace With, and lose only the most recently unsaved changes.\n\n\nTo replace a Workbench resource with a state in the local history: \n\n1. In the Navigator view, select the resource that you want to replace with a local history state. \n2. Right-click the resource, select Replace with > Local History. The Replace from Local History page opens. \n3. Select a state from the Local History list. The Text Compare editor opens. \n4. Click the Select Next Change and Select Previous Change buttons to browse through the changes made between states in the local history and the Workbench resource. \n5. Select the state you want to replace, and click Replace. \n\nThe online documentation has more details about using the local history feature. From the Message Brokers Toolkit choose the menu option Help -> Help Contents to access the Information Center. Search using the search argument \"Working with local history [http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fau16520_.htm]\".\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Toolkit 9.0 All Editions \nHISTORICAL NUMBER\n 67242 7TD 000 \n\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker IBM Integration Bus IIB IBMIB MQ Integrator WBIMB WBI-MB MQSI WMQI",
+ "metadata": {
+ "sourceDocumentId": "swg21175141",
+ "date": "2013-08-29",
+ "productName": "WebSphere Message Broker",
+ "productId": "SSKM8N,SSNQK6",
+ "canonicalUrl": "http://www.ibm.com/support/docview.wss?uid=swg21175141"
+ }
+ },
+ "swg21967763": {
+ "id": "swg21967763",
+ "content": "
\n
\n\n\n\n
\nMustGather crash pda restart netezza rca rootcause
\n\n\n \n \n
\nTechnote (FAQ)
\n \n
\n
\n \n \n\n
Question
\nWhat to collect when a PureData System for Analytics Crashes or Restarts for IBM technical support to carry out Root Cause Analysis (RCA)?
\nCause
\n\n
\n NPS crashes, fails over or restarts
\nAnswer
\n\n
\n Contact IBM Technical Support via PMR. Once a PMR has been created share time and date of incident, confirm system is in stable online state and provide the following information (substitute <PMR#.Branch#.Country#> with valid complete PMR number, Branch and Country codes separated by dots(.) ):
su - nz
mkdir -p /nzscratch/pmr<PMR#.Branch#.Country#>
cd /nzscratch/pmr<PMR#.Branch#.Country#>
/nz/kit/bin/adm/nzhealthcheck 2>&1 | tee healthcheck.out
##Copy report to /nzscratch/pmr<PMR#.Branch#.Country#>:
cp /nz/kit.<nspVersion>/log/nzhealthcheck/Netezza_System_Health_Check_Report_<date>_<time>.txt .
nzstats > nz.txt
nzrev >> nz.txt
nzds -issues >> nz.txt
nzhw -issues >> nz.txt
nzspupart -issues >> nz.txt
nzhw -type spu -detail >> nz.txt
##If you have nzlogcollector please run the following:
/nz/support/bin/adm/nzlogcollector/nzlogcollector -symptom crash -days 5
## Collect pg.log and dbos.log for dates when restart occurred (please include logs for day before and after is possible)
cp /nz/kit/log/postgress/pg.log .
cp /nz/kit/log/dbos/dbos.log .
tar -czvf bootsvr.tgz /nz/kit/log/bootsvr/
tar -czvf startupsvr.tgz /nz/kit/log/startupsvr/
tar -czvf sysmgr.tgz /nz/kit/log/sysmgr/
tar -czvf eventmgr.tgz /nz/kit/log/eventmgr/
tar cvzf HA1_messages.tgz /var/log/messages*
ssh ha2 "/nzscratch/HA2_messages.tgz /var/log/messages*"
scp root@ha2:nzscratch/HA2_messages.tgz .
crm_mon -1 > crm_mon.out
ssh ha2 !!
ps aux|grep heartbeat > HA1_ps.aus.heartbeat.out
ssh ha2 "ps aux|grep heartbeat > /nzscratch/HA2_ps.aus.heartbeat.out"
scp root@ha2:nzscratch/HA2_ps.aus.heartbeat.out .
find -L /nz/kit/log -iname 'core*' -exec ls -alh {} \\; > spucores.out
find -L /nz/data -iname 'core*' -exec ls -alh {} \\; >> spucores.out
## if spucores.out contains a crash report please send it to the PMR as well
cd ..
tar -czvf <PMR#.Branch#.Country#>.tgz /nzscratch/pmr<PMR#.Branch#.Country#>
Send us <PMR#.Branch#.Country#>.tgz with all the information.
Reference Technote:
How to properly collect a PureData Systems for Analytics Health Check Report using nzhealthcheck?
http://www.ibm.com/support/docview.wss?uid=swg21903167
\n \n
\n ",
+ "title": "IBM Must Gather: PureData Systems for Analytics Crash or Restart - United States",
+ "text": "MustGather crash pda restart netezza rca rootcause TECHNOTE (FAQ)\n\nQUESTION\n What to collect when a PureData System for Analytics Crashes or Restarts for IBM technical support to carry out Root Cause Analysis (RCA)? \n\nCAUSE\nNPS crashes, fails over or restarts\n\nANSWER\nContact IBM Technical Support via PMR. Once a PMR has been created share time and date of incident, confirm system is in stable online state and provide the following information (substitute