Posts

Showing posts from August, 2015

Unable to open Cognos Configuration after a change in the Java on the Cognos Server.

Problem(Abstract) Unable to open Cognos Configuration after a Java change on the Cognos Server. Symptom Cognos Configuration was unable to successfully use the cryptographic information with the current Java Runtime Environment located in <location>/cognos/crn/bin/jre/1.3.1 The cryptographic information may have been corrupted or the Cognos Configuration tool is not running with the Java Runtime Environment that generated the cryptographic information: <location>/cognos/crn/bin/jre/1.3.1.Original Cause The Encryption keys were created against either an older version of Java or the JAVA_HOME variable was changed Resolving the problem Recreate the Encryption keys in crn/configuration directory and restart the services. For Cognos 8, the Encryptions keys are located in c8/configuration Steps: 1. Stop CRN services 2. Navigate to crn/configuration 3. Backup and remove the following folders a...

Unable to log into cognos due to internal server errors

Problem(Abstract) When attempting to log into cognos an internal server error is returned after entering the username and password. No errors recorded in the cognos logs. In the web servers log something like this is recorded: Premature end of script headers: cognos.cgi, referer: https://<server>/crn/cgi-bin/cognos.cgi Cause Encryption keys are out of sync between gateway and application servers Diagnosing the problem Error Message in web server log: Premature end of script headers: cognos.cgi, referer: https://<server>/crn/cgi-bin/ cognos.cg Resolving the problem Regenerate the keys on all gateway servers. See TechNote 1342261 for steps. Related information TechNote 1342261

Internal Server Error thrown when trying to login to Cognos

Problem(Abstract) When trying to login to Cognos 8/10, the following error message is immediately thrown after entering valid credentials: ================= Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. ================= You will also see the following error in the Apache log: [error] [client x.x.x.56] Premature end of script headers: cognos.cgi, referer: http://<hostname>/ibmcognos/cgi-bin/cognos.cgi?b_action=xts.run&m=portal/main.xts&startwel=yes Cause This typically occurs when the user running Apache has insufficient permissions to the Cognos /configuration directory Environment - Ap...

WebSphere fails to start after changing the XMETA password for Information Server

Problem(Abstract) WebSphere fails to start after changing the XMETA password for Information Server. Here is the error in the SystemOut.log file: Connection authorization failure occurred.  Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000 Symptom WebSphere fails to start. Cause Backup copies of obj-conf.jar and other ojb-conf.jar artifacts left behind in the <wasprofile>/informationServer/apps/lib and <ISInstall>/ASBServer/apps/lib directories. Diagnosing the problem Look in the SystemOut.log found in <WAS Install>/profiles/<profile name>/logs/<server name>, by default at 8.5 and above /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1, for the following errors: 12/5/12 16:07:51:112 CST] 00000000 SystemOut     O org.apache.ojb.broker.accesslayer.ConnectionFactoryAbstractImpl] ERROR: Error getting Connection from DriverManager with url ...

Change the passwords for IBM InfoSphere Information Server users on Windows

Question What is the correct procedure to change the passwords for each of my IBM InfoSphere Information Server users (wasadmin, isadmin, xmeta, iadb)? Answer There is a specific sequence that should be followed. First shutdown DataStage Services in the following order: - Information Server - WebSphere Service - DB2 Services Perform the instructions below for each user, as required, if you are using Local OS authentication. DB2Admin Open Computer Management Open Db2Admin User Change Password Change the Password for all DB2 Services to reflect this new password Open the DB2 Command Window and issue the following command: >connect to xmeta user db2admin using <password> Start DB2 Services Start Websphere Service xmeta Open Computer Management Open xmeta User Change Password Open command prompt and issue the following command: ASBServer\bin\AppServerAdmin.bat -db -user <new user name> -password <new password> Open WA...

Resetting the xmeta password in InfoSphere Information Server

Question My xmeta password expired and needed to be changed. I now see errors in SystemOut.log that my xmeta password is wrong. How can I tell WebSphere what my new xmeta password is? Answer As an admin user, you will need to run: On Unix/Linux: IBM/InformationServer/ASBServer/bin/AppServerAdmin.sh -db -user xmeta -password <your password> On Windows: IBM\InformationServer\ASBServer\bin\AppServerAdmin -db -user xmeta -password <your password>

IHS fails to load mod2_cognos.so

