Guru Of Geeks

Technote (troubleshooting) Problem(Abstract) When trying to log in to DataStage using the DataStage Designer or DataStage Director client, the user receives the following error: Failed to connect to Information Server Engine: <engine_name>, <project_name> (The host name specified is not valid, or the host is not responding (81011)) Cause Information Server DataStage clients perform a 2-step login -- first they authenticate against the service tier (WebSphere) and if successful the client then connects to the engine tier using the hostname that was setup during DataStage install (not the host name shown in DataStage client login dialog). Error 81011 is an engine tier error code which means the hostname specified in login dialog to access service tier worked, but that the hostname setup for DataStage engine could not be resolved. This situation usually occurs when the user specifies a fully qualified hostname in...

​Once new kernel passes the test system, Ubuntu offers you to install it through its update system. At the same time, old kernel remains in the system. It means that after some time of using Ubuntu , you may have a number of old kernels. They take your disk space and also may clutter the GRUB menu, although the latter issue is resolved in newer versions of Ubuntu. https://youtu.be/yzqOGVzqpJI This video shows you the way to remove old obsolete kernels from your Ubuntu installation. The same approach is valid for whole Ubuntu family and derivatives: Xubuntu , Edubuntu ,  Kubuntu , Zorin OS , Linux Mint and so on. Please remember that the "best practice" is to keep at least two kernels in the system: the current and the previous one. This is to ensure the fallback solution if current kernel fails for whatever reason.​

Problem(Abstract) When you use security that is enabled out-of-the-box and select the 2. Use WebSphere Application Server registry option in the Customization dialogs for a WebSphere® Application Server for z/OS® installation, an error message similar to the following information is logged in the job log of the node agent: Trace: 2006/05/10 16:04:37.551 01 t=6B7E78 c=UNK key=S2 (13007002) ThreadId: 00000018 FunctionName: com.ibm.ws.channel.framework.impl.WSChannelFrameworkImpl SourceId: com.ibm.ws.channel.framework.impl.WSChannelFrameworkImpl Category: AUDIT ExtendedMessage: BBOO0222I: CHFW0019I: The Transport Channel Service has started chain IIOP_SECURE_OUT_9366c15e. CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN "CN= WEBS37.PDL.POK.IBM.COM , OU=S37MCSB1, O=IBM" was sent from target host:port " WEBS37.pdl.pok.ibm.com:16211 ". For example, you might need to add the signer to the /WebSphere/V6R1M0B/AppServer1/profiles /de...

Question When installing WebSphere Process Server through the launchpad, the IBM Installation Manager install location is defaulted. Can I change where this gets installed? Answer Yes. As long as there is not already an installation of IBM Installation Manager on the box, the default installation location for IBM Installation Manager can be changed by using the following procedure: Steps 1. Modify the <imageLocation>/launchpad/content/userExtensions.js file, where <imageLocation> is the location of the installation image of WebSphere Process Server. 2. Replace the following lines within the existing writeIMInstallXML(was_home, cdLocation, isRoot) function: + "\<install\>" + "\<offering features=\'agent_core,agent_jre\' id=\'com.ibm.cic.agent\' version=\'" + IMversion + "\'/\>" + "\</install\>" with the following lines updated with y...

Question When installing WebSphere Process Server through the launchpad, the IBM Installation Manager agent data location is defaulted. Can I change where the agent data location gets created? Answer Yes. The default location for the IBM Installation Manager agent data location can be changed by using the following procedure: NOTE: If IBM Installation Manager has already been installed you cannot change the agent data location. This procedure only changes the location when WebSphere Process Server is installing IBM Installation Manager for the first time. Steps Obtain information from the IBM Installation Manager product documentation on the Agent data location . This information provides you the default location as well as what pieces of information are kept in the agent data location. Modify the <imageLocation> /launchpad/content/global.properties file, where <imageLocation> is the location of the installation...

Question When installing WebSphere Process Server through the launchpad, can I change the default shared resource location? Answer Yes. You can change the default shared resource location by using the following procedure. The following steps are for new installations. If you already have installed and want to change the shared resource location, you will have to uninstall and reinstall after following these steps. Steps 1. Locate the default shared resource. Depending on whether you are an administrative (root) or non-administrative (non-root) user, find the default shared resource location in one of the following tables. Administrative or root users Platform Default Location for shared resources AIX /usr/IBM/BPMShared HP-UX /opt/IBM/BPMShared Linux /opt/ibm/BPMShared Solaris /opt/IBM/BP...

