Saturday, November 29, 2008

Post Code of Khulna Division in Bangladesh

District
Thana
Suboffice
Postcode
Kustia
Bheramara
Bheramara
7040
Kustia
Bheramara
Ganges Bheramara
7041
Kustia
Bheramara
Allardarga
7042
Kustia
Janipur
Janipur
7020
Kustia
Janipur
Khoksa
7021
Kustia
Kumarkhali
Kumarkhali
7010
Kustia
Kumarkhali
Panti
7011
Kustia
Kustia Sadar
Kustia Sadar
7000
Kustia
Kustia Sadar
Kushtia Mohini
7001
Kustia
Kustia Sadar
Jagati
7002
Kustia
Kustia Sadar
Islami University
7003
Kustia
Mirpur
Mirpur
7030
Kustia
Mirpur
Poradaha
7031
Kustia
Mirpur
Amla Sadarpur
7032
Kustia
Rafayetpur
Rafayetpur
7050
Kustia
Rafayetpur
Taragunia
7051
Kustia
Rafayetpur
Khasmathurapur
7052
Meherpur
Gangni
Gangni
7110
Meherpur
Meherpur Sadar
Meherpur Sadar
7100
Meherpur
Meherpur Sadar
Amjhupi
7101
Meherpur
Meherpur Sadar
Mujib Nagar Complex
7102
Meherpur
Meherpur Sadar
Amjhupi
7152
Chuadanga
Alamdanga
Alamdanga
7210
Chuadanga
Alamdanga
Hardi
7211
Chuadanga
Chuadanga Sadar
Chuadanga Sadar
7200
Chuadanga
Chuadanga Sadar
Munshiganj
7201
Chuadanga
Damurhuda
Damurhuda
7220
Chuadanga
Damurhuda
Darshana
7221
Chuadanga
Damurhuda
Andulbaria
7222
Chuadanga
Doulatganj
Doulatganj
7230
Jinaidaha
Harinakundu
Harinakundu
7310
Jinaidaha
Jinaidaha Sadar
Jinaidaha Sadar
7300
Jinaidaha
Jinaidaha Sadar
Jinaidaha Cadet College
7301
Jinaidaha
Kotchandpur
Kotchandpur
7330
Jinaidaha
Maheshpur
Maheshpur
7340
Jinaidaha
Naldanga
Naldanga
7350
Jinaidaha
Naldanga
Hatbar Bazar
7351
Jinaidaha
Shailakupa
Shailakupa
7320
Jinaidaha
Shailakupa
Kumiradaha
7321
Jessore
Bagharpara
Bagharpara
7470
Jessore
Bagharpara
Gouranagar
7471
Jessore
Chaugachha
Chougachha
7410
Jessore
Jessore Sadar
Jessore Sadar
7400
Jessore
Jessore Sadar
Jessore Upa-Shahar
7401
Jessore
Jessore Sadar
Chanchra
7402
Jessore
Jessore Sadar
Jessore canttonment
7403
Jessore
Jessore Sadar
Jessore Airbach
7404
Jessore
Jessore Sadar
Rupdia
7405
Jessore
Jessore Sadar
Basundia
7406
Jessore
Jessore Sadar
Churamankathi
7407
Jessore
Jhikargachha
Jhikargachha
7420
Jessore
Keshabpur
Keshobpur
7450
Jessore
Monirampur
Monirampur
7440
Jessore
Noapara
Noapara
7460
Jessore
Noapara
Rajghat
7461
Jessore
Noapara
Bhugilhat
7462
Jessore
Sarsa
Sarsa
7430
Jessore
Sarsa
Benapole
7431
Jessore
Sarsa
Jadabpur
7432
Jessore
Sarsa
Bag Achra
7433
Narail
Kalia
Kalia
7520
Narail
Laxmipasha
Laxmipasha
7510
Narail
Laxmipasha
Lohagora
7511
Narail
Laxmipasha
Itna
7512
Narail
Laxmipasha
Naldi
7513
Narail
Laxmipasha
Baradia
7514
Narail
Mohajan
Mohajan
7521
Narail
Narail Sadar
Narail Sadar
7500
Narail
Narail Sadar
Ratanganj
7501
Magura
Arpara
Arpara
7620
Magura
Magura Sadar
Magura Sadar
7600
Magura
Mohammadpur
Mohammadpur
7630
Magura
Mohammadpur
Binodpur
7631
Magura
Mohammadpur
Nahata
7632
Magura
Shripur
Shripur
7610
Magura
Shripur
Langalbadh
7611
Magura
Shripur
Nachol
7612
Khulna
Alaipur
Alaipur
9240
Khulna
Alaipur
Rupsha
9241
Khulna
Alaipur
Belphulia
9242
Khulna
Batiaghat
Batiaghat
9260
Khulna
Batiaghat
Surkalee
9261
Khulna
Chalna Bazar
Chalna Bazar
9270
Khulna
Chalna Bazar
Dakup
9271
Khulna
Chalna Bazar
Bajua
9272
Khulna
Chalna Bazar
Nalian
9273
Khulna
Digalia
Digalia
9220
Khulna
Digalia
Chandni Mahal
9221
Khulna
Digalia
Senhati
9222
Khulna
Digalia
Ghoshghati
9223
Khulna
Digalia
Gazirhat
9224
Khulna
Khulna Sadar
Khulna G.P.O
9000
Khulna
Khulna Sadar
Khula Sadar
9100
Khulna
Khulna Sadar
Khulna Shipyard
9201
Khulna
Khulna Sadar
Doulatpur
9202
Khulna
Khulna Sadar
BIT Khulna
9203
Khulna
Khulna Sadar
Siramani
9204
Khulna
Khulna Sadar
Jahanabad Canttonmen
9205
Khulna
Khulna Sadar
Sonali Jute Mills
9206
Khulna
Khulna Sadar
Atra Shilpa Area
9207
Khulna
Khulna Sadar
Khulna University
9208
Khulna
Madinabad
Madinabad
9290
Khulna
Madinabad
Amadee
9291
Khulna
Paikgachha
Paikgachha
9280
Khulna
Paikgachha
Godaipur
9281
Khulna
Paikgachha
Kapilmoni
9282
Khulna
Paikgachha
Katipara
9283
Khulna
Paikgachha
Chandkhali
9284
Khulna
Paikgachha
Garaikhali
9285
Khulna
Phultala
Phultala
9210
Khulna
Sajiara
Sajiara
9250
Khulna
Sajiara
Ghonabanda
9251
Khulna
Sajiara
Chuknagar
9252
Khulna
Sajiara
Shahapur
9253
Khulna
Terakhada
Terakhada
9230
Khulna
Terakhada
Pak Barasat
9231
IBH WAs Here
Bagerhat Sadar
Bagerhat Sadar
9300
IBH WAs Here
Bagerhat Sadar
P.C College
9301
IBH WAs Here
Bagerhat Sadar
Rangdia
9302
IBH WAs Here
Chalna Ankorage
Chalna Ankorage
9350
IBH WAs Here
Chalna Ankorage
Mongla Port
9351
IBH WAs Here
Chitalmari
Chitalmari
9360
IBH WAs Here
Chitalmari
Barabaria
9361
IBH WAs Here
Fakirhat
Fakirhat
9370
IBH WAs Here
Fakirhat
Mansa
9371
IBH WAs Here
Fakirhat
Bhanganpar Bazar
9372
IBH WAs Here
Kachua UPO
Kachua
9310
IBH WAs Here
Kachua UPO
Sonarkola
9311
IBH WAs Here
Mollahat
Mollahat
9380
IBH WAs Here
Mollahat
Kahalpur
9381
IBH WAs Here
Mollahat
Dariala
9382
IBH WAs Here
Mollahat
Charkulia
9383
IBH WAs Here
Mollahat
Nagarkandi
9384
IBH WAs Here
Mollahat
Pak Gangni
9385
IBH WAs Here
Morelganj
Morelganj
9320
IBH WAs Here
Morelganj
Sannasi Bazar
9321
IBH WAs Here
Morelganj
Telisatee
9322
IBH WAs Here
Rampal
Rampal
9340
IBH WAs Here
Rampal
Foylahat
9341
IBH WAs Here
Rampal
Sonatunia
9342
IBH WAs Here
Rampal
Gourambha
9343
IBH WAs Here
Rayenda
Rayenda
9330
Satkhira
Ashashuni
Ashashuni
9460
Satkhira
Ashashuni
Baradal
9461
Satkhira
Debbhata
Debbhata
9430
Satkhira
Debbhata
Gurugram
9431
Satkhira
kalaroa
kalaroa
9410
Satkhira
kalaroa
Murarikati
9411
Satkhira
kalaroa
Jhaudanga
9412
Satkhira
kalaroa
Hamidpur
9413
Satkhira
kalaroa
Khordo
9414
Satkhira
kalaroa
Chandanpur
9415
Satkhira
Kaliganj UPO
Kaliganj UPO
9440
Satkhira
Kaliganj UPO
Nalta Mubaroknagar
9441
Satkhira
Kaliganj UPO
Ratanpur
9442
Satkhira
Nakipur
Nakipur
9450
Satkhira
Nakipur
Noornagar
9451
Satkhira
Nakipur
Naobeki
9452
Satkhira
Nakipur
Buri Goalini
9453
Satkhira
Nakipur
Gabura
9454
Satkhira
Nakipur
Habinagar
9455
Satkhira
Satkhira Sadar
Satkhira Sadar
9400
Satkhira
Satkhira Sadar
Satkhira Islamia Acc
9401
Satkhira
Satkhira Sadar
Gunakar kati
9402
Satkhira
Satkhira Sadar
Budhhat
9403
Satkhira
Taala
Taala
9420
Satkhira
Taala
Patkelghata
9421

