Sponsored Content
Operating Systems Solaris 3320 Disk Array Configuration for Oracle 10 Post 302298418 by StarSol on Tuesday 17th of March 2009 12:43:30 PM
Old 03-17-2009
I could install the package. I will put the information requested shortly

Last edited by StarSol; 03-17-2009 at 06:43 PM..
 

10 More Discussions You Might Find Interesting

1. Solaris

LaCie Big Disk configuration on SUN 280R

hi , i am trying to configure LaCie Big Disk on solaris 9 running on a 280R server . i am trying to use the USB prot to connect to the external disk . please i need help on this as i have no clue on how and from where to start . thanks for ur help . cheers (0 Replies)
Discussion started by: ppass
0 Replies

2. Shell Programming and Scripting

bash array passed to oracle

Hi all.. Does anyone know have an example of passing the contents of a bash array to oracle? basically I am looking to loop through the contents of a file(not csv!) and store each line into a bash array. Once i have this I can then pass the array into an oracle procedure that accepts an array... (1 Reply)
Discussion started by: satnamx
1 Replies

3. Solaris

Disk Array

So I have 2 solaris sun servers one with a disk array with 14 drives which I need to move to the other server. How do I move the disk array configured as a Raid 5 to another server without losing data? So far I know I'll connect the drive, run devfsadm, use format to verify the server see's... (5 Replies)
Discussion started by: Kjons76
5 Replies

4. Filesystems, Disks and Memory

Backup Sun StorageTek Common Array Manager's configuration

In Sun manuals, I didn't find how to backup Sun StorageTek Common Array Manager's configuration. Is there a way to do it like backing up Brocade switch configuration? CAM is under Solaris 10. Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 Replies

5. UNIX for Advanced & Expert Users

Disk Array

HI: I have a DUAL redundant system running in HP-UX 10.20 ( 2 servers) Both servers share an external SCSI disk array. Both server runs a Data base wich uses the disk array to write the data, and that is the way they share the information. The way that the servers see the disk array, is like... (1 Reply)
Discussion started by: pmoren
1 Replies

6. Solaris

Can not access storedge 3320 info

Hey guys I am new at Solaris 10, and I'm having a open error on /dev/dsk/c1t1d0s6, when booting. We have a Sunfire v240 running Solaris 10, which is connected to a Storedge 3320, via SCSI. Any help, is appreciated (14 Replies)
Discussion started by: sirkanto
14 Replies

7. Shell Programming and Scripting

Read Oracle connection details from a configuration file

Hi, Is it possible to pass oracle connection information from a configuration file and use that to connect to oracle database in my unix shell scripts. Following is the scenario: (1) I would like to save oracle connection string details in a configuration file (ex., dbconfig.txt) (2) from my... (6 Replies)
Discussion started by: sudhakaratp
6 Replies

8. Filesystems, Disks and Memory

DISK ARRAY PROTECTION SUSPENDED message displayed following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (1 Reply)
Discussion started by: terrya
1 Replies

9. AIX

DISK ARRAY PROTECTION SUSPENDED message following disk replacement

Hello, On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active. We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED. ... (3 Replies)
Discussion started by: terrya
3 Replies

10. AIX

Replaced pdisk not showing up in SAS Disk Array Configuration

OSLevel: 5300-10-02-0943 System Model: IBM,8203-E4A Power 6 == Hi! I replaced a failed pdisk in the raid enclosure as follows, - rmdev -l 'pdisk18' '-d' - Replaced it. - cfgmgr (detected) - I can see the new drive, with the correct serial # lscfg -v -l pdisk18 pdisk18... (2 Replies)
Discussion started by: estrar
2 Replies
DH_INSTALL(1)							     Debhelper							     DH_INSTALL(1)

NAME
dh_install - install files into package build directories SYNOPSIS
dh_install [-Xitem] [--autodest] [--sourcedir=dir] [debhelperoptions] [file...dest] DESCRIPTION
dh_install is a debhelper program that handles installing files into package build directories. There are many dh_install* commands that handle installing specific types of files such as documentation, examples, man pages, and so on, and they should be used when possible as they often have extra intelligence for those particular tasks. dh_install, then, is useful for installing everything else, for which no particular intelligence is needed. It is a replacement for the old dh_movefiles command. This program may be used in one of two ways. If you just have a file or two that the upstream Makefile does not install for you, you can run dh_install on them to move them into place. On the other hand, maybe you have a large package that builds multiple binary packages. You can use the upstream Makefile to install it all into debian/tmp, and then use dh_install to copy directories and files from there into the proper package build directories. From debhelper compatibility level 7 on, dh_install will fall back to looking in debian/tmp for files, if it doesn't find them in the current directory (or whereever you've told it to look using --sourcedir). FILES
debian/package.install List the files to install into each package and the directory they should be installed to. The format is a set of lines, where each line lists a file or files to install, and at the end of the line tells the directory it should be installed in. The name of the files (or directories) to install should be given relative to the current directory, while the installation directory is given relative to the package build directory. You may use wildcards in the names of the files to install (in v3 mode and above). OPTIONS
--list-missing This option makes dh_install keep track of the files it installs, and then at the end, compare that list with the files in the source directory. If any of the files (and symlinks) in the source directory were not installed to somewhere, it will warn on stderr about that. This may be useful if you have a large package and want to make sure that you don't miss installing newly added files in new upstream releases. Note that files that are excluded from being moved via the -X option are not warned about. --fail-missing This option is like --list-missing, except if a file was missed, it will not only list the missing files, but also fail with a nonzero exit code. -Xitem, --exclude=item Exclude files that contain item anywhere in their filename from being installed. --sourcedir=dir Look in the specified directory for files to be installed. Note that this is not the same as the --sourcedirectory option used by the dh_auto_* commands. You rarely need to use this option, since dh_install automatically looks for files in debian/tmp in debhelper compatibility level 7 and above. --autodest Guess as the destination directory to install things to. If this is specified, you should not list destination directories in debian/package.install files or on the command line. Instead, dh_install will guess as follows: Strip off debian/tmp (or the sourcedir if one is given) from the front of the filename, if it is present, and install into the dirname of the filename. So if the filename is debian/tmp/usr/bin, then that directory will be copied to debian/package/usr/. If the filename is debian/tmp/etc/passwd, it will be copied to debian/package/etc/. Note that if you list exactly one filename or wildcard-pattern on a line by itself in a debian/package.install file, with no explicit destination, then dh_install will automatically guess the destination even if this flag is not set. file ... dest Lists files (or directories) to install and where to install them to. The files will be installed into the first package dh_install acts on. EXAMPLE
Suppose your package's upstream Makefile installs a binary, a man page, and a library into appropriate subdirectories of debian/tmp. You want to put the library into package libfoo, and the rest into package foo. Your rules file will run "dh_install --sourcedir=debian/tmp". Make debian/foo.install contain: usr/bin usr/share/man/man1 While debian/libfoo.install contains: usr/lib/libfoo*.so.* If you want a libfoo-dev package too, debian/libfoo-dev.install might contain: usr/include usr/lib/libfoo*.so usr/share/man/man3 LIMITATIONS
dh_install cannot rename files or directories, it can only install them with the names they already have into wherever you want in the package build tree. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 8.9.0ubuntu2.1 2012-06-12 DH_INSTALL(1)
All times are GMT -4. The time now is 09:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy