Not set configure retention policy to recovery window of 7 days

HI all,
if parameter "" configure retention policy to recovery window of 7 days "" is not set
then i am taking weekly and inreamental cumulative backup any effect of backup
i think in this case delete obsolete is not working.
currently parameter set is CONFIGURE RETENTION POLICY TO REDUNDANCY 1;

Similar Messages

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;

Hi Guys
Can you please put some light on the 0 days. what is the meaning on 0 days and how does this work.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS; If I take full backup every night how many backup will it contain and how will it obsolete the backup.
RMan 9i R2
Soalris 5.9
I understand the concept if recover window is 1 or more days but confuse with 0 days.
Thank you in advance.

RECOVERY WINDOW OF 0 DAYS is effective like REDUNDANCY 1.
RMAN> configure retention policy to recovery window of 0 days;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=15 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 0 days
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           10     09-SEP-07
Backup Piece       10     09-SEP-07          E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
RMAN> delete backup;
using channel ORA_DISK_1
List of Backup Pieces
BP Key BS Key Pc# Cp# Status      Device Type Piece Name
10      10      1   1   AVAILABLE   DISK        E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1
11      11      1   1   AVAILABLE   DISK        E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0BIRHB2F_1_1 recid=10 stamp=632859727
deleted backup piece
backup piece handle=E:\ORACLE\ORA92\DATABASE\0CIRHB4Q_1_1 recid=11 stamp=632859802
Deleted 2 objects
RMAN> configure retention policy to redundancy 1;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 0 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> backup datafile 4;
Starting backup at 09-SEP-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=E:\ORACLE\ORADATA\WIN9I\DRSYS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-SEP-07
channel ORA_DISK_1: finished piece 1 at 09-SEP-07
piece handle=E:\ORACLE\ORA92\DATABASE\0EIRHB9H_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 09-SEP-07
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           12     09-SEP-07
Backup Piece       12     09-SEP-07          E:\ORACLE\ORA92\DATABASE\0DIRHB90_1_1
RMAN>

Backup with retention policy to recovery window of N days

Hello,
I've issued command to create database incremental backup with configuration:
run
configure retention policy to recovery window of 14 days;
backup incremental level 1 cumulative
tag daily_incr_14_days
database
plus archivelog delete all input;
All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
BR
Patrycjusz.

TenakaKhan wrote:
Mahir,
thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
Yes it is.
Maintaining RMAN Backups and Repository&nbsp;Records
keepOption
backup retention policy
A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
recovery window
A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
Regards
Mahir M. Quluzade

Retention policy to recovery window of 31 days means

HI all,
according to our company policy we need to restore database from last 7year.
backup happen on SBT TAPE.. we freez that tape for next 7 year.
my doubt is we are taking backup using recovery catalog...daily basis we are taking backup using recovery catalog...but i have one doubt while configuring we have configure retention policy of recovery window 31 days..
i m very much confused about this policy ..if we use this policy then can we able to recover database before 7 year or not..
becacuse we are not firing any delete obsulate backup command on recovery catalog.
we are only deleting archivelog by using delete nopromt archive log sysdate-3..
so please suggest does it possible if renrtion policy to recovery window 31 days...i can able to restore this database before 31 days.
Thanks,

Hi there user12009184
If you do not delete old backups through your rman script, then old backups will have to be deleted through your tape backup software. Unless you have endlessly large tapes ;-)
So, yes you could theoretically restore from backups older than your retention window of 31 days.
You should ensure that your control_file_record_keep_time is set to a value of 31 or larger (set it to your retention window period plus 1). Otherwise your control files will now know about your older backups.
If you want to restore a very old backup, than you will need to restore a spfile and a control file first, then restore, then recover your database.
You really, really need to test this. So that you know exactly how to do it and you have it documented.
hope this helped,
Andrew

Setting the retention Policy to recovery window.

We are using Netbackup as a our third party tool for corporate backups and have used brbackup with backint on Windows for many years with great success.We would like to incorporate RMAN incremental backups for our backup strategy. Currently our retention policies through netbackup are:
Backup              Retention
Daily Online        2 weeks.
Weekly Online     4 weeks.
Monthly Online   12 months.
Redologs            4 weeks.
We would like to continue to retain the monthly backup. Other than setting the retention policy window to 365, how could we do this???? We would like to avoid growing a huge control file.
Regards
Scott