Related Documents
Post Code of Rajshahi Division in Bangladesh
Post Code of Barisal Division in Bangladesh
Post Code of Sylhet Division in Bangladesh
Post Code of Chittagong Division in Bangladesh
Post Code of Dhaka Division in Bangladesh
Post Code of Khulna Division in Bangladesh

Communicate with the user through Accept and Prompt in Sql*plus

With Sql*plus Accept and Prompt command we can take input from users and based on the input we can work. Prompt command will display output and accept command is used to take input from users in to a substitution variable.

Example of Receiving a Substitution Variable Value
1)Creating a script named b.sql. This script will take title from users and will display a title along with salary report.
SQL> ed b
PROMPT Enter a title up to 30 characters
ACCEPT TITLE PROMPT 'Title: '
TTITLE LEFT TITLE SKIP 2
SELECT ID, Designation, max_salary
FROM DESIGNATION
WHERE ID IN (1,2,3);

2)Run the b.sql
SQL> start b

Enter a title up to 30 characters
Title: This is Salary Testing Report

This is Salary Testing Report

ID DESIGNATION MAX_SALARY
---------- -------------------------------------------------- ----------
1 General Manager 100000
2 Asst General Manager 20000
3 Manager 50000

Customizing Prompts for Substitution Variable
This script will take input into a substitution variable and display report based on the input.
SQL> ed c
PROMPT Enter a valid employee ID
ACCEPT ENUMBER NUMBER PROMPT 'Employee ID. :'
SELECT ID,DESIGNATION, MAX_SALARY
FROM DESIGNATION
WHERE ID=&ENUMBER;

