Rollback with rman level 0

Hello all,
I am very new to oracle and i wanted to know if i have a full level 0 rman backup (with archive log ) that i have taken today(2/9/2012 13:00 pm cst)....
and now the questions is...
is there anyway possible or is oracle is capable of rolling me back to lets say 2 days back with just my backup i have taken 2 days back??...but keep in mind i only have level 0 backup that i took today... lets say i am on version 11.2.0.1
From my understanding of rman, i can only go back up until 2/9/2012 13:00 pm cst ?? or can i go back to lets says 2/7/2012 13:00 pm cst ??

In your case RMAN alone cannot rewind back data. You would need to have older backups that the point in time needed and/or to have flasback database enabled (http://docs.oracle.com/cd/E11882_01/backup.112/e10642/flashdb.htm#BRADV180).

Similar Messages

Auxiliary channel allocation in TSPITR with RMAN-managed instance

Hi,
I'm trying do perform TSPITR with RMAN-managed auxiliary instance. All backups are stored on tape. I need to send MML environment values while allocating auxiliary channel to connect to correct NetWorker server and send other NetWorker parameters.
Unfortunately I have issues with sending these params - I can't send them from recover RUN block, as auxiliary instance does not exists at the time when I'm starting to execute script. (example from test env using disk channels)
RMAN> RUN
2> {
3> ALLOCATE CHANNEL c1 DEVICE TYPE disk;
4> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE disk;
5> SET NEWNAME FOR DATAFILE 1 TO '/u01/backup/tspitr/10gdb2/system01.f';
6> SET NEWNAME FOR DATAFILE 2 TO '/u01/backup/tspitr/10gdb2/undo01.f';
7> SET NEWNAME FOR DATAFILE 7 TO '/u01/backup/tspitr/10gdb2/hr_bak01.f';
8> SET AUXILIARY INSTANCE PARAMETER FILE TO '/home/oracle/params_auxinit.ora';
9> RECOVER TABLESPACE hr_test UNTIL TIME "SYSDATE - 1/4"
10> AUXILIARY DESTINATION '/u01/backup/tspitr/10gdb2';
11> RELEASE CHANNEL c1;
12> RELEASE CHANNEL aux1;
13> }
allocated channel: c1
channel c1: sid=141 devtype=DISK
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 04/07/2010 17:21:53
RMAN-06174: not connected to auxiliary databaseI know I can do it using configure, but is there any way to set this on session level?
10.2.0.4, RHEL
Thanks,
Lukasz

What can be done here, is to CONFIGURE AUXILIARY CHANNEL to set appropriate params for auxiliary instance (without allocating channels manually).
I just wanted to know, if I can do it just for this one session (without permanent modification). What I can do, is:
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE DEFAULT DEVICE TYPE TO sbt_tape;
RUN
(new names, auxiliary parameter file)
RECOVER TABLESPACE ...
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE DEFAULT DEVICE TYPE CLEAR;I just wanted more 'elegant' solution.
Update:
Due to bug no. 4768353 there is no possibility to use automatic channel allocation in auxiliary instance. Problem resolved by using own customized auxiliary instance started before recovery process. Channels have been allocated manually using ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt... on already running aux.
Thanks,
Lukasz
Edited by: Łukasz Mastalerz on Apr 19, 2010 6:47 PM

Rman level 0

Hi I have taken RMAN level 0 backup and scheduled level1 previously. Now we have moved the old datafiles and backupset and wanted to start from level 0 again. So we are running the same script and it is not running in level 0 but looking for level 1. and throwing errors. Now the flash recovery area is empty but only having the archivelogs and we want to take level 0 freshly. following is the error i am getting.
RMAN> run {
2> allocate channel oem_disk_backup device type disk;
3> recover copy of database with tag 'ORA\$OEM_LEVEL_0';
4> delete backup completed before 'SYSDATE-30' device type disk;
5> backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA\$OEM_LEVEL_0' database plus archivelog ;
6> delete archivelog until time 'SYSDATE-30';
7> release channel oem_disk_backup;
8> }
9>
using target database control file instead of recovery catalog
allocated channel: oem_disk_backup
channel oem_disk_backup: sid=564 devtype=DISK
Starting recover at 20-AUG-07
no copy of datafile 6 found to recover
no copy of datafile 7 found to recover
no copy of datafile 8 found to recover
no copy of datafile 9 found to recover
no copy of datafile 10 found to recover
channel oem_disk_backup: starting incremental datafile backupset restore
channel oem_disk_backup: specifying datafile copies to recover
recovering datafile copy fno=00001 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_system_3bk8d7hk_.dbf
recovering datafile copy fno=00002 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_undotbs1_3bk8f0m4_.dbf
recovering datafile copy fno=00003 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_sysaux_3bk8fhov_.dbf
recovering datafile copy fno=00004 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_users_3bk8fyrp_.dbf
recovering datafile copy fno=00005 name=/disk02/orabackup/beprod/flash_recovery_area/BEPROD/datafile/o1_mf_becms_3bk7zghd_.dbf
channel oem_disk_backup: reading from backup piece /disk02/orabackup/beprod/flash_recovery_area/BEPROD/backupset/2007_08_20/o1_mf_nnnd1_TAG20070820T010830_3d
ldd8z4_.bkp
released channel: oem_disk_backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/20/2007 21:25:04
ORA-19870: error reading backup piece /disk02/orabackup/beprod/flash_recovery_area/BEPROD/backupset/2007_08_20/o1_mf_nnnd1_TAG20070820T010830_3dldd8z4_.bkp
ORA-19505: failed to identify file "/disk02/orabackup/beprod/flash_recovery_area/BEPROD/backupset/2007_08_20/o1_mf_nnnd1_TAG20070820T010830_3dldd8z4_.bkp"
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Recovery Manager complete.
Please help,
Thanks,
G.

Take Level 0 backup using the below command and then go for the one you are executing
BACKUP INCREMENTAL LEVEL 0 TAG='ORA\$OEM_LEVEL_0' DATABASE;
Regards

Oracle 3113 creating a standby with rman

Hello,
environment is 11gR2 on Linux.
Tested on CentOS 5.5 as OS and local LAN as interconnect and the duplicate command terminates successfully in some minutes.
Same script but using oel 5.5 and a wan (3Mbit/s) and I keep getting 3113 errors after about 2h or 3h.
I suspect some timeout on wan (that is over vpn) but I would also like to trace something at my side.
I run a shell script with nohup and send it to background and this is the log, from which you can see the rman script:
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Sep 7 14:50:11 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: TESDB1 (DBID=11492743)
RMAN>
connected to auxiliary database: DUMMY (not mounted)
RMAN>
RMAN> run{
2> allocate channel prmy1 type disk;
3> allocate auxiliary channel stby1 type disk;
4> duplicate target database for standby from active database
5> spfile
6> parameter_value_convert 'TESDB1','TESDB1DR'
7> set db_file_name_convert='/TESDB1/','/TESDB1DR/'
8> set log_file_name_convert='/TESDB1/','/TESDB1DR/'
9> set 'db_unique_name'='TESDB1DR'
10> set control_files='/app/oradata/TESDB1DR/control01.ctl','/app/oradata/flash_recovery_area/TESDB1DR/control02.ctl'
11> set db_recovery_file_dest='/app/oradata/flash_recovery_area'
12> set DB_RECOVERY_FILE_DEST_SIZE='4977M'
13> nofilenamecheck;
14> }
using target database control file instead of recovery catalog
allocated channel: prmy1
channel prmy1: SID=12 device type=DISK
allocated channel: stby1
channel stby1: SID=135 device type=DISK
Starting Duplicate Db at 07-SEP-10
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /app/oradata/TESDB1DR/temp01.dbf in control file
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting backup at 07-SEP-10
channel prmy1: starting datafile copy
input datafile file number=00003 name=/app/oradata/TESDB1/undotbs01.dbf
.. after about three hours (and 3.2Gb transferred) it continues with:
RMAN-03009: failure of backup command on prmy1 channel at 09/07/2010 17:53:49
RMAN-06136: ORACLE error from auxiliary database: ORA-03113: end-of-file on communication channel
Process ID: 3187
Session ID: 192 Serial number: 3
continuing other job steps, job failed will not be re-run
.. after 15 minutes:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/07/2010 18:09:35
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on clone_default channel at 09/07/2010 18:09:34
RMAN-10038: database session for channel clone_default terminated unexpectedly
RMAN> **end-of-file**
RMAN>
Recovery Manager complete.
the undo tbs is 3.2 Gb so I'm not sure if the 3113 happens at the end of copy... but the tablespace doesn't succeed
and the other jobs don't start even if it says "continuing other job steps"..
rman started at 14:50 and in listener at dr site I have:
Tue Sep 07 14:50:55 2010
07-SEP-2010 14:50:55 * service_update * TESDB1DR * 0
07-SEP-2010 14:50:55 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=oracle)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35240)) * establish * TESDB1DR * 0
Tue Sep 07 15:00:58 2010
07-SEP-2010 15:00:58 * service_update * TESDB1DR * 0
Tue Sep 07 16:35:04 2010
07-SEP-2010 16:35:04 * service_update * TESDB1DR * 0
Tue Sep 07 17:02:04 2010
07-SEP-2010 17:02:04 * service_update * TESDB1DR * 0
07-SEP-2010 17:02:10 * service_update * TESDB1DR * 0
Tue Sep 07 17:53:17 2010
07-SEP-2010 17:53:17 * service_update * TESDB1DR * 0
Tue Sep 07 18:09:00 2010
07-SEP-2010 18:09:00 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=rman)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=32610)) * establish * TESDB1DR * 0
In alert.log at dr site I have at 17:02 (about 50 minutes before error):
Tue Sep 07 15:05:01 2010
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Sep 07 17:02:03 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:02:03
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35226))
some times (always at 17:02) and nothing more
In alert.log at primary site:
Tue Sep 07 14:50:36 2010
Clearing standby activation ID 11529351 (0xafec87)
The primary database controlfile was created using the
'MAXLOGFILES 16' clause.
There is space for up to 13 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
Tue Sep 07 16:00:40 2010
Thread 1 advanced to log sequence 759 (LGWR switch)
Current log# 3 seq# 759 mem# 0: /app/oradata/TESDB1/redo03.log
Tue Sep 07 16:00:41 2010
Archived Log entry 528 added for thread 1 sequence 758 ID 0xafec87 dest 1:
In sqlnet.log of primary site:
Tue Sep 07 17:53:49 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:53:49
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.12.41)(PORT=1521))
and the same at 18:09
No other errors.
Any hints?
BTW: what is the minimum size of undo tbs? Can I have compression enabled also during duplication if transport service is configured with COMPRESSION=ENABLED, or does it count only when copying redo files?
Thanks in advance,
Gianluca

