Skip to main content

Removing IBM DB2 products using the db2_deinstall command (UNIX) - Middleware News


This task provides steps for removing DB2 Version 8 products using the db2_deinstall command. The db2_deinstall command removes all DB2 products from your system. If you want to remove a subset of DB2 products, use your operating system's native tools to remove DB2 components, packages, or file sets.
PrerequisitesBefore you remove DB2 products from your UNIX system:
  • Ensure that you have performed all steps outlined in Removing DB2 on UNIX before removing DB2 products from your UNIX system.
  • You must have root authority to remove DB2 products.
  • You will need your product CD-ROM to use the db2_deinstall command. The db2_deinstall command is found in the root directory on the DB2 Version 8 product CD-ROM.
ProcedureTo remove DB2 products from your UNIX system:
  1. Log in as user with root authority.
  2. Mount the DB2 Version 8 product CD-ROM.
  3. Run the db2_deinstall -n command from the root directory of your DB2 Version 8 product CD-ROM. The -n parameter makespkgrm non-interactive. The -n parameter is only on System V (Solaris).This command will remove all DB2 products from your system.
There are alternative methods for removing DB2 products from your operating system. You may employ one of these methods if you only want to remove a subset of DB2 products from your system. Alternative methods for removing DB2 products include:
AIX
You can use the System Management Interface Tool (SMIT) to remove some or all DB2 products. If you use SMIT to remove DB2, DB2 Version 8 products can be identified by their prefix of db2_08_01. You can also remove all DB2 products from AIX systems using theinstallp command by entering installp -u db2_08_01.
HP-UX
You can use the swremove command to remove some or all DB2 products.
Linux
You can use the rpm command to remove some or all DB2 products.
Solaris Operating Environment
You can remove some or all DB2 products using the pkgrm command.

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w