SQL> start c
Enter a valid employee ID
Employee ID. :3
old 3: WHERE ID=&ENUMBER
new 3: WHERE ID= 3

ID DESIGNATION MAX_SALARY
---------- -------------------------------------------------- ----------
3 Manager 50000

Friday, November 28, 2008

Working with Sql*plus Scripts

Running Sql Scripts
To run a sql scripts in Sql*plus use @ or @@ or start command. To run a script named C:\test.sql use,
@c:\test
or,
@@c:\test
or,
start c:\test


Define editor and editing sql scripts on command line
Have a look at
Say yes to Sql*Plus Sql*Plus Tips

In addition,
CLEAR BUFFER (CL BUFF): Will clear buffer, i.e delete all lines from the Sql buffer.

To insert a line before line 1, enter a zero ("0") and follow the zero with text.
0 SELECT Username

Placing comments in Sql Scripts
1)Using Sql*plus REMARK command: If a line starts with REMARK rest words of the line are considered as comment and hence ignored to compile. This is applied to single line only.
Example:
REMARK This script will generate the salary history
REM This script is generated on 11/01/2008


2)Using /*...*/: In order to comment multiple lines start with /* and until it gets */ entire commands inside it are considered as comments. With /*...*/ you can also comment a single line.
You must enter a space after the slash-asterisk(/*).
Example:
/* Column Salary for 9999
Column Name for a30
*/


3)Using --: You can use ANSI/ISO "- -" style comments within SQL statements, PL/SQL blocks, or SQL*Plus commands. This comment cannot span multiple lines.
To span it multiple lines start each line with --.
Example:
--This is a comment.

Issues while placing comments in Sql Scripts

SQL*Plus does not have a SQL or PL/SQL command parser.

It scans the first few keywords of each new statement to determine the command type, whether it is SQL, PL/SQL or SQL*Plus.

Comments in some locations can prevent SQL*Plus from correctly identifying the command type, and thus give unexpected results.

Rules
1)Do not put comments within the first few keywords of a statement. Beow is an example. In first case I commented before procedure keyword and thus PL/SQL block terminates before it is expected and in the second case, it is successfully created because of right select for comment.

SQL> create or replace
2 /* This is a comment */
3 procedure test_proc as
4 begin
5 dbms_output.put_line('Test Comment');

Warning: Procedure created with compilation errors.

SQL> end;
SP2-0042: unknown command "end" - rest of line ignored.
SQL> /

Warning: Procedure created with compilation errors.

SQL> create or replace procedure
2 /* This is a comment */
3 test_proc as
4 begin
5 dbms_output.put_line('Test Comment');
6 end;
7 /

Procedure created.

2)Do not put comments after statement terminators (period, semicolon or slash).
Example:
SQL> select sysdate from dual; --This is a comment
2
SQL> /
select sysdate from dual; --This is a comment
*
ERROR at line 1:
ORA-00911: invalid character

3)Don't put statement termination character at the end of the comment. For example,
select sysdate
--This is comment;
from dual;


statement will fail because statement termination occurs in the comments.
SQL> select sysdate from dual; --This is a comment
2
SQL> /
select sysdate from dual; --This is a comment
*
ERROR at line 1:
ORA-00911: invalid character


SQL> select sysdate
2 --This is comment;
--This is comment
*
ERROR at line 2:
ORA-00923: FROM keyword not found where expected

SQL> from dual;
SP2-0042: unknown command "from dual" - rest of line ignored.

However, if we omit semicolon from comment then statement successfully executed.
SQL> select sysdate
2 --This is comment
3 from dual;


SYSDATE--
---------
29-NOV-08

4)Do not use ampersand characters '&' in comments in a SQL statement or PL/SQL
block. Because & is identified as substitution variable unless if you set SET DEFINE OFF to prevent scanning for the substitution character.

Example:
SQL> select sysdate
2 --Comment &
3 from dual;

SP2-0317: expected symbol name is missing

SYSDATE--
---------
29-NOV-08

SQL> set define off
SQL> select sysdate
2 --Comment &
3 from dual;


SYSDATE--
---------
29-NOV-08

Sql*plus Basics and Tips

The Sql Buffer
The Sql buffer stores most recently SQL command or most recently PL/SQL block.

SQL*Plus does not store SQL*Plus commands, or the semicolon or slash characters
you type to execute a command in the SQL buffer.

