Backup with Veritas Netbackup

Hi,
We will start a EP project soon, but I have a question about the backups of the database. I need to know if we can use Veritas Netbackup to make a online  backup on Maxdb, because i dont have find documentation about this topic.
Thanks in advance

http://help.sap.com/saphelp_nw73/helpdata/en/e2/c39ed1b6754e94bad924b41bc4ee5d/frameset.htm

Similar Messages

  • Duplication with Veritas netbackup 4.5

    Alright. This is driving me crazy. How can you clone a database using Veritas? Right now we are using TSM and are switching to Veritas. With TSM, I can run the duplication from either the target or the auxiliary. With Veritas it states you must run it on the auxiliary. One problem with this is if your target does not have a password file. I can't bounce a production db just to create a temp password file.
    Another issue is with the username. I understand you have to restore logged in as the user who created the backup. We have 28 different servers with 28 different oracle users so to do this will be an administrative hastle. With TSM you can pass rman an options file with the username in there.
    If there's any documention other than in Veritas' manual under "Redirected Restore" I'd love to see it. Veritas' documentation doesn't use the RMAN duplicate command. It's almost as if they expect the exact same directory structure and user on the aux server.
    The error that is killing me is the:
    Failed to open for restore
    I know the backup is there on tape, I just can't get permissions to it and don't know how.
    Thanks

    Hi 152124
    Once you have the catalog created you can begin to play with RMAN. You could backup the whole database and backup it partially and so on. I recommend you to look for the manuals for it.
    Regarding Veritas NetBackup , I have not has experienced with that. I have always worked backing up the database directly to file systems for after move them to tapes.
    If you have any doubt during your learning you can ask here in this forum.
    Joel Pérez
    http://otn.oracle.com/experts

  • Configure MaxDB with Veritas Netbackup

    Hi team,
        When i configure Veritas Netbackup with MaxDB I have the following queries:
    1. should i create a staging file (will it get created automatically) ?
    2. Will all the log, error & History files get created automatically?
    3. Should i use PIPES only to take backup? can't i use FILE backup?
    please help
    Thanks in advance
    Regards,
    Pradeep Chandru.

    Hi,
      I have made the log files to be generated. Now i am getting the following error:
    dbm.prt
    2006-09-04 16:07:15 0x00002624 INF        283 DBMSrv   command backup_save "test01" DATA RECOVERY
    2006-09-04 16:08:22 0x00002624 ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x00002624 ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    2006-09-04 16:32:50 0x00002624 INF        226 DBMSrv   DBM Server client disconnect: PID 7012 on computer xxxxxxxx.local
    dbm.ebl
      2006-09-04 16:07:49 The database is working on the request.
        2006-09-04 16:08:09 The database is working on the request.
        2006-09-04 16:08:20 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
        2006-09-04 16:08:21 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
    The backup operation has ended.
    2006-09-04 16:08:21
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    Reply buffer filled.
    2006-09-04 16:08:22
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
    dbm.prt
    (established at 2006-09-04 15:31:14): PID 11028 on computer xxxxxxxx.local
    2006-09-04 15:31:14 0x000026f8 INF        283 DBMSrv   command backup_start BACKt09 DATA
    2006-09-04 15:32:20 0x000026f8 ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x000026f8 ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    2006-09-04 15:32:20 0x000026f8 INF        226 DBMSrv   DBM Server client disconnect: PID 11028 on computer xxxxxx.local
    2006-09-04 15:32:53 0x00001900 INF        216 DBMSrv   DBM Server client connection (established at 2006-09-04 15:32:53): PID 7308 on computer xxxxx.local
    2006-09-04 15:32:53 0x00001900 INF        283 DBMSrv   command backup_start BACKt09 DATA
    2006-09-04 15:33:58 0x00001900 ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x00001900 ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    2006-09-04 15:33:58 0x00001900 INF        226 DBMSrv   DBM Server client disconnect: PID 7308 on computer xxxxxx.local
    Incase any logs are required then please let me know.

  • Veritas Netbackup Client Installed on Solaris 10 Zone Unable to Work

    Hi
    I am having problems with Veritas Netbackup client which had been installed on a Solaris 10 zone only. We are using Veritas Netbackup server which is installed on a Windows 2000 server and the NBU server is unable to add the new client for backup.
    The way I installed the NBU client was using the manual method where I installed directly on the zone. The zone I've created is a full root zone and the installation seems to be successful.
    Somehow the NBU server just can't see the new client. Do I need to install the client in the global zone to make it work? Is there any checks I can do to make sure I have installed the client correctly and that the services are running in the solaris 10 zone side? Any kind of help would be much appreciated.
    Thanks
    Xavier

    Hi mcbrune1
    I've check on the services in the client and all 4 services were up and running. Than I realized that this client was hardened a few weeks back. So I checked on the /etc/hosts.allow file and added an entry to allow the Master server to communicate using bpcd.
    Now the Master server is able to see the client and everything seems to be working. Thanks for your help.
    Cheers

  • Backup MaxDB 7.7.06.09 to Veritas Netbackup 6.5 fails

    We want to backup MaxDB to Veritas Netbackup server.
    According documentation found about this topic the backup is configured
    by creating 3 files: bsi.env, initWDO.par (for backint for MaxDB) and
    initWDO.utl (for backint for Oracle). The contents of these files are shown below.
    When running the backup, it seems that backint for MaxDB ends with return code 2,
    the error message received is:
      -24920,ERR_BACKUPOP: backup operation was unsuccessful
      The backup tool failed with 2 as sum of exit codes.
    Unfortunately no further errors/warnings are shown that points in any direction
    what's going wrong here.
    We start the backup via the following dbmcli-command:
    dbmcli -u control,****** -d WDO -uUTL control,****** backup_start BACKData_WDO
    (for the time being without xuser entries, first make sure the backup is ok)
    The files dbm.ebl, dbm.prt and several others do not show any additional details/hints.
    It seems as if the "save data quick" to the named pipe is ok, the sql-code returns "0".
    After this the backint for MaxDB should read the named pipe and write it to stage-files,
    but backint (for MaxDB) ends with return code 2.
    Any idea what might go wrong here?
    With kind regards,
    R. Hoogeveen
    The Netherlands
    File bsi.env:
    =========
    BACKINT                /sapdb/WDO/db/bin/backint
    INPUT                  /tmp/backint4maxdb_WDO.in
    OUTPUT                 /tmp/backint4maxdb_WDO.out
    ERROROUTPUT            /tmp/backint4maxdb_WDO.err
    PARAMETERFILE          /sapdb/data/wrk/WDO/initWDO.par
    TIMEOUT_SUCCESS        600
    TIMEOUT_FAILURE        300
    ORIGINAL_RUNDIRECTORY  /sapdb/data/wrk/WDO
    File initWDO.par:
    =============
    STAGING AREA:                  /tmp/stageWDO 1 GB
    FILES PER BACKINT CALL:        1
    BACKINT:                       /usr/openv/netbackup/bin/backint
    PARAMETERFILE OF BACKINT:      /sapdb/data/wrk/WDO/initWDO.utl
    HISTORY FILE:                  /sapdb/data/wrk/WDO/backint_history_WDO.log
    INPUTFILE FOR BACKINT:         /tmp/backint4ora_WDO.in
    OUTPUTFILE FOR BACKINT:        /tmp/backint4ora_WDO.out
    ERRORFILE FOR BACKINT:         /tmp/backint4ora_WDO.err
    MAXIMAL DELAY OF BACKINT CALL: 30
    File initWDO.utl:
    =============
    switch_list /tmp/.switch_WDO.lis
    switch_sem /tmp/.switch_WDO.sem
    switch_log /tmp/.switch_WDO.log
    drives 1
    client wdocsz01
    server backfire
    policy sap_WDO

    Lars,
    The /tmp/backint4maxdb.err file tells me:
    Backint for Oracle was unsuccessful.
    (Unfortunately that was all information in this file.)
    The backint4ora.in file tells me:
    /tmp/stageWDO.0
    (looks ok to me, also at the time backint4ora was started the stage file was created with non-zero size)
    The backint4ora.out file tells me:
    ERROR: incorrect format or option in .utl file (-p)
    (this seems as if the -p option is not recognized by the backint4ora executable)
    When I run this executable manually as user sdb it shows me the commandline that I should use, including the -p option.
    One strange thing I notice is that the order of the options is different from the commandline that is executed.
    (in the usage it shows -p as almost last parameter, the command executed has -p in the middle; I will see if I can execute the backint4ora command manually, since I have the stage file available, I have copied it during the process)
    The backint4ora.err file is empty.
    The commandline of the dbmcli command I execute shows me another interesting error message,
    this might also be the source of all problems here.
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    Could not get external backup ID's from the backup tool.
    I tried to retrieve the external backup id's manually for medium BACKDataWDO, it show me OK without any external backup id's.
    I am not sure, but I think this is correct since no successfull backup was created yet with external backup tool.
    Can it also be that the parameter "history file" from the initWDO.par file is set wrong?
    Currently it is set to "/sapdb/data/wrk/WDO/backint_history_WDO.log" (see above also), but I can imagine
    that this should be set to the dbm.knl or dbm.ebf file ??
    With kind regards,
    Roger Hoogeveen

  • ORA-19511 when backup with rman (using NetBackup Media Manager)

    Hello forum
    I added new database hosts to NetBackup, tried to test backup of the first instance on one host, below is what I get - Do you know cause and solution? Backup from NetBackup master server can be performed without problems. Below you will find the output from sbttest too.
    Thanks Casi
    ---------- rman log -----------
    Recovery Manager: Release 10.2.0.3.0 - Production on Fri Mar 7 10:26:28 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: IARTS (DBID=2414804385)
    connected to recovery catalog database
    RMAN> run
    2> {
    3> allocate channel c1 DEVICE TYPE sbt PARMS='ENV=(NB_ORA_SERV=sksta00500.ksta.zh.ch,NB_ORA_CLASS=LX_ORA_ONL)';
    4> backup current controlfile;
    5> }
    allocated channel: c1
    channel c1: sid=110 instance=IARTS1 devtype=SBT_TAPE
    channel c1: VERITAS NetBackup for Oracle - Release 5.1 (2004122520)
    Starting backup at 07-MAR-08
    channel c1: starting full datafile backupset
    channel c1: specifying datafile(s) in backupset
    including current control file in backupset
    channel c1: starting piece 1 at 07-MAR-08
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on c1 channel at 03/07/2008 10:27:11
    ORA-19506: failed to create sequential file, name="19jalk7t_1_1", parms=""
    ORA-27028: skgfqcre: sbtbackup returned error
    ORA-19511: Error received from media manager layer, error text:
    VxBSAValidateFeatureId: Failed with error:
    Server Status: file open failed
    RMAN>
    ---- sbttest ---------------------------
    $ORACLE_HOME/bin/sbttest /tmp/x.lst
    The sbt function pointers are loaded from libobk.so library.
    -- sbtinit succeeded
    -- sbtinit (2nd time) succeeded
    sbtinit: Media manager supports SBT API version 2.0
    sbtinit: Media manager is version 5.0.0.0
    sbtinit: vendor description string=VERITAS NetBackup for Oracle - Release 5.1 (2004122520)
    sbtinit: allocated sbt context area of 8 bytes
    sbtinit: proxy copy is supported
    -- sbtinit2 succeeded
    -- regular_backup_restore starts ................................
    -- sbtbackup succeeded
    Segmentation fault

    Are you sure, you installed the proper media management software? Check it:
    (1) cd to your $ORACLE_HOME/bin directory
    (2) Type sbttest test
    The sbttest is a standalone program which test to see if the MML(Media
    Management Layer) software is installed and can accept a data stream and return
    an identical data stream.
    sbttest will return 0 which indicates success or 1 which indicates an error has
    occurred. An error means it's not an Oracle problem.

  • Is SECURE BACKUP a good alternative to Veritas Netbackup ?

    Folks,
    With Oracle becoming more and more "one place - get all" company, i guess for support perspective, it will good to use or atleast start evaluating different Oracle products that are used with RDBMS
    Got a question, Is Secure Backup product having all the capabilities and can it be a viable alternative to veritas netbackup ? I got the documentation and presentations. But it will be pleasing to know if somebody has already switched to secure backup from netbackup utility.
    -Thanks
    Srinivas
    Message was edited by:
    Srinivas.R

    Hi,
    Our application is entirely Oracle-based, so OSB was a good fit. The solution originally had NBU as the backup technology but was very expensive (I spent several days fighting off the Symantec account manager), even after generous discounts.
    My experience of Oracle RMAN interfacing with NBU was patchy, but with OSB it "worked first time" - much more seamless. After some initial device configuration issues, we are now up and running in development, and I'm looking at rolling OSB out across 80 Solaris servers, including OAS and RAC servers.
    Cheers.

  • Veritas NetBackup using backint: error -8020 Reply buffer filled

    Hi All
    I'm trying to configure NetBackup on one of our SAP BW 7.0 system with MaxDB 7.6.00.35 running on Linux. I followed sap help and configure the backint. But when I execute the backup I'm getting the following error.
    Constructed the following reply:
    ERR
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    following is the dbm.ebp
    2007-06-26 21:35:40
    Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
    Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
    Using connection to Backint for MaxDB Interface.
    2007-06-26 21:35:40
    Checking existence and configuration of Backint for MaxDB.
    Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/BWA/backint/config' as path of the configuration file of Backint for MaxDB.
    Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB to configuration value '/sapdb/data/wrk/BWA/backint/config'.
    Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/BWA/backint/config'.
    Found keyword 'BACKINT' with value '/sapdb/BWA/db/bin/backint'.
    Found keyword 'INPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
    Found keyword 'OUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
    Found keyword 'ERROROUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/BWA/backint/adapter.para'.
    Found keyword 'TIMEOUT_SUCCESS' with value '600'.
    Found keyword 'TIMEOUT_FAILURE' with value '300'.
    Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/BWA/'.
    Finished reading of the Backint for MaxDB configuration file.
    Using '/sapdb/BWA/db/bin/backint' as Backint for MaxDB program.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in' as input file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/adapter.para' as parameter file for Backint for MaxDB.
    Using '600' seconds as timeout for Backint for MaxDB in the case of success.
    Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
    Using '/sapdb/data/wrk/BWA/dbm.knl' as backup history of a database to migrate.
    Using '/sapdb/data/wrk/BWA/dbm.ebf' as external backup history of a database to migrate.
    Checking availability of backups using backint's inquire function.
    Check passed successful.
    2007-06-26 21:35:40
    Checking medium.
    Check passed successfully.
    2007-06-26 21:35:40
    Preparing backup.
    Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
    Setting environment variable 'BI_REQUEST' to value 'NEW'.
    Setting environment variable 'BI_BACKUP' to value 'FULL'.
    Constructed Backint for MaxDB call '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
    B.in -c'.
    Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output for Backint for MaxDB.
    Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output for Backint for MaxDB.
    Writing '/backup/BWA/BWAPIPE #PIPE' to the input file.
    Prepare passed successfully.
    2007-06-26 21:35:40
    Creating pipes for data transfer.
    Creating pipe '/backup/BWA/BWAPIPE' ... Done.
    All data transfer pipes have been created.
    2007-06-26 21:35:40
    Starting database action for the backup.
    Requesting 'SAVE DATA QUICK TO '/backup/BWA/BWAPIPE' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BWAPIPE'' from db-kernel.
    The database is working on the request.
    2007-06-26 21:35:40
    Waiting until database has prepared the backup.
    Asking for state of database.
    2007-06-26 21:35:40 Database is still preparing the backup.
    Waiting 1 second ... Done.
    Asking for state of database.
    2007-06-26 21:35:41 Database is still preparing the backup.
    Waiting 2 seconds ... Done.
    Asking for state of database.
    2007-06-26 21:35:43 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2007-06-26 21:35:43
    Starting Backint for MaxDB.
    Starting Backint for MaxDB process '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
    B.in -c >>/sapdb/data/wrk/BWA/backint/backint4MAXDB.out 2>>/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Process was started successfully.
    Backint for MaxDB has been started successfully.
    2007-06-26 21:35:44
    Waiting for end of the backup operation.
    2007-06-26 21:35:44 The backup tool is running.
    2007-06-26 21:35:44 The database is working on the request.
    2007-06-26 21:35:49 The backup tool is running.
    2007-06-26 21:35:49 The database is working on the request.
    2007-06-26 21:35:59 The backup tool is running.
    2007-06-26 21:35:59 The database is working on the request.
    2007-06-26 21:36:14 The backup tool is running.
    2007-06-26 21:36:14 The database is working on the request.
    2007-06-26 21:36:34 The backup tool is running.
    2007-06-26 21:36:34 The database is working on the request.
    2007-06-26 21:36:41 The backup tool process has finished work with return code 2.
    2007-06-26 21:36:41 The database has finished work on the request.
    Receiving a reply from the database kernel.
    Got the following reply from db-kernel:
    SQL-Code :-8020
    Date :20070626
    Time :00213542
    Database :BWA
    Server :s254176rg04
    KernelVersion :Kernel 7.6.00 Build 035-123-139-084
    PagesTransfered :131072
    PagesLeft :2847194
    MediaName :BWAPIPE
    Location :/backup/BWA/BWAPIPE
    Errortext :end of file
    Label :DAT_000000025
    IsConsistent :true
    FirstLogPageNo :1777329
    DBStamp1Date :20070626
    DBStamp1Time :00213541
    BDPageCount :2978242
    DevicesUsed :1
    DatabaseID :s254176rg04:BWA_20070605_123955
    Max Used Data Page
    Converter Page Count :1604
    The backup operation has ended.
    2007-06-26 21:36:41
    Filling reply buffer.
    Have encountered error -24920:
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Constructed the following reply:
    ERR
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    2007-06-26 21:36:41
    Cleaning up.
    Removing data transfer pipes.
    Removing data transfer pipe /backup/BWA/BWAPIPE ... Done.
    Removed data transfer pipes successfully.
    Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
    Reading parameter file /sapdb/data/wrk/BWA/backint/adapter.para.
    Using staging area /sapdb/BWA/backintstage/stage1 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage2 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage3 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage4 with a size of 1073741824 bytes.
    Using 2 file per Backint for Oracle call.
    Using /sapdb/BWA/db/bin/backint as Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/initBWA.utl as parameterfile of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/BackintHistory as history file.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.in as input of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.out as output of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.err as error output of Backint for Oracle.
    Reading input file /sapdb/data/wrk/BWA/backint/backint4MAXDB.in.
    Backing up pipe /backup/BWA/BWAPIPE.
    Found 1 entry in the input file.
    Starting the backup.
    Starting pipe2file program(s).
    Waiting for creation of temporary files.
    1 temporary file is available for backup.
    Calling Backint for Oracle at 2007-06-26 21:36:40.
    Calling '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/initBWA.utl -i /sapdb/data/wrk/BWA/backint/backint4Oracle.in -c' .
    Backint for Oracle ended at 2007-06-26 21:36:40 with return code 2.
    Backint for Oracle output: Reading parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl.
    Backint for Oracle output:
    Backint for Oracle output:
    Backint for Oracle error output: No staging area is defined in the parameter file.
    Backint for Oracle error output: The path of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the history file is not defined in the parameter file.
    Backint for Oracle error output: The name of the input file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the output file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the error output file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output:
    Finished the backup unsuccessfully.
    #ERROR /backup/BWA/BWAPIPE
    End of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
    Removed Backint for MaxDB's temporary output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
    Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
    Backint for Oracle was unsuccessful.
    End of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
    Removed Backint for MaxDB's temporary error output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Removed the Backint for MaxDB input file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
    Have finished clean up successfully.
    Please help
    Thanks
    Andy

    Hi Natalia
    Thanks for the reply. Below is initBWA.utl file. At this stage The first staging file is successfully written to the tape and the backup fails after that. The problem I guess is the staging file is not getting deleted or over written after it is written to the tape. Thanks   
    backint parameters
    switch_list: is required and is used as a control file to communicate with
    BACKINT and BRBACKUP for online backups.  A switch list file is created
    every time BRBACKUP wants to backup a file or when it wants to indicate that
    a backup is finished.  The switch_list parameter must be set to a file path
    that is located in: $ORACLE_HOME/sapbackup/.switch.lis.
    switch_list /sapdb/BWA/backintstage/.switch.lis
    switch_sem: is required and is used as a control file which is used between
    BACKINT and BRBACKUP to communicate.  After the switch list file has been
    created and closed, BACKINT creates the switch semaphore file and waits until
    it is deleted by BRBACKUP.  The switch_sem parameter must be set to a file
    path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.
    switch_sem /sapdb/BWA/backintstage/.switch.sem
    switch_log: is required and is used as a control file which is used between
    BACKINT and BRBACKUP to communicate.  After the switch semaphore file has
    been deleted, BACKINT opens and reads the switch log file to determine if
    the process is successful.  The switch log file is created by BRBACKUP.  The
    switch_log parameter must be set to a file path that is located in:
    $ORACLE_HOME/sapbackup/.switch_log.
    switch_log /sapdb/BWA/backintstage/.switch.log
    backint_dir: is an optional parameter and must be set to a directory that is
    public.  BACKINT uses this directory for work space and to store files called
    backint.times, which keeps track of backup information.
    #backint_dir /oracle/SAP/sapscript/backint_dir
    server: is an optional parameter and is the machine name of the NetBackup
    Master server.   The NetBackup Master server is the name of the machine that
    provides most of the administration and control for Netbackup operations and
    contains the NetBackup database.  If BACKINT finds a $SAP_SERVER environment
    variable, the server parameter's value will be overriden by the value of
    $SAP_SERVER.  Also, if the server parameter is not specified and there is no
    environment variable then the server parameter value will default to the
    SERVER option specified in the Netbackkup bp.conf file.
    #server jupiter
    client: is an optional parameter and must be set to a machine name that has
    the NetBackup client software, an Oracle database, and a SAP environment.
    In some cases the server and client machine will be the same machine.  If
    BACKINT finds a $SAP_CLIENT environment variable, the client parameter value
    will be overriden by the assigned environment variable.  If the client
    parameter is not specified and there is no environment variable, then the
    client parameter value will default to the CLIENT_NAME specified in the
    Netbackkup bp.conf file.  If the value is not in bp.conf, BACKINT uses the
    value returned by the gethostname() libary function.
    #client jupiter
    drives: is an optional parameter and should be set to the number of
    simultaneous tape drives to kickoff backup. Set NetBackup Server to support
    multiple simultaneous client backups and the number of storage units/tape
    drives for this backup policy.  Based on the number of drives specified
    BACKINT will simultaneously run the same number of bpbackup/bprestore
    commands.  So for example, if the drives parameter is set to 5, then 5
    bpbackup/bprestore jobs will run at the same time.  The drives parameter
    should be set to the following rule:
    drives = Number of storage units per policy  X  MPX number
    The drives parameter value should not exceed the Set Maxium Jobs per Client
    global attribute.  If BACKINT finds a $SAP_DRIVES environment variable, the
    drive parameter value will be overriden by the value of the $SAP_DRIVES
    variable.  If the drive parameter is not specified and there is no
    environment variable, then BACKINT will exit with an error.
    #drives 1
    policy: is an optionl parameter and should be set to the name of a SAP policy
    type that has been defined in Netbackup.  The SAP policy must have a schedule
    type of Application Backup defined in order for BACKINT to work.  If BACKINT finds
    a $SAP_POLICY environment variable, the policy parameter value will be
    overriden by the value of the $SAP_POLICY variable.  If the policy parameter
    is not specified and there is no environment variable, then the policy
    parameter value will default to the BPBACKUP_POLICY option in the NetBackup
    bp.conf file.  By default, BPBACKUP_POLICY is not in any bp.conf file, then
    NetBackup uses the first SAP policy type that it finds that has the client
    and a user-directed backup schedule.
    policy AXON2541766-SAP
    schedule: Is optional and must be set to the name of type  Application Backup
    schedule that is associates with a SAP policy type.  The schedule can
    define aspects of the backup such as how long Netbackup retains images,
    maximum MPX per drive, storage unit, and volume pool.  If BACKINT finds a
    $SAP_SCHED environment variable, the schedule parameter value will be
    overriden by the value of the $SAP_SCHED environment variable.  If the
    schedule parameter is not specified and there is no environment variable,
    then the schedule parameter value will default to the BPBACKUP_SCHED option
    in the NetBackup bp.conf file.  By default BPBACKUP_SCHED is not in any
    bp.conf file then, NetBackup uses the first schedule of type Application Backup
    that it finds. It is higly recommended to set schedule parameter in *.utl file.
    #schedule Default-Application-Backup
    policy2: is optional and is the name of a policy to be used for the
    secondary SAP backup.  The secondary backup is performed for each SAP
    database backup on files that are needed to track SAP backup information.
    This option would be used to save the backup information on a different
    media.  If policy2 is not specified, then the policy parameter value is used.
    #policy2 sap_sec_backup
    schedule2: is optional and is the name of a Application Backup schedule to be
    used for the secondary SAP  backup.  The secondary backup is performed for
    each SAP database backup on files that are needed to track SAP backup
    information.  This option would be used to save the backup information on a
    different media.  If schedule2 is not specified, then the schedule parameter
    value is used.
    #schedule2 userbkps
    sort_backup_type: [size | custom | device | drive ]
    This parameter is optional and is used to specify four different backup
    sort option.  If sort_backup_type is not specified it will default to
    the size option.
    #sort_backup_type size
    sort_backup_type: [image | custom | drive ]
    This parameter is optional and is used to specify three different restore
    sort option.  If sort_restore_type is not specified it will default to
    the image option.
    #sort_restore_type image
    custom_sort_file: is optional and is used in conjunction with the
    sort_backup_type and sort_restore_type parameter.  If the custom option is
    specified on either the sort_backup_type or sort_restore_type parameter,
    then the custom_sort_file parameter needs to be set to a valid file.  The
    value for this parameter must be a full path name to a custom sort file and
    must have public permissions.
    #custom_sort_file /oracle/SAP/sapscripts/custom_sort_file
    master_time_offset:  is an option parameter used to restore old backups
    if there was a time difference between the master and client machines.
    This option should only be used for restoring 3.0 or older backup or if a
    backint restore can't find a specified backup.  The master_time_offset is
    specified in minutes.  The value will be subtract from the start time and
    added to the end time for a restore or inquire.
    #master_time_offset 2
    #sleep: is optional and is used to specify a sleep time to monitor the
    bpbackup or bprestore logs.  The default is 5 seconds.  When BACKINT is
    called a number of bpbackup/bprestore commands can be running at the
    sametime.  BACKINT monitors each command and display the information to the
    -o parameter.  In some cases bpbackup/bprestore information is not displayed
    because of the monitoring cycle.  Therefore this option is used mainly for
    debug reasons.
    #sleep 5
    policy_log: is optional and is the name of a policy to be used for
    backing up a second copy of an archive log.  If this option is specified
    then two backups will be performed on the same archive log.  The first
    backup will go to the "policy" name option and the second backup will go
    to the "policy_log" name option.
    #policy_log sap_archive_logs
    sched_log: is optional and is the name of a schedule to create a second
    backing up of an archive log.  If this option is specified then two backup
    will be performed on the same archive log.  The first backup will go to the
    "schedule" option and the second backup will be go to the "sched_log" and
    option.  The "sched_log" name must be a valid schedule name under the
    "policy_log" name option, otherwise it must be a valid schedule name under
    the "policy" name option.
    #sched_log Default-Application-Backup
    retry_backup: is an optional parameter and should be set to the number of
    retries for a failed backup.  If this option is specified BACKINT will
    retry a failed bpbackup job.  The number of retries is determine by the
    value on the retry_backup parameter.
    #retry_backup 2
    fail_backup: is optional and is used to stop the backup process immediately
    when an error occurs.  The standard behavior of BACKINT is to continue
    processing even in the event of an error and then report what files failed
    and what files were successful.  If this parameter is specified then BACKINT
    will stop process on the first error and report failures for all the
    files that were not backed up.
    #fail_backup
    media_notify_script: is optional and is used to call a script when a
    "Waiting mount" is displayed in a bpbackup/bprestore log.  The value for this
    option must be the full path name to a script.  The script should also have
    the right file permissions and should be tested before implementation.  If
    the message is encountered and this optional is specified, then the
    following commands will be executed from BACKINT:
      MEDIA_ID=A001;export MEDIA_ID
      NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
      /oracle/SAP/sapscripts/sap_media_notify
    #media_notify_script /oracle/SAP/sapscripts/sap_media_notify
    restore_filter: is optional and is used to resolve linked file paths on a
    restore.  This parameter should be commented out and should be used only on
    rare occassions.  The following are the cases were this parameter is needed:
      1) Oracle table spaces use file paths
      2) The directory paths to the Oracle table spaces are linked paths
      3) The linked directory paths don't exist at restore time
    The value for this parmater must be a fully qualified file path name to a
    script, which has the right permissions and has been tested before being
    implemented.  The script must have an input and output parameter and be able
    to modify the contents of a text file which contains file paths.  The script
    is responsible for converting linked directory paths into absolute directory
    paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for
    an example.
    #restore_filter /oracle/SAP/sapscripts/restore_filter.sh
    bplist_filter: is optional and is used to resolve linked file passes on an
    inquire.  This parameter should be commented out and should be used only on
    rare occassions.  Like the restore_filter_script parameter this is needed
    for the following cases:
      1) Oracle table spaces use file paths
      2) The directory paths to the Oracle table spaces are linked paths
      3) The linked directory paths don't exist at restore time
    The value for this option must be a fully qualified path name to a script,
    which has the right file permission and has been tested before being
    implemented.  The script must have an input and output parameter and be able
    to modify the contents of a text file, which contains file paths.  The script
    is responsible for converting absolute directory paths into linked directory
    paths.  This is just the opposite of the restore filter script. See
    /usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example.

  • Steps to  setup MML on veritas Netbackup to perform rman restore from tape

    RMAN backup is taken to tape...
    can anyone please give the steps to setup the MML on veritas Netbackup ...
    and also the steps to perform rman restore from tape to a new server ....
    Thanks in advance

    can u please answer them ..
    1)how to find out that the which tape is mounted on a backup server ?? command please ....
    2)how to find out that the rman backup was successful on the tape ?
    3)how to find out what are the tapes involved in that backup ?
    4)do u have to the create a auxillary database while restoring from rman by tape to a new server ?
    5)is there a way to findout how many GB completed in x timeframe by RMAN on oracle 11.2.0.2/10g and and oracle 9i during the backup process ??
    and also please answer ...
    #)RMAN backup is taken to tape...
    can anyone please give the steps to setup the MML on veritas Netbackup ...
    and also the steps to perform rman restore from tape to a new server ....
    and
    #)--- can i know the steps for the MML
    CATALOG command to define new locations
    ----May i know the commands

  • Sun c4 and veritas netbackup 6 mp4 installation

    Hello, please help me!
    We have SAN with 2 st6140 and 3 broacade 200e switch. One site is: two 200e and 3 linux hosts, other site is: v240 server (one FC port) with solaris preinstalled and installed Veritas NetBackup mp4, 1 200e switch, Sun C4 library whith FC ports.
    On second site I connected C4 FC host port to the 200e swith, FC port on v240 also connected to the 200e switch.
    Can you describe me a common porcedure to configure correctly a server with Veritas and C4?
    I cant add "device" in veritas Administration console now, because it cant see nothing.
    How i have to connect C4 and Veritas server to SAN correctly ?

    create a soft zone on your brocade , with your C4's FCs ports and your Netbackup Master server, for Netbackup use version 6.5 , not 6.0
    once you activate your zone, run cfgadm -al -o show_FCP_dev, you should be able to see your paths, one path or more paths from your server, two or more from your C4 libraries' fabrics, netbackuop 6.5 is very clean and installed , to be able to recognize your drivers ...once the software installed, go to your GUI, to configure device...
    Also, use the latest version of Solaris10 on this..it is much cleaner to work with netbackup 6.5

  • Required to take backup with out TSM in PROD server.

    Dear all,
    I required to take backup with out using TSM .
    we have got error in TSM . so that i am getting error .
    Prod server backup is working automated through TSM .
    now i need to take Online backup with out using TSM like DEV and QA (Manual backup) .
    For DEV and QA server backup is manual . i am simply moved the tape to tape library and fired the online backup as well same QA also .
    Now my query is reqiured to take backup with out the help of TSM in PROD server  . Is it possible ?
    2 profiles are configured for Online backup and offline backup .
    pls check the below profiles .
    initSIDdaily.sap -
    > Online backup .
    initSIDweekly.sap -
    > Offline backup
    is there any parameter i need to change ?
    Kindly advise

    Dear all ,
    I have initialised the Tape IRPB01 , after i have try to tkae backup , i got below error .
    BR0051I BRBACKUP 7.00 (48)
    BR0055I Start of database backup: bedqreyq.ant 2010-07-12 13.19.44
    BR0484I BRBACKUP log file: /oracle/IRP/sapbackup/bedqreyq.ant
    BR0477I Oracle pfile /oracle/IRP/102_64/dbs/initIRP.ora created from spfile /ora
    cle/IRP/102_64/dbs/spfileIRP.ora
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.45
    BR0319I Control file copy created: /oracle/IRP/sapbackup/cntrlIRP.dbf 15122432
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.46
    BR0057I Backup of database: IRP
    BR0058I BRBACKUP action ID: bedqreyq
    BR0059I BRBACKUP function ID: ant
    BR0110I Backup mode: ALL
    BR0077I Database file for backup: /oracle/IRP/sapbackup/cntrlIRP.dbf
    BR0061I 42 files found for backup, total size 158434.742 MB
    BR0143I Backup type: online
    BR0112I Files will not be compressed
    BR0130I Backup device type: tape
    BR0102I Following backup device will be used: /dev/rmt0.1
    BR0103I Following backup volume will be used: IRPB01
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.46
    BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
    c
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.52
    BR0257I Your reply: 'c'
    BR0259I Program execution will be continued...
    BR0208I Volume with name IRPB01 required in device /dev/rmt0.1
    BR0210I Please mount BRBACKUP volume, if you have not already done so
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.52
    BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
    c
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
    BR0257I Your reply: 'c'
    BR0259I Program execution will be continued...
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
    BR0226I Rewinding tape volume in device /dev/rmt0 ...
    BR0351I Restoring /oracle/IRP/sapbackup/.tape.hdr0
    BR0355I from /dev/rmt0.1 ...
    BR0241I Checking label on volume in device /dev/rmt0.1
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
    BR0226I Rewinding tape volume in device /dev/rmt0 ...
    BR0202I Saving /oracle/IRP/sapbackup/.tape.hdr0
    BR0203I to /dev/rmt0.1 ...
    BR0209I Volume in device /dev/rmt0.1 has name IRPB01
    BR0202I Saving init_ora
    BR0203I to /dev/rmt0.1 ...
    BR0202I Saving /oracle/IRP/102_64/dbs/initIRPdaily.sap
    BR0203I to /dev/rmt0.1 ...
    BR0280I BRBACKUP time stamp: 2010-07-12 13.19.59
    BR0198I Profiles saved successfully
    BR0280I BRBACKUP time stamp: 2010-07-12 13.20.00
    BR0315I 'Alter tablespace PSAPSR3 begin backup' successful
    BR0202I Saving /oracle/IRP/sapdata1/sr3_1/sr3.data1
    BR0203I to /dev/rmt0.1 ...
    BR0278E Command output of 'LANG=C dd obs=64k bs=64k if=/oracle/IRP/sapdata1/sr3_
    1/sr3.data1 of=/dev/rmt0.1':
    dd: /oracle/IRP/sapdata1/sr3_1/sr3.data1: Invalid argument
    BR0280I BRBACKUP time stamp: 2010-07-12 13.20.00
    BR0279E Return code from 'LANG=C dd obs=64k bs=64k if=/oracle/IRP/sapdata1/sr3_1
    /sr3.data1 of=/dev/rmt0.1': 2
    BR0222E Copying /oracle/IRP/sapdata1/sr3_1/sr3.data1 to/from /dev/rmt0.1 failed
    due to previous errors
    BR0280I BRBACKUP time stamp: 2010-07-12 13.20.02
    BR0317I 'Alter tablespace PSAPSR3 end backup' successful
    BR0056I End of database backup: bedqreyq.ant 2010-07-12 13.20.00
    BR0280I BRBACKUP time stamp: 2010-07-12 13.20.02
    BR0054I BRBACKUP terminated with errors
    BR0292I Execution of BRBACKUP finished with return code 5
    BR0668I Warnings or errors occurred - you can continue to ignore them or go back
    to repeat the last action
    BR0280I BRTOOLS time stamp: 2010-07-12 13.20.02
    BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
    Kindly Advise

  • I have just upgraded to Mavericks and have been using Time Machine on an external disk with Snow Leopard.  Can I continue to backup with Time Machine on the same external disk or do I need a new disk since the operating system has changed?

    I have just upgraded to Mavericks and have been using Time Machine on an external disk with Snow Leopard.  Can I continue to backup with Time Machine on the same external disk or do I need a new disk since the operating system has changed?

    Hi there,
    I found that Time Machine in Mavericks will sort it all out for you. You shouldn't need to buy another backup drive, unless you have insufficient space left and can't afford to delete whats on there. It should just work fine.

  • How can I create a new TC backup with ethernet, so I don't have to wait two days for a new wireless backup?

    How can I create a new TC backup with ethernet, so I don't have to wait two days for a new wireless backup?
    Several times in the last year, I've gotten a message that Time Machine needs to completely redo my backup. Using the wireless connection, this takes almost two days. Is there a way to do the backup with ethernet and then switch back to wireless? Thanks.

    May I know what is needed to make sure the MacBook is able to see Time Capsule on ethernet?
    Connect an Ethernet cable from one of the LAN <-> ports on the 2Wire gateway to the WAN port (circle of dots icon) on the Time Capsule.
    If AirPort Utility cannot "see" the Time Capsule now, you will need to perform a "hard reset" by holding in the reset button for 7-8 seconds or so and then reconfigure the Time Capsule. You can use the same Time Capsule name and password, etc. as before.
    Configure the Time Capsule to "Create a wireless network" and select the Bridge Mode option when it appears during the setup using AirPort Utility.
    Once the Time Capsule is configured, restart the entire network again. Power down everything, start the 2Wire first and then start each other device after that one at a time about a minute apart.
    Now you can connect your Mac directly to one of the LAN <-> ports on the Time Capsule for the backup using another Ethernet cable. In general, about 20-25 GB per hour will transfer.
    The Time Capsule will broadcast a much faster wireless network than the 2Wire can provide, so you might want to leave the setup "as is" for awhile after the first backup is complete. If you decide to use the Time Capsule as your main wireless access point, you would want to turn the wireless off on the 2Wire since two wireless networks in close proximity can create interference problems.
    Or, if you want to use the wireless on the 2Wire, you could turn off the wireless on the Time Capsule. Then backups will occur over the 2Wire wireless, or over Ethernet.
    I don't really recommend the "Join a wireless network" setting on the Time Capsule for most users, but you could go back to that setup as well if you want after the first backup is complete.

  • How can i use "icloud backup" with ios 4.2.1?

    How can i use "icloud backup" with ios 4.2.1? I tried to update my ihpone 3G wih the newest IOs. Seems not to be possible.

    You cannot.
    It requires ios 5.
    Your iphone can only go to 4.2.1

  • Error in backup with verification in DB13

    Dear all,
    I am taking backup through DB13. There is two options in that with verification & without verification. when i am taking backup without verification , it is completed succesfuly, but when i am taking backup with verification, there is some error.
    I am giving the error lines....
    BR0428W File /oracle/BWD/sapreorg/bwd.data1 will be overwritten  
    BR0278E Command output of '/oracle/BWD/920_64/bin/dbv file=/oracle/BWD/sapreorg/bwd.data1 blocksize=8192':
    DBVERIFY: Release 9.2.0.6.0 - Production on Thu Nov 6 16:08:07 2008
    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
    DBV-00102: File I/O error on FILE (/oracle/BWD/sapreorg/bwd.data1) during end read operation (-1)
    BR0280I BRBACKUP time stamp: 2008-11-06 16.08.07
    BR0279E Return code from '/oracle/BWD/920_64/bin/dbv file=/oracle/BWD/sapreorg/bwd.data1 blocksize=8192': 1
    BR0397E Verification of backup of /oracle/BWD/sapreorg/bwd.data1 using DBVERIFY failed due to previous errors
    BR0056I End of database backup: bdzeuhyo.ant 2008-11-06 16.08.07
    BR0280I BRBACKUP time stamp: 2008-11-06 16.08.10
    BR0054I BRBACKUP terminated with errors
    Plz help me to solve this error.
    Thanks & Regards,
    Ankit Gupta

    There is no problem if you delete oracle/BWD/sapreorg/bwd.data1 prior to backup. It will come again since you are using Verify option with BRBACKUP.
    What happens when you use verify option is Once the backup phase is complete, all the saved files are restored from the volume (for example, tape) in sequence to the temperory directory (in this case /oracle/BWD/sapreorg), decompressed (when compress = yes was used), read by the check program, and compared with the originals. And the check program being used is dbverify (command dbv).
    The problem may not be with oracle/BWD/sapreorg/bwd.data1, it may be with the original datafile bwd.data1. What you can do is,
    Run dbv on all your datafiles and check for errors. (recommend to run dbv when database is offline)
    If dbv returns an error, then fix that.
    If there are no errors reported by dbv, then your database is perfect.
    The reason why BRBACKUP gave the error in such a case, as i see it is, since you are doing an online backup, the datafile is first backed up to a backup media. Since verify is ON, the file is restored to the temperory folder. Some changes (even if minor) may occur in the datafile within this time frame and the comparison fails.
    Another chance is if there is no enough space in sapreorg and the restored datafile is not complete.
    If you get an error like "DBV-00102: File I/O error on FILE (/oracle/BWD/sapdata1/bwd.data1) during end read operation (-1)" on the original datafile, then, resizing of the datafile may help.Not sure though.
    Please refer the link http://help.sap.com/saphelp_nw04/Helpdata/EN/0d/d30c774a0c11d182b80000e829fbfe/content.htm

Maybe you are looking for

  • Vertical single item Report

    Hi, I have a small app where I register clients for demo. After I register them, I need to send them a registration confirmation with all the details (Location address, and details of demo) The process is: 1) I use a form to enter their registration

  • HT1695 how do i activate my iphone 4 after upgrading to ioS 5.1

    how do i activate my iphone 4 after upgrading to ioS 5.1

  • Horizontal black/dotted lines on Apple Studio Display

    As of about six hours ago, my screen is suddenly showing several horizontal 1px thick lines at the top of the screen; they are usually black but sometimes change to alternating black and white dotted line when a window is moved around in the area the

  • 400 RAM instead of 333 ina 1,25 iMac

    I tried to buy new DDR 2700 333 RAM to upgrade my 1,25 iMac, but I can only find SO-DIMM modules, no stock of the desktop ones. In every shop i ask for I've been told I can use 400 DDR RAM instead of 333 with no problem, but some sellers tell me I ca

  • After Effects error : layer does not have a source.

    Hi All,           I add a Text layer and then add my custom fill  effect to it. Then I call AdvItemSuite1()->PF_ForceRerender(in_data, &(params[0]->u.ld)) from AEGP for all the layers. But only for Text layer, AE pops up a dialog displaying the follo