Oracle Database Disaster Recovery SAN replication consistency

Hi all

just a quick question after a long search and not yet knowing the answer.

What technology or configuration do I need make the eve of Oracle DB compatible on asynchronous SAN replication between cities?

The version is Oracle Standard Edition 11 g, then the enterprise like DataGuard and GoldenGate features aren't possible?

Entire database replication Oracle Streams don't work?

Hello

You can do it yourself (as everyone else used to do many years ago), to a product like dbvisit which is popular in this space (never used, but I heard good things about this). Streams can do it, but I think he uses triggers rather than redo log mining so he can have more impact on the source system.

SAN replication is possible but probably very expensive and you should be sure it correctly handles oracle blocks - the seller must be able to tell if it is certified or not.

See you soon,.

Rich

Tags: Database

Similar Questions

  • Disaster recovery with replication for VSphere

    Am just test VSphere 5 of replication. with a couple of test VMs

    The replication process works very well

    What I want to know is the process to recover a VM replicated to new hardware in the case of the complete failure of the original host and/or data store

    In essence, disaster recovery.

    Are there other parts (software), that I need to take the replica VMDK and files related to re - create a new virtual machine on a new host

    Steve

    Yes, because it will be all your hard and .vmx files.

  • vCloud Air Disaster Recovery - vSphere replication of specific records

    In the most recent documentation for vSphere replication, the ability to select specific disks when you replicate a single workload is described:

    Documentation Centre of vSphere 5.5

    However, in the videos of vCloud Air DR, this option is not currently available. Is - this specific to Air DR vCloud or some videos of previous versions?

    vCloud Air Disaster Recovery: configuration of the Virtual Machine replication - YouTube

    Answer: No.

    http://vjourneyman.com/replicating-to-vCloud-air-Dr

  • Is it possible to install oracle fail-safe-kind-of (active-passive) SAN replication for oracle?

    Dear Experts,

    Is it possible to configure replication of SAN (active-passive) integrated security for oracle for oracle?

    To get the RTO < 60 seconds

    • If the primary host fails, the remote site should have the option to start the oracle database.
    • Sites are geographically remote.

    SAN storage replication, can it be used in my scenario?

    • I have no option to implement oracle Data Guard as its very expensive.

    Is that what someone achieved something similar with SAN storage replication?

    • I have oracle SE.
    • It is obvious that the all-flash backup can be quick.

    What should be the strategy to have DR site get a few seconds, if the primary site failed for some reason any

    • Daily incremental backup with RMAN. And archive backup runs for every 1 minutes
    • To have the site of DR upward and running within 60 seconds, it still requires too much time to restore the database on remote site and have archive APPLIED setpoint
    • What could be the solution with san replication? RTO is 60 seconds

    Thanks and greetings

    SAN storage replication, can it be used in my scenario?

    I have no option to implement oracle Data Guard as its very expensive.

    --> If you want to use the data that it is free of CHARGE, additional license is not required for normal data guard

    --> additional license is only for the ADG

    Is that what someone achieved something similar with SAN storage replication?

    I have oracle SE.

    It is obvious that the all-flash backup can be quick.

    --> Here, I understand that if oraclle EA is going to be expensive

    --> Again, you can use manual standby

    --> What you are looking for SAN replication, you will need to check with the storage vendor

    --> If your intention is to check with oracle storage, then this may be the correct discussion room

    What should be the strategy to have DR site get a few seconds, if the primary site failed for some reason any

    Daily incremental backup with RMAN. And archive backup runs for every 1 minutes

    To have the site of DR upward and running within 60 seconds, it still requires too much time to restore the database on remote site and have archive APPLIED setpoint

    What could be the solution with san replication? RTO is 60 seconds

    --> If your intention is to check with oracle storage, then this may be the correct discussion room

    Check in this

    https://community.Oracle.com/community/Server_%26_storage_systems/storage

  • Script the replication consistency AD AD partner operations master Client-side Test database has not finished

    Why the alerts listed below is generated? What is the cause of this and the resolution?

    1 script the replication consistency AD AD partner operations master Client-side Test database has not finished
    2 could not determine the FSMO role holder
    3. overall the status of essential Services
    4. all replication partners failed to replicate.
    5. the report of chess AD Machine account has authentication of data
    6. registration of DNS of essential domain controller records is failing
    7 AD Site Performance Health Rollup monitor
    8 AD Site availability health Rollup monitor
    9 AD domain availability health Rollup monitor
    10 field Performance Health Rollup monitor
    Please someone help me to get the Exact details, Cause and resolution of these. These all relate to an AD alerts generated in SCOM

    Hi Nimit Kumar,

    You try to post your question here for assistance:

    http://social.technet.Microsoft.com/forums/en-us/home

    Thank you.

  • 3rd party such as san replication solution: strategy

    Dear Experts,

    Can you please share some of your ideas.

    Oracle DataGuard comes free with Oracle Enterprise Edition (EE). The only reason why a company could NOT use Oracle DataGuard is because they are not on the ERA and the cost of upgrading to EE just to use DataGuard does not justify the price.

    With 3rd party such as san replication solution. (for example hp3par)

    It is obvious that the all-flash backup can be quick.

    What should be the strategy to have DR site get a few seconds, if the primary site failed for some reason any

    1. daily incremental backup with RMAN. And archive backup runs for every 1 minutes

    2. so that the DR site facing up and running within 60 seconds, it still requires too much time to restore the database on remote site and have archive APPLIED setpoint

    What could be the solution with san replication? RTO = 60 seconds

    Thanks ivw

    Hello

    Great topic, I'll try to summarize all this in a post.

    I have worked with HP EVA for a few years and I must say that I have used many of the features of replication - HP EVA Business Copy (local replication) and HP EVA continues access (remote replication) as well - for the oracle database and other applications as well. Most storage systems use copy-on-write to create two points in time of the LUN (snapshot) image or clone LUN using cow again.

    Of course, like other people, said earlier the replication SAN is block based, in the same way with Dataguard, you have synchronous and asynchronous replication. When your data is written to the data files it usually goes in storage cache and then is pushed down the disc as soon as it will be more efficient, at the same point, replication is pushing data to the Dominican Republic. The same way with Dataguard if you use synchronous replication that you won't get you "speedy return" until the blocks of primary storage has been written for DR storage system.

    I never had problems with replication to be honest. I used a lot of copy of databases of production using local replication. For example if you want to quickly test a patch on the production system, you can create a snapshot that will only increase with the amount of changes you have made. The only concern is nowadays though we use ASM so if your diskgroup names are the same in DEV that the PROD does not work the approach that I mention.

    Regarding remote replication - because you do not have Dataguard more every time you failover to the Dominican Republic to your database will pass by instance recovery!

    Regardless of the type of replication is not the speed but the latency of the network - SAN or Dataguard, you will always have a penalty of a long replication distance. The biggest typical WAN latency factor is the speed of light, via fiber optic cable, which is about 124 miles per millisecond. Based on that you can calculate what would be the round-trip latency time.

    Indeed for many people SE installation choose DBvisit Standby to manage their databases on hold. I did the installation of the couple and it is really simple and works out of the box. However, your RPO depends on how often you switch your redologs and how many times you ship them to the backup site. You must configure dbvisit to spend with each log file (all the 5,10,15 minutes) OR configure archive_lag_target to configure OR use both at the same time. Also, you can store a copy of the archivelogs on a separate location just in case, for example, an NFS share.

    And finally my five cents on RAC on Clusters of extended - be careful with this one. Each of the nodes in the extended database cluster need access to both storage (primary and DR) systems. You must also third location to store a voting quorum disk, usually an NFS share. It is also very important to note that the latency between the nodes is of crucial importance due to global cache activity.

    Kind regards

    EVS

  • SAN replication for fault tolerance

    Hello world

    I hope that someone could point me in the right direction - it seems that I do not have enough review in the subject and the deadlines are too tight for me to explore different scenarios in depth...

    We have two data centers a few miles of each other connected by 100 Mbps link. Each datacenter will have 5 blades BL490 with ESX Standard accommodation about 50 VMs. ABC message a HP eva4400 SAN with SAN replication implemented. VC will be the first data center and the two data center are networked.

    SAN replication is block-level, so it seems that I can not just replicate changes, but all entries will have to be replicated. This should not be a problem because the link can support about 1.8 TB a jouret of data can be buffered.

    I am not however a vision how recovery would work in this case. We don't need instant recovery, I would say that 4 hours of recovery time is accepted if SRM fancy Automatic as DR scenario would not easily be accepted financial reasons, but your comments are welcome.

    Current idea is the following: replicate LUNS of primary site to the secondary. When disaster strikes, personal COMPUTER turns on the ESX host on the remote side and connects replicated LUNS, and then registered VMs and change my IP address.

    I understand that this seems horribly manual process and I'm pretty sure I missed some obvious pitfalls here.

    Could someone let me know which direction should I go? An article on the subject?

    This is a new installation and we prefer to put in place the basic recovery process and resize it later. I just need to have a good direction to allow this scalability.

    I thank very you much in advance!

    I think you have a good understanding of how it should work it is something I would like to implement, but use Veeam as support for replication. Here's what I would do for the IP addresses of the virtual machine. I like to keep the same IP addresses because I know that not every simple VM uses DNS for all of its applications, databases, etc. So unless you are POSITIVE you covered all the basics of your DNS, I'll try to use the same IP addresses. You just work on the part of this routing before start you your virtual machines. So make sure that when switch you or test your virtual machine failover, you make sure that if you have a virtual machine with the IP 10.10.10.10 with two Datacenters A & B, the routing would ensure that all your customers cannot talk to the datacenter B until you do this active way. In this way, you can test your failover

  • Problem with different ASM disaster recovery start - new

    Hello together,

    I had an old net here about it but now will not solve the problem with the points in the old thread. Here's the old: https://community.oracle.com/thread/3608049?start=0 & tstart = 0

    I'm doing a disaster recovery with the 'apex11A' on a new server database, which has an another ASM starts. The old man starts is '+ DGA112_1' and '+ FRA112_1', newcomers are called '+ DATA_QUM169' and '+ FRA_QUM169 '. I changed the settings in the spfile restored by writing in a pfile file and creating the spfile from pfile.

    I tried in several ways. First lay the new ASM with RMAN to the course:

    run
    {
    SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
    restore database until LOGSEQ 24286;
    switch datafile all;
    switch tempfile all;
    recover database until LOGSEQ 24286;
    }
    

    Then I tried it in RMAN by defining the new ASM for each data file:

    run
    {
    SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
    restore database until LOGSEQ 24286;
    switch datafile all;
    switch tempfile all;
    recover database until LOGSEQ 24286;
    }
    

    Then I tried the bot in one:

    run
    {
    SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
    restore database until LOGSEQ 24286;
    switch datafile all;
    switch tempfile all;
    recover database until LOGSEQ 24286;
    }
    

    Whenever I get one

    Starting restore at 03-FEB-16
    using channel ORA_DISK_1
    
    
    creating datafile file number=1 name=+DATA_QUM169
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/03/2016 16:20:41
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'
    

    The backuppiece which I bring are correctly defined with

    RMAN> catalog backuppiece '/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1', '/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1';
    
    
    cataloged backup piece
    backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1 RECID=3779 STAMP=902851052
    cataloged backup piece
    backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1 RECID=3780 STAMP=902851052
    
    
    RMAN> list backup;
    
    
    
    
    List of Backup Sets
    ===================
    
    
    
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    3779    52.61M     DISK        00:00:00     03-FEB-16
            BP Key: 3779   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145340
            Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1
    
    
      List of Archived Logs in backup set 3779
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    24285   11073415926066 03-FEB-16 11073416327345 03-FEB-16
      1    24286   11073416327345 03-FEB-16 11073416678326 03-FEB-16
    
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    3780    Full    813.86M    DISK        00:00:00     03-FEB-16
            BP Key: 3780   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145042
            Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1
      List of Datafiles in backup set 3780
      File LV Type Ckp SCN    Ckp Time  Name
      ---- -- ---- ---------- --------- ----
      1       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/system.1423.788355253
      2       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/sysaux.1422.788355259
      3       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/undotbs1.1359.788355263
      4       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/users.1362.788355273
      5       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4.1369.788356305
      6       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4_files.1366.788356317
      7       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms_archiv.1358.788357229
      8       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/planwerte.1357.788357243
      9       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_prod.1352.788456613
      10      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais.1353.788456763
      11      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms.1354.788456995
      12      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/externe_wirk.1355.788457525
      13      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2mt.1356.788458151
      14      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_read.1351.788458291
      15      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329
      16      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657
      17      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/macmon.1340.788458691
      18      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais_read.1339.788458725
      19      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2srm.266.788458799
      20      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859
      21      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/quickcheck.1338.788458887
      22      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/switch.1337.788459139
      23      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/veit_r.1333.788459167
      24      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/test-btdb.1298.795097725
      25      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11dev.986.874230931
      26      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11devbt.985.874230963
      27      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hrbew.1083.851007823
      28      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/optimadata.1032.865951029
    

    I also tried to put the new ASM SQL:

    SQL*Plus: Release 11.2.0.4.0 Production on Wed Feb 3 16:04:05 2016
    
    
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.
    
    
    
    
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
    With the Partitioning, Automatic Storage Management and OLAP options
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 1 - new file '+DATA_QUM169' not found
    ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 2 - new file '+DATA_QUM169' not found
    ORA-01110: data file 2: '+DGA112_1/apex11a/datafile/sysaux.1422.788355259'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 3 - new file '+DATA_QUM169' not found
    ORA-01110: data file 3: '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 4 - new file '+DATA_QUM169' not found
    ORA-01110: data file 4: '+DGA112_1/apex11a/datafile/users.1362.788355273'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 5 - new file '+DATA_QUM169' not found
    ORA-01110: data file 5: '+DGA112_1/apex11a/datafile/apex4.1369.788356305'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 6 - new file '+DATA_QUM169' not found
    ORA-01110: data file 6: '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 7 - new file '+DATA_QUM169' not found
    ORA-01110: data file 7: '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 8 - new file '+DATA_QUM169' not found
    ORA-01110: data file 8: '+DGA112_1/apex11a/datafile/planwerte.1357.788357243'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 9 - new file '+DATA_QUM169' not found
    ORA-01110: data file 9: '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 10 - new file '+DATA_QUM169' not found
    ORA-01110: data file 10: '+DGA112_1/apex11a/datafile/mais.1353.788456763'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 11 - new file '+DATA_QUM169' not found
    ORA-01110: data file 11: '+DGA112_1/apex11a/datafile/mms.1354.788456995'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 12 - new file '+DATA_QUM169' not found
    ORA-01110: data file 12:
    '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 13 - new file '+DATA_QUM169' not found
    ORA-01110: data file 13: '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 14 - new file '+DATA_QUM169' not found
    ORA-01110: data file 14: '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 15 - new file '+DATA_QUM169' not found
    ORA-01110: data file 15: '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 16 - new file '+DATA_QUM169' not found
    ORA-01110: data file 16: '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 17 - new file '+DATA_QUM169' not found
    ORA-01110: data file 17: '+DGA112_1/apex11a/datafile/macmon.1340.788458691'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 18 - new file '+DATA_QUM169' not found
    ORA-01110: data file 18: '+DGA112_1/apex11a/datafile/mais_read.1339.788458725'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 19 - new file '+DATA_QUM169' not found
    ORA-01110: data file 19: '+DGA112_1/apex11a/datafile/mais2srm.266.788458799'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 20 - new file '+DATA_QUM169' not found
    ORA-01110: data file 20:
    '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 21 - new file '+DATA_QUM169' not found
    ORA-01110: data file 21: '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 22 - new file '+DATA_QUM169' not found
    ORA-01110: data file 22: '+DGA112_1/apex11a/datafile/switch.1337.788459139'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 23 - new file '+DATA_QUM169' not found
    ORA-01110: data file 23: '+DGA112_1/apex11a/datafile/veit_r.1333.788459167'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 24 - new file '+DATA_QUM169' not found
    ORA-01110: data file 24: '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 25 - new file '+DATA_QUM169' not found
    ORA-01110: data file 25: '+DGA112_1/apex11a/datafile/apex11dev.986.874230931'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 26 - new file '+DATA_QUM169' not found
    ORA-01110: data file 26: '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 27 - new file '+DATA_QUM169' not found
    ORA-01110: data file 27: '+DGA112_1/apex11a/datafile/hrbew.1083.851007823'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 28 - new file '+DATA_QUM169' not found
    ORA-01110: data file 28: '+DGA112_1/apex11a/datafile/optimadata.1032.865951029'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    

    But my new database will not set the new ASM and I have no why.

    The db_create_file_dest parameter is set correctly, so I think that:

    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    db_create_file_dest                  string      +DATA_QUM169
    

    I forgot something? Would be nice to get help ...

    A big thank you and best regards,

    David

    Your data checkpoint SCN file are in the LOW and HIGH range of the SNA for SEQUENCE 24286.

    Therefore, your UNTIL clause should be 24287 SEQUENCE up to THAT.

    Hemant K Collette

  • OBIEE Disaster Recovery can be configured without CARS and shared storage?

    Hi people,

    As say the topic, I'm looking for advice on disaster recovery. What I find in the docs pointing me to the high availability configuration, or maybe I'm simply not find the docs I'm looking for. And it always points to the RAC, etc. of shared storage. My database is already configured to Dataguard and I want to do things this way, with a recovery site which isn't always upwards and a part of a cluster (although it's very well as long as the CAR is not involved), I'm looking for some feedback on how people do things. I have 11.1 now, but will be upgrading to 12.2 soon.  Just a straight stitch to the documentation would be useful if I'm missing just that.

    Thank you

    -Adam

    Since you have already configured Dataguard and in a DR situation, you will be switching/switch on your course in standby mode and it will active db. All this is fine. You can do the same with instances of weblogic OBIEE. You can clone your binaries installed using tools provided by Oracle cloning, or build binaries from weblogic with the accurate determination of drive on your Dr. use the pack of weblogic server and then unzip tool to archive your entire weblogic domain and it Unarchive in your prepared DR server.

    Now, you have to just challenge the hostname (s) of your domain to point to your database JDBC data sources and weblogic.

    To facilitate the task, you can change the host name used by weblogic to host alias that can be remapped in DNS during DR. Similarly, you can change the JDBC connection string so that it can automatically select the active database as long as you use a database instead of a SID service name in the connection string.

    You will need to regularly make a pack on your weblogic domain in order to maintain an up-to-date backup of your domain proximity. Similarly, if you have reports that are stored on the file system, they must also be backed up regularly so that they can be restored.

  • Proposal Setup infrastructure - Oracle database, LDAP, Weblogic Server, part operational

    Hello Experts!

    First of all, until I opened this topic I tried to search for similar positions that can hold at least part of the necessary information for me. This topic is that most related to the architecture of the whole system in the sense of the application that contains a part of database (oracle with data models database), the operational part (unix scripts called from the web interface), weblogic server where MS Java application runs and the last part is LDAP Setup for supported LDAP grups.

    Currently confirmed architecture is for me unacceptable from the point of view of dorsal because everything would be installed on the same physical server (physical machine). From my point of view, there should be at least 3 physical separate servers:

    (1) Server database where the Oracle database is installed (say ommit backup and disaster at this stage recovery)

    (2) operation of servers shared between several applications to manage operational tasks and application configurations

    (3) separate server for Weblogic server, the LDAP server and Java application is

    Given that 2 points are obvious to me and I provided them with really simplified form then 3. is not entirely clear to me mainly due to the fact that I am the architect of solution for datawarehausing, not for applications based on J2EE.  Under the following link:

    webloic Oracle server needs a server infrastructure

    I just read to support failover and balancing I should have two different boxes physical and Weblogic software installed on each of them. I know not so so many separate for the 3rd point above mentioned how boxes I need. I would appreciate if you can share your thoughts on this subject by considering the following points:

    -scalability (1000 users at the same time)

    -further development

    -maintenance

    -installation costs

    If you can guide also links to cover this topic, I'd be more than happy

    Thanks in advance!

    Kind regards

    Bolo


    Hi Bolo

    Here's WDM of Oracle Identity management includes the installation of OID:

    Content

    I'm sorry for the confusion.

    I meant "General guidelines of architecture of say that you should keep the boxes", for example: LDAP must be in another box of WLS, also database must be in a different area, this isn't really something related to Oracle products, it is only related to the definitions of architecture.

    WebLogic Server at the end being that a java application is running in the virtual machine JAVA, WLS should run in the same box as the JVM as it comes to a unit in terms of functionality.

    Best regards

    Luz

  • Need help in the migration of windows 2003 server Oracle database server 2012

    Hello

    My environment is oracle database 9i in windows server 2003, we want to move to Windows 2012 since the end of support for windows 2003.

    Please give me a plan, what no need to make the first database upgrade or upgrade of windows, what are the things will have to be considered at the level of Oracle database?

    Any help would be appreciated.

    Thank you

    Lherault

    Hello

    Given the version of your database is 9.2.0.8 and you want to upgrade to 11.2.0.4 and 9i database is running with log mode archive

    I have plan.

    (1) your database 9i working with the log mode archive Server 2003

    (2) you can take backup of Database 9i with RMAN

    (3) you can restore the backup to the base in 2008 (by using 11.2.0.4 software)

    (4) when the recovery is complete, you can open the database with resetlogs option upgrade.

    change the upgrade of open database resetlog.

    (5) once the database is open, you can run 'Upgrade PROCESS'

    (6) it should complete your upgrade in 2008

    If you think, restoration and recovery will take time, so you can install physics Eve with 11.2.0.4 version in 2008 for the Database 9i.

    During failover, you can recreate the controlfile and open the database ' change the upgrade of database open resetlog. "

    you will need to check the compatibility with the help from under documents

    Reference list Oracle database upgrade (Doc ID 730365.1)

    Note 551141.1 : Server Upgrade/Downgrade Compatibility matrix data base

  • Linux and oracle database installation best practices windows

    can anyone recommend the guide of best practices for the installation/design of windows/Linux oracle database servers.

    Microsoft, sql Server, provide a number of useful resources on the evolution of the default parameters that can die of hunger the operating system of resources, where to and where not to store the data in files/logs etc etc, but I've yet to find a similar guide for Oracle. Research on best practices during the installation/initial design in order to avoid the risk of recovery/redundancy later on any line, reliability, availability, performance. Guidance most welcome.

    See following note metalink on system requirements for the different versions:

    (Doc ID 169706.1) - database Oracle (RDBMS) Unix AIX, HP - UX, Linux, Mac OS X, Solaris, Tru64 Unix OS Installation and Configuration requirements checklist (8.0.5 to 11.2)

    Online Oracle Database Documentation 11g Release 2 (11.2)

    -Som

  • Server problems of Oracle database since the upgrade to 5.5 Update 2

    Hello world

    Reach out to see if someone else can meet the same problems we are experiencing. Since his arrival at 5.5 to day 2 5.0, we have experienced some problems with our servers, Oracle Database 11.2 running on Oracle Linux 6.2.  Nothing really the consistency between the question, brief description of what we had problems, we had 2 VMS are inaccessible, another who froze this necessary and the most recent reset which displays the virtual machine entered mode isolated, requiring a person to get on the console to access the network.  Before the upgrade, these virtual machines have been broadcast for years without any problem. The only common denominator issues is the upgrade to ESX 5.5 Update 2. Any input would be really appreciated.


    Thank you

    Ken

    Hello world

    In collaboration with HP and VMware, we believe that we have narrowed it down to the question of the 554FLB firmware and driver adapter, have updated and environments have been stable, we keep our fingers crossed.

    Kind regards

    Ken

  • SRM 5.0 protect VM with oracle database

    Hi all

    l don't know if SRM 5.0 can use vSphere replication to protect VM with oracle database, please advise kindly. Thank you!

    If your Oracle DB Don t use physical RDM´s, you can use the vSphere replication.

    Kind regards

    Mario

  • Record great shape data in the Oracle database

    Hi all

    I have a question as to how we store a large xml for example more than 10000 bytes in the oracle database. I tried to use varchar, but the length is limited to only 4000 bytes. Could someone let me know how to achieve this.

    Basically what I'm doing is in adobe livecycle workflow I will get the user entered data in the form as formData (xml) variable and I want to keep the same for any future reference. I need to use the same data to fill the form again in the future.

    Thanks in advance.

    Shekhar,

    I had handy MySQL, so I did it using that and attached here is a sample. For Oracle, this is mission for you as well as recovery.

    -Wasil

Maybe you are looking for