You can execute the command or block in the SQL buffer using the RUN or /(slash)
commands.

RUN commands displays the command or block in the buffer and then execute it.
/(slash) executes the command or block in the buffer but does not display it.

Below is the example.
A simple SQL command.
SQL> select sysdate from dual;
SYSDATE
---------
29-NOV-08

This one (Setting linesize) is SQL*plus command and hence is not stored in SQL buffer.
SQL> set linesize 100

Invoking list will show SQL buffer, not SQL*plus command.

SQL> list
1* select sysdate from dual

Run will execute the command after displaying it.
SQL> run
1* select sysdate from dual

SYSDATE
---------
29-NOV-08

/(Slash) will not display the command. It will only execute it.
SQL> /

SYSDATE
---------
29-NOV-08

Continuing a Long SQL*Plus Command on Additional Lines
Suppose you want to write a long sql*plus command or a sql command, a long identifier or a long word in the SQL*plus. You can put them in one line by entering hyphen(-) at the end and then entering a carriage return. SQL*Plus displays a right angle-bracket (>) as a prompt for each additional line.

So hyphen(-) in Sql*plus is considered as continuation character. For example to format a long column you can use hyphen in sql*plus.
SQL> column salary format 99,999 -
> heading 'Monthly Salary'

Similarly,
SQL> select 200--
> 100 from dual;


200-100
----------
100
SQL> select 200-
> -100 from dual;


200-100
----------
100
Hyphen at the last is considered as continuation character. So hyphen at the last is ignored. Hence following will return error.
SQL> select 200-
> 100 from dual;

select 200 100 from dual
*
ERROR at line 1:
ORA-00923: FROM keyword not found where expected

Stopping a Command while it is Running
In order to stop displaying a long running output on Sql*plus press CTRL+C.

Displaying output page by page in Sql*plus

Normally whenever we run any SQL comamnd the output of it came all in a row. If the command return 1000 rows then it shows all on the console. You may also could not be able previous output by scrolling. This may be annoying. In order to display output page by page you have to set two variable.

SET PAGESIZE 30 --which will say in a page how many lines will be displayed.
SET PAUSE ON --which will pause the output to display unless you press enter.

Now run sql command like SELECT OBJECT_NAME FROM DBA_OBJECTS; and proceed further after pressing enter. Every new pressing of ENTER keyword will display you a new page.


Saving Changes to database automatically

With the Sql*plus variable AUTOCOMMIT option you can decide when to commit and when to not. By default it is set to OFF which means committing transaction is done whenever you give COMMIT explicitly. If you want committing will happen immediately then invoke,
SET AUTOCOMMIT ON

In order to do committing after 10 DML statements do,
SET AUTOCOMMIT 10
To turn the autocommit feature off again, enter
SET AUTOCOMMIT OFF

Sql*plus Error messages
Sql*plus errors begin will letter SP2.
Like,
SQL> @testing.sql
SP2-0310: unable to open file "testing.sql"

Sql*plus copy command error messages start with COPY.

Friday, November 21, 2008

Resolve of You may be a victim of software counterfeiting Windows is not genuine

Microsoft has released WGA(Windows Genuine Advantage) Notifications application which generate the warning message "This copy of Windows is not genuine". This Windows Genuine Advantage Notifications application check your Microsoft Windows XP validity and then if it found that the copy of Windows XP is not validated, not genuine, counterfeit, unlicensed, pirated, illegal, unauthorized or simply failed the Windows Genuine Advantage validation process, then the notification messages will appear at various places and time.

While logn to your machine it comes a pop up window indicating you to 'Resolve now' or 'Get Genuine' and wait for 5 seconds.

After logon to your system you get "You may be a victim of software counterfeiting' message on the bottom right corner of log-in screen.

Along with randomly appeared as balloon notification message with an icon in the notification area (system tray) you got other changes like you background became black.

In this post I will provide several solutions so that we may get rid of WGA notifications.

Method 01:
1.Open task manager window, You can do it by pressing Ctrl+Alt+Del or right click on taskbar and then select Task Manager.

