Full Discussion: Server replication
Operating Systems Solaris Solaris BigAdmin RSS Server replication Post 302470828 by aravindan on Thursday 11th of November 2010 07:48:39 AM
Lightbulb Server replication


We are planning to setup a new server at new location (A) having a server (which is at location B) as reference.
What (all) parameters do we need to keep in mind, when we plan to replicate a server?
My thanks in advance.

Test Your Knowledge in Computers #251
Difficulty: Easy
MILNET was designed for highly classified military communications.
True or False?

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

dns replication

my primary dns server is not replicating to secondary. i dont know why. i am running solaris 2.6 on both servers. what should i do?:confused: (2 Replies)
Discussion started by: lealyz
2 Replies

2. UNIX for Dummies Questions & Answers

BIND DNS replication

I have a RedHat 7.1 box that we use for DNS in our System Engineering lab. We have a Windows 2000 box that handles DNS in our main office. The Microsoft Admin and I have been given the task of making both of our domains accessible to each other. I had originally made his domain my forwarder, so... (5 Replies)
Discussion started by: Jody
5 Replies

3. HP-UX

HP Unix replication solution

Hi, I looking to setup HP Unix to HP Unix replication as plan of business continuity. The setup can be active passive or active active. Anyone can give me some idea what solution able to perform that? Thanks (3 Replies)
Discussion started by: ufo_999
3 Replies

4. UNIX and Linux Applications

Need Oracle Replication steps.

Hi All, Can anybody tell that Where is to find simple and easy steps of ORACLE replication process? Any help on this highly appreciated. http://www.unix.com/images/misc/progress.gif Thanks. (1 Reply)
Discussion started by: amit_27
1 Replies

5. SCO

Replication using NFS.

Hi all, I am going to implement a script which will use NFS to replicate data between two SCO unix servers. It will take files with mtime -1 and copy the data periodically .In this regard my questions are : Is this approach good and reliable enough with respect... (2 Replies)
Discussion started by: dextergenious
2 Replies

6. Red Hat

Openldap 2.4.31 replication

Hi, I have done setup for openldap master and slave. Its working fine and replicating also. But it is working only with plane text password in syncrepl . How we can use encrypted password here also like we are using in rootpw ? Below portion is working. syncrepl rid=101 ... (3 Replies)
Discussion started by: Priy
3 Replies

7. Linux

Mysql replication

Need to recover a replication broken error on the mysql slave server. I want to force it to resend the binlog file from the begining. What is the correct value for the: MASTER_LOG_POS ? 0, 1 or 107 ? (2 Replies)
Discussion started by: andriesh
2 Replies

8. HP-UX

Database replication process stopped in server

Hi, A database (Oracle) replication process was executed by the DBA team in one server (serverX). However, this replication process gets terminated, and there are no errors in the replication log. But there is error in the OS log files (syslog.log) : Aug 8 16:51:47 L28dre02 sshd: subsystem... (1 Reply)
Discussion started by: anaigini45
1 Replies
PREPARE(7)							   SQL Commands 							PREPARE(7)

PREPARE - create a prepared query SYNOPSIS
PREPARE plan_name [ (datatype [, ...] ) ] AS query INPUTS plan_name An arbitrary name given to this particular prepared query. It must be unique within a single session, and is used to execute or remove a previously prepared query. datatype The data-type of a parameter to the prepared query. To refer to the parameters in the prepared query itself, use $1, $2, etc. OUTPUTS PREPARE The query has been prepared successfully. DESCRIPTION
PREPARE creates a prepared query. A prepared query is a server-side object that can be used to optimize performance. When the PREPARE statement is executed, the specified query is parsed, rewritten, and planned. When a subsequent EXECUTE statement is issued, the prepared query need only be executed. Thus, the parsing, rewriting, and planning stages are only performed once, instead of every time the query is executed. Prepared queries can take parameters: values that are substituted into the query when it is executed. To specify the parameters to a pre- pared query, include a list of data-types with the PREPARE statement. In the query itself, you can refer to the parameters by position using $1, $2, etc. When executing the query, specify the actual values for these parameters in the EXECUTE statement -- refer to EXECUTE [execute(7)] for more information. Prepared queries are stored locally (in the current backend), and only exist for the duration of the current database session. When the client exits, the prepared query is forgotten, and so it must be re-created before being used again. This also means that a single prepared query cannot be used by multiple simultaneous database clients; however, each client can create their own prepared query to use. Prepared queries have the largest performance advantage when a single backend is being used to execute a large number of similar queries. The performance difference will be particularly significant if the queries are complex to plan or rewrite. For example, if the query involves a join of many tables or requires the application of several rules. If the query is relatively simple to plan and rewrite but rel- atively expensive to execute, the performance advantage of prepared queries will be less noticeable. NOTES In some situations, the query plan produced by PostgreSQL for a prepared query may be inferior to the plan produced if the query were sub- mitted and executed normally. This is because when the query is planned (and the optimizer attempts to determine the optimal query plan), the actual values of any parameters specified in the query are unavailable. PostgreSQL collects statistics on the distribution of data in the table, and can use constant values in a query to make guesses about the likely result of executing the query. Since this data is unavailable when planning prepared queries with parameters, the chosen plan may be sub-optimal. For more information on query planning and the statistics collected by PostgreSQL for query optimization purposes, see the ANALYZE [ana- lyze(7)] documentation. COMPATIBILITY
SQL92 SQL92 includes a PREPARE statement, but it is only for use in embedded SQL clients. The PREPARE statement implemented by PostgreSQL also uses a somewhat different syntax. SQL - Language Statements 2002-11-22 PREPARE(7)

Featured Tech Videos

All times are GMT -4. The time now is 06:23 AM.
Unix & Linux Forums Content Copyright 1993-2019. All Rights Reserved.
Privacy Policy