Automatic log backup to pipe

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
JM

Hello 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

Similar Messages

SAP Livecache automatic log backup turning off

Hi,
We have set automatic log backup ON for our livecache. Recently, it got turned off automatically.
We found that our filesystem to which the archive files were getting generated during log backups had got full.
My question is, if the filesystem where log backups are archived gets full does the setting of automatic log backup gets turned
OFF automatically? Please suggest,
Rg,
Sandeep.

> We have set automatic log backup ON for our livecache. Recently, it got turned off automatically.
> We found that our filesystem to which the archive files were getting generated during log backups had got full.
> My question is, if the filesystem where log backups are archived gets full does the setting of automatic log backup gets turned
> OFF automatically? Please suggest,
Yes, that is expected behaviour. If the database can't back up logs to a directory it gets turned off. You'll have to release space and turn it on manually.
Markus

Deactivating Automatic log backup

Hello All,
I have a query.
How can we check when automatic log backup of livecache log area has been deactivated. and Why?
Any log file registring this?
Thanks.
Regards,
Tushar

Hello Melanie,
Thanks a lot.
I checked dbm.prt file which does not mention autolog_off command means it has been deactivated by error.
So checked knldiag.err file, which mentioned the error:
========================================================
2007-11-11 06:08:47 156 ERR 11000 d0_aopen Cannot open device, Permission denied
2007-11-11 06:08:47 156 ERR 11000 d0_aopen Device name '/sapdb/OEM/lcbackup/log/autolog.003'
2007-11-11 06:08:47 83 ERR 1 Backup Backupmedium #1 (/sapdb/OEM/lcbackup/log/autolog.003) Could not open volume
2007-11-11 06:08:47 83 ERR 6 KernelCo + Backup error occured, Errorcode 3700 "hostfile_error"
2007-11-19 08:42:52 189 ERR 11000 d0_aopen Cannot open device, Permission denied
===========================================================
-rw-rw---- 1 oemadm sapsys 349765632 Jun 26 2006 autolog.002
-rw-rw---- 1 oemadm sapsys 57540608 Jul 21 10:58 autolog.003
===========================================================
I checked autolog.003 file which has permission as owner (<livecache_sid>adm) and group sapsys.
It also has overwrite option as NO:
Corrosponding entries in the KNLDIAG file are :
=========================================================2007-11-11 06:08:43 28 12929 TASKING Task T5 started
2007-11-11 06:08:43 28 20018 Pager Start TaskId: 5
2007-11-11 06:08:43 28 20019 Pager First DataCacheSegment:31
2007-11-11 06:08:44 12 3 RunTime State changed from STARTING to ADMIN
2007-11-11 06:08:44 24 31 SrvTasks Permanently reserved 10 servertasks for 'Backup / Restore'.
======================================= end of startup part ====================
2007-11-20 23:23:17 14 11561 COMMUNIC Connecting T95 local 29873
2007-11-20 23:23:17 118 12929 TASKING Task T95 started
2007-11-20 23:23:17 118 11007 COMMUNIC wait for connection T95
=========================================================
So it owner:group is wrong or is it due to overwrite option?
What should be owner and group sdb:sdba for backup medium of file type?
Thanks for your help.
Regards,
Tushar
Message was edited by:
 Tushar Chavan
Message was edited by:
 Tushar Chavan

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,
Subba

Hi 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

Redo log backup failing with BR253E errno 2:

Hi all,
I am able to take online as well as offline backup through sapdba , but unfortunately from last 7 days my redo log backup is failing after online backup is complete with below mentioned error. I also tried to start redo log backup seperately but failed as below...
BR002I BRARCHIVE 6.20 (18)
BR006I Start of offline redo log processing: adwpawsw.sve 2007-11-13 21.33.22
BR280I Time stamp 2007-11-13 21.33.25
BR008I Offline redo log processing for database instance: PRD
BR009I BRARCHIVE action ID: adwpawsw
BR010I BRARCHIVE function ID: sve
BR048I Archive function: save
BR011I 195 offline redo log files found for processing, total size 9469.831 MB
BR112I Files will not be compressed
BR130I Backup device type: disk
BR106I Files will be saved on disk in directory: F:\oracle\PRD\sapbackup
BR126I Unattended mode active - no operator confirmation required
BR202I Saving init_ora
BR203I to F:\oracle\PRD\sapbackup\PRD ...
BR202I Saving o:\orcle\prd\920\DATABASE\initPRD.sap
BR203I to F:\oracle\PRD\sapbackup\PRD ...
BR280I Time stamp 2007-11-13 21.33.26
BR198I Profiles saved successfully
BR252E Function fopen() failed for 'F:\oracle\PRD\sapbackup\.PRD/oraarch/PRDarch
ARC10479.001' at location arch_process-4
BR253E errno 2: No such file or directory
BR121E Processing log file F:\oracle\PRD\sapbackup\.PRD/oraarch/PRDarchARC10479.
001 failed
BR016I 0 offline redo log files processed, total size 0.000 MB
BR007I End of offline redo log processing: adwpawsw.sve 2007-11-13 21.33.26
BR280I Time stamp 2007-11-13 21.33.26
BR005I BRARCHIVE terminated with errors
End of output from program 'BRARCHIVE' -
SAPDBA: Execution of BRARCHIVE failed.
 (2007-11-13 21.33.27)
