I have been tasked with archiving Oracle tables. The data is on raw devices, and possibly will span multiple logical volumes.
Has anyone ever had to do this? How did you accomplish it?
Any references to accomplish this would be greatly appreciated.
Thanks, (2 Replies)
Hello
I wonder if someone could help me in reading a raw (non-Solaris) disk on a Solaris system...
I have an IDE HDD in my Sun Blade and would like to read it (using C). It appears on the system and with the format command shows up as c0t1d0.
I use the dd command to read the disk as such:... (19 Replies)
Hi all,
I would like to know how to make new partitions....
I currently have allocated 60G for various slices (I have totally used 4 out of 7 available slices...
I am running only solaris on my box.
My plan is to have entire disk dedicated to solaris and run other OS from within... (19 Replies)
I am using Solaris 10. I have a raw device attached to my system which is
/dev/md/rdsk/d91
I want to mount this as a disk with file system on a mount point /u05.
Actually this raw device was earlier part of Oracle ASM. Now I have removed this disk from ASM, and want to use it as normal... (3 Replies)
Hi,
Can any one please provide the command to format an Oracle Raw Disk in Solaris 10.
I have been used the following commands:
dd if=/dev/zero of=<raw disk path>
Thanks
---------- Post updated at 12:20 PM ---------- Previous update was at 10:11 AM ----------
Well this didn't give... (0 Replies)
I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below:
root@moneta # df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 9.8G 513M 9.3G 6% /
... (0 Replies)
I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below:
root@moneta # df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Hi,
I'm in process of creating oracle RAC using Solaris 10 in VirtualBox. I want to know how can I change the ownership of device e.g /dev/rdsk/c0t3d0s0 and keep it persistent during rebbots.
When I enter
chown grid:install /dev/rdsk/c0t3d0s0
ls -l still shows root:root.
Thanks
... (2 Replies)
Hi All,
Hope someone can help me with this.
I have noticed that on some of the servers i am currently administering there is a difference in the setup of some of the LVM disks.
Some of the disks have been created by SN disk allocated, disk partitioned using type 8e over the entire disk,... (2 Replies)
Discussion started by: Tommyk
2 Replies
LEARN ABOUT CENTOS
systemd.slice
SYSTEMD.SLICE(5) systemd.slice SYSTEMD.SLICE(5)NAME
systemd.slice - Slice unit configuration
SYNOPSIS
slice.slice
DESCRIPTION
A unit configuration file whose name ends in ".slice" encodes information about a slice which is a concept for hierarchially managing
resources of a group of processes. This management is performed by creating a node in the Linux Control Group (cgroup) tree. Units that
manage processes (primarilly scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may the
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchially in a tree. The name of the
slice encodes the location in the tree. The name consists of a dash-separated series of names, which describes the path to the slice from
the root slice. The root slice is named, -.slice. Example: foo-bar.slice is a slice that is located within foo.slice, which in turn is
located in the root slice -.slice.
By default, service and scope units are placed in system.slice, virtual machines and containers registered with systemd-machined(1) are
found in machine.slice, and user sessions handled by systemd-logind(1) in user.slice. See systemd.special(5) for more information.
See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic
[Unit] and [Install] sections. The slice specific configuration options are configured in the [Slice] section. Currently, only generic
resource control settings as described in systemd.resource-control(7) are allowed.
Unless DefaultDependencies=false is used, slice units will implicitly have dependencies of type Conflicts= and Before= on shutdown.target.
These ensure that slice units are removed prior to system shutdown. Only slice units involved with early boot or late system shutdown
should disable this option.
SEE ALSO systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)systemd 208SYSTEMD.SLICE(5)