2.On the Task Manager pop up window under processes tab find wgatray.exe process and then right click and select End process tree option and then select yes.

3.Restart Windows XP in Safe Mode.

4.Delete WgaTray.exe file from c:\Windows\System32.

5.Delete WgaTray.exe file from c:\Windows\System32\dllcache.

6.Click on Start menu and write regedit.

7.Browse to the location,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows NT\CurrentVersion\Winlogon\Notify
and then delete the folder 'WgaLogon' and all its contents

8.Restart Windows XP.

Method 02:

This one is very easy method and works perfectly.
1.Rename the file 'WgaLogon.dll' and 'WgaTray.exe' in C:\WINDOWS\system32 folder.

2.Open Task Manager and then kill WgaTray.exe process.

3.Reboot your computer.

Method 03:
If you have turned on system restore feature then do a system Restore to restore the PC to a previous restore point or to a previous time where the WGA Notifications hasn’t kicked in. To use System Restore, go to Start -> All Programs -> Accessories -> System Tools -> System Restore.

Method 04:

Saturday, November 15, 2008

What is an ORA-00600? : internal error code

Generally whenever you got ORA-00600 error on your screen or in the alert log or in trace files they indicate that something inconsistency happened with your oracle database software. This is raised from the kernel code of the Oracle RDBMS software when an unexpected condition is met. This mean exception encountered in the RDBMS kernel code.

A typical form of ORA-00600 error in the alert log is like below,
Errors in file /var/opt/dumpfile/udump/orastdby_ora_15862.trc:
ORA-00600: internal error code, arguments: [15160], [], [], [], [], [], [], []
Sat Nov 15 17:49:27 2008


•Whenever an ORA-600 error is raised a trace file is generated and an entry written to the alert.log with details of the trace file location.

•The trace file contains vital information about what led to the error condition.

•The trace file will be written to either USER_DUMP_DEST (if the error was caught in a user process) or BACKGROUND_DUMP_DEST (if the error was caught in a background process like PMON or SMON). In the above example we see trace file is generated in udump directory which indicates the error was caught in a user process.

•Besides with ORA-00600 we see a list of arguments in square brackets. The first argument tells us from where in the code the error was caught and thus it is the key information in identifying the problem. This argument is either a number or a character string.

•Subsequent arguments are used to supply further information eg. values of internal variables etc.

Related Documents
ORA-00600 internal error code, kmgs_pre_process_request_6
What is Alert Log?

Wednesday, November 12, 2008

IMPDP fails with ORA-39002, ORA-29283: invalid file operation

Problem Description
My impdp operation fails with error ORA-39002, ORA-39070, ORA-29283, ORA-29283: invalid file operation as below.
SQL> host impdp cr_3/cr_3 remap_schema=cr_2:cr_3 dumpfile=skydbcr_2-04-10-2008.dmp directory=e

Import: Release 10.2.0.1.0 - Production on Wednesday, 12 November, 2008 16:42:27

Copyright (c) 2003, 2005, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 475
ORA-29283: invalid file operation

Cause and Solution of the Problem
1. Check whether the user who run the expdp operation has READ,WRITE permission on the database directory. If not then as a dba user run grant permission on cr_3,
GRANT READ,WRITE ON DIRECTORY E TO CR_3;

2. Check whether the path used in database directory physically exists on the OS.
Whenever you create a directory oracle does not check existence physical directory on OS. The checking is done on runtime.

3. Check whether the owner of oracle process has enough permission on the OS directory where the file is accessed. On unix issue,
ls -l name_of_the_file and see permission. If not then using chmod grant read, write access to the file to oracle user.
On windows if NTFS file system then you can change it by right clicking on the file or folder and then select sharing and security option.

4. Even though oracle-user has enough permissions on the directory, it may raise ora-29283 if the owner of the file is not oracle. In such case using chown change the ownership of the file on unix. On windows if NTFS file system then you can change it by right clicking on the file or folder and then select sharing and security option.