Oracle RAC and crossover cable for private network

Hi,
I have the following configuration: two database servers, each has four network cards, two for public network and two for private, cluster network. Each public card has own IP-address and both have virtual IP-address, defined in operation system (SLES-9) for redundancy. Because I have only two machines in the cluster I want to connect the two machines for private with crossover cable without switch. For redundancy I want to make two connections between machines. Is it at all possible? How should I defined all network interfaces and what should be included in /etc/hosts for properly work of Oracle cluster?
Best Regards,
Jacek

Hi,
You can build a RAC witch CROSSOVER, but the Oracle no homolog.
As you have 4 cards, 2 to public (redundancy) and 2 to interconnect (redundancy) you need of a software to to make a TEAM, and create a card virtual that will have a IP address.
Eder

Similar Messages

Need to understand basics of Oracle RAC and Grid technology, for training

I need to understand Oracle RAC and Grid infrastructure, from a manager's / training perspective.
I see links here and here, so a couple questions:
- what's the basic difference from a layman's (e.g., a manager's) perspective ?
- What training options are available for a generic 11g DBA to learn this new technology ? I've seen this course from an Oracle partner ("Course:Oracle 11g: RAC and Grid Infrastructure Administration Accelerated Release 2"), for a boat load of money, for 5 days I think. So we're looking for something a little more reasonable (and accessible), e.g., books, online, etc.

Wm Peck 1958 wrote:
I need to understand Oracle RAC and Grid infrastructure, from a manager's / training perspective.
I see links here and here, so a couple questions:
- what's the basic difference from a layman's (e.g., a manager's) perspective ?
- What training options are available for a generic 11g DBA to learn this new technology ? I've seen this course from an Oracle partner ("Course:Oracle 11g: RAC and Grid Infrastructure Administration Accelerated Release 2"), for a boat load of money, for 5 days I think. So we're looking for something a little more reasonable (and accessible), e.g., books, online, etc.
For a very basic definition, RAC is technology that is used by the database and GI is the infrastructure that makes RAC work. In a forum reply, that's probably all what can be said about both. For a very lengthy answer, you should read the links that you have quoted.
For #2, the course that you are looking at is called Accelerated as it combines two courses in a single week training-RAC(4) and GI(3). So it's a 7 day curriculum that one would be doing in a 5 day course and that should justify its cost. But let me say, it's a really really good course. But on the other side, it can be quite overwhelming for someone who doesn't know about these technologies already. So I shall suggest that you send your team to each course individually and probably after doing some homework . They can start reading the following books,
Pro Oracle Database 11g RAC on Linux
https://www.mheducation.co.in/html/9781259004063.html
And this doc link,
Oracle Database Online Documentation 11g Release 2 (11.2)
Aman....

File and printer sharing for Microsoft Networks on Windows server 2008

Hi Expert,
I found that the properties of File and printer sharing for Microsoft Networks service disabled after I install the windows server 2008 64bits. I tried to install that service via adding the file and printer sharing services in the properties of local area connection, but it doesn't contain any service in the popup box. Also, no such service file available in the disk when I tried to install the service from installation disk of windows server 2008 64bits. Is the file "sacsrv.dll" corresponding to the service name of file and printer sharing? I found it is in the directory of "Windows\system32". I have no idea about where is the problem? Do I miss some components? Please tell me what can I do for it? Thanks!
Best Wishes,

Do any experts know the reason of this problem? Thanks!

Script to disable Client for Microsoft Networks and File and Print Sharing for Microsoft Networks

Hi, I am trying to find a way of using a batch file or vbscript to disable Client for Microsoft Networks and File and Print Sharing for Microsoft Networks on a Network Interface Controller.
I've done some searching on the internet and I can see some suggestions to locate the Setting ID of the NIC and then remove the value from the "Bind" string under "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Linkage" and "HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Linkage"
I tried this but it didn't seem to uncheck itself from the NIC properties under NCPA.cpl
Can someone help me?

http://social.msdn.microsoft.com/Forums/vstudio/en-US/b0407073-07bc-462b-9de9-7295be5fa183/disable-file-and-printer-sharing-for-mircorosoft-networks?forum=csharpgeneral
¯\_(ツ)_/¯

How to uncheck File and Printer Sharing for Microsoft Networks by Command!!

Dear everybody,
I meet a problem with my System now, and I need your help!!!
As mentioned in title, I need uncheck on File and Printer Sharing for Microsoft Networks by Command for Security purpose.
Could you show me the way to do it by command line
I think GPO can solve this but My Boss want to do it by command line
Thanks for your help!!!

netsh advfirewall firewall set rule group="Network Discovery" new enable=Yes
netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes
To disable these functions in Windows, use the same command and replace 'Yes' to 'No' in the above commands.

X301 "File and Printer Sharing for Microsoft Networks" removed at re booting (XP SP-3)

Even if I run the “Network Identification Wizard” (under System properties/Computer Name) to join a Workgroup, the box ‘File and Printer Sharing for Microsoft Networks’ remains unchecked. If I ticked it manually, it remains checked for the current session, but it is unchecked at booting.
The same occurs with the Windows Firewall (I am running that from Symantec). I switch the Windows Firewall off, but after rebooting, it appears selected again!.
This happens only with my brand new ThinkPad X301, which came with Vista. The package included a kit to convert to XP, but this installed a ‘naked’ XP, which required downloading from Lenovo and Windows about 1Gb of files (bad service, Lenovo guys!).
I wonder which “safety” issue of the X301 causes this, but how can I stop this happening? (It does not occur with any of my two old ThinkPads, also running XP SP-3 and Lenovo software).
Solved!
Go to Solution.

See -> http://www.vistax64.com/vista-networking-sharing/72537-file-printer-sharing-turned-off-reboot.html Here is the text. Re: File and Printer sharing turned off on reboot
I FOUND MY SOLUTION!!!
In my case, it was in Lenovo's "ThinkVantage Access Connections" applet. It
is additional security that is applied at the CONNECTION level.
Here is how I fixed it:
1. Double click on the ThinkVantage Access Connections applet in the
notification area.
2. Click on the MANAGE button on the toolbar
3. Select the SSID where you want File Sharing to work, and click EDIT
4. Click on the ADDITIONAL SETTINGS tab
5. Next to "Network Security", click the SETTINGS button
6. The first option in Security Settings is "Disable file and printer
sharing". UNCHECK this box. Click OK for 3 levels of dialog boxes, then
close Access Connections
Although these directions are specific to ThinkPad notebooks, the same
principle may apply for other manufacturers' connection managers.
Best of luck!

File and Printer Sharing for Microsoft Networks is missing

I have a Server 2012 Hyper-V VM that is missing the File and Printer Sharing for Microsoft Networks. When I try to Install the service it is not listed. The only service listed is Windows Network Virtualization Filter driver. I have the install media but
I don't know where the driver would be located. I'm hoping someone can tell me where it is located.
Update:
I am trying to run Enable-NetAdapterBinding -Name Ethernet -ComponentID ms_server but it's not working and it's giving me this error.
Enable-NetAdapterBinding : No matching MSFT_NetAdapterBindingSettingData objects found by CIM query for instances of
the ROOT/StandardCimv2/MSFT_NetAdapterBindingSettingData class on the CIM server: SELECT * FROM
MSFT_NetAdapterBindingSettingData WHERE ((Name LIKE 'Ethernet')) AND ((ComponentID LIKE 'ms[_]server')). Verify query
parameters and retry.
At line:1 char:1
+ Enable-NetAdapterBinding -Name Ethernet -ComponentID ms_server
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (MSFT_NetAdapterBindingSettingData:String) [Enable-NetAdapterBinding], C
   imJobException
    + FullyQualifiedErrorId : CmdletizationQuery_NotFound,Enable-NetAdapterBinding
Vincent Sprague

Ok, fixed it, I found the netserv.inf file in c:\windows\inf and tried to use it to reinstall File and Printer Sharing. However File and Printer Sharing was not listed. I copied the netserv.inf file from another Server 2012 VM and was able to install File
and Printer Sharing using the copied NetServ.inf. After rebooting the server I was able to access network shares on the server.
Vincent Sprague

Oracle RAC and Datastage

Could anyone tell me If you have some Best Practices with Oracle RAC and Datastage ETL. I am concerned about performace of ETL loads into oracle database......

http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/bus_intl.htm#sthref2435
Your answers are just a few clicks beyond the URL below.
http://tahiti.oracle.com

Oracle RAC and ASM for SAP in SLES

Hello,
We are installing our SAP ERP with Oracle RAC 11.2.0.2 on SLES 11 x86_64. According note 527843 (Oracle RAC support in the SAP environment), this is supported for SAP. But as a requirement ASM Cluster File System must be setup.
But when Oracle Grid is installed, ACFS installation returns the following error:
ACFS-9459: ADVM/ACFS is not supported on this OS version: 'sles-release-11.1-1.152'
So Oracle GRID has been installed without ACFS, so we will not be able to use Oracle Clusterware for providing high availability of SAP.
As this is supposed to be a feasible combination (Oracle RAC 11.2.0.2 with ASM on SLES 11 SP1, Netweaver 7.0), I'm wondering if it is a bug, a lack of documentation or something I'm missing.
Kind regards,
Fermí

Read this below Oracle Note:
ACFS not supported on certain platforms [ID 1075058.1]
oracle@node1:~/app/oracle/product/grid/log/node1> tail -1 alertesiha.log
[client(14083)]CRS-10001:ADVM/ACFS is not supported on SUSE
Then these can be ignored, since ACFS/ADVM may not be supported for your platform. As of this writing, Sun, AIX, SuSE 10 are all supported in 11.2.0.2 only. HP-UX, SuSe 11 and RH6.0, as well as Oracle UEK ((2.6.32-100*) are not yet supported in 11.2.0.2. Keep in mind that this does not prevent your Grid Infrastructure stack (Clusterware and ASM) from starting. This is just an informational message for these platforms
Extract from SAP Note:
RAC 11.2.0.2 (x86 & x86_64 only):
Oracle Clusterware 11.2.0.2 + ASM/ACFS 11.2.0.2 (currently only for SLES10, RHEL5, OL 5.x (without UEK))
Thanks
Srikanth M

Infrastructure suggestion for Oracle RAC and Dataguard

Hello,
We are working on migration business proposal and need to suggest HA and DR infrastructure solution with Oracle 11G databases. I am thinking to suggest Oracle 11g RAC and Dataguard to meet this requirement. We also wanted to cover Dev, Test and Pre Prod along with Prod in new environment. Can someone suggest cost effective, stable and scalable infrastructure for this requirement
Best regards,
Venkat

In terms of cost ? Perhaps.
In terms of performance? NO.
Bear in mind I'm not trying to sell anything here, but in my experience hardly anything matches the performance of Exadata. It has specific features for the DB such as de iDB protocol which enables the offloading of queries to the exadata storage servers. More unique features include: storage indexes, HCC compression, smart flash cache... It's all a matter of how much you want to spend.
Yes, you can have all your servers on the same box if you want, just make sure it is not a single point of failure. (Have appropriate safeguards in place in case of power failure, Data center catastrophes, etc). In case of LPARs on the same box, be aware of one server over-utilizing resources which would affect the other LPARs (configurable).
More info on Exadata: http://www.oracle.com/technetwork/server-storage/engineered-systems/exadata/dbmachine-x3-twp-1867467.pdf
If your company has a tight budget you might also look at your options with Database appliance: http://www.oracle.com/technetwork/server-storage/engineered-systems/database-appliance/documentation/oracle-db-appliance…
Database appliance has more flexibility in terms of licensing and it's also a complete hardware solution from oracle for Databases.
Regards

Database replication between Oracle RAC and Oracle Standalone DB in 9i

Hi,
We have currently 4 node RAC environment and Oracle RAC implementation with 4 Oracle instances. We want to move the one instance and make it Standalone with Oracle database due to availability issue. Thus we will remain with 3 nodes on the RAC database and one Standalone database. We want to implement Oracle replication on this solution, where partial database of RAC environment needs to be replicated to Standalone node.
We will have Oracle 9i database server for both RAC and Standalone machine.
The partial data that we are looking for replication are of size 25GB. Some of questions we have:
1. Is there any other replication mechanism apart from Materilzed view for this solution?
2. Is it feasible to sychronize around 25GB data between servers?
3. What can be estimated time for refresh or Synchronization?
The methods that we are evaluating currently for this replication are:
1. Multi Master replication
2. Oracle 9i Datagaurd.
Please let me know if we need to look for some other methods of replication also.
Thanks in advance for help.

ManojMac wrote:
The partial data that we are looking for replication are of size 25GB. Some of questions we have:
1. Is there any other replication mechanism apart from Materilzed view for this solution?Streams is another option
2. Is it feasible to sychronize around 25GB data between servers?Sure. Depending on the rate of change, your latency requirements, whether the standalone database has the horsepower to apply all the changes generated by to other three nodes, etc.
3. What can be estimated time for refresh or Synchronization?Depends on the architecture, the network connection, whether you are doing incremental refreshes, etc. And it depends on what time you're measuring-- you might be measuring the latency between the RAC cluster and the standalone database, you might be measuring the time it takes to incrementally refresh a single materailized view when there have been no changes, you might be measuring the time it takes to do a complete refresh of an entire refresh group, pulling 25 GB of data over the network.
The methods that we are evaluating currently for this replication are:
1. Multi Master replication
2. Oracle 9i Datagaurd.DataGuard is not an option if you only want to replicate a subset of the data. The two realistic options are materialized views and Streams. Are you anticipating that you will be making changes on both nodes? If not, you can use simple materialized views rather than multi-master replication.
Since 9.2 is not longer covered by Premier Support, are you planning to upgrade to a supported version in the near future? In particular, Streams works a lot better in later versions of the database.
Justin

SC 3.1/3.2 Oracle RAC and EMC replication

hi,
i need to cluster existing 2 node Oracle RAC for disaster recovery. The secondary site is about 180 km away, there is another site 10 km away which is planned to be use for bunker replication (SRDF/STAR). Is it possible to build such topology with Sun Cluster 3.1/3.2? Network connection to all sites is provided (min. 10Gbp).
What is needed to complete this task with SC?

I would recommend that you read my Blueprint from April 2006 (Architecting Availability and Disaster Recovery Solutions) as this has a lot of background on the subject.
First, you will need to implement it as a two node cluster plus a single node disaster recovery system. Ideally, the two node cluster would be configured between the two 'local' sites, i.e. with the site that is 10Km away. The remote site, at 180Km, would then be used for the disaster recovery system.
The recently announced Sun Cluster 3.2 Geographic Edition adds support for SRDF, so you could use Sun Cluster 3.2 and Geo Edition with SRDF for this. I would add that disk block based replication is not ideal for this as it does involve a lot of unnecessary replication data traffic compared with something like Oracle Data Guard. This would be my preferred option, although this is not currently integrated with Geo Edition.
If you need any more info or help, please post again.
Tim
---

Shared Variables using Two Computers and Crossover Cable

I'm just trying to put together a simple bench test tying two computers together by a crossover cable. They ping correctly to each other. I used the LabVIEW examples for TCP connections and they talk correctly that way too. I try to build and deploy shared variables on one computer, but the other computer will not identify the SV's on the first computer and vice versa.
Can someone give me some details on how to build, deploy, and effectively use SV's? I've read all the NI documentation, but I'm not getting the step-by-step approach very well.
Thanks.
Nathan - Certified LabVIEW Developer
Solved!
Go to Solution.

Are you making them network published shared variables and binding them to each other? This doc gives a pretty good step by step:
http://digital.ni.com/public.nsf/allkb/7815BCE435DCC432862575DA006FEBF8
--Ryan

Setting Up Mailserver to received and Send Mail for external Network

I have a G5 currenty running 10.3.9 Server with Mail services run and working fine, we are upgrading to 10.4 Server and would like our Sales Reps the ability to send and Receive mail from outside the office. How do I configure my server, Router, ISP and/or Mail clients to do this??? we are currently able to recieve mail from outside just not send.

I cannot find the Line #submission inet n - n -- smtpd in the Main.CF file...here is what I get when I open it
# Global Postfix configuration file. This file lists only a subset
# of all 250+ parameters. See the sample-xxx.cf files for a full list.
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# sample-smtpd.cf).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination and $inet_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see sample-local.cf).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# $inet_interfaces, while $local_recipient_maps is non-empty and the
# recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#unknown_local_recipient_reject_code = 550
unknown_local_recipient_reject_code = 450
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in file sample-smtpd.cf.
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions restriction in the
# file sample-smtpd.cf for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction in the file sample-smtpd.cf.
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = gateway.my.domain
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 50 SMTP server process
# limit, this limits the mail inflow to 50 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# Insert text from sample-virtual.cf if you need virtual domain support.
# "USER HAS MOVED" BOUNCE MESSAGES
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.
# TRANSPORT MAP
# Insert text from sample-transport.cf if you need explicit routing.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination
# and unknown@[$inet_interfaces] is returned as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see the sample-filter.cf file.
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#fast_flush_domains = $relay_domains
#fast_flush_domains =
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 10
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you don't have X installed on the Postfix machine, try:
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
# THE FOLLOWING DEFAULTS ARE SET BY APPLE
# bind to localhost only
inet_interfaces = all
# turn off relaying for local subnet
mynetworks_style = host
# mydomain_fallback: optional domain to use if mydomain is not set and
# myhostname is not fully qualified. It is ignored if neither are true.
mydomain_fallback = localhost
myhostname = jamestownpress.com
mailbox_transport = cyrus
enable_server_options = yes
luser_relay =
maps_rbl_domains = dun.dnsrbl.net
message_size_limit = 0
mydestination = $myhostname,localhost.$mydomain
smtpd_use_tls = no
smtpd_enforce_tls = no
smtpd_tls_loglevel = 0
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = plain
server_enabled = 1
relayhost =
smtpd_client_restrictions = permit_mynetworks reject_rbl_client dun.dnsrbl.net permit
always_bcc =
mynetworks = 127.0.0.1/32,192.168.0.0/16,192.168.1.98,192.168.1.3,192.168.1.13,192.168.1.5,1 92.168.1.22,192.168.1.18,192.168.1.41
content_filter = smtp-amavis:[127.0.0.1]:10024
so what do I need to change

Oracle RAC and datacontrol

Hello, I have an Oracle RAC 10gR2 with 2 nodes on Suse Linux Enterprise Server 10. When I enter on the enterprise manager database control (no grid control). I see the follow message:
"Availability calculations for the cluster database target are disabled. Please enable the DBMS JOB EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS for Database Control."
What is it? How can I clean it?
Thanks in advance.

Check out MOS note :
What is EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS dbms_job and how to Remove / Re-create it [ID 444033.1]
Regards
Rajesh

Oracle RAC and crossover cable for private network

Similar Messages

Maybe you are looking for