Press <return> to continue ...
SAPDBA: Last line from BRARCHIVE summary log:
 '#* PRD disk adwpawsw sve 2007-11-13 21.33.22 2007-11-13 21.33.26
 5 ........... -
c 6.20 (18)'
Press <return> to continue ...
Appreciate your quick replies.
Best Regards,
AjitR

Unfortunately backlogs point to directory
'F:\oracle\PRD\sapbackup\.PRD
But i have my logfiles getting archived at D:\oracle\PRD\oraarch
and they are supposed to be backed up at F:\oracle\PRD\sapbackup
Below is my init.sap file for your ref, i cant find where this .PRD folder came from
backup mode [all | all_data | full | incr | sap_dir | ora_dir
| <tablespace_name> | <file_id> | <file_id1>-<file_id2>
| <generic_path> | (<object_list>)]
default: all
backup_mode = all
restore mode [all | all_data | full | incr | incr_only | incr_full
| <tablespace_name> | <file_id> | <file_id1>-<file_id2>
| <generic_path> | (<object_list>)]
redirection with '=' is not supported here - use option '-m' instead
default: all
restore_mode = all
backup type [offline | offline_force | offline_standby | offline_split
| offline_stop | online | online_cons | online_split]
default: offline
backup_type = offline
backup device type
[tape | tape_auto | tape_box | pipe | pipe_auto | pipe_box | disk
| disk_copy | disk_standby | stage | stage_copy | stage_standby
| util_file | util_file_online | rman_util | rman_disk | rman_stage
| rman_prep]
default: tape
#backup_dev_type = tape
backup_dev_type = disk
backup root directory [<path_name> | (<path_name_list>)]
default: %SAPDATA_HOME%\sapbackup
#backup_root_dir = D:\oracle\PRD\sapbackup
backup_root_dir = F:\oracle\PRD\sapbackup
stage root directory [<path_name> | (<path_name_list>)]
default: value of the backup_root_dir parameter
#stage_root_dir = D:\oracle\PRD/sapbackup
stage_root_dir = F:\oracle\PRD\sapbackup
compression flag [yes | no | hardware | only]
default: no
compress = no
compress command
first $-character is replaced by the source file name
second $-character is replaced by the target file name
<target_file_name> = <source_file_name>.Z
for compress command the -c option must be set
recommended setting for brbackup -k only run:
"%SAPEXE%\mkszip -l 0 -c $ > $"
no default
compress_cmd = "@SAPEXE@\mkszip -c $ > $"
uncompress command
first $-character is replaced by the source file name
second $-character is replaced by the target file name
<source_file_name> = <target_file_name>.Z
for uncompress command the -c option must be set
no default
uncompress_cmd = "@SAPEXE@\uncompress -c $ > $"
directory for compression [<path_name> | (<path_name_list>)]
default: value of the backup_root_dir parameter
#compress_dir = D:\oracle\PRD/sapreorg
compress_dir = F:\oracle\PRD\sapreorg
brarchive function [save | second_copy | double_save | save_delete
| second_copy_delete | double_save_delete | copy_save
| copy_delete_save | delete_saved | delete_copied]
default: save
archive_function = save
directory for archive log copies to disk
default: first value of the backup_root_dir parameter
#archive_copy_dir = D:\oracle\PRD/sapbackup
archive_copy_dir = F:\oracle\PRD\sapbackup
directory for archive log copies to stage
should contain <SID> subdirectory
default: first value of the stage_root_dir parameter
#archive_stage_dir = D:\oracle\PRD/sapbackup
archive_stage_dir = f:\oracle\PRD\sapbackup
new database home directory for disk_copy | disk_standby
no default
new_db_home = X:\oracle\C11
stage database home directory for stage_copy | stage_standby
default: value Cof the new_db_home parameter
stage_db_home = /oracle/C11
original database home directory for split mirror disk backup
no default
orig_db_home = /oracle/C11