Thanks for your reply.
I will try your suggestion as it could come useful some time.
So with this alternate method at the end I would have standby aligned as of backup time, correct?
And after running something like this on standby:
SQL> alter database recover managed standby database disconnect from session;
It will begin to receive, archive and apply redo logs, correct?
Some answers regarding the original question. It was confirmed that there was a 2hours cut-off time at firewall level.
The first datafile that the rman session began to copy was 3.2Gb in size, taking more than 2 hours completing.
Monitoring with netstat on source and target I saw this at source during the duplicate process:
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
tcp 0 369240 10.49.1.93:50371 192.168.12.41:1521 ESTABLISHED
and the session bound to port 50371 was the only one pushing data (send queue not empty).
The other 3 ones I presume are for control of rman session. I get 3 sessions even if I open only one channel on primary side.
After the first datafile completes copy, a new session (with port 14871) is established substituting the other one.
The three initial ones instead remain for all the duplicate process.
tcp 0 487872 10.49.1.93:14871 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
So after the copy of the first file, the session come back to one or more of the initial 3 ones, and they probably make a push-ack, got a 3113 as the firewall has silently cut them after 2 hours.... and the datafile, even if completed, is not marked as completed. A new run would copy again it...
Now the time has been put to 8hours, with 24hours being the maximum value set (no disable possible as far as the network guy said...).
And the duplicate completed correctly.
Would I have to fear any problems with this cut-off due to "normal" dataguard operations or not, in your opinion?
Thanks
Gianluca

