Database in Raw device recover in time tablespace
How recover database in raw device using clone database
(Recovery Manager) ?
The problem is follow:
When RMAN begin then recover proces he need create the clone
database. @ How create this database ? @ In file system or raw
device ? if he create it in raw device @ Then device necessary
must be created before ?
@ How many devices ? @ What is your size ?
Thanks ...
null
With raw devices alternative cost of performance is typical management difficulties like this, but after 10g ASM is a big shift - http://www.dbazine.com/olc/olc-articles/still5
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/storeman.htm#i1021337
Best regards.
Similar Messages
-
Hello,
I am getting the following error when I try to complete approval process.
ORA-20001: Unable to create tablespace. ORA-01
119: error in creating database file '//./FLOW_1.dbf' ORA-27040: skgfrcre: creat
e error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 2)
The system cannot find the file specified.
I checked the alert log for error here is the error in the alert log file.
ORA-1119 signalled during: CREATE TABLESPACE FLOW_1 DATAFILE '//./FLOW_1.dbf'..
and i found the syntax for create tablespace was wrong.
To create a tablespace in RAC with RAW device environment under windows.
it should have forward black slash instead of backward slash "/" without .dbf extension.
so, I changed the syntax i was able to create tablespace through sqlplus.
When APEX tool try to create this tablespace it throws this error..
Old: CREATE TABLESPACE FLOW_1 DATAFILE
'\\.\FLOW_1.dbf' SIZE 10304 K REUSE AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
error : ORA-01119: error in creating database file '\\.\FLOW_1.dbf'
New:
CREATE TABLESPACE FLOW_1 DATAFILE
'\\.\FLOW_1' SIZE 10304 K REUSE AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
Tablespace created.
Is it a bug in APEX 3.0.1.??
Is anyone installed APEX in RAC ??
JamesHi,
One observation, Apex is switching the Session ID after one got killed ? I was working on Apex page with browse Item to test open cursor count,
after killing the SID (227) on which the open cursor count was getting increase, it APEX automatically switches to new SID(149) for that session.
Now the problem is even if I have two SID's and one hits the maximum open cursor count, It is not switching to other SID instead the whole application becomes unavailable.
STATNAME SID VALUE USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 74 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 227 325 APEX_PUBLIC_USER Killed
opened cursors current 244 15 APEX_PUBLIC_USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 76 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 244 15 APEX_PUBLIC_USER
Please kindly help in this.
Thanks in Advance
Thanks & Regards
Sanjay
Edited by: user11204334 on Dec 8, 2010 1:02 AM -
How use raw device in linux?
Hi all.
scene:
oracle 8.1.6.1
Linux red hat 6.1
I'm trying to create a database with raw device.
In HPux the raw device is /dev/rdsk but I found no documentation for linux raw device.
thanks for any help.
nullProve it: try to create file large than 2Gb on 8.1.6 under Linux (under NT it works) and try to use raw partitions. About Pmon ORA-601 simply check Metalink.
I know Oracle, it is my work. I like Oracle database. I think, Linux is the best OS. But i want Oracle to solve current bugs more quickly, for a customers could not say "Oracle on Linux - it ***** ". Because, customers must to know about problems to avoid it. It is a more biger problem, when database is crashed. -
Convert from raw devices to filesystems
Is there a document or technote that describes a best practice approach to converting a database from raw devices to filesystems?
Thanks!Thank you for your posting - The Member Feedback forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions cannot be answered. However we recommend that you post this thread to the "Database - General" forum.
The URL is: General Database Discussions
Also, please try using OTN's search function.
Thanks - The OTN team -
Tablespace creation problem in RAC using raw device.
Hi ,
If i created a tablespace with the .dbf extension i am able to create the tablespace. on other hand if i use .dbf extension it;s failing..
can anyone help me out why it is happening??
here is the code...
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SYS at terac >
SYS at terac >CREATE TABLESPACE FLOW_1 DATAFILE
2 '\\.\FLOW_1' SIZE 10304 K REUSE AUTOEXTEND OFF
3 EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
4
SYS at terac >/
Tablespace created.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
CREATE TABLESPACE TEST2 DATAFILE '\\.\FLOW_1.DBF' SIZE 10304 K
REUSE AUTOEXTEND OFF EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT
SPACE MANAGEMENT AUTO
SYS at TERAC >/
CREATE TABLESPACE TEST2 DATAFILE '\\.\FLOW_1.DBF' SIZE 10304 K
ERROR at line 1:
ORA-01119: error in creating database file '\\.\FLOW_1.DBF'
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
thanks
james.I'm by no means a windows expert so I might be totally wrong here, but here goes.
You have to refer to the raw device by its name in the datafile clause. If you use a different name then the o/s can't find the device. Simple as that. -
Why don't we keep Oracle Database ARCH logs in RAW devices
Hi All,
Why don't we keep Oracle Database ARCH logs in RAW devices?
How ARCH process is related to Block Device and Character Device ?
Thanks,
Tusar
Edited by: user11987718 on 26-Jun-2012 09:59Why don't we keep Oracle Database ARCH logs in RAW devices? 1.This is because raw devices do not enable sequential writing of consecutive archive log files.
http://docs.oracle.com/cd/E11882_01/rac.112/e16795/rman.htm#RACAD320
2.with raw you have to specify the exact size of the file at creation time, in contrast with file system, where you can create file without specifying its size, start writing to it, apending new blocks to it until you are done, and thus creating a file of whatever size it needs to be to hold all information.
http://www.dbasupport.com/forums/archive/index.php/t-16429.html
3.raw file systems are difficult to manage because you cannot run normal os commands on them.(as there is no file systems)
How ARCH process is related to Block Device and Character Device ?A block device would read/write bytes in fixed size blocks, as in disk sectors. Character devices read/write 0 or more bytes, in a stream, such as a TTY or a keyboard.
For more details about what is block and character device type :
http://en.wikipedia.org/wiki/Device_file
And now think, how arch process is related to block and character devices.
Regards
Girish Sharma -
Database Data files on RAW Devices
Hi,
I'm creating a database and wish to locate the tablespaces on a raw device.
How do I specify the datafiles for the tablespaces on the raw device.> Any reason for moving to raw device?
I actually prefer raw devices and ASM over using cooked file systems.
By default RAW devices eliminate the "interference" of the kernel. It does not manage a file system on the device. There are no other foreign processes that can use that raw device (as is often the case with cooked devices). There is no o/s file system cache for that device. A physical I/O on the Oracle side means a dinkum physical I/O and not a maybe-logical-I/O-from-the-file-system-o/s-cache.
There is no need for me as DBA to manage that file system according to OFA standards (ASM does it for me). There is no need for me to go through the learning curve of using a 3rd party volume manager. I have features like automated load balancing while the instance is up and running.
Yes, there is an argument to be made for just how much of a performance improvement in I/O one can get from a raw device versus a cooked file system. But I/O performance is not the only consideration. -
Advantage of using RAW devices for storing database
Hi,
Marry Christmas to all.
Oracle 10g version 10.2.0.1.0 (rac)
OS : HP-UX 11i
I am new to this enviornment. We are using raw devices for storig the database.
Please tell what are the advantages for using raw devices for storing the database?
Thanks.http://www.fors.com/orasupp/unix/37914_1.HTM
The above link explains the raw devices and advantages. -
Is database using File system, RAW devices or ASM?
Hi there
Is is possible to find out if the database is using File system, RAW devices or ASM for storage?
I think for ASM, we can tell by querying the V$DATAFILE view if it has ' DATA ' or something like that (a name that has ' ' prefixed to it). Is this the only way? How about other sotrage types (RAW and Filesystem)?
Thanks in advance!user12033597 wrote:
I think for ASM, we can tell by querying the V$DATAFILE view if it has ' DATA ' or something like that (a name that has ' ' prefixed to it). Is this the only way? How about other sotrage types (RAW and Filesystem)?V$DATAFILE or DBA_DATA_FILE
Raw depends on your OS - in *nix, likely something like /dev/sdc1
ASM depends on ASM and will include + and will follow an ASM pattern, such as described http://docs.oracle.com/cd/B19306_01/server.102/b14200/clauses004.htm
File depends on OS - in *nix, likely start with a '/' and NOT be in /dev or /proc. In Winders start with C:\ or some other disk path.
Nicely discussed in the docs in the Administrators Guide found at http://tahiti.oracle.com -
Create tablespace using RAW device
Hi,
When you create the tablespace using RAW device, you no need to specify the size parameter in the sql. It works in Solaris but not in Linux.
I dont know why, can anyone experience this issue before? please let me know
Thanks
VeeraMy advice for you would be to always include SIZE parameter when you create tablespace, redo log file on raw device.
Best Regards
Krystian Zieja / mob -
Have anyone tried to use raw devase base database?
I tried all teh documentation available but could not find
anything about this
If I tell Orecle to create a database on a raw device (like
/dev/sda6), it tries to erase the file. However it should accept
it I suppose. Mounting the device /dev/sda6 under a directory
doesn't help either. Is it normal behaviour and I am missing
something or raw device database structure is not implemented
under Linux yet?
Thanks in advance
nullNicholas Tufar (guest) wrote:
: Have anyone tried to use raw devase base database?
: I tried all teh documentation available but could not find
: anything about this
: If I tell Orecle to create a database on a raw device (like
: /dev/sda6), it tries to erase the file. However it should
accept
: it I suppose. Mounting the device /dev/sda6 under a directory
: doesn't help either. Is it normal behaviour and I am missing
: something or raw device database structure is not implemented
: under Linux yet?
: Thanks in advance
Linux dosn't support raw devices. Oracle requires symbol
device but in Linux you have only block devices. Also access to
this devices is cached by OS.
null -
TSPITR - Recover a Dropped Tablespace aborting due dependency over XDB.
I found an issue using TSPITR to Recover a Dropped Tablespace when XML DB (XDB) is installed on a different tablespace from "SYSAUX".
During execution of TSPITR RMAN use Data Pump to export/import Tablespace Metadata as Data Pump has dependency over XDB views and related objects and XDB is installed on a set of tablespace not included on dummy database then EXPDP fails.
Errors raised ORA-39123, ORA-00376, ORA-01110.
I didn't found any limitation about XDB location on documentation or MoS.
This looks like a Oracle Bug.
See this:
XDB installed on TABLESPACE XDB.
SQL> select owner,tablespace_name
from dba_segments
where owner='XDB'
GROUP BY owner,tablespace_name ;
OWNER TABLESPACE_NAME
XDB XDBDropping Tablespace SOE.
SQL> select to_char(sysdate,'dd-mm-yyyy hh24:mi:ss') actual_date from dual;
ACTUAL_DATE
17-12-2012 11:57:44
SQL> drop tablespace SOE including contents and datafiles;
Tablespace dropped.Restoring Dropped Tablespace.
RMAN> list backup tag TAG20121217T112226;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
69 Full 995.61M DISK 00:02:41 17-12-2012 11:25:07
BP Key: 69 Status: AVAILABLE Compressed: YES Tag: TAG20121217T112226
Piece Name: +DG_16M/prod/backupset/2012_12_17/nnndf0_tag20121217t112226_0.286.802264947
List of Datafiles in backup set 69
File LV Type Ckp SCN Ckp Time Name
1 Full 1628648 17-12-2012 11:22:26 +DS8000_DG/prod/datafile/system.349.799325249
2 Full 1628648 17-12-2012 11:22:26 +DS8000_DG/prod/datafile/sysaux.348.799325249
3 Full 1628648 17-12-2012 11:22:26 +DS8000_DG/prod/datafile/undotbs1.347.799325251
4 Full 1628648 17-12-2012 11:22:26 +DS8000_DG/prod/datafile/users.335.799325251
5 Full 1628648 17-12-2012 11:22:26 +DS8000_DG/prod/datafile/audit_aux.287.799330083
6 Full 1628648 17-12-2012 11:22:26
7 Full 1628648 17-12-2012 11:22:26 +DS8000_DG/prod/datafile/xdb.311.801410833
RMAN>
run{
SET NEWNAME FOR DATAFILE 6 TO "+DS8000_DG";
RECOVER TABLESPACE SOE
UNTIL TIME "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')"
AUXILIARY DESTINATION '/u01/app/oracle/flash_recovery_area01/stage_area_tspitr';
executing command: SET NEWNAME
Starting recover at 17-12-2012 12:01:29
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='FCox'
initialization parameters used for automatic instance:
db_name=PROD
db_unique_name=FCox_tspitr_PROD
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr
log_archive_dest_1='location=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr'
#No auxiliary parameter file used
starting up automatic instance PROD
Oracle instance started
Total System Global Area 292278272 bytes
Fixed Size 2220880 bytes
Variable Size 109055152 bytes
Database Buffers 176160768 bytes
Redo Buffers 4841472 bytes
Automatic instance created
List of tablespaces that have been dropped from the target database:
Tablespace SOE
contents of Memory Script:
# set requested point in time
set until time "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')";
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 17-12-2012 12:01:46
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=16 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece +DG_16M/prod/autobackup/2012_12_17/s_802265113.276.802265115
channel ORA_AUX_DISK_1: piece handle=+DG_16M/prod/autobackup/2012_12_17/s_802265113.276.802265115 tag=TAG20121217T112513
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:05
output file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/controlfile/o1_mf_8dy9ghpz_.ctl
Finished restore at 17-12-2012 12:01:52
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until time "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')";
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 6 to
"+DS8000_DG";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 3, 2, 6;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 17-12-2012 12:01:58
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_undotbs1_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to +DS8000_DG
channel ORA_AUX_DISK_1: reading from backup piece +DG_16M/prod/backupset/2012_12_17/nnndf0_tag20121217t112226_0.286.802264947
channel ORA_AUX_DISK_1: piece handle=+DG_16M/prod/backupset/2012_12_17/nnndf0_tag20121217t112226_0.286.802264947 tag=TAG20121217T112226
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:09:15
Finished restore at 17-12-2012 12:11:13
datafile 6 switched to datafile copy
input datafile copy RECID=5 STAMP=802267873 file name=+DS8000_DG/prod/datafile/soe.487.802267321
datafile 1 switched to datafile copy
input datafile copy RECID=6 STAMP=802267873 file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_system_8dy9gs09_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=7 STAMP=802267873 file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_undotbs1_8dy9ov17_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=8 STAMP=802267873 file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_sysaux_8dy9hxsc_.dbf
contents of Memory Script:
# set requested point in time
set until time "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')";
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 3 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 6 online";
# recover and open resetlogs
recover clone database tablespace "SOE", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 3 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 6 online
Starting recover at 17-12-2012 12:11:14
using channel ORA_AUX_DISK_1
starting media recovery
archived log for thread 1 with sequence 15 is already on disk as file +DG_16M/prod/archivelog/2012_12_17/thread_1_seq_15.277.802267317
channel ORA_AUX_DISK_1: starting archived log restore to default destination
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=14
channel ORA_AUX_DISK_1: reading from backup piece +DG_16M/prod/backupset/2012_12_17/annnf0_tag20121217t112512_0.264.802265113
channel ORA_AUX_DISK_1: piece handle=+DG_16M/prod/backupset/2012_12_17/annnf0_tag20121217t112512_0.264.802265113 tag=TAG20121217T112512
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/1_14_801941068.dbf thread=1 sequence=14
channel clone_default: deleting archived log(s)
archived log file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/1_14_801941068.dbf RECID=141 STAMP=802267877
archived log file name=+DG_16M/prod/archivelog/2012_12_17/thread_1_seq_15.277.802267317 thread=1 sequence=15
media recovery complete, elapsed time: 00:00:01
Finished recover at 17-12-2012 12:11:19
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace SOE read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01/app/oracle/flash_recovery_area01/stage_area_tspitr''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/u01/app/oracle/flash_recovery_area01/stage_area_tspitr''";
executing Memory Script
sql statement: alter tablespace SOE read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01/app/oracle/flash_recovery_area01/stage_area_tspitr''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01/app/oracle/flash_recovery_area01/stage_area_tspitr''
Performing export of metadata...
EXPDP> Starting "SYS"."TSPITR_EXP_FCox":
EXPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-00376: file 7 cannot be read at this time
ORA-01110: data file 7: '+DS8000_DG/prod/datafile/xdb.311.801410833'
Removing automatic instance
shutting down automatic instance
database closed
database dismounted
Oracle instance shut down
Automatic instance removed
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_temp_8dyb0qok_.tmp deleted
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/onlinelog/o1_mf_3_8dyb0kfp_.log deleted
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/onlinelog/o1_mf_2_8dyb0fm9_.log deleted
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/onlinelog/o1_mf_1_8dyb07xv_.log deleted
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_sysaux_8dy9hxsc_.dbf deleted
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_undotbs1_8dy9ov17_.dbf deleted
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_system_8dy9gs09_.dbf deleted
auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/controlfile/o1_mf_8dy9ghpz_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/17/2012 12:12:19
RMAN-06962: Error received during export of metadata
RMAN-06965: Datapump job has stopped
RMAN-06960: EXPDP> Job "SYS"."TSPITR_EXP_FCox" stopped due to fatal error at 12:12:02
RMAN>If I drop tablespace SOE and XDB on Target database and try to restore both (SOE,XDB) export will succeeds but during IMPORT Metadata RMAN will faill due XDB dependency.
In my view, they (mean Oracle) need find way to include XDB Tablespace at DUMMY database only to export (EXPDP) Metadata purposes.
If someone get a workaround for this error will be grateful.
P.S: This is not a Production environment and will soon open a SR on Oracle Support.Hi Michael,
I did not find solution to use TSPITR to recover dropped tablespace if XML DB is installed in a non-default tablespace (i.e outside of SYSAUX).
As far I could understand, the only way to perform this RESTORE is using the old fashion. By creating clone database excluding all unnecessary tablespace, exporting and importing metadata from desired tablespace manually.
Since Oracle has not solved the issue I created my own workaround.
@All
If someone is able to use TSPITR to restore dropped tablespace when XDB is installed in a non-default tablespace, please let me know!!!
The procedure below is supported on All Oracle Version since 10.1 until 11.2.
I DON'T RECOMMEND to create AUXILIARY (clone) database using the same server from TARGET because you can damage the TARGET database.
On this example I'm using same server.
See this example:
### ON TARGET DATABASE
SQL> select count(1) SEG_COUNT from dba_segments where tablespace_name='SOE';
SEG_COUNT
32
SQL> ! date
Wed Dec 19 15:08:11 GMT-02:00 2012
SQL> drop tablespace soe including contents and datafiles;
Tablespace dropped.
### CHECK TABLESPACE TO BE EXCLUDED FROM RESTORE
SQL> select tablespace_name
from dba_tablespaces
where tablespace_name not in ('SYSTEM','SYSAUX','UNDOTBS1','SOE','XDB','TEMP');
TABLESPACE_NAME
USERS
AUDIT_AUX
### CHECK BACKUP ON TARGET DATABASE
RMAN> list backup completed between "sysdate-1" and "sysdate";
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
95 Full 986.56M DISK 00:03:18 19-12-2012 14:41:59
BP Key: 95 Status: AVAILABLE Compressed: YES Tag: TAG20121219T143840
Piece Name: /fra/PROD/backupset/2012_12_19/o1_mf_nnndf_TAG20121219T143840_8f3vdn3q_.bkp
List of Datafiles in backup set 95
File LV Type Ckp SCN Ckp Time Name
1 Full 1675258 19-12-2012 14:38:42 +DS8000_DG/prod/datafile/system.349.799325249
2 Full 1675258 19-12-2012 14:38:42 +DS8000_DG/prod/datafile/sysaux.348.799325249
3 Full 1675258 19-12-2012 14:38:42 +DS8000_DG/prod/datafile/undotbs1.347.799325251
4 Full 1675258 19-12-2012 14:38:42 +DS8000_DG/prod/datafile/users.335.799325251
5 Full 1675258 19-12-2012 14:38:42 +DS8000_DG/prod/datafile/audit_aux.287.799330083
6 Full 1675258 19-12-2012 14:38:42
7 Full 1675258 19-12-2012 14:38:42 +DS8000_DG/prod/datafile/xdb.311.801410833
BS Key Size Device Type Elapsed Time Completion Time
96 1.16M DISK 00:00:00 19-12-2012 14:42:08
BP Key: 96 Status: AVAILABLE Compressed: YES Tag: TAG20121219T144208
Piece Name: /fra/PROD/backupset/2012_12_19/o1_mf_annnn_TAG20121219T144208_8f3vm0k3_.bkp
List of Archived Logs in backup set 96
Thrd Seq Low SCN Low Time Next SCN Next Time
1 8 1675198 19-12-2012 14:38:25 1675365 19-12-2012 14:42:07
BS Key Type LV Size Device Type Elapsed Time Completion Time
97 Full 7.52M DISK 00:00:02 19-12-2012 14:42:11
BP Key: 97 Status: AVAILABLE Compressed: NO Tag: TAG20121219T144209
Piece Name: /fra/PROD/autobackup/2012_12_19/o1_mf_s_802449729_8f3vm2cc_.bkp
SPFILE Included: Modification time: 19-12-2012 14:36:30
SPFILE db_unique_name: PROD
Control File Included: Ckp SCN: 1675376 Ckp time: 19-12-2012 14:42:09
RMAN>
### PREPARING ENV
cp $ORACLE_HOME/dbs/orapwprod $ORACLE_HOME/dbs/orapwtspitr
cd $ORACLE_HOME/dbs
## Creating INIT from TSPITR Instance
vi inittspitr.ora
DB_NAME=prod
DB_UNIQUE_NAME=tspitr
CONTROL_FILES=/stage_area_tspitr/PROD/controlfile/control01.ctl
REMOTE_LOGIN_PASSWORDFILE=exclusive
COMPATIBLE =11.2.0
DB_BLOCK_SIZE=8192
memory_target=700M
streams_pool_size=100M
### creating stage area to deploy database
mkdir -p /fra/stage_area_tspitr/PROD
cd /fra/stage_area_tspitr/PROD
mkdir controlfile datafile onlinelog
#### RESTORING DATABASE TSPITR
export ORACLE_SID=tspitr
$ rman target /
RMAN> startup nomount
Oracle instance started
Total System Global Area 730714112 bytes
Fixed Size 2225088 bytes
Variable Size 553651264 bytes
Database Buffers 167772160 bytes
Redo Buffers 7065600 bytes
RMAN> restore controlfile from '/fra/PROD/autobackup/2012_12_19/o1_mf_s_802449729_8f3vm2cc_.bkp';
Starting restore at 19-12-2012 15:16:27
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=146 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/fra/stage_area_tspitr/PROD/controlfile/control01.ctl
Finished restore at 19-12-2012 15:16:31
RMAN> startup mount
database is already started
database mounted
released channel: ORA_DISK_1
### REPORT SCHEMA TO GET DATAFILE NUMBER TO BE RESTORED
RMAN> report schema;
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name TSPITR
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
1 700 SYSTEM *** +DS8000_DG/prod/datafile/system.349.799325249
2 600 SYSAUX *** +DS8000_DG/prod/datafile/sysaux.348.799325249
3 200 UNDOTBS1 *** +DS8000_DG/prod/datafile/undotbs1.347.799325251
4 5 USERS *** +DS8000_DG/prod/datafile/users.335.799325251
5 100 AUDIT_AUX *** +DS8000_DG/prod/datafile/audit_aux.287.799330083
6 0 SOE *** +DS8000_DG/tspitr/datafile/soe.368.802445265
7 100 XDB *** +DS8000_DG/prod/datafile/xdb.311.801410833
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
1 385 TEMP 32767 +DS8000_DG/prod/tempfile/temp.300.799325437
RMAN>
### GET LOGFILE NAME to RENAME to new location.
$ sqlplus / as sysdba
SQL> select member from v$logfile;
MEMBER
+DS8000_DG/prod/onlinelog/group_1.330.802352807
+DS8000_DG/prod/onlinelog/group_2.331.802352815
+DS8000_DG/prod/onlinelog/group_3.321.802352821
run {
set newname for datafile 1 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
set newname for datafile 2 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
set newname for datafile 3 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
set newname for datafile 7 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
set newname for datafile 6 to "+DS8000_DG";
restore datafile 1,2,3,7,6 from tag 'TAG20121219T143840' ;
switch datafile 1;
switch datafile 2;
switch datafile 3;
switch datafile 7;
switch datafile 6;
switch tempfile all;
set until time "to_date('19-12-2012 14:42:00','dd-mm-yyyy hh24:mi:ss')";
recover database SKIP TABLESPACE "USERS", "AUDIT_AUX" delete archivelog;
## Renaming ONLINELOG
sql "alter database rename file ''+DS8000_DG/prod/onlinelog/group_1.330.802352807'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group1.rdo''";
sql "alter database rename file ''+DS8000_DG/prod/onlinelog/group_2.331.802352815'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group2.rdo''";
sql "alter database rename file ''+DS8000_DG/prod/onlinelog/group_3.321.802352821'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group3.rdo''";
alter database open resetlogs;
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 19-12-2012 15:32:13
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSTEM_FNO-1
channel ORA_DISK_1: restoring datafile 00002 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSAUX_FNO-2
channel ORA_DISK_1: restoring datafile 00003 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-UNDOTBS1_FNO-3
channel ORA_DISK_1: restoring datafile 00007 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-XDB_FNO-7
channel ORA_DISK_1: restoring datafile 00006 to +DS8000_DG
channel ORA_DISK_1: reading from backup piece /fra/PROD/backupset/2012_12_19/o1_mf_nnndf_TAG20121219T143840_8f3vdn3q_.bkp
channel ORA_DISK_1: piece handle=/fra/PROD/backupset/2012_12_19/o1_mf_nnndf_TAG20121219T143840_8f3vdn3q_.bkp tag=TAG20121219T143840
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:12:35
Finished restore at 19-12-2012 15:44:48
datafile 1 switched to datafile copy
input datafile copy RECID=6 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSTEM_FNO-1
datafile 2 switched to datafile copy
input datafile copy RECID=8 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSAUX_FNO-2
datafile 3 switched to datafile copy
input datafile copy RECID=10 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-UNDOTBS1_FNO-3
datafile 7 switched to datafile copy
input datafile copy RECID=12 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-XDB_FNO-7
datafile 6 switched to datafile copy
input datafile copy RECID=14 STAMP=802453489 file name=+DS8000_DG/tspitr/datafile/soe.304.802452733
renamed tempfile 1 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-TEMP_FNO-1 in control file
executing command: SET until clause
Starting recover at 19-12-2012 15:44:49
using channel ORA_DISK_1
Executing: alter database datafile 4 offline
Executing: alter database datafile 5 offline
starting media recovery
archived log for thread 1 with sequence 8 is already on disk as file +DS8000_DG/prod/onlinelog/group_2.331.802352815
archived log file name=+DS8000_DG/prod/onlinelog/group_2.331.802352815 thread=1 sequence=8
media recovery complete, elapsed time: 00:00:02
Finished recover at 19-12-2012 15:44:55
sql statement: alter database rename file ''+DS8000_DG/prod/onlinelog/group_1.330.802352807'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group1.rdo''
sql statement: alter database rename file ''+DS8000_DG/prod/onlinelog/group_2.331.802352815'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group2.rdo''
sql statement: alter database rename file ''+DS8000_DG/prod/onlinelog/group_3.321.802352821'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group3.rdo''
database opened
## Exporting Tablespace Metadata
RMAN >
run {
sql 'alter tablespace SOE read only';
# create directory for datapump export
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''";
# grant on directory to SYSTEM
sql "grant read,write on directory TSPITR_DIROBJ_DPDIR to system";
# exporting metadata
host "expdp system/oracle@localhost:1521/tspitr DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_FULL_CHECK=Y TRANSPORT_TABLESPACES=SOE";
using target database control file instead of recovery catalog
sql statement: alter tablespace SOE read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''
sql statement: grant read,write on directory TSPITR_DIROBJ_DPDIR to system
Export: Release 11.2.0.3.0 - Production on Wed Dec 19 15:53:02 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, Oracle Label Security, OLAP,
Data Mining, Oracle Database Vault and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_TRANSPORTABLE_01": system/********@localhost:1521/tspitr DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_FULL_CHECK=Y TRANSPORT_TABLESPACES=SOE
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Processing object type TRANSPORTABLE_EXPORT/TABLE
Processing object type TRANSPORTABLE_EXPORT/INDEX/INDEX
Processing object type TRANSPORTABLE_EXPORT/INDEX/FUNCTIONAL_INDEX/INDEX
Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/INDEX/STATISTICS/FUNCTIONAL_INDEX/INDEX_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/REF_CONSTRAINT
Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
Master table "SYSTEM"."SYS_EXPORT_TRANSPORTABLE_01" successfully loaded/unloaded
Dump file set for SYSTEM.SYS_EXPORT_TRANSPORTABLE_01 is:
/fra/stage_area_tspitr/exp_transport_soe.dmp
Datafiles required for transportable tablespace SOE:
+DS8000_DG/tspitr/datafile/soe.304.802452733
Job "SYSTEM"."SYS_EXPORT_TRANSPORTABLE_01" successfully completed at 15:54:28
host command complete
## Stop Database and destroy it to make sure that Datafile 6 will not be used by this database;
RMAN>
run {
shutdown immediate;
## removing controlfile and SYSTEM Tablespace to make sure that database will not be opened
host "rm -f /fra/stage_area_tspitr/PROD/controlfile/control01.ctl /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSTEM_FNO-1";
database closed
database dismounted
Oracle instance shut down
host command complete
## TARGET Database
## Plugging Tablespace on TARGET database.
$ export ORACLE_SID=prod
$ rman target /
run {
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''";
# grant on directory to SYSTEM
sql "grant read,write on directory TSPITR_DIROBJ_DPDIR to system";
host "impdp system/oracle@localhost:1521/prod DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_DATAFILES=''+DS8000_DG/tspitr/datafile/soe.304.802452733''";
sql "alter tablespace soe read write";
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''
sql statement: grant read,write on directory TSPITR_DIROBJ_DPDIR to system
Import: Release 11.2.0.3.0 - Production on Wed Dec 19 16:09:30 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, Oracle Label Security, OLAP,
Data Mining, Oracle Database Vault and Real Application Testing options
Master table "SYSTEM"."SYS_IMPORT_TRANSPORTABLE_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TRANSPORTABLE_01": system/********@localhost:1521/prod DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_DATAFILES=+DS8000_DG/tspitr/datafile/soe.304.802452733
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Processing object type TRANSPORTABLE_EXPORT/TABLE
Processing object type TRANSPORTABLE_EXPORT/INDEX/INDEX
Processing object type TRANSPORTABLE_EXPORT/INDEX/FUNCTIONAL_INDEX/INDEX
Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/INDEX/STATISTICS/FUNCTIONAL_INDEX/INDEX_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/REF_CONSTRAINT
Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
Job "SYSTEM"."SYS_IMPORT_TRANSPORTABLE_01" successfully completed at 16:10:03
host command complete
sql statement: alter tablespace soe read write
### Recompiling Invalid Objects and Checking objects from tablespace SOE
$ sqlplus / as sysdba
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
TIMESTAMP
COMP_TIMESTAMP UTLRP_BGN 2012-12-19 16:10:34
OBJECTS WITH ERRORS
0
ERRORS DURING RECOMPILATION
0
Function created.
PL/SQL procedure successfully completed.
Function dropped.
PL/SQL procedure successfully completed.
SQL> select count(1) SEG_COUNT from dba_segments where tablespace_name='SOE';
SEG_COUNT
32
SQL> SELECT COUNT(1) OBJ_INVALID FROM DBA_OBJECTS WHERE STATUS != 'VALID';
OBJ_INVALID
0
## PERFORM A FULL BACKUP AFTER RESTORE TABLESPACE.Regards,
Levi Pereira -
Raw device for oracle 8.1.7 on AIX 4.3.3
Hi there,
I am trying to use a raw device on AIX 4.3.3 for ORACLE 8.1.7.
I have created a raw device /dev/or_system
brw-rw---- 1 oracle dba 54, 1 Mar 04 10:44 or_system
but it is not possible to create a datafile on it :
SVRMGR> create database "GLM"
maxinstances 8
character set "WE8ISO8859P1"
datafile '/dev/or_system' size 150M REUSE
logfile
GROUP 1 ('/oracle/GLM/redo/log1.ora') size 100M,
GROUP 2 ('/oracle/GLM/redo/log2.ora') size 100M,
GROUP 3 ('/oracle/GLM/redo/log3.ora') size 100M,
GROUP 4 ('/oracle/GLM/redo/log4.ora') size 100M;
create database "GLM"
ORA-01501: CREATE DATABASE failed
ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 407
ORA-00604: error occurred at recursive SQL level 1
ORA-01119: error in creating database file '/dev/or_system'
ORA-27038: skgfrcre: file exists
SVRMGR>
The ORA-27028 in exact this situation was reported as a bug in prior ORACLE Versions 8.0.4/ 8.0.5 and had
the bug no. 690228.
But we use as mentioned 8.1.7.
What do I do wrong?
Any suggestions are welcome.
Thank you
GerhardEach raw device you create is used as a single data file.
Eg mklv -y 'myfile' <vgname> <number of logical partitians>
Will have two special files associated with them /dev/rmyfile and /dev/myfile. The number of logical partitians will be the size of your datafile subtract 1 meg for overhead.
So, if you were addding the above raw volume to a tablespace, and the lp size was 32 meg, you would
create tabelspace tsname datafile '/dev/rmyfile' size 31 m;
Note the use of rmyfile not myfile. -
How to create DIR/File on a raw device in RAC environment.
Hi all,
I use a shell script to create DIR and File on a raw device also it creates schema and tablespaces.
I am facing problem in creating DIR and Files on raw device.
One more thing, can multiple tablespaces be created on a raw device.
Thanks & regards,
SanjeevThanks for the response. Please help me further.
About the Script - It asks for the path for creating DIR and uses shell command to create DIR. Later same path and DIR name is used to create Oracle DIR. Now in place of absolute path raw device name is passed. The same script is also used for creating tablespaces and schema.
There is second script that is .sql script that creates external table in the newly created schema. All this has been working fine on single instance Oracle server. we have tested many times but fails in RAC environment when we use raw device.
Question is - If I use filesystem will the external table's flat files and Directories be accessible to all the instances.
I have one application written in java that would be clustered and running on these oracle servers. This application would be accessing those external tables and their flat files. Will there be a problem accessing these flat files accross the instances.
Regards,
Sanjeev. -
Good morning,
I would like to make some i/o test with a database version 10g, actually I have the redo log on standard zfs filesystem (cooked), I would like to
migrate this redo log on raw device without recreating the database, is this possible ?
Thanks for your help
Fabrice ChapuisOne more question, in case of node failure , redo on raw device are more critical for a recover than if they were on a filesystem ?More critical? Or more difficult?
Redo is critical, period. Does not matter whether you use a cooked file system or a raw device.
As for difficulty - that depends on what you are attempting to do. If you want to treat the raw device as a file system, that will be difficult as it it not a file system. (which kind of begs the question as to treat it like a file system when it is not?)
From a RMAN perspective - a device is a device. RMAN does not care.
From a DB perspective - that is why ASM exist. To remove the complexities of using raw devices, and eliminate the requirement of needing to use an external Volume Manager. And provide the DBA with a familiar SQL*Plus interface and SQL commands to administer ASM.
It may seem difficult at first - but anything that needs a learning curve to go through, tends to seem difficult in the beginning. All you need to do is learn the basics and grasp the concepts.. and that +"difficulty"+ disappears.
Maybe you are looking for
-
Nokia E75 does not support sis files
I've been trying to upgrade the Ovi maps on my E75, because navigation has kept me saying that I need to renew the license. I went to Nokia web site and found out that I need to upgrade Ovi maps in order to get the free navigation. I have a 202.12.01
-
Hi all, I need to print currency field in Cheque layout. It is showing million format. For ex: 999,999,999.00. But i need to print it as 99,99,99,999.00. This is Indian rupees format. Dont forget, This is to print in SAP script not in report pro
-
Question on Transport level acknowledgment
Hi all, I use an acknowledgment at transport level in a send step of a BPM, to send an IDoc to a R/3 system. I have seen that when PI sends a lot of IDocs to R/3 from multiple BPMs in a short time, transport acknowledgments are not sent when R/3 rece
-
Create a glossary/element index in WebCenter Portal
I need to create a glossary/element index like this in WebCenter Portal. Do you know if exists any ADF/Trinidad element to do this? Thank you
-
Hi, I'd be really grateful if someone could help me with this as its beginning to drive me insane!! I have a mac mini 10.5.8 and an iphone 4 that I would really like to synchronize which I understand I have to do through icloud. But, from what I ca