Something about DataStage, DataStage Administration, Job Designing,Developing, DataStage troubleshooting, DataStage Installation & Configuration, ETL, DataWareHousing, DB2, Teradata, Oracle and Scripting.
Showing posts with label Utility. Show all posts
Showing posts with label Utility. Show all posts
Wednesday, February 26, 2014
Get DataStage Job Information without using Director
With the help of this script, You can get the job no, category and other information without opening DataStage Director.
This Script need two arguments :
1. DataStage Project Name
2. DataStage Job Name
Script :
Labels:
Administration
,
commands
,
DataStage
,
DBMS
,
dsenv
,
Information
,
Job
,
Linux
,
Script
,
SQL
,
status
,
Troubleshoot
,
Unix
,
Utility
,
UV
Saturday, August 17, 2013
Search the string in the file : Linux/Unix
Here, I am going to share a small shell utility which will ask source file name and the pattern which need to be searched in file and give the formatted output with the line no with line. You can select the no of lines which display before and after the string.
Thursday, January 10, 2013
How to delete DataStage jobs at the command line
1. Login
to the DataStage Administrator. Select the Project and click the Command
button. Then execute the following command:
LIST DS_JOBS <job_name>
Monday, December 24, 2012
The Unix "SCRIPT" command : a command recorder
script is a standard Unix command that records a script of
your interaction with the Unix system. Once it's started, it works "in the
background", meaning that you continue to work normally, but the script
session is dumping everything that shows up on your screen (more or less*) into
some file. It probably would be better called carbon-copy.
The most
common use of script is to document terminal session. By running script you
log all the information displayed on your terminal. You can then print the log
file or view it with an editor. In a way script is a specialized tee for the
shell.
Friday, July 27, 2012
DataStage huge logs removal resolution
Problem – While running the Jobs in
DataStage, sometimes the log becomes so huge that the jobs hangs down.
Sometimes when the Job is aborted, even then the Warnings keep on generating
for a long time. And this increases the log messages for that job, subsequently
increasing the table saving information in the Metadata database.
This
increases the size of the table and the database tremendously.
Monday, July 23, 2012
Resetting the XMETA password in InfoSphere Information Server
On Unix/Linux:
IBM/InformationServer/ASBServer/bin/AppServerAdmin.sh -db -user
xmeta -password <your password>
Saturday, July 14, 2012
How to deploy a configuration file in DataStage
Hi Friends
Now how to Deploy/Apply the Conf file.
Deploying the new configuration file
Now that you have created a new
configuration file, you use this new file instead of the default file. You use
the Administrator client to deploy the new file. You must have DataStage® Administrator privileges to use the
Administrator client for this purpose.
Labels:
Administration
,
Configuration
,
DataStage
,
deploy
,
ETL
,
file
,
tips
,
Utility
Friday, July 13, 2012
DataStage tip for beginners: developer short cuts
Hi guys,
Last night I am googling for some shortcut to execute jobs, some tool
tricks. I found this another great Article by Vincent McBurney. So sharing that
here with you all…will join you soon with the DS command line tricks.
Import Export
* When you do an export cut and paste the export file name. When you go to your project and run an import paste the file name instead of having to browse for it. While export and import independently remember the last file name used they do not share that name between each other.
* When you switch
export type between category and individual job it is quick to switch the type,
close the export form and open it again. That way the job name or category you
have highlighted will be automatically picked.
There is an Export option to export by individual job name or export by category name. This is on the second tab in the export form. Often when you go to export something it is on the wrong option,
There is an Export option to export by individual job name or export by category name. This is on the second tab in the export form. Often when you go to export something it is on the wrong option,
Labels:
Administration
,
copy
,
DataStage
,
ETL
,
export
,
import
,
Job
,
modify
,
sequence
,
stages
,
switch
,
transformer
,
Utility
,
Vincent McBurney
Wednesday, July 11, 2012
Vmstat : Monitoring Virtual Memory
Virtual Memory :
Using a disk as an extension of RAM so that
the effective size of usable memory grows correspondingly
How Virtual Memory Works
Physical memory—the actual RAM installed—is a finite resource on any system. As we know All processes use memory, but each process doesn't need all its allocated memory all the time. Taking advantage of this fact, the kernel frees up physical memory by writing some or all of a process' memory to disk until it's needed again.
When pages are written to disk, the event is called a page-out, and when pages are returned to physical memory, the event is called a page-in. A page fault occurs when the kernel needs a page, finds it doesn't exist in physical memory because it has been paged-out, and re-reads it in from disk.
Page ins are usual, so no need to worry about these, but Page out have. When Kernel got to know that we are running low on Physical memory then it start searching defined virtual space in Hard Disk and write the processes in there. Sometimes Kernel is quite busy with these task, fetching n inserting pages, and unable to give more resource to process running in front.
For tracking the memory status we use “VMSTAT” command.
By default vmstat displays the memory information in kb
A) If we simply execute the “vmstat” command on the terminal
$ vmstat
This will give the current status of Virtual Memory and quit.
·
kthr
– r: Total number of processes waiting to run
·
kthr
– b: Total number of busy processes
·
Memory
– avm: Active virtual pages
·
Memory
– free: Free virtual memory
·
Page – re: Pager input/output list
·
Page
– pi: Pages paged in from paging space
·
Page
– po: Pages paged out to paging space
·
Page – fr: Pages freed (page replacement)
·
Page
– sr: Pages scanned by page-replacement algorithm
·
Page
– cy: Clock cycles by page-replacement algorithm
·
Faults
– in : Device interrupts
·
Faults
– sy : System calls
·
Faults
– cs : Kernel thread context switches
·
Cpu
– us : User time
·
Cpu
– sy : System time
·
Cpu
– id : CPU idle time
·
Cpu
– wa : CPU idle time during which the system had I/O or disk request
·
Cpu
– pc : Number of physical processors consumed
·
Cpu
– ec : The percentage of entitled capacity consumed
B) To get the Virtual memory status in every 3 seconds
$ vmstat 3
This command will generate the result in every 3 sec for infinity times. For stopping the output we can use Ctrl-C
C) To get the Virtual memory status in every 2 seconds with 10 update only
$ vmstat 2 10
D) Display number of forks since last boot
$ vmstat –f
E) Displays the number of interrupts taken by each device since system startup
$ vmstat –i
F) Display the Sum of event in readable format
$ vmstat –s
display the sum of events, which contains an absolute count of paging events since system startup.
G) Display the various statistics
$ vmstat –v
H) To increase the width of output
$ vmstat –w
The default output without increasing the width
For more detailed information about “VMSTAT” go to this link
VMSTAT
njoy the simplicity.......
Atul Singh
Tuesday, July 10, 2012
File System Monitoring Script in NIX
Hi
Friends,
Here
I am come up with second FS monitoring script, this script sent you the list of
FS which
Have
the FS size more then the THRESHOLD value you defined.
njoy the simplicity.......
Atul Singh
Labels:
Administration
,
Code
,
commands
,
Linux
,
shell scripting
,
Unix
,
Utility
Verify DB2 is available or Not
In
this post, telling you the 3 method to know if DB2 is available or not.
Method
1
Log onto
the server and execute db2start as the instance owner. If
the instance is running you’ll see , something like:
$ db2start
07/10/2012 23:36:14 0 0
SQL1026N The database manager is already active.SQL1026N The
database manager is already active.
Method 2
Log onto
the server a run a netstat –a/ NETSTAT -a. This
lists all TCP/IP connections. Look for the instance names or the ports , such
as :
$ netstat –a |
grep –i db2
tcp
0 0
*:db2c_db2a
*:*
LISTEN
tcp 0 0 *:db2c_db2b *:* LISTEN
tcp 0 0 *:db2c_db2c *:* LISTEN
tcp 0 0 *:db2c_db2d *:* LISTEN
tcp 0 0 *:db2c_db2e *:* LISTEN
tcp 0 0 *:db2c_db2b *:* LISTEN
tcp 0 0 *:db2c_db2c *:* LISTEN
tcp 0 0 *:db2c_db2d *:* LISTEN
tcp 0 0 *:db2c_db2e *:* LISTEN
Method 3
On the Linux command line , issue the command :
$ ps aux | less |
grep 'db2sysc'
If you see
similar to this reponse – then the DB2 servers are running.
db2test
13474 0.1 11.3 8860292 3506408 ? Sl Jul07 24:49 db2sysc 0
db2dba 13823 0.0 0.9 1858144 279532 ? Sl Jul07 9:09 db2sysc 0
db2dba 13823 0.0 0.9 1858144 279532 ? Sl Jul07 9:09 db2sysc 0
njoy the simplicity.......Atul Singh
Tuesday, July 03, 2012
DB2 problem determination using db2top utility
Hi
guys,
Last
night someone asked me about db2top command. After going through a long
discussion we googled and found This nice tutorial on the db2top command so
sharing this to you also. will come back with more...
DB2
problem determination using db2top utility
njoy the simplicity.......
Atul Singh
Monday, June 25, 2012
Subscribe to:
Posts
(
Atom
)