Automatic OCR backup has failed. How to diagnose?

DB version:10.2.0.4
OS : Solaris
Automatic OCR backup taken by CRS every four hour in $ORA_CRS_HOME/cdata/crs has failed in our cluster. It hasn't been running for the last 3 weeks. Where should i start the diagnosis? day.ocr file's timestamp shows November 19, 2010 !!

Check out the CRS log files for any error ..
Also in the meantime , don't forget to backup OCR manually ..
What is free space available on CRS_HOME mount point ?
Check if you are hitting below BUG :
*Bug 6134126 - OCR backup can fail [ID 6134126.8]*
I would suggest to raise SR with support.
Regards
Rajesh

Restore a log backup on to database whose recovery model is SIMPLE ?

Hi All,
Today, it was new thing I found when I was testing some log shipping?
Question is can we restore a LOG BACKUP on a database whose recovery model is SIMPLE?
Brief background:
I setup log shipping in SQL Server 2012 SP1 Enterprise Edition between 2 instances. Log shipping is in Standby/readonly mode. So, everything was working very fine...
Now I changed the recovery model of secondary database on 2nd instance from Full to SIMPLE, still the restores are happening very fine. So, is this a normal behavior? other thing is once after restore job is complete the recovery model is getting changed to
FULL automatically on secondary db and I verify it before and after restore job using below query:
select name,recovery_model_desc from sys.databases
Based on my knowledge when a database is in SIMPLE recovery model, we can't perform any log backups on the database and since no log backups, we cant perform Point in Time recovery?
Please clarify what I am seeing is normal ? Also, would like to know what is happening behind the scenes?
Thanks and appreciate your help.
Sam

Hi,
>>Question is can we restore a LOG BACKUP on a database whose recovery model is SIMPLE?
Yes you can restore Log backup on database which is in simple recovery.
You must understand what recovery model is for. Recovery model affects Logging and recovery of a database it does not puts restriction on what can be restore on it. Of course you cannot take log backup of database in simple recovery but you can restore.
Reason being in simple recovery log is truncated after checkpoint (unless something is holding logs like long running transaction). Recovery model also controls the extent of logging which would be done for transaction and hence recovery which you can do
PS: Dont play with logshipping like this which is configured on prod environment
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Help needed - automatic log in on public computer. How to get rid of the account.

Hi there
Recently while on vacation, my son logged into a public computer on his ichat. Unfortuantely, it was clicked as automatic log in.
Now we are back home and have realized that someone has been accessing his account.
We have tried deleting the account from our home computer, however, it does not delete it from the public computer.
What will happen if we change the password on our home computer? Will the public computer be prompted to re-login with the new password, and therefore won't be able to?
Help please

hI,
Yes change the Password and they will not be able to login.
That is change the Password at the server you are using.
Either AIM itself for AIM name or iForgot for @MAC.com or MobilMe names
Login to your Google account and change the password there in your Account Settings
With any other Jabber Account you will have to use the third Party app you used to get the accounst Name set up.
Then Change it in iChat.
10:25 PM Sunday; June 26, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.7)
 Mac OS X (10.6.7),
"Limit the Logs to the Bits above Binary Images."  No, Seriously
Message was edited by: Ralph Johns (UK)

[OBSOLET]Automatically logging in different sessions in KDM via kdmctl

I recently found comfort in KDE, so I try to use KDM on my mediacenter to manage both, a KDE session, as well as an XBMC session.
What I want to do: Log in as $USER on two different sessions, one with XBMC and one with the KDE desktop automatically on boot without the need to provide a password.
After playing a bit with the control center, I came as far as automatically logging in a user and/or allowing a user a passwordless login. This is a good first step. I cannot, however, find a way to define the session it should use, the control center setting for auto login will always use the default session (which is the last session I manually logged in to). There is no way to configure multiple sessions at once in the controlcenter.
So I looked for cli tools and discovered kdmctl. It has a number of features, for example will "kdmctl activate :1" jump to the display :1. Another step closer to my goal is "kdmctl reserve", which opens a new login prompt on the next free $DISPLAY. Now it seems like kdmctl is very session-sensitive. I need root access to call it from a tty, while a normal user is sufficient inside a KDM managed X session. Calling kdmctl in a tty will give me more options, than calling it in X, even with sudo. Upon "# kdmctl" in a tty, I can see resume, manage and login options, which are not there in a KDE session.
What I have so far:
1. I can use the KDE control center to log in a user automatically on :0, but I cannot specify the session (Plasma, XBMC, etc.).
2. I can run "# kdmctl reserve" to create a new login prompt at :1
3. I can login to :1 by issuing "# kdmctl login :1 now USERNAME PASSWORD", but only from a tty (which would be sufficient, as I intend to write a systemd unit).
What I cannot do:
1. I cannot specify the session. I have found http://docs.kde.org/stable/de/kde-works … opics.html, but it is not really helpful. It says I need "[session_arguments]" in the "format of printf specified .dmrc". I assume this is how I could specify my session, but I cannot find any documentation. Maybe I'm using the wrong keywords. There is neither a man page for kdmrc nor for dmrc. This is what I'd like to have some help with.
EDIT: It's not actually solved but has become obsolete. KDE4 is fading away and, according to the wiki, KDE5/plasma5 prefers SDDM. Besides that, I stopped using KDE, stopped switching sessions, stopped working on this a long time ago.
Last edited by Awebb (2015-03-29 11:55:33)

