Prevention policy for DB2

I need a solution

I see under the AIX prevention the only DB prevention policy for MySQl.  Is there a best practice or template  for DB2? We are trying to set up prevention for an AIX 7.2 server running IBM DB2. We have a policy in place for the  OS – but want one geared toward the Data Base.

0

Related:

Netwoker Client Direct Backup not Working

Hi,

We have the NW 9.1 deployed on a VM. OS is Win 2012 R2. We are expecting backup slowness on our DB client. It contains ~1.4 TB data. We are use the client direct for backup the data to DD. To investigate this issue we have rendered the daemon.raw file in the NW server and go through it. Then we are able to identified client direct backup it not happening. Pls refer the below log output.

70896 9/19/2018 4:00:50 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001)

91797 9/19/2018 4:00:50 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device ‘DWHDD1_Digital_Banking_Prod_DB’; setting up traditional save for save-set ID ‘3600907418’ (prdbsvr1:DB2:/PB_PROD/NODE0000)

71659 9/19/2018 7:44:12 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 done saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001) 1358 GB

70896 9/19/2018 7:44:15 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool ‘Digital_Banking_Prod_DB’ (DigitalBankingProdDB.001)

91797 9/19/2018 7:44:15 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device ‘DWHDD1_Digital_Banking_Prod_DB’; setting up traditional save for save-set ID ‘2124525815’ (prdbsvr1:DB2:/PB_PROD/NODE0000)

Then we have check the connectivity between the client and DD vice versa. Connectivity is fine. And we are use the dedicated VLAN for the backup purpose. That means all the backup clients and DD are in the same range.

How can we solve this issue. Pls advised.

Related:

Re: DataDomain with IBMI Direct-Connection

Hardware

Switched connectivity supported by the host operating system. Please verify with Compatibility Guide.

Power 8 hardware: Direct or FC Switch connect

  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 8 drives on each port)
  • EN0A/577F- 16Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required
  • EN0B/577F- 16Gb PCIe2 “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required

Power 7 hardware: Direct or FC Switch connect

  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0 :(best practice is 4 drives on each port)
  • 5749/576B – 4Gb PCI-x “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0:(best practice is 8 drives on each port)
  • 5273/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.0, v6.1.1, v7.1.0, v7.2.0::(best practice is 8 drives on each port)
  • EN0A/577F- 16Gb PCIe “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port) FC Switch required
  • EN0B/577F- 16Gb PCIe2 “SmartIOA” IBM i v7.1.0, v7.2.0:(best practice is 10 drives on each port)

Power 6 hardware: Direct or FC Switch connect with Smart IOA

  • 5761/280D – 4Gb PCI-x HBA (best practice is 4 drives on each port)
  • 5704/5704 – 2Gb PCI-x HBA IBM i v5.4.5, v6.1.1:(best practice is 2 drives on each port) IOP 2844 & FC Switch required
  • 5774/5774 – 4Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5749/576B – 4Gb PCI-x “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 4 drives on each port)
  • 5735/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 8 drives on each port)
  • 5273/577D – 8Gb PCIe “SmartIOA” IBM i v6.1.1, v7.1.0:(best practice is 8 drives on each port)

Power 5 hardware: NO Direct, FC switch required

  • 5761/280D – 4Gb PCI-x HBA (best practice is 4 drives on each port) IOP 2844 & FC Switch required
  • 5704/5704 – 2Gb PCI-x HBA IBM i v5.4.5, v6.1.0, v6.1.1:(best practice is 4 drives on each port) IOP 2844 & FC Switch required

The 5704 and 5761 IOAs support a maximum of 16 devices per card (IOP 2844 & FC Switch required to use on DD)

The 5774, 5749, 5735, 5273, EN0A & EN0B Smart-IOA’s (2 ports) support a maximum of 64 devices per port, and 128 per card, with a limit of 32 devices per tape library device

Software

The IBM i License for the VTL will need to be installed before starting any VTL connections.

