What really is "UNTIL TIME" ?

hi. Im fretting again.
Another couple of quibbles Im afraid:
I have read countless descriptions for the UNTIL clause in rman. That there is UNTIL TIME, that there is UNTIL SEQUENCE and UNTIL SCN.
I have the Oracle9i DBA Handbook here, p.487. And its thrown another spanner in the works. It lists the various clauses used, and under untilClause this is is description:
Specifies an upper limit by TIME, SCN, or log sequence number.This clause is usually used to specify the desired point in time for an incomplete recovery"
This might be a matter of semantics, but those of you with OCP exam question experience might understand that some of the questions put in the exam are intentionally wired that way. Specifically UNTIL TIME demands us to literally specify a time. Yet generally, could we say that even UNTIL SEQUENCE is to "specify a point in time", since using a log sequence number is indeed to specify a time in the past - just measured a different way???
Another quibble I have is to confirm this: that in an offline backup we would copy the online redo logs, yet in an online backup we would only want to copy the archivelog redo.
Thanks.
DA
Im not sure who has read the OCP 9i Exam Guide by Oracle Press (Velpuri) but on p.295 he explains that tablespace recovery may be done while the db is on OR offline. I've read a million times that the database MUST be online for tablespace recovery (while for datafile recovery it can be off or on). Just another mind-bender for those of us having to learn from texts)
Message was edited by:
Dan A

I have read countless descriptions for the UNTIL
clause in rman. That there is UNTIL TIME, that there
is UNTIL SEQUENCE and UNTIL SCN.Dan,
You and I use a clock that measures seconds, minutes, and so on.
Oracle uses a clock that measures system changes. Every once in a while the Oracle internal clock 'ticks' and a new 'SCN' appears.
specify a point in time", since using a log sequence number is indeed to specify a time in the past - just measured a different way???The SCN clock is not perfectly in alignment with your clock. It may not even have regular ticks - at peak load the ticks may come in at several thousand per second, under light load the SCN ticks could happen only a few [hundred] per second.
Any point in time identified by external (to the database) reference is translated to the internal SCN clock tick. If the people time is specified to the nearest minute, which SCN does that translate to? To the nearest second?
Now, for the 'upper bound' part ... if a tablespace was turned read-only at SCN 567 and the database is currently at SCN 887, what should the "SELECT ... AS OF SCN 753" return from the tablespace?

Similar Messages

I am using Firefox v 8.0 on Vista. Lately it is opening really slowly until I get so frustrated I keep clicking on the desktop icon, Then it finally opens 3 times! How can I correct his?

Question
I am using Firefox v 8.0 on Vista. Lately it is opening really slowly until I get so frustrated I keep clicking on the desktop icon, Then it finally opens 3 times! How can I correct this? e

This is a user to user forum.
I have noted herein a number for Apple Customer Relations for you to try.
Apple Computer Customer Relations: (800) 767-2775
Avoid the rude language when dealing with them. It will get you better results.
Good luck!

How to fix RMAN-20207: UNTIL TIME is before RESETLOGS time

