The best reasons why CHECK-pending state happens in DB2

The number one is referential integrity issue:

  • RECOVER to a point in time

Also Read : DB2 different Pending States and Descriptions

Table check violations place a table space or partition in
CHECK-pending status when any of the following conditions exist:

  • A check constraint is defined on a populated table by using the ALTER TABLE statement, and the value of the CURRENT RULES special register is DB2®.
  • The LOAD utility is run with CONSTRAINTS NO, and check constraints are defined on the table.
  • CHECK DATA is run on a table that contains violations of check constraints.
  • A point-in-time RECOVER introduces violations of check constraints.
  • An index might be placed in CHECK-pending status if you recovered an index to a specific RBA or LRSN from a copy and applied the log records, but you did not recover the table space in the same list. The CHECK-pending status can also be set on an index if you specified the table space and the index, but the recovery point in time was not a point of consistency (QUIESCE or COPY SHRLEVEL REFERENCE).

Corrective action or Solution

  • Run the CHECK DATA utility.
  • If a table space is in both REORG-pending and CHECK-pending status (or auxiliary CHECK-pending status), run the REORG TABLESPACE utility first and then run CHECK DATA to reset the respective states.

Best reasons why people not become expert in Linux

How did you become a Linux expert and what advice do you have for those starting out?
I’ve used Linux on my personal computers since as early as 1995 or 1996 and started working with Linux professionally in 1999. I was immediately drawn to Linux. It was love at first sight for me.

Machine Learning Jobs
Machine Learning Jobs

The Linux design and philosophy made total sense to me, and I wanted to learn everything I could about it.

I started using Linux daily and set out to get a job using Linux. Since then I’ve used Linux in almost every type of situation imaginable: at large well-known corporations, at small privately owned companies, at a startup, at a security firm, at an airline, and at a university supporting researchers.

I’ve run Linux on hardware, in virtual machines, in containers, and in the cloud. I’ve done so many things with Linux it’s hard to list them all.

Also Read: The best course on Linux

Why many people fail to learn Linux

  1. My advice to those who are starting out is to use your time wisely.
  2. I see so many people wasting precious time searching for free videos and reading random blog posts trying to cobble together their own Linux curriculum.
  3. The result is usually hours, days, or even months spent learning unrelated bits and pieces with no clear structure and no real progress to show for their work.
  4. I highly recommend taking a course that uses a logical and systematic approach so you learn things in an order that makes sense. This way you can build upon your knowledge.
  5. Another common mistake is spending a lot of time trying to find the “perfect” Linux distribution and worrying about the choice. It’s way more important that you just start learning Linux. Linux is Linux at the core, and the concepts you learn when starting out apply to every Linux distribution. Pick one and get started!

How Crontab the best way in scheduling jobs simplified

A crontab file contains entries for each cron job. Entries are separated by newline characters. Each crontab file entry contains six fields separated by spaces or tabs in the following form:

minute  hour  day_of_month  month  weekday  command

Also Read: The best Job Scheduling Interview Questions

These fields accept the following values:

Item Description
minute 0 through 59
hour 0 through 23
day_of_month 1 through 31
month 1 through 12
weekday 0 through 6 for Sunday through Saturday
command a shell command

You must specify a value for each field. Except for the command field, these fields can contain the following:

  • A number in the specified range. To run a command in May, specify 5 in the month field.
  • Two numbers separated by a dash to indicate an inclusive range. To run a cron job on Tuesday through Friday, place 2-5 in the weekday field.
  • A list of numbers separated by commas. To run a command on the first and last day of January, you would specify 1,31 in the day_of_month field.
  • A combination of two numbers separated by a dash to indicate an inclusive range and a list of numbers separated by commas can be used in conjunction. To run a command on the first, tenth to sixteenth and last day of January, you would specify 1,10-16,31 in the day_of_month field. The above two points can also be used in combination.
  • An * (asterisk), meaning all allowed values. To run a job every hour, specify an asterisk in the hour field.

Note: Any character preceded by a backslash (including the %) causes that character to be treated literally. The specification of days may be made by two fields (day of the month and day of the week). If you specify both as a list of elements, both are adhered to. For example, the following entry:

0 0 1,15 * 1 command

would run command on the first and fifteenth days of each month, as well as every Monday. To specify days by only one field, the other field should contain an * .

Specifying Commands

The cron daemon runs the command named in the sixth field at the selected date and time. If you include a % (percent sign) in the sixth field, the cron daemon treats everything that precedes it as the command invocation and makes all that follows it available to standard input, unless you escape the percent sign (\%). Blank lines and lines whose first non-blank character is the number sign (#) will be ignored. If the arguments to the command have a backslash (‘\’), the backslash should be preceded by another backslash.