Log archive partition is full

In windows 2003 + db2 combination, archive log partition is full now so can anybody tell me how to archive the logs and delete it from DB2 system level.
I would appreciate the procedure with steps and prerequisite.
Thanks in advance

Hello Daniel,
I am not sure about your current situation. So, I can only guess.
I supposed the drive that hold your log_archive directory becomes full at a certain point. When that happens, DB2 will keep on trying to archive the logs to the log_archive directory. And when it fails, the logs will stay in log_dir and thus your log_dir and gradually fill up log_dir until it is full as well.
Now that your log_archive has more space, DB2 will try to archive the logs from log_dir to log_archive again and in the end, all the archive logs that are supposed to be in log_archive should be in log_archive.
Once the logs are moved to log_archive. You can save them to a safe location (TSM or tape drives) OR "prune" them once you have determined that you don't need them any more.
Regards,

Similar Messages

I meet the partition too full problem

I updated the pacman to Pacman v4.0.1 - libalpm v7.0.1
when i run pacman -Syu
and it said:
(12/12) checking package integrity [##################################################] 100%
(12/12) loading package files [##################################################] 100%
(12/12) checking for file conflicts [##################################################] 100%
(12/12) checking available disk space [##################################################] 100%
error: Partition / too full: 60 blocks needed, 0 blocks free
error: not enough free disk space
error: failed to commit transaction (not enough free disk space)
Errors occurred, no packages were upgraded.
My system runs in ramfs
[FW: /]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/run 10240 208 10032 3% /run
udev 10240 0 10240 0% /dev
shm 1032408 0 1032408 0% /dev/shm
/dev/sda4 1433376 258208 1175168 19% /secwall
log 10240 428 9812 5% /var/log
/dev/sdb1 109332384 51627496 52151072 50% /mnt/archlinux

I got a similar error while trying to install a package. Here's the debug info:
[nak@arch ~]$ sudo pacman --debug -S ogre
debug: parseconfig: options pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: HoldPkg: pacman
debug: config: HoldPkg: glibc
debug: config: SyncFirst: pacman
debug: config: arch: x86_64
debug: config: SigLevel: Never
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 81: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 85: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 93: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: config: finished parsing /etc/pacman.conf
debug: setup_libalpm called
debug: option 'logfile' = /var/log/pacman.log
debug: option 'gpgdir' = /etc/pacman.d/gnupg/
debug: option 'cachedir' = /var/cache/pacman/pkg/
debug: parseconfig: repo pass
debug: config: attempting to read file /etc/pacman.conf
debug: config: finish section '(null)'
debug: config: new section 'options'
debug: config: finish section 'options'
debug: config: new section 'core'
debug: config file /etc/pacman.conf, line 81: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'core'
debug: registering sync database 'core'
debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: adding new server URL to database 'core': http://cosmos.cites.illinois.edu/pub/archlinux/core/os/x86_64
debug: config: new section 'extra'
debug: config file /etc/pacman.conf, line 85: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'extra'
debug: registering sync database 'extra'
debug: database path for tree extra set to /var/lib/pacman/sync/extra.db
debug: adding new server URL to database 'extra': http://cosmos.cites.illinois.edu/pub/archlinux/extra/os/x86_64
debug: config: new section 'community'
debug: config file /etc/pacman.conf, line 93: including /etc/pacman.d/mirrorlist
debug: config: attempting to read file /etc/pacman.d/mirrorlist
debug: config: finished parsing /etc/pacman.d/mirrorlist
debug: config: finish section 'community'
debug: registering sync database 'community'
debug: database path for tree community set to /var/lib/pacman/sync/community.db
debug: adding new server URL to database 'community': http://cosmos.cites.illinois.edu/pub/archlinux/community/os/x86_64
debug: config: finished parsing /etc/pacman.conf
debug: loading package cache for repository 'local'
debug: added 607 packages to package cache for db 'local'
debug: loading package cache for repository 'core'
debug: opening database archive /var/lib/pacman/sync/core.db
debug: added 192 packages to package cache for db 'core'
debug: loading package cache for repository 'extra'
debug: opening database archive /var/lib/pacman/sync/extra.db
debug: added 2785 packages to package cache for db 'extra'
debug: loading package cache for repository 'community'
debug: opening database archive /var/lib/pacman/sync/community.db
debug: added 2331 packages to package cache for db 'community'
debug: adding package 'ogre'
debug: adding package ogre-1.8.0RC1-3 to the transaction add list
resolving dependencies...
debug: resolving target's dependencies
debug: started resolving dependencies
debug: checkdeps: package ogre-1.8.0RC1-3
debug: checkdeps: missing dependency 'zziplib' for package 'ogre'
debug: checkdeps: missing dependency 'ois' for package 'ogre'
debug: pulling dependency zziplib (needed by ogre)
debug: pulling dependency ois (needed by ogre)
debug: checkdeps: package zziplib-0.13.60-1
debug: checkdeps: package ois-1.3-1
debug: finished resolving dependencies
debug: started sorting dependencies
debug: sorting dependencies finished
looking for inter-conflicts...
debug: looking for conflicts
debug: check targets vs targets
debug: check targets vs targets
debug: check targets vs db and db vs targets
debug: check targets vs db
debug: check db vs targets
debug: checking dependencies
debug: checkdeps: package zziplib-0.13.60-1
debug: checkdeps: package ois-1.3-1
debug: checkdeps: package ogre-1.8.0RC1-3
debug: found cached pkg: /var/cache/pacman/pkg/zziplib-0.13.60-1-x86_64.pkg.tar.xz
debug: setting download size 0 for pkg zziplib
debug: found cached pkg: /var/cache/pacman/pkg/ois-1.3-1-x86_64.pkg.tar.xz
debug: setting download size 0 for pkg ois
debug: found cached pkg: /var/cache/pacman/pkg/ogre-1.8.0RC1-3-x86_64.pkg.tar.xz
debug: setting download size 0 for pkg ogre
debug: returning error 31 from alpm_db_get_pkg : could not find or read package
debug: returning error 31 from alpm_db_get_pkg : could not find or read package
debug: returning error 31 from alpm_db_get_pkg : could not find or read package
Targets (3): ois-1.3-1 zziplib-0.13.60-1 ogre-1.8.0RC1-3
Total Installed Size: 89.52 MiB
Proceed with installation? [Y/n] y
debug: using cachedir: /var/cache/pacman/pkg/
debug: using cachedir: /var/cache/pacman/pkg/
checking package integrity...
debug: found cached pkg: /var/cache/pacman/pkg/zziplib-0.13.60-1-x86_64.pkg.tar.xz
debug: sha256sum: 34f32859b0ef5d5858220df14ea4fc4af2a09f577f71955c296f483b67767f83
debug: checking sha256sum for /var/cache/pacman/pkg/zziplib-0.13.60-1-x86_64.pkg.tar.xz
debug: found cached pkg: /var/cache/pacman/pkg/ois-1.3-1-x86_64.pkg.tar.xz
debug: md5sum: 5208b2316828afe8de8beff154785b4f
debug: checking md5sum for /var/cache/pacman/pkg/ois-1.3-1-x86_64.pkg.tar.xz
debug: found cached pkg: /var/cache/pacman/pkg/ogre-1.8.0RC1-3-x86_64.pkg.tar.xz
debug: sha256sum: a5d1af59ef6571b1207fbfe274a25093b8acf826700216a0b9bf63dd37fdfc68
debug: checking sha256sum for /var/cache/pacman/pkg/ogre-1.8.0RC1-3-x86_64.pkg.tar.xz
loading package files...
debug: found cached pkg: /var/cache/pacman/pkg/zziplib-0.13.60-1-x86_64.pkg.tar.xz
debug: replacing pkgcache entry with package file for target zziplib
debug: starting package load for /var/cache/pacman/pkg/zziplib-0.13.60-1-x86_64.pkg.tar.xz
debug: sorting package filelist for /var/cache/pacman/pkg/zziplib-0.13.60-1-x86_64.pkg.tar.xz
debug: found cached pkg: /var/cache/pacman/pkg/ois-1.3-1-x86_64.pkg.tar.xz
debug: replacing pkgcache entry with package file for target ois
debug: starting package load for /var/cache/pacman/pkg/ois-1.3-1-x86_64.pkg.tar.xz
debug: sorting package filelist for /var/cache/pacman/pkg/ois-1.3-1-x86_64.pkg.tar.xz
debug: found cached pkg: /var/cache/pacman/pkg/ogre-1.8.0RC1-3-x86_64.pkg.tar.xz
debug: replacing pkgcache entry with package file for target ogre
debug: starting package load for /var/cache/pacman/pkg/ogre-1.8.0RC1-3-x86_64.pkg.tar.xz
debug: sorting package filelist for /var/cache/pacman/pkg/ogre-1.8.0RC1-3-x86_64.pkg.tar.xz
checking for file conflicts...
debug: looking for file conflicts
debug: searching for file conflicts: zziplib
debug: searching for filesystem conflicts: zziplib
debug: checking possible conflict: /usr/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/bin/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/include/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/lib/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/lib/pkgconfig/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/share/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/share/aclocal/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/share/man/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/share/man/man3/
debug: file is a directory, not a conflict
debug: searching for file conflicts: ois
debug: searching for filesystem conflicts: ois
debug: checking possible conflict: /usr/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/include/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/lib/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/lib/pkgconfig/
debug: file is a directory, not a conflict
debug: searching for file conflicts: ogre
debug: searching for filesystem conflicts: ogre
debug: checking possible conflict: /opt/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/bin/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/include/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/lib/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/lib/pkgconfig/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/share/
debug: file is a directory, not a conflict
debug: checking possible conflict: /usr/share/licenses/
debug: file is a directory, not a conflict
checking available disk space...
debug: checking available disk space
debug: mountpoint: /tmp
debug: mountpoint: /sys/kernel/security
debug: mountpoint: /sys/kernel/debug
debug: mountpoint: /sys/fs/fuse/connections
debug: mountpoint: /sys/fs/cgroup/systemd
debug: mountpoint: /sys/fs/cgroup/net_cls
debug: mountpoint: /sys/fs/cgroup/memory
debug: mountpoint: /sys/fs/cgroup/freezer
debug: mountpoint: /sys/fs/cgroup/devices
debug: mountpoint: /sys/fs/cgroup/cpuset
debug: mountpoint: /sys/fs/cgroup/cpu,cpuacct
debug: mountpoint: /sys/fs/cgroup/blkio
debug: mountpoint: /sys/fs/cgroup
debug: mountpoint: /sys
debug: mountpoint: /run
debug: mountpoint: /proc/sys/fs/binfmt_misc
debug: mountpoint: /proc/sys/fs/binfmt_misc
debug: mountpoint: /proc
debug: mountpoint: /mnt/ubuntu
debug: mountpoint: /media
debug: mountpoint: /home/nak/.gvfs
debug: mountpoint: /home
debug: mountpoint: /dev/shm
debug: mountpoint: /dev/pts
debug: mountpoint: /dev/mqueue
debug: mountpoint: /dev/hugepages
debug: mountpoint: /dev
debug: mountpoint: /boot
debug: mountpoint: /
debug: mountpoint: /
debug: partition /, needed 22700, cushion 5121, free 15105
error: Partition / too full: 27821 blocks needed, 15105 blocks free
debug: returning error 7 from _alpm_check_diskspace : not enough free disk space
error: not enough free disk space
error: failed to commit transaction (not enough free disk space)
Errors occurred, no packages were upgraded.
debug: unregistering database 'local'
debug: freeing package cache for repository 'local'
debug: unregistering database 'core'
debug: freeing package cache for repository 'core'
debug: unregistering database 'extra'
debug: freeing package cache for repository 'extra'
debug: unregistering database 'community'
debug: freeing package cache for repository 'community'
and df output:
[nak@arch ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 7.4G 7.3G 0 100% /
/dev 3.9G 0 3.9G 0% /dev
/run 3.9G 364K 3.9G 1% /run
/dev/sdb3 7.4G 7.3G 0 100% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 3.9G 0 3.9G 0% /media
tmpfs 3.9G 4.6M 3.9G 1% /tmp
/dev/sdb1 99M 19M 76M 20% /boot
/dev/sdb4 225G 8.3G 206G 4% /home
/dev/sda1 587G 318G 241G 57% /mnt/ubuntu
/dev/sdb3 is looking full... (be back later...)
EDIT:
I ran `pacman -Scc`
which opened up /dev/sdb3 to 97% and allowed me to install the package.
I'm willing to be educated as to what's going on. I did auto-partition and do not remember setting up a 7.4G partition. A guess would be its `/var/` but that's just a guess. Any tips? What should I read to learn more or what commands can I run to find out what's mounted to where?
Thanks
Last edited by uberscientist (2012-02-02 07:50:28)

Archive directory is full

Hello Experts,
I'm very new into SAP.
Plz tell me how to look that the archive directory is full at the database level and what command to use to bring the system up again as it hanged when the redo logs are not deleted from the system.
Thanks in advance.

Hi,
As suggested by other SDN members, offline redologs needs to be backed-up & then deleted to make space for new logs.
You can check disk utilization with following command:
df -g | grep oraarc
If above command shows that it is more than 90% full, move your archive logs to another folder (e.g. /oracle/<SID>/arc_backup). Since this is faster option to make your system available. Backup on tape takes comparatively longer time.
Once space becomes available in /oracle/<SID>/oraarc directory, systems automatically comes out of hung state & users can continue their work. You need not stop or start your database.
Regards,
-Pankaj Kapote

C000000* Folder in log archive directory

Hi,
We use db2 9,5 + ecc 6.0 in our landscape
We see the folders C0000<number> created in the log_archive path and some log files inside this
We wanted to know the following
Is this folders created after particular size of log archive files in the directory
Is this folders created after restart etc
Please assist

Hi Balaji,
Yes, the C...number represents the log chains.
Please see page 11 of the db admin guide:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50c7d3ef-5a59-2a10-a3ab-fb3b0887f479?quicklink=index&overridelayout=true
The log chain with the highest number contains the active log files.
For example:
If we restore from backup and only go to a point in time, instead of all the way to the latest logs, in the old log file management, the subsequent logs, left over after the point in time we restored to would be dropped. But in new logfile management, they are kept as a generation of log files and the log file chain is increased and new logs then created under the new chain number.
regards,
Paul

The file structure online redo log, archived redo log and standby redo log

I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

FZheng:
Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
Edited by: 853153 on Jun 22, 2011 9:42 AM

Log Archive Failed via dbacockpit

Hi,
I've scheduled Oracle db log archive via dbacockpit. It failed at 1am, but it completed successfully later at 1pm as scheduled. So far, had 2 such occurences.
Any where to diagnose the intermittent error ? Please enlighten. TIA !
05.05.2009     01:00:29     Job started
05.05.2009     01:00:34     Step 001 started (program RSDBAJOB, variant &0000000000024, user ID BACKUP_USER)
05.05.2009     01:00:56     No application server found on database host - rsh/gateway will be used
05.05.2009     01:00:56     Execute logical command BRARCHIVE On host burger
05.05.2009     01:00:56     Parameters:-u / -jid LOG__20080926010000 -c force -p initprd.sap -sd
05.05.2009     01:02:09     SXPG_COMMAND_EXECUTE(LONG)
05.05.2009     01:02:09     COMMANDNAME = BRARCHIVE
05.05.2009     01:02:09     OPERATINGSYSTEM = ANYOS
05.05.2009     01:02:09     TARGETSYSTEM = burger
05.05.2009     01:02:09     DESTINATION = SAPXPG_DBDEST_BURGER
05.05.2009     01:03:46     External communication error at program start (see system log)
05.05.2009     01:03:46     SAPXPG_START_XPG_LONG: sy-subrc ne 0
05.05.2009     01:03:46     destination = SAPXPG_DBDEST_BURGER
05.05.2009     01:03:52     SXPG_STEP_XPG_START: execute_sapxpg: rc = 1,005
05.05.2009     01:03:52     SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1,005
05.05.2009     01:03:52     SXPG_COMMAND_EXECUTE failed for BRARCHIVE - Reason: x_error
05.05.2009     01:03:52     Job cancelled after system exception ERROR_MESSAGE
DL
Edited by: Desmond Lim on May 5, 2009 10:26 AM

Hello Desmond,
check the system log (SM21) as adviced:
05.05.2009 01:03:46 External communication error at program start (see system log)
Additionally check the trace of the according workprocess (ST11), ABAP dumps (ST22) and the brarchive log (DB12) too.
Greetings
Christian

Is 15 second for log archiving acceptable ?

Version : 11.2.0.3
Platform : RHEL 5.4
3-Node RAC
DB in ARCHIVELOG mode
Question1
============
As you can see below sometimes it takes upto 15 seconds for the archiving of Redo logs.
Online redo log switching is happening fast though . It takes less than 2 seconds (maybe not fast enough for you guys )
Is this acceptable ?
--- Log archiving is slow
SQL> set timing on
SQL> alter system archive log current;
System altered.
Elapsed: 00:00:11.08
SQL>
SQL>
SQL> alter system archive log current;
System altered.
Elapsed: 00:00:10.77
SQL> alter system archive log current;
System altered.
Elapsed: 00:00:15.06
SQL>
SQL>
-- But log switching is fast !
SQL> alter system switch logfile;
System altered.
Elapsed: 00:00:01.89
SQL> alter system switch logfile;
System altered.
Elapsed: 00:00:00.21Question2.
=========
For a DB in archivelog mode, ALTER SYSTEM ARCHIVE LOG CURRENT and ALTER SYSTEM SWITCH LOGFILE have the same effect . Right ? I mean, both of these commands asks the archiver process to archive the ORL which is being currently written to. Right ?

It's fast enough as long as you don't fill up all the online redo before you are finished archiving the first one. It's a round-robin, so if you get all the way around to the first one which is still being archived, everything will stop until it is done.
The ALTER SYSTEM ARCHIVE LOG CURRENT waits for the archiver to finish archiving, so it is slower than ALTER SYSTEM SWITCH LOGFILE, possibly much much so with larger redo.

Require Information for Log Archiving

Hi,
I have ECC 6 system with MAXDB 7.6.5.015,
i want to know the step for LOG Archiving.
And also when we have to restore the system what data should we have,
like a complete backup, incremental back and logs .
Can you explain the scenario.
Thanks in Advance.
Regards,
Ritesh Bhatia,

Duplicate due to connection problem

Partition / too full

Hey, so I just installed arch onto a usb key, 4G and am trying to install some applications onto it. I keep getting the error message:
error: Partition / too full: 15647 blocks needed, 9397 blocks free
error: not enough free disk space
error: failed to commit transaction (not enough free disk space)
with different amount of blocks depending on the application. I should have enough space judging by the free space (in Mb) but they still say the disk is full. Is there nothing I can do or is something funny going on?
thanks

Filesystem Size Used Avail Use% Mounted on
rootfs 1.9G 1.9G 0 100% /
dev 1005M 0 1005M 0% /dev
run 1007M 324K 1006M 1% /run
/dev/sdb5 1.9G 1.9G 0 100% /
shm 1007M 132K 1007M 1% /dev/shm
tmpfs 1007M 244K 1007M 1% /tmp
/dev/sdb1 91M 17M 70M 20% /boot
/dev/sdb6 1.8G 151M 1.6G 9% /home
it looks like it could actually be full
i'll look into those reserved blocks (and getting a bigger usb )

Find number of logs archived

I know how to change the number of SQL Server Logs archived but is there a table that stores the number of logs archived? I need to read from this table to perform some conditional statements.
Ex. SELECT @archive_log_number = logs_archived from [schema.table_name]
if (@archive_log_number = 6)
begin
end
else
begin...
end

Is there a table that holds the number of SQL Server logs?
Hi,
There is an Undocumented command
fn_dblog which has information about SQL server logs.There are others as well dbcc loginfo() ,sp_readerrorlog but none would give you information about transaction apart from fn_dblog
Edit:
http://blogs.msdn.com/b/dfurman/archive/2009/11/05/reading-database-transaction-log-with-fn-dump-dblog.aspx
http://blogs.msdn.com/b/vijaybk/archive/2009/04/29/query-fn-dblog-for-the-list-of-operation-in-active-transaction-of-the-current-session.aspx
select * from fn_dblog(null,null)
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 Articles

Solaris 10 - / partition almost full - deleting obsoleted patches

I installed Solaris 10 on a Sun Blade last month, and have used Sun Update Manager to patch my system regularly. Now, my / partition is 92% full:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 6196110 5612522 521627 92% /
/devices 0 0 0 0% /devices
ctfs 0 0 0 0% /system/contract
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 2305496 1064 2304432 1% /etc/svc/volatile
objfs 0 0 0 0% /system/object
fd 0 0 0 0% /dev/fd
swap 2305504 1072 2304432 1% /tmp
swap 2304480 48 2304432 1% /var/run
/dev/dsk/c0t2d0s7 38476820 12548276 25543776 33% /data1
/dev/dsk/c0t0d0s3 28420342 1772874 26363265 7% /space
/dev/dsk/c0t0d0s7 3099342 769885 2267471 26% /export/home
Does anyone know if/how I can remove old, obsoleted patch versions to free up some space? Is it recommended to use patchrm -f to remove old patch versions? I am hoping that I can avoid re-installing Solaris 10 and, in doing so, make my / partition larger.
Also, I have noticed that Sun Update Manager (SUM) cannot install all available patches. Some patches are evidently signed, and will not install. The only way I have been able to install them is to separately download the unsigned version of the patch and use patchadd -Gd. Is this normal, or am I doing something wrong, or can I somehow reconfigure SUM to change this behavior?

Command patchrm will remove patch and restore old version of patched files. Saved files are stored in /var/sadm/pkg/"PKG_NAME"/save/"PATCH_NO". You can remove these files, but you will not able to restore these files with patchrm. I found this example somewhere in the internet. It removes all saved patches older then 365 days.
Example:
find /var/sadm/pkg/*/save/??????-?? -type d -mtime +365 -prune | xargs rm -r
I use smpatch (simple "smpatch update" command) utility, but i think it is probably same as SUM. smpatch downloads patches to /var/sadm/spool. When patches are successfully installed then they are deleted from this directory otherwise they remain there. They are downloaded as jar archives /var/sadm/spool/??????-??.jar and then unpacked into var/sadm/spool/??????-??.jar.dir. When you delete these files/directories, smpatch will just have to download them again when it is necessary. Log files can be found in /var/sadm/patch/??????-??.
I have only problems with patches for Sun Studio. I must patchadd -G them manually from /var/sadm/spool. Sometime smpatch wants to install absurd patches but then installing simply failed.
I must say, that if you delete files, you do it at your own risk!!!

Database in log archive mode and redo log file in mode not archive

Hello,
I have a dabatabase running in archive log mode, recently changed, I have 5 redo log groups and one of them (the current one) shows in the v$log view, that ARC: NO, I mean, no archiving. All redo logs except it shows ARC:Yes
What does it mean?
Am I going to have problems with this redo log file?
Thanks

If you do describe on v$log, you'll find that the full column name is Archived (meaning is it archived yet?).
You could try alter system switch logfile and then check v$log again a few times after.
Use the docu for finding out more about v$ views and so on
http://www.oracle.com/pls/db102/print_hit_summary?search_string=v%24log

Status of db backup taken after 2 logs archived went missing

Hi ,
what would be the effect or issues of the full db backup & archivelog backup of 9i db taken after 2 archive logs missing that were never backed up, since backup, or crosscheck did't alerted any error messages. will this be still a valid backup to restore or recovery in case.
posting the backup script details;
note:we are not using catalog repository
run {
allocate channel dev1 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
allocate channel dev2 type disk format 'Z:\Rbackup\DMP\db_t%t_s%s_p%p';
backup database;
backup archivelog all;
delete noprompt archivelog until time 'sysdate-1' ;
crosscheck archivelog all;
release channel dev1 ;
release channel dev2 ;
}

logs missing date is Jan 14th and no backups were taken on this day. In that case, the "BACKUP ARCHIVELOG ALL" on the 15th would have generated an error flagging the missing archivelogs because the "ALL" specification is a direction to backup all known ArchiveLogs that are available for backup. The only reasons why it wouldn't have flagged the missing ArchiveLogs would be :
a. You have another job that deletes archivelogs and this one ran before the backup on 15th Jan
b. The ArchiveLogs are in the FRA and Oracle had automatically purged ArchiveLogs when the FRA was running low on free space.
The Backup on 15th is good for restore and recovery. Use the "VALIDATE" command in RMAN to validate the database and archivelogs.
See http://hemantoracledba.blogspot.com/2010/03/misinterpreting-restore-database.html
However, as two archivelogs are missing and not backed up, you will not be able to do a Point In Time Recovery to any point in time from the time of the first missing archivelog to the end of the backup of the 15th.
Hemant K Chitale

Root partition suddenly full while updating packages with Pacman

Hello
I'm not sure if this is a problem with Pacman, but my root partition seems to have become completely full while updating my system using pacman -Syu. Before updating anything, there seems to have been an update to a new version of Pacman (3.3.1-1) that needed to be installed before updating packages.
In the middle of the updates, I got this error:
error: error writing to file '/var/cache/pacman/pkg/openoffice-base-3.1.1-2-x86_64.pkg.tar.gz': No space left on device
Also, I don't know if this is related, but I got a lot of 'not found' errors after that.
The entire output from everything:
~ $ sudo pacman -Syu
Password:
:: Synchronizing package databases...
core 34.6K 101.4K/s 00:00:00 [#####################] 100%
extra 427.5K 394.3K/s 00:00:01 [#####################] 100%
community 374.7K 362.2K/s 00:00:01 [#####################] 100%
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n] y
resolving dependencies...
looking for inter-conflicts...
Targets (1): pacman-3.3.1-1
Total Download Size: 0.60 MB
Total Installed Size: 2.10 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from core...
pacman-3.3.1-1-x86_64 618.9K 455.6K/s 00:00:01 [#####################] 100%
checking package integrity...
(1/1) checking for file conflicts [#####################] 100%
(1/1) upgrading pacman [#####################] 100%
~ $ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (42): taglib-extras-1.0.1-1 qt-4.5.3-2 liblastfm-0.3.0-4
loudmouth-1.4.3-1 libmtp-0.3.7-1.1 amarok-2.2.0-1 apr-1.3.9-1
db-4.8.24-1 apr-util-1.3.9-3 apache-2.2.13-3 bluez-4.54-1
python-2.6.3-1 dbus-python-0.83.0-2.1 device-mapper-2.02.53-1
eclipse-3.5.1-1 gpm-1.20.6-3 perl-5.10.1-3 groff-1.20.1-3
vim-7.2.266-1 gvim-7.2.266-2 heimdal-1.2.1-7 inkscape-0.46-13
iproute2-2.6.29-2 lib32-db-4.8.24-1 lib32-heimdal-1.2.1-7
libical-0.44-1 libsasl-2.1.23-2 lm_sensors-3.1.1-2
lvm2-2.02.53-1 nexuiz-data-2.5.2-1 nexuiz-2.5.2-1
redland-1.0.9-4 openoffice-base-3.1.1-2 pam-1.0.4-2
php-5.3.0-5 pstoedit-3.50-1 ruby-1.9.1_p243-2 soprano-2.3.1-1
texlive-bin-2009.4-1 texlive-core-2009.15574-1 wget-1.12-1
xchat-2.8.6-5
Total Download Size: 1354.95 MB
Total Installed Size: 2035.02 MB
Proceed with installation? [Y/n] y
:: Retrieving packages from core...
db-4.8.24-1-x86_64 4.7M 432.0K/s 00:00:11 [#####################] 100%
device-mapper-2.02.... 479.0K 287.9K/s 00:00:02 [#####################] 100%
gpm-1.20.6-3-x86_64 173.2K 243.7K/s 00:00:01 [#####################] 100%
perl-5.10.1-3-x86_64 13.5M 412.5K/s 00:00:33 [#####################] 100%
groff-1.20.1-3-x86_64 4.1M 365.7K/s 00:00:12 [#####################] 100%
heimdal-1.2.1-7-x86_64 2.8M 368.5K/s 00:00:08 [#####################] 100%
iproute2-2.6.29-2-x... 489.0K 303.8K/s 00:00:02 [#####################] 100%
libsasl-2.1.23-2-x86_64 118.5K 252.4K/s 00:00:00 [#####################] 100%
lvm2-2.02.53-1-x86_64 930.3K 327.3K/s 00:00:03 [#####################] 100%
pam-1.0.4-2-x86_64 537.8K 289.5K/s 00:00:02 [#####################] 100%
wget-1.12-1-x86_64 672.4K 308.0K/s 00:00:02 [#####################] 100%
:: Retrieving packages from extra...
qt-4.5.3-2-x86_64 26.9M 418.8K/s 00:01:06 [#####################] 100%
liblastfm-0.3.0-4-x... 223.4K 252.0K/s 00:00:01 [#####################] 100%
loudmouth-1.4.3-1-x... 80.8K 183.8K/s 00:00:00 [#####################] 100%
libmtp-0.3.7-1.1-x86_64 439.4K 309.5K/s 00:00:01 [#####################] 100%
amarok-2.2.0-1-x86_64 10.9M 486.0K/s 00:00:23 [#####################] 100%
apr-1.3.9-1-x86_64 328.5K 332.4K/s 00:00:01 [#####################] 100%
apr-util-1.3.9-3-x86_64 237.6K 322.3K/s 00:00:01 [#####################] 100%
error: failed retrieving file 'apache-2.2.13-3-x86_64.pkg.tar.gz' from archlinux.unixheads.org : Connection timed out
error: failed retrieving file 'apache-2.2.13-3-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'apache-2.2.13-3-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
bluez-4.54-1-x86_64 671.6K 361.7K/s 00:00:02 [#####################] 100%
python-2.6.3-1-x86_64 15.2M 442.0K/s 00:00:35 [#####################] 100%
dbus-python-0.83.0-... 177.4K 225.6K/s 00:00:01 [#####################] 100%
eclipse-3.5.1-1-x86_64 162.0M 457.1K/s 00:06:03 [#####################] 100%
vim-7.2.266-1-x86_64 8.6M 437.9K/s 00:00:20 [#####################] 100%
gvim-7.2.266-2-x86_64 1115.4K 216.9K/s 00:00:05 [#####################] 100%
inkscape-0.46-13-x86_64 18.4M 464.6K/s 00:00:41 [#####################] 100%
libical-0.44-1-x86_64 281.3K 283.7K/s 00:00:01 [#####################] 100%
lm_sensors-3.1.1-2-... 133.2K 228.9K/s 00:00:01 [#####################] 100%
redland-1.0.9-4-x86_64 307.4K 275.7K/s 00:00:01 [#####################] 100%
error: error writing to file '/var/cache/pacman/pkg/openoffice-base-3.1.1-2-x86_64.pkg.tar.gz': No space left on device
error: failed retrieving file 'openoffice-base-3.1.1-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'openoffice-base-3.1.1-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
error: error writing to file '/var/cache/pacman/pkg/php-5.3.0-5-x86_64.pkg.tar.gz': No space left on device
error: failed retrieving file 'php-5.3.0-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'php-5.3.0-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
error: error writing to file '/var/cache/pacman/pkg/pstoedit-3.50-1-x86_64.pkg.tar.gz': No space left on device
error: failed retrieving file 'pstoedit-3.50-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'pstoedit-3.50-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
error: error writing to file '/var/cache/pacman/pkg/ruby-1.9.1_p243-2-x86_64.pkg.tar.gz': No space left on device
error: failed retrieving file 'ruby-1.9.1_p243-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'ruby-1.9.1_p243-2-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
error: error writing to file '/var/cache/pacman/pkg/soprano-2.3.1-1-x86_64.pkg.tar.gz': No space left on device
error: failed retrieving file 'soprano-2.3.1-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'soprano-2.3.1-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
error: error writing to file '/var/cache/pacman/pkg/texlive-bin-2009.4-1-x86_64.pkg.tar.gz': No space left on device
error: failed retrieving file 'texlive-bin-2009.4-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'texlive-bin-2009.4-1-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
error: error writing to file '/var/cache/pacman/pkg/texlive-core-2009.15574-1-any.pkg.tar.gz': No space left on device
error: failed retrieving file 'texlive-core-2009.15574-1-any.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'texlive-core-2009.15574-1-any.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
error: error writing to file '/var/cache/pacman/pkg/xchat-2.8.6-5-x86_64.pkg.tar.gz': No space left on device
error: failed retrieving file 'xchat-2.8.6-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : Not Found
error: failed retrieving file 'xchat-2.8.6-5-x86_64.pkg.tar.gz' from mirror.cs.vt.edu : File unavailable (e.g., file not found, no access)
warning: failed to retrieve some files from extra
error: failed to commit transaction (File unavailable (e.g., file not found, no access))
Errors occurred, no packages were upgraded.
~ $
Also, I haven't restarted my system yet. Should I try and see what happens?
Thanks!

This happened to me recently. I could not restart my laptop properly due to lack of space on my root partition.
The error during boot was along the lines of:-
Starting D-BUS system messagebus - Failed
Failed to start message bus: Failed to close "var/run/dbus.pid": No space left on drive
Hardware Abstraction Layer - Failed
everything else during the boot was as normal till I started to type in my username - but couldn't because the keyboard was inactive.
I used a Wolvix live CD to investigate and found a QT4 file in the packman cache which was 6.9GB in size (compared to the normal 27mb size). Once that was deleted and the drive/partition error checked everything was back to normal. So before you reboot I would definitely recommend clearing any oversize file out of your packman cache, or just clearing the whole cache.
Last edited by Nixie (2009-10-05 17:16:13)

ORA-00257: archiver error. Full - how to remove with Streams

So, I have not run a backup in about two weeks.
With Oracle GUI (OEM) saves my life since I am not a dba.
Now, I have filled up my archive logs drive slice. It is at 100%.
We are running Oracle streams, and I can not automatically delete backed up archive logs after a backup because streams may still be using it.
So how do I fix the problem!!!
Oracle 10.2.0.2
So can I delete the archive logs... Well, no, because if I remove them from the OS, Oracle will still think they are there or should be there...
OK command line mode, RMAN backup, yikes, not at that level yet.
Then how to remove the archive logs...
Question:
I read a document on streams...
How to identify redo logs that streams no longer needs:
SELECT name
FROM v$archived_log
WHERE next_change# < (SELECT first_scn FROM dba_capture);
Does this mean these can be deleted?
Identify redo logs that Streams has purged:
SELECT file_name
FROM dba_logmnr_purged_log;
Again, does this mean these can be deleted?
The numbers are not the same.

Rman should take care of that. It is aware of which archived logs are needed by streams.

Log archive partition is full

Similar Messages

Maybe you are looking for