Early this morning, in my haste to get a point in time restore and recovery started, I forgot to restore the controlfile as the 1st step.
I used the current database control file, and now I have "RMAN-06004: ORACLE error from recovery catalog database: RMAN-20207: UNTIL TIME is before RESETLOGS time". I have a recovery catalog database. This is Oracle 8.1.7.4.
Here was my script syntax:
export ORACLE_SID=myname
export ORACLE_HOME=/x01/oracle/product/8.1.7
export LOG=/x01/admin/recover/point_in_time_${ORACLE_SID}_${TimeStamp}.log
echo "Starting Time: `date`" > $LOG
/x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
set echo on;
connect target
connect catalog myuser/mypass@mycatalog
startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
alter database mount;
run {
set until time "to_date('2006-12-02:03:00:00','yyyy-mm-dd:hh24:mi:ss')";
allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
restore database;
recover database;
release channel t1;
release channel t2;
Alter Database Open Resetlogs;
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
exit
echo "Finished Time: `date`" >> ${LOG}
Can I do the following to try to restore the controlfile? First, I would shutdown my database.
export ORACLE_SID=myname
export ORACLE_HOME=/x01/oracle/product/8.1.7
export LOG=/x01/admin/rman/recover/db_point_in_time_8i_${ORACLE_SID}_${TimeStamp}.log
echo "Starting Time: `date`" > $LOG
/x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
set echo on;
connect target
connect catalog myuser/mypass@mycatalog
startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
alter database mount;
run {
set until time "to_date('2006-12-02:03:00:00','yyyy-mm-dd:hh24:mi:ss')";
allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
restore controlfile to '/x01/disk/control01.ctl';
replicate controlfile from '/x01/disk/control01.ctl';
recover database;
release channel t1;
release channel t2;
Alter Database Open Resetlogs;
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
exit
echo "Finished Time: `date`" >> ${LOG}
I have a new incarnation of the database too -
List of Database Incarnations
DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time
1 2 MYNAME 1849293826 NO 1 06-AUG-03
1 25874 MYNAME 1849293826 NO 750748990 26-SEP-03
1 143681 MYNAME 1849293826 NO 6610874669464 12-AUG-05
1 265345 MYNAME 1849293826 YES 6611455777113 14-DEC-06
What is the fastest way to fix this situation without having to restore the entire database?
Thanks,
Message was edited by:
user521040

Here is the "revised" script - I have not run this again on the Production system, but I might get a chance - finding corruption on the disk. I will test out later on a development database:
#!/usr/bin/ksh
TimeStamp=`date +%Y%m%d_%H%M%S`
export ORACLE_SID=myname
export ORACLE_HOME=/x01/oracle/product/8.1.7
export LOG=/x01/admin/rman/recover/8i_${ORACLE_SID}_${TimeStamp}.log
echo "Starting Time: `date`" > $LOG
/x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
set echo on;
connect target
connect catalog myuser/mypass@mycat1
startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
run {
set until time "to_date('2006-11-25:18:08:00','yyyy-mm-dd:hh24:mi:ss')";
allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t3 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t4 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
restore controlfile to '/x01/disk/control01.ctl';
replicate controlfile from '/x01/disk/control01.ctl';
alter database mount;
restore database;
recover database;
Alter Database Open Resetlogs;
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 20
97217536";
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 20
97217536";
release channel t1;
release channel t2;
release channel t3;
release channel t4;
exit
echo "Finished Time: `date`" >> ${LOG}
Message was edited by:
user521040

Set until time TO_DATE

Hi,
what is wrong with my syntaxe :
RMAN> run {
2> set until time TO_DATE("07/07/07 09:38:00","DD/MM/YY HH:MI:SS");
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "double-quoted-string, equal, single-quoted-string"
RMAN-01008: the bad identifier was: TO_DATE
RMAN-01007: at line 2 column 16 file: standard input
Can you help me please ?

Duplicate post:
RMAN ERROR when duplicating

PIT recovery until time when database was in backup mode

Hello,
Is it possible to recover database until some point/time which is within "time window" when database tablespaces were still in online backup mode?
I was basicaly replicatying database from source to target DB by putting DB to online backup mode, then copy all datafiles, after copy of datafiles was finished I started applying redologs generated on source DB afterwards. After I applied tens of redologs with "recover database until cancel using backup controlfile" and then typed "CANCEL" after 10-20 redologs applied I still got an error that opening DB would get an error due to inconsistent datafile. When I ended backup mode on source DB and applied few of redologs after ending backup mode on source DB datafiles were consistent.....
Thx a lot for answer in advance.

Hello Hemant K Chitale ,
thats clear. I probably did not express it clearly, so I will describe it once again:
Teoreticall scenario 1:
I put 'source" database to backup mode and start copy datafiles to "target" db. When copy of all datafiles is succesfully finished (lets say it 5:00AM), I don't issue "end backup" on source DB but I keep tablespaces in backup mode until 7:00AM. On target DB I will start recovery and apply redologs from source system.
Question 1:Is it possible to recover database until time 6:00AM? At this time all datafiles were already succesfully copied, BUT source db was still in backup mode. Or will I be able to get target DB to consistent state only after 7:00AM (end backup issuied on source DB) and not in window 5:00AM-7:00AM?
Teoreticall scenario 2 (small correction comparing to scenario1):
I will put source DB to begin backup mode at 5:00AM on 20.february and let it in this state until 7:00AM on 20.february. On target DB I will restore backup from source DB performed day before (or few days before does not matter) that means on 19.february and start to apply redologs generated after this backup.
Question 2: Will I be able to recover DB until 6:00AM on 20.february and open database after recovery until this time? Or wont I be able to recover and open DB witin window 20.february 5:00AM-7:00AM (source db in backup mode)
Bear in mind this is just teoreticly (don't ask me why would you do it and why you don't do it this way etc...). I just want to understand how it really works ;)
Thx a lot!

Set until time clause to restore controlfile

Hello
How can I use "set until" clause to restore the controlfile ?
The database is already in archivelog mode.
RMAN>
run {
set until time "TO_DATE('2011-02-24 09:30:00','yyyy-mm-dd hh24:mi:ss')";
restore controlfile from autobackup;
RMAN>
RMAN> 2> 3> 4>
executing command: set until time
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 02/24/2011 09:52:54
ORA-01507: database not mountedThis is the rman backup log:
Starting Control File and SPFILE Autobackup at 24-FEB-11
piece handle=/oracle/ora1020/dbs/c-1270860316-20110224-01 comment=NONE
Finished Control File and SPFILE Autobackup at 24-FEB-11I can also confirm that it was backed up.
ls -l /oracle/ora1020/dbs/c-1270860316-20110224-01
-rw-r----- 1 oracle dba 7143424 Feb 24 09:25 /oracle/ora1020/dbs/c-1270860316-20110224-01

For Datafiles and ArchiveLogs :
SET UNTIL works because RMAN can query the Controlfile (that is already present) {OR the Catalog, if available} to determine the Database Incaranation and identify all the BackupSets, BackupPieces and SCNs for datafiles.
For Controlfiles :
SET UNTIL needs to be able to query a source or determine a default location. If a Catalog is available, it can query the catalog. In the absence of the catalog, it can only determine the expected location to restore from on the basis of the AUTOBACKUP location and FORMAT.
When you have AutoBackup to Disk, using an FRA and have the AUTOBACKUP FORMAT set correctly you will notice that the controlfile backups go to a directory that has the date as part of the directory name. RMAN can "query" the backups it finds in each of the folders in the autobackup location and determine the correct piece to restore from. This is predicated on the FORMAT being the expected format. That is why the example also shows how you set the FORMAT before you do the restore -- to "tell" RMAN what format to expect. (Remember that it has no repository -- controlfile or catalog -- to query so it doesn't know the backup piece names, unless they follow the expected location and format !)
All of this works well on disk. On tape, it has to actually send it's requests to the Medial Management Layer -- it is the Media Management Layer that maintains the catalog of tapes and files on tapes. (Remember that RMAN still doesn't have a repository that it can query !).
Going back to my earlier comment that SET UNTIL is used for Datafiles and Archivelogs : Because it is much easier for RMAN to query a known repository for all the information it needs.
Hemant K Chitale

Using set until time for duplicate is extremely slow

Whenever I do a duplicate using the set until time it takes forever to get started. The executing command: SET until clause takes about 20 minutes, and then when allocating channels it takes about 10 minutes per channel. Both db's are 10.2.0.3, and in archivelog mode. When I do just a plain duplicate database it runs through just fine, no pauses or anything. Can someone please poing me in the right direction or shed some light on this issue for me?
Thanks!

Hi,
Here is what happens when I kick off the duplicate command with the run block:
RMAN> run {
2> set until time "to_date('Mar 14 2009 06:00:00','Mon DD YYYY HH24:MI:SS')";
3> duplicate target database to DEST;
4> }
executing command: SET until clause
using target database control file instead of recovery catalog
Starting Duplicate Db at 17-MAR-09
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=3985 devtype=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: sid=3984 devtype=DISK
allocated channel: ORA_AUX_DISK_3
channel ORA_AUX_DISK_3: sid=3983 devtype=DISK
allocated channel: ORA_AUX_DISK_4
channel ORA_AUX_DISK_4: sid=3982 devtype=DISK
allocated channel: ORA_AUX_DISK_5
channel ORA_AUX_DISK_5: sid=3981 devtype=DISK
It takes anywhere from 15 to 20 minutes to allocate each channel, then it proceeds with the restoring of datafiles from the last backup. After that is done then it switches all the files, then it does this to start the recovery of the archive logs:
contents of Memory Script:
set until time "to_date('Mar 14 2009 06:00:00','Mon DD YYYY HH24:MI:SS')";
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 17-MAR-09
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=3981 devtype=DISK
allocated channel: ORA_AUX_DISK_2
channel ORA_AUX_DISK_2: sid=3982 devtype=DISK
allocated channel: ORA_AUX_DISK_3
channel ORA_AUX_DISK_3: sid=3983 devtype=DISK
allocated channel: ORA_AUX_DISK_4
channel ORA_AUX_DISK_4: sid=3984 devtype=DISK
allocated channel: ORA_AUX_DISK_5
channel ORA_AUX_DISK_5: sid=3977 devtype=DISK
again it takes about 15 to 20 minutes to allocate each channel.

What is safety delta time

Hi Experts
Can any one please explain me
What is safety delta time in terms of delta data source
Thanks

Hi,
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
Leaving the value blank increases the risk that the system could not extract records arising during extraction.
Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:40:00. In this case, the selection interval is 12:00:00 to 12:40:00. At the end of extraction, the pointer is set to 12:40:00.
A record - for example, a document- is created at 12:40 but not saved until 12:40. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
these are used to determining the delta in a datasource:
1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
2. Calendar day - The field is a DATS8 field which always contains the day
check the thread:
safety intervels in genric delta extraction.?
Sriram

PT880----Possible cold boot issue-----What are YOUR boot times??

I may have an issue with this board that I hadn't really noticed since I've been so heavy into the max overclock I could get.
My post and then boot time is strange and annoying-----and sometimes I have to just shut off and turn on-----to actually complete the process. It just seems WAY too long! But maybe this is normal for the chipset.
Turn on>>>>>to POST beep = 40 seconds----D-Bracket shows code of "Memory Detection" during this time.....(----This is the time that seems way out of whack)----most boards I've ever had go from turn on>>>>to Post beep VERY quickly.
From POST beep>>>>>to "Welcome" screen in BOOT = another 20 seconds
Completion of BOOT = another 10 seconds-----not so much worried about this one as I would think it would be Windows dependent and what additional software was loaded.
This total process seems remarkably slow----and again----sometimes-----I NEVER get the post beep (The D-Bracket code is stuck in Memory Detection) and I have to turn the machine off and start again.
What are you guys' times with your PT880???? I tried two different types of RAM---no difference----changing RAM DIMM slots-----no difference----changing RAM timings and voltages----no difference-----I also ran Memtest on both sets of RAM (passed), reflashed Bios----cleared CMOS, and reset NVRAM----no change.
Any ideas??? Beta Bios 1.53 issue??
John

Quote
Originally posted by markt435
Well I finally got my system fixed. Hmmm I have about a 20 sec start up. My proc is overclocked to 3.4Ghz as well. I would try reseating memory or clearing the BIOS. Or putting different sticks of memory in if you have any laying around.
Already done-----See last paragraph of my post....

RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

Hello,
i am working for a scenerio and you can see my restore script below,
RMAN> RUN
2> {
3> SET UNTIL TIME "to_date('24-05-2010 18:00:00','DD-MM-YYYY HH24:MI:SS')";
4> RESTORE DATABASE;
5> RECOVER DATABASE;
6> }
executing command: SET until clause
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/26/2010 11:23:24
RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
also you can see my backups,
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
89 B 1 A DISK 24-05-2010 15:36:04 1 1 NO BACKU
P_BISE1DB_000_052410030823
90 B 1 A DISK 24-05-2010 15:36:13 1 1 NO BACKU
P_BISE1DB_000_052410030823
91 B 0 A DISK 25-05-2010 12:01:09 1 1 NO TAG20
100525T113815
92 B 0 A DISK 25-05-2010 12:01:13 1 1 NO TAG20
100525T113815
93 B 1 A DISK 25-05-2010 12:01:55 1 1 NO TAG20
100525T120152
94 B 1 A DISK 25-05-2010 12:04:55 1 1 NO TAG20
100525T120451
95 B 1 A DISK 25-05-2010 13:55:00 1 1 NO TAG20
100525T134431
96 B 1 A DISK 25-05-2010 13:55:09 1 1 NO TAG20
100525T134431
97 B 1 A DISK 25-05-2010 14:01:43 1 1 NO TAG20
100525T140139
98 B 1 A DISK 25-05-2010 14:55:33 1 1 NO TAG20
100525T140356
so i am trying to understand that what is the earliest date that i can restore my database and avoid tihs error, according to the my backup sets?
thank you
Ugur

Please query the following query and specify the RESETLOGS time
SELECT RESETLOGS_TIME FROM v$database;
i cant have result with this, because database is mount state,
And post the result of the following command to provide an information about database incarnations:
RMAN>LIST INCARNATION
RMAN> list incarnation;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 BISE1DB 4092555014 PARENT 1116016 01-05-2007 16:22:55
2 2 BISE1DB 4092555014 PARENT 1226717 14-12-2007 15:28:11
3 3 BISE1DB 4092555014 PARENT 5783997202 04-05-2010 09:59:11
4 4 BISE1DB 4092555014 CURRENT 5785721070 26-05-2010 10:59:32
thank you

Recover Datafile until time

Hi ALL,
what is the correct syntax ....i get 'illegl recovery option until'
when i use
RECOVER DATAFILE 'COMPLETE FILENAME WITH PATH' UNTIL TIME '2006-01-28:16:00:00' ;
wHAT IS THE CORRECT ONE ?
Regards
Sunny

Recovery command in 9i

Rman delete archivelog until time 2hrs

guys,
I want to use this inside rman.
rman{
RUN{
ALLOCATE CHANNEL ch01 TYPE DISK FORMAT 'blah lah';
BACKUP
ARCHIVELOG ALL
DELETE archivelog until time "older than 2 hrs ago" backed up 1 times to device type sbt; ;
RELEASE CHANNEL ch01;
how do i translate this "older than 2 hrs ago" to RMAN language
Edited by: user2579172 on Mar 29, 2010 1:19 PM

this served my purpose :
DELETE archivelog until time "sysdate-1/30" backed up 1 times to device type disk ;
but
rman is prompting whether to delete the archivelogs or not
ex:
List of Archived Log Copies
Key Thrd Seq S Low Time Name
4303374 1 11623
Do you really want to delete the above objects (enter YES or NO)?
Error occurred getting response - assuming NO response
released channel: ch01
RMAN>
HOW i heck I tell RMAN inside the run { to delete the archive logs without prompting me for YES OR NO

What is meant by Time Phased Planning?

Dear Experts,
What is meant by Time Phased Planning?
Pls tell me both functionally & how we do it in SAP...as i am an Abapper
Kind Regards
Sajid

Dear,
If a vendor always delivers a material on a particular day of the week, it makes sense to plan this material according to the same cycle in which it is delivered, but displaced by the delivery time. This is possible with the time-phased planning procedure.
Materials that are planned using the time-phased planning technique are provided with an MPR date in the planning file. This date is set when creating a material master record and is re-set after each planning run. It represents the date on which the material is to be planned again and is calculated on the basis of the planning cycle entered in the material master record. For materials that are planned using the time-phased planning procedure, the two indicators, the total change indicator and the net change planning indicator are irrelevant. Therefore, they are not set by the system even if changes that are relevant to the planning run are made.
The system uses the interval between the MRP date and the availability date of the next MRP date for the requirements calculation in the planning run. Existing stocks must cover this interval. You must bear in mind that if nothing is ordered at the first MRP date, you have to wait for the next MRP date before you can plan and order this material again. Therefore, if an order proposal is created during this planning run, it will not be available until the end of the interval.
The requirements are calculated using the following formula:
forecast value for the interval (cycle + purchasing department processing time + planned delivery time + goods receipt processing time) + safety stock
this may help u
Regards,
Pardeep Malik

RECOVER UNTIL TIME

Hi all,
I try to flashback my database and when i do the command FLASHBACK DATABASE TO SCN 122343434; i receive the message saying that i don´t have any flashback logs. I don´t know why these logs disappear. What i whant now is recover database until time because i have all my archives. How can i do this??
RECOVER DATABASE UNTIL SCN my_scnnumber;
ALTER DATABASE OPEN RESETLOGS;
Is just that??
Tks,
Paulo.

Do you have FLASHBACK enabled?
sys@ORCL> select flashback_on from v$database;
FLASHBACK_ON
YES
Elapsed: 00:00:00.03
sys@ORCL>You can do incomplete recovery with user managed backups.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/osrecov008.htm#sthref1743

What really is a wrapper object?

Hi all,
What really is a wrapper object? Can't seem to find a definition that is easily understood.
Thanks

Good Day Friend!
Let me explain you what is wrapper object
java uses primitive types such as int and char for performance reasons. these data types are not part of the object hierarchy. They are passed by value to methods and cannot be directly passed by reference. Also, there is no way for two methods to refer to the same instance of an int. At times, we need to create an object representation for one of these primitive types.For eg, there are collection of these classes, that deal only with objects; to store a primitive type in one of these classes, we need to wrap the primitive type in a class. To address this need, Java provides classes that correspond to each of the primitive types. In essence, these classes encapsulate or wrap the primitive types with in a class. Thus they are commonly referred to as type wrappers.

What really is "UNTIL TIME" ?

Similar Messages

Maybe you are looking for