Problem(Abstract) Unable to start IHS (IBM HTTP Server) with Cognos Apache Mod. [ihs@slqerp03 bin]$ ./start Syntax error on line 182 of /apps/ihs/prod/conf/ihs2_cognos/conf/httpd.conf: Cannot load /apps/crn/prod/c8gate/cgi-bin/mod2_cognos.so into server: libhttpdap2_stub.so: cannot open shared object file: No such file or directory /etc/init.d/ibmhttpd20 : httpd ihs2_cognos could not be started Cause IHS cannot load the Cognos libraries in cgi-bin directory. Environment Serveur IHS Linux Red hat 5 IHS 6.1 Diagnosing the problem The LD_LIBRARY_PATH is not set correctly in the IHS scripts Resolving the problem Modify the LD_LBRAIRY_PATH in the script file "envars" to add the Cognos cgi-bin path. # envvars-std - default environment variables for apachectl # # This file is generated from envvars-std.in # LD_LIBRARY_PATH="/apps/ihs/6.1/lib:/apps/crn/prod/c8gate/bin:/apps/...

Starting and stopping Cognos in UNIX without using the Cognos Configuration GUI

Problem(Abstract) This document explains how to start and stop Cognos 8 services in Windows and UNIX without using the Cognos Configuration user interface, in much the same way as crnctl.sh works in IBM Cognos ReportNet. The crnctl.sh script was not included in Cognos 8, so that functionality is unavailable. This information is also valid for Window installs of the Cognos 8 (as per below). Resolving the problem cogconfig.sh -s ( cogconfig.bat -s for Windows) This will save and start silently. cogconfig.sh -stop ( cogconfig.bat -stop for Windows) This will stop silently. To view log messages that were generated during an unattended configuration (and start), see the cogconfig_response.csv file in the c8_location/ logs directory. The cogconfig.sh -s applies the configuration settings specified in the local copy of cogstartup.xml, encrypts credentials, generates digital certificates, and if applicable, starts the Cognos 8 ...

Start cognos on startup linux server

​ If you have cognos installed on an linux server it is nice to start cognos bi automatic when the server starts. To achieve this you have to add a script to the folder /etc/init.d After that you have to perform some commands to add cognos to the startup proces of the linux server. The following script is used to start cognos 8 on a Oracle Linux installation [Enterprise Linux release 4 (October Update 5)]: #!/bin/bash # # Description: Cognos services auto start-stop script. # Save script in: /etc/init.d as "cognos" # Perform next steps to make it autostart on powerup: # – chmod a+x cognos # – chkconfig –add cognos # – chkconfig cognos on # JAVA_HOME=/opt/IBMJava2-142/jre COGNOS_OWNER=root RETVAL=0 prog="Cognos Services" start() { echo -n $"Starting $prog: " # Start the Cognos services su – $COGNOS_OWNER -c "/opt/cognos/c8/bin/cogconfig.sh -s" RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lo...

In DataStage Designer, an error 'Specified security mechanism, (Unknown), is not supported by server' occurs when trying to connect via ODBC connector to a DB2 database

Problem(Abstract) In Designer, when testing a connection to a DB2 database within the ODBC connector, the following error occurred. ODBC function "SQL Connect" reported: SQLSTATE = HY000: Natvie Error Code = 8,339: Msg = [IBM(DataDirect OEM)][ODBC DB2 Wire Protocol driver]Specified security mechanism, (Unknown), is not supported by server. Diagnosing the problem In the DataDirect ODBC User's Guide: AuthenticationMethod (AM) Description Specifies the method the driver uses to authenticate the user to the server when a connection is established. If the specified authentication method is not supported by the database server, the connection fails and the driver generates an error. Valid Values 0 | 1 | 2 | 3 | 4 | 7 | 8 If set to 0 (No Encryption), the driver sends the user ID and password in clear text to the server for authentication. If set to 1 (Encrypt Password), the driver sends the user ID in clear text and an encr...

Information Analyzer configuration

Question How to configure Information Analyzer when IADB is a local DB2 instance? Cause After installing InfoSphere Information Server, Information Analyzer must be configured prior to its usage. Please reference the following links for further information and steps on how to configure Information Analyzer: IBM Education Assistant : http://publib.boulder.ibm.com/infocenter/ieduasst/imv1r0/index.jsp?topic=/com.ibm.iea.infosphere_is/infosphere_is/8.5/configuration/ConfiguringInformationAnalyzer/player.html InfoCenter : - Version 8.5: http://pic.dhe.ibm.com/infocenter/iisinfsv/v8r5/index.jsp?topic=%2Fcom.ibm.swg.im.iis.ia.administer.doc%2Ftopics%2Fc_setting_up_ia.html - Version 8.7: http://pic.dhe.ibm.com/infocenter/iisinfsv/v8r7/index.jsp?topic=%2Fcom.ibm.swg.im.iis.ia.administer.doc%2Ftopics%2Fc_setting_up_ia.html - Version 9.1: http://pic.dhe.ibm.com/infocenter/iisinfsv/v9r1/topic/com.ibm.swg.im.iis.ia.administer.doc/topics/c_setting_up_ia.html Regardi...

