MAXDB Force Log Backup
Hi All,
I am facing an issue in generating the Log backup. The scenario is given below:
1. Most of the users will not work on the system. If we can see the previous data, for one week only 20 MB of log will be written.
2. And I want to enable time controlled Log Backup on this system. So I have followed the note 869267 and enable the interval using the command -- autolog_on <medium> INTERVAL <time in secs>.
3. Now I am not able to get the logs backed up for every 15 minutes.
So Please can anyone of you tell me how to forcefully write the log for every 15 mins.
Best Regards,
GK.
Hi GK,
> My concern is, irrespective of whether users work or not on the system, it has to generate a log for every 15min.
Yes, I got that the first time
Anyhow, for MaxDB this is a nonsense operation. If there are no changes to the database then there are no log entries and thus no log to be backed up.
We never "make up" entries there and we don't copy data/redo files during backup.
We save the data we have to new files
> The same we have enabled on Oracle Database and it is working fine for some systems like Enterprise Portal. HI GK,
And that is a nice idea for Oracle - but just because of the way Oracle redo log files and the redo log archiving works.
For Oracle - at least for the user managed backups (you know, BEGIN BACKUP/END BACKUP, not RMAN - you want to perform log file switches to have a kind of "sync"-point between log and data files.
That concept of redo log files and the switches between them just don't exist with MaxDB.
For MaxDB the log area is a rather contiguous space where we put in our log data.
On backup time we write out portions of it to the backup medium (the portions are called LOG BACKUP SEGMENTS).
We don't need to "finish" one file of the log area to be able to do that.
And we always "know" at what position in the log area our most current entry resides - thus we don't need the extra "sync" point.
You may want to read more about how logging works in MaxDB [>here<|http://maxdb.sap.com/training/internals_7.6/logging_EN_76.pdf].
To close, your current setup is doing exacty what you want to archive.
You don't want to get an empty file every 15 min. but you want to make sure that - should there be any changes to the database - that the log entries for those are backed up within the following 15 mins.
That's what you got here.
Cheers,
Lars
Similar Messages
-
Hello,
the LOG backup of the database crashes with following error:
ERR
-24988,ERR_SQL: sql error
-8888,connection broken [183]
KNLDIAG
2005-12-06 14:18:56 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:18:56 0x370 19651 CONNECT Connection released, T4
2005-12-06 14:18:56 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:18:56 0x370 19651 CONNECT Connection released, T4
2005-12-06 14:19:57 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:19:59 0x370 19615 VOLUMEIO Attaching volume 'F:\sapdb\EXI\saplog\DISKL001'
2005-12-06 14:19:59 0x9C8 19613 DBSTATE I/O thread for 'F:\sapdb\EXI\saplog\DISKL001' started
2005-12-06 14:19:59 0x370 19617 VOLUMEIO Single I/O attach, 'F:\sapdb\EXI\saplog\DISKL001', UKT:3
2005-12-06 14:19:59 0xCB4 19625 IO Async I/O thread started, 'H:\Sicherung_XI\logs\EXI_LOG.017
2005-12-06 14:19:59 0xEE0 52101 SAVE Filetype: file
2005-12-06 14:19:59 0xEE0 52024 SAVE 200 pages -> "erung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:04 0xEE0 52024 SAVE 10800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:09 0xEE0 52024 SAVE 20000 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:14 0xEE0 52024 SAVE 29400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:19 0xEE0 52024 SAVE 39000 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:24 0xEE0 52024 SAVE 48200 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:29 0xEE0 52024 SAVE 57600 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:34 0xEE0 52024 SAVE 66800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:39 0xEE0 52024 SAVE 76400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:44 0xEE0 52024 SAVE 85400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:49 0xEE0 52024 SAVE 94800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:54 0xEE0 52024 SAVE 104000 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:20:59 0xEE0 52024 SAVE 113200 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:21:04 0xEE0 52024 SAVE 122600 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:21:09 0xEE0 ERR 0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
2005-12-06 14:21:09 0xEE0 ERR 18196 DBCRASH vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
current write position -
KNLDIAG.ERR
2005-12-06 14:18:41 --- Starting GMT 2005-12-06 13:18:41 7.5.0 Build 031-123-104-253
2005-12-06 14:21:09 0xEE0 ERR 0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
2005-12-06 14:21:09 0xEE0 ERR 18196 DBCRASH vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
in online mode the database works fine, also a full backup...
Regards,
DomiHi,
the reason for the problem might be a partially written logpage on a logvolume, or a non-written, but expected logpage. If this page is not found, the logbackup throws the error you received. This should be a very rare error.
In order to solve this, you could try the following:
1. Then bring the database instance to mode <b>online</b>
2. Then bring the database instance to mode <b>admin</b>
3. Clear the log:
dbmcli -d <SID> -u <controluser>,<controlpasswd> -uUTL <controluser>,<controlpasswd> util_execute clear log
4. Perform full data backup
5. Perform log backup
Regards,
Roland
P.S.: the clear log command is a 'dangerous' command, please don't use it otherwise. -
Maxdb restore - transaction log backup
Hi,
Is it possible to restore the db backup without the transaction log backup? I know this is kinda lame to ask this but just wondering if this is possible and how it can be done.
Database is MaxDB and OS is Linux.
Thanks in advance!Hi,
the restore does not depend onto the database state in which the databackup has been made.
Instead you are able to recover every complete databackup without a logrecovery. You can do this by using the dbmcli command DB_ACTIVATE RECOVER <medium_name> or the corresponding dbmgui actions.
After the recovery you simply need to restart the database.
Kind regards, Martin -
Hello!
How do I force a log switch using dbmcli?
For data protection purpose I would like to do this on daily basis.
The system has autolog=on, and I run the backups using dbmcli via crontab on a linux box. MaxDB version is 7.6.01.12
Regards,
Fredrik
Message was edited by:
Fredrik Rosengren
Message was edited by:
Fredrik RosengrenHi Fredrik,
with Oracle Databases you use logswitches to get online redo logs copied to archive logs even when these online redo logs are not yet completely filled.
Basically you just want to make sure to have the latest changes in your backup too.
Well in MaxDB there is no "switch logfile" because there is no such thing as the logfiles. And there is also no limitation like the one of Oracle when backing up log data.
If you want to backup each and all not yet backed up log entries: no problem!
Deactivate the automatic log backup, perform a manual log backup and restart the automatic logbackup.
The log segments in MaxDB are not like the online redo logfiles of oracle. They are just markers in the logarea that are used by the autolog features to know "oh, there had been some changes again - let's do a backup of that now".
You may also want to have a look into this note:
<a href="https://websmp206.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=869267&_NLANG=E">#869267 - FAQ: MaxDB LOG area</a>
KR Lars -
Getting error while taking MAX DB trans log backup.
Hi,
I am getting error while taking trans log backup of Maxdb database for archived log through data protector as below,
[Critical] From: OB2BAR_SAPDBBAR@ttcmaxdb "MAX" Time: 08/19/10 02:10:41
Unable to back up archive logs: no autolog medium found in media list
But i am able to take complete data and incremental backup through data protector.
I have already enabled the autolog for MAX DB database and it is writing that log file directly to HP-UX file system. Now i want to take backup of this archived log backup through data protector i.e. through trans log backup. So that the archived log which is on the file system after trans log backup completed will delete the archived logs in filesystem. So that i don;t have to manually delete the archived logs from file system.
Thanks,
SubbaHi Lars,
Thanks for the reply...
Now i am able to take archive log backup but the problem is i can take only one archive file backup. Not multiple arhive log files generated by autolog at filesystem i.e /sapdb/MAX/saparch.
I have enabled autolog and it is putting auto log file at unix directory i.e. /sapdb/MAX/saparch
And then i am using the DataProtector 6.11 with trans log backup to backup the archived files in /sapdb/MAX/saparch. When i start the trans backup session through data protector it uses the archive stage command as "archive_stage BACKDP-Archive LOGBackup NOVERIFY REMOVE" If /sapdb/MAX/saparch has only one archive file it will backup and remove the file successfully. But if /sapdb/MAX/saparch has multiple archive files it gives an error as below,
Preparing backup.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'OLD'.
Setting environment variable 'BI_BACKUP' to value 'ARCHIVE'.
Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.
bsi_in -c'.
Created temporary file '/var/opt/omni/tmp/MAX.bsi_out' as output for Backint for MaxDB.
Created temporary file '/var/opt/omni/tmp/MAX.bsi_err' as error output for Backint for MaxDB.
Writing '/sapdb/data/wrk/MAX/dbm.ebf' to the input file.
Writing '/sapdb/data/wrk/MAX/dbm.knl' to the input file.
Prepare passed successfully.
Starting Backint for MaxDB.
Starting Backint for MaxDB process '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.
bsi_in -c >>/var/opt/omni/tmp/MAX.bsi_out 2>>/var/opt/omni/tmp/MAX.bsi_err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
Waiting for the end of Backint for MaxDB.
2010-09-06 03:15:21 The backup tool is running.
2010-09-06 03:15:24 The backup tool process has finished work with return code 0.
Ended the waiting.
Checking output of Backint for MaxDB.
Have found all BID's as expected.
Have saved the Backup History files successfully.
Cleaning up.
Removing data transfer pipes.
Removing data transfer pipe /var/opt/omni/tmp/MAX.BACKDP-Archive.1 ... Done.
Removed data transfer pipes successfully.
Copying output of Backint for MaxDB to this file.
Begin of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
#SAVED 1009067:1 /sapdb/data/wrk/MAX/dbm.ebf
#SAVED 1009067:1 /sapdb/data/wrk/MAX/dbm.knl
End of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/MAX.bsi_out'.
Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
End of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/MAX.bsi_err'.
Removed the Backint for MaxDB input file '/var/opt/omni/tmp/MAX.bsi_in'.
Have finished clean up successfully.
The backup of stage file '/export/sapdb/arch/MAX_LOG.040' was successful.
2010-09-06 03:15:24
Backing up stage file '/export/sapdb/arch/MAX_LOG.041'.
Creating pipes for data transfer.
Creating pipe '/var/opt/omni/tmp/MAX.BACKDP-Archive.1' ... Done.
All data transfer pipes have been created.
Preparing backup tool.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'OLD'.
Setting environment variable 'BI_BACKUP' to value 'ARCHIVE'.
Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.bsi_
in -c'.
Created temporary file '/var/opt/omni/tmp/MAX.bsi_out' as output for Backint for MaxDB.
Created temporary file '/var/opt/omni/tmp/MAX.bsi_err' as error output for Backint for MaxDB.
Writing '/var/opt/omni/tmp/MAX.BACKDP-Archive.1 #PIPE' to the input file.
Prepare passed successfully.
Constructed pipe2file call 'pipe2file -d file2pipe -f /export/sapdb/arch/MAX_LOG.041 -p /var/opt/omni/tmp/MAX.BACKDP-Archive.1 -nowait'.
Starting pipe2file for stage file '/export/sapdb/arch/MAX_LOG.041'.
Starting pipe2file process 'pipe2file -d file2pipe -f /export/sapdb/arch/MAX_LOG.041 -p /var/opt/omni/tmp/MAX.BACKDP-Archive.1 -nowait >>/var/tmp/tem
p1283767880-0 2>>/var/tmp/temp1283767880-1'.
Process was started successfully.
Pipe2file has been started successfully.
Starting Backint for MaxDB.
Starting Backint for MaxDB process '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.bsi_
in -c >>/var/opt/omni/tmp/MAX.bsi_out 2>>/var/opt/omni/tmp/MAX.bsi_err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
Waiting for end of the backup operation.
2010-09-06 03:15:25 The backup tool process has finished work with return code 2.
2010-09-06 03:15:25 The backup tool is not running.
2010-09-06 03:15:25 Pipe2file is running.
2010-09-06 03:15:25 Pipe2file is running.
2010-09-06 03:15:30 Pipe2file is running.
2010-09-06 03:15:40 Pipe2file is running.
2010-09-06 03:15:55 Pipe2file is running.
2010-09-06 03:16:15 Pipe2file is running.
Killing not reacting pipe2file process.
Pipe2file killed successfully.
2010-09-06 03:16:26 The pipe2file process has finished work with return code -1.
The backup operation has ended.
Filling reply buffer.
Have encountered error -24920:
The backup tool failed with 2 as sum of exit codes and pipe2file was killed.
Constructed the following reply:
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes and pipe2file was killed.
Reply buffer filled.
Cleaning up.
Removing data transfer pipes.
Removing data transfer pipe /var/opt/omni/tmp/MAX.BACKDP-Archive.1 ... Done.
Removed data transfer pipes successfully.
Copying output of Backint for MaxDB to this file.
Begin of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
End of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/MAX.bsi_out'.
Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
End of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/MAX.bsi_err'.
Removed the Backint for MaxDB input file '/var/opt/omni/tmp/MAX.bsi_in'.
Copying pipe2file output to this file.
Begin of pipe2file output (/var/tmp/temp1283767880-0)----
End of pipe2file output (/var/tmp/temp1283767880-0)----
Removed pipe2file output '/var/tmp/temp1283767880-0'.
Copying pipe2file error output to this file.
Begin of pipe2file error output (/var/tmp/temp1283767880-1)----
End of pipe2file error output (/var/tmp/temp1283767880-1)----
Removed pipe2file error output '/var/tmp/temp1283767880-1'.
Have finished clean up successfully.
The backup of stage file '/export/sapdb/arch/MAX_LOG.041' was unsuccessful.
2010-09-06 03:16:26
Cleaning up.
Have encountered error -24919:
Can not remove file '/var/tmp/temp1283767880-0'.
(System error 2; No such file or directory)
Could not remove temporary output file of pipe2file ('/var/tmp/temp1283767880-0' ).
Have encountered error -24919:
Can not remove file '/var/tmp/temp1283767880-1'.
(System error 2; No such file or directory)
Could not remove temporary output file of pipe2file ('/var/tmp/temp1283767880-1' ).
Have finished clean up successfully.
Thanks,
Subba -
RMAN never deletes archive log backups
Hi all,
I have same problem as some of you have already faced.
I have some instances 10.2.0.4 running un archive log mode.
I take full hot backup daily.
I setup a rman script to backup and delete obsolete backups according to the following policy:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
and then:
run {
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
CROSSCHECK ARCHIVELOG ALL;
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
crosscheck archivelog all;
delete noprompt archivelog all completed before 'sysdate -2';
DB full backups are being deleted, however archive logs backups are not deleted.
There are no tablespaces in backup or offline mode.
How can I know the reason why some archive log backups are kept ?
Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
Thanks in advance.Hi Fernando,
This are the ouputpus of the commands:
RMAN> REPORT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> LIST BACKUP OF ARCHIVELOG ALL;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
1090 69.65M DISK 00:00:16 23-FEB-11
BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
List of Archived Logs in backup set 1090
Thrd Seq Low SCN Low Time Next SCN Next Time
1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1411 125.43M DISK 00:00:28 24-FEB-11
BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
List of Archived Logs in backup set 1411
Thrd Seq Low SCN Low Time Next SCN Next Time
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1600 164.40M DISK 00:00:37 25-FEB-11
BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
List of Archived Logs in backup set 1600
Thrd Seq Low SCN Low Time Next SCN Next Time
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1829 132.24M DISK 00:00:30 26-FEB-11
BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
List of Archived Logs in backup set 1829
Thrd Seq Low SCN Low Time Next SCN Next Time
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2058 218.03M DISK 00:00:48 27-FEB-11
BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
List of Archived Logs in backup set 2058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2298 205.39M DISK 00:00:45 28-FEB-11
BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
List of Archived Logs in backup set 2298
Thrd Seq Low SCN Low Time Next SCN Next Time
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2546 180.29M DISK 00:00:39 01-MAR-11
BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
List of Archived Logs in backup set 2546
Thrd Seq Low SCN Low Time Next SCN Next Time
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
2801 85.40M DISK 00:00:19 02-MAR-11
BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
List of Archived Logs in backup set 2801
Thrd Seq Low SCN Low Time Next SCN Next Time
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3058 137.93M DISK 00:00:30 03-MAR-11
BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
List of Archived Logs in backup set 3058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3324 138.96M DISK 00:00:31 04-MAR-11
BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
List of Archived Logs in backup set 3324
Thrd Seq Low SCN Low Time Next SCN Next Time
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3597 178.07M DISK 00:00:39 05-MAR-11
BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
List of Archived Logs in backup set 3597
Thrd Seq Low SCN Low Time Next SCN Next Time
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3835 198.44M DISK 00:00:43 06-MAR-11
BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
List of Archived Logs in backup set 3835
Thrd Seq Low SCN Low Time Next SCN Next Time
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4131 185.94M DISK 00:00:40 07-MAR-11
BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
List of Archived Logs in backup set 4131
Thrd Seq Low SCN Low Time Next SCN Next Time
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4435 161.37M DISK 00:00:35 08-MAR-11
BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
List of Archived Logs in backup set 4435
Thrd Seq Low SCN Low Time Next SCN Next Time
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4745 79.24M DISK 00:00:18 09-MAR-11
BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
List of Archived Logs in backup set 4745
Thrd Seq Low SCN Low Time Next SCN Next Time
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
5270 135.13M DISK 00:00:31 10-MAR-11
BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
List of Archived Logs in backup set 5270
Thrd Seq Low SCN Low Time Next SCN Next Time
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
RMAN>
For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
I'd like to understand why it happens :-)
Thanks a lot,
Regards,
Diego. -
hello,
if i try to use DB13 for relo log backup it gives error as
Job started
Step 001 started (program RSDBAJOB, variant &0000000000286, user name BASIS)
Execute logical command BRARCHIVE On host dmrctst
Parameters: -u / -c force -p initQAS.sap -cds -v QAS_TUE2_00
BR002I BRARCHIVE 6.10 (76)
BR157E Value 'QAS_TUE2_00' for option '-v' longerthan 10 characters
BR007I End of offline redo log processing: adxynlbm.log 2008-05-19 18.39.22
BR280I Time stamp 2008-05-19 18.39.22
BR005I BRARCHIVE terminated with errors
External program terminated with exit code 3
BRARCHIVE returned error status E
Job finished
how should i take backup of redo logs,we are using 4.6C version?
-saurabh"BR157E Value 'QAS_TUE2_00' for option '-v' longerthan 10 characters"
This is the pertinent bit. Your naming convention for your media does not comply with the limitations ..... i.e, change your tape name to be 10 or less characters. -
Force logging in archivelog mode
Hi !!!
What happen if I have "force_logging" parameter set to true when the database is in archivelog mode ?
Thanks.rarain wrote:
Hi Juamd,
You should only use this option when it is really required because this option will forcibly generate redo for all Nologging operations that means you might find more archives and you need to setup more space for archive.
Normally we use this option when we need to replicate data changes from one database to another database like in standby configuration, Golden Gate replication etc. I would suggest you to monitor Redo amount generated after enabling this option and accordingly estimate archive space and backup space for archive.
Thanks...Ah, don't agree with that at all. You can compromise your recovery if you happen to want to restore to a point-in-time when there was a NOLOGGING operation going on. Fine, if it's an index, but if it happens to be on a table...
(Yes, been there, done that - with a non-Production database, thankfully)
This is one of the 'must haves', IMO, for Production - set it at the database-level and it overrides any tablespace or object setting.
Archivelogs are generated for a reason. If you have a particular operation that really does massively benefit from NOLOGGING and is something you are sure that you simply re-run/re-create yourself, fine. If not, by default, you really should FORCE LOGGING. -
Whole database offline + redo log backup Scheduling failed
Hi Experts,
In DB13 I have the following Issue, Whole database offline + redo log backup Scheduling failed.
How to solve this.Hi,
Below is the Log details,
BR0120I Control files
File Size Id. Device Link Type
/oracle/PRD/origlogA/cntrl/cntlrPRD.dbf 13975552 0 5578783 NOLINK FILE
/oracle/PRD/origlogB/cntrl/cntrlPRD.dbf 13975552 0 5578784 NOLINK FILE
/oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf 13975552 0 5578772 NOLINK FILE
BR0616I Tablespaces in table TSORA for SAP owner SAPSR3:
PSAPSR3, PSAPSR3700, PSAPSR3USR
BR0227E Not enough disk space in /test123/PRDBK for backup, missing at least 149478.274 MB
BR0056I End of database backup: behzgxph.afd 2012-02-28 03.05.40
BR0280I BRBACKUP time stamp: 2012-02-28 03.05.40
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2012-02-28 03.05.40
BR0291I BRARCHIVE will be started with options '-U -jid ALGOF20110129030500 -d disk -c force -p initPRD.sap -sd'
BR0280I BRBACKUP time stamp: 2012-02-28 03.06.09
BR0292I Execution of BRARCHIVE finished with return code 0 -
Redo log backup to disk is failed
Hi,
My Archive log backup to disk is failed
BR0002I BRARCHIVE 7.00 (13)
BR0006I Start of offline redo log processing: aeamsbyx.svd 2009-05-04 15.15.07
BR0477I Oracle pfile E:\oracle\DV1\102\database\initDV1.ora created from spfile E:\oracle\DV1\102\database\spfileDV1.ora
BR0101I Parameters
Name Value
oracle_sid DV1
oracle_home E:\oracle\DV1\102
oracle_profile E:\oracle\DV1\102\database\initDV1.ora
sapdata_home E:\oracle\DV1
sap_profile E:\oracle\DV1\102\database\initDV1.sap
backup_dev_type disk
archive_copy_dir W:\oracle\DV1\sapbackup
compress no
disk_copy_cmd copy
cpio_disk_flags -pdcu
archive_dupl_del only
system_info SAPServiceDV1 SAP2DQSRV Windows 5.2 Build 3790 Service Pack 1 Intel
oracle_info DV1 10.2.0.2.0 8192 21092 71120290
sap_info 46C SAPR3 DV1 W1372789206 R3_ORA 0020109603
make_info NTintel OCI_10103_SHARE Apr 5 2006
command_line brarchive -u / -c force -p initDV1.sap -sd
BR0013W No offline redo log files found for processing
BR0007I End of offline redo log processing: aeamsbyx.svd 2009-05-04 15.15.11
BR0280I BRARCHIVE time stamp: 2009-05-04 15.15.11
BR0004I BRARCHIVE completed successfully with warnings
I have checked the target directory nothing is backed up and gone through few SAP notes 10170, 17163, 132551, 490976 and 646681 but nothing is helped.
And anohter question is in DB13 Calander --> Schedule an action pattern maximum I can backup only 1 month redo logs. But I have 3 months redo log files are there. How can I back up those files.
Our environment is SAP R/3 4.6C, windows 2003 and Oracle 10.2.0.2.0
Please some one help me on this.
Thanks and Regards
SatyaUpdate your BRTools. They are very old.
Check that your DB is in archive-log-mode. If no enable it.
testing backup
- run a online backup
- run "sqlplus / as sysdba"
- SQL> alter system switch logfile; ... this switches the current online log... a new log will written to oraarch.
- run a archivelog backup
... now you should have complete db-backup with minimum 1!!! archive log.
Now you can delete old redologs from oraarch.
If this doesn't work and your database is in archive-log-mode:
- shutdown sap and oracle
- MOVE all redologs from oraarch to a other location manually... no more files should be on oraarch
- run a offline backup
If the offline backup was running successfully you can delete the prior moved redologs. The backup is consistent and the redologs will no more required.
- start oracle and sap
Oracle should now write new redologs to oraarch. Test online backup!
Edited by: Thomas Rudolph on May 6, 2009 10:16 PM
Edited by: Thomas Rudolph on May 6, 2009 10:17 PM -
Hi,
My redo log backup failed and I've no clue on the errors. Below is the job log. Please advise. TIA !
Job started
Step 001 started (program RSDBAJOB, variant &0000000000064, user ID BACKUP_USER)
No application server found on database host - rsh/gateway will be used
Execute logical command BRARCHIVE On host bering
Parameters:-u / -jid LOG__20090313130000 -c force -p initprd.sap -cds
SXPG_COMMAND_EXECUTE(LONG)
COMMANDNAME = BRARCHIVE
OPERATINGSYSTEM = ANYOS
TARGETSYSTEM = bering
DESTINATION = SAPXPG_DBDEST_BERING
BR0002I BRARCHIVE 7.00 (32)
BR0181E Option '-cds' not supported for 'disk'
BR0007I End of offline redo log processing: aeactnyg.log 2009-03-13 13.00.19
BR0280I BRARCHIVE time stamp: 2009-03-13 13.00.21
BR0005I BRARCHIVE terminated with errors
External program terminated with exit code 3
BRARCHIVE returned error status E
Job finished
DLHi,
You tried to backup redo log on disk.
Option -cds (create second copy, delete and the first copy serial) is not supported when you do a redolog backup using disk as backup device type.
Try to change the option to -sd (save first copy and delete)
rgds,
fendhy. -
Hi everyone,
When I'm scheduling Archive log backup through DB13 the backup are failing.
Here is the logfile of the failed Redo log backup file.
2008-09-03 14:45:05 Job started
2008-09-03 14:45:05 Step 001 started (program RSDBAJOB, variant &0000000000014, user ID ROHANKU)
2008-09-03 14:45:05 Execute logical command BRARCHIVE On host ncsdev12
2008-09-03 14:45:05 Parameters:-u / -jid LOG__20080903144505 -c force -p initRD1.sap -cds
2008-09-03 14:45:53 BR0002I BRARCHIVE 7.00 (24)
2008-09-03 14:45:53 BR0006I Start of offline redo log processing: adystlhx.cds 2008-09-03 14.45.05
2008-09-03 14:45:53 BR0484I BRARCHIVE log file: /hcs/oracle/RD1/saparch/adystlhx.cds
2008-09-03 14:45:53 BR0477I Oracle pfile /hcs/oracle/RD1/102_64/dbs/initRD1.ora created from spfile /lms/oracle/RD1/102_64/dbs/spfileRD1.ora
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.07
2008-09-03 14:45:53 BR0008I Offline redo log processing for database instance: RD1
2008-09-03 14:45:53 BR0009I BRARCHIVE action ID: adystlhx
2008-09-03 14:45:53 BR0010I BRARCHIVE function ID: cds
2008-09-03 14:45:53 BR0048I Archive function: copy_delete_save
2008-09-03 14:45:53 BR0011I 1 offline redo log file found for processing, size 41.846 MB
2008-09-03 14:45:53 BR0130I Backup device type: util_file
2008-09-03 14:45:53 BR0109I Files will be saved by backup utility
2008-09-03 14:45:53 BR0134I Unattended mode with 'force' active - no operator confirmation allowed
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.07
2008-09-03 14:45:53 BR0229I Calling backup utility with function 'backup'...
2008-09-03 14:45:53 BR0278I Command output of '/usr/sap/RD1/SYS/exe/run/backint -u RD1 -f backup -i /lms/oracle/RD1/saparch/.adystlhx.lst -t file -p
2008-09-03 14:45:53 ERROR - Failed to get the policy method type: LNSDQP10-SAP
2008-09-03 14:45:53 ERROR: incorrect format or option in .utl file (-p)
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.52
2008-09-03 14:45:53 BR0279E Return code from '/usr/sap/RD1/SYS/exe/run/backint -u RD1 -f backup -i /lms/oracle/RD1/saparch/.adystlhx.lst -t file -p
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0232E 0 of 1 file saved by backup utility
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.52
2008-09-03 14:45:53 BR0231E Backup utility call failed
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0016I 0 offline redo log files processed, totalsize 0.000 MB
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0007I End of offline redo log processing: adystlhx.cds 2008-09-03 14.45.53
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.53
2008-09-03 14:45:53 BR0005I BRARCHIVE terminated with errors
2008-09-03 14:45:53 External program terminated with exit code 5
2008-09-03 14:45:53 BRARCHIVE returned error status E
2008-09-03 14:45:53 Job finished
Can you please help me out.
Thanks in Advance.
Regards,
RohanHi Rohan,
Are you using any backup software to manage SAP Backups? Has anything changed? Any upgrades done to backup software?
2008-09-03 14:45:53 BR0278I Command output of '/usr/sap/RD1/SYS/exe/run/backint -u RD1 -f backup -i /lms/oracle/RD1/saparch/.adystlhx.lst -t file -p
2008-09-03 14:45:53 ERROR - Failed to get the policy method type: LNSDQP10-SAP
2008-09-03 14:45:53 ERROR: incorrect format or option in .utl file (-p)
Cheers,
Nisch -
Force logging at tablespace level for standby database
Hi
Can we create a standby database by enabling force logging at tablespace level instead of enabling it at database level.I want to out the tablespace containing indexes in nologging mode so that when I rebuild the indexes no logs will be generated.Technically, you can create a Standby without having set FORCELOGGING at the Primary database.
You can also then selectively FORCELOGGING for all your important tablespaces (beginning with SYSTEM, SYSAUX, UNDO ....)
However, for a Physical Standby Redo Apply will mark the blocks (e.g. those populated by the CREATE INDEX .. NOLOGGING) as "corrupt". You will get Read Errors (ORA-1578 and ORA-26040) when you attempt to read the index (e.g. for a Table query).
So you have to monitor your NOLOGGING operations and the datafiles where NOLOGGING is applied. You can take Incremental RMAN Backups of such datafiles and restore them to the Standby immediately after the NOLOGGING operations.
Hemant K Chitale -
Why we need some ddl not to be wroten to the redo logs? What is the idea? How can we recover the database if some infromation in archivelogs is missed?
Thanks in advanceIn theory, yo may wish to allow an application to load data as a "no logging" operation, this can speed up large data loads and reduce the volume of archivelogs produced.
However the major drawbacks are:
if you need to recover the database form a backup any data added using a no logging operation performed after the backup was taken will not be recoverable from the archive logs.
If you are using log shipping/data guard these operations will not get transmitted to the standby server.
If you work in a controlled an disciplined enviroment then it should be possible to repeat any no logging operations after the database is recovered as everyone should be aware of the limitations of loading data in this manner.
If you work anywhere thats like the places I've come accross a more likely situation is after a database recovery someone will want to know why data is missing from the database and how long it will be untill you resolve the problem. Usually I set force logging on and let the users think they have the option to run nologgign operations as it leads to a quieter life in the long run. -
Hi SAPers
I have problem with maxdb (content server). Is it possible to activate automatic log backup to pipe? We are backuping through Tivoli on tapes. Backup media are created and manual backups are working fine but i am not able to activate automatic log backups! Always when I am activating this the file instead of pipe is created in /sapdb/RDB/backup directory and backup is not performed.
In the Note 869267 - FAQ: MaxDB LOG area I found out that it is not possible to activate automatic log backups to pipe is it true?
Thanks in advance
JMHello JM,
What database version are you running?
You already found the note 869267, which gave you answer on the question "24. Can the log area be saved to a pipe? ". The SAP note 869267 also give you the answer on the question "26. How do I archive the log backup files generated?
"Is it possible to activate automatic log backup to pipe?"
*No.
And it's true, that "Automatic log backups to a pipe CANNOT be supported at present" , as it was explained in the SAP note 869267.
But you could run the interactive log backups to a pipe.
In general you could find the information/documents at https://www.sdn.sap.com/irj/sdn/maxdb
-> The Complete SAP MaxDB Documentation Set -> Open the SAP MaxDB 7.7 Library
-> Database Administration-> Backing Up the Database
< -> Backing Up Log Entries >
Thank you and best regards, Natalia Khlopina
Edited by: Natalia Khlopina on Apr 28, 2008 1:26 PM
Edited by: Natalia Khlopina on Apr 28, 2008 1:26 PM
Maybe you are looking for
-
I've only noticed this since the software update (10.7.1), but I've got a big problem with preview at the moment. I'm trying to open some PDFs (journal articles) saved on my MacBook Pro, which I've previously had no trouble opening, but all I get is
-
Why do I keep getting a runtime error in Photoshop Elements 6.0?
I have had Photoshop Elements 6.0 for several years now with no issues at all. Recently my computer crashed and I bought a new ASUS touchscreen laptop (Q301L model). I have tried, with no luck, to get Photoshop to work. After a few actions, it will
-
Process is always in Processing Status
Hello i created the UDT2UDT scenario as the official document but always it appears in processing status is there any missing config? how can i nresolve it?
-
I want to remove the credit on my account.
I want to remove the credit on my account.
-
Calling a javascript function from an Applet
I am trying to make an applet that works on as many browsers as possible, so I am sticking to Version JCK 1.1 I am trying to call pass the javascript function into a URL object like this URL url = new URL("javascript:" + function, "_self");but I keep