Make sure your eclipse.ini file includes the following lines. - vm C : \path\to\6 4bit \java\bin\javaw . exe My eclipse.ini for example: - startup plugins / org . eclipse . equinox . launcher_1 . 1.1 . R36x_v20101122_1400 . jar -- launcher . library plugins / org . eclipse . equinox . launcher . win32 . win32 . x86_64_1 . 1.2 . R36x_v20101222 - product org . eclipse . epp . package . java . product -- launcher . defaultAction openFile -- launcher . XXMaxPermSize 256M - showsplash org . eclipse . platform - vm C : \Program Files \Java\jdk1 . 6.0 _32\bin\javaw . exe -- launcher . XXMaxPermSize 256m -- launcher . defaultAction openFile - vmargs - Dosgi . requiredJavaVersion = 1.5 - Xms40m - Xmx512m Use OS and Eclipse both 64 bit or both 32 bit keep same and config eclipse.ini . Your eclipse.ini file can be found in your eclipse folder.

​ Question Changing hostname of the DB2 server. What updates in DB2 need to be made? Cause Changing the DB2 server's hostname. Answer Perform the following on the DB2 server: 1) Login as the dasadm user on UNIX/Linux or Local Administrator on Windows. Stop the DB2 Administration Server (DAS): db2admin stop 2) Login as the instance owner on UNIX/Linux or Local Administrator on Windows. Stop the DB2 instance: db2stop 3) Change the server's hostname. On a Windows system, a reboot is required before this change will take effect. Do not reboot the Windows Server at this time - you must make the DB2 Configuration changes first. 4) Login as user ROOT if DB2 is on UNIX/Linux and Local Administrator on Windows. Update the DB2SYSTEM registry variable while in the instance home directory: UNIX/Linux db2set -g DB2SYSTEM=<new hostname> Windows db2set -g DB2SYSTEM=<new hostname> ...

IBM Announced on 12/9/15…upgrade your 11.3 installation to 11.5 just like a Fix Pack! Please note this download document releasing a Mod Pack for customers to be able to upgrade their existing 11.3.x systems to 11.5.0.0.  Customers that wish to do an inplace upgrade will install this Mod Pack (ispkg) file, just like a Fix Pack installation. http://www.ibm.com/support/docview.wss?uid=swg24041335 The Download document includes a lot of pertinent information, please read it carefully.  Links directly to Fix Central are also provided.