It is recommended to set the Auto Configure System Value QAUTOCFG (Auto configure Devices) to 1 during the configuration of new tape devices. To change the system value from the command line enter the command CHGSYSVAL SYSVAL(QAUTOCFG) VALUE(‘1’). This value can be changed back after the configuration of the tape library and devices.

Tape Management Applications

Data Domain VTL for IBM i supports the following tape management applications along with the Native CL commands:

  1. IBM Backup and Recovery Media Services (BRMS) @ i5/OS, IBM i v5.4.5, v6.1, v6.1.1, v7.1, v7.2 and v7.3.0.
    1. Since BRMS is a licensed program product, the operating system release level will determine the BRMS release level, which is consistent with the OS level.
  2. Help Systems Robot/SAVE v12.13; only on i5/OS v7.2.0, v7.1.0 & v6.1.1

Help Systems Robot/SAVE v11.32; only on i5/OS v5r4m5, IBM i 6.1.0 & v6.1.1.

  1. LXI Enterprise Storage (MMS) v5.4.3; only on i5/OS v7.1.0 & v6.1.1, v6.1.0.

PTFs

To display individual PTFs level with a MF prefix type the follow command DSPPTF and press Enter. Look for “Release of base option”, this is the level of the hardware.

To display individual PTFs with a SI prefix type the follow command DSPPTF and press Enter TWICE. Look for “Release of base option”, this is the level of the software.

IBM i PTF (Software Patches) Levels

Table 129 IBM i PTF (SW patches) Levels

V5R4M5

V6.1.0

V6.1.1

V7.1.0

V7.2.0

Cumulative

12094

14197

14197

14283

14276

Hiper

203

186

186

125

18

DB2 for IBM i

33

32

32

32

3

Backup Recovery solution

57

52

52

39

5

Tech Refresh Level

9

1

Note

EMC supports legacy PTF levels up to what is listed in the table. Customers do not have to

be at the levels shown in the table to receive support.

V5R4M5

V5R4M5 requires PCI-x based HBAs with a separate IOP for Fiber Tape connectivity. The IOP based 5704 and 5761 are the only HBAs that are supported on V5R4M5 of i/OS.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended lowest PTF levels are:

SF99540 Cumulative PTF Package: Level 10117 (C0117540)

SF99539 Group HIPER: Level 129

SF99504 DB2 for IBM i: Level 26

SF99186 Backup Recovery Solutions: Level 32

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.



v6.1.0

V6R1M0 has been qualified to use the 5704 and 5761 IOAs on Power5 hardware, while Power6 hardware allows the use of either 5704/5761 or the “SmartIOA” cards, 5749 / 5774 / 5735. EMC highly recommends the use of the SmartIOA to get the best possible throughput when running Tape jobs. A SmartIOA also gives a larger number of VTL tape emulations for more processing resources. The latest Cumulative package should have all PTFs required for Old IOAs but if the SmartIOA is used the following will apply.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended Lowest PTF levels are:

Cumulative: SF99610

Release:

V6R1M0

Abstract:

Cumulative PTF package C1256610

Level:

11256

Oct 13, 2011

Group: SF99609

Release:

V6R1M0

Abstract:

Group Hiper

Level:

00110

Dec 6, 2011

Group: SF99601

Release:

V6R1M0

Abstract:

DB2 for IBM i

Level:

00021

Oct 8, 2011

Group: SF99187

Release:

V6R1M0

Abstract:

Backup Recovery Solutions

Level:

00024

Nov 30, 2011

However if the client cannot apply these levels above, then they can apply the minimal subset supplied below:

MF54179

MF53670

MF53550

MF52469

MF52324

MF52219

MF51777

MF51773

MF51356

MF50808

MF50176

MF46933

MF46409

v6.1.1

V6R1 has been qualified to use the 5704 and 5761 IOAs on Power5 hardware, while Power6 hardware allows the use of either 5704/5761 or the “SmartIOA” cards, 5749 / 5774 / 5735. Power7 hardware requires the use of the “SmartIOA” cards and V6.1.1 of the operating system.