Hello Scott,
> We would like to avoid growing a huge control file.
Ok nice approach, but the (RMAN) data in the control file is reused after the value of the init parameter CONTROL_FILE_RECORD_KEEP_TIME. (has nothing todo with the retention policy)
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams029.htm#CHDDBCDB
> Other than setting the retention policy window to 365, how could we do this????
You can use the KEEP clause with the command BACKUP or CHANGE.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta035.htm#i97063
Regards
Stefan

Rman Retention policy to recovery window

Hi,
I have few basic doubts in RMAN backup policy
1 . Is that possible to set Retention policy to recovery window in minutes??
2 . If i set Backup Retention Policy to recovery window to 3 days and i am performing RMAN differential incremental backup for 4 days. Will my backups become obsolete after 3 days even though they are needed for recovery or they won't become obsolete since they are needed for recovery ???
Regards,
007

1) Syntax is .... TO RECOVERY WINDOW OF integer DAYS ... no other time statement.
2) Backups become obsolete when no longer needed to fulfil a retention policy. In a (theoretical) scenario, you perform a level 0 backup and then only incremental backups, the starting level 0 backup must be kept for ever (even if it WOULD be possible to define a recovery window in minutes).
Werner

RMAN-05021 configuring retention policy on standby

Hello all.
Running Oracle 11.2.0.2 on Linux (x64); single-node instance.
We've the following setup:
bvlive (PRIMARY)
bvstby2 (STANDBY)
We currently have a retention policy of 21 days, and backup space on the standby is starting to be an issue.
Initially, I thought I could reconfigure this on the standby - but RMAN won't allow this:
STANDBY:
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 days;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 10/15/2012 10:09:50
RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control fileWhich makes sense when I think about it. I saw this thread retention policy is not configure but get different results:
PRIMARY:
RMAN> configure retention policy to recovery window of 14 days;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> show all;
RMAN configuration parameters for database with db_unique_name BVLIVE are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;STANDBY:
RMAN> SHOW ALL;
RMAN configuration parameters for database with db_unique_name BVSTBY2 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;Which also makes sense; so I'm not convinced the original poster solved his problem. I've seen a few threads about this which involve:
1. shutting down standby
2. configuring retention policy on primary
3. taking a backup controlfile from primary
4. copying it across to the standby
5. restarting standby using the backed-up controlfile
But then this seems to be for RAC, which we're not using.
It occurred to me that I could use the KEEP UNTIL option when taking backups, but ran into; ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes (i.e. I can't use KEEP and store backups in the FRA).
Can anyone please advise on the best way to get the retention period down on the standby, ideally without having to rebuild the standby from scratch?
Thanks,
Ray
Edited by: ray_h on 15-Oct-2012 03:33

Hello all.
@ P. Forstmann: thanks for confirming.
@ S Rao: Yep - this is the link I had in mind. Tried it out and it worked. One thing to note is that I didn't have to rename datafiles - presumably creating the standby controlfile negates the need for this in 11g (indeed, the alert log shows these two lines when you mount):
Set as converted control file due to db_unique_name mismatch
Changing di2dbun from bvlive to bvstby2which put my mind at ease when the rename commands failed, saying the files didn't exist
@ mseberg: Typically, our MOS license ran out just as a useful link shows up.
Thanks everyone.
Ray

Configure Retention Policy?

Dear all,
What is the difference between "configure retention policy to recovery window of 14 days" and "configure retention policy to redundancy 2"?
Best Regards,
Amy

We are backing up our database full backup once a week (on Monday) and 2 times of daily backup.
Is "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS" good enough?
I am very confused about retention policy.
here is our parameters in RMAN
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/db/ba
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.1.0/db_1/db
Please advice.

Control_file_record_time -retention policy to recover window

Hi:
If i have control_file_record_time=7 and retention policy to recover window=3 can i still go back and recover upto the last 5th day provided the backups are available.If i have run delete obsolete at the end of 5th day it will delete obsolete backups from the disk but i have the copies stored on some othere disks ...how does rman deal with obsolete but control file still having backup information.
Are they related in anyway or just the obsolete command is for DBA convinence to delete the obsolete backups and does not play a factor during recovery
Thanks,
Ganesh

Hi there user12009184
If you do not delete old backups through your rman script, then old backups will have to be deleted through your tape backup software. Unless you have endlessly large tapes ;-)
So, yes you could theoretically restore from backups older than your retention window of 31 days.
You should ensure that your control_file_record_keep_time is set to a value of 31 or larger (set it to your retention window period plus 1). Otherwise your control files will now know about your older backups.
If you want to restore a very old backup, than you will need to restore a spfile and a control file first, then restore, then recover your database.
You really, really need to test this. So that you know exactly how to do it and you have it documented.
hope this helped,
Andrew

