Restore archive logs
Hi gurus,
I'm in a question, How to restore archive logs backuped?
Scene:
1- We backup the archive logs each hour.
2- We backup the database in a cold backup.
3- We restore the database in another machine.
4- We want to apply this archives in the database restored.
We already do:
1- Restore the archive logs in a temp directory;
2- Shutdown the application
3- Startup Mount
4- rman nocatalog target /
Possibilities already do:
5- Run the command:
RUN {
SET ARCHIVELOG DESTINATION to '/oracle/PRD/saparch';
RESTORE ARCHIVELOG FROM SEQUENCE 52939 UNTIL SEQUENCE 53333;
OR
RESTORE DATABASE UNTIL TIME "TO_DATE('2011-09-06:15:00:00','YYYY-MM-DD:HH24:MI:SS')";
RECOVER DATABASE UNTIL TIME "TO_DATE('2011-09-06:12:00:00','YYYY-MM-DD:HH24:MI:SS')";
OR
RUN
SET ARCHIVELOG DESTINATION TO '/oracle/PRD/saparch';
RESTORE ARCHIVELOG ALL;
To test if this procedure were correct, we got the total entries of a table in production database.
After this procedures, we check a total entries of a table in database restored and the entries isn't equal a production database.
Could you help us?
Thanks,
Denis
Oracle 10g
Aix 6.1
Brazil
HI,
Volker thanks for your replies.
This are the outputs of the commands:
unbru10@root:/:#ls -ltr /oracle/PRD/sapbackup | tail -15
-rwxrwxrwx 1 oraprd dba 422 Mar 22 20:00 backPRD.log
-rwxrwxrwx 1 oraprd dba 9711 Sep 09 16:50 vegsxylp.crv
-rwxrwxrwx 1 oraprd dba 4589 Sep 09 16:51 vegsxyrq.crv
-rwxrwxrwx 1 oraprd dba 4366 Sep 09 16:52 vegsxyuk.crv
-rwxrwxrwx 1 oraprd dba 2461 Sep 12 10:15 vegtlilw.crv
-rwxrwxrwx 1 oraprd dba 1731 Sep 13 07:57 regtpunt.rsa
-rwxrwxrwx 1 oraprd dba 1731 Sep 13 08:06 regtpvix.rsa
-rwxrwxrwx 1 oraprd dba 16224 Sep 13 08:18 vegtpvwk.crv
-rwxrwxrwx 1 oraprd dba 393 Sep 13 08:20 restPRD.log
-rwxrwxrwx 1 oraprd dba 1724 Sep 13 08:20 regtpwqi.rsb
-rwxrwxrwx 1 oraprd dba 5362 Sep 13 08:21 vegtpwqv.crv
-rwxrwxrwx 1 oraprd dba 4367 Sep 13 08:23 vegtpwwa.crv
-rw-r--r-- 1 oraprd dba 8150 Sep 13 08:25 vegtpwyx.crv
-rwxrwxrwx 1 oraprd dba 729 Sep 13 10:29 recovPRD.log
-rw-r--r-- 1 oraprd dba 2461 Sep 13 10:29 vegtqhyk.crv
unbru10@root:/:#ls -ltr /oracle/PRD/saparch | tail -30
-rw-r----- 1 oraprd dba 13652992 Sep 06 14:36 PRDarch1_55003_741174238.dbf
-rw-r----- 1 oraprd dba 13586432 Sep 06 14:44 PRDarch1_55004_741174238.dbf
-rw-r----- 1 oraprd dba 13580288 Sep 06 15:04 PRDarch1_55005_741174238.dbf
-rw-r----- 1 oraprd dba 13630976 Sep 06 15:20 PRDarch1_55006_741174238.dbf
-rw-r----- 1 oraprd dba 13586432 Sep 06 15:22 PRDarch1_55007_741174238.dbf
-rw-r----- 1 oraprd dba 13586432 Sep 06 15:26 PRDarch1_55008_741174238.dbf
-rw-r----- 1 oraprd dba 13591552 Sep 06 15:27 PRDarch1_55009_741174238.dbf
-rw-r----- 1 oraprd dba 13609472 Sep 06 15:35 PRDarch1_55010_741174238.dbf
-rw-r----- 1 oraprd dba 13620736 Sep 06 15:42 PRDarch1_55011_741174238.dbf
-rw-r----- 1 oraprd dba 13586432 Sep 06 15:43 PRDarch1_55012_741174238.dbf
-rw-r----- 1 oraprd dba 14359040 Sep 06 15:44 PRDarch1_55013_741174238.dbf
-rw-r----- 1 oraprd dba 13609472 Sep 06 15:45 PRDarch1_55014_741174238.dbf
-rw-r----- 1 oraprd dba 13585408 Sep 06 15:51 PRDarch1_55015_741174238.dbf
-rw-r----- 1 oraprd dba 13582848 Sep 06 16:00 PRDarch1_55016_741174238.dbf
-rw-r----- 1 oraprd dba 13687808 Sep 06 16:15 PRDarch1_55017_741174238.dbf
-rw-r----- 1 oraprd dba 13589504 Sep 06 16:17 PRDarch1_55018_741174238.dbf
-rw-r----- 1 oraprd dba 13586944 Sep 06 16:22 PRDarch1_55019_741174238.dbf
-rw-r----- 1 oraprd dba 13721088 Sep 06 16:35 PRDarch1_55020_741174238.dbf
-rw-r----- 1 oraprd dba 13642240 Sep 06 16:47 PRDarch1_55021_741174238.dbf
-rw-r----- 1 oraprd dba 13623808 Sep 06 16:47 PRDarch1_55022_741174238.dbf
-rw-r----- 1 oraprd dba 13584896 Sep 06 16:55 PRDarch1_55023_741174238.dbf
-rw-r----- 1 oraprd dba 13629440 Sep 06 16:57 PRDarch1_55024_741174238.dbf
-rw-r----- 1 oraprd dba 13608448 Sep 06 17:09 PRDarch1_55025_741174238.dbf
-rw-r----- 1 oraprd dba 13616640 Sep 06 17:30 PRDarch1_55026_741174238.dbf
-rw-r----- 1 oraprd dba 13596672 Sep 06 19:16 PRDarch1_55027_741174238.dbf
-rw-r----- 1 oraprd dba 13593088 Sep 06 19:19 PRDarch1_55028_741174238.dbf
-rw-r----- 1 oraprd dba 13593600 Sep 09 16:03 PRDarch1_53122_741174238.dbf
-rw-r----- 1 oraprd dba 13586432 Sep 09 16:03 PRDarch1_53123_741174238.dbf
-rw-r----- 1 oraprd dba 4837376 Sep 09 16:46 PRDarch1_53124_741174238.dbf
When i tried to execute the command brrestore -a ...
unbru10:oraprd 5> brrestore -a 54925-55028
BR0401I BRRESTORE 7.00 (32)
BR0405I Start of file restore: regtrbix.rsa 2011-09-13 14.06.43
BR0484I BRRESTORE log file: /oracle/PRD/sapbackup/regtrbix.rsa
BR0252E Function fopen() failed for '/oracle/PRD/saparch/archPRD.log' at location BraSlogRead-2
BR0253E errno 2: No such file or directory
BR0121E Processing of log file /oracle/PRD/saparch/archPRD.log failed
BR0406I End of file restore: regtrbix.rsa 2011-09-13 14.06.43
BR0280I BRRESTORE time stamp: 2011-09-13 14.06.43
BR0404I BRRESTORE terminated with errors
I checked in /oracle/PRD/saparch and the file archPRD.log doesn't exist. How do we recreate it?
Thanks,
Denis
Brazil
Similar Messages
-
Restoring archive log after cold backup
Hello forums users,
I read many thing on this topic but I didn't find the good answer.
I performed a cold backup each sunday.
My database is in ARCHIVE LOG mode.
Is it possible to restore ARCHIVE LOG files after restoring COLD backup?
Sunday : cold backup
Monday : new archive log have been created since cold backup
Tuesday : same as Monday
Wednesday : I would like to restore to Monday 22:00 for example
Can I restore cold backup + apply archive log until Monday 22:00 ?
Regards,
Guillaumerecover database using backup controlfile until cancel|time|logseq|scn
will do this and prompt you for the archivelogs.
Known as 'incomplete recovery'
Hth
Sybrand Bakker
Senior Oracle DBA -
Restore archive log which were not backed up
Hi experts,
as per understandings, after the creation of database the scn will starts from 1 and it grows sequentially,
1)i have not taken any backup until today.
2) i deleted all the archivelogs, but i have database alive
3) taken a full backup.
so i tried to restore from scn 100 to 200.
restore archivelog from scn 100 until scn 200;error:
RMAN-20242: specification does not match any archivelog in recovery cataloag
now my scn is 504575
is it possible to restore archive log from 100 scn to 200 scn?
Thanks & Best Regards.
appriciated for the right answers.784585 wrote:
Hi,
iam not using any STANDBY database..But earlier you said "see if any case accidently missed archives are deleted, those archives need to apply in standby, so what can we do?"
So of course people thought you were trying to sync up a standby ...
i want to generate all the archives from the scratch of the database..
my question is , database SCN will start from 1, so all the database has information from 1 to end...so why cant we take backup again as archives from database?This is pretty basic. You cannot recover from a backup you do not have. You've already said
1)i have not taken any backup until today.
2) i deleted all the archivelogs, but i have database aliveSo with no backup and no archive log, what would expect to recover from?
OK, here's how it works.
As changes are made to the database, a record of the change is written to a memory (not disk) structure called the "redo log buffer". When a transaction is committed the redo log buffer is written to the online redo log file. You must have a minimum of two online redo log files. This online redo log file is of fixed size. When it is full, the process of writing to it switched to the other (or next, if you have more than two). When an online redo log file is filled, and writing of redo info is switched to the next file, the filled file is copied to a NEW archived log file. After going through all the online redo logs in this round-robin fashion, it will come back to the first and start overwriting its previous contents. The archived log files are given unique names so that they are not over written but instead generate a constant stream of new archivelogs. It is these archive log files that contain all of your redo info that pre-dates the oldest info remaining in the online redo logs.
In a recovery operation, the following happens
first, the database files are restored from backup, starting with the newest full backup that meets your recovery needs, then following with all incremental backups after that. You said you have no backups prior to today.
Second, after the files are restored from backups (which you said you don't have) additional redo information is applied to get the changes since the most recent full or incremental backup that was restored. This additional info comes from the archivelog files, which you said you didn't back up and apparently you deleted.
So, you've said you have no database backup and no archivlogs either backed up or original. So from where do you expect to be able to recover this information? -
RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE
제품 : RMAN
작성날짜 : 2002-12-09
RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE
==========================================================
PURPOSE
이 자료는 Oracle 9.2 이상의 RMAN에서 사용 가능한 MAXSIZE 기능에 대하여
설명할 것이다.
How to restore archive logs with limited disk space
Old Backup을 사용하여 RMAN으로 database를 recvoery할때, 모든 archived
redo logfile들을 Restore할 destination의 disk space가 모자란 경우를 종종 만난다.
이러한 경우 여러 개의 restore and recovery job으로 나누어 수행한다.
즉, 첫 번째 restore and recovery job이 끝나면 archived redo logfile들을 지우고
다음 적용될 것들을 restore한다. 그리고 다시 Recovery를 수행한다. 이러한 작업을
원하는 시점까지 recovery를 하기위해 반복적으로 수행한다.
Oracle 9iR2(9.2.0.x)부터 RMAN은 MAXSIZE option을 제공하는데 이것은 archive log
file이 restore될 disk의 space를 control할 수 있게 해 준다.
만약 disk space가 매우 제한적이라면, 즉 예를 들어 모든 archive log의 size 합보다
disk free space가 적다면 MAXSIZE option을 사용하는 것은 매우 유용하다.
이 OPTION이 기술되면 RMAN은 Media Manager에게 disk space 크기에 부합하는 만큼만
archive log들을 restore하도록 한다. 부가적인 restore operation들은 restore된
마지막 archive log가 적용될 때마다 발생한다.
MAXSIZE option은 이러한 작업들을 하나의 rman job으로 처리하게 해 주고
실수를 하지 않게 해 준다.
아래는 MAXSIZE를 설명하기 위한 예제이며 총 6 단계로 구성되어 있다.
STEP 1: Add data to the database to enforce log switches
STEP 2: Backup the database and archive logs and delete the logs
STEP 3: Add additional data to enforce new log switches
STEP 4: Remove the data file and simulate a database crash
STEP 5: Restore the data file from the backup
STEP 6: Recover the database using MAXSIZE
위 예제는 Unix와 Windows 모두에 적용될 수 있다.
STEP 6 는 다음과 같은 조건으로 두 번 수행될 것이다.
1) MAXSIZE가 archive log size보다 작은 경우:
이 경우 RMAN-6558 Error message를 만나게 된다.
그러므로 MAXSIZE를 archive log보다는 크게 설정해야한다.
2) MAXSIZE가 archive log size보다 큰 경우:
예를 들어 여러 개의 archive log를 포함할 수 있을 정도로 크게 설정하면
restore/recovery는 user에게 transparent하게 수행되어진다.
즉 archive log들은 restore된 후 applied되고 deleted되어 진다. 다시 새로운
archive log들이 restore되어지고 applied된 후 deleted 되어 진다. 이러한 작업은
recovery가 끝날 때까지 반복되어진다. 이러한 작업들이 진행되는 동안 RMAN은
아무런 Message도 발생시키지 않는다.
# Step 1: INSERT enough new data to generate log switches
create table rman_tst (col1 varchar2 (10));
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 2: BACKUP the database and the archive logs automatically
# and then delete the input
run {
backup database format='/web01/usupport/krosenme/admin/backups/db_%d%s%t'
plus archivelog format='/web01/usupport/krosenme/admin/backups/arch_%d%s%t'
delete input;
# Step 3: INSERT enough new data to generate new log switches
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 4: REMOVE users01.dbf file and crash the database
mv users01.dbf users01.org
shutdown abort
# Restore is now needed as the data file is deleted. The backup was
# taken before the new data was added to it, thus archive logs are
# needed to bring the database up to date
# Step 5: RESTORE the data file from the full backup
run {
restore datafile '/web01/usupport/krosenme/oradata/kro_920/users01.dbf';
# Step 6: RECOVER
run {
recover database delete archivelog maxsize 10 K;
# This will fail with RMAN-6558 as the archived log has a size of 16 KB,
# which is bigger than MAXSIZE limit of 10 KB. So the error is expected
# and MAXSIZE works as designed.
# Now rerunning STEP 6: but with MAXSIZE 50 K
run {
recover database delete archivelog maxsize 50 K;
RELATED DOCUMENTS
Recovery Manager Reference, Release 2 (9.2)cold backup means offline backup, you shut database normally and copy datafiles to another location.
i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
backing up archivelogs whith rman script which is:
run {
allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
change archivelog all validate;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
release channel c1;
so here is the details.
1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
So
first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
and then restore them and then apply them.
we need rman commands to register these backups and restore them.
Regards,
Kamil -
Hi,
in 10g R2 , my DB is backed up (all database, control files and Archived logs) every day. Now I need to restore the archived logs (from first of may to 15 of may) in a folder. How can I do that ?
Thank you.Ok , thank you.
I found this :
RMAN> RUN
SET ARCHIVELOG DESTINATION TO '/oracle/temp_restore';
RESTORE ARCHIVELOG ALL;
}here
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta051.htm#RCMRF149
but when executing I receive :
RMAN-06025 no backup of log thread 1 seq 6 scn 843036 found to restore
RMAN-06025....................................................................................................
RMAN-06025....................................................................................................
RMAN-06025....................................................................................................
RMAN-06025....................................................................................................What other option to use instead of ALL, to restore what is available ?
I know that there are the following options:
from, high, like, logseq, low, scn, sequence, time, untilbut do not know how to determine which option with which value to chose ?
For
restore archivelog FROM sequence 23 until sequence 99 ;how can I determine the available sequence in backup ?
Thank you.
Edited by: user522961 on May 21, 2009 8:53 AM -
How to restore archive logs with rman
Hi,
here is the scenario:
we have lost everything because of disk failure.
we have a full cold backup and archivelog backups which were created after cold backup and were backed up with rman.
after restoring from cold backup, because archivelog backups do not exist in controlfile, how can we catalog archivelog backups and restore them?
could you give me the exact rman command for this?
Best Regards,
Kamilcold backup means offline backup, you shut database normally and copy datafiles to another location.
i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
backing up archivelogs whith rman script which is:
run {
allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
change archivelog all validate;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
release channel c1;
so here is the details.
1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
So
first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
and then restore them and then apply them.
we need rman commands to register these backups and restore them.
Regards,
Kamil -
RMAN not able to restore archive logs from net backup
Hello Everybody,
While trying to restore a datafile and then recover the database, RMAN failed with the following error stack.
RMAN-03002: failure of recover command at 12/05/2007 09:19:24
ORA-19870: error reading backup piece arch-s110-p1
ORA-19615: some files not found in backup set
ORA-19614: archivelog thread 1 sequence 231 not found in backup set
ORA-19614: archivelog thread 1 sequence 230 not found in backup set
ORA-19614: archivelog thread 1 sequence 229 not found in backup set
But when I do a crosscheck the status is shown as Available. We are using net backup as MML.
Could you please suggest any alternatives to solve this issue.
Regards
Satish V ChandranGive some other location than /tmp and see if it works.
-
How restore Archive log from one unix server to another server and how analyses witch archive log resore after online backup
kaviI have restore full online backup then offline archive log
BR0280I BRRECOVER time stamp: 2010-07-15 07.30.06
BR0657I Input menu 134 - please check/enter input values
Applying archivelog files to database PRD
1 - Archivelog directory (archive_dir) ....... [/oracle/PRD/oraarch]
2 # Instance of archivelog thread (instance) . []
3 ~ Apply from redolog group (apply_redo) .... []
4 - First sequence number (first_seq) ........ [38055]
5 - Last sequence number (last_seq) .......... [38084]
6 ~ Last system change number (last_scn) ..... []
7 ~ End point-in-time (end_pit) .............. []
8 - Use backup control file (back_ctl) ....... [no]
9 ~ Parallel recovery (degree) ............... []
10 - SQLPLUS command (command) ................ [recover from '/oracle/PRD/oraarch' dat
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
c
BR0280I BRRECOVER time stamp: 2010-07-15 07.30.10
BR0663I Your choice: 'c'
BR0259I Program execution will be continued...
BR0783I Archivelog files with sequence number 38055-38084 of database instance PRD will
BR0280I BRRECOVER time stamp: 2010-07-15 07.30.10
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
c
BR0280I BRRECOVER time stamp: 2010-07-15 07.30.12
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRRECOVER time stamp: 2010-07-15 07.30.12
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38055_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38056_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38057_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38058_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38059_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38060_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38061_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38062_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38063_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38064_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38065_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38066_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38067_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38068_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38069_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38070_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38071_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38072_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38073_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38074_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38075_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38076_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38077_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38078_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38079_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38080_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38081_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38082_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38083_637623713.dbf
BR0336I Applying offline redo log file /oracle/PRD/oraarch/PRDarch1_38084_637623713.dbf
BR0278E Command output of '/oracle/PRD/102_64/bin/sqlplus':
SQL*Plus: Release 10.2.0.2.0 - Production on Thu Jul 15 07:30:12 2010
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
SQL> Connected.
SQL>
SQL> SQL> ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SQL> SP2-0734: unknown command beginning "/oracle/PR..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
SQL> startup
ORACLE instance started.
Total System Global Area 4714397696 bytes
Fixed Size 2050336 bytes
Variable Size 2365589216 bytes
Database Buffers 2332033024 bytes
Redo Buffers 14725120 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 337067467 generated at 07/14/2010 09:56:10 needed for thread
1
ORA-00289: suggestion : /oracle/PRD/oraarch/PRDarch1_38055_637623713.dbf
ORA-00280: change 337067467 for thread 1 is in sequence #38055
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 337067467 generated at 07/14/2010 09:56:10 needed for thread
1
ORA-00289: suggestion : /oracle/PRD/oraarch/PRDarch1_38055_637623713.dbf
ORA-00280: change 337067467 for thread 1 is in sequence #38055
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00279: change 337080381 generated at 07/14/2010 10:21:14 needed for thread
1
ORA-00289: suggestion : /oracle/PRD/oraarch/PRDarch1_38056_637623713.dbf
ORA-00280: change 337080381 for thread 1 is in sequence #38056
ORA-00278: log file '/oracle/PRD/oraarch/PRDarch1_38055_637623713.dbf' no
longer needed for this recovery
ORA-00279: change 337092700 generated at 07/14/2010 10:34:19 needed for thread
1
ORA-00289: suggestion : /oracle/PRD/oraarch/PRDarch1_38057_637623713.dbf
ORA-00280: change 337092700 for thread 1 is in sequence #38057
ORA-00278: log file '/oracle/PRD/oraarch/PRDarch1_38056_637623713.dbf' no
longer needed for this recovery
ORA-00279: change 337101635 generated at 07/14/2010 10:36:42 needed for thread
1
ORA-00289: suggestion : /oracle/PRD/oraarch/PRDarch1_38058_637623713.dbf
ORA-00280: change 337101635 for thread 1 is in sequence #38058
ORA-00278: log file '/oracle/PRD/oraarch/PRDarch1_38057_637623713.dbf' no
longer needed for this recovery
ORA-00279: change 337110148 generated at 07/14/2010 10:38:59 needed for thread
How start my orackle -
RMAN: How to apply Archive Logs after recoverying of all physical files
Hi;
I am using RMAN Oracle10g; my test database has being corrupted. I have already taken 0 level backup through this command
run {
allocate channel c1 type disk;
backup incremental level 0 tag = Test_Weekly_database format 'O:\rman\backup\Full_Weekly_%d_%s_%p_%t'(database);
release channel c1;
configure controlfile autobackup format for device type disk to 'O:\rman\backup\Auto_Ctrl_weekly_%F';
allocate channel c1 type disk;
sql 'alter system archive log current';
BACKUP tag = Test_Weekly_Arch ARCHIVELOG UNTIL TIME 'SYSDATE-7' format 'O:\rman\backup\Archive_weekly_%d_%s_%p_%t';
DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
release channel c1;
After backing up I inserted few records in TEST123 table. And switch current log file.
Then my database has been corrupted. Now I have last 0 level backup (RMAN) and archive logs files on OS level.
I am recovering my database with the following commands; but archive logs have not being applied. And my inserted records were not presented in TEST123 table.
Kindly guide me
SQL> startup nomount
CMD> RMAN target=/
RMAN>set DBID 1168995671
RMAN>RUN {
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
RESTORE CONTROLFILE from autobackup;
RMAN> ALTER DATABASE MOUNT;
RMAN> RESTORE DATABASE CHECK READONLY;
RMAN> RECOVER DATABASE NOREDO;
RMAN> restore archivelog all;
SQL> startup mount
SQL> alter database backup controlfile to trace;
SQL> shut immediate
SQL> startup nomount
SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG................;
SQL> alter database open resetlogs
---Database altered.
SQL> select * from TEST123;
Not record found
regards;
AsimDear Khurram;
Kindly advise where i m worrg???????
C:\>RMAN target=/
RMAN> set DBID 1168995671
executing command: SET DBID
RMAN> RUN {
2> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
3> RESTORE CONTROLFILE from autobackup;
4> }
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
Starting restore at 27-DEC-07
using channel ORA_DISK_1
recovery area destination: O:\rman\backup
database name (or database unique name) used for search: ORCL
channel ORA_DISK_1: no autobackups found in the recovery area
channel ORA_DISK_1: looking for autobackup on day: 20071227
channel ORA_DISK_1: autobackup found: O:\rman\backup\Auto_Ctrl_weekly_c-11689956
71-20071227-04
channel ORA_DISK_1: control file restore from autobackup complete
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
Finished restore at 27-DEC-07
RMAN> ALTER DATABASE MOUNT;
database mounted
released channel: ORA_DISK_1
RMAN> RESTORE DATABASE CHECK READONLY;
Starting restore at 27-DEC-07
Starting implicit crosscheck backup at 27-DEC-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=155 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=154 devtype=DISK
Crosschecked 9 objects
Finished implicit crosscheck backup at 27-DEC-07
Starting implicit crosscheck copy at 27-DEC-07
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 27-DEC-07
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
restoring datafile 00005 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST.DBF
restoring datafile 00006 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST2
channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_
1_642420573
channel ORA_DISK_1: restored backup piece 1
piece handle=O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_1_642420573 tag=Test_WEEKLY_DATAB
ASE
channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
Finished restore at 27-DEC-07
RMAN> restore archivelog all;
archive log thread 1 sequence 1 is already on disk as file O:\ARCHIVE\ARC00001_0642356125.001
archive log thread 1 sequence 2 is already on disk as file O:\ARCHIVE\ARC00002_0642356125.001
archive log thread 1 sequence 3 is already on disk as file O:\ARCHIVE\ARC00003_0642356125.001
archive log thread 1 sequence 4 is already on disk as file O:\ARCHIVE\ARC00004_0642356125.001
archive log thread 1 sequence 5 is already on disk as file O:\ARCHIVE\ARC00005_0642356125.001
archive log thread 1 sequence 6 is already on disk as file O:\ARCHIVE\ARC00006_0642356125.001
archive log thread 1 sequence 7 is already on disk as file O:\ARCHIVE\ARC00007_0642356125.001
archive log thread 1 sequence 8 is already on disk as file O:\ARCHIVE\ARC00008_0642356125.001
archive log thread 1 sequence 9 is already on disk as file O:\ARCHIVE\ARC00009_0642356125.001
archive log thread 1 sequence 10 is already on disk as file O:\ARCHIVE\ARC00010_0642356125.001
archive log thread 1 sequence 11 is already on disk as file O:\ARCHIVE\ARC00011_0642356125.001
archive log thread 1 sequence 12 is already on disk as file O:\ARCHIVE\ARC00012_0642356125.001
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=15
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=16
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=17
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=18
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=19
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=20
channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630
channel ORA_DISK_1: restored backup piece 1
piece handle=O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630 tag=Test_WEEKLY_ARCH
channel ORA_DISK_1: restore complete, elapsed time: 00:00:08
Finished restore at 27-DEC-07
RMAN> ALTER DATABASE OPEN;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 12/27/2007 10:27:10
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
Regards;
Asim -
Hi
I need to restore archive logs from the tape. I am pretty new on this, do i have to go brtools and restore the archive logs or there is a t code in sap that I can recover from that? if it is using brtools, what is step and procedure? do I have to use sqlplus? while I am doing this type of recovery, do I need to shut the dabase down?
please share
thanksWei,
You can restore redo logs from below command.
brrestore -a <start_log#>-<end_log#> -c -d util_file -r <Oracle_Home>\database\initSID.utl
If you want to do a restore & recovey you can go for point intime recovery. Here You need to restore online backup & then additionally need to apply redologs which were generated after the online backup.
Check below link for details.
http://help.sap.com/saphelp_nw04/helpdata/en/93/4ffb72309fb04e80ebfefae1b7a96f/frameset.htm
also check below SAP notes which will answers of your questions.
602497 - BRRECOVER - New tool for Oracle Restore and Recovery
Note 4161 - Complete Recovery
Note 23070 - Backup and Recovery: Basic Concepts
Note 4160 - Tape management for recovery
Hope this helps
Thanks
Sushil -
Incomplete Recovery Fails using Full hot backup & Archive logs !!
Hello DBA's !!
I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
3) Restored all Hot backup files from Tape to Test Server.
4) Restored all archive logs from tape to Test server.
5) Restored Latest Binary Control file from Tape to Test Server.
6) Now, Started recovery using following command from SQL prompt.
SQL> recover database until cancel using backup controlfile;
7) Open database after Recovery Completion using RESETLOGS option.
Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
Let me know What should be the reason behind recovery failure !
Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
Atul Patil.oh you made up a new thread so here again:
there is nothing wrong.
You restored your backup, archives etc.
you started your recovery and oracle applyed all archives but the archive
'/oracle/EPR/oraarch/1_9624_601570270.dbf'
does not exist because it represents your current online redo log file and that is not present.
the recovery process cancels by itself.
the solution is:
restart your recovery process with:
recover database until cancel using backup controlfile
and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
type cancel!
now you should be able to open your database with open resetlogs. -
Dear All,
Please help me at the time of Netvault RMAN backup how i move the archive log file another location.
Normal case if i moved the archive log file Netvault RMAN backup fail, so please suggest.
Thanks,
ManasHi;
You have to login https://support.oracle.com/CSP/ui/flash.html and you have to CSI account.
This site is oracle site for tech. documents for can rise SR etc.. for more details please check Re: Installing Oracle Database 10.2.0.4
you need to customer support identifier which is called CSI for can login metalink(https://support.oracle.com/CSP/ui/flash.html)
If you dont have metalink account there is no way to see doc or download patch.
Pretty simple process:
1) You purchase a perpetual or term license from Oracle;
2) At the beginning of the period, during the valid term you purchase
Support for the period (1 year);
3) Oracle sends you the CSI.
Easy to do at http://store.oracle.com armed with a credit card.
You can also see:
http://repettas.wordpress.com/2008/11/01/restore-archive-logs-to-new-location-using-rman/
http://oracledisect.blogspot.com/2008/06/when-your-archive-log-destination-is.html
Regard
Helios -
How to restore cold backup + archived log files
Hi,
Suppose I take a cold backup on 18th. After that I have four days of archived log files. if the database crashes on 5th day, I have to restore the 18th cold back + 4 days of archived log files. How do I restore since it is a cold backup and I cant do incomplete recovery.
can I use
Recover database ( with 18th cold backup) in mount state and apply archived logs.
PrabhathThe details of how you perform forward recovery using a cold backup depends on
1- rman or manual backup
2- using current or backup control file
3- if rman, recovery catalog or no recovery catalog
4- if full database recovered or only a few files
Each of these conditions will affect what is known to Oracle and what needs to be done. For example if you restored the entire cold backup including the control file then Oracle would see a consistent database and not need to perform recovery so you would need to startup mount and tell the database to perform recovery using a backup control file. If using rman and no recovery catalog you might need to catalog some of the archived redo logs, etc....
It is advisable to consult the Backup and Recovery manuals before attempting recovery for any new scenario.
HTH -- Mark D Powell -- -
What order are Archive logs restored in when RMAN recover database issued
Ok, you have a run block that has restored your level-0 RMAN backup.
Your base datafiles are down on disc.
You are about to start recovery to point in time, lets say until this morning at 07:00am.
run { set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
recover database;
So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
required and starts to restore the archive logs. All as expected and works.
My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
Any inputs on experience welcome. I am now drilling into the documentation for any references there.
ThanksHi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
This is from interpreting the list backup of archivelog commands.
Backupset = 122672
==============
Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
Backupset = 122677
==============
Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
Thanks for inputs. Answers some questions. -
RMAN archive logs backup and restore in RAC environment.
Hello All,
I have a 8 node RAC using ASM production database and a single node standby database using ASM. I have archive log gap on the standby database and the archive logs on the primary database is backed up and removed.
I need to resync the standby database using RMAN backup/restore.
Could you please help me on how to backup the specific archive logs file (all threads) from production and restore/recover the standby database. Any specific RMAN script or Metalink ID will help alot.
Details:
Source: 8 node RAC, ASM, Linux,
target: Non-RAC, ASM, Linux.
Regards,You can try LIKE clause of BACKUP ARCHIVELOG such as:
RMAN> backup archivelog like '%XE%2010%20%';
Starting backup at 20-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=58 recid=19 stamp=727519553
input archive log thread=1 sequence=59 recid=20 stamp=727544121
input archive log thread=1 sequence=60 recid=21 stamp=727544127
channel ORA_DISK_1: starting piece 1 at 20-AUG-10
channel ORA_DISK_1: finished piece 1 at 20-AUG-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_08_20\
O1_MF_ANNNN_TAG20100820T154401_66X1O353_.BKP tag=TAG20100820T154401 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 20-AUG-10or you can try SEQUENCE clause:
RMAN> backup archivelog sequence between 58 and 60 thread 1;
Starting backup at 20-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=58 recid=19 stamp=727519553
input archive log thread=1 sequence=59 recid=20 stamp=727544121
input archive log thread=1 sequence=60 recid=21 stamp=727544127
channel ORA_DISK_1: starting piece 1 at 20-AUG-10
channel ORA_DISK_1: finished piece 1 at 20-AUG-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_08_20\
O1_MF_ANNNN_TAG20100820T154911_66X1YRJL_.BKP tag=TAG20100820T154911 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 20-AUG-10or
RMAN> backup archivelog sequence between 58 and 60;
Starting backup at 20-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=58 recid=19 stamp=727519553
input archive log thread=1 sequence=59 recid=20 stamp=727544121
input archive log thread=1 sequence=60 recid=21 stamp=727544127
channel ORA_DISK_1: starting piece 1 at 20-AUG-10
channel ORA_DISK_1: finished piece 1 at 20-AUG-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_08_20\
O1_MF_ANNNN_TAG20100820T154748_66X1W5Z0_.BKP tag=TAG20100820T154748 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 20-AUG-10See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta008.htm#i78730
Maybe you are looking for
-
Safari painfully slow on new Mac Mini
I know there have been a number of threads on this topic and I have tried all of the tricks listed but Safari is still painfully slow to load web pages. I have tested my internet connection and it is fine. The real interesting thing here is that when
-
Struts - Problem with ActionMessages
Hi everyone: Here is my problem: This is the code in my action class catch (Exception e){ ActionMessages errors = new ActionMessages(); if (e instanceof DatabaseException) errors.add("e
-
this is not a smart tv butI have a question , can I conect that TV to internet via WI-FI USB adapter only?
-
Hi, Can you tell me where can i find detailed descriptions about General Ledger Reports in R12? on what documentation? and one more question do you know which report can i used to report numbering and reporting sequences?. Thanks a lot. Lena
-
"An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX
Hi all, While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58 Only a particular Idoc type is having this issue. Below are the checks done before posting this query: 1. Pushed other Idocs from the SAP ECC t