The latest Cumulative, HIPER and Database PTF packages should be applied, in addition to the BRS group PTF package. Recommended Lowest PTF levels are:

SF99610 Cumulative PTF Package: Level 10215 (C0215610)

SF99609 Group HIPER: Level 70

SF99601 DB2 for IBM i: Level 15

SF99187 Backup Recovery Solutions: Level 16

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.

Also, ensure the following individual PTFs are applied on V6.1.1 while using Smart IOAs:

There is no support for i6.1.1 in combination with applied PTF MF50093. If not needed do not apply!

SI36084

SI35218

SI34026

SI32538

MF50751

MF50691

MF50671

MF50587

MF49463

MF49458

MF49246

MF49234

MF47237

Review the Informational APAR for PTF requirements on the IBM website for the latest PTF requirements for Smart-IOAs:

II14355 – PTF PREREQUISITES AND SPECIFIC SUPPORT DATES FOR THE SMART-IOA (IOPless) FIBRE CHANNEL, SAS, and SCSI LVD ADAPTERS SUPPORT:

http://www-01.ibm.com/support/docview.wss?uid=nas27f65244c38e39c46862573cb0041f343



V7.1.0 , V7.2.0, V7.3.0

Fully supported with Data Domain OS 5.2 and Higher

V7.1.0, V7.2.0 & V7.3.0 has been qualified to use the “SmartIOA” cards.

Power 7 and Power 8 hardware has been qualified to use the “SmartIOA” cards listed above.

Required PTF due to IBM i OS FC failover:

PTF MF61618 for i 7.2

PTF MF61619 for i 7.3

To Display the current PTF levels on the operating system from the command line enter the command WRKPTFGRP. Press F11 to display the text description of the PTF Groups and use option 5 to display the PTF level.

VIOS (Virtual IO Server)

Fully supported with Data Domain OS 5.2.

Virtual Input Output Server, also known as PowerVM. PowerVM is a virtualization layer

supporting the IBM i on blades and the Power6 platform at V6.1 and above. VIOS can only connect with the Data Domain System through a NPIV Switch and a 5735/577D – 8Gb PCIe “SmartIOA” card.

  • Data Domain OS v5.2 and higher supports
    • IBM VIOS versions: v2.1.x & v2.2.x
    • IBM i OS: v6.1.0, v7.1.0, v7.2.0, & V7.3.0
    • Only IOA supported: 5735/577D – 8GB PCIe “SmartIOA”



The IBM i License for the VTL will need to be installed before starting any VTL connections.

The IBM i utilizes a hardware virtualization layer commonly referred to as the Licensed Internal Code, or LIC, to provide access from the operating system to physical hardware. All peripheral equipment must emulate IBM equipment, including IBM tape libraries and devices, when presented to the operating system.

Additionally, there are no hardware drivers used by i/OS. All drivers are embedded in the LIC, or in LIC PTFs, or Program Temporary Fixes. In most cases, hardware configuration settings cannot be manually configured, as only IBM or IBM emulated equipment will be attached, requiring only fixed configuration settings.

Fiber Channel devices can be connected directly to IBM i host through an arbitrated loop (FC-AL) topology or through a switched fabric (FC-SW) topology, the DD VTL supports both switched fabric for connectivity or direct connect. The IBM i Fiber Channel host bus adapters or IOAs (Input / Output Adapters) can negotiate at 2 GB, 4GB, and 8GB speeds in a FC-SW environment without any configuration on the operating system other than plugging in the cable at the host.

While the IBM i HBAs support switched or direct connection for tape, the Data Domain VTL can also use switched connectivity or direct connect. Switched connectivity also allows access to a greater number of HBAs and increase flexibility and scalability, as well as the ability to share a single library among multiple systems.