CONFIGURE RETENTION POLICY TO REDUNDANCY 0

Our database is 11g R2, below is our RMAN script
Presently our retention policy is 1, so 1 backup is retained along with the current backup.
I Just want to have 1 backup, i.e RMAN should take the backup and delete the old bacup.
Will it work if i change the retention policy to 0 ?
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE;
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
RMAN> show all
2> ;
using target database control file instead of recovery catalog
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # defaultEdited by: user10243788 on Apr 24, 2012 1:14 AM

user10243788 wrote:
Our database is 11g R2, below is our RMAN script
Presently our retention policy is 1, so 1 backup is retained along with the current backup.
I Just want to have 1 backup, i.e RMAN should take the backup and delete the old bacup.
Will it work if i change the retention policy to 0 ?You cannot set the retention policy to redundancy 0 because redundancy count must be greater than zero.
>
RUN
ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE;
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
}Just switch the order of operation:
use
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
DELETE NOPROMPT OBSOLETE;
instead of
DELETE NOPROMPT OBSOLETE;
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
You can also exclude the operation SQL "ALTER SYSTEM ARCHIVE LOG CURRENT" because BACKUP ARCHIVELOG ALL implicitly switch logfile before archiving.

ASM and CONFIGURE RETENTION POLICY TO REDUNDANCY 1

I have a 11gR2 database in Linux. ALL the database files (including ARCHIVELOGs) are in ASM. I'm configuing and using RMAN in order to backup the DB & ArchiveLogs.
I have "CONFIGURE RETENTION POLICY TO REDUNDANCY 1" configured.
Please help me understand its meaning and function within ASM.
I thought that based on that configuation that my OBSOLETE ARCHIVELOG files within ASM would be automatically be deleted?
So once I completed my second set of backups, when I executed, "DELETE NOPROMPT OBSOLETE" & "DELETE NOPROMPT EXPIRED ARCHIVELOG ALL", that the first second of ARCHIVELOG backups would be deleted?
...thanks in advance

ASM has nothing to do with retention or deletion. You can find the definition of redundancy in the docs at http://tahiti.oracle.com

I can not set up my officejet 4500 with windows 8

I NEED HELP
I can not set up my officejet 4500 with windows 8
I put disk in but no good

You can get the software from your printer's website:
Start at
HP 4500 officejet
Select your exact model, put in your Operating System...
You are looking for the Product Installation Software -- the Full Feature Software for your OS
Download the package, it may be large..
Then install it... Reboot your computer after the installation.
That may do it!
Good Luck!
Kind Regards,
Dragon-Fur

RMAN backups does not match its retention policy

Hello,
I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
I have clear retention policy and set to 14 days again but does not seem to work.
I would appreciate suggestion(s) regarding the strange issue.
Thanks a lot.
Best Regards

