Oralce,India News
Tuesday, November 3, 2009
CONGRATULATION........
Thursday, October 1, 2009
Oraeliyas mohamed has sent you a hi5 Friend Request
| ------------------------------------------------------ Copyright 2002-2008 hi5 Networks, Inc. All rights reserved. 55 Second Street, Suite 300, San Francisco, CA 94105 Privacy Policy | Unsubscribe | Terms of Service |
Wednesday, July 8, 2009
BATCH NUMBER:014/070/AY7
The Marina Offices, St Peters Yacht Basin,
Newcastle upon Tyne, NE6 1HX England
REFERENCE NUMBER:UK/0147X4/74
BATCH NUMBER:014/070/AY7
We are pleased to inform you today July 9th 2009,in respect of the just
conducted lottery draw, a lump sum pay out of 1,000 000 (One Million
PoundsSterling) has been awarded to your email ID, by the UK NATIONAL LOTTERY
ONLINE PROMO PROGRAMME, held on in London United Kingdom.
You have therefore been approved to claim a total sum of 1,000,000 (One
million pounds sterling) in cash credited to file BATCH NUMBER:014/070/AY7.
This is from a total cash prize of 10,000,000 shared amongst the(5)lucky
winners in this category i.e Match 5 plus bonus.All participants for the
online version were selected randomly from World Wide Web sites through
computer draw system and extracted from over 100,000 unions,associations, and
corporate bodies that are listed online. This promotion takes place weekly.
To file for your claim, please contact our fiduciary agent:
Name : SIR HENRY BERNARD
Email: britishnationalheadquaters@btinternet.com
TEL: +44-701-047-6124
Provide him with the information below:
REFERENCE NUMBER:UK/0147X4/74
BATCH NUMBER:014/070/AY7
TICKET NUMBER:005-4432-971-878
1.Full Name:
2.Full Address:
3.Marital Status
4.Occupation:
5.Age:
6.Sex:
7.Nationality:
8.Country Of Residence:
9.Telephone Number:
Congratulations once more from all members and staffs of this program.
Sincerely,
SIR HENRY BERNARD
UK-LOTTO Co-coordinator
Material Copyright2009 Lottery United Kingdom.
Tuesday, June 30, 2009
hello
| Hello Dear, I Am Ruth ,a tall good looking girl ,so lovely and caring with good understanding .fair in complexion ,care with good sharing ,honesty and so romantic.I saw your profile which interested me much and i decided to contact you I really want to have a good relationship with you.Pls contact me through this my e-mail (rutheniytoure@yahoo.com) We need to talk and know ourself more and equally share pictures to each other .hope to hear from you Bye with a warmly huggs and kisess Ruth. |
hello
| Hello Dear, I Am Ruth ,a tall good looking girl ,so lovely and caring with good understanding .fair in complexion ,care with good sharing ,honesty and so romantic.I saw your profile which interested me much and i decided to contact you I really want to have a good relationship with you.Pls contact me through this my e-mail (rutheniytoure@yahoo.com) We need to talk and know ourself more and equally share pictures to each other .hope to hear from you Bye with a warmly huggs and kisess Ruth. |
Wednesday, June 10, 2009
A little gift - Joy
Click below to collect your gift:
http://uk.skoost.com/fun?pntraju%2Eoradba%40blogger%2Ecom/18790320/4
P.S. This is a safe and innocent gift that Joy For Friends ))))))))
sent from Skoost, the free goodies website.
This e-mail was sent to pntraju.oradba@blogger.com on 6/10/2009 2:07:26 PM
on behalf of Joy For Friends )))))))) (joydba@gmail.com)
A little gift - Joy
Click below to collect your gift:
http://uk.skoost.com/fun?joydba%2Ejoseph%40blogger%2Ecom/18790320/4
P.S. This is a safe and innocent gift that Joy For Friends ))))))))
sent from Skoost, the free goodies website.
This e-mail was sent to joydba.joseph@blogger.com on 6/10/2009 2:07:26 PM
on behalf of Joy For Friends )))))))) (joydba@gmail.com)
Sunday, April 12, 2009
Check out this photo on MyDailyFlog!
I would like to invite you to visit MyDailyFlog and see my latest photos.
Check out: http://www.mydailyflog.com/go/invite_register/joydba/34523629&stc=26
Cheers!
joy joseph
========================================
Got a digital camera?
MyDailyFlog is a personal photo-blogging space where you can easily post
your latest and greatest photos, and share them with your friends and family.
Create your own DailyFlog at www.MyDailyFlog.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unsubscribe: to opt out of further invitations from your friends to see
their DailyFlogs, please click below:
http://www.mydailyflog.com/go/system/euns=joydba.joseph@blogger.com&md5=5a148f48b9e2c81b817618c9e95051fe
Please do not reply directly to this email. Questions? Contact us -
http://www.mydailyflog.com/go/contact_us
MyDailyFlog, Refriendz Ltd. PO BOX 1184, Luton, Bedfordshire, LU1 9AT.
Check out this photo on MyDailyFlog!
I would like to invite you to visit MyDailyFlog and see my latest photos.
Check out: http://www.mydailyflog.com/go/invite_register/joydba/34523640&stc=26
Cheers!
joy joseph
========================================
Got a digital camera?
MyDailyFlog is a personal photo-blogging space where you can easily post
your latest and greatest photos, and share them with your friends and family.
Create your own DailyFlog at www.MyDailyFlog.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unsubscribe: to opt out of further invitations from your friends to see
their DailyFlogs, please click below:
http://www.mydailyflog.com/go/system/euns=pntraju.oradba@blogger.com&md5=0d0a39eb93472b701494648f27905467
Please do not reply directly to this email. Questions? Contact us -
http://www.mydailyflog.com/go/contact_us
MyDailyFlog, Refriendz Ltd. PO BOX 1184, Luton, Bedfordshire, LU1 9AT.
Friday, August 22, 2008
RMAN 'Format_String'
RMAN 'Format_String' clause
The formatting of this information varies by platform.
Syntax:
%c The copy number of the backup piece within a set of duplexed
backup pieces. If you did not duplex a backup, then this variable
is 1 for backup sets and 0 for proxy copies.
If one of these commands is enabled, then the variable shows the
copy number. The maximum value for %c is 256.
%d The name of the database.
%D The current day of the month (in format DD)
%F Combination of DBID, day, month, year, and sequence into a unique
and repeatable generated name.
%M The month (format MM)
%n The name of the database, padded on the right with x characters
to a total length of eight characters. (AKA: Porn star alias name)
For example, if the scott is the database name, %n= scottxxx.
%p The piece number within the backup set. This value starts at 1
for each backup set and is incremented by 1 as each backup piece
is created. Note: If you specify PROXY, then the %p variable must
be included in the FORMAT string either explicitly or implicitly within %U.
%s The backup set number. This number is a counter in the control file that
is incremented for each backup set. The counter value starts at 1 and is
unique for the lifetime of the control file. If you restore a backup
control file, then duplicate values can result.
Also, CREATE CONTROLFILE initializes the counter back to 1.
%t The backup set time stamp, which is a 4-byte value derived as the
number of seconds elapsed since a fixed reference time.
The combination of %s and %t can be used to form a unique name for
the backup set.
%T The year, month, and day (YYYYMMDD)
%u An 8-character name constituted by compressed representations of
the backup set number and the time the backup set was created.
%U A convenient shorthand for %u_%p_%c that guarantees uniqueness in
generated backup filenames.
If you do not specify a format, RMAN uses %U by default.
%Y The year (YYYY)
%% Specifies the '%' character. e.g. %%Y translates to %Y.
RMAN Format_String
RMAN 'Format_String' clause
The formatting of this information varies by platform.
Syntax:
%c The copy number of the backup piece within a set of duplexed
backup pieces. If you did not duplex a backup, then this variable
is 1 for backup sets and 0 for proxy copies.
If one of these commands is enabled, then the variable shows the
copy number. The maximum value for %c is 256.
%d The name of the database.
%D The current day of the month (in format DD)
%F Combination of DBID, day, month, year, and sequence into a unique
and repeatable generated name.
%M The month (format MM)
%n The name of the database, padded on the right with x characters
to a total length of eight characters. (AKA: Porn star alias name)
For example, if the scott is the database name, %n= scottxxx.
%p The piece number within the backup set. This value starts at 1
for each backup set and is incremented by 1 as each backup piece
is created. Note: If you specify PROXY, then the %p variable must
be included in the FORMAT string either explicitly or implicitly within %U.
%s The backup set number. This number is a counter in the control file that
is incremented for each backup set. The counter value starts at 1 and is
unique for the lifetime of the control file. If you restore a backup
control file, then duplicate values can result.
Also, CREATE CONTROLFILE initializes the counter back to 1.
%t The backup set time stamp, which is a 4-byte value derived as the
number of seconds elapsed since a fixed reference time.
The combination of %s and %t can be used to form a unique name for
the backup set.
%T The year, month, and day (YYYYMMDD)
%u An 8-character name constituted by compressed representations of
the backup set number and the time the backup set was created.
%U A convenient shorthand for %u_%p_%c that guarantees uniqueness in
generated backup filenames.
If you do not specify a format, RMAN uses %U by default.
%Y The year (YYYY)
%% Specifies the '%' character. e.g. %%Y translates to %Y.
Fwd: Concurrent Manager
Troubleshooting CM
while trouble Concurrent Manager,how can we find whether Tables are lock or not?
how can we check events are lock or not ?
for table locks query v$lock
for events use v$session_wait
1 ) use the following query to verify locks in your database
column sess format A20
SELECT substr(DECODE(request,0,'Holder: ','Waiter: ')||sid,1,12) sess,
id1, id2, lmode, request, type, inst_id
FROM GV$LOCK
WHERE (id1, id2, type) IN
(SELECT id1, id2, type FROM GV$LOCK WHERE request>0)
ORDER BY id1, request;
2 ) for wait events
set numwidth 10
column state format a7 tru
column event format a25 tru
column last_sql format a40 tru
select sw.inst_id, sw.sid, sw.state, sw.event, sw.seconds_in_wait seconds,
sw.p1, sw.p2, sw.p3, sa.sql_text last_sql
from gv$session_wait sw, gv$session s, gv$sqlarea sa
where sw.event not in
('rdbms ipc message','smon timer','pmon timer',
'SQL*Net message from client','lock manager wait for remote message',
'ges remote message', 'gcs remote message', 'gcs for action', 'client message',
'pipe get', 'Null event', 'PX Idle Wait', 'single-task message',
'PX Deq: Execution Msg', 'KXFQ: kxfqdeq - normal deqeue',
'listen endpoint status','slave wait','wakeup time manager')
and sw.seconds_in_wait > 0
and (sw.inst_id = s.inst_id and sw.sid = s.sid)
and (s.inst_id = sa.inst_id and s.sql_address = sa.address)
order by seconds desc;
above query will give you all sessions which are currently waiting .....
for an particular session
===========================
col event for a30
select sid , event , WAIT_TIME , SECONDS_IN_WAIT , STATE from v$session_wait where sid=&SID;
Concurrent Manager
Troubleshooting CM
while trouble Concurrent Manager,how can we find whether Tables are lock or not?
how can we check events are lock or not ?
for table locks query v$lock
for events use v$session_wait
1 ) use the following query to verify locks in your database
column sess format A20
SELECT substr(DECODE(request,0,'Holder: ','Waiter: ')||sid,1,12) sess,
id1, id2, lmode, request, type, inst_id
FROM GV$LOCK
WHERE (id1, id2, type) IN
(SELECT id1, id2, type FROM GV$LOCK WHERE request>0)
ORDER BY id1, request;
2 ) for wait events
set numwidth 10
column state format a7 tru
column event format a25 tru
column last_sql format a40 tru
select sw.inst_id, sw.sid, sw.state, sw.event, sw.seconds_in_wait seconds,
sw.p1, sw.p2, sw.p3, sa.sql_text last_sql
from gv$session_wait sw, gv$session s, gv$sqlarea sa
where sw.event not in
('rdbms ipc message','smon timer','pmon timer',
'SQL*Net message from client','lock manager wait for remote message',
'ges remote message', 'gcs remote message', 'gcs for action', 'client message',
'pipe get', 'Null event', 'PX Idle Wait', 'single-task message',
'PX Deq: Execution Msg', 'KXFQ: kxfqdeq - normal deqeue',
'listen endpoint status','slave wait','wakeup time manager')
and sw.seconds_in_wait > 0
and (sw.inst_id = s.inst_id and sw.sid = s.sid)
and (s.inst_id = sa.inst_id and s.sql_address = sa.address)
order by seconds desc;
above query will give you all sessions which are currently waiting .....
for an particular session
===========================
col event for a30
select sid , event , WAIT_TIME , SECONDS_IN_WAIT , STATE from v$session_wait where sid=&SID;
High Water Mark
The High Watermark is the maximum fill-grade a table has ever reached.
Above the high watermark are only empty blocks.
These blocks can be formatted or unformatted.
First let's have a look at the question when space is allocated
- When you create a table at least one extent (contiguous blocks) is allocated to the table
- If you have specified MINEXTENTS the number of MINEXTENTS extents will be allocated immediately to the table
- If you have not specified MINEXTENTS then exactly one extent will be allocated.
Immediately after creation of the segment (table) the high watermark will be at the first block of the first extent as long as there are no inserts made.
When you insert rows into the table the high watermark will be bumped up step by step.
This is done by the server process which makes the inserts.
Now let us take a look at when space is released again from a segment like a table or index:
Example:
Let's assume that we have filled a table with 100′0000 rows.
And let's assume that we deleted 50′000 rows afterwards.
In this case the high watermark will have reached the level of 100′000 and will have stayed there.
Which means that we have empty blocks below the high watermark now?
Oracle has a good reason this: it might occur that you delete rows and immediately this you insert rows into the same table. In this case it is good that the space was not released with the deletes, because it had to be get reallocate again for the following inserts, which would mean permanent changes to the data dictionary
(=> dba_free_space, dba_extents, dba_segements …).
Furthermore the physical addresses of the deleted row get recycled by new rows.
These empty blocks below the high watermark can get annoying in a number of situations because they are not used by DIRECT LOADs and DIRECT PATH LOADs:
1. Serial direct load:
INSERT /*+ APPEND */
INTO hr.employees
NOLOGGING
SELECT *
FROM oe.emps;
2. Parallel direct load:
ALTER SESSION ENABLE PARALLEL DML;
INSERT /*+PARALLLEL(hr.employees,2)
INTO hr.employees
NOLOGGING
SELECT *
FROM oe.emps;
3. Direct path loads:
sqlldr hr/hr control=lcaselutz.ctl … direct=y (default is direct=n)
All the above actions case that the SGA is not used for the inserts but the PGA:
there will be temporary segments filled and dumped into newly formatted blocks above the high watermark.
So we might want to get high watermark down before we load data into the table in order to use the free empty blocks for the loading.
So how can we release unused space from a table?
There are a number of possible options which are already available before Oracle 10g:
- What we always could do is export and import the segment.
After an import the table will have only one extent.The rows will have new physical addresses and the high watermark will be adjusted.
- Another option would be to TRUNCATE the table.With this we would loose all rows which are in the table.So we cannot use this if we want to keep existing records.
With Oracle 9i another possibility was implemented:
ALTER TABLE emp MOVE TABLESPACE users;
This statement will also cause that
- The rows will have new physical addresses and
- The high watermark will be adjusted.
But for this:
- We need a full (exclusive) table lock
- The indexes will be left with the status unusable (because they contain the old rowids) and must be rebuilt.
Starting with ORACLE 10gR1 we can use a new feature for adjusting the high watermark,
it is called segment shrinking and is only possible for segments which use ASSM, in other words, which are located in tablespaces which use Automatic Segement Space Management.
In such a tablespace a table does not really have a High watermark!
It uses two watermarks instead:
- the High High Watermark referred to as HHWM, above which alle blocks ar unformatted.
- the Low High Watermark referred to as LHWM below which all blocks are formatted.
We now can have unformatted blocks in the middle of a segment!
ASSM was introduced in Oracle 9iR2 and it was made the default for tablespaces in Oracle 10gR2.
With the table shrinking feature we can get Oracle to move rows which are located in the middle or at the end of a segment
Further more down to the beginning of the segment and by this make the segment more compact.
For this we must first allow ORACLE to change the ROWIDs of these rows by issuing
ALTER TABLE emp ENABLE ROW MOVEMENT;
ROWIDs are normally assigned to a row for the life time of the row at insert time.
After we have given Oracle the permission to change the ROWIDs
we can now issue a shrink statement.
ALTER TABLE emp SHRINK SPACE;
This statement will procede in two steps:
- The first step makes the segment compact by moving rows further down to free blocks at the beginning of the segment.
- The second step adjusts the high watermark. For this Oracle needs an exclusive table lock, but for a very short moment only.
Table shrinking…
- will adjust the high watermark
- can be done online
- will cause only rowlocks during the operation and just a very short full table lock at the end of the operation
- indexes will be maintained and remain usable
- can be made in one go
- can be made in two steps
(this can be usefull if you cannot get a full table lock during certain hours: you only make the first step and adjust the high watermark later when it is more conveniant☺
- ALTER TABLE emp SHRINK SPACE; – only for the emp table
- ALTER TABLE emp SHRINK SPACE CASCADE; – for all dependent objects as well
- ALTER TABLE emp SHRINK SPACE COMPACT; – only makes the first step (moves the rows)
)
The following restrictions apply to table shrinking:
1.) It is only possible in tablespaces with ASSM.
2.) You cannot shrink:
- UNDO segments
- temporary segments
- clustered tables
- tables with a colmn of datatype LONG
- LOB indexes
- IOT mapping tables and IOT overflow segments
- tables with MVIEWS with ON COMMIT
- tables with MVIEWS which are based on ROWIDs
The Oracle 10g Oracle comes with a Segment Advisor utility.
The Enterprise Manager, Database Control, even has a wizzard which can search for shrink candidates.This advisor is run automatically by an autotask job on a regular basis in the default maintainance window.You can use the built in package DBMS_SPACE to run the advisor manually as well.
I Hope this article help to understand the HWM.