A zone is comprised of a set of devices that access one another, in an initiator to target model. It is required that only one target and one initiator be in each VTL zone. Additional HBAs may be assigned to a VTL HBA by adding another zone. Soft zoning is recommended, in which the zone will consist of the WWPN or alias of one of the HBA ports on the Data Domain VTL, and the WWPN or alias of one of the IBM i HBA ports. Zones are then added to a zone set and activated.

4 Gb or 8 Gb switches are recommended for connectivity to IBM i. The list of IBM i qualified switches are listed in the IBM interoperability matrix.

Once the cabling of the VTL and the IBM i HBA has been completed, create appropriate tape zones with one initiator and one target: the WWPN of the VTL HBA and the WWPN of the IBM i HBA. The IBM i does not allow multiple paths to tape devices, so the zoning for each library or tape device should consist of only one initiator and one target.

Related:

7022962: Mail relay not working with SLES11 postfix

This document (7022962) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)

Situation

Customer has a SLES11 SP3 server and when they configure postfix to relay mail to another SMTP server, it fails to relay the mail message and shows an error in the /var/log/mail log file, the error is :

May 1 18:24:21 USA-US-X1015 postfix/smtpd[29037]: NOQUEUE: reject: RCPT from unknown[10.43.64.178]: 451 4.3.0 <john.smith@mycompany.com>: Temporary lookup failure; from=<john.smith@mycompany.com> to=<john.smith@mycompany.com> proto=ESMTP helo=<mycompany.com>

Resolution

It was discovered in the problem server “main.cf” file there as an invalid ip address range listed in the

“mynetworks” parameter. Of the 28 ip address ranges listed in this parameter, one was invalid, it was :
10.205.149/0/24
It should be :
10.205.149.0/24
Once this was corrected and postfix restarted, the problem went away.

Cause

Invalid ip address range in the postfix main.cf configuration file.

Additional Information

A clue to this solution was listed in the error one line above the error listed in the “Situation” section of this

technical document, it was :
postfix/smtpd[29037]: warning: bad net/mask pattern: “10.205.149/0/24”

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7021498: Using the Show Host Files File Transfer Dialog in Reflection Desktop 16, Reflection 2014, or Reflection 2011

The Show Host Files feature makes it possible to quickly retrieve a list of host file names from a 3270 IBM Host system. The host files are displayed in a tree view, and the display you see depends on the protocol selected. Reflection displays only those files that can be transferred using the currently selected transfer protocol.

Note: Show Host Files is not available if you are connected to a CICS host.

To use Show Host Files:

  1. Connect a configured terminal session using Reflection Desktop 16, Reflection 2014 or Reflection 2011, and logon to your host.
  2. In the Transfer group on the Session ribbon, click File Transfer.
  3. In the Transfer dialog box, click Setup. On the Protocol tab, select Mainframe under Protocol and select the proper system type (CMS or TSO) under Host system. Click OK.
  4. Click the Show Host Files button.

Using the Show Host Files Feature on CMS and TSO Systems

The process that Reflection uses to display a list of host files on the workstation differs between CMS and TSO systems.

CMS

On a CMS system, the Show Host Files button executes the LISTFILE command through the terminal session. The output of LISTFILE is then used to populate the Show Host Files list box with file names.

TSO

On a TSO system, the Show Host Files button executes the LISTCAT command through the terminal session. The output of the LISTCAT command is then used to populate the Show Host Files list box with file names.

Note: Some prior versions of Reflection required you to upload two Attachmate-supplied REXX execs to TSO to support the Show Host Files function. These files (WRQLDS and WRQLCAT) are no longer needed.

Troubleshooting Show Host Files Problems

If clicking the Show Host Files button does not display the host file list, follow these troubleshooting procedures in the order they are presented.

Verify Your Host Connection