John-MK wrote:
Hello,
I have couple of PROD instances on Windows environment with 11.2.0.3 DB version. RMAN retention policy is set to 14 days but I have noticed that backup is showing longer than that.
For example: LIST BACKUP OF DATABASE whows backups since 13th October. I also checked backup pieces at netapp share and they are present.
DELETE NOPROMPT OBSOLETE do not remove anything as expired backup.
I have clear retention policy and set to 14 days again but does not seem to work.
I would appreciate suggestion(s) regarding the strange issue.
Thanks a lot.
Best Regards
We would need to know what kind of backups and when they were taken. Consider this scenario:
retention policy of 7 days.
Incremental level 0 backup taken on Sundays
Incremental level 1 backups taken Mon through Sat.
Let's say Oct 1 is a Sunday, so we take an inc-0 backup on Oct 1, and again on Oct 8.
Now let's say we are at Oct 10. Our 7 day retention policy dicatates that we be able to recover to any day back to Oct 3.
The only way we can recover to Oct 3 is to begin with that inc-0 backup from Oct 1.
All recovery begins with the last inc-0 backup prior to the point in time to be recovered. In a normal, regularly cycling schedule of backups, you will actually end up with backups 1 day short of being twice as old as your retention period.
Let's take a more extreme example. Same 7-day retention period, but after a single inc-0 backup, you don't take any more backups for 3 months. That one single backup is still needed to enforce your recovery window, and so is not obsolete, despite the fact it is 3 months old and your recovery window is only 7 days.
Also, you mention 'expired'. In terms of oracle backups, 'expired' is not the same as 'obsolete'.
"Obsolete" means 'no longer needed to enforce recovery policy'.
"Expired" is a bit more complex.
when a backup is taken, or an archivelog is written, a record of that is written to the repository. when you do an rman 'crosscheck', those repository records are compared to reality -- to see if the recorded backup file or archivelog file actually exists. Maybe someone used an OS command to delete them. Any file found to have 'gone walkabout' have their repository records marked as 'expired'. An rman 'delete expired' then removes those records from the repository.

Setting a Retention Policy - Is there a way to first query it's effectiveness - Here's the Retention Policy I'd like to set...

Hi All,
I've inherited and Exchange 2010 SP3 UR4 environment that has UM but no Retention Policy has been set. As a result, I have MP3s filling up disk space. Adding to that is that I'm a N00b when it comes to Exchange. I've more or less created
User and Room Mailboxes, etc.
This Retention Policy should address it:
New-RetentionPolicyTag "Voice Mail 60 Day Retention" -Type All -MessageClass voicemail -Comment "Untagged messages removed after 60 days." -RetentionEnabled $true -AgeLimitForRetention
60 -RetentionAction DeleteAndAllowRecovery
Thing is, just like any "set" cmdlet, I prefer to first query like everyone else with a "get" cmdlet.
Do you know if there's a way to query this first?
Thank you very much for your time,
Mr Mister

You mean you want to see if it actually works as expected? In that case I would create the policy and then apply only to one mailbox and see how that goes.
http://technet.microsoft.com/en-us/library/dd298052(v=exchg.141).aspx
Apply a Retention Policy to Mailboxes
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Business service NOT getting configured from jca file in Windows 7

I am faced with a problem in Windows 7.
In one machine with Win XP as OS, when I create a business service from a JCA(.jca) file, the Endpoint URI gets configured automatically with jca://<jndi name>/... and having protocol as jca.
But, when I do the same in Windows 7, the endpoint URI is not getting configured neither do I find a jca option in protocol so that I can configure it manually.
The probable reason I sense, is that some files(may be jar or others) are not getting the acccess required by OEPE.
Any suggestions, which jars or files are required for the configuration to be correct??? I mean for the JCA protocol to come up ??

I could create a JCA business service on windows 7 64bit without any issues. Can you follow below points and let us know the result -
1. Make sure that you are running eclipse as administrator. right click on "eclipse.exe" and select "Run as administrator"
2. Make sure that file $OEPE_Installation_Dir\dropins\oracle.osb.ide.link has a valid OSB home entry like below -
path=E:/ofmw11g/mw/Oracle_OSB13. Make sure that below directory exists -
$OSB_home\eclipse\plugins\com.bea.alsb.transports.jca_1.1.0
For e.g. - my setup have E:\ofmw11g\mw\Oracle_OSB1\eclipse\plugins\com.bea.alsb.transports.jca_1.1.0
Regards,
Anuj

Not set configure retention policy to recovery window of 7 days

Similar Messages

Maybe you are looking for