Backupexec symantec rman backup

Hi
We have Oracle 10gR2 database on Linux with Oracle remote agent installed/configured. Database size is about 100GB. Backup exec 10 on another win2k3 backupserver with Oracle agent installed./configured.
Can we take manual rman backup with this tape drive on another linux server.

Hello,
Ora 00603 Oracle server session terminate by fatal error.
Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer) The ORA-04030 error message is interesting. It means that the OS doesn't have enough memory for Oracle.
So you may monitore the Memory usage of the Server during the Symantec Backup, and check for any activity. May be the Symantec Backup runs when other Batch Jobs use already a lot of memory . You may also have to extend the RAM of the Server.
Also, check for the RMAN script used by Symantec and compare with the "manual" script. May be, some options are used with Symantec and consume more resources on the Server.
Hope this help.
Best regards,
Jean-Valentin

Similar Messages

  • Rman backup job Suspended on Agent Unreachable

    Hi,
    I have Oracle 10.2.0 installed on windows 2003 server. i configure oracle suggested rman backup which works fine till now. but now it shows
    Suspended on Agent Unreachable message and backup doesn't happen.
    if check like
    C:\Documents and Settings\Administrator>emctl status agen
    Oracle Enterprise Manager 10g Database Control Release 10
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights
    Agent is Not Running
    C:\Documents and Settings\Administrator>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights
    These Windows services are started:
       Application Experience Lookup Service
       Application Management
       Automatic Updates
       COM+ Event System
       COM+ System Application
       Computer Browser
       Cryptographic Services
       DCOM Server Process Launcher
       DefWatch
       Distributed File System
       Distributed Transaction Coordinator
       DNS Client
       DNS Server
       Error Reporting Service
       Event Log
       File Replication Service
       FTP Publishing Service
       HTTP SSL
       IIS Admin Service
       Indexing Service
       Intel PDS
       Intersite Messaging
       IPSEC Services
       Kerberos Key Distribution Center
       Logical Disk Manager
       LogMeIn
       LogMeIn Maintenance Service
       Net Logon
       Network Connections
       Network Location Awareness (NLA)
       NT LM Security Support Provider
       OracleDBConsoleneo
       OracleOraDb10g_home1iSQL*Plus
       OracleOraDb10g_home1TNSListener
       OracleServiceNEO
       Plug and Play
       Print Spooler
       Protected Storage
       Remote Access Connection Manager
       Remote Procedure Call (RPC)
       Remote Registry
       Secondary Logon
       Security Accounts Manager
       Server
       Shell Hardware Detection
       SQL Server (MSSQLSERVER)
       SQL Server Agent (MSSQLSERVER)
       SQL Server Analysis Services (MSSQLSERVER)
       SQL Server FullText Search (MSSQLSERVER)
       SQL Server Integration Services
       SQL Server Reporting Services (MSSQLSERVER)
       Symantec AntiVirus Server
       System Event Notification
       Task Scheduler
       TCP/IP NetBIOS Helper
       Telephony
       Terminal Services
       Windows Management Instrumentation
       Windows Search
       Windows Time
       Workstation
       World Wide Web Publishing Service
    The command completed successfully.means my agent was stop but now i start it.
    i find on Google that this type of error happen when you change in database like ip address, sid etc but i haven't do any change.
    i am facing same problem so many times.
    Now how to reschedule the existing backup job so that it starts work again.
    thanks
    umesh

    thanks for reply
    i do it.
    C:\Documents and Settings\Administrator>emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    EM Daemon is not running.
    Logs are generated in directory C:\oracle\product\10.2.0\db_1/Techwave_neo/sysman/log
    C:\Documents and Settings\Administrator>emctl stop dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    The OracleDBConsoleneo service is stopping.....
    The OracleDBConsoleneo service was stopped successfully.
    C:\Documents and Settings\Administrator>emctl start dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation.  All rights reserved.
    http://Techwave:5500/em/console/aboutApplication
    Starting Oracle Enterprise Manager 10g Database Control ...The OracleDBConsoleneo service is starting................
    The OracleDBConsoleneo service was started successfully.now it is working fine.
    now issue is how i reschedule my suspended job.
    i got this error.
    Edit is not supported for this job type, only general information about the job can be updated No scheduled executions - this job can not be modified.

  • Configure backup agent to take the RMAN backup

    Hi,
    We have a Sun Storagetek SL48 tape library with us. we want to take the backup to tape using Rman.
    In order to take the RMAN backup, we need a backup agent needs to be installed on the database server.
    1. My doubt is If we have Sun Storagetek SL48 tape library, what backup agent needs to be installed on the server?
    2. If we know agent name, Could you please share the document to install the agent?
    Thanks for your help.
    R.Sundaravel

    These softwares support the SL48 and they have an agent for RMAN : Symantec NetBackup, Legato Networker.
    For Symantec, please check this URL : http://www.symantec.com/business/support/index?page=content&id=HOWTO44847#v15496705
    For Legato, this one : https://store.emc.com/Product-Family/DATA-DOMAIN-PRODUCTS/EMC-NetWorker/p/EMC-NetWorker

  • RMAN Backup to tape using Oracle Secure Backup

    I am trying to take 11g R2 (11.2.0.3) database backup using RMAN. I am using Oracle Secure Backup for configuring virtual tape library and virtual tape drive.
    Whenever, I am running the RMAN backup script it simply hangs. While checking the backup job status from Oracle Secure Backup web interface, the job status are displaying 'pending resource availability'.
    On, furthur investigating the job, the following error message are displayed,
    " Dispatching job to run on oradb. Drive or volume on which mount attempted is unusable".
    Library and Tape Creation:
    mkdev -t library -o -S 4 -a oradb:/vlib -v vlib
    mkdev -t tape -o -a ora11:/vt -v -l vlib -d 1 vt
    Not able to fix this error. Need help
    Message was edited by: 799814

    There is a VTL: http://mhvtl-linux-virtual-tape-library-community-forums.966029.n3.nabble.com/
      really work well with OSB 10.3.0.3 64bit, the version of it, fully tested by me , is 1.2
    The installation guide of it here:
    mh virtual tape & library system.
    Instructions assume reader is familiar with the kernel build process.
    There are two sections of code to build.
    - The kernel module
    - The user-space daemons.
    Kernel module mhvtl:
    ==================
    1) Make sure the kernel-devel package to match your running kernel is installed.
    e.g.
    RedHat AS 4 & 5:
    # rpm -qa|grep kernel
    kernel-2.6.9-34.0.1.EL
    kernel-devel-2.6.9-34.0.1.EL
    kernel-2.6.9-5.EL
    kernel-devel-2.6.9-5.EL
    kernel-utils-2.4-13.1.80
    SLES 9 & 10:
    # rpm -qa|grep kernel
    2) Extract the mhvtl source code.
    # tar xvfz mhvtl-2012-04-04.tgz
    3) Change directory into the kernel driver source.
    # cd mhvtl-1.2/kernel/
    # make
    # make install
    User space daemons:
    ===================
    Pre-req for a running mhvtl
    - sg3_utils (http://sg.danny.cz/sg/sg3_utils.html)
    Pre-req to build/compile userspace:
    - zlib-devel
    * To build an RPM
      ===============
    cp mhvtl-YYYY-MM-DD.tar.gz /usr/src/packages/SOURCE/
    cd /usr/src/packages/SOURCE
    rpmbuild -tb mhvtl-YYYY-MM-DD.tar.gz
    <wait for rpm build to complete>
    rpm -Uvh /usr/src/packages/RPMS/<cpu type>/mhvtl-1.2-z.<cpu type>.rpm
    (The rpm install will create system group & accounts vtl)
    - Note: For RedHat, replace 'packages' with 'redhat'
    * To build from tar archive (Debian / Ubuntu):
      ============================================
    apt-get install lsscsi
    apt-get install sg3_utils
    To limit damage that may occur by wayward daemons, I highly recommend creating
    a group and user called 'vtl'
    # /usr/sbin/groupadd --system vtl
    # /usr/sbin/useradd --system -c "Vitrual Tape Library" -d /opt/vtl -g vtl -m vtl
    Now build user space daemons:
    From the parent directory where you extracted the source.
    # cd mhvtl-1.2
    Build the binaries
    # make
    Install the rc script into /etc/init.d/ and binaries to /usr/local/bin/
    # make install
    Start daemons:
    /etc/init.d/mhvtl start
    Test:
    Note: Make sure the 'mtx' & 'lsscsi' utilities are installed
    The virtual devices are attached to HBA #5 in this example.
    e.g.
    # lsscsi -g
    [0:0:0:0]    disk    ATA      WDC WD1200BEVS-0 02.0  /dev/sda  /dev/sg0
    [3:0:0:0]    cd/dvd  Optiarc  DVD RW AD-7910A  1.D1  /dev/sr0  /dev/sg1
    [5:0:0:0]    mediumx SPECTRA  PYTHON           5500  /dev/sch0  /dev/sg6
    [5:0:1:0]    tape    QUANTUM  SDLT600          5500  /dev/st0  /dev/sg2
    [5:0:2:0]    tape    QUANTUM  SDLT600          5500  /dev/st1  /dev/sg3
    [5:0:3:0]    tape    IBM      ULT3580-TD4      5500  /dev/st2  /dev/sg4
    [5:0:4:0]    tape    IBM      ULT3580-TD4      5500  /dev/st3  /dev/sg5
    # mtx -f /dev/sg6 status
      Storage Changer /dev/sg6:4 Drives, 37 Slots ( 4 Import/Export )
    Data Transfer Element 0:Empty
    Data Transfer Element 1:Empty
    Data Transfer Element 2:Empty
    Data Transfer Element 3:Empty
          Storage Element 1:Full :VolumeTag=SDLT01S3                           
          Storage Element 2:Full :VolumeTag=SDLT02S3                           
          Storage Element 3:Full :VolumeTag=SDLT03S3                           
          Storage Element 4:Full :VolumeTag=SDLT04S3                           
          Storage Element 5:Full :VolumeTag=SDLT05S3                           
          Storage Element 6:Full :VolumeTag=SDLT06S3                           
          Storage Element 7:Full :VolumeTag=SDLT07S3                           
          Storage Element 8:Full :VolumeTag=SDLT08S3                           
          Storage Element 9:Full :VolumeTag=SDLT09S3                           
          Storage Element 10:Empty
          Storage Element 11:Full :VolumeTag=ULT001L1                           
          Storage Element 12:Full :VolumeTag=ULT002L2                           
          Storage Element 13:Full :VolumeTag=ULT003L3                           
          Storage Element 14:Full :VolumeTag=ULT004L4                           
          Storage Element 15:Full :VolumeTag=ULT005L1                           
          Storage Element 16:Full :VolumeTag=ULT006L2                           
          Storage Element 17:Full :VolumeTag=ULT007L3                           
          Storage Element 18:Full :VolumeTag=ULT008L4                           
          Storage Element 19:Full :VolumeTag=ULT009L1                           
          Storage Element 20:Empty
          Storage Element 21:Full :VolumeTag=8MM001X4                           
          Storage Element 22:Full :VolumeTag=8MM002X4                           
          Storage Element 23:Full :VolumeTag=8MM003X4                           
          Storage Element 24:Full :VolumeTag=8MM004X4                           
          Storage Element 25:Empty
          Storage Element 26:Empty
          Storage Element 27:Empty
          Storage Element 28:Empty
          Storage Element 29:Empty
          Storage Element 30:Empty
          Storage Element 31:Full :VolumeTag=CLN001L1                           
          Storage Element 32:Full :VolumeTag=CLN002L1                           
          Storage Element 33:Full :VolumeTag=CLN003L1                           
          Storage Element 34 IMPORT/EXPORT:Empty
          Storage Element 35 IMPORT/EXPORT:Empty
          Storage Element 36 IMPORT/EXPORT:Empty
          Storage Element 37 IMPORT/EXPORT:Empty
    Enjoy.
    Please feel free in letting me know if this works for you.
    Bug fixes and suggestions always welcome.
    [email protected]
    [email protected]

  • How can i do a RMAN backup of my database from the network ?

    i'm using oracle 8i.1.7.3 with win server 2003
    i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
    i'd like to save the backup in another machine (the same LAN, the same OS ).
    to do that i've mapped a logical device in my comptur (z):
    when i run rman command i got this error:
    channel ORA_DISK_1: starting piece 1 at .......
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
    00
    ORA-19504: failed TO CREATE file "\\remote\save\"
    ORA-27040: skgfrcre: create error, unable to create file
    OSD-04002: unable to open file
    O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
    rrect.

    Hi,
    ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
    also make sure that oracle user has permission to write to this direcotry (chmod command)
    hope this helps
    cheers, walrus

  • Can not recover table from rman backup

    For testing I want to recover deleted table from rman backup.
    I have make vm of oracle 11g.  the following step i have applied but could not recover the table.
    rman> backup database ;
    On sqlplus create login as scott/tiger
    create table scott.emp1(col1 varchar2(10));
    insert into emp1(col1) value('Yasir ') ;
    commit ;
    select * from emp1 ;
    it shows me one row successfully.
    Now i have login the  sys as sysdba
    sqlplus> alter system switch logfile ;
    after this i have drop the table .
    Now to recover the table i have restored database on same vm.
    rman>restore database ;
    rman> recover database ;
    rman> alter database open ;
    on sqlplus i have issued
    sqlplus> select * from scott.emp1 ;
    table or view does not exist.
    any help how to recover the deleted table from rman backup

    Hi,
    Check this test case
    SQL> create table TEST2 as select * from emp;
    Table created.
    SQL> select count(*) from TEST2;
      COUNT(*)
            15
    SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
    TO_CHAR(SYSDATE,'DD-
    10-SEP-2013 10:57:05
    SQL> alter system switch logfile;
    System altered.
    SQL> drop table TEST2 purge;
    Table dropped.
    SQL> shu immediate
    [oracle@vnode MYSHELL]$ rman target /
    Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: DDTEST (DBID=1667776968, not open)
    RMAN> run{
    set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
    restore database;
    recover database;
    alter database open resetlogs;
    }2> 3> 4> 5> 6>
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 10-SEP-13
    database opened
    RMAN> exit
    SQL> set lin 200 pages 100
    SQL> select count(*) from test2;
      COUNT(*)
            15
    HTH

  • Unable to restore and recover my Database from RMAN Backup

    Dear All,
    Iam practicing RMAN in Windows environment.
    My configurations are
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
    Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
    then i tried to startup the DB but it is saying
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
    So i tried to restore the Database with my rman backup
    RMAN> restore database;
    But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
    So, i am unable to recover my DB
    Please tell me whether i am doing any mistake, what is the solution for my problem.
    Thanks in advance
    Mahi

    All you restored was your datafiles.
    Now issue recover database and that will apply the archive logs.
    This is in the oracle documentation.
    "You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
    In this case after issuing restore database in RMAN, then issue this.
    "Recover database"
    It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

  • Create a new Database in an other server using a copie of RMAN backup

    Hi all,
    I want to create an other instance for our production database. We have disk and tape in rman backup. My question is can i create a new database using our disk backup in an other server?
    If some procedure or steps is there, email it to my adresse [email protected]
    Hamid.
    Thanks

    By means of the use of Recovery Manager it is possible to duplicate a database out from a previously taken rman backup. The method will be outlined in the next few lines.
    Let's assume a source database named SRCDB and the target database, named GEMINI. A unix like environment is assumed, but it can be implemented on windows as well, just beware of the particular Oracle implementation on a windows platform (orapwd file name, service creation, path format)
    1. Create a password file for the Cloned (GEMINI) instance:
    orapwd file=/u01/app/oracle/product/9.2.0.1.0/dbs/orapwGEMINI password=password entries=10
    2. Configure tnsnames.ora and listner.ora
    Properly identify the database at the tnsnames.ora and have the instance manually registered against the listener.ora files, both files located at the $ORACLE_HOME/network/admin directory.
    2.a Manually register the database against the listener (listener.ora)
    (SID_DESC =
    (ORACLE_HOME = /u01/app/oracle/product/9.2.0.1.0)
    (SID_NAME = GEMINI)
    2.b Added the target GEMINI to the tnsnames.ora
    GEMINI =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1521))
    (CONNECT_DATA =
    (ORACLE_SID = GEMINI)
    2.c Reload the listener
    lsnrctl reload
    3. Create a new init.ora for the cloned database.
    Next create an init.ora file for the cloned database. In case the same paths cannot be used on the target host, either because it is the same source host or because those paths are not reproducible on the target, then DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT may be required to be defined
    DB_NAME=GEMINI
    CONTROL_FILES=(/u02/oradata/GEMINI/control01.ctl,
    /u02/oradata/GEMINI/control02.ctl,
    /u02/oradata/GEMINI/control03.ctl)
    # Convert file names to allow for different directory structure.
    DB_FILE_NAME_CONVERT=(/u02/oradata/SRCDB/,/u02/oradata/GEMINI/)
    LOG_FILE_NAME_CONVERT=(/u01/oradata/SRCDB/,/u01/oradata/GEMINI/)
    # block_size and compatible parameters must match those of the source database
    DB_BLOCK_SIZE=8192
    COMPATIBLE=9.2.0.0.0
    4. Connect to the cloned instance
    ORACLE_SID=GEMINI; export ORACLE_SID
    sqlplus /nolog
    conn / as sysdba
    5. Create an SPFILE based on the init.ora
    CREATE SPFILE FROM PFILE='/u01/app/oracle/admin/GEMINI/pfile/init.ora';
    6. Start the database in NOMOUNT mode:
    STARTUP FORCE NOMOUNT;
    7. Connect to the TARGET, CATALOG and AUXILIARY databases.
    By means of the rman three connections are open, one for the Source Database (SOURCEDB), another for the Catalog database (RCAT), and one more for the cloned database (GEMINI)
    ORACLE_SID=GEMINI; export ORACLE_SID
    rman TARGET sys/password@SRCDB CATALOG rman/rman@RCAT AUXILIARY /
    8. Complete or Incomplete clone (recover)
    From the rman the database using one of the following commands:
    8.a Clone the database by means of a complete recover.
    DUPLICATE TARGET DATABASE TO GEMINI;
    8.b Clone the database up to a defined point in time in the past by means of an incomplete recover
    DUPLICATE TARGET DATABASE TO GEMINI UNTIL TIME 'SYSDATE-2';
    9. Process finished.
    Once the process is finished, the newly created GEMINI database is ready to be used as an independent new cloned database.
    Ref. RMAN Clone a Database
    ~ Madrid

  • I am getting below error while taking RMAN backup.

    Friends,
    I am getting below error while taking RMAN backup.
    The issue is related with a lock while trying to backup the controlfile.
    The lock is more likely caused by the autobackup controlfile process started just before RMAN process was also trying the backup controlfile as shown in the following alert.log excerpt.
    Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
    ORA-00230: operation disallowed: snapshot control file enqueue unavailable
    Is there anyway to solve this issue?Thanks in advance.

    Hi,
    SQL> SELECT s.sid, username AS "User", program, module, action, logon_time "Logon", l.*
    FROM v$session s, v$enqueue_lock l
    WHERE l.sid = s.sid and l.type = 'CF' AND l.id1 = 0 and l.id2 = 2; 2 3
    no rows selected
    Oracle version : 10.2.0.3
    I am getting this error once in a month not everyday.
    Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
    ORA-00230: operation disallowed: snapshot control file enqueue unavailable
    Please suggest me based on this..Thanks in advance..

  • Creating a new controlfile with datafiles in RMAN backup

    Hi,
    i am using oracle 10g (10.2.0.1) in RHEL5 server. i am trying to restore a RMAN backup from one server to another new server with new db name. i have taken out the spfile from RMAN autobackup and created pfile from it and edited the pfile with new dbname and directory structure and started the db in nomount with the new pfile. Now i have restored the controfile from the RMAN autobackup tried to put the database in mount state. But it failed due to the below error
    RMAN-03002: failure of alter db command at 11/05/2012 21:44:56
    ORA-01103: database name 'ORADB' in control file is not 'DEVDB'
    Hence i shutdown the database and started the db in nomount with new pfile and tried to create the controlfile with the new db name,but it failed as it is looking for the datafiles.
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01565: error in identifying file
    '/u01/app/oracle/oradata/DEVDB/datafile/o1_mf_system_80jq0kfw_.dbf'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    All my datafiles reside in my RMAN backup. How to get the datafiles from RMAN backup in the above scenario??
    Regards,
    007

    Hello;
    The location and filename and DBIS will be different, but you need something like this :
    $ORACLE_HOME/bin/rman  << EOF
    CONNECT TARGET /
    STARTUP NOMOUNT;
    SET DBID 3754763357;  #DBID of PROD database
    RUN
       ALLOCATE CHANNEL c1 DEVICE TYPE disk format '/u01/oradata/backups';
       RESTORE CONTROLFILE FROM '/u01/oradata/backups/sb_t790762003_s85_p1';
       ALTER DATABASE MOUNT;
       SET NEWNAME FOR DATAFILE 1 TO '/u01/app/oracle/oradata/CLONE/system01.dbf';
        SET NEWNAME FOR TEMPFILE 1 TO '/u01/app/oracle/oradata/CLONE/temp01.dbf';
       RESTORE DATABASE;
       SWITCH DATAFILE ALL;
       RECOVER DATABASE;
       release channel c1;
    ALTER DATABASE OPEN RESETLOGS; So you need "SET NEWNAME" for all your files
    Full Example
    http://www.visi.com/~mseberg/rman/restore_database_without_catalog.html
    Best Regards
    mseberg

  • Setting up new dbname/sid while creating oracle db from rman backups in 11g

    Hi all,
    I have rman backups and need to create another database from rman backups with different name... but it is unsuccessful..
    created instance with new db...
    running create new db connecting rman auxiliary sys/password@newdb
    run {
    SET NEWNAME FOR DATAFILE 1 TO 'F:\app\HOME\oradata\clonedb1\SYSTEM01.DBF';
    SET NEWNAME FOR DATAFILE 2 TO 'F:\app\HOME\oradata\clonedb1\SYSAUX01.DBF';
    SET NEWNAME FOR DATAFILE 3 TO 'F:\app\HOME\oradata\clonedb1\UNDOTBS01.DBF';
    SET NEWNAME FOR DATAFILE 4 TO 'F:\app\HOME\oradata\clonedb1\USERS01.DBF';
    SET NEWNAME FOR DATAFILE 5 TO 'F:\app\HOME\oradata\clonedb1\EXAMPLE01.DBF';
    SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';
    DUPLICATE DATABASE TO clonedb
    pfile 'D:\TESTDELETE\initclonedb1.ora'
    BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'
    LOGFILE GROUP 1 ('F:\APP\HOME\ORADATA\ORCL\REDO01.LOG') SIZE 60M REUSE,
    GROUP 2 ('F:\APP\HOME\ORADATA\ORCL\REDO02.LOG.rdo') SIZE 60M REUSE,
    GROUP 3 ('F:\APP\HOME\ORADATA\ORCL\REDO03.LOG') SIZE 60M REUSE;
    Error it shown is in rman backup creation is as follows
    <part>>
    sql statement: alter system set db_name = ''ORCL'' comment= ''Modified by RMAN
    duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area 640286720 bytes
    Fixed Size 1376492 bytes
    Variable Size 314576660 bytes
    Database Buffers 318767104 bytes
    Redo Buffers 5566464 bytes
    Starting restore at 20-DEC-11
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=133 device type=DISK
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
    output file name=F:\APP\HOME\ORADATA\CLONEDB1\CONTROL01.CTL
    output file name=F:\APP\HOME\FLASH_RECOVERY_AREA\CLONEDB1\CONTROL02.CTL
    Finished restore at 20-DEC-11
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/20/2011 07:07:11
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01102: cannot mount databa
    se in EXCLUSIVE mode
    RMAN> EXIT
    how can i prevent rman setting db_name=orcl which is already exists in the db.. i need to create db from rman backups with different dbname...
    whould someone help me out, how can i create database from another database rman backups with different dbname/sid on same host..
    My pfile has new db_name , but while db creation rman setting to db_name to source dbname.. it should be new db name that i want create with new db name...
    is there any RMAN command to specify new DB name it should set while running
    sql statement: alter system set db_name = newdbname -- as part rman script execution...
    it appears to be i should not touch the soruce db.. i have access to only source db rman backups and need to create another db with different dbname/sid.. please do help...

    When you performing RMAN duplicate why you making your script so complicated?
    Your instance name and DB name can be different, But what is the contents in your pfile "D:\TESTDELETE\initclonedb1.ora" ? please do post
    Have you started any other services related to ORACLE? check in start --> run --> services.msc any other active oracles services, Make sure you have clonedb1.
    Startup in nomount
    check the connectivity to target server.
    SET NEWNAME FOR TEMPFILE 1 TO 'F:\app\HOME\oradata\clonedb1\TEMP01.DBF';Why you mentioning SET NEWNAME FOR DATAFILE ? You have option of db_file_name_convert/log_file_name_convert in case if your file system different in Target & auxiliary.
    BACKUP LOCATION 'F:\app\HOME\flash_recovery_area\orcl\'When you have backup in same location why you are mentioning this clause?
    First run duplicate from auxiliary server as
    rman target sys/*****@prod auxiliary /
    RMAN> duplicate target database to "db_name";
    Am not sure what you are trying to do. is it 11gR1 or 11gR2?
    You have option of duplicate from active database without having backup also..
    here some links please check it.
    http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmdupdb.htm#BGBFDJHB
    RMAN 11GR2 : DUPLICATE WITHOUT CONNECTING TO TARGET DATABASE [ID 874352.1]
    knowledgespring      
         Newbie
    Handle:      knowledgespring
    Status Level:      Newbie (10)
    Registered:      Dec 26, 2007
    Total Posts:      243
    Total Questions:      77 (75 unresolved)
    So sad that forum was able to help only in two answers out of your 77 questions :(
    Edited by: CKPT on Dec 21, 2011 5:12 PM

  • Error , ORA-19809 & ORA-19804 While restoring RMAN backup .

    Hi Experts,
    I am restoring production RMAN backup to UAT . Using below steps
    1)rman target=/
    2)RMAN> startup nomount;
    3) RMAN> restore controlfile from '/orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl';
    Starting restore at 05-AUG-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=3 device type=DISK
    channel ORA_DISK_1: copied control file copy
    output file name=+DATA_ACME/acme/controlfile/current.256.724845209
    output file name=+DATA_ACME/acme/controlfile/current.257.724845209
    Finished restore at 05-AUG-10
    4) RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    5) RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME1/current/%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
    new RMAN configuration parameters are successfully stored
    6) RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    old RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
    new RMAN configuration parameters are successfully stored
    released channel: ORA_DISK_1
    7) RMAN> CATALOG START WITH '/orabkdump/Rman_Bak/ACME';
    searching for all files that match the pattern /orabkdump/Rman_Bak/ACME
    List of Files Unknown to the Database
    =====================================
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
    File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
    File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
    File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
    File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
    File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
    File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
    List of Files Which Where Not Cataloged
    =======================================
    File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
    RMAN-07517: Reason: The file header is corrupted
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
    RMAN-07517: Reason: The file header is corrupted
    File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
    RMAN-07517: Reason: The file header is corrupted
    8) RMAN> run {
    2> set until sequence 1789 thread 2;
    3> restore database;
    4> recover database;
    5> sql 'alter database open resetlogs';
    6> }
    executing command: SET until clause
    Starting restore at 06-AUG-10
    using channel ORA_DISK_1
    Finished restore at 06-AUG-10
    Starting recover at 06-AUG-10
    using channel ORA_DISK_1
    starting media recovery
    channel ORA_DISK_1: starting archived log restore to default destination
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=2803
    channel ORA_DISK_1: restoring archived log
    archived log thread=2 sequence=6051
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=2804
    channel ORA_DISK_1: reading from backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/06/2010 23:10:38
    ORA-19870: error while restoring backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 49283072 bytes disk space from 5218762752 limit
    ** My UAT database should be in noarchival mode . Generally such errors have been observed during backup , but have no clue why they occurred during recovery .Please advice .
    Thanks
    Edited by: user11981514 on Aug 6, 2010 9:46 AM

    Hi,
    Since the error ORA-19809 indicates the lack of space in flash recovery area during the media recovery, I suggested increasing the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
    Yes, during the media recovery the RMAN will restore the archived log to the default destination (only if the required archived logs are not already on the disks).You can confirm the restore location of the archived log in RMAN restore log/destination specified by parameters log_archive_dest_1/db_recovery_file_dest.
    Regards,
    Vaibhav

  • Restore spfile from rman backup ---- error.

    Hi,
    I am trying to execute recovery on new machine ...
    I have done the following steps..
    I have one database as ora10g2 as peroduction database on one machine as hosta
    I have created a catalog on another machine cora10g2 (hostb)
    I have taken a full backup from hosta as per following ...
    the following command execute from hosta machine.
    $ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
    Backup completed ...
    Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
    I have done the following setting ...on host b
    set oracle_sid=DUP
    and execute following command ...
    rman target / catalog rman/rman@cora10g2
    RMAN> set dbid 2760732370
    executing command: SET DBID
    database name is "BAAN10G2" and DBID is 2760732370
    RMAN>
    RMAN>
    RMAN> startup force nomount ;
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area 159383552 bytes
    Fixed Size 1977112 bytes
    Variable Size 67114216 bytes
    Database Buffers 83886080 bytes
    Redo Buffers 6406144 bytes
    RMAN>
    RMAN>
    RMAN>
    RMAN> show all ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    RMAN>
    RMAN>
    RMAN> list backup of spfile ;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2420 Full 7.33M DISK 00:00:01 14-JUN-07
    BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
    SPFILE Included: Modification time: 14-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2509 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2694 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2760 Full 80.00K DISK 00:00:01 15-JUN-07
    BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
    Piece Name: /rman/spfile/spfile.ora
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2769 Full 7.33M DISK 00:00:02 15-JUN-07
    BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
    SPFILE Included: Modification time: 15-JUN-07
    RMAN>
    RMAN>
    RMAN> restore spfile from autobackup ;
    Starting restore at 19-JUN-07
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=36 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=35 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=34 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=33 devtype=DISK
    channel ORA_DISK_1: looking for autobackup on day: 20070619
    channel ORA_DISK_1: looking for autobackup on day: 20070618
    channel ORA_DISK_1: looking for autobackup on day: 20070617
    channel ORA_DISK_1: looking for autobackup on day: 20070616
    channel ORA_DISK_1: looking for autobackup on day: 20070615
    channel ORA_DISK_1: looking for autobackup on day: 20070614
    channel ORA_DISK_1: looking for autobackup on day: 20070613
    channel ORA_DISK_1: no autobackup in 7 days found
    channel ORA_DISK_2: looking for autobackup on day: 20070619
    channel ORA_DISK_2: looking for autobackup on day: 20070618
    channel ORA_DISK_2: looking for autobackup on day: 20070617
    channel ORA_DISK_2: looking for autobackup on day: 20070616
    channel ORA_DISK_2: looking for autobackup on day: 20070615
    channel ORA_DISK_2: looking for autobackup on day: 20070614
    channel ORA_DISK_2: looking for autobackup on day: 20070613
    channel ORA_DISK_2: no autobackup in 7 days found
    channel ORA_DISK_3: looking for autobackup on day: 20070619
    channel ORA_DISK_3: looking for autobackup on day: 20070618
    channel ORA_DISK_3: looking for autobackup on day: 20070617
    channel ORA_DISK_3: looking for autobackup on day: 20070616
    channel ORA_DISK_3: looking for autobackup on day: 20070615
    channel ORA_DISK_3: looking for autobackup on day: 20070614
    channel ORA_DISK_3: looking for autobackup on day: 20070613
    channel ORA_DISK_3: no autobackup in 7 days found
    channel ORA_DISK_4: looking for autobackup on day: 20070619
    channel ORA_DISK_4: looking for autobackup on day: 20070618
    channel ORA_DISK_4: looking for autobackup on day: 20070617
    channel ORA_DISK_4: looking for autobackup on day: 20070616
    channel ORA_DISK_4: looking for autobackup on day: 20070615
    channel ORA_DISK_4: looking for autobackup on day: 20070614
    channel ORA_DISK_4: looking for autobackup on day: 20070613
    channel ORA_DISK_4: no autobackup in 7 days found
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/19/2007 18:00:13
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    RMAN>
    I am not able to restore spfile from rman backup ;;;

    Hi,
    I would like to know few things
    1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
    2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
    Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

  • How to find out when last rman backup was made in 9i

    Hello,
    i have an oracle 9i database running on windows here. Is there a way to find out when the last rman backup was done with a sql query?
    I would like to create a job inside the database that regulary checks if a rman backup ran sucessfully instead of using scripts in the operating system.
    But i only know about commands in the rman utility (that i can not execute as a job, right?) - is something similar possible with for example sqlplus?

    Hello,
    this gives some results, but none of the views begins with RC:
    ALL_DIM_HIERARCHIES
    ALL_SOURCE
    ALL_SOURCE_TABLES
    ALL_SOURCE_TAB_COLUMNS
    DBA_DIM_HIERARCHIES
    DBA_RCHILD
    DBA_REGISTRY_HIERARCHY
    DBA_RSRC_CONSUMER_GROUPS
    DBA_RSRC_CONSUMER_GROUP_PRIVS
    DBA_RSRC_MANAGER_SYSTEM_PRIVS
    DBA_RSRC_PLANS
    DBA_RSRC_PLAN_DIRECTIVES
    DBA_SOURCE
    DBA_SOURCE_TABLES
    DBA_SOURCE_TAB_COLUMNS
    USER_DIM_HIERARCHIES
    USER_RESOURCE_LIMITS
    USER_RSRC_CONSUMER_GROUP_PRIVS
    USER_RSRC_MANAGER_SYSTEM_PRIVS
    USER_SOURCE
    Edited by: user590072 on 22.06.2010 05:49

  • Creating a standbay database from an rman backup

    hi,
    I have a situation that a standby database has a large gap in archive log files, the primary server does not now have those files. I understand that you can create a standby from an rman backup of the primary but all reading I have done shows thatn you have to have a recovery catalog to carry this out. The system I am on does not have such a catalog so is there any other way to do this?
    regards
    Alan

    Requirement 'You must have a recovery catalog in a standby requirement' is a little bit misleading. In fact you can do what you want : creating a standby from RMAN backups without having a recovery catalog. 'Duplicate target database for standby' does not require a connection to a recovery catalog.
    You need mandatorily a recovery catalog, when you plan to take backups from the standby later on in order to free the primary from this task. The reason for that is it's not possible to transfer backup records from the standby controlfiles to the primary ones directly. After a backup on the standby you resync the catalog with the standby controlfile. Then you connect to the catalog and the primary,resync again and have actual backup informations in the primary controlfiles. When there's a media recovery problem, you easily can restore/recover the primary.
    Werner

Maybe you are looking for

  • Could not load Module... A known bug in Logic Pro 7.3 with Snow Leopard?

    I know this issue has been discussed before, but on my brand new MacBook Pro it's still an issue, so can someone please help me out with this? Here goes: Loading Logic 7.2.3 in Snow Leopard: The previously selected audio interface is not available Th

  • Apple TV , new software issue

    Just downloaded the new software , Apple TV no longer lets you resume playing or start from the beginning , programs also stop while watching and take you back to the main selection screen

  • SQL: order of WHERE clauses important for performance?

    I wonder if the order of the WHERE clauses does affect performance or if the database optimize each query so that the order is irrelevant? Example: is SELECT * FROM Table1 WHERE (fast condition check) AND (slow condition check) faster than SELECT * F

  • How to find a program's dependencies?

    Hi all, I recently set up a web site including some programs that I wrote over the years, using Arch Linux of course I received a bug report today from someone who failed to compile the source package, because "configure" failed due to missing shell

  • MacBook Pro SSD drive: need to free up space

    Hi, I have a MacBook Pro (late 2011), running OSX 10.7.5, with a 128GB SSD drive. The problem I have is that I am running out of space on my drive, even though I don't appear to be storing that much on it. When I view my usage in 'About This Mac', I