Vulnerability in RC4 (CVE-2015-2808) stream cipher affects ODBC Drivers used in IBM InfoSphere Information Server

Problem(Abstract) The RC4 "Bar Mitzvah" vulnerability in SSL/TLS might affect some of the DataDirect ODBC Drivers. Resolving the problem Add CipherList=DEFAULT:!RC4 attribute to the $DSHOME/.odbc.ini file On Linux / Unix platforms : By default, the ODBCINI environment variable points to the .odbc.ini file under $DSHOME. The .odbc.ini file used at runtime is the file pointed to by ODBCINI. To resolve the issue, the customer needs to edit this file. You can add the attribute in one of the following ways: 1. Add the attribute to each individual Data source (DSN). In this method, it is effective only for that particular DSN. 2. Add the attribute under the [ODBC] section. In this method, it is effective for all the DSNs defined in the .odbc.ini file. For example, a sample DSN showing the attribute added to the DSN. [DB2 Wire Protocol] Driver=/opt/IBM/InformationServer/Server/branded_odbc/lib/VMdb200.so Description=DataDirect DB2 Wir...

Infosphere Metadata Server Asset Manager Data Connection Test - "Failed to Load Native Library"

Problem(Abstract) When creating a new Data Connection in a new import area the data connection list is empty. Also, after manually entering server name, and selecting "Test Connection", action fails with error "Failed to load native library: fcl". Symptom Data connection server list empty when creating new data connection, and following error returned when type server name and test connection: IMAM_GUI> [CDIMR3741E] Failed to perform connection test. com.ibm.mif.ChannelException: [CDIMR0047E] There was an error testing the data connection by using the CAS/OracleConnector__10 connector. Failed to load native library: fcl (A file or directory in the path name does not exist.) at com.ibm.mif.dataconnection.DataConnectionManager.handleConnectorServiceException(DataConnectionManager.java:1699) <lines omitted> Caused by: com.ascential.asb.cas.shared.ConnectorServiceException: Failed to load native library: fcl (A fi...

DataStage "Connector Import Wizard" and "View data" in Oracle Connector fails with error "Failed to send the request to the handler: The agent at : 31531 is not available"

Problem(Abstract) DataStage "Connector Import Wizard" and "View data" in Oracle Connector fails with error "Failed to send the request to the handler: The agent at <Engine Server>: 31531 is not available" Cause - Import metadata using "Connector Import Wizard" in DataStage designer client and/or "View data" from Connector stages in the DataStage job fails when the ASB port 31531 on Engine tier is blocked in a Multi-tier environment (Repository and Services tier resides on one server and Engine tier resides on another server) - Because the "Connector Import Wizard" and "View data" request flow goes from DataStage Designer Client through ASB Agent to Connector Access Service to Connector Framework to Oracle Connector to Oracle database and then result flows back in-reverse order through all these items to GUI and/or repository (depending on the operation), so If ...

Error when trying to test connection or view data within a Datastage Connector stage

Problem(Abstract) The following error message is received from Datastage Designer client when using the test connection or view data functions within one of the Datastage Connector Stages (e.g., DB2 Connector, Oracle connector, etc): Error Message: An exception occurred while trying to send the request to the handler: The agent at <hostname>:31531 is not available. Resolving the problem This error message is indicating that the NodeAgents (ASBAgents) are not up and running and need to be restarted. Please ensure you are restarting the NodeAgents as per the following instructions: https://www-304.ibm.com/support/docview.wss?uid=swg21452589

Tuning the UVCONFIG parameters for IBM InfoSphere Information Server Workload Management

Question How do I tune the UVCONFIG parameters for IBM InfoSphere Information Server Workload Management to support running and queueing a large number of jobs Answer When IBM InfoSphere DataStage jobs are started or are queued, locks are created to prevent: 1. the deletion of the job while it is running or is in a queue. 2. the deletion of the project while the job is running or is in a queue. The lock table size is defined by the RLTABSZ tunable in the UVCONFIG file. The job also opens and reads status and run time information for the job from several dynamic hashed files. The dynamic hashed file handle limit is defined by the T30FILE tunable in the UVCONFIG file. The default size for the lock table is 300 and the default limit for the file handle is 512. With the default settings, approximately 150 jobs can be running and/or queued concurrently in the system. To increased the number of jobs that can be running or queued, the RLTABSZ and...

InfoSphere DataStage: How to calculate the value for the T30FILE parameter in uvconfig?

Question How do I calculate the value for the parameter T30FILE in the uvconfig file? Answer The T30FILE parameter in the uvconfig file specifies the number of dynamic files that may be opened concurrently in DataStage Server. This setting is system wide, not by project. Some examples of dynamic files are the repository files (such as job's logs, status, and config files) and also the hash files you can create using server jobs. By default, this value is set to 200 but a system running multiple jobs concurrently may need to access more than 200 dynamic files at a given time. If InfoSphere DataStage hits the limit of open dynamic files, jobs will abort and the error "Unable to allocate Type 30 descriptor, table is full" will be shown in the job's log. To solve this problem you need to stop the InfoSphere DataStage services, increase the T30FILE parameter in the $DSHOME/uvconfig file, regenerate the configuration, and t...

Automatically tune values in the uvconfig file of the server engine by using a script

Image
​ Technote (troubleshooting) Problem(Abstract) The default tunable values used for job control in IBM InfoSphere DataStage might not be sufficient in all customer environments. You can now use a script to configure particular tunable valuables in the server engine uvconfig file. The script automates the effort of changing default values to recommended values. Cause Customers that run many jobs simultaneously might need to increase tunable values to avoid job hangs or aborts. The tunable values of concern are related to locks and files, for example: MFILES, T30FILES, RLTABSZ, and MAXRLOCK. Refer to the following technote for details on these parameters ( https://www-304.ibm.com/support/docview.wss?uid=swg21412963 ). Environment The script works on all InfoSphere DataStage platforms (Windows and all flavors of UNIX). Resolving the problem The DSEtune.tar image contains two files; DSEt...

Use of the tunable parameters in the UVCONFIG file

Image
​ Question How do I use the tunable parameters in the UVCONFIG file? Answer The most commonly used parameters in the UVCONFIG file are as follows: MFILES This parameter defines the size of the server engine (DSEngine) rotating file pool. This is a per process pool for files such as sequential files that are opened by the DataStage server runtime. It does not include files opened directly at OS level by the parallel engine (PXEngine running osh). The server engine will logically open and close files at the DataStage application level and physically close them at the OS level when the need arises. Increase this value if DataStage jobs use a lot of files. Generally, a value of around 250 is suitable. If the value is set too low, then performance issues may occur, as the server engine will make more calls to open and close at the physical OS level in order to map the logical pool to the physical pool. NOTE: The OS parameter of   nofiles   needs to be set higher than MFILES. Ideally, it wou...

DataStage dsjob command fails to open job and then reports error -1004.

Problem(Abstract) The DataStage dsjob command reports error for a specific job, even if only requesting job info: dsjob -jobinfo projectname jobname ERROR: Failed to open job Status code = -1004 Resolving the problem There are 2 primary causes for this error: DataStage engine not using default port 31538 in which case the dsjob command requires -server parameter with hostname:port , for example: dsjob -server myhost:31539 -jobinfo projectname jobname Permission problem with files in the project directory that prevent the user who ran dsjob command from opening some job files. Confirm that the DataStage engine is using the default port and if not update the dsjob command to specify the actual port. If that does not resolve the issue, or if the problem only occurs for specific jobs in a project rather than all jobs, then check the project directory to confirm that all files and directories have the same correc...

IBM InfoSphere DataStage dsjob Command Returns Status code = 80011

Technote (troubleshooting) Problem(Abstract) Running dsjob utility with or without -domain option results in an error message: Status Code = 80011 Cause The dsjob utility is unable to authenticate and validate against the DataStage Engine. Resolving the problem Use -domain NONE option. For example, instead of using <DS_HOME>/bin/dsjob - domain server_name:por t -user xxxx -password xxxx -server server_name -lprojects use: <DS_HOME>/bin/dsjob - domain NONE -user xxxx -password xxxx -server server_name -lprojects Also see related information below for online references for dsjob utility

The 'Manage Group' Add User search in the Process Admin Console does not return available users for IBM Business Process Manager (BPM)

Technote (troubleshooting) Problem(Abstract) When you search for a user within the 'Manage Group' in the Process Admin Console for IBM Business Process Manager, a more specific search keyword does not result in any entries. In addition, an LDAP timeout message is added to the SystemOut.log file. Symptom When you do a broad search with a small keyword, you expect to receive many entries in return. When your search is more specific, you use a longer keyword to try to narrow the search. However, when you expect fewer returns from your search, it does not happen. The user list remains empty. You can find the following exception in the SystemOut.log file: [8/7/12 14:02:59:435 CEST] 000000xx exception     E com.ibm.ws.wim. adapter.ldap.LdapConnection search(String, String, Object[], SearchControls) CWWIM4520E  The 'javax.naming.NamingException: LDAP response read timed out, timeout used:20000ms.; Remaining name: 'DC...