Restore incremental backup with rman

Dear Friends
can u tell me how to restore an incremental backup with rman? i backup my rman with statement below :
1. backup full database format '/oracle/PRD/sapbackup/%U';
the results was :
-rw-r----- 1 oraprd dba 19006996480 Jun 10 12:08 0ojiit4n_1_1
-rw-r----- 1 oraprd dba 12746752 Jun 10 12:08 0pjiiu6b_1_1
2. after that i do incremental backup :
backup incremental level 1 cumulative database format '/oracle/PRD/sapbackup/%U';
the results was :
-rw-r----- 1 oraprd dba 173400064 Jun 10 13:44 0ujij2k0_1_1
-rw-r----- 1 oraprd dba 12746752 Jun 10 13:44 0vjij3qc_1_1
what statement i need to run for restore the incremental backup?

run{
ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
RESTORE DATABASE;
RECOVER DATABASE;
The above command will restore your database from the last good RMAN backup. Your last backup is incremental level backup as you posted. The above command will fullfill your requirements

Have anyone got Veritas BLIB working with RMAN?

We are trying to set up backups of Oracle 8.1.6 databases
using Veritas software:
- Veritas File System
- Veritas NetBackup 3.4
- Veritas Database Edition for Oracle
- Veritas BLIB agent (Block-Level Incremental backups)
We were able to perform BLIB backups without RMAN,
and run non-proxy backups to tape with RMAN. However, when I
attempt to run BLIB backup with RMAN, something like
run
allocate channel c1 type 'SBT_TAPE'
parms 'ENV=(NB_ORA_CLASS=TestOracle)';
beckup
incremental level 0
proxy only
I get
RMAN-08526: channel c1: VERITAS NetBackup for Oracle8 - Release
3.4GA (030800)
fsckpt_fsopen: You don't have a license to run this program
This does not make sense because
1. We do have a valid PERMANENT (i.e. non-expiring) license
as can be seen by running vxlicense
2. Non-RMAN BLIB backups work
3. I can initiate VxFS checkpoints using vxdba utility.
Thanks,
Sev
[email protected]

Are you running Oracle Enterprise Edition? That my be the
problem.

ORA-19502 with RMAN

Hi All
I am taking hat backup with rman. and every time by backup fails with ORA-19502 and ORA-27072 error. I have sufficient space on the mount point then also every time (i have tried 4 time) backup fails when this start /v01/oradata/PATCH/APPS_TS_MEDIA07.dbf. I have checked dbf file with dbv utility, datafile is ok.
-rw-r--r-- 1 oraptc dba 5974 Aug 30 05:52 PATCH_Full_083011_05:17:28.log
ZEUSoraptc>tail -f PATCH_Full_083011_05:17:28.log
input datafile fno=01034 name=/v01/oradata/PATCH/APPS_TS_MEDIA07.dbf
channel t4: starting piece 1 at 30-AUG-11
RMAN-03009: failure of backup command on t1 channel at 08/30/2011 05:52:58
ORA-19502: write error on file "/v05/appp/oraptc/backup/full/PATCH-Full-14ml8vbu_1_1.bkp", blockno 262017 (blocksize=8192)
ORA-27072: File I/O error
HP-UX Error: 2: No such file or directory
Additional information: 4
Additional information: 262017
Additional information: 1040383
channel t1 disabled, job failed on it will be run on another channel
ZEUSoraptc>bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 204800 192432 12368 94% /
/dev/vg00/lvol1 298928 44600 224432 17% /stand
/dev/vg00/lvol8 5120000 2960336 2151464 58% /var
/dev/vg05/lvol1 943718400 683801552 257887840 73% /v05
Kindly advice me. I am using /v05 mount point which have 250Gb free space. and in general my backup size is 140Gb.
OS is HP-Unix and database is 10.2.0.4
Thanks
krishna

Hi Krishna
I think it has something to do with configuration. Make sure oracle software owner (oracle user, by default) at OS level has full permissions on the file system under the new mount point. If everything is OK, configure the disk channel explicitly and see if it works.
To test, do this in RMAN session
$> rman target / catalog rman/<pass>@catalog
RMAN> configure channel ch1 device type disk format '/v05/appp/oraptc/backup/full/PATCH-Full-%U' ;
RMAN> backup datafile 1;
If it's fine, you can go ahead and do the database backup.

Got error while recover controlfile with rman

Dear all,
My controlfile and some datafiles were crash and i tried to recover their with rman as the following step:
1. startup nomount;
2. restore controlfile from autobackup;
3. alter database mount;
4. restore database;
5.SELECT archivelog_change#-1 FROM v$database;
ARCHIVELOG_CHANGE#-1
1301671
6.run {
set until scn 1301671;
recover database;
executing command: SET until clause
Starting recover at 01 พ.ย. 2006
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/01/2006 15:38:01
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver if needed
start until change 1301671 using backup controlfile
ORA-00283: recovery session canceled due to errors
ORA-01190: controlfile or data file 1 is from before the last RESETLOGS
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\DB01\SYSTEM01.DBF'
What happend? Please give me some advise.
Thaks for advance !
Chara

After every resetlogs you have to take fresh backup.
It seems you have opened your database in resetlogs and your backup is prior to this resetlogs.So the controlfile is showing inconsistance with the other datafiles.

Migrating with RMAN from 10g to 11g

Hi gurus,
I am following the following procedure to migrate database from 10g to 11g using rman
Source side:
RMAN>connect target
RMAN>backup database;
RMAN>backup archivelog all;
RMAN>backup current controlfile;
SQL> create pfile from spfile;
Copied datafile, archivelog backup files and pfile and password files to target side. i.e. on 11g server side
Target side:
Set proper parameters for 11g
SQL>startup nomount;
RMAN>connect target
RMAN>set dbid=<source database id>
RMAN>catalog start with '<rman backup file location';
RMAN>restore controlfile;
RMAN>run
set newname for datafile 1 to '<target datafiles location with file name';
restore database;
switch datafile all;
finished
upto now it's success full when i am trying to recover
RMAN>recover database;
it is saying
rman 00571
rman 00569
rman 00571
rman 03002
ora - 19698
can you please suggest the solution for this.
thanks a lot.

I'm not sure what you're doing is supported.
You are taking a 10g database and restore and recover it using 11g software.
I think you are allowed to do that with 10g software only.

How can an ADF Tree be configured to work with varying levels of heirarchy?

We have a need for a Locations tree that represents the Locations heirarchy for any one of our clients. Depending on the client the number of levels in a location heirarchy could range from 1 to 9.
I have created 9 different tree bindings and I can change the tree binding in the jsp page - the example below is for a client with 4 location levels.
<af:tree value="#{bindings.ScdLocs4View1.treeModel}" var="node"
binding="#{backing_locations.tree2}" id="tree2">
For a client with 5 location levels, I'd like to programatically change the value to
#{bindings.ScdLocs5View1.treeModel. How can I do this?
I was thinking I could use the setValue method on the tree control in my page's backing bean. But I have been unable to get a reference to the tree binding.
I don't see an appropriate method for finding a Tree Binding. There are methods for finding an Iterator Binding, an Executable Binding, or a Region Binding (whatever that is). But how do I "find" a reference to a Tree Binding?
I have also given consideration to using a single Tree Binding with 9 levels (or rules in the Tree Binding Editor) and finding a way to programatically "start" the rendering at a particular level (or rule) - in effect telling the ADF Tree control to ignore some number of rules and begin with the specified rule. But I haven't been able to figure out how to do this either.
Help would be greatly appreciated.

Bill,
A tree binding is a particular kind of control binding, so you can find it as a control binding and then cast it to the more specific interface to work with it.

Sales order display-how to change color of item with high level 0

Please does anyone know how can i chenge the color of item with high level 0 in display of sales order in red or yellow so it can be seen better for better searching on page?
thank you in advance...
regards..

You'd probably have to do a modification in SD for that. But what you can do, is make the higher level item not changeable. You could also set the display range to UHAU to only see the main items, do this in transaction VOV8. Or you could change your item category in VOV7 only to show main items.
good luck

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

Logical Standby recover with RMAN

Hi All,
I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
My steps e.g.:
1. Make a new server for my new_log_stdb and repair structure of catalogs;
2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
3. Restore DB with RMAN from backup to new_log_stdb;
4. On cur_log_stdb execute "alter database stop logical standby apply";
5. Change a DNS name from cur_log_stdb to new_log_stdb;
6. On new_log_stdb execute "alter database start logical standby apply immediate";
I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
But if this plan won't work how can I restore Logical Standby DB from RMAN backup and resume replication from Primary?
Configuration:
Oracle Linux 6.4
Oracle Database 11.2.0.3
Primary and Physical with Data Guard

Hello;
The only way to know for sure is to test it. You are asking somebody you don't know to confirm a recovery test for you. You have to perform the test yourself to be certain.
If your plan does not work you can always rebuild the Standby.
Best Regards
mseberg

Problem in Aggregate with Multiple level of dimension

Hi,
I have a BI repository with a snowflake schema. I have also designed the business model with snowflake, It works with drilling and all but I am facing problem when I am
creating a logical column aggregating with a higher level of dimentation. Let me illustrate that :
I have the Following Hierarchy :
Tournament(id, Name) ---- > Round (id, name, tournament_id) -------> Match (id, Name, RoundId ) | Match is fact table and other 2 dimension.
I also created a logical dimension called tournament with 3 levels.
Now say I want to create a logical column Total Number of Matches , aggregating to the dimension level of Tournament. The result gives counts a 0 for every tournament. However
it is working perfectly when the dimension level is Round (which is the immediate next level after fact).
The Logical request generated (in case of Tournament level) :
   MatchId:[DAggr(Measure1.MATCHID by [ Matches$.TournamentId] SB Tournament)] as c1 GB.
    There is no such column as TournamentId in Matches$ table. How does the BI server got this ?
   The execution plan evaluate this:
     cast(NULL as INTEGER ) as c1 GB [for database 0:0,1]
   Can someone please explain why is this happening, is it because of the snowflake schema, but I guess if BI server can handle a snowflake schema it should work the Aggregate
   properly in multiple levels of dimensions, or it is something I am doing wrong.
   Execution Environment:
     Windows XP , OBI 10g on OC4J. Data source : MS Excel (ODBC 3.5)
Regards,
Ru

Hi,
With reference to your question.
Can any operator perform this task..I don't think any single operator will help you.
I suggest using an intermediate (staging) table by using a PL SQL procedure with output port to store the values of account number provided the number of accounts are limited. Else use an array variable for account of an employee.
In short no simple solution because of the bad source design else the pivot/unpivot operator would have helped you.
Cheers
- Mohammed

Why open items with dunning level 0 sometimes appear?

Hi All,
when I run the dun transaction (F150) sometimes in table MHND and MHNK open items with dunning level 0 appear. These are open items overdue, but not enough to level 1. Note that this problem appear only sometimes.
Do you know how to avoid this?
Many thanks

Check if deselcting the indicator for Always Dun? in dunning level configuration in FBMP ,solves your issue.
Thanks and regards
Kedar

Rollback with rman level 0

Similar Messages

Maybe you are looking for