Technote (troubleshooting) Problem(Abstract) Websphere Application Server (WAS) fails to come up when used with Information Server because WAS is unable to contact the DB2 XMeta database. In the WAS SystemOut.log is has the errors: Error getting Connection from DriverManager with url (jdbc:db2://db2server:50000/xmeta) and driver (com.ibm.db2.jcc.DB2Driver) Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-5005, SQLSTATE= , SQLERRMC=null, DRIVER=3.58.135 Symptom Webpshere Application Server fails to start, inspection of the SystemOut.log shows the following Caused by: org.apache.ojb.broker.accesslayer.LookupException: Error getting Connection from DriverManager with url (jdbc:db2://db2server:50000/xmeta) and driver (com.ibm.db2.jcc.DB2Driver) at org.apache.ojb.broker.accesslayer.ConnectionFactoryAbstractImpl.newConne ctionFromDriverManager(Unknown Source) at org.apache.ojb.broker.acces...

Problem(Abstract) When attempting to start the DataStage Engine users get the error [dsadm@ DSEngine]$ $DSHOME/bin/uv -admin -start -bash: /opt/IBM/InformationServer/Server/DSEngine/sample/ds.rc: Permission denied Cause Common cause of the issue is incorrect permissions on the below files in $DSHOME/bin directory For Ex. $ ls -altr |grep rws -rwsr-x--x 1 root dstage 66821 Mar 06 2007 uv -rwsr-x--x 1 root dstage 1615899 Mar 06 2007 list_readu -rwsr-x--x 1 root dstage 1646771 Mar 06 2007 dsdlockd -rws--x--x 1 root dstage 6920 Mar 06 2007 dstskup -rwsr-x--x 1 root dstage 1603427 Mar 06 2007 dslictool -rws--x--x 1 root dstage 87585 Mar 06 2007 DBsetup -rwsr-x--x 1 root system 1607287 Apr 17 2007 load_NLS_shm *$DSHOME is the path to the home directory where DataStage engine is installed Resolving the problem Compare the output ls -altr |grep rws in $DSHOME/bin directory to the above

Question How can I change the drive or path of the Reporting workspace directory to a different location than where Information Server creates it by default? Cause The Information Server Reporting workspace is used at run time for holding temporary status and information related to report generation. The amount of space required varies depending on the number, types and complexity of reports created. In some cases, the default location of the Reporting workspace does not have adequate space so it may be necessary to relocate to a different location. When the workspace is located in a tmp directory location, it could potentially be vulnerable to being deleted or files removed as part of some system administrator or user maintenance activity. To avoid this problem you may wish to change the default reporting workspace to a different directory. Answer The default reporting workspace location is different for various releases o...

Backing-up Files Open My Computer . Go to: C drive --> Documents and Settings --> your username for your computer Open Application Data . If you do not see it, you may need to go to Tools --> Folder Options and then select the View tab at the top. Make sure Show hidden files and folders is selected. Then, click OK . You should now be able to see Application Data . Open it. From inside the Application Data folder, go to: Thunderbird --> Profiles --> RANDOM SET OF CHARACTERS --> Mail NOTE: RANDOM SET OF CHARACTERS varies from install to install of Thunderbird. It is typically the only folder in the Profiles directory unless you have more than one profile. You should back up all contents of this folder. Restoring Files After reformatting, or on another computer, install Thunderbird . While Thunderbird is NOT running , restore the folder tree to the directory:v C:\Documents and Settings\USERNAME\Application Data\Thunderbird\Profiles\RANDOM SET OF CHARACTERS...

Symptom  CDIIA0001E: PXProcessor.java:150  PxValidation26877554: Job status -> 1:Job 2: PxValidation_PxValidation26877554 failed, please verify that the job is submitted correctly. DS job Numer is RT_SC464.  Detailed Log: Event 1: main_program: **** Startup error on node1  connecting with conductor on servername with cookie 1449726886.728000.1eb0:  unable to connect to port 10000  on conductor; socket = 0, Unknown error **** Startup error on node2  connecting with conductor on vps42320 with cookie 1449726886.728000.1eb0:  unable to connect to port 10000  on conductor; socket = 0, Unknown error Event 2: main_program: Accept timed out retries = 8 Event 3: main_program: The section leader on servername died Event 4: main_program: **** Parallel startup failed **** This is usually due to a configuration error, such as not having the Orchestrate install directory properly mounted on all nodes, rsh permissions not correctly set (via /etc/hosts.equiv or .rhosts), or running from a directory...

Question How can I increase or decrease the number of nodes that are displayed in the lineage report graph? Cause InfoSphere Information Governance Catalog has a default limit for maximum visible nodes of 500. Although this number is appropriate for many use cases, it can be configured to meet the needs of your enterprise. Factors in choosing the suitable value are consumability and performance. Answer Use Case #1: Too many nodes in the graph make it difficult to track the data flow First, consider using data lineage filters to hide uninteresting nodes so that the graph becomes more compact. Alternatively, lower the number of maximum visible nodes. When that number is reached, the graph branches are truncated. You can resume lineage from any truncated node by clicking the arrow symbol on top of that node. Use Case #2: The graph is truncated too early and I do not see enough nodes First, look at using data lineage fi...

DataStage logging was changed at release 8.1 to log job run detail records into the operational repository, (xmeta) rather than the local project level log files, (RT_LOGxxx). In case XMETA repository logging causing problem (i.e not visible from designer), we able to change the logging method back to local project log files. RTLogging ---> Log will saved in  project level log files which is UV binary files ORLogging --->  Log will saved in XMETA DB Here are the steps: 1) Log into DS machine 2) Go to /opt/IBM/InformationServer/Server/Projects/ 3) Choose you project directory 4) Edit DSParams file 5) Look for RTLogging and ORLogging entries RTLogging=0 ORLogging=1  6) Change it to RTLogging=1 ORLogging=0 The logging should now go to project level log files instead of xmeta DB. Note: We still need to rely on Director client to verbose the log information as the log files data are in binary form. @DataStage