Verify that you are connected to the host and that the correct system (CMS or TSO) has been selected. Follow these steps to change the system type, if necessary:

  1. On the Reflection Session ribbon, click File Transfer in the Transfer group.
  2. In the center of the Transfer dialog box, click the Setup button.
  3. On the Transfer Setup > Protocol tab, select Mainframe under Protocol and select the proper system type (CMS or TSO) under Host system. Click OK.

Verify That the Host Screen Can Accept Input

Verify that the host screen can accept and process command input. Not all host screens can accept commands. Being at the CMS or TSO command prompt is preferred, but you may also be in ISPF if you use Option 6.

Verify the CMS Command

If you are on a CMS system, logon to your host and enter the following command at the Ready; prompt:

LISTFILE

If you receive an error when attempting to run LISTFILE, contact your system administrator for assistance.

If the command runs without generating an error, contact Micro Focus Customer Support to trouble-shoot further problems with the Show Host Files functionality.

Verify the TSO Command

If you are on a TSO system, logon to your host and enter the following command at the READY prompt:

LISTCAT

If you receive an error when attempting to run LISTCAT, contact your system administrator for assistance.

If the command runs without generating an error, contact Micro Focus Customer Support to trouble-shoot further problems with the Show Host Files functionality.

Related:

Re: Li-ion SPS modules

The Li Ion SPS is a FRUable 10-lb battery, removed from the front of the system. The SPS transports separately and will be part of the install procedure. SPS units have 2.2KW capacity, and provide two five-minute intervals of battery life to allow vaulting in the event of a power failure. In System Bay 1 of a single engine bay, there are up to two SPS trays (four SPSs total) to support the engine and Fabric, if installed. In System Bays 2 through 8, there is only one SPS tray (two SPSs) to support the engine.

When installed in System Bay 1, SPS 1A and 1B are cabled to both the engine and the fabric, and SPS 3A and 3B are also cabled to both the engine and the fabric. This is true in multi-engine systems only. In single engine systems, SPS 3A and 3B support the engine only.

Related:

cluster9.us.messagelabs.com Connection timed out

I need a solution

Dear Support,

Our mail server with IP addresses 175.144.213.75 (are not blacklisted and with good reputation) can not send email to our customers and suppliers who use messagelabs.com
It maybe block by messagelabs.com 
Please help us.

Here the sample of report:

Reporting-MTA: dns; mail.destinigroup.com
X-Postfix-Queue-ID: C02A02B1DEA
X-Postfix-Sender: rfc822; akma@destinigroup.com
Arrival-Date: Wed, 25 Apr 2018 14:22:14 +0800 (MYT)

Final-Recipient: rfc822; ewong7@lenovo.com
Original-Recipient: rfc822;ewong7@lenovo.com
Action: failed
Status: 4.4.1
Diagnostic-Code: X-Postfix; connect to
    cluster9.us.messagelabs.com[216.82.249.35]:25: Connection timed out

Thank you!
Regards,

Amir Rosli.

0

Related:

Re: VNX SPS replacement – is it non-disruptive?

Hi,

I’ve got a VNX5100 with two SPs and two SPSs and one of the SPSs has failed.

The array is continuing to operate as normal and the write cache is enabled.

Can anyone confirm if the SPS replacement is non-disruptive and if there is a documented procedure for doing the replacement?

I’ve tried to find a procedure on SoLVe but there does not seem to be anything for SPSs.

My understanding of the SP and PSU design is that the PSUs are connected to the SPSs (one PSU per SPS) and power a common power bus in the DPE enclosure from which the SPs and drives draw power. This allows both for non-disruptive PSU replacement and I think non-disruptive SPS replacement. I’d like this confirmed before doing the actual replacement.

We are assuming/hoping but want confirmation that we can do the following:

  • with SPS A functional and SP A and SP B operating
    • power off SPS B using its power switch
    • SP B will continue to operate as it will continue to receive power via SPS A via SP A and the common power bus
    • disconnect SPS B
    • remove SPS B
    • insert replacement SPS
    • connect replacement SPS
    • power on replacement SPS

Can anyone confirm this?

Related: