RMAN writes two destined for archiving

Similar Questions

• Secondary destination for archived logs

  Version: 10.2, 11.1, 11.2
  
  Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?
  
  I think that LOG_ARCHIVE_DEST_2 is reserved for archiving to Dataguard standby DB logs in which specify you the day before tns input using the parameter of the shipping SERVICE.
  
  Can I specify LOG_ARCHIVE_DEST_3 as my secondary site in case LOG_ARCHIVE_DEST_1 saturates? -What is LOG_ARCHIVE_DEST_n meant for? Even though the documentation says that you can have up to 10 locations, I'm confused, if they are intended to store copies of archive logs multiplex? This is not what I'm looking for?

  >

  Hi Tom,

  Occasionally, we get "archiver error" on our production because of our satiety LOG_ARCHIVE_DEST_1 DBs. How
  can I have a secondary for archiving logs location where my position "primary" (LOG_ARCHIVE_DEST_1) saturates?

  From [https://forums.oracle.com/forums/thread.jspa?threadID=1033460 url] here:

  LOG_ARCHIVE_DEST_STATE_n = ALTERNATE
  To specify the nth destination metnioned in the LOG_ARCHIVE_DEST_n as a destination alternative.

  Look at "replacement" [url http://docs.oracle.com/cd/E14072_01/server.112/e10595/archredo004.htm] here - if all else fails, read the docco ;)

  Also check out here [url http://docs.oracle.com/cd/B10501_01/server.920/a96521/archredo.htm].
  HTH,

  Paul...

• Two destinations for Syslog

  Is it possible to set up a second IP to Syslog destination on an ESXi 4.0 server address. I read that ESXi on supports a single destination, however, I also read that a work-around has been put in place a syslog relay. If a second destination is possible, is it supported by VMware, and someone can share with me the steps on how to set up? Thank you...

  As far as I know that a single destination is possible with ESXi.  You need to configure a Repeater on a different host to forward syslog messages to multiple receivers.

  Dave

  VMware communities user moderator

  Forum - VMware communities forums upgrade notice will be upgraded the weekend of December 12.  The forum will be in playback mode only the Friday 10 December 18: 00 PST until Sunday December 12 2 AM PST.

  Now available - vSphere Quick Start Guide

  You have a system or a PCI with VMDirectPath?  Submit your specifications to Officieux VMDirectPath HCL.

• RMAN-06025: no log backup archived for thread 1 with sequence - on double

  I tried to make a duplicate of a database, something I have done before, but this time I have run in to a problem.

  So, make a

  RMAN > list archivelog all;

  Shows that I have log sequence numbers 2600-2862 available.

  I have removed the expired archive logs and made an overlap and have issued the order on «alter system current archivelog» DB

  I did the pfile file and open the destination DB in nomount.

  The backup of the DB and the archivelogs seems to work fine without error.

  RMAN > backup as backupset = compressed database format ' / u04/tmpback/%u' tag "CLONE_TO_PPRD" include current controlfile;

  RMAN > backup as backupset archivelog Tablet all format = ' / u04/tmpback/al_%u' tag "CLONE_TO_PPRD_AL".

  Thus, with the environment on the destination DB (PPRD), opening a new rman to make the duplicate... "' rman target auxiliary sys@source_db /" "

  Then run the command

  target database duplicate to the PPRD until the SNA 2538794790;

  It seems to work fine, until this...

  Instance Oracle to close

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of the command duplicate Db at 30/10/2014 14:46:22

  RMAN-05501: abandonment of duplicate target database

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06053: unable to perform the recovery of the media because of the missing journal

  RMAN-06025: no backup log archived for thread 1 with sequence 2599 and YVERT departure from 2500202517 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2598 and YVERT departure from 2500201335 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2597 and YVERT departure from 2500102904 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2596 and YVERT departure from 2499995595 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2595 and YVERT departure from 2499836289 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2594 and YVERT departure from 2499642775 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2593 and YVERT departure from 2499478641 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2592 and YVERT departure from 2499413468 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2591 and YVERT departure from 2499410632 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2590 and YVERT departure from 2499408867 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2589 and YVERT departure from 2499381186 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2588 and YVERT departure from 2499068021 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2587 and YVERT departure from 2498925555 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2586 and YVERT departure from 2498802786 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2585 and YVERT departure from 2498614939 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2584 and YVERT departure from 2498564861 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2583 and YVERT departure from 2498562153 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2582 and YVERT departure from 2498561088 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2581 and YVERT departure from 2498484636 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2580 and YVERT departure from 2498271487 found to restore

  RMAN-06025: no backup log archived for 1 with sequence 2579 threads and YVERT departure from 2498214991 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2578 and YVERT departure from 2498212309 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2577 and YVERT departure from 2498211201 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2576 and YVERT departure from 2498136750 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2575 and YVERT departure from 2498007880 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2574 and YVERT departure from 2497940390 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2573 and YVERT departure from 2497937659 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2572 and YVERT departure from 2497935694 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2571 and YVERT departure from 2497906173 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2570 and YVERT departure from 2497856983 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2569 and YVERT departure from 2497596547 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2568 and YVERT departure from 2497456509 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2567 and YVERT departure from 2497319931 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2566 and YVERT departure from 2497256972 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2565 and YVERT departure from 2497254201 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2564 and YVERT departure from 2497252909 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2563 and YVERT departure from 2497193527 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2562 and YVERT departure from 2496934735 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2561 and YVERT departure from 2496745593 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2560 and YVERT departure from 2496657121 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2559 and YVERT departure from 2496603411 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2558 and YVERT departure from 2496600720 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2557 and YVERT departure from 2496599649 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2556 and YVERT departure from 2496488543 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2555 and YVERT departure from 2495585865 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2554 and YVERT departure from 2495399778 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2553 and YVERT departure from 2495269888 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2552 and YVERT departure from 2495267113 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2551 and YVERT departure from 2495264943 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2550 and YVERT departure from 2495263264 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2549 and YVERT departure from 2495032426 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2548 and YVERT departure from 2494891192 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2547 and YVERT departure from 2494748475 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2546 and YVERT departure from 2494688135 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2545 and YVERT departure from 2494685342 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2544 and YVERT departure from 2494684167 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2543 and YVERT departure from 2494617350 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2542 and YVERT departure from 2494441823 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2541 and YVERT departure from 2494219188 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2540 and YVERT departure from 2494146694 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2539 and YVERT departure from 2494143651 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2538 and YVERT departure from 2494141374 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2537 and YVERT departure from 2494140316 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2536 and YVERT departure from 2494039070 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2535 and YVERT departure from 2493969002 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2534 and YVERT departure from 2493966234 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2533 and YVERT departure from 2493964141 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2532 and YVERT departure from 2493962603 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2531 and YVERT departure from 2493730362 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2530 and YVERT departure from 2493626024 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2529 and YVERT departure from 2493623327 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2528 and YVERT departure from 2493620995 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2527 and YVERT departure from 2493619424 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2526 and YVERT departure from 2493412146 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2525 and YVERT departure from 2493235154 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2524 and YVERT departure from 2493121677 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2523 and YVERT departure from 2493059844 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2522 and YVERT departure from 2493057083 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2521 and YVERT departure from 2493055871 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2520 and YVERT departure from 2492957915 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2519 and YVERT departure from 2492880955 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2518 and YVERT departure from 2492544076 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2517 and YVERT departure from 2492423758 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2516 and YVERT departure from 2492417400 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2515 and YVERT departure from 2492414719 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2514 and YVERT departure from 2492413908 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2513 and YVERT departure from 2492327128 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2512 and YVERT departure from 2492230125 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2511 and YVERT departure from 2491947217 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2510 and YVERT departure from 2491884830 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2509 and YVERT departure from 2491821845 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2508 and YVERT departure from 2491819116 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2507 and YVERT departure from 2491817468 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2506 and YVERT departure from 2491784652 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2505 and YVERT departure from 2491719981 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2504 and YVERT departure from 2487354643 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2503 and YVERT departure from 2487272304 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2502 and YVERT departure from 2487218716 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2501 and YVERT departure from 2487215968 found to restore

  RMAN-06025: no backup log archived for thread 1 with 2500 sequence and YVERT departure from 2487214915 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2499 and YVERT departure from 2487178867 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2498 and YVERT departure from 2475666929 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2497 and YVERT departure from 2475424798 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2496 and YVERT departure from 2475356185 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2495 and YVERT departure from 2475353406 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2494 and YVERT departure from 2475352071 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2493 and YVERT departure from 2475297238 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2492 and YVERT departure from 2475237220 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2491 and YVERT departure from 2475177867 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2490 and YVERT departure from 2475175065 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2489 and YVERT departure from 2475173911 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2488 and YVERT departure from 2475116250 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2487 and YVERT departure from 2475011369 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2486 and YVERT departure from 2474948383 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2485 and YVERT departure from 2474945180 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2484 and YVERT departure from 2474943701 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2483 and YVERT departure from 2474893025 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2482 and YVERT departure from 2474114073 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2481 and YVERT departure from 2473907191 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2480 and YVERT departure from 2473776113 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2479 and YVERT departure from 2473773241 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2478 and YVERT departure from 2473770145 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2477 and YVERT departure from 2473769454 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2476 and YVERT departure from 2473666106 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2475 and YVERT departure from 2473483998 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2474 and YVERT departure from 2473381579 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2473 and YVERT departure from 2473134334 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2472 and YVERT departure from 2473066760 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2471 and YVERT departure from 2473064023 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2470 and YVERT departure from 2473062119 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2469 and YVERT departure from 2473038503 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2468 and YVERT departure from 2472797901 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2467 and YVERT departure from 2472710532 found to restore

  RMAN-06025: no backup log archived for thread 1 with sequence 2466 and YVERT departure from 2472456854 found to restore

  RMAN-00567: Recovery Manager could not print error messages

  Why is it always get all these old newspapers archive? What should I do to get that continues. I'm sure miss me something small, but it is just eluding me.

  Thank you

  Rob

  Follow these steps:

  RMAN > crosscheck backup;

  RMAN > overlapping copy;

• How to write a query for the data exchange between two columns?

  How to write a query for the data exchange between two columns?
  
  I tried a request, does NOT work.
  

  update tmp t1 set t1.m1=t1.m2 and t1.m2=(select t2.m1 from tmp t2 where t2.student_id = t1.student_id)

  Thank you.
  
  Published by: user533361 on October 23, 2009 14:04

  Just plain and simple:

  update tmp t1
   set t1.m1=t1.m2,
       t1.m2=t1.m1
  /
  

  SY.

• Two part question: 1 How can I write a script for long Division, 2. How can I make my form?

  1. I have a field where I need to write a formula for a division problem: (power/population) / 365.  When I use the simplified field notation I get an error: the entered value does not match the format field.  I want the answer as a number with no decimal point.  If I format the field to 'no format' I don't get an error message but the answer comes with up to 10 digits after the decimal point.  I'd rather have the answer in integer without figures after the decimal point.  How can I write this in the custom calculation script?

  2. on accessibility - I never checked on the display/a Mode and unlocked the Acrobat/PDF compatibility.  Some users do not have a problem by filling out the form, but others are not allowed to fill that PDF/A is enabled for their document.  Is this something on their end?  Or is it something on my end blocking them?

  If you multiply by 100, it appears correctly. But if you need to retain the value of the field, you need to use a script to Format custom instead. If you need help, post again.

• error: could not write the destination file (1 003)

  I am trying to export 40 photos of Photos.  I just installed OX El Capitan.  Only 13 of them get downloadable.  For the rest, I get this message: error: could not write the destination file (1 003)

  I tried to manually fix the library but still does not work (command + option + opening photos).

  And I do not have a backup on icloud photo library I have a backup on an external drive...

  You try to export the originals of your photos or revised versions?

  When you try to export photos to?

  You try to export to a folder on your system drive or a folder on an external drive?  If an external drive, which is the file system? And how the player is connected?

  You have permissions to write to the folder, when you export to?

• Retention policy for archive logs.

  Retention policy is set to "REDUNDANCY 2".

  We do the complete disk backup without archive logs at 12:00.

  After that, we make full backup with newspapers to archive tape at 18:00.

  RMAN will consider newspapers to check-in after 12:00 as obsolete as it is backed up to tape?

  Thank you.

  REDUNDANCY applies only to the data files and control files. For archiving logs, there are POLICY of DELETE ARCHIVELOG. But "remove obsolete" won't use POLICY of DELETE ARCHIVELOG, so archiving logs should be removed separately if they meet this policy.

• RMAN-06820: WARNING: unable to archive the current log on the primary database

  I got the following exception when I try to backup the data files and the archivelogs on the physical by uisng RMAN standby database.

  RMAN-06820: WARNING: unable to archive the current log on the primary database

  Target ORACLE database error:

  ORA-17629: unable to connect to the remote database server

  ORA-17627: ORA-00942: table or view does not exist

  It's the backup script

  "

  connection target sys/oracle

  Configure controlfile autobackup on;

  Run {}

  nocfau together;

  allocate channel ch01 device type disc format ' / test/%U';

  allocate channel ch02 device type disc format ' / test/%U';

  backup database copy archivelog;

  backup copy current controlfile;

  }

  "

  And there is no error ora in the primary alert log.

  I was able to tnsping two server (primary/secondary) properly and could also primary of the remote login on standby db server and switch logfile. I read there is a very similar thread, but it has failed so I post again and hope I could get a few clues. Thank you.

  Hello again;

  Try to change this:

  connection target sys/oracle

  to something like this:

  RMAN target sys/password@PRIMARY auxiliary.

  Complete example:

  http://www.Visi.com/~mseberg/data_guard/duprman2.html

  Best regards

  mseberg

• Two Destinations - a VDR

  I met an interesting problem...

  I have two network shares added to my camera VDR, it is NFS, the other is CIFS (Windows share). They use different credentials of course.

  I created two backup tasks, using the NFS share, the other uses the CIFS share.

  The first backup job, using NFS Sharing worked well for centuries. The second task of backup and the corresponding CIFS network to share, I added at a later date. When I added the second network (CIFS) share, the second backup task went very well but the first backup task, then failed to run. When I returned in the first backup job, it seemed that the network share was more accessible - the 'Destination' option is grey and when I tried to click on it, I received the following error message:

  "This destination is not available for a backup job. Please make sure that the destination has been formatted and has enough free space.

  I disassembled the part and mounted successfully. This was going well apart from checking the integrity resulting takes too long (over 12 hours).

  Verification of backups, the next day, it turned out that the second backup task now was not to run and of course, when I watched the 'Destination' in the settings of the backup task, it is gray as well!

  So it seems that if I add a network share with different credentials for a backup job, network, share different, with different credentials, will be made invalid which will then affect backup specifying as a destination.

  Is there a 'best practice' for multiple destinations on one device VDR? Is it because they are of different types of share or the device does support only two destinations if they use the same credentials?

  Please note that both of my destinations to target the same NAS (same IP address) - every action is on a separate virtual disk of 500GB.

  Note the two destinations by its IP address to the value 'Server' but I use a different value to the value of 'folder '.

  This is the value of the server that must be unique for different credentials. You can try to plug the CIFS share using the host name (assuming that name resolution works)

  I wonder if the difficulty would be to publish my second network share using NFS which will then use the same credentials.

  It should work.

  André

• Is it possible to write a script for underlined text export to PDF?

  When I make changes in the financial document, I must emphasize this purpose to show what I edit, these underscore was called "markup". And then print (paper version) and gen (PDF) of the amendment, which means I have to print and gen text underlined (or called markup text) after modification.

  sample PIC:

  

  If:

  Customer requires a new version of the markup, which means I have to change the last beacon color (color of the underline to the last amendments) in 'back' and then make new 'red' as this markup:

  

  What I want:

  is it possible to write a script for printing and gen only markup in the document text all open

  and I want two versions

  (1) all text markup gen no matter the color of the underline

  (2) the red color of the markup text gen

  Thank you!

  Hi HarveyLiu,

  Why, you ask? It will export the pages who pointed out the text.

  var doc = app.documents;
  app.findTextPreferences = null;
  app.findTextPreferences.underline = true;
  for(var i=0;i
  Kind regards
  Cognet
  		   

• Destination of archive

  Hello
  
  I am performing some tests in a database and I put the destination archive (log_archive_dest) at E:\bkp\arch.
  
  The archives are get stored at the specified location (E:\bkp\arch). But physically, if I rename the directory "Ark" to something else and do not make any changes in the file pfile and spfile, the database should be suspended or throw me error that the destination of archive is not available.
  
  Is not to launch any error, but the archives are get generated in the directory of 1 level upward. I mean, the archives are now get generated in E:\bkp\ location eventhough the pfile and spfile show that log_archive_dest = "E:\bkp\arch."
  
  Why Oracle would not error throw?

  Yes. What you said is quite right. I also tried out.
  The reason why Oracle has started archiving E:\bkp location after you rename the file arch is that Oracle goes in search of the destination of the archives to E:\bkp\ and later couldn't find the folder "Ark" and began to be archived under E:\bkp\

  Your check-in process in the database would definitely get hooked and get errors generated in the alert log file. You have specified the destination as E:\bkp\arch. If you specify the destination of archive as E:\bkp\arch\ then definitely Oracle would throw an error when starting the database if it cannot locate the folder "Ark".

  If you start the database with having the location such as "E:\bkp\arch\" and later rename the 'arc' directory, then try to generate archives. You will certainly get the error messages in your alert log file and database would get hooked. Error messages would be something like below

  ORA-16038: log 2 sequence # 23 can be archived
  ORA-00312: wire 2 1 online journal: "REMAKING the PASSAGE of WIRE of LOG '.
  * ORA-09291: sksachk: invalid device specified for the destination of archive
  OSD-04018: cannot access the specified directory or device
  S/O-error: (OS 2) the system cannot find the file specified

  Complete the destination path to archive with a "-" so that oracle looks like inside the directory and not only to the directory

• RMAN supports two types of backups...

  [http://www.amazon.com/Oracle-Database-RMAN-Backup-Recovery/dp/0072263172#reader_0072263172]
  
  This question is related to the book "Oracle Database 10g RMAN Backup & Recovery" by Matthew Hart and Robert G Freeman on page 6.
  
  Please see the attachment. It says 'RMAN supports two types of backups.
  
  Stop the database instance for cold backup and copy the necessary files using OS commands.
  
  So, what is the meaning of say RMAN supports the backup of cold. We must not RMAN do cold back.
  
  Context in which the author said that the above sentence.
  
  Thank you
  Smith

  If you're doing a cold backup by RMAN (which is done with the database in MOUNT State), the advantage is that RMAN updates its repository / controlfile with information about the backup that was made.
  As a result, RMAN can be used to identify and restore the backup.

  (Of course, if the backup is a BACKUPSET, then you must RMAN to restore the backup, while a backup as COPY DATA file can also be restored using OS commands).

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• Two copies of archive newspapers with one sense

  Hello
  
  On a 11g database, I got only defined flash_recovery_area. When set to log mode archive, planned only a copy of archive newspapers produced in the defined location of USE_DB_RECOVERY_FILE_DEST, but there is another copy so obtained in $ORACLE_HOME/dbs directory. How to explain this? and how to DISABLE the second copy to produce?
  
  Thanks for any help
  
  Li Zhuang
  
  PS: more information
  
  In spfile:
  
  ORCL.__java_pool_size = 50331648
  ORCL.__large_pool_size = 16777216
  ORCL.__oracle_base='/usr/oracle11g'#ORACLE_BASE the value of the environment
  ORCL.__pga_aggregate_target = 1828716544
  ORCL.__sga_target = 1056964608
  ORCL.__shared_io_pool_size = 0
  ORCL.__shared_pool_size = 654311424
  ORCL.__streams_pool_size = 0
  *.audit_file_dest='/usr/Oracle11g/Admin/ORCL/adump '
  * .audit_trail = "db".
  * full = '11.1.0.0.0'
  * .control_file_record_keep_time = 30
  *.control_files='/DB/orcl1/control0^@^@C^AC"^@^@^@^@^@^C^@^@^@^@^@^@^A^D{^S^@^@1.ctl','/DB/orcl1/control02.CTL ',.
  ' / db/orcl1/control03.ctl'
  * .db_block_size = 8192
  * .db_domain = "
  * .db_name = "orcl".
  *.db_recovery_file_dest='/usr/Oracle11g/flash_recovery_area '
  * .db_recovery_file_dest_size = 6442450944
  * .diagnostic_dest = "/ usr/oracle11g."
  *. Dispatchers ='(Protocol=TCP) (SERVICE = orclXDB)"
  * .job_queue_processes = 5
  * .open_cursors = 300
  * .pga_aggregate_target = 1824522240
  * runoff = 150
  * .remote_login_passwordfile = "EXCLUSIVE."
  * .sga_max_size = 1258291200 #internally adjusted
  *. SGA_TARGET^@^@C^AC"^@^@^@^@^@^D^@^@^@^@^@^@^A^DCS^@^@=1056964608
  * .undo_tablespace = "UNDOTBS1.
  
  ==============================
  SQL > select destination from V$ ARCHIVE_DEST;
  
  
  DESTINATION
  --------------------------------------------------------------------------------
  / usr/Oracle11g/R1/DBS/Arch
  
  
  
  
  
  
  
  
  USE_DB_RECOVERY_FILE_DEST
  
  10 selected lines.
  
  SQL > SQL > archive log lis
  SP2-0718: illegal option ARCHIVE LOG
  SQL > list of archive logs
  Database log mode Archive Mode
  Active AutoArchive
  Destination of archive USE_DB_RECOVERY_FILE_DEST
  Sequence of journal online oldest 2549
  Log sequence archive 2551
  Current log sequence 2551
  SQL >
  
  ===================
  SQL > show parameter Archives
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  ARCHIVE_LAG_TARGET integer 0
  log_archive_config string
  Log_archive_dest chain
  Log_archive_dest_1 chain
  LOG_ARCHIVE_DEST_10 string
  LOG_ARCHIVE_DEST_2 string
  log_archive_dest_3 string
  log_archive_dest_4 string
  log_archive_dest_5 string
  log_archive_dest_6 string
  log_archive_dest_7 string
  log_archive_dest_8 string
  log_archive_dest_9 string
  allow the chain of log_archive_dest_state_1
  allow the chain of log_archive_dest_state_10
  allow the chain of LOG_ARCHIVE_DEST_STATE_2
  allow the chain of log_archive_dest_state_3
  allow the chain of log_archive_dest_state_4
  allow the chain of log_archive_dest_state_5
  allow the chain of log_archive_dest_state_6
  allow the chain of log_archive_dest_state_7
  allow the chain of log_archive_dest_state_8
  allow the chain of log_archive_dest_state_9
  log_archive_duplex_dest string
  log_archive_format string %t_%s_%r.dbf
  log_archive_local_first Boolean TRUE
  log_archive_max_processes integer 4
  log_archive_min_succeed_dest integer 1
  log_archive_start boolean FALSE
  log_archive_trace integer 0
  standby_archive_dest channel? / dbs/arch

  It's how 11g install sets up the destination archive initially after the database is created using s/n.

  What you can do is to go to the settings of recovery in Enterprise Manager. You will notice that the number 1 destination of the journal Archive is set to usr/oracle11g/R1/dbs/arch number 10 is set to USE_DB_RECOVERY_FILE_DEST

  Delete the number 1 entry (leave it blank). Apply the settings. This will force Oracle to log only flash_recovery_area.

  
  
  Oracle database FAQ
  
  

• Firefox displays the two shockwave for Director 12.0.7.148 & 12.0.5.146 plugins

  I am running firefox 26 and when I discovered my plugins (Tools > Modules > Plugins), I see the two Shockwave for Director, 12.0.7.148 and 12.0.5.146. When I click on the link "Check to see if your plugins are up to date", Shockwave for Director 12.0.7.148 is the only one that is listed and also shows to date.

  Is this all true, or I have to delete 12.0.5.146 and if so how?

  Thank you
  Robert

  You can remove the older Shockwave for Director plugin or remove the two (uninstall via Control Panel).
  
  Shockwave for Director is a different plugin than the Shockwave Flash Player and hardly use these days.

  • https://support.Mozilla.org/KB/using+the+Shockwave+plugin+with+Firefox