Anybody any clues?
-Mahendra.

Automatically log back in for a given period of time

I just started to work on web and have the following issue:
We want some (mobile) users to be able to automatically log back in for a given period of time. It is not difficult to set cookie (valid user information without clear text) on the mobile device. For now the question is how we can log in using this cookie info.
Web application uses "j_security_check", "j_security_check" checks the user/password.
Question is how we can autologin using cookie information. Thanks guys!

it is not problem to check cookie on exists and valid. Problem is 'where' where can I do it using 'j_security_check'

HT2534 how can my daughter and i have our own itunes accounts on one computer because it automatically logs on with mine?

how can my daughter and i have our own itunes accounts on one computer because it automatically logs in with mine?

Hi theirmimi,
Go to Manage your Apple ID (on a computer) and sign in with your Apple ID. Then you can edit the email information on your account:
https://appleid.apple.com/cgi-bin/WebObjects/MyAppleId.woa/
Cheers,
GB

I have set up two users, one for myself and one for children. The computer automatically logs in for the children with no password required. When the children go to spotlight and type in a search criteria all of my files show up. How do I prevent this?

I have set up two users, one for myself and one for children. The computer automatically logs in for the children with no password required. When the children go to spotlight and type in a search criteria all of my files show and open up. How do I prevent this?

Log in to your account, and move all your files to your home folder. No other users should be able to access them there and they won't show up with a Spotlight search.
Make sure your kids' account(s) do not have admin privileges.

I don't want to be logged into game center, but it automatically logs me in every time I log out. How do I stop that from happening?

I am trying to disable my game center, but every time I log out of game center, it automatically logs me back in. How do I prevent this from happening?

System Preferences - Mail, Contacts and Calendars - delete the Facebook account you see there, and/or add your own account.
Matt

Error while taking archive log backup

Dear all,
We are getting the below mentioned error while taking the archive log backup
============================================================================
BR0208I Volume with name RRPA02 required in device /dev/rmt0.1
BR0210I Please mount BRARCHIVE volume, if you have not already done so
BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.41
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRARCHIVE:
c
BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.46
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.46
BR0226I Rewinding tape volume in device /dev/rmt0 ...
BR0351I Restoring /oracle/RRP/sapreorg/.tape.hdr0
BR0355I from /dev/rmt0.1 ...
BR0278W Command output of 'LANG=C cd /oracle/RRP/sapreorg && LANG=C cpio -iuvB .tape.hdr0 < /dev/rmt0.1':
Can't read input
===========================================================================
We are able to take offline, online backups but we are facing the above mentioned problem while taking archive log backup
We are on ECC 6 / Oracle / AIX
The kernel is latest
The drive is working fine and there is no problem with the tapes as we have tried using diffrent tapes
can this be a permissions issue?
I ran saproot.sh but somehow it is setting owner as sidadm and group as sapsys to some of the br* files
I tried by changing the permissions to oraSID : dba but still the error is the same
Any suggestions?

Means you have not initialized the medias but trying to take backups.
First check how many medias you have entered in your tape count parameter for archive log backups (just go to initSID.sap and check)
Then increase/reduce them to according to your archive backup plan >> Initialize all the tapes according to their name (same as you have initialized in initSID.sap) >> stick physical label to all the medias according to name >> Schedule archive backups
It will not ask you for initialization as already you have initialized in second step.
Suggestion: Use 7 medias per week (one tape per day)
Regards,
Nick Loy

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.

Automatic log backup to pipe

Similar Messages

Maybe you are looking for