Archivelog deletion policy for GG
Hi All,
We have GG on one of the database.
The archivelog is getting deleted before it is applied to GG. The archivelog needs to be restored manually to proceed GG to work properly.
This is very frequent. Now every time the archivelog needs to be restored manually.
As far is i know there is archivelog deletion policy is there for standby. which will not delete the archivelog until it is applied to standby.
Is there any policy for GG so that archivelog which is required by GG should not delete by RMAN until it is applied to GG.
Kindly suggest.
Thanks,
Hi,
To ensure that RMAN retains all archive logs required by Oracle Golden Gate, when you add or register an Extract group in GGSCI with ADD EXTRACT (TRANLOG option) or REGISTER EXTRACT.
You can configure Extract to retain enough logs through RMAN for a normal recovery by using the TRANLOGOPTIONS parameter with the LOGRETENTION option set to SR.
You can read more about this feature in detail in the OGG Installation Guide on Oracle database, pages 58 & 59.
Regards,
RB
Similar Messages
-
Retention policy vs. Archivelog deletion policy
Environment:
Oracle EE 11.2.0.3 on Solaris 10.5
Which policy takes precedence?
My Retention Policy is set to 'Recovery window of 8 days' and my Archivelog deletion policy is set to 'backed up 2 times to disk'.
My DAILY full backup happens at 03:00am and uses the following commands:
backup incremental level 0 cumulative database tag 'full_daily' plus archivelog tag 'full_daily';
DELETE NOPROMPT OBSOLETE;I also have an archivelog backup that runs every 4 hours at 02:00, 06:00, 10:00, 14:00, 18:00 and 22:00 and looks like this:
backup archivelog all tag '&1';
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';With the archivelog backup running every 4 hours the logs are getting backed up to disk the required 2 times very quickly. Much sooner than 8 days! :-)
I have a problem where the archivelog backup that runs immediately AFTER the full database backup fails due to not being able to find some older archivelog files.
In looking at V$ARCHIVED_LOG the files were dated (COMPLETION_DATE) just outside the 8 day retention window but they had a status of 'A' (Archived) instead of the 'D' (Deleted) I was expecting. When I ran a 'Crosscheck archivelog all' it changed the statuses to 'D' and the next archivelog backup ran successfully.
What am I missing?
Should I change the archivelog deletion policy to something else? If so, what and why (just trying to understand!) ?
I am not using an FRA and have controlfile autobackup turned on.
Please let me know if you need more information. I have been scouring the docs and the 11g RMAN Oracle Press book but haven't found the trick yet!
Thanks for any assistance!
-garyHemant K Chitale wrote:
The Retention Policy applies to Backups. It does not apply to ArchiveLogs.
The ArchiveLog Deletion Policy applies to ArchiveLogs. It does not apply to Backups.
Since you have 2 copies of ArchiveLogs in the backups and these are retained for 8 days, a "delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';" is overkill. Why retain 8 days of archivelogs on disk if there are 2 copies already backed up ?
Does your full backup that begins at 3am complete before 6am ? If it goes beyond 6am, it will be deleting some files after 6am but the "backup archivelog all" at 6am will expect some archivelogs (8 days old) to be present.
Hemant K Chitale
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';
Starting backup at 22-MAY-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00001 name=/oracle/oracle/oradata/orcl/system01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_system_7vpg432v_.dbf tag=TAG20120522T122602 RECID=1 STAMP=783951999
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:46
channel ORA_DISK_1: starting datafile copy
input datafile file number=00002 name=/oracle/oracle/oradata/orcl/sysaux01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_sysaux_7vpg5l1n_.dbf tag=TAG20120522T122602 RECID=2 STAMP=783952038
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile copy
input datafile file number=00003 name=/oracle/oracle/oradata/orcl/undotbs01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_undotbs1_7vpg6ms0_.dbf tag=TAG20120522T122602 RECID=3 STAMP=783952046
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=/oracle/oracle/oradata/orcl/users01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_users_7vpg6ptn_.dbf tag=TAG20120522T122602 RECID=4 STAMP=783952047
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
Finished backup at 22-MAY-12
Starting Control File and SPFILE Autobackup at 22-MAY-12
piece handle=/oracle/oracle/product/11.2.0/dbhome_1/dbs/controlfile_c-1309370544-20120522-02 comment=NONE
Finished Control File and SPFILE Autobackup at 22-MAY-12
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';
new RMAN configuration parameters are successfully stored
RMAN> delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=196 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_04_28/o1_mf_1_2_7sq8tf5p_.arc thread=1 sequence=2
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_05_22/o1_mf_1_3_7vpdcjjm_.arc thread=1 sequence=3
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN> having problem with Archivelog backup. -
ARCHIVELOG DELETION POLICY 10g?
I know in 11g, we have this command.
RMAN>CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 3 TIMES TO DEVICE TYPE sbt;
is there a similar command in 10g as well for this feature?Hi Karl,
You can enforce a similar strategy inside the backup script for 10g.
# Delete archived log entries before the run
delete noprompt copy of archivelog all backed up 3 times to SBT_TAPE;
backup
filesperset 20
format='al_%d_%s_%p_%t'
archivelog all ;
# Delete archived log entries after the run
delete noprompt copy of archivelog all backed up 3 times to SBT_TAPE;If for some reason the backup fails halfway through the run, the before delete will purge all archivelogs already 3 times on tape.
Regards,
Tycho -
RMAN show archivelog deletion policy;
RMAN> show archivelog deletion policy;
RMAN configuration parameters are:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
What choices i have for its deletion policy? I want to carry only 30 days archivelogs , How i can chnage that?Hello,
These are the options.
When backups of archived redo log files are taken on the standby database:
1)Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2) Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
When backups of archived redo log files are taken on the primary database:
1) Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2) Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
Check this url for more info
https://dpt-info.u-strasbg.fr/doc/oracle/server.102/b14239/rman.htm
-Sri -
Question about Archive Log Deletion policy
I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
Messages of the database are in German, but I guess you'll understand them.
SQL> startup
ORACLE-Instance hochgefahren.
Total System Global Area 5344731136 bytes
Fixed Size 2129240 bytes
Variable Size 2684355240 bytes
Database Buffers 2617245696 bytes
Redo Buffers 41000960 bytes
Datenbank mounted.
Datenbank geöffnet.
SQL> archive log list
Datenbank-Log-Modus Archive-Modus
Automatische Archivierung Aktiviert
Archivierungsziel E:\oracle\thetis_iv\arch
Älteste Online-Log-Sequenz 17917
Nächste zu archivierende Log-Sequenz 17919
Aktuelle Log-Sequenz 17919
SQL> alter system switch logfile;
System wurde geändert.I created a brand new archive log.
SQL> exit
Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:04 <DIR> .
06.04.2011 15:04 <DIR> ..
06.04.2011 15:04 17.137.152 ARC17919_0721667907.001
1 Datei(en), 17.137.152 Bytes
2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
Kennwort für Recovery-Katalog-Datenbank:
Verbindung mit Datenbank des Recovery-Katalogs
RMAN> show all;
RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
Now I backup all archive logs, that havn't been backed up for at least two times.
RMAN> run { backup archivelog all not backed up 2 times
2> format '%d_AR_%Y%M%D_%s_%t'
3> tag 'ARCHIVE LOGS'
4> DELETE ALL INPUT;
5> }
Starten backup um 06.04.2011 15:08:01
Aktuelles Log archiviert
Zugewiesener Kanal: ORA_SBT_TAPE_1
Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
Beendet backup um 06.04.2011 15:08:10
RMAN> exit
Recovery Manager abgeschlossen.
D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
Datenträger in Laufwerk E: ist Volume
Volumeseriennummer: 3EBD-77E5
Verzeichnis von E:\oracle\thetis_iv\arch
06.04.2011 15:08 <DIR> .
06.04.2011 15:08 <DIR> ..
0 Datei(en), 0 Bytes
2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
Thats not what I expected. Where is my mistake?Hi,
I do new tests it's very strange.
BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
You can open a SR on MOS. (to check bugs)
I reproduce the same test and the result was the same, it seems that this is a bug.
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
RMAN> backup archivelog all not backed up 2 times delete all input;
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=16 STAMP=747753711
input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
Finished backup at 06-APR-11
RMAN> list archivelog all;
specification does not match any archived log in the repositoryOracle Docs Says:
The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
This command eliminates the separate step of manually deleting archived redo logs.
With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
As explained in "Configuring an Archived Redo Log Deletion Policy",
the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
But in ours case it's not honors this policy.
Only with the FORCE command should this happen. But it is not our case.
Oracle Docs:
If FORCE is not specified on the deletion commands,
then these deletion commands obey the archived log deletion policy.
If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
Alternatively you can do the following:
Set the commands separately.
Check this:
RMAN> run {
2> backup archivelog all not backed up 2 times ;
3> delete archivelog all backed up 2 times to disk;
4> }
Starting backup at 06-APR-11
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
channel ORA_DISK_1: starting piece 1 at 06-APR-11
channel ORA_DISK_1: finished piece 1 at 06-APR-11
piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 06-APR-11
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM -
Data guard and RMAN deletion policy.
Dear experts,
I have Data guard setup with physical standby. I scheduled backup archivelog to tape from both primary and standby servers. I need that archivelogs will be deleted only after shiped on standby and after backup 1 time to tape device. So I set following RMAN configure command.
I am using separate RMAN catalogs for primary and secondary.
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
After I did a test.
1. Stop standby
2. Generate archivelogs in Primary (so to fill 100% the FRA )
3. Backup archivelogs
4. Start standby
The logs dosen't shiped to standby because Oracle deleted them to free up space in FRA. So the second part of my deletion policy don't want to work. My goal is that when FRA is full the primary will hang instead of deleting not yet shiped archivelogs.
Please share with me your experience.
Thanks in advance.Hello;
Test on 11.2.0.3
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN-08591: WARNING: invalid archived log deletion policy
But this is OK
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO 'SBT_TAPE' SHIPPED TO ALL STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
These should work:
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY;
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Best Regards
mseberg -
Retention policy for incremental cumulative backup question
Hi,
I have a production database configured with retention policy for 30 days window. No catalog is used.
The backup plan is:
Sunday - Level 0 backup.
Weekdays - Incremental 1 cumulative backup.
I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
Thanks for your help!
RMAN> list backup summary;
using target database control file instead of recovery catalog
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
*14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
*17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
21 B F A SBT_TAPE 08-MAR-10 1 1 NO
24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
27 B F A SBT_TAPE 08-MAR-10 1 1 NO
35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
38 B F A SBT_TAPE 09-MAR-10 1 1 NO
46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
49 B F A SBT_TAPE 10-MAR-10 1 1 NO
57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
60 B F A SBT_TAPE 11-MAR-10 1 1 NO
66 B A A SBT_TAPE 12-MAR-10 1 1 NO
67 B A A SBT_TAPE 12-MAR-10 1 1 NO
68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
70 B A A SBT_TAPE 12-MAR-10 1 1 NO
71 B F A SBT_TAPE 12-MAR-10 1 1 NO
77 B A A SBT_TAPE 14-MAR-10 1 1 NO
78 B A A SBT_TAPE 14-MAR-10 1 1 NO
79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
81 B A A SBT_TAPE 14-MAR-10 1 1 NO
82 B F A SBT_TAPE 14-MAR-10 1 1 NO
88 B A A SBT_TAPE 15-MAR-10 1 1 NO
89 B A A SBT_TAPE 15-MAR-10 1 1 NO
90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
92 B A A SBT_TAPE 15-MAR-10 1 1 NO
93 B F A SBT_TAPE 15-MAR-10 1 1 NO
99 B A A SBT_TAPE 16-MAR-10 1 1 NO
100 B A A SBT_TAPE 16-MAR-10 1 1 NO
101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
103 B A A SBT_TAPE 16-MAR-10 1 1 NO
104 B F A SBT_TAPE 16-MAR-10 1 1 NO
109 B A A SBT_TAPE 17-MAR-10 4 1 NO
110 B F A SBT_TAPE 17-MAR-10 1 1 NO
111 B A A SBT_TAPE 17-MAR-10 1 1 NO
112 B F A SBT_TAPE 17-MAR-10 1 1 NO
113 B A A SBT_TAPE 17-MAR-10 1 1 NO
114 B A A SBT_TAPE 17-MAR-10 1 1 NO
115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
117 B A A SBT_TAPE 17-MAR-10 1 1 NO
118 B F A SBT_TAPE 17-MAR-10 1 1 NO
123 B A A SBT_TAPE 18-MAR-10 2 1 NO
124 B F A SBT_TAPE 18-MAR-10 1 1 NO
125 B A A SBT_TAPE 18-MAR-10 2 1 NO
126 B F A SBT_TAPE 18-MAR-10 1 1 NO
127 B A A SBT_TAPE 18-MAR-10 1 1 NO
128 B F A SBT_TAPE 18-MAR-10 1 1 NO
129 B A A SBT_TAPE 18-MAR-10 1 1 NO
130 B F A SBT_TAPE 18-MAR-10 1 1 NO
131 B A A SBT_TAPE 18-MAR-10 1 1 NO
132 B A A SBT_TAPE 18-MAR-10 1 1 NO
133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
135 B A A SBT_TAPE 18-MAR-10 1 1 NO
136 B F A SBT_TAPE 18-MAR-10 1 1 NO
142 B A A SBT_TAPE 19-MAR-10 2 1 NO
143 B F A SBT_TAPE 19-MAR-10 1 1 NO
144 B A A SBT_TAPE 19-MAR-10 1 1 NO
145 B F A SBT_TAPE 19-MAR-10 1 1 NO
146 B A A SBT_TAPE 19-MAR-10 1 1 NO
147 B F A SBT_TAPE 19-MAR-10 1 1 NO
148 B A A SBT_TAPE 19-MAR-10 1 1 NO
149 B F A SBT_TAPE 19-MAR-10 1 1 NO
150 B A A SBT_TAPE 19-MAR-10 1 1 NO
151 B A A SBT_TAPE 19-MAR-10 1 1 NO
152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
154 B A A SBT_TAPE 19-MAR-10 1 1 NO
155 B F A SBT_TAPE 19-MAR-10 1 1 NO
161 B A A SBT_TAPE 21-MAR-10 1 1 NO
162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
164 B A A SBT_TAPE 21-MAR-10 1 1 NO
165 B F A SBT_TAPE 21-MAR-10 1 1 NO
171 B A A SBT_TAPE 22-MAR-10 1 1 NO
172 B F A SBT_TAPE 22-MAR-10 1 1 NO
173 B A A SBT_TAPE 22-MAR-10 1 1 NO
174 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
Backup Set 8 07-MAR-10 Backup Piece 19 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_5_1
Backup Set 8 07-MAR-10 Backup Piece 18 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_4_1
Backup Set 8 07-MAR-10 Backup Piece 17 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_3_1
Backup Set 8 07-MAR-10 Backup Piece 16 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_2_1
Backup Set 8 07-MAR-10 Backup Piece 15 07-MAR-10 CCBPROD_inc_20100307_713034799_07l8031f_1_1
Backup Set 7 07-MAR-10 Backup Piece 14 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_5_1
Backup Set 7 07-MAR-10 Backup Piece 13 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_4_1
Backup Set 7 07-MAR-10 Backup Piece 12 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_3_1
Backup Set 7 07-MAR-10 Backup Piece 11 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_2_1
Backup Set 7 07-MAR-10 Backup Piece 10 07-MAR-10 CCBPROD_inc_20100307_713034799_08l8031f_1_1
Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
Edited by: user12019850 on 22-Mar-2010 10:53 AMAnother database with the same configuration and same plan seems fine:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
797 B A A SBT_TAPE 20-FEB-10 1 1 NO
803 B A A SBT_TAPE 20-FEB-10 1 1 NO
804 B F A SBT_TAPE 20-FEB-10 1 1 NO
805 B A A SBT_TAPE 20-FEB-10 1 1 NO
806 B F A SBT_TAPE 20-FEB-10 1 1 NO
807 B A A SBT_TAPE 20-FEB-10 1 1 NO
808 B F A SBT_TAPE 20-FEB-10 1 1 NO
809 B A A SBT_TAPE 21-FEB-10 1 1 NO
810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
812 B A A SBT_TAPE 21-FEB-10 1 1 NO
813 B F A SBT_TAPE 21-FEB-10 1 1 NO
818 B A A SBT_TAPE 21-FEB-10 1 1 NO
819 B F A SBT_TAPE 21-FEB-10 1 1 NO
820 B A A SBT_TAPE 21-FEB-10 1 1 NO
821 B F A SBT_TAPE 21-FEB-10 1 1 NO
822 B A A SBT_TAPE 21-FEB-10 1 1 NO
823 B F A SBT_TAPE 21-FEB-10 1 1 NO
824 B A A SBT_TAPE 22-FEB-10 1 1 NO
825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
827 B A A SBT_TAPE 22-FEB-10 1 1 NO
828 B F A SBT_TAPE 22-FEB-10 1 1 NO
833 B A A SBT_TAPE 22-FEB-10 1 1 NO
834 B F A SBT_TAPE 22-FEB-10 1 1 NO
835 B A A SBT_TAPE 22-FEB-10 1 1 NO
836 B F A SBT_TAPE 22-FEB-10 1 1 NO
837 B A A SBT_TAPE 22-FEB-10 1 1 NO
838 B F A SBT_TAPE 22-FEB-10 1 1 NO
839 B A A SBT_TAPE 22-FEB-10 1 1 NO
840 B F A SBT_TAPE 22-FEB-10 1 1 NO
841 B A A SBT_TAPE 23-FEB-10 1 1 NO
842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
844 B A A SBT_TAPE 23-FEB-10 1 1 NO
845 B F A SBT_TAPE 23-FEB-10 1 1 NO
850 B A A SBT_TAPE 23-FEB-10 1 1 NO
851 B F A SBT_TAPE 23-FEB-10 1 1 NO
852 B A A SBT_TAPE 23-FEB-10 1 1 NO
853 B F A SBT_TAPE 23-FEB-10 1 1 NO
854 B A A SBT_TAPE 23-FEB-10 1 1 NO
855 B F A SBT_TAPE 23-FEB-10 1 1 NO
856 B A A SBT_TAPE 24-FEB-10 1 1 NO
857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
859 B A A SBT_TAPE 24-FEB-10 1 1 NO
860 B F A SBT_TAPE 24-FEB-10 1 1 NO
865 B A A SBT_TAPE 24-FEB-10 1 1 NO
866 B F A SBT_TAPE 24-FEB-10 1 1 NO
867 B A A SBT_TAPE 24-FEB-10 1 1 NO
868 B F A SBT_TAPE 24-FEB-10 1 1 NO
869 B A A SBT_TAPE 24-FEB-10 1 1 NO
870 B F A SBT_TAPE 24-FEB-10 1 1 NO
871 B A A SBT_TAPE 24-FEB-10 1 1 NO
872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
874 B A A SBT_TAPE 24-FEB-10 1 1 NO
875 B F A SBT_TAPE 24-FEB-10 1 1 NO
880 B A A SBT_TAPE 24-FEB-10 1 1 NO
881 B F A SBT_TAPE 24-FEB-10 1 1 NO
882 B A A SBT_TAPE 25-FEB-10 1 1 NO
883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
885 B A A SBT_TAPE 25-FEB-10 1 1 NO
886 B F A SBT_TAPE 25-FEB-10 1 1 NO
891 B A A SBT_TAPE 25-FEB-10 1 1 NO
892 B F A SBT_TAPE 25-FEB-10 1 1 NO
893 B A A SBT_TAPE 25-FEB-10 1 1 NO
894 B F A SBT_TAPE 25-FEB-10 1 1 NO
895 B A A SBT_TAPE 25-FEB-10 1 1 NO
896 B F A SBT_TAPE 25-FEB-10 1 1 NO
897 B A A SBT_TAPE 25-FEB-10 1 1 NO
898 B F A SBT_TAPE 25-FEB-10 1 1 NO
899 B A A SBT_TAPE 25-FEB-10 1 1 NO
900 B F A SBT_TAPE 25-FEB-10 1 1 NO
901 B A A SBT_TAPE 25-FEB-10 1 1 NO
902 B F A SBT_TAPE 25-FEB-10 1 1 NO
903 B A A SBT_TAPE 26-FEB-10 1 1 NO
904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
906 B A A SBT_TAPE 26-FEB-10 1 1 NO
907 B F A SBT_TAPE 26-FEB-10 1 1 NO
912 B A A SBT_TAPE 26-FEB-10 1 1 NO
913 B F A SBT_TAPE 26-FEB-10 1 1 NO
914 B A A SBT_TAPE 26-FEB-10 1 1 NO
915 B F A SBT_TAPE 26-FEB-10 1 1 NO
916 B A A SBT_TAPE 26-FEB-10 1 1 NO
917 B F A SBT_TAPE 26-FEB-10 1 1 NO
918 B A A SBT_TAPE 27-FEB-10 1 1 NO
919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
921 B A A SBT_TAPE 27-FEB-10 1 1 NO
922 B F A SBT_TAPE 27-FEB-10 1 1 NO
927 B A A SBT_TAPE 27-FEB-10 1 1 NO
928 B F A SBT_TAPE 27-FEB-10 1 1 NO
929 B A A SBT_TAPE 27-FEB-10 1 1 NO
930 B F A SBT_TAPE 27-FEB-10 1 1 NO
931 B A A SBT_TAPE 27-FEB-10 1 1 NO
932 B F A SBT_TAPE 27-FEB-10 1 1 NO
933 B A A SBT_TAPE 28-FEB-10 1 1 NO
934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
936 B A A SBT_TAPE 28-FEB-10 1 1 NO
937 B F A SBT_TAPE 28-FEB-10 1 1 NO
942 B A A SBT_TAPE 28-FEB-10 1 1 NO
943 B F A SBT_TAPE 28-FEB-10 1 1 NO
944 B A A SBT_TAPE 28-FEB-10 1 1 NO
945 B F A SBT_TAPE 28-FEB-10 1 1 NO
946 B A A SBT_TAPE 28-FEB-10 1 1 NO
947 B F A SBT_TAPE 28-FEB-10 1 1 NO
948 B A A SBT_TAPE 01-MAR-10 1 1 NO
949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
951 B A A SBT_TAPE 01-MAR-10 1 1 NO
952 B F A SBT_TAPE 01-MAR-10 1 1 NO
957 B A A SBT_TAPE 01-MAR-10 1 1 NO
958 B F A SBT_TAPE 01-MAR-10 1 1 NO
959 B A A SBT_TAPE 01-MAR-10 1 1 NO
960 B F A SBT_TAPE 01-MAR-10 1 1 NO
961 B A A SBT_TAPE 01-MAR-10 1 1 NO
962 B F A SBT_TAPE 01-MAR-10 1 1 NO
963 B A A SBT_TAPE 02-MAR-10 1 1 NO
964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
966 B A A SBT_TAPE 02-MAR-10 1 1 NO
967 B F A SBT_TAPE 02-MAR-10 1 1 NO
970 B A A SBT_TAPE 02-MAR-10 1 1 NO
971 B F A SBT_TAPE 02-MAR-10 1 1 NO
972 B A A SBT_TAPE 02-MAR-10 1 1 NO
973 B F A SBT_TAPE 02-MAR-10 1 1 NO
974 B A A SBT_TAPE 02-MAR-10 1 1 NO
975 B F A SBT_TAPE 02-MAR-10 1 1 NO
976 B A A SBT_TAPE 03-MAR-10 1 1 NO
977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
979 B A A SBT_TAPE 03-MAR-10 1 1 NO
980 B F A SBT_TAPE 03-MAR-10 1 1 NO
983 B A A SBT_TAPE 03-MAR-10 1 1 NO
984 B F A SBT_TAPE 03-MAR-10 1 1 NO
985 B A A SBT_TAPE 03-MAR-10 1 1 NO
986 B F A SBT_TAPE 03-MAR-10 1 1 NO
987 B A A SBT_TAPE 03-MAR-10 1 1 NO
988 B F A SBT_TAPE 03-MAR-10 1 1 NO
989 B A A SBT_TAPE 04-MAR-10 1 1 NO
990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
992 B A A SBT_TAPE 04-MAR-10 1 1 NO
993 B F A SBT_TAPE 04-MAR-10 1 1 NO
996 B A A SBT_TAPE 04-MAR-10 1 1 NO
997 B F A SBT_TAPE 04-MAR-10 1 1 NO
998 B A A SBT_TAPE 04-MAR-10 1 1 NO
999 B F A SBT_TAPE 04-MAR-10 1 1 NO
1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 30 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
Backup Set 804 20-FEB-10
Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
Edited by: user12019850 on 22-Mar-2010 11:03 AM -
RMAN-08591: WARNING: invalid archived log deletion policy
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,kkrm333 wrote:
Hi,
My database is 11.2.0.1 running on OEL 5.
We have stndby database running on other server, i have configured rman like this
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
But while running db backup, getting the error
RMAN-08591: WARNING: invalid archived log deletion policy.
RMAN retention policy is set to redundancy 1.
The archive files are deleting even though they are not applied on standby.
Thanks,
bcm@bcm-laptop:~$ oerr rman 8591
8591, 3, "WARNING: invalid archived log deletion policy"
// *Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived
// log deletion policy was APPLIED but there was no mandatory
// archived log destinations.
// *Action: One of the following:
// 1) Change archived log deletion policy using CONFIGURE command
// 2) Make one or more of standby destination as MANDATORY. -
Archivelogs deleted in RAC ASM Production for standby
Hi,
DB: 10.2.0.4
OS: AIX 5.3 L
This is 2 node RAC ASM database with single standby on ASM.
I set the retention policy to 2 days for my Live database.While running the TAPE backup script, the archivelogs were deleted .The deleted archivelogs are generated just before /while the TAPE backup.Backup script has not considered the retention policy for Primary.All archivelogs , except generated after backup ,were deleted .
Now my standby is waiting for deleted archivelogs.
How do i can make sync of my standby with Primary ?.
Please understand my position and request you to help me on this.
Regards,
Sunand
Edited by: sunand on Jan 22, 2011 3:15 AMHi Jean & Abhi,
Thanks you very much for your reply.
I came out the problem with following taking the backup of incremental from standby SCN value.
Actually i did not have backup of deleted archivelog .Now my standby database is in sync with primary and working fine.
About recovering of deleted archivelog from backup piece, If i run below script , whether it will recover the specified archivelogs to our archivelog destination or will recover to database ?.I never done this before.Could you explain me ,please.
run
allocate channel t1 type sbt.....;
restore archivelog from sequence X until sequence Y thread 1;
Also, my database is on ASM. Once we recover the archivelogs,how do i can move to standby?.I mean , moving them from ASM to file system and registering to standby database .
Thank you very much,
Regards,
Sunand -
Retention policy for archivelogs in the flash recovery area
I am using the flash recovery area for all my backup files (archive logs, data and control files). I want to use the redundancy retention policy because it is easy to calculate the space requirement. However, I am not clear how the retention policy applies to archive logs.
Say I set the retention policy to be "keeping 3 backups". How does it affect the archive logs? Will archive logs in the flash recovery area be deleted automatically or I need to do it manually. If they are deleted automatically just like dataset files, what is the "retention policy" for them? I do not have a tape device so all archive logs are going to be stay in disk.
Thanks.I am using the flash recovery area for all my backup
files (archive logs, data and control files). I want
to use the redundancy retention policy because it is
easy to calculate the space requirement. However, I
am not clear how the retention policy applies to
archive logs.
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> list backup
2> ;
RMAN>AS documentation says
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
consider it here that i am getting archived before any taking backup i.e backup database in order to make
archive older then the oldest datafile.
SQL> show parameter control_file_record_keep_time
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL> create table a1 as select * from all_objects
2 /
Table created.
SQL> create table a2 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
03/17/2008 03:44 PM <DIR> .
03/17/2008 03:44 PM <DIR> ..
03/17/2008 03:44 PM 9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
1 File(s) 9,750,528 bytes
2 Dir(s) 62,714,875,904 bytes free
Now i take backup
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Archive Log 402 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
be useful for recovery process.
now back to pavillion
RMAN> delete obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Archive Log 402 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
Deleted 1 objects
RMAN> delete backup
2> ;
using channel ORA_DISK_1
RMAN> list backup
2> ;
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 03:59 PM <DIR> .
03/17/2008 03:59 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
then the oldest datafile backup.
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
SQL> create table a3 as select * from all_objects
2 /
Table created.
SQL> create table a4 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 04:09 PM <DIR> .
03/17/2008 04:09 PM <DIR> ..
03/17/2008 04:09 PM 9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
1 File(s) 9,751,552 bytes
2 Dir(s) 62,563,205,120 bytes free
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
is not older then oldest datafile backup.
But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
retetnion policy from the period of 2.
RMAN> backup database
2> ;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 240 17-MAR-08
Backup Piece 231 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
KP
Backup Set 241 17-MAR-08
Backup Piece 232 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
KP
Archive Log 403 17-MAR-08 C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram -
ARCHIVELOG deletion on primary and physical standby
Hi,
We have a primary and a physical standby database running Oracle 11.1.0.7.0 software on Red Hat Enterprise Linux x-64 bit OS. I will be using backup software
to only backup the primary database and do not have the backup software for the standby server and database.
We need to backup archived redo log files from primary site and delete the ones which are more than one month old. These archived redo log files will be applied from primary to standby database as and when the log switch occurs.
Can anybody please let me know if the following steps can be used:
Details are:
primary database name - sun (machine name is node1)
standby database name - drsun (machine name is node2)
On node1 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
#!/bin/sh
ORACLE_SID=sun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@sun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_sun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
On node2 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
#!/bin/sh
ORACLE_SID=drsun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@drsun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_drsun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
RegardsHello;
Welcome to the forums. ( By physical Standby I assume Data Guard )
The short answer is it should work. I noticed this :
/cleanup_rman_arch_drsun.rcv
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;I see no reason for the "alter system switch logfile". In fact you can do something very simple on the Standby :
$ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalog> << EOF
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-1';
exit
EOFThis assumes you have doing a backup with RMAN on the Primary ( tested on 11.2.0.2 ) and have this set on the Primary :
CONFIGURE ARCHIVELOG DELETEION POLICY TO APPLIED ON ALL STANDBY;
If you are deleting Archive without using RMAN first then yes something like this ( But I would try to use RMAN and not delete using another method )
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`
Best Regards
mseberg
h2. Another Standby Option
/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
SET echo off
SET feedback off
SET term off
SET pagesize 0
SET linesize 200
SET newpage 0
SET space 0
col name format a120
spool /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
select 'rm '||NAME from v$archived_log
where REGISTRAR='RFS'
and APPLIED='YES'
and DELETED='NO'
and COMPLETION_TIME < (SYSDATE-10);
SPOOL OFFMain shell script
/u01/app/oracle/dba_tool/bin/removestandbyarch.sh
#!/bin/bash
if [ "$1" ]
then DBNAME=$1
else
echo "basename $0 : Syntax error : use . removestandbyarch <DBNAME> "
exit 1
fi
# Set the Environmental variable for input instance ( ORACLE_SID, ORACLE_HOME path etc )
. /u01/app/oracle/dba_tool/env/${DBNAME}.env
$ORACLE_HOME/bin/sqlplus /nolog <<EOF
connect / as sysdba
-- spool /u01/app/oracle/dba_tool/bin/rm_arch_${ORACLE_SID}.sh
@/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
SPOOL OFF
EOF
echo `date`
# Now run the generated script
echo "Setting permissions and running script"
chmod 740 /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
. /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
# Use RMAN to update V$ARCHIVED_LOG.DELETED
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`Edited by: mseberg on Apr 30, 2012 8:40 AM -
Error occurred while retrieving policy for this computer (0x8009310b)
Hey I was wondering if someone could help me out. I applied the CU3 to SCCM SP1 CU2 and since then I'm having issues with OSD I keep getting the error..
Error occurred while retrieving policy for this computer (0x8009310b)
here is the log files..
Retrieving Policy Assignments: TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {4bf8faa2-5d00-4a90-b9e5-383b0871efb0}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {cc26aff9-ab59-4984-a3ac-f008380f048f}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {f08e9723-d51a-416d-82ff-d2f1d6fcfc58}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {50feec00-f6cf-4805-97ab-5a228fdd873a}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {0acbe4de-ab99-472b-8d7a-de75bc10e6d1}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {2ccc1bec-7f9c-48bd-b94f-262ffa9711af}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {8ffdf237-4b86-41e7-ad68-a80ca1ddbe99}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {69456004-d3af-4f66-b425-8bb09d98a6a1}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {2fd8694e-bec7-41a6-ab25-fb8f0a275489}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {f032b175-e84a-4a4b-b2e5-3e804b66a528}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {e37f6b90-a1ff-4ce1-849d-936c8be4fc2b}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {c54e27c2-233b-454d-a277-8514b5e0ae8d}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {926ae109-a321-4826-90a9-577f565225a3}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {a9516dcf-f248-46af-b051-0367a0134e65}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {509b6c13-4fd3-443e-98c7-4703a9fb338c}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {050b9a4e-0776-439d-8d7c-e54cca9091f3}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {5b8d7b35-86f7-42b6-945f-faa62701421c}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {1fd389bc-2825-4e6a-a8fe-c3e50150818b}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {76aa3bc7-1c40-4415-b533-8b20c914afe0}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {a5eaed00-afb8-48ab-b030-e7809f0dd432}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {10054616-84aa-4f21-8b74-f6ae6142b794}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {a16430b4-b87c-4450-862d-3ee632df4db9}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {211060af-cae0-41a2-847c-ce08245d5900}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {ba947774-81a4-4ebf-a86d-1f05a7c5bc9a}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {2ad8b520-3701-4a07-ba92-09c25c9ee970}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {8ff1fc52-f1aa-44de-ab31-7fc3f7ed7266}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {279361f7-9750-473a-9ca9-f82b5b19f047}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {a64b913a-2318-4f57-b223-6af3b82bac3a}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {6a762475-f76c-4b91-bb00-3550fec86c4c}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {09c0bb21-01c0-41eb-a39e-5d8274ed2b99}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {730b6fe3-103a-4f65-866a-36eab232610e}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {d500add8-54c9-4c9f-a08f-9a84715d5ea8}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {cd900a7b-8469-4b35-93ba-d0d15c37b689}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment B0120000-B0100004-3B5BFFE2. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment SRC10000. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {947a63da-65e5-41bc-8a3c-1ee201618fbd}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment {SMS000US}. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment B0120059-B01000AD-6F6BCC28. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment DEP-B0120059-B0100003-6F6BCC28. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment DEP-B0120059-B0100005-6F6BCC28. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Processing Policy Assignment DEP-B0120059-B0100022-6F6BCC28. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Successfully read 41 policy assignments. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Downloading policy body B0120059-B01000AD-6F6BCC28. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Preparing Policy Body Request. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Setting transport. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Setting policy location = http://<mp>/SMS_MP/.sms_pol?B0120059-B01000AD-6F6BCC28.1_00. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Executing Policy Body Request. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
CLibSMSMessageWinHttpTransport::Send: URL: MZINFCCMPRD01.brownell.local:80 GET /SMS_MP/.sms_pol?B0120059-B01000AD-6F6BCC28.1_00 TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Error. Status code 404 returned TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Found a secure policy. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Trying to decode policy. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
CryptDecryptMessage ( &DecryptParams, pbEncrypted, nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=8009310b (e:\qfe\nts\sms\framework\smscrypt\windes.cpp,339) TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Decoding in non ssl mode failed. Checking if decoding was really needed. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Failed to verify a properly formed XML. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
oPolicy.RequestPolicy((GetPolicyFlags() & POLICY_SECURE) != 0, (GetPolicyFlags() & POLICY_COMPRESS) != 0), HRESULT=8009310b (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,2067) TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Failed to download policy B0120059-B01000AD-6F6BCC28 (Code 0x8009310b). TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
(*iTSPolicyAssignment)->GetObjects(pszClassName, aTSPolicyObjectArray ), HRESULT=8009310b (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,1224) TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
m_pPolicyManager->GetObjects( TS::Policy::TaskSequence::GetClassNameW(), TS::Policy::TaskSequence::GetPolicyCategory(), TS::Policy::TSPolicyAssignment::POLICY_TS_FOR_CD_AND_PXE, aTSPolicyObjectArray ), HRESULT=8009310b (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1205) TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Exiting TSMediaWizardControl::GetPolicy. TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=8009310b (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303) TSPxe 2/18/2014 1:48:19 PM 836 (0x0344)
Setting wizard error: An error occurred while retrieving policy for this computer (0x8009310B). For more information, contact your system administrator or helpdesk operator. TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
WelcomePage::OnWizardNext() TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Skipping Confirmation Page. TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Skipping Task Sequence Selection Page. TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Skipping Variables Selection Page. TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Skipping Resolve Progress Page. TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Activating Finish Page. TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Initializing the countdown timer. TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Loading bitmap TSPxe 2/18/2014 1:48:19 PM 728 (0x02D8)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 2/18/2014 1:48:23 PM 780 (0x030C)
The command completed successfully. TSBootShell 2/18/2014 1:48:23 PM 780 (0x030C)
Successfully launched command shell. TSBootShell 2/18/2014 1:48:23 PM 780 (0x030C)
What I've done for troubleshooting tips so far.
Deleted the Machines I'm trying to image
Re-created all the Task sequences
Disabled PXE, rebooted the machine and after 45minutes enabled PXE again.
I've checked the certificates its all unblocked.
is there anything?Hopefully this other thread helps you:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/631086ac-3b59-4437-a6af-0f1a834edcc2/problems-with-pxe-booted-pe-environment?forum=configmgrosd
The marked answer in this thread is saying check the certificates? Would this be under Administration ->Security-> Certificates? I haven't tried re-installing the MP yet I'll give it a shot -
Hi!
I Have one AD Security group for each shared printer, I have one GPP that map the printer if the user is in the security group that belong to the printer. And one GPP to delete the printer if the user is NOT member of the security group. The security group
is also applied in “Security” tab on the printsrv with PRINT rights and “everyone” is removed. This works 100 % on Windows 7 clients and Windows 2003 Terminal Servers. But on Windows 2008 R2 RDS this dont work.The Delete Policy will not delete the shared
printer. No warning in any logs, and the gpresult shows that the gpo setting applyed sucessfully. The only way I can make the Delete policy work is if i give the user print rights on the printer on the printsrv. Looks like for the policy to work on 2008
R2 the user must have print rights on the printer object on the printserver. The GPP Delete Policy will not delete printers that have status : access denied. Anyone else had this problem?Hi,
Based on your description, it seems that we need to give users appropriate permissions, for the error
Access is denied is more or less related to permissions.
However, we can avoid deploying the GPP printer delete policy. As far as I know, we can use Item-Lvel Targeting of GPP to push the shared printers
to the targeted users or groups.
Regarding ILT, the following articles can be referred to for more information.
Preference Item-Level Targeting
http://technet.microsoft.com/en-us/library/cc733022.aspx
Security Group Targeting
http://technet.microsoft.com/en-us/library/cc772471.aspx
Best regards,
Frank Shen -
Sample of weblogic.policy for WLS6.0
Dear all,
I had installed WLS6.0 on Solaris 2.6 and try to turn on
java security manager with this option
-Djava.security.policy==/usr/home/bea/wlserver6.0/lib/
weblogic.policy -Djava.security.manager
This make me unable to boot WLS. Here is contents of my weblogic.policy
grant {
// Permission "enableSubstitution" needed to run the WebLogic console
permission java.io.SerializablePermission "enableSubstitution";
// Permission "modifyThreadGroup" required to run the WebLogic Server
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.lang.RuntimePermission "setContextClassLoader";
// Permission "setIO" needed to start a server from the WebLogic console
permission java.lang.RuntimePermission "setIO";
// Permission "getClassLoader" needed for many EJB clients
permission java.lang.RuntimePermission "getClassLoader";
permission java.lang.RuntimePermission "stopThread";
permission java.net.SocketPermission "localhost:1024-", "listen";
permission java.util.PropertyPermission "*", "read,write";
permission java.io.FilePermission "${/}usr${/}home${/}bea${/}wlserver6.0${/}-",
"read,write,delete,execute";
And here is the error occurs
java.security.AccessControlException: access denied (java.io.FilePermission /usr/home/bea/wlserver6.0
read)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:272)
at java.security.AccessController.checkPermission(AccessController.java:399)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.lang.SecurityManager.checkRead(SecurityManager.java:890)
at java.io.File.exists(File.java:535)
at weblogic.utils.classloaders.ClasspathClassFinder.<init>(ClasspathClassFinder.java:61)
at weblogic.Home.getFileSource(Home.java:64)
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:82)
at weblogic.Home.getPath(Home.java:90)
at weblogic.security.internal.ServerAuthenticate.main(ServerAuthenticate.java:76)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:167)
at weblogic.Server.main(Server.java:35)
Could anyone give me what goes wrong. If you have a working version of weblogic.policy,
please share with me.
Regards,
KhemchartHere's a snippet from upcoming release notes about the Java
security manager and the example weblogic.policy file.
Using the Java Security Manager with WebLogic Server
When you run WebLogic Server under Java 2 (JDK 1.2 or 1.3), WebLogic
Server can use the Java Security Manager in Java 2 to provide
additional access control for WebLogic Server resources. The Java
Virtual Machine (JVM) has security mechanisms built into it which can
be managed via a security policy file. The Java Security Manager can
enforce a set of permissions granted to CodeSource or SignedBy
classes. The permissions allow certain classes running in that
instance of the JVM to do or not do certain runtime operations. In
many cases, where the threat model does not include malicious code
being run on the JVM, the Java Security Manager is unnecessary. In
cases such as when an Application Service Provider uses WebLogic
Server and unknown classes are being run, the Java Security Manager is
necessary. To use the Java Security Manager with WebLogic Server,
specify the -Djava.security.manager property when starting WebLogic
Server.
Note: In past releases of WebLogic Server, the Java Security Manager
was enabled by using the -Dweblogic.security.manager property when
starting WebLogic Server. Please note the change in the property for
WebLogic Server version 6.0 and greater.
The Java Security Manager uses a security policy file that defines
permissions. The full pathname of security policy is specified in the
-Djava.security.policy property when starting WebLogic Server. If you
enable the Java Security Manager but do not specify a security policy
file, the Java Security Manager uses the default security policies
defined in the java.security and java.policy files in the
$JAVA_HOME/lib/security directory.
WebLogic Server includes an example security policy file named
weblogic.policy. This file contains a set of default permissions.
You need to make the following edits to the file in order to use the
file with your WebLogic Server deployment.
1. Edit the following lines in the weblogic.policy file, replacing the
specified location with the location of your WebLogic Server
installation:
grant codebase "file://BEA/-"{
permission java.io.FilePermission "D:${/}BEA${/}=", ...
Note: This change assumes your installation directory structure is the
same as the one described in the BEA Home Directory topic in the BEA
WebLogic Server Installation Guide.
2. If you want to run the Administration Console, add the following
grant block and permissions to the weblogic.policy file:
grant {
permission java.io.FilePermission
"D:{/}BEA${/}wlserver600${/}weblogic${/}management${/}console${/}-",
"read";
permission java.io.FilePermission
"D:{/}BEA${/}wlserver600${/}config${/}mydomain${/}applications${/}.wl_te\
mp_do_not_delete${/}weblogic${/}management${/}console${/}-", "read";
permission java.util.PropertyPermission "user.*", "read";
3. If you have extra directories in your CLASSPATH or if you are
deploying applications in extra directories, you need to add specific
permissions for those directories to your weblogic.policy file.
BEA also recommends taking the following precautions:
? Make a backup copy of the weblogic.policy file and put the backup
copy in a secure location.
? Set the permissions on the weblogic.policy file such that the
adminstrator of the WebLogic Server deployment has write and read
privileges and no other users
To use the Java Security Manager and the weblogic.policy file with
your WebLogic Server deployment, use the following properties when
starting WebLogic Server:
$java... -Djava.security.manager \
-Djava.security.policy==D:/BEA/wlserver600/lib/weblogic.policy
For more information about the Java Security Manager, see the Javadoc
shipped with Java 2.
The RecordingSecurityManager utility can be used to detect permission
problems that occur when starting and running WebLogic Server. The
utility outputs permissions that can be added to your security policy
file to resolve the permission problems that the utility finds. The
RecordingSecurityManager is available at the BEA Developer's Center. -
Could not deploy policy for resource: type= url , application=MySecurex,
Hi
My situation :
I have 2 managed weblogic portal 10.3.0 managed servers in a cluster and 1 admin server. All are running as a service.
Deployments of new versions of applications are submitted by an automated script.
The steps in the script are :
- stop the services of the managed servers
- undeploy the previous version by using ant task
<target name="undeploy_old" description="undeploy old application" depends="downloadFiles">
<java classname="weblogic.Deployer" output="./temp/${buildProject}_${deployEnv}/${buildVersion}/undeploy.txt" fork="yes">
<arg value="-adminurl" /> <arg value="${adminurl}" />
<arg value="-username" /> <arg value="${weblogic_user}" />
<arg value="-password" /> <arg value="${weblogic_pwd}" />
<arg value="-undeploy" />
<arg value="-name" />
<arg value="${buildProject}" />
<arg value="-verbose" />
<classpath refid="project.class.path"/>
</java> - deploy the new version by using ant task
<java classname="weblogic.Deployer"
output="./temp/${buildProject}_${deployEnv}/${buildVersion}/deploy.txt"
fork="yes"
maxmemory="512m"
inputstring="" >
<arg value="-adminurl" /> <arg value="${adminurl}" />
<arg value="-username" /> <arg value="${weblogic_user}" />
<arg value="-password" /> <arg value="${weblogic_pwd}" />
<arg value="-stage" />
<arg value="-verbose" />
<arg value="-upload" />
<arg value="-deploy" />
<arg value="-name" /> <arg value="${buildProject}" />
<arg value="-source" /> <arg value="./temp/${buildProject}_${deployEnv}/${buildVersion}/${buildProject}.ear" />
<arg value="-targets" /> <arg value="${deploytargetinstances}" />
<classpath refid="project.class.path"/>
</java>- start the services of the managed servers
Problem:
When the managed servers are restarting and the new version is going to prepared status, an error occurs for the new version of the application :
####<27-dec-2011 13.42 u. CET> <Info> <Deployer> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758076> <BEA-149059> <Module MySecurexEarAdmin of application MySecurex is transitioning from STATE_NEW to STATE_PREPARED on server s40beaportacc1p9106.>
####<27-dec-2011 13.42 u. CET> <Error> <Security> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-090064> <The DeployableAuthorizer "myrealm_weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl" returned an error: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource.>
####<27-dec-2011 13.42 u. CET> <Error> <HTTP> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-101199> <Could not deploy policy for resource: type=<url>, application=MySecurex, contextPath=/MySecurexEarAdmin, uri=/campaigns/emails/*.
weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
at com.bea.common.security.internal.service.PolicyDeploymentServiceImpl$DeploymentHandlerImpl.deployPolicy(PolicyDeploymentServiceImpl.java:173)
at weblogic.security.service.WLSPolicyDeploymentServiceWrapper$DeploymentHandlerImpl.deployPolicy(Unknown Source)
at weblogic.security.service.AuthorizationManager$HandlerAdaptor.deployPolicy(Unknown Source)
at weblogic.security.service.AuthorizationManager.deployPolicy(Unknown Source)
at weblogic.servlet.security.internal.ResourceConstraint.deploy(ResourceConstraint.java:108)
at weblogic.servlet.security.internal.WebAppSecurityWLS.deployPolicies(WebAppSecurityWLS.java:253)
at weblogic.servlet.security.internal.WebAppSecurity.registerSecurityConstraints(WebAppSecurity.java:140)
at weblogic.servlet.internal.WebAppServletContext.prepareFromDescriptors(WebAppServletContext.java:1189)
at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1121)
at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:449)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:424)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:119)
at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:162)
at weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl.deployPolicy(XACMLAuthorizationProviderImpl.java:281)
weblogic.management.utils.CreateException:
at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:241)
at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:112)
com.bea.security.xacml.PolicyStoreException: <openjpa-1.1.0-r422266:657916 fatal store error> kodo.jdo.FatalDataStoreException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:684)
at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:576)
at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:222)
at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
<openjpa-1.1.0-r422266:657916 nonfatal store error> kodo.jdo.ObjectNotFoundException: The instance "netscape.ldap.LDAPException: error result (32)" does not exist in the data store.
FailedObject: netscape.ldap.LDAPException: error result (32)
at com.bea.common.ldap.LDAPStoreManager.flush(LDAPStoreManager.java:370)
at org.apache.openjpa.abstractstore.AbstractStoreManager.flush(AbstractStoreManager.java:277)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
at org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:554)
at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2007)
....>
My workaround:
Delete the <domain>\servers\s40beaportacc1p9106\data\ldap directory on the managed servers and restart
Does anyone knows what causes the error and how to solve it?
The goal is to be able to deploy our application by automation.You must use not the original bean that you coded. You must use the bean generated by axis-wsdl2java.
The bean generated by axis-wsdl2java is:
- in the first beanMapping: MSPCSService.SMSMO
- in the second beanMapping: MSPCSService.SMSMOResponse
As you can see, the bean the axis-wsdl2java will generate is build with the namespace + "." + qname. If you use an domain like java.sun.com in namespace, then the package name you will use is inverted (in the sample, com.sun.java). Look at the code generated.
You client must use this beans, not the original coded by you.
This must work, worked for me :)
Maybe you are looking for
-
Error while saving service order?
Dear SAPIENTS, While saving service order system is throwing error in commitment check message number CO634 can anybody tell where i need to check to resolve this problem? Regards, Kaushal Rai
-
Wifi doens't connect after upgrade to 10.7.5
I upgraded my imac to 10.7.5, and some how my wifi did not connect to the internet from yesterday. I tried network diagnostics for couple times, and there is one time the internet was on when the small window popup with the msn "some thing abt the ne
-
Keynote Sync problems with music Playback
Dear Keynote Experts, after long trying I can´t fix this problem. I want to synchronize Pictures with 4s duration. This shall run in sync with a music playback which is 120 bpm. So it would be in Sync with the progression of the beats. At least the p
-
How to permanently disable Windows Defender?
Windows Defender won't stay disabled. I searched through the threads and saw several others have had this problem but the issue has apparently never been resolved. I removed Windows Defender from startup using MSCONFIG, disabled it from the GUI tha
-
trying to update a plugin, I do, then reboot but when I